Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#2,161 13 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@darwvin-dev ci sta già lavorando.

Dal 13/10/2026.

  • #2207 di @darwvin-dev — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
perl
Ambito
audio-video-rtc, networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Perl
Stelle
992
Fork
459
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di sipwise/rtpengine

Tutte le issue di sipwise/rtpengine

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.