TCP Relay

[Ben Hamrick]

I am unable to get the turn server to use tcp as the rally protocol. I have been testing the candidates and I seem to only get udp candidates no matter what I do. Should I not see both? When I configure the server to have --no-udp-relay I just get an error message when I try to create the webrtc connection telling me that udp has been turned off. Am I missing something here? We are trying to get webrtc to work over a network that blocks all udp traffic.

[Ben Hamrick]

relay not rally

[Tom van der Geer]

Hi Ben,

Did you ever get this to work? Of find out why it didn't work?

I'm trying the same and seem to face the same problem.

Best regards,

Tom

Op woensdag 7 juni 2017 00:42:23 UTC+2 schreef Ben Hamrick:

[Tom van der Geer]

Turns out that I had the concept wrong. The generated candidate is the candidate that is sent to the other peer. It’s in no way an indication on how the requesting client will send its media to the TURN server but is merely the notice that the peer can send its media to the TURN server over UDP. While the local peer - which is requesting the TURN connection - will send its media over TCP to the TURN server. But you will not see any candidate for that at all. It’s all handled automatically in the PeerConnection.

I’ve verified this by making a wireshark trace. Chrome is sending its media over TCP to the TURN server. And it’s sending a UDP relay candidate to the other peer. In my case this is a FreeSWITCH based media server. FreeSWITCH sends its media to the TURN server over UDP. (It’s not even capable of doing this over TCP; aka ICE-TCP)

Best regards,

Tom