1296475 - TURN/TCP with hostnames doesn't work with talky.io

Status: RESOLVED WORKSFORME

(Core :: WebRTC: Networking, defect, P2)

Description

[Nils Ohlmeier [:drno]]

After fixing bug 1290365 I checked (too late) if the same problem exists on Windows or Mac.
As it turn out even after landing bug 1290365 Windows and Mac both fail to gather relay candidates with this test (note: it fails on 48 and 51, so the problem is independent of the code in bug 1290365):

1. go to https://talky.io
2. grab turn credentials by pasting this into the console:
  var ice = app.xmpp.jingle.config.peerConnectionConfig.iceServers[2]
3. set
  ice.url = 'turn:turn1.talky.io:80?transport=tcp'
4. gather candidates by pasting 
this into the console:
  var pc = new RTCPeerConnection({iceServers: [ice]}); pc.onicecandidate = function(event) { console.log(event.candidate ? event.candidate.candidate : null); }; pc.createOffer({offerToReceiveAudio: 1}).then((offer) => pc.setLocalDescription(offer));
5. observe the lack of relay candidates until the 'null' candidate gets logged

Comment 1

[Nils Ohlmeier [:drno]]

Apparently the reason for the lack of relay candidates is that Talky's TURN server rejects all of Firefox requests with 401's (even with the credentials provided by talky.io).

I'll check with my own TURN server...

Comment 2

[Nils Ohlmeier [:drno]]

It works fine with my own TURN server. So this is either some strange interop issue with Talky's TURN server, or something else specific to Talky's setup.

Comment 3

[Nils Ohlmeier [:drno]]

Cross check with Chrome shows the same symptom: works with IP address, but fails to gather relay candidate with the DNS name.

Comment 4

[Nils Ohlmeier [:drno]]

And here is the solution: you have to use ice.url = 'turn:turn2.talky.io:80?transport=tcp'. So apparently turn1 doesn't accept turn2's credentials :-)