Hey! Thanks for the answer, actually I did so, I installed an rtpproxy in every sip server and solve those issues, now I have a "good enough" solution, both high available and fault tolerant (though added some extra traffic).
Thanks again! 2013/7/17 Samuel <[email protected]> > Hola Jose, > > I believe we can't solve it only at signaling level. Who controls the > source > IP address it's the client, and when behind NAT it's even worst since the > NAT box is the one who controls the source port. > I had some kind of issues and could solve it only via RTP relaying. > > You will need to use RTP/Media relay server. Some kind of NAT can be solved > only via relaying the RTP in intermediate server. RTPproxy it's a option. > At > signaling level we can't fix the port, since SDP do not contain the correct > port and it's different from the SIP used source port. > RTPproxy will receive the RTP and find what it's the source address of RTP > and then will send the the RTP to that port. > > You need to install RTPProxy. > > Hope this helps > > > > > -- > View this message in context: > http://opensips-open-sip-server.1449251.n2.nabble.com/NAT-issues-with-certain-routers-tp7587132p7587161.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
