No audio after Kernelizing Media

[neimaravila]

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

[neimaravila]

full.txt
Full Call

[rfuchs]

What does /proc/rtpengine/0/list show? Anything in dmesg?

[neimaravila]

cat /proc/rtpengine/0/list
local inet4 45.32.215.190:16958
stats: 98056 bytes, 548 packets, 0 errors
RTP payload type 0: 99736 bytes, 548 packets
RTP payload type 8: 0 bytes, 0 packets
last packet: 1751898489 SSRC in: 766a61a2 [seq 33305/0]
SRTP decryption parameters:
cipher: AES-CM-128
master key: 850bf6b2a8c6cf9f5576808387586f4b
master salt: d895ea53d5747ad199a2215687e9
session key: 374227b51c4ce45258d5e32a92d50d0b
session salt: 8fd25ad4d4e49d9e2de5240c56c2
session auth: eb9ba2372b5ca853418ce4ea66ea7b8786e0ca80
HMAC: HMAC-SHA1
auth tag length: 10
options: RTP PT-filter SSRC-tracking forward-RTCP
output #0
src inet4 10.6.96.3:13710
dst inet4 10.6.96.3:21024
stats: 94256 bytes, 548 packets, 0 errors
SSRC out: 0 [seq 33305+0/0]
local inet4 45.32.215.190:16959
stats: 454 bytes, 6 packets, 0 errors
last packet: 1751898488 SSRC in: 766a61a2 [seq 33305/0]
SRTP decryption parameters:
cipher: AES-CM-128
master key: 850bf6b2a8c6cf9f5576808387586f4b
master salt: d895ea53d5747ad199a2215687e9
session key: 374227b51c4ce45258d5e32a92d50d0b
session salt: 8fd25ad4d4e49d9e2de5240c56c2
session auth: eb9ba2372b5ca853418ce4ea66ea7b8786e0ca80
HMAC: HMAC-SHA1
auth tag length: 10
options: RTP RTCP SSRC-tracking forward-RTCP
output #0 (RTCP)
src inet4 10.6.96.3:13711
dst inet4 10.6.96.3:21025
stats: 360 bytes, 5 packets, 0 errors
SSRC out: 0 [seq 33305+0/0]
local inet4 10.6.96.3:13710
stats: 94256 bytes, 548 packets, 0 errors
RTP payload type 0: 94256 bytes, 548 packets
RTP payload type 8: 0 bytes, 0 packets
last packet: 1751898489 SSRC in: 5faf71f8 [seq 18926/0]
options: RTP PT-filter SSRC-tracking forward-RTCP
output #0
src inet4 45.32.215.190:16958
dst inet4 200.142.100.226:4002
stats: 95936 bytes, 548 packets, 0 errors
SSRC out: 0 [seq 18926+0/2]
SRTP encryption parameters:
cipher: AES-CM-128
master key: b1e25b168efb63be3cab0707fe0a7da4
master salt: b40ce27b51e69d5539bdbec5e87a
session key: d2b908fb9f88653de5cc01a40c86c8c8
session salt: 1271f48bec10c2d9f737165d134d
session auth: 517515c7b76170c77ca8ee314d542c439ec2911a
HMAC: HMAC-SHA1
auth tag length: 10
local inet4 10.6.96.3:13711
stats: 300 bytes, 3 packets, 0 errors
last packet: 1751898488 SSRC in: 5faf71f8 [seq 18926/0]
options: RTP RTCP SSRC-tracking forward-RTCP
output #0 (RTCP)
src inet4 45.32.215.190:16959
dst inet4 200.142.100.226:4003
stats: 214 bytes, 2 packets, 0 errors
SSRC out: 0 [seq 18926+0/2]
SRTP encryption parameters:
cipher: AES-CM-128
master key: b1e25b168efb63be3cab0707fe0a7da4
master salt: b40ce27b51e69d5539bdbec5e87a
session key: d2b908fb9f88653de5cc01a40c86c8c8
session salt: 1271f48bec10c2d9f737165d134d
session auth: 517515c7b76170c77ca8ee314d542c439ec2911a
HMAC: HMAC-SHA1
auth tag length: 10

dmesg
[246008.179533] Registering xt_RTPENGINE module - version

[rfuchs]

Is there just no RTP being forwarded? Or does the remote client discard/ignore/reject it?