RTCPeerConnectionIceErrorEvent interface—based upon the
Event interface—provides details pertaining to an ICE error announced by sending an
icecandidateerror event to the
- Creates and returns a new
RTCPeerConnectionIceErrorEventobject, with its
typeand other properties initialized as specified in the parameters. You will not normally create an object of this type yourself.
RTCPeerConnectionIceErrorEvent interface includes the properties found on the
Event interface, as well as the following properties:
DOMStringproviding the local IP address used to communicate with the STUN or TURN server being used to negotiate the connection, or
nullif the local IP address has not yet been exposed as part of a local ICE candidate.
- An unsigned integer value stating the numeric STUN error code returned by the STUN or TURN server. If no host candidate can reach the server, this property is set to the number 701, which is outside the range of valid STUN error codes. The 701 error is fired only once per server URL, and only while the is
DOMStringcontaining the STUN reason text returned by the STUN or TURN server. If communication with the STUN or TURN server couldn't be established at all, this string will be a browser-specific string explaining the error.
- An unsigned integer value giving the port number over which communication with the STUN or TURN server is taking place, using the IP address given in
nullif the connection hasn't been established (that is, if
DOMStringindicating the URL of the STUN or TURN server with which the error occurred.
RTCPeerConnectionIceErrorEvent has no methods other than any provided by the parent interface,
|WebRTC 1.0: Real-time Communication Between Browsers
The definition of 'RTCPeerConnectionIceErrorEvent' in that specification.
|Candidate Recommendation||Initial definition.|
BCD tables only load in the browser