-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Properly handle non-media probes #2816
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2816 +/- ##
==========================================
- Coverage 79.14% 79.03% -0.11%
==========================================
Files 89 89
Lines 8270 8290 +20
==========================================
+ Hits 6545 6552 +7
- Misses 1257 1265 +8
- Partials 468 473 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Yay! For more info on when this can happen, it requires RTX to be enabled and it requires SetAllowProbeWithoutMediaPacket to be enabled (modules/pacing/bitrate_prober.cc in libwebrtc). In this case BWE probes get sent as soon as the ICE connection is established, before tracks start. The probes have SSRC 0. This change was made recently in the Chromium repo, I am not sure if it is in production yet (or just in canary) but if it isn't happening now, it soon will so this PR is super important. Right now Pion ignores this 'probe track' which means TWCC/RTCP RRs do not get sent for it. This makes the sender think there is 100% packet loss on the probes, which causes it to adjust sender bandwidth to hit the defined bitrate floor - not very nice! |
08a15e6
to
458dcba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
3a6298f
to
2cd7263
Compare
libwebrtc has started sending media probes on an unannounced SSRC(0). Currently Pion will ignore this as the SSRC hasn't been declared explicitly and no RID/MID RTP Headers. This adds a special case to accept SSRC 0 and Read the RTP packets. This allows the TWCC reports to properly be generated.
2cd7263
to
ca717ff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
libwebrtc has started sending media probes on an unannounced SSRC(0). This adds a special case to accept SSRC 0 and Read the RTP packets. This causes the TWCC reports to properly be generated.