922928 - TURN feature not working

Status: RESOLVED FIXED

(Core :: WebRTC, defect)

Description

[ristar85]

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36

Steps to reproduce:

Set up a Web RTC session.

Go to apprtc.appspot.com for one peer, and then go to the URL (example: apprtc.appspot.com/?r=3453453) for another peer to set up a Web RTC video & audio session when both peers are connected to different networks.

I have tested it on FF 24.0 and the latest versions of Aurora and Nightly.


Actual results:

Both peers can not see/hear one another because TURN was not done. When the peers are on the same network, it works perfectly.


Expected results:

Both peers should be able to do video chat when they are connected to different networks.

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

TURN will be enabled in FF 25, so this is expected in FF24.  It can be turned on in 24 via a pref, but there are some bugs.

Since you say you tried it in Aurora and Nightly, we'd be interested in what exactly you're seeing - wireshark captures and/or logs from the browser.

https://wiki.mozilla.org/Media/WebRTC/Logging

I'd grab both ICE/STUN/TURN logs and signaling logs (signaling:5,mtransport:5,timestamp)

Also please report the build information (from about:support (UserAgent))

Comment 2

[(mostly gone) XtC4UaLL [:xtc4uall]]

see previous comment

Comment 3

[mike.melo]

It seems the Firefox TURN client is not installing permissions for an Allocation's destinations.  This needs to be done either via a CreatePermissions request or a ChannelBind request (see RFC5766 Section 2.3).  The Firefox TURN client is sending TURN Send Indication messages and the TURN server is not forwarding them due to lack of installed permissions.  These Send Indications would contain the STUN connectivity checks that need to be forwarded to the remote user agent.  

You can test using the Citrix open source TURN server (http://code.google.com/p/rfc5766-turn-server/) and Firefox 29.0a1 as endpoints.  I am attaching pcaps taken on the TURN server for both turn->noturn calls and noturn->turn calls.  This test works fine using Chrome as both endpoints.

Comment 4

[mike.melo]

Attachment: noturn -> turn webrtc (audio only) call using Citrix open source TURN server

capture shows STUN/TURN traffic at the Citrix TURN server (10.1.26.35).  Firefox endpoints are 10.1.26.58 and 192.168.1.100 (the 192.168.1.100 endpoint is behind NAT, NAT public interface is 10.1.26.32)

Comment 5

[Eric Rescorla (:ekr)]

Hmm... That doesn't match my results. Can you please re-test with ICE logging
on as shown here, specificlaly with R_LOG_LEVEL 9

https://wiki.mozilla.org/Media/WebRTC/Logging

Alternately, if you want to give me an account on your server, I would be happy
to test myself.

Comment 6

[mike.melo]

Attachment: Firefox WebRTC log, TURN client

Comment 7

[mike.melo]

Attachment: STUN/TURN traffic noturn->turn call, turn client on Linux

Comment 8

[mike.melo]

Attachment: STUN/TURN traffic noturn->turn call, turn client on Windows7

Comment 9

[mike.melo]

My normal testing uses a TURN client running on 64bit Windows 7.  However setting ICE/STUN/TURN logging environment variables per https://wiki.mozilla.org/Media/WebRTC/Logging yields no logfile.

Running same test (no-turn -> turn call) with TURN client running on Debian7/VirtualBox/Windows7 yields slightly better results.  I see a CreatePermission TURN request and an initial video frame is transferred in the no-turn->turn direction.

I have attached network captures at the TURN server for cases where TURN client runs on Win7 and where TURN client runs on Debian7. I also attached the logfile produced when TURN client runs on Debian7.

How exactly does one produce a ICE/STUN/TURN logfile when Firefox Nightly is running on Win7 ?

Thanks!

Comment 10

[Eric Rescorla (:ekr)]

jesup, can you please help mike capture the logs on Windows?

Comment 11

[Randell Jesup [:jesup] (needinfo me)]

mike: see https://wiki.mozilla.org/Media/WebRTC/Logging

Also: on Aurora or nightly (and soon on Beta) you can go to about:webrtc turn on ICE logging, then Select All, Copy and paste it into a file to attach here.

Comment 12

[Byron Campen [:bwc]]

We have a fix up in bug 1000858; could you pull down the latest nightly and give it a try?