Note: Until recently, the
stopped property was provided to return
true if the connection is
stopped. That property has been deprecated and will be removed at some point. Instead,
check the value of
currentDirection. If it's
stopped, the transceiver has been stopped.
This method does nothing if the transceiver is already stopped.
RTCPeerConnectionof which the transceiver is a member is closed.
When you call
stop() on a transceiver, the sender immediately stops
sending media and each of its RTP streams are closed using the RTCP
"BYE" message. The receiver then stops receiving media; the receiver's
track is stopped, and the transceiver's
direction is changed to
stopped, and renegotiation is triggered by sending a
negotiationneeded event to the
The negotiation process causes
currentNegotiation to be set to
stopped, finally indicating that the
transceiver has been fully stopped.
|WebRTC 1.0: Real-time Communication Between Browsers
The definition of 'RTCRtpTransceiver.stop()' in that specification.
BCD tables only load in the browser