26 Feb
2010
26 Feb
'10
8:07 p.m.
El Viernes, 26 de Febrero de 2010, Daniel-Constantin Mierla escribió:
On 02/26/2010 03:09 PM, Iñaki Baz Castillo wrote:
Interesting, I'll try it and will comment the result.
Thanks.
--
Iñaki Baz Castillo <ibc(a)aliax.net>
El Viernes, 26 de Febrero de 2010,
Daniel-Constantin Mierla escribió:
there is a deadlock when chaining two rtpproxy. In learning mode
rtpproxy waits for the other side to send first packet to know the ip
and port. iirc it is r flag to avoid this. Do you re-engage rtpproxy for re-INVITEs?
Yes, the client is behind NAT so I must use RtpProxy for initial INVITE.
Then, if I don't re-engage rtpproxy for re-INVITE RtpProxy would receive
RTP in already working ports but from a different source, so RtpProxy
would reject/ignore such RTP traffic.
Also, have you played with
force rtp proxy flags to trust public addresses?
But that wouldn't solve the problem, am I wrong?