Closed Bug 1640697 Opened 5 years ago Closed 5 years ago

MID filtering filters out RTX packets

Categories

(Core :: WebRTC: Signaling, defect, P1)

78 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla79
Tracking Status
firefox78 --- disabled
firefox79 --- fixed

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.

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.

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.

Attachment #9151848 - Attachment description: Bug 1640697 - Test multiple MID associates with multiple SSRCs; r=ng! → Bug 1640697 - Test MID associated with multiple SSRCs; r=ng!
Blocks: 1641600
Pushed by dminor@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/19790cba352a Use set for MID bindings in MediaPipelineFilter; r=ng https://hg.mozilla.org/integration/autoland/rev/a540f1bff6d1 Test MID associated with multiple SSRCs; r=ng
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79

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.

Flags: needinfo?(dminor)

Since RTX is disabled on 78 I don't think we need to uplift this.

Flags: needinfo?(dminor)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: