In Section 22.214.171.124 it is stated:
If the server could not be reached, errorCode will be set to a TBD value in the 7XX range, as this does not conflict with the STUN error code range.
This will be a problem for IPv6 where the browser can have interfaces (such as tunnel interfaces) with routability problems.
From Robin Raymond:
"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)."
We need someway to debug which TURN serves could not be reach.
Server cannot be reached - Issues with IPv6
Fix for Issue #542
Server could not be reached
Fix for w3c/webrtc-pc#542 (from WebRTC 1.0).
Server cannot be reached
Grammatical improvement. Related to Issue w3c/webrtc-pc#542 (from WebRTC 1.0).