Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No audio after Kernelizing Media

Open
  • Is something wrong?
#1,970 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, linux
Domain
networking

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
Perl
Stars
992
Forks
459
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sipwise/rtpengine

All issues in sipwise/rtpengine

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.