possible regression regarding one-way audio calls in version 13.5.1.25, 13.5.1.27

Abierto
  • ¿Algo no está bien?
#2,161 16 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
perl
Área
audio-video-rtc, networking

Línea de trabajo

The report describes one-way audio after upgrading from 13.5.1.13 to 13.5.1.25/.27, but gives no reproduction steps and only production observations. Start by diffing the 13.5.1.13..13.5.1.25 commits and reading the changelog for changes in RTP forwarding or session setup, noting anything around websocket control or the Kamailio RPC-managed instance handling. Done would be a reproduction or a bisected commit that isolates the regression.

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

Descripción

bug
rtpengine version the issue has been seen with

13.5.1.25-1~bpo12+1

Used distribution and its version

Debian 12

Linux kernel version used

No response

CPU architecture issue was seen on (see uname -m)

x86_64

Expected behaviour you didn't see

The rtpengine should route the calls without one-way audio.

Unexpected behaviour you saw

After an update from 13.5.1.13-1~bpo12+1 to 13.5.1.25-1~bpo12+1 we saw a much higher number of one-way audio calls on the new production rtpengine instance. The instance was removed after one hour, but the number of one-way calls were multiple times higher on the new rtpengine as on the old. The new .25 version rtpengine instance was left running for some time, to eliminate eventual statistical anomalies. The control part (Kamailio 6.0.x) was also rebooted, this did not had any effect regarding this issue. The issue was observed multiple times as well, after removing the rtpengine and adding it back.

Steps to reproduce the problem

So far we only observed it in production on a specific customer system. The control side (Kamailio) was not changed. The same configuration is running on multiple older .13 rtpengine systems without any issues.

No special rtpengine flags were used, also the rtpengine configuration by itself its quite standard. Notable probably that websocket is used as control protocol. The rtpengine instances are managed using the Kamailio RPC command.

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.