[OpenSIPS-Users] NAT - Unable to solve RTP Problem
Jens Sauer
sauer.jens at yahoo.de
Sun Jun 23 19:21:31 CEST 2013
Just posting my solution - maybe helps someone here ...
Host:
rtpproxy -l <public IP> -m 35510 -M 37790 -s udp:10.1.1.1:12500 -n tcp:10.1.1.200:12500 -d INFO:LOG_LOCAL1 -i -u rtpp:rtpp
Client (Guest)
opensips.cfg <snippet>
# Modul
...
loadmodule "rtpproxy.so"
modparam("rtpproxy", "rtpproxy_sock", "udp:10.1.1.1:12500") # CUSTOMIZE ME
modparam("rtpproxy", "rtpp_notify_socket", "tcp:10.1.1.200:12500")
...
# routing
...
rtpproxy_offer("nro");
rtpproxy_answer("nro");
...
----
Runs good except of UA Client (WLan - Android CSipSimple/Keyyo-Voip) <--> Server
Here i have after random time connection loss (rtp) ... maybe WLan, but try to figure it out
Greetings
Jens
________________________________
Von: Ovidiu Sas <osas at voipembedded.com>
An: OpenSIPS users mailling list <users at lists.opensips.org>
CC: Jens Sauer <sauer.jens at yahoo.de>
Gesendet: 18:58 Sonntag, 23.Juni 2013
Betreff: Re: [OpenSIPS-Users] NAT - Unable to solve RTP Problem
<snip>
> Rtpproxy does not work behind a firewall without a patch.
</snip>
Rtpproxy works just fine out of the box behind NAT. There's no need
to patch rtpproxy to achieve this functionality.
There was a patch posted a while ago to achieve this functionality,
but the patch is not necessary:
http://opensips-open-sip-server.1449251.n2.nabble.com/Rtpproxy-behind-the-NAT-td5008041.html
All one needs to do is force the IP to be used in SDP via the second
parameter of rtpproxy_offer/answer function.
Regards,
Ovidiu Sas
--
VoIP Embedded, Inc.
http://www.voipembedded.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130623/0b8a178b/attachment-0001.htm>
More information about the Users
mailing list