<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>Hi, Ignacio!<br>
<br>
So you are trying to use RTPProxy in bridge mode (between a
private and a public network). This means that for INVITE you
should have a public IP, and for 200OK a private IP (or the
other way around, depending on your scenario). You have three
possible solutions to achieve this:<br>
<br>
1. For INVITE, call rtpproxy_offer("flags", "PUBLIC_IP") and for
200OK, rtpproxy_answer("flags", "PRIVATE_IP") (or reverse the
IPs in case of a different scenario). I am not sure this works,
as RTPProxy will have no idea about where exactly is your
UAC/UAS - therefore it might use wrong sockets to send data (for
example, it might use a PRIVATE_IP socket to send RTP to a
public ip).<br>
2. Enable the autobridge mode, by setting the
'rtpproxy_autobrige' parameter [1]. I've never used this, so I
can't confirm whether it works properly or not.<br>
3. Call the rtpproxy_offer/answer functions with the 'E' or 'I'
flags[2]. This is the most reliable method I've used I can
confirm it works.<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://www.opensips.org/html/docs/modules/1.8.x/rtpproxy#id250154">http://www.opensips.org/html/docs/modules/1.8.x/rtpproxy#id250154</a><br>
[2]
<a class="moz-txt-link-freetext" href="http://www.opensips.org/html/docs/modules/1.8.x/rtpproxy#id292744">http://www.opensips.org/html/docs/modules/1.8.x/rtpproxy#id292744</a><br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Razvan Crainea
OpenSIPS Core Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
</pre>
On 11/14/2012 05:14 PM, Ignacio Gonzalez wrote:<br>
</div>
<blockquote
cite="mid:CAL5dx5SFyx7U_pE=YvEK1wmpNFDm7ODXnrQfYM_eyDUxeGWOsQ@mail.gmail.com"
type="cite">Ok i will check the flags, I set the domain parameter
of rtpproxy_offer to PUBLIC_IP, i create the rules in my router to
bind the ports 35000 to 35200 of the public_ip to the ports 35000
to 35200 in the PRIVATE_IP of rtpproxy 192.168.1.220, I'm not sure
if this is correct.<br>
<br>
If i don't put the domain parameter in the rtpproxy_offer the SDP
message contains the private ip of the RTPPROXY (192.168.1.220)
and my clients are outside this nat.<br>
<br>
Thanks<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2012/11/14 Răzvan Crainea <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><tt>Hi, Ignacio!<br>
<br>
The ports you have listed in the SDP snippet belong to
a single rtp stream - Callee-RTPProxy-Caller. You
should also check the ports in the 200OK.<br>
The "nortpproxy_str" parameter you are specifying is
used by RTPProxy to determine if the SDP has to be
changed, or somebody else already changed in the path.<br>
I noticed that you call rtpproxy_offer() function with
two parameters:<br>
1. "ro" - if the SDP has a private IP, you shouldn't
use the "r" flag. This flag is used to specify that
RTPProxy should accept packages only from that IP,
whereas in your case he will receive the packets from
a public IP.<br>
2. "domain" - you shouldn't use this parameter unless
you really know what you are doing. This overwrites
the domain specified by RTPProxy, which is not always
such a good idea.<br>
<br>
I hope these remarks will help you fix your problem.<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Razvan Crainea
OpenSIPS Core Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a>
</pre>
<div>
<div class="h5"> On 11/14/2012 01:11 AM, Ignacio
Gonzalez wrote:<br>
</div>
</div>
</div>
<div>
<div class="h5">
<blockquote type="cite">I change the attribute using
adding this to the opensips configuration file<br>
<br>
<pre>modparam("rtpproxy", "nortpproxy_str", "a=sdpmangled:yes\r\n")</pre>
<br>
<br>
a=nortpproxy:yes<br>
<br>
<br>
But there is no audio, i check the traffic using
wireshark and i see that a lot of packets are sent
to another port not the one that i send in the first
message, example:<br>
<br>
First SDP<br>
<br>
v=0<br>
o=- 465641 0 IN IP4 10.168.123.201<br>
s=-<br>
c=IN IP4 10.168.123.201<br>
t=0 0<br>
m=audio 11670 RTP/AVP 0<br>
a=rtpmap:0 PCMU/8000<br>
a=sendrecv<br>
<br>
<br>
<br>
Changed by opensips and rtpproxy to look like<br>
<br>
<br>
v=0<br>
o=- 465641 0 IN IP4 IP_PUBLIC<br>
s=-<br>
c=IN IP4 IP_PUBLIC<br>
t=0 0<br>
m=audio 35000 RTP/AVP 0<br>
a=rtpmap:0 PCMU/8000<br>
a=sendrecv<br>
<br>
<br>
And packets are being recived on the udp:<a
moz-do-not-send="true"
href="http://10.168.123.201:45708" target="_blank">10.168.123.201:45708</a><br>
<br>
<br>
Thanks for your help<br>
<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2012/11/13 Ignacio
Gonzalez <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:mylaneza@gmail.com"
target="_blank">mylaneza@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"> Hello, I change the
command line to run rtpproxy and change my
configuration file:<br>
<br>
./rtpproxy -l <a moz-do-not-send="true"
href="http://timewarnercable.dyndns.org"
target="_blank">timewarnercable.dyndns.org</a>
-s udp:<a moz-do-not-send="true"
href="http://192.168.1.220:12333"
target="_blank">192.168.1.220:12333</a> -n
tcp:<a moz-do-not-send="true"
href="http://192.168.1.220:12333"
target="_blank">192.168.1.220:12333</a> -u
syrium -m 35000 -M 35200<br>
<br>
rtpproxy_offer("ro" , "<a
moz-do-not-send="true"
href="http://timewarnercable.dyndns.org"
target="_blank">timewarnercable.dyndns.org</a>");<br>
<br>
And now the SDP message looks like this:<br>
<br>
v=0<br>
o=- 0 0 IN IP4 PUBLICIP<br>
s=-<br>
c=IN IP4 PUBLICIP<br>
t=0 0<br>
m=audio 35134 RTP/AVP 0<br>
a=rtpmap:0 PCMU/8000<br>
a=sendrecv<br>
a=nortpproxy:yes<br>
<br>
But there is no audio, and I don't know what
is the meaning of the a=nortpproxy:yes<br>
<br>
<br>
Thanks for your help.
<div>
<div><br>
<br>
<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2012/11/12
Ignacio Gonzalez <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:mylaneza@gmail.com"
target="_blank">mylaneza@gmail.com</a>></span><br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex"> I use the
same port but tcp because in the
post the answer is that. I Attach
the debug file
<div>
<div><br>
<br>
<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2012/11/12
spady <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:spady77@gmail.com"
target="_blank">spady77@gmail.com</a>></span><br>
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">Please,
post entire opensips log (
set debug to 6 ).<br>
<br>
Why are you using same
port for sock and
notify_sock ??? Have you
tried with<br>
different ports?<br>
<br>
Bye<br>
<br>
<br>
<br>
--<br>
View this message in
context: <a
moz-do-not-send="true"
href="http://opensips-open-sip-server.1449251.n2.nabble.com/RTPProxy-Problem-tp7582930p7582974.html"
target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/RTPProxy-Problem-tp7582930p7582974.html</a><br>
<div>
<div>Sent from the
OpenSIPS - Users
mailing list archive
at Nabble.com.<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a
moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>