Transceivers allow the sending and/or receiving of media in WebRTC. Stopping a transceiver makes it permanently inactive.
Stopping a transceiver allows freeing its network port, encoder and decoder resources. This also makes its m= section in the SDP reusable by future transceivers, preventing the SDP from growing indefinitely as transceivers are added and removed. This is part of "Perfect Negotiation", which makes signaling in WebRTC race-free and less error-prone. For more details, see https://docs.google.com/presentation/d/1xcvf0udNeSH7s1FOY7RRqr1dEFvokZjn-MZPjwy3iXQ/edit?usp=sharing.
Status in Chromium
Enabled by default (tracking bug) in:
- Chrome for desktop release 88
- Chrome for Android release 88
- Android WebView release 88
Consensus & Standardization
- No signals
Intent to Prototype urlIntent to Prototype thread
Search tagsWebRTC RTCRtpTransceiver transceiver stop media,
Last updated on 2020-10-25