You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the exact meaning, refer to the [RTCDtlsTransport: state property](https://developer.mozilla.org/en-US/docs/Web/API/RTCDtlsTransport/state)
60
60
"""
@@ -73,10 +73,10 @@ defmodule ExWebRTC.PeerConnection do
73
73
Most of the messages match the [RTCPeerConnection events](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection#events),
74
74
except for:
75
75
* `:dtls_transport_state_change` - traditional WebRTC implementation does not emit such event.
76
-
Instead, developer can read DTLS transport state by iterating over RTP receiver/senders, and checking their
76
+
Instead, developer can read DTLS transport state by iterating over RTP receivers/senders, and checking their
77
77
DTLS transports states. See https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpSender/transport.
78
78
However, because Elixir WebRTC creates a single DTLS transport for all receivers and senders, there is one generic
79
-
notification informing about DTLS transport state.
79
+
notification for convenience and parity with other events informing about ice/signaling/connection state changes.
80
80
* `:track_muted`, `:track_ended` - these match the [MediaStreamTrack events](https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack#events).
81
81
* `:data` - data received from DataChannel identified by its `ref`.
82
82
* `:rtp` and `:rtcp` - these contain packets received by the PeerConnection. The third element of `:rtp` tuple is a simulcast RID and is set to `nil` if simulcast
@@ -1748,9 +1748,7 @@ defmodule ExWebRTC.PeerConnection do
0 commit comments