[RTPproxy Users] RTPProxy sending RTP packets before receiving initial packet.

[mayamatakeshi]

On Thu, Oct 22, 2009 at 12:13 AM, mayamatakeshi <mayamatakeshi at gmail.com>wrote:

> Hello,
> we are running RTPPRoxy 1.1 with Kamailio.
> 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
> 192.168.1.2:60000).
> 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.
> However, why would be rtpproxy doing this? It doesn't seem to be according
> to the HOWITWORKS explanation in the man page.
> Does rtpproxy receive this SDP info from SER?
> 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.
> And I don't see these private ports sending any packets to rtpproxy ports
> to make it behave as such.
>

Trying to solve problems with my kamailio installation I think I got the
reason rtprproxy does this:
this is necessary to avoid deadlock in case there are other instances of
rtpproxy handling the call.
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,
takeshi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rtpproxy.org/pipermail/users/attachments/20091101/c498fe64/attachment.html