New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Effect of a BYE on receiver.track #639

Closed
aboba opened this Issue Jan 18, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@aboba
Contributor

aboba commented Jan 18, 2017

Some questions:

  1. If an RtpReceiver receives a BYE from an RtpSender, what happens?
  2. When transceiver.stop() is called, does transceiver.sender send a BYE?
  3. When transceiver.sender.replaceTrack(null) is called does transceiver.sender send a BYE?
  4. What about when transceiver.sender.track.enabled is set to "false"?

Related WebRTC 1.0 issue: w3c/webrtc-pc#961

@aboba

This comment has been minimized.

Contributor

aboba commented Jan 24, 2017

Here is the resolution being proposed in the WEBRTC WG:

BYE is sent only if SSRC won’t be used again.
When sender.stop() is called, a BYE is sent for all of the sender’s encodings[].ssrc
No BYE sent when setTrack(null) is called because setTrack(anotherTrack) might cause the SSRC to become active again (though the remote receiver might timeout the SSRC, as described in RFC 3550 Section 6.3.5).
No BYE sent when sender.track.enabled is set to "false" since sender.track.enabled could be set back to “true”, reactivating the SSRC.

aboba added a commit that referenced this issue Jan 24, 2017

aboba added a commit that referenced this issue Jan 26, 2017

@aboba aboba added the PR exists label Jan 26, 2017

@aboba aboba closed this Feb 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment