-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTCPeerConnectionIceErrorEvent errorCode not defined #521
Comments
I'm not sure this particular error is wise. In any implementation (especial IPV6), it's very likely many host candidates will not be able to reach the TURN server or STUN server because they don't route appropriately. So you will warn/flag these as being failed but with other host candidates they actually succeed. The programmer will think things are going horribly wrong when this is probably normal. Further, if you don't indicate that this URI is actually succeeding then the programmer is going to be somewhat in the dark as to what's going on. I would only use the "cannot contact server" error if NONE of the host IPs could reach the server. (Although that could just indicate a general connectivity problem and not really a server problem). |
Removed "server cannot be reached" error, responding to Robin Raymond's comment on Issue #521
Fixed in #525 |
https://www.w3.org/2011/04/webrtc/wiki/images/5/50/WebRTCWG-2016-02-25.pdf#9 lists the error codes, but the spec does not provide that info (just says the error is a string).
The text was updated successfully, but these errors were encountered: