<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
you should not set the second parameter of rtpproxy_manage(...), let
it be the one returned by rtpproxy.<br>
<br>
And yes, all the occurrences of IP addresses in c= lines will be
replaced by the rtpproxy ip, but providing different ports for each
media stream.<br>
<br>
Practically the rtp streams are going from end device to rtpproxy
and then based on port will be delivered to different IPs of the
MCU. Also, the MCU will send from different IPs to RTPProxy on
different ports and from there to the end device.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 10/8/12 6:05 PM, MARINA SERRANO
MONTES wrote:<br>
</div>
<blockquote
cite="mid:8654B3E2294AB0439D60F0A7245577C8041CD6@EX10-MB2-MAD.hi.inet"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>Hi Daniel,</div>
<div><br>
</div>
<div>I have tested using "rtpproxy_manage("", public IP), but in
this case, it replaces all the c= lines with this public IP,
included c=lines in media descriptions and then, the rtp traffic
is not routing to the right IP in MCU. </div>
<div><br>
</div>
<div>Have I to set up any value/param….to route rtp traffic
through rtpproxy in sip server and then it will dispatch RTP
packets to MCU?</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div>Br,</div>
<div>Marina</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; border-bottom:medium none;
border-left:medium none; padding-bottom:0in; padding-left:0in;
padding-right:0in; border-top:#b5c4df 1pt solid;
border-right:medium none; padding-top:3pt">
<span style="font-weight:bold">From: </span>Daniel-Constantin
Mierla <<a moz-do-not-send="true"
href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a
moz-do-not-send="true" href="mailto:miconda@gmail.com">miconda@gmail.com</a>"
<<a moz-do-not-send="true" href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>lunes 8 de
octubre de 2012 16:04<br>
<span style="font-weight:bold">To: </span>"SIP Router -
Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List" <<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>><br>
<span style="font-weight:bold">Cc: </span>Vicente Hernando
<<a moz-do-not-send="true"
href="mailto:vhernando@systemonenoc.com">vhernando@systemonenoc.com</a>>,
Marina Serrano Montes <<a moz-do-not-send="true"
href="mailto:marinas@tid.es">marinas@tid.es</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [SR-Users]
how to use fix_nated_sdp("2") with multiple media types<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF">Hello,<br>
<br>
I understood that Marina is looking for the option of being
able to use different IP addresses for updating various c=
lines in SDP.
<br>
<br>
fix_nated_sdp(...) can work only with one IP address given
as second parameter (or taken for source address of the
packet).<br>
<br>
Perhaps fix_nated_sdp(...) can be easily extended to support
a list of ip addresses in the second parameter. For now the
solution is to use rtpproxy to rewrite all the IP addresses
in c= lines with the IP address of the rtpproxy. RTPProxy
will then dispatch RTP to the right IP address assigned for
each media stream.<br>
<br>
Regarding the patch sent by Vicente, I just replied on
sr-dev mailing list.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 10/8/12 3:25 PM, Vicente
Hernando wrote:<br>
</div>
<blockquote type="cite">
<div class="moz-cite-prefix">Hello Marina,<br>
<br>
there is a bug in sdp parser about c IPs which are not
correctly reset for non existent c values in streams.<br>
<br>
I have still not uploaded it to master branch, sorry.<br>
<br>
May be it is related to your issue, in this link you
have the attached patch.<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html">http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html</a><br>
<br>
<br>
Kind regards,<br>
Vicente.<br>
<br>
On 10/08/2012 01:18 PM, MARINA SERRANO MONTES wrote:<br>
</div>
<blockquote type="cite">
<div><span class="Apple-style-span"
style="font-family:Consolas; font-size:14px">Hi,</span></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas"><br>
</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">I have a
doubt about how to use "fix_<span
style="font-style:italic">nated_</span>sdp("2")"
function when we have an scenario with multiple
media types (audio and video) and the param "c" in
sdp for each media type has a different IP.</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">We are
using a SCOPIA 400 MCU to multi-party in a call, and
it will set up different IP to send RTP depend on
media type.</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas"><br>
</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">I have
tested this function, but it rewrites always all the
"c" parameter with the same value.</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas"><br>
</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">Is there
any option to use the function or to rewrite "c"
value for each media type independently?</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas"><br>
</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">Many
thanks.</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas"><br>
</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">Br,</font></div>
<div style="font-size:14px"><font
class="Apple-style-span" face="Consolas">Marina</font></div>
<br>
<hr>
<font size="1" color="Gray" face="Arial"><br>
Este mensaje se dirige exclusivamente a su
destinatario. Puede consultar nuestra política de
envío y recepción de correo electrónico en el enlace
situado más abajo.<br>
This message is intended exclusively for its
addressee. We only send and receive email on the basis
of the terms set out at:<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
</font><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://asipto.com/u/kat">http://asipto.com/u/kat</a>
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://asipto.com/u/katu">http://asipto.com/u/katu</a></pre>
</div>
</div>
</span><br>
<hr>
<font size="1" color="Gray" face="Arial"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede
consultar nuestra política de envío y recepción de correo
electrónico en el enlace situado más abajo.<br>
This message is intended exclusively for its addressee. We only
send and receive email on the basis of the terms set out at:<br>
<a class="moz-txt-link-freetext" href="http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
</font>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - <a class="moz-txt-link-freetext" href="http://asipto.com/u/kat">http://asipto.com/u/kat</a>
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - <a class="moz-txt-link-freetext" href="http://asipto.com/u/katu">http://asipto.com/u/katu</a></pre>
</body>
</html>