No audio after Kernelizing Media

Aperta
  • Qualcosa non va?
#1,970 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 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
c, linux
Ambito
networking

Direzione di ricerca

The entry point is the kernelization path that emits the 'Kernelizing media stream' lines in the log, plus the netfilter target the nft ruleset reports as 'XT target RTPENGINE not found'. Reproduce on AlmaLinux 9 with the same iptables-nft/nftables ruleset and confirm whether the kernel module receives packets at all, since the userland log shows both streams confirmed before kernelization and then silence. Done means RTP keeps flowing after the switch to kernel mode instead of stopping.

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

Descrizione

bug
rtpengine version the issue has been seen with

13.5.0.0+0~mr13.5.0.0-1.el9

Used distribution and its version

AlmaLinux release 9.6

Linux kernel version used

5.14.0-570.24.1.el9_6.x86_64

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

x86_64

Expected behaviour you didn't see

audio flow after Kernelizing media

Unexpected behaviour you saw

After kernelizing media, audio stop flow.

Steps to reproduce the problem

Fresh install of Almalinux 9, no iptables.

nft list ruleset

Warning: table ip filter is managed by iptables-nft, do not touch!

table ip filter {
chain INPUT {
type filter hook input priority filter; policy accept;
ip protocol udp counter packets 3191 bytes 743596 jump rtpengine
}

    chain rtpengine {
            # Warning: XT target RTPENGINE not found

xt target "RTPENGINE" counter packets 1889 bytes 483196
}
}

Warning: table ip6 filter is managed by iptables-nft, do not touch!

table ip6 filter {
chain INPUT {
type filter hook input priority filter; policy accept;
ip6 nexthdr udp counter packets 223 bytes 88076 jump rtpengine
}

    chain rtpengine {
            # Warning: XT target RTPENGINE not found

xt target "RTPENGINE" counter packets 223 bytes 88076
}
}

/etc/rtpengine/rtpengine.conf
[rtpengine]
table = 0
interface = priv/10.6.96.3;pub/45.YYY.YYY.YYY
listen-ng = 10.6.96.3:2223
listen-tcp = 10.6.96.3:2230
listen-udp = 10.6.96.3:12222
log-level = 7

Additional program output to the terminal or logs illustrating the issue
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Handling packet: remote 200.XXX.XXX.XXX:4024 (expected: 200.XXX.XXX.XXX:4024) -> local 45.YYY.YYY.YYY:15520 (RTP seq 32465 TS 24000 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Forward to sink endpoint: local 10.6.96.3:14048 -> remote 10.6.96.3:17166 (RTP seq 32465 TS 24000 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Handling packet: remote 10.6.96.3:17166 (expected: 10.6.96.3:17166) -> local 10.6.96.3:14048 (RTP seq 31262 TS 24000 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Forward to sink endpoint: local 45.YYY.YYY.YYY:15520 -> remote 200.XXX.XXX.XXX:4024 (RTP seq 31262 TS 24000 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Handling packet: remote 200.XXX.XXX.XXX:4024 (expected: 200.XXX.XXX.XXX:4024) -> local 45.YYY.YYY.YYY:15520 (RTP seq 32466 TS 24160 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Forward to sink endpoint: local 10.6.96.3:14048 -> remote 10.6.96.3:17166 (RTP seq 32466 TS 24160 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Handling packet: remote 10.6.96.3:17166 (expected: 10.6.96.3:17166) -> local 10.6.96.3:14048 (RTP seq 31263 TS 24160 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Forward to sink endpoint: local 45.YYY.YYY.YYY:15520 -> remote 200.XXX.XXX.XXX:4024 (RTP seq 31263 TS 24160 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Handling packet: remote 200.XXX.XXX.XXX:4024 (expected: 200.XXX.XXX.XXX:4024) -> local 45.YYY.YYY.YYY:15520 (RTP seq 32467 TS 24320 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Forward to sink endpoint: local 10.6.96.3:14048 -> remote 10.6.96.3:17166 (RTP seq 32467 TS 24320 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Handling packet: remote 10.6.96.3:17166 (expected: 10.6.96.3:17166) -> local 10.6.96.3:14048 (RTP seq 31264 TS 24320 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Forward to sink endpoint: local 45.YYY.YYY.YYY:15520 -> remote 200.XXX.XXX.XXX:4024 (RTP seq 31264 TS 24320 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Confirmed peer address as 200.XXX.XXX.XXX:4024
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Handling packet: remote 200.XXX.XXX.XXX:4024 (expected: 200.XXX.XXX.XXX:4024) -> local 45.YYY.YYY.YYY:15520 (RTP seq 32468 TS 24480 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Forward to sink endpoint: local 10.6.96.3:14048 -> remote 10.6.96.3:17166 (RTP seq 32468 TS 24480 SSRC 7d7c63bb)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Kernelizing media stream: remote 200.XXX.XXX.XXX:4024 -> local 45.YYY.YYY.YYY:15520
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Kernelizing media stream: 200.XXX.XXX.XXX:4024 -> 45.YYY.YYY.YYY:15520 | 10.6.96.3:14048 -> 10.6.96.3:17166
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Kernelizing media stream: 200.XXX.XXX.XXX:4024 -> 45.YYY.YYY.YYY:15520 | 10.6.96.3:14049 -> 10.6.96.3:17167
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Confirmed peer address as 10.6.96.3:17166
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Handling packet: remote 10.6.96.3:17166 (expected: 10.6.96.3:17166) -> local 10.6.96.3:14048 (RTP seq 31265 TS 24480 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/c144a81ac36040b98f5fc1bae9f641e2/1 port 15520]: [core] Forward to sink endpoint: local 45.YYY.YYY.YYY:15520 -> remote 200.XXX.XXX.XXX:4024 (RTP seq 31265 TS 24480 SSRC 145861ef)
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Kernelizing media stream: remote 10.6.96.3:17166 -> local 10.6.96.3:14048
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Kernelizing media stream: 10.6.96.3:17166 -> 10.6.96.3:14048 | 45.YYY.YYY.YYY:15520 -> 200.XXX.XXX.XXX:4024
Jul 04 17:11:08 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14048]: [core] Kernelizing media stream: 10.6.96.3:17166 -> 10.6.96.3:14048 | 45.YYY.YYY.YYY:15521 -> 200.XXX.XXX.XXX:4025
Jul 04 17:11:10 rtpengine13 rtpengine[134113]: INFO: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14049]: [core] Confirmed peer address as 10.6.96.3:17167
Jul 04 17:11:10 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14049]: [core] Handling packet: remote 10.6.96.3:17167 (expected: 10.6.96.3:17167) -> local 10.6.96.3:14049
Jul 04 17:11:10 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14049]: [rtcp] Calling handler for RTCP packet type 200
Jul 04 17:11:10 rtpengine13 rtpengine[134113]: DEBUG: [664ab44ee94e4e558e3c043d6b1747a1/5c9e2fe1-1494-4079-ab3f-0b6eabf775d9/1 port 14049]: [core] SR from 145861ef: RTP TS 40000 PC 242 OC 38720 NTP TS 3960637870/756292096=3960637870.176088
Anything else?

No response

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.