Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Repeated peer confirmation and kernelisation messages

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

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start by grepping the rtpengine daemon source for the two log strings quoted in the payload, 'Confirmed peer address' and 'Kernelizing media stream', to find the confirm and kernelisation paths in the media-stream core. Reproduce with a single offer/answer and verbose logging (the reporter confirmed no re-invites and no duplicate iptables -j RTPENGINE rules), then trace why the same peer/port pair re-confirms hundreds of times. Done when one media stream kernelises once and the repeated INFO lines stop.

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

Descripción

In mr11.2.1.5 on kernel 4.18.0-425.10.1.el8_7.x86_64, on some calls, we are seeing hundreds of messages like this from rtpengine logs, essentially instantaneously:

Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Kernelizing media stream: y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as x.x.x.x:28202
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Kernelizing media stream: y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as x.x.x.x:28202
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Kernelizing media stream: y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as x.x.x.x:28202
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Kernelizing media stream: y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as x.x.x.x:28202
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Kernelizing media stream: y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as x.x.x.x:28202
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Kernelizing media stream: y.y.y.y:39412
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 43562]: [core] Confirmed peer address as x.x.x.x:28202
Mar 21 20:18:18 rtp-relay rtpengine[1237]: INFO: [SDgmmb201-ed3883e83407be71a657612939715d49-v300g00 port 54928]: [core] Confirmed peer address as z.z.z.z:52108

On this call, it was 400+.

I confirmed via wire protocol trace that there was only a single offer, answer and delete command, so no re-invites. There's nothing unusual about the SDP, it's as banal as can be.

Offer:

v=0
o=Sonus_UAC 20105 5717 IN IP4 y.y.y.y
s=SIP Media Capabilities
c=IN IP4 y.y.y.y
t=0 0
m=audio 39412 RTP/AVP 0 8 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=maxptime:20

Answer:

v=0
o=xxx 1679377785 1679377786 IN IP4 z.z.z.z
s=xxx
c=IN IP4 10.100.153.236
t=0 0
m=audio 52108 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=rtcp:52109 IN IP4 z.z.z.z

I cannot find any correlation between any SDP attributes and this phenomenon occurring.

I also checked to make sure there were no duplicate -j RTPENGINE rules in the INPUT chain; there are not.

Would appreciate any insight into the cause of this!

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.