Repeated peer confirmation and kernelisation messages
I maintainer di solito rispondono entro 3 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 15/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- linux, perl
- Ambito
- audio-video-rtc, networking
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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!
- Lingua principale
- Perl
- Stelle
- 992
- Fork
- 459
- Metriche di merge delle PR
- 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di sipwise/rtpengine
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 3 giorni
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
I maintainer di solito rispondono entro 3 giorni
-
SRTP decryption failed after client seq wrap on transcoded WebRTC call (mr26.2.1.2)Forse già presa @armanbahlakeh-ct l’ha presa 1 giorno fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 43/100
sipwise/rtpengine#2220 · 3 commenti ·
I maintainer di solito rispondono entro 3 giorni
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
sipwise/rtpengine#2219 · 3 commenti ·
I maintainer di solito rispondono entro 3 giorni
-
HTTP/WS worker threads spin forever in `__websocket_write_done()` (`sched_yield` loop) — 100% CPU with `--listen-http`Forse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 15/100
sipwise/rtpengine#2197 · 1 commento ·
I maintainer di solito rispondono entro 3 giorni
Tutte le issue di sipwise/rtpengine
Issue simili
-
observablt-ci
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
elastic/golang-crossbuild#840 ·
I maintainer di solito rispondono entro 1 giorno
-
Sync playback crashes repeatedly in a sync group (v9.1.1)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
LMS-Community/slimserver#1701 · 6 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
RotherOSS/otobo#6286 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
fix(api): API v3 Product Read ignores request language (lc) for sample products and image URLsForse già presa @muntasir-396 l’ha presa 4 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
openfoodfacts/openfoodfacts-server#15042 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno