MID filtering filters out RTX packets
Categories
(Core :: WebRTC: Signaling, defect, P1)
Tracking
()
People
(Reporter: dminor, Assigned: dminor)
References
Details
Attachments
(2 files)
With MID filtering enabled, we drop RTX packets because they arrive with the same MID but a different ssrc. I didn't notice this in my initial testing because the first few RTX packets seem to make it through. We probably need to match against ssrc and payload type instead of just ssrc.
Comment 1•5 years ago
|
||
Or turn it into a list of SSRCs. Because as long as we know the MID we know to which m-section the RTP stream belongs to.
Assignee | ||
Comment 2•5 years ago
|
||
With RTX enabled, we have multiple SSRCs associated with a single MID, but the
filter code assumes that only one binding will be present. This change allows
a set of SSRCs to be associated with a MID.
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D76894
Updated•5 years ago
|
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/19790cba352a
https://hg.mozilla.org/mozilla-central/rev/a540f1bff6d1
Comment 6•5 years ago
|
||
The patch landed in nightly and beta is affected.
:dminor, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 7•5 years ago
|
||
Since RTX is disabled on 78 I don't think we need to uplift this.
Updated•5 years ago
|
Description
•