Skip to content

PeerConnectionState does not transition to "failed" when DTLSTranport state is "failed" #3272

@enobufs

Description

@enobufs

Your environment.

  • Version: v4 master (ae65995)
  • Browser: n/a
  • Other Information - macOS M1

What did you do?

Ran a unit test TestInvalidFingerprintCausesFailed

What did you expect?

PeerConnectionState to transition to "failed" when DTLSTransport state goes to "failed"

What happened?

No state change in PeerConnection. (PeerConnection state in the test eventually goes to "closed" along with ICE connection state.

According to the W3C WebRTC spec, when a DTLSTransport is in "failed" state, the PeerConnection should also transition to "failed" state:

failed: Any of the RTCIceTransports or RTCDtlsTransports are in a "failed" state.

Currently, the PeerConnection state does not reflect the DTLS failure (it goes directly from connecting to closed).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions