Add support for STUNS scheme for STUN server
Reported by
mak...@appvuze.com,
Jun 15 2017
|
|||||||
Issue descriptionWhat steps will reproduce the problem? 1. Open https://appvuze.io:8443 2. Remove default google stun server, by selecting it and clicking remove server 3. Enter stuns:webrtcweb.com:7788 in the STUN or TURN URI text box and click add server 4. Click Generate Candidates and allow microphone sharing (this was added for another bug investigation) What is the expected result? It should produce stun webrtc candidates What do you see instead? Exception: Uncaught DOMException: Failed to construct 'RTCPeerConnection': 'stuns' is not one of the supported URL schemes 'stun', 'turn' or 'turns'. at window.RTCPeerConnection (https://webrtc.github.io/adapter/adapter-latest.js:1033:16) at start2 (https://appvuze.io:8443/js/main.js:134:8) What version of the product are you using? On what operating system? Latest Chrome 59 and Opera 45 on Mac OS X. Please provide any additional information below. It looks like native webrtc libjingle already supports stuns protocol, however, it looks like it's not exposed to JavaScript in Chrome. Please add it. Thank you!
,
Jun 16 2017
,
Jun 16 2017
By the way, without this, doing WebRTC connections without ICE trickle results in 40 second delay when generating ICE candidates, see bug: https://bugs.chromium.org/p/webrtc/issues/detail?id=7844
,
Jun 16 2017
See my comment on that bug. I don't see how the two are related, since the repro steps there don't involve a "stuns" URI.
,
Jun 19 2017
,
Jun 27 2017
Unable to triage this issue from our end (chrome-hyd team )as this issue related to STUN server WebRTC,Could some one from dev team please look into this issue. Adding 'TE-NeedsTriageHelp' label for further investigation. Thank you..!!
,
Jun 27 2017
,
Oct 12 2017
Ping for triaging.
,
Oct 12 2017
,
Oct 15
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kjellander@chromium.org
, Jun 16 2017