[SR-Users] Re: Rtpengine: no audio after kernelization.

Appreciate the help Richard! Media is traversing the team0 link <> one of the two carrier vlan’s as per: team0: connected to Team connection 1 "team0" team, 50:9A:4C:XX:XX:XX, sw, mtu 1500 ip4 default inet4 203.x.x.x/27 route4 203.x.x.x/27 metric 350 route4 default via 203.x.x.x metric 350 carrierX180: connected to carrierX180 "carrierX180" vlan, 50:9A:4C:XX:XX:XX, sw, mtu 1500 inet4 10.x.x.x/28 route4 10.x.x.x/28 metric 401 route4 202.x.x.x/27 via 10.x.x.x metric 401 route4 10.x.x.x/30 via 10.x.x.x metric 401 inet6 fe80::xxx/64 route6 fe80::/64 metric 1024 carrierY178: connected to carrierY178 "carrierY178" vlan, 50:9A:4C:XX:XX:XX, sw, mtu 1500 inet4 10.x.x.x/28 route4 10.x.x.x/28 metric 400 //CUT// inet6 fe80::xxx/64 route6 fe80::/64 metric 1024 Cheers, Tim From: Richard Fuchs &lt;rfuchs(a)sipwise.com&gt; Sent: Friday, March 24, 2023 8:51 PM To: sr-users(a)lists.kamailio.org Subject: [SR-Users] Re: Rtpengine: no audio after kernelization. On 22/03/2023 08.19, [EXT] Tim Bowyer wrote: Evening! I ditched firewalld and swapped to configuring iptables manually… I’ve also made some basic calls with media going in/out of the same interface and I’m still seeing the audio stop completely or become one-way once kernelized. On the two different interfaces, I get no-way audio once kernelized. Weird! Could this be related to the kernel module being unsigned (running CentOS 8 Stream)? kernel: xt_RTPENGINE: loading out-of-tree module taints kernel. kernel: xt_RTPENGINE: module verification failed: signature and/or required key missing - tainting kernel kernel: Registering xt_RTPENGINE module - version git-HEAD-5bf2c50a systemd-modules-load[781]: Inserted module 'xt_RTPENGINE' No, that is expected and perfectly fine. Have been pulling my hair out! [root@blahblah zgadmin]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination rtpengine udp -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere //cut// Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain rtpengine (1 references) target prot opt source destination RTPENGINE udp -- anywhere anywhere RTPENGINE id:0 That looks fine. How about the actual network setup? Any network namespaces, policy routing, or other unusual setup in place? Cheers