Each SDP media section describes one bidirectional SRTP ("Secure Real Time Protocol") stream (excepting the media section for
RTCDataChannel, if present). This pairing of send and receive SRTP streams is significant for some applications, so
RTCRtpTransceiver is used to represent this pairing, along with other important state from the media section. Each non-disabled SRTP media section is always represented by exactly one transceiver.
A transceiver is uniquely identified using its
mid (en-US) property, which is the same as the media ID (
mid) of its corresponding m-line. An
RTCRtpTransceiver is associated with an m-line if its
mid is non-null; otherwise it's considered disassociated.
- A read-only string from the enum
RTCRtpTransceiverDirection(en-US) which indicates the transceiver's current directionality, or
nullif the transceiver is stopped or has never participated in an exchange of offers and answers. To change the transceiver's directionality, set the value of the
- A string from the enum
RTCRtpTransceiverDirection(en-US) which is used to set the transceiver's desired direction.
- The media ID of the m-line associated with this transceiver. This association is established, when possible, whenever either a local or remote description is applied. This field is
nullif neither a local or remote description has been applied, or if its associated m-line is rejected by either a remote offer or any answer.
RTCRtpReceiver(en-US) object that handles receiving and decoding incoming media.
RTCRtpSender(en-US) object responsible for encoding and sending data to the remote peer.
- Indicates whether or not sending and receiving using the paired
RTCRtpReceiverhas been permanently disabled, either due to SDP offer/answer, or due to a call to
- A list of
RTCRtpCodecParameters(en-US) objects which override the default preferences used by the user agent for the transceiver's codecs.
- Permanently stops the
RTCRtpTransceiver. The associated sender stops sending data, and the associated receiver likewise stops receiving and decoding incoming data.
|WebRTC 1.0: Real-time Communication Between Browsers
BCD tables only load in the browser