RTCDtlsTransport: error event

An RTCDtlsTransport receives an error event when a transport-level error occurs on the RTCPeerConnection.

This event is not cancelable and does not bubble.

Syntax

Use the event name in methods like addEventListener(), or set an event handler property.

addEventListener('error', (event) => {});

onerror = (event) => { };

Event type

Event properties

In addition to the standard properties available on the Event interface, RTCErrorEvent also includes the following:

error Read only

An RTCError object specifying the error which occurred; this object includes the type of error that occurred, information about where the error occurred (such as which line number in the SDP or what SCTP cause code was at issue).

Description

Transport-level errors will have one of the following values for the specified error's RTCError property errorDetail:

dtls-failure

The negotiation of the DTLS connection failed, or the connection was terminated with a fatal error. The error's message contains details about the nature of the error. If a fatal error is received, the error object's receivedAlert property is set to the value of the DTLSL alert received. If, on the other hand, a fatal error was sent, the sentAlert is set to the alert's value.

fingerprint-failure

The remote certificate for the RTCDtlsTransport didn't match any of the fingerprints listed in the SDP. If the remote peer can't match the local certificate against the provided fingerprints, this error doesn't occur, though this situation may result instead in a dtls-failure error.

Examples

In this example, the onerror event handler property is used to set the handler for the error event.

transport.onerror = (ev) => {
  const err = ev.error;

  // …
}

Note: Since RTCError is not one of the legacy errors, the value of code is always 0.

Specifications

No specification found

No specification data found for api.RTCDtlsTransport.error_event.
Check for problems with this page or contribute a missing spec_url to mdn/browser-compat-data. Also make sure the specification is included in w3c/browser-specs.

Browser compatibility

BCD tables only load in the browser

See also