RTCRtpReceiver: transport property
Baseline Widely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since January 2020.
The read-only transport
property of an
RTCRtpReceiver
object provides the RTCDtlsTransport
object
used to interact with the underlying transport over which the receiver is exchanging
Real-time Transport Control Protocol (RTCP) packets.
This transport is responsible for receiving the data for the media on the receiver's
track
.
Value
An RTCDtlsTransport
object representing the underlying transport being
used by the receiver to exchange packets with the remote peer, or null
if
the receiver isn't yet connected to a transport.
Description
When the RTCRtpReceiver
is first created, the value of
transport
is null
. This is replaced with an
RTCDtlsTransport
once the receiver's transport has been established.
Note that when bundling is in effect—that is, when the RTCPeerConnection
was created with a configuration object whose bundlePolicy
is max-compat
or max-bundle
—multiple receivers may be sharing the same transport; in this
case, all of them are using the same connection to transmit and/or receive
RTP and RTCP packets.
Specifications
Specification |
---|
WebRTC: Real-Time Communication in Browsers # dom-rtcrtpreceiver-transport |
Browser compatibility
Report problems with this compatibility data on GitHubdesktop | mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
transport |
Legend
Tip: you can click/tap on a cell for more information.
- Full support
- Full support