<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">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">127.0.0.1:2223</a> --tos=184 --no-fallback --sip-source <br></div><div><br></div><div><br></div><div>when using kernel module, I'm also setting this rules on chain INPUT under iptables:</div><div><br></div><div>-A INPUT -p udp -m udp --dport 5000:16383 -j RTPENGINE --id 0<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</div><div><br></div><div><br></div><div>Looking forward to hear from you guys.</div><div><br></div><div>Regards,<br></div><div><br></div><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></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 16, 2020 at 1:23 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 15/01/2020 13.39, Nuno Miguel Reis
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi guys.</div>
<div><br>
</div>
<div>I'm replacing a environment where I was using kamailio +
freeswitch by another where I'm adding rtpengine to the mix.</div>
<div>One of the issues I'm having now is when I have a SIP
Client behind NAT:</div>
<div><br>
</div>
<div>When I send the INVITE from the SIP Client, the SDP is
using the private LAN IP address + the advertised media port,
let's admit it's <a href="http://10.10.10.10:5000" target="_blank">10.10.10.10:5000</a> when the call
establishes with a public server running kamailio + rtpengine,
the actual RTP arrives from the home router public IP on a
natted port, let's admit it's <a href="http://100.100.100.100:65100" target="_blank">100.100.100.100:65100</a>,
event though, RTPENGINE assumes that RTP stream is coming from
<a href="http://100.100.100.100" target="_blank">100.100.100.100</a>:<span style="background-color:rgb(255,0,0)">5000.<span style="background-color:rgb(255,255,255)"> I'm using the
'--sip-source' with RTPENGINE to make it use the received
ip address instead of the private IP coming in the SDP but
I'm not finding anything to make RTPENGINE adapt an start
sending the RTP FLOW to the port where he starts receiving
the RTP flow from, discarding the SDP media port
information.</span></span></div>
</div>
</blockquote>
<p>Rtpengine does this automatically, unless the `asymmetric` flag
is used. You should see a log message about a `confirmed peer
address` as soon as the first RTP is received on a port.</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>