<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div>Hi Saul,</div><div><br></div><div>I mean by 'the rest' that I don't have to write code in the opensips.cfg to have ICE ( e.g. see which kind of NAT it is etc.), just to set the parameters for the mediaproxy as written below.</div><div>I think I understood from your answer what I have to do.</div><div><br></div><div>In the same time I'm thinking how to test ICE, do you think a proper way is to make two tests:</div><div>1. Two clients behind a router that does not have symmetric nat (e.g. conic nat) and server with public IP, in this case the media stream should follow the STUN way (not via relay).</div><div>2. Two clients behind a router with symmetric nat, in this case media stream should go via relay (mediaproxy).</div><div>Obviously we should have clients with ICE support, we use Bria 3.2, 2.5.4 or
Blink.</div><div><br></div><div>And to follow the media streams I have to install CDRTool and FreeRadius server.</div><div>Do you think this scenario is suitable to prove the ICE capability of the server?</div><div><br></div><div>Thanks,</div><div>Liviu</div><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Saúl Ibarra Corretgé <saul@ag-projects.com><br><b><span style="font-weight: bold;">To:</span></b> OpenSIPS users mailling list <users@lists.opensips.org><br><b><span style="font-weight: bold;">Sent:</span></b> Thu, June 23, 2011 10:20:47 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [OpenSIPS-Users] ICE How-To<br></font><br>
Hi,<br><br>On Jun 22, 2011, at 5:35 PM, Barsan Liviu wrote:<br><br>> Hello,<br>> <br>> We have built until now an OpenSIPs-MediaProxy server which knows far end NAT traversal, Messaging and Presence (basic), it works reliable.<br><span>> Now we would like to add ICE capability to this solution and we are not sure on How-To. According to <a target="_blank" href="http://mediaproxy-ng.org/wiki/ICE">http://mediaproxy-ng.org/wiki/ICE</a>, we understood that is enough to set the mediaproxy modules parameters as written in the site, something like:</span><br>> <br>> ice_candidate="high-priority"<br>> ice_candidate_avp="$avp(s:ice_priority)"<br>> <br><br>The AVP is meant to be used for fine grained control, the ice_candidate module parameter should be enough in most cases.<br><br>> It is enough to have these settings?<br>> The rest will be done by MediaProxy and OpenSIPs automatically?<br>> <br><br>What do you mean by 'the rest'
? If you client is offering ICE and OpenSIPS/MediaProxy are mangling the signaling, that setting will make MediaProxy modify the SDP in such a way that ICE is not broken.<br><br>If you want to really test ICE you'll want to set the ice_candidate parameter to low-priority, otherwise chances are MediaPRoxy will always be used.<br><br><br>Regards,<br><br>--<br>Saúl Ibarra Corretgé<br>AG Projects<br><br><br><br><br>_______________________________________________<br>Users mailing list<br><a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><span><a target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></span><br></div></div><div style="position:fixed"></div>
</div></body></html>