<div dir="ltr"><div>Hi again Richard et al,</div><div><br></div><div>In the meanwhile
I've figured out what was causing the issue. The problem was related to
the way I had my iptables rules defined. I had :</div><div><br></div><div>-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT</div><div><br></div><div>and only after that</div><span class="gmail-im"><div><span><br>-A INPUT -p udp -m udp --dport 16384:32768 -j RTPENGINE --id 0<br>-A INPUT -p udp -m udp --dport 49152:65535 -j RTPENGINE --id 0</span></div><div><span><br></span></div></span><div><span>I basically changed that to:</span></div><div><span><br></span></div><div><span>...<br></span></div><div><span>-A INPUT -m state --state RELATED,ESTABLISHED -m udp -p udp --dport 16384:32768 -j RTPENGINE --id 0<br>-A INPUT -m state --state RELATED,ESTABLISHED -m udp -p udp --dport 49152:65535 -j RTPENGINE --id 0<br>-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT</span></div><div><span>...</span></div><div><span>-A INPUT -p udp -m udp --dport 16384:32768 -j ACCEPT<br>-A INPUT -p udp -m udp --dport 49152:65535 -j ACCEPT</span></div><div><span><br></span></div><div><span>and now everything works as expected.<br></span></div><div><span><br></span></div><div><span>Thanks for all the support anyway.</span></div><div><span><br></span></div><div><span>Cheers,</span></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">--<br>Nuno Miguel Reis<br>Departamento de Engenharia Informática <br>Faculdade de
Ciências e Tecnologia <br>Universidade de Coimbra<br></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 16, 2020 at 10:10 PM Richard Fuchs <<a href="mailto:rfuchs@sipwise.com">rfuchs@sipwise.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 16/01/2020 12.29, Nuno Miguel Reis
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi again.</div>
<div><br>
</div>
<div>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.</div>
<div>Do you have any hints on why this could be happening with
the kernel module?</div>
<div><br>
</div>
<div>I'm running rtpengine like this:</div>
<div><br>
</div>
<div>usersapece: $ rtpengine -f -L 7 --interface=100.100.100.100
--listen-ng=<a href="http://127.0.0.1:2223" target="_blank">127.0.0.1:2223</a> --tos=184
--sip-source</div>
<div><br>
</div>
<div>kernel: $ rtpengine -f -L 7 --table=0
--interface=100.100.100.100 --listen-ng=<a href="http://127.0.0.1:2223" target="_blank">127.0.0.1:2223</a>
--tos=184 --no-fallback --sip-source <br>
</div>
<div><br>
</div>
</div>
</blockquote>
<p>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?</p>
<p>Cheers<br>
</p>
</div>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div>