Codec / Transcoding information returned by ng query

Abierto
  • ¿Algo no está bien?
#1,807 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
perl
Área
audio-video-rtc

Línea de trabajo

Start from the handler that builds the ng query reply in the rtpengine control protocol and see what per-call state is already available there. Codec selection is decided during SDP handling for the A-leg and B-leg media streams, so trace where negotiated codecs and any transcoding decision are recorded on the call. Nothing in the issue names files or tests, so locating those entry points is the first task. Done means the ng query output reports A-leg and B-leg codecs plus a flag for whether transcoding was engaged.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Is your feature request related to a problem? Please describe

When a call is established and the ng query command is ran, we get a lot of useful information about what is happening, however this information about what codecs are being used.

This is particularly important if we want to limit the amount of transcoded calls which are allowed to pass through a system. By being able to know if transcoding was engaged for a specific call we can better help to control the capacity allowed from OpenSIPs/Kamalio, etc.

Describe the solution you'd like

If RTPEngine is aware of what codec's are used the information should be available in the response to the ng query command.

This can include:

  1. A-leg / B-leg codecs which are used
  2. Has the call been transcoded
Describe alternatives you've considered

There is no simple feasible solution.

The rtpengine version you checked that didn't have the feature you are asking for

12.1.1

Lenguaje dominante
Perl
Estrellas
992
Forks
459
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de sipwise/rtpengine

Todos los issues de sipwise/rtpengine

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.