1012625 - WebRTC TURN Candidate: connection IP == relay IP

Status: RESOLVED DUPLICATE of bug 931700

(Core :: WebRTC, defect)

Description

[richard.screene]

Attachment: Output from Firefox

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)
Build ID: 20140518030203

Steps to reproduce:

This problem occurs on Firefox Nightly 32.0a1 (2014-05-16) as well as Firefox Stable.

I ran the Google example trickle-ice code from here:
//googlechrome.github.io/webrtc/samples/web/content/trickle-ice
(Although, I did have to modify createOffer() call so that second argument was an empty function.)
I entered my TURN server details [munged to the.turn.server.com (aa.bb.cc.dd)]


Actual results:

I received the STUN candidates.  But, I did not receive any local candidates and I received the following TURN candidate:
candidate:3 2 UDP 100401150 aa.bb.cc.dd 57427 typ relay raddr aa.bb.cc.dd rport 57427
ie. with the connection IP and the relay IP identical which sounds a bit wrong!

(As a result of this, calls using our application that require a TURN server go get media delivered.)


Expected results:

I expected to receive local candidates and TURN candidates where the connection IP is the destination and the relay IP is the TURN server.

The behaviour is fine when I use apprtc.appspot.com so I suspect it might be due to the response from my TURN server.  I am using restund 0.4.2

Also, Chrome Stable and Canary work fine with my TURN server.

This might be related to bug 922928

Comment 1

[richard.screene]

I'm seeing the same problem when I attempt to use the Citrix TURN server version 3.2.3.8

Comment 2

[Philipp Hancke]

sounds like bug 931700 -- shouldn't affect functionality though, raddr and rport are only for debugging purposes.