Hi again.

Thanks for all the help and suggestions. I realized the issue happens if using kernel forwarding only. If I change rtpengine to start at userspace without the kernel module enabled everything works fine as expected.

Do you have any hints on why this could be happening with the kernel module?

I'm running rtpengine like this:

usersapece: $ rtpengine -f -L 7 --interface=100.100.100.100 --listen-ng=127.0.0.1:2223 --tos=184 --sip-source

kernel: $ rtpengine -f -L 7 --table=0 --interface=100.100.100.100 --listen-ng=127.0.0.1:2223 --tos=184 --no-fallback --sip-source

The kernel module receives its instructions from the userspace daemon, so there's no reason there should be a difference. Can you post 1) logs and 2) the flags you use for your offers/answers?

Cheers