The read-only RTCRtpTransceiver
property direction
is a string which indicates the transceiver's preferred directionality. Its value must be one of the strings defined by the RTCRtpTransceiverDirection
enumeration.
The transceiver's current direction is indicated by the currentDirection
property.
var direction = RTCRtpTransceiver.direction
A DOMString
whose value is one of the strings which are a member of the RTCRtpTransceiverDirection
enumerated type, indicating the transceiver's preferred direction.
The RTCRtpTransceiverDirection
type is an enumeration of string values. Each describes how the transceiver's associated RTCRtpSender
and RTCRtpReceiver
behave as shown in the table below.
Value |
RTCRtpSender behavior |
RTCRtpReceiver behavior |
---|---|---|
"sendrecv" | Offers to send RTP data, and will do so if the other peer accepts the connection and at least one of the sender's encodings is active1. | Offers to receive RTP data, and does so if the other peer accepts. |
"sendonly" | Offers to send RTP data, and will do so if the other peer accepts the connection and at least one of the sender's encodings is active1. | Does not offer to receive RTP data and will not do so. |
"recvonly" | Does not offer to send RTP data, and will not do so. | Offers to receive RTP data, and will do so if the other peer offers. |
"inactive" | Does not offer to send RTP data, and will not do so. | Does not offer to receive RTP data and will not do so. |
[1] To determine if a sender has at least one active encoding, the user agent gets its parameters using RTCRtpSender.getParameters()
, then looks at the parameters' encodings
property; if any of the listed encodings has its active
property set to true
, the sender has an active encoding.
When setting the value of direction
, the following exceptions can occur:
InvalidStateError
RTCPeerConnection
is closed or the RTCRtpReceiver
is stopped.When you change the value of direction
, an InvalidStateError
exception will occur if the connection is closed or the receiver is stopped.
If the new value of direction
is in fact different from the existing value, renegotiation of the connection is required, so a notificationneeded
event is sent to the RTCPeerConnection
.
The value of direction
is used by RTCPeerConnection.createOffer()
or RTCPeerConnection.createAnswer()
in order to generate the SDP generated by each of those methods. The SDP contains an a-line which specifies the directionality. For example, if the direction
is specified as "sendrecv"
, the corresponding SDP a-line is:
a=sendrecv
Specification | Status | Comment |
---|---|---|
WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCRtpTransceiver.direction' in that specification. | Candidate Recommendation |
Desktop | ||||||
---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | |
Basic support | No | ? | 59 | No | No | ? |
Mobile | |||||||
---|---|---|---|---|---|---|---|
Android webview | Chrome for Android | Edge Mobile | Firefox for Android | Opera for Android | iOS Safari | Samsung Internet | |
Basic support | No | No | ? | 59 | No | ? | No |
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpTransceiver/direction