Relay over TCP

Paul Davies

unread,

Oct 14, 2016, 2:54:43 AM10/14/16

to kurento

We have a coturn server that can listen on 80 and 443 with TLS and can relay over UDP and TCP but I never see an ICE offering from Chrome or Firefox that relays over TCP - always UDP.

Our Kurento server is on Google Cloud and when we are behind a simple NAT like a home cable network, we have no trouble connecting.

When we are in corp networks we fail to negotiate Trickle ICE. In the same corp network I have seen Google Hangout work and the Slack phone call work (both use WebRTC).

Anyone have any experience with relay over TCP?

Ivan Gracia

unread,

Oct 14, 2016, 7:00:09 AM10/14/16

to Kurento Public

It seems like your TURN server is not working in some environments. You have two options

Configure TLS in coturn. The coturn forums are the best place for this I guess.
Get an external TURN server.

Cheers,

Ivan Gracia

--
You received this message because you are subscribed to the Google Groups "kurento" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kurento+unsubscribe@googlegroups.com.
To post to this group, send email to kur...@googlegroups.com.
Visit this group at https://groups.google.com/group/kurento.
To view this discussion on the web visit https://groups.google.com/d/msgid/kurento/cb20e9ef-2e9e-42a4-b03d-3c35332fbbc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Paul Davies

unread,

Oct 14, 2016, 8:20:54 AM10/14/16

to kurento

Our turn server does do TLS, has a real and valid certificate, listens on 443 and it is external (it is my coturn server running on Google Cloud)

https://turn2-eu.uxpro.be/?transport=tcp

Do I need to do anything in the client to help get this to work?

Looking at the webrtc docs I see you can set options.iceTransportPolicy = 'relay'

Is this useful?

thanks

Paul

On Friday, October 14, 2016 at 1:00:09 PM UTC+2, igracia wrote:

It seems like your TURN server is not working in some environments. You have two options
Configure TLS in coturn. The coturn forums are the best place for this I guess.
Get an external TURN server.
Cheers,

Ivan Gracia

On Fri, Oct 14, 2016 at 8:54 AM, Paul Davies <paul....@uxpro.be> wrote:

We have a coturn server that can listen on 80 and 443 with TLS and can relay over UDP and TCP but I never see an ICE offering from Chrome or Firefox that relays over TCP - always UDP.

Our Kurento server is on Google Cloud and when we are behind a simple NAT like a home cable network, we have no trouble connecting.

When we are in corp networks we fail to negotiate Trickle ICE. In the same corp network I have seen Google Hangout work and the Slack phone call work (both use WebRTC).

Anyone have any experience with relay over TCP?

--
You received this message because you are subscribed to the Google Groups "kurento" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kurento+u...@googlegroups.com.

Ivan Gracia

unread,

Oct 14, 2016, 9:49:30 AM10/14/16

to kur...@googlegroups.com

Sorry, I understood that you didn't get candidates at all. Candidates sent by TURN are always UDP. That means that the TURN server has opened a UDP port at the relay address.The connection from the client to the TURN server shouldl be TCP. You can see this in the "priority" field: 1 | 30 | 255, where 1 indicates that you are using TCP as transport for TURN. You might also use wireshark to check that.

Setting IceTransportPolicy to relay should force the use of those candidates.

To view this discussion on the web visit https://groups.google.com/d/msgid/kurento/438b4932-4c40-46ba-bda9-e24f0c338c1c%40googlegroups.com.

Reply all

Reply to author

Forward