Expand description
A WebRTC transport represents a network path negotiated by both, a WebRTC endpoint and mediasoup, via ICE and DTLS procedures. A WebRTC transport may be used to receive media, to send media or to both receive and send. There is no limitation in mediasoup. However, due to their design, mediasoup-client and libmediasoupclient require separate WebRTC transports for sending and receiving.
§Notes on usage
The WebRTC transport implementation of mediasoup is ICE Lite, meaning that it does not initiate ICE connections but expects ICE Binding Requests from endpoints.
Structs§
- Empty list of listen IPs provided, should have at least one element
WeakWebRtcTransport
doesn’t ownWebRtcTransport
instance on mediasoup-worker and will not prevent one from being destroyed once last instance of regularWebRtcTransport
is dropped.- A
WebRtcTransport
represents a network path negotiated by both, a WebRTC endpoint and mediasoup, via ICE and DTLS procedures. AWebRtcTransport
may be used to receive media, to send media or to both receive and send. There is no limitation in mediasoup. However, due to their design, mediasoup-client and libmediasoupclient require separateWebRtcTransport
s for sending and receiving. - Struct that protects an invariant of having non-empty list of listen IPs
WebRtcTransport
options.- Remote parameters for
WebRtcTransport
. - RTC statistics of the
WebRtcTransport
.
Enums§
- How
WebRtcTransport
should listen on interfaces.