<br><div class="gmail_quote">On Thu, Oct 22, 2009 at 12:13 AM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com">mayamatakeshi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>we are running RTPPRoxy 1.1 with Kamailio.<br>After a call is set up, I can see rtpproxy sending 24 RTP packets to the private ip and port advertised in the SDP of the caller (like <a href="http://192.168.1.2:60000" target="_blank">192.168.1.2:60000</a>).<br>
This doesn't cause any problem to the call, as less then one second after this, rtpproxy starts to send the packets to the global IP addresses.<br>However, why would be rtpproxy doing this? It doesn't seem to be according to the HOWITWORKS explanation in the man page.<br>
Does rtpproxy receive this SDP info from SER?<br>The problem is that we have those addresses (192.168.1.*) in our network, so this causes several "icmp destination unreachable" packets to be sent back and this is flooding our network.<br>
And I don't see these private ports sending any packets to rtpproxy ports to make it behave as such.<br></blockquote></div><br>Trying to solve problems with my kamailio installation I think I got the reason rtprproxy does this:<br>
this is necessary to avoid deadlock in case there are other instances of rtpproxy handling the call. <br>rtpproxy cannot just sit and wait for the initial packets to come from both ends: if it does, RTP will not start on a chain of rtpproxies because no one will start the transmission.<br>
<br>br,<br>takeshi<br>