<p dir="ltr">Hi, </p>
<p dir="ltr">I understand that OpenSIPS supports Mediaproxy which only relays RTP packets over UDP. My concern now is that due to Mediaproxy only supporting UDP, OpenSIPS might have this limitation built into it for all TURN servers, including Coturn. </p>
<p dir="ltr">In Linphone settings, there is a 'Stun server' option, and although it does not state 'TURN server' here, I found that in most clients which do support a TURN server, they still tend to refer to this as a 'Stun server' in their settings. </p>
<div class="gmail_quote">On 6 Feb 2016 8:56 am, "Adrian Georgescu" <<a href="mailto:ag@ag-projects.com">ag@ag-projects.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">OpenSIPS does not need to interact in anyway with a TURN server. A TURN server is used by the SIP client that has built-in TURN functionality. While they may run side by side, the only interaction of a sip proxy and TURN server is sharing the same database with credentials in order to authenticate the end-users.<div><br></div><div>What MediaProxy does, it simulates a TURN server candidate by inserting it into an offer generated by a SIP client that has ICE support. But it is not real TURN in the sense that it does not implement the TURN protocol (which does a lot of other things, not just the relaying packets over UDP part), and the client is unaware of this TURN candidate insertion. Practically, MediaProxy only relays RTP packets over UDP and is fouling both end-points into believing that during the ICE negotiation there is a relay server that can be used when end-to-end RTP does not work. One cannot get RTP over TCP running with this hybrid model.</div><div><br></div><div>If you want TCP, you need a real TURN client with a real TURN server. </div><div><br></div><div>Regards,</div><div>Adrian<br><div><br></div><div><div><br><div><blockquote type="cite"><div>On 06 Feb 2016, at 01:07, Nabeel <<a href="mailto:nabeelshikder@gmail.com" target="_blank">nabeelshikder@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 3 February 2016 at 23:42, sevpal <span dir="ltr"><<a href="mailto:sevpal@aol.com" target="_blank">sevpal@aol.com</a>></span> wrote:</div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="font-size:12pt;font-family:Calibri">
<div>Opensips interacts with the TURN in server MediaProxy only.</div></div></div></div></blockquote><div><br></div><div><br></div><div>That's not completely true, because the TURN server works with OpenSIPS when using UDP for calls. It just doesn't work - or only partially works - with TCP/TLS. I tested by changing configurations in the TURN server to use TCP relays/listeners only, but it still only works with UDP. This leads me to believe that it is a limitation in OpenSIPS that it only handles the TURN server properly when calls are using UDP, not TCP/TLS.</div><div><br></div><div>Coturn is probably the most comprehensive TURN server available today. Is there any chance that OpenSIPS will fully support this in the future?</div></div></div></div>
_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br></div></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div>