<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font-family:Calibri,sans-serif">
<div>Hi Daniel, </div>
<div>I have tested using "rtpproxy_manage()" before rewritehost(ip public-MCU) and then, in the 200 OK response, using rtpproxy _manage(public ip rtpproxy) and it works.</div>
<div>Endpoint sends ftp traffic to MCU through rtpproxy and MCU sends ftp traffic to endpoint through rtpproxy.</div>
<div>I am going to update kamailio version too.</div>
<div><br>
</div>
<div>Many 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 href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>" <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>martes 9 de octubre de 2012 14:30<br>
<span style="font-weight:bold">To: </span>Marina Serrano Montes <<a href="mailto:marinas@tid.es">marinas@tid.es</a>><br>
<span style="font-weight:bold">Cc: </span>"SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List" <<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</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>
the signaling shows traffic going from public IP (caller) to private IP (kamailio) then back to public IP (callee). So it is a bit of complex routing if you keep it like this. The best is to get it done working with kamailio, rtpproxy and mcu on their public
ip, because they have such already. Then you can think of moving to use some private networks.<br>
<br>
Your fourth bullet below is not clear for me: the clients should have visibility to sip server in order to register and call, but you say not, maybe just a typo.<br>
<br>
Also, I would recommend to start with latest kamailio 3.3.1 version, 3.2.0 is very old, if you really want that release series, the use latest 3.2.x, not 3.2.0.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 10/9/12 1:36 PM, MARINA SERRANO MONTES wrote:<br>
</div>
<blockquote type="cite">
<div>Hi Daniel:</div>
<div><br>
</div>
<div>The network is:</div>
<ul>
<li>MCU is running in a private network with IP's (10.95.94.142 and 10.95.94.143) and public IP's 195.235.93.166 and 195.235.93.161.
</li><li>SIP server and rtpproxy are running in another network: 10.95.94.92, with public IP: 195.235.93.8.
</li><li>SIP server, rtpproxy and MCU has visibility between them. </li><li>Clients have not visibility with sip server and MCU, and they try register, invite,….using the public IP: 195.235.93.8 (public IP of rtpproxy)
</li><li>When I have not use MCU, only 2 participants, the video and audio is routing OK.
</li><li>I can verify using web browser conference in MCU that it is sending RTP traffic (out traffic).
</li></ul>
<div>Thank you very much.</div>
<div><br>
</div>
<div>Br,</div>
<div>Marina</div>
<div><br>
</div>
<div>I attach the sip messages of a call with/without MCU:</div>
</blockquote>
...<br>
<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>
</div>
</div>
</span><br>
<hr>
<font face="Arial" color="Gray" size="1"><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>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>