W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2019

[webrtc-pc] Setting active attribute to false triggers BYE? (#2202)

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Thu, 06 Jun 2019 00:43:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-452779348-1559781837-sysbot+gh@w3.org>
aboba has just created a new issue for https://github.com/w3c/webrtc-pc:

== Setting active attribute to false triggers BYE? ==
We are currently seeing a BYE being sent as a result of setting the `active` attribute to `false`. This doesn't seem right - my understanding is that a BYE is to be sent only when an SSRC is removed, such as for [RTCRtpTransceiver.stop()](https://w3c.github.io/webrtc-pc/#rtcrtptransceiver-interface).  Setting the active attribute to false doesn't cause the SSRC to removed, so it shouldn't result in sending a BYE.  However, it could cause the inactivated SSRC to timeout on the receiver (https://w3c.github.io/webrtc-pc/#mediastreamtrack) . From RFC 3550 Section 6.3.5:

   Any member on the sender list who has not sent an RTP packet
   since time tc - 2T (within the last two RTCP report intervals) is
   removed from the sender list, and senders is updated.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2202 using your GitHub account
Received on Thursday, 6 June 2019 00:44:00 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 6 June 2019 00:44:01 UTC