Skip to content

/ ortc

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

Jump to bottom

Multiple RTX in RTCRtpCapabilities.codecs #627

Closed
aboba opened this issue Dec 22, 2016 · 1 comment
Closed

Multiple RTX in RTCRtpCapabilities.codecs #627

aboba opened this issue Dec 22, 2016 · 1 comment
Assignees
@aboba
Labels
1.1 PR exists

Comments

@aboba
Copy link
Contributor

@aboba aboba commented Dec 22, 2016 •
edited

To allow for capabilities negotiation, it makes sense to have multiple RTX codecs advertised in capabilities, one for each codec that is being retransmitted. Although RTX could be understood to apply to all codecs of a given kind, having the preferred payload type enables capability-exchange signaling. The spec already says this, but could use more explanation.
@robin-raymond
Copy link
Contributor

@robin-raymond robin-raymond commented Dec 22, 2016

This makes sense to me with the apt in the capability.
@aboba aboba changed the title Multiple RTX in RTCRtpCapabilities Multiple RTX in RTCRtpCapabilities.codecs Dec 24, 2016
@aboba aboba self-assigned this Jan 3, 2017
@aboba aboba added the 1.1 label Jan 3, 2017
aboba added a commit that referenced this issue Jan 4, 2017
@aboba
RTX in RTCRtpCapabilities.codecs
52261eb 
Fix for Issue #627
@aboba aboba mentioned this issue Jan 4, 2017
Merged
@aboba aboba added the PR exists label Jan 4, 2017
@aboba aboba closed this Jan 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aboba aboba

Labels
1.1 PR exists
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@aboba @robin-raymond