From 6d7f9877f879aab02c60f473f14daa9713655de0 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Wed, 25 Jul 2018 13:41:26 -0700 Subject: [PATCH] Merger of PR 1902 Re-base and merging of PR https://github.com/w3c/webrtc-pc/pull/1902 --- webrtc.html | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/webrtc.html b/webrtc.html index 6e0b95405..05e58d074 100644 --- a/webrtc.html +++ b/webrtc.html @@ -707,8 +707,8 @@

RTCSignalingState Enum

stable - There is no offer­answer exchange in progress. This is - also the initial state in which case the local and remote + There is no offer/answer exchange in progress. This is + also the initial state, in which case the local and remote descriptions are empty. @@ -7182,10 +7182,20 @@

Methods

RTCRtpTransceiver's associated RTCPeerConnection.

Stopping a transceiver will cause future calls - to createOffer to generate a zero port - in the media description for the corresponding - transceiver, as defined in + to createOffer or createAnswer to + generate a zero port in the media description for the + corresponding transceiver, as defined in [[!JSEP]].

+

If this method is called in between applying a + remote offer and creating an answer, and the transceiver is + associated with the "offerer tagged" media description as + defined in [[!BUNDLE]], this will cause all other transceivers + in the bundle group to be stopped as well. To avoid this, one + could instead stop the transceiver when + signalingState + is "stable" + and perform a subsequent offer/answer exchange. +

When the stop method is invoked, the user agent MUST run the following steps: