No connection a valid turn server candidate if the first attempt was to connect to an unreachable candidate
Reported by
tamar2...@gmail.com,
Dec 28 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce the problem: 1. Enter two turn server candidates: 1.1 first server - set unreachable server 1.2 Second server - set reachable server 2. Start WebRTC conference in turn What is the expected behavior? 1. Connection to the first candidate turn server fails 2. Recovery by connecting to the second candidate 3. WebRTC conference starts What went wrong? 1. No connection to the second candidate server 2. WebRTC conference fails to connect Did this work before? N/A Does this work in other browsers? N/A Chrome version: 63.0.3239.108 Channel: stable OS Version: 10.0 Flash Version:
,
Jan 1 2018
Thanks for filing the issue! @Reporter: Could you please mention if there is any setup or page which can be used to test this. Any further inputs from your end helps us to triage the issue in a better way.
,
Jan 2 2018
,
May 21 2018
Also: Are you SURE that no connection is made to the second server? Because that's definitely unexpected. My guess would be that the unreachable server just delays the transition to an RTCIceGatheringState of "complete" (indicated by "onicecandidate" event with a null candidate). Does reversing the order of the servers make a difference?
,
Nov 9
Closing this issue due to lack of user feedback and assuming that issue got fixed from their end. Please feel fee to raise a new issue if the issue is still reproducible on latest chrome builds. Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Dec 28 2017