"srflx" candidates missing in /trickle-ice/ page with TURN server |
|||
Issue descriptionVersion: Win, Mac, Linux OS: M49 Stable, M50 dev/Beta What steps will reproduce the problem? (1) Go to https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ (2) Gather candidates with the default STUN server (3) Now establish an apprtc loopback call in another tab (4) Collect TURN server credentials from the apprtc JS console (5) Copy-paste the credentials in the trickle-ice page, and add the TURN server (6) Remove the default STUN server (7) Gather candidates again What is the expected output? What do you see instead? Expected: "srflx" and "relay" candidates should be seen for TURN server Actual: only "relay" candidates are seen; "srflx" candidates are missing Attached screenshot. Please use labels and text to provide additional information.
,
Mar 11 2016
srnarayanan@ - it looks like your machine was on the google-a wireless network. Can you try the same test while on googleguest?
,
Mar 11 2016
FYI because you are not getting a a particular candidate does not necessary mean Chrome or the sample page is doing something wrong. You will not always get all candidate types, as Ted mentioned, it depends on the network configuration.
,
Mar 11 2016
Thanks for the clarification! With GoogleGuest, I see srflx and relay candidates for TURN server. My bad, I assumed this had something to do with the recent TURN server issue, hence this bug :/ So far, on Google-A, I've always seen both srflx and relay candidates when I run the trickle-ice test case.
,
Apr 11 2016
srnarayanan@ - Any updates on this bug? Can we close this issue as per your comment #4?
,
Apr 11 2016
Yes, Closing as "Won't fix". |
|||
►
Sign in to add a comment |
|||
Comment 1 by srcv@chromium.org
, Mar 10 2016