Force TCP for WebRTC PeerConnections

Question

Is it possible to force a TCP tunneled (TLS) connection with WebRTC?

We are developing a WebRTC application for our business, but we are experiencing some major issues with incoming UDP streams caused by our internal network. We are already using a TURN server and we are getting a bunch of ICE candidates (even relay UDP ones).

The thing is, as I stated above, that our incoming UDP traffic does not work reliable here (stuttering, very bad image quality, very low fps). It's enough to give the Browser the impression, that WebRTC can use it for it's PeerConnection(s), but the actual result is very bad over UDP.

If I block all outgoing and incoming UDP streams, I can see (in Wireshark) that WebRTC falls back to TCP traffic by using our turn server.

With TCP connections, we are getting very good results (with high frame rates and a very good image quality).

I've already tried several things to force TCP:

1. I deleted the UDP part in the m=video line

   m=video TLS/RTP/SAVPF 100 116 117 96

2. I've excluded every single UDP candidate from my candidate list

In each case I was not even able to establish a connection.

Is there anything I can do to force TCP in WebRTC or do we really depend completely on the browser here?

Answer 1

Configure the peerconnection with a TURN/TCP server and set the iceTransports constraint to relay. See http://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ Note that quality is typically worse than over UDP.

ICE-TCP is not supported for browser-to-browser connections. Only if you have a SFU/MCU/Gateway thing.