-
Notifications
You must be signed in to change notification settings - Fork 5
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
Find out why we have so many warnings on missing RTPs on certain active subscriptions #121
Comments
One of the reasons why this happens is if there is a video that is muted. There are possible mitigations for this warning, see: #137 (comment) |
After running it with the OpenTelemetry, so far it looks like these happened in two cases for video tracks only:
UPD: We receive the update of the metadata when muting/unmuting. |
When the user mutes the video, we don't get any RTPs. We don't assume this error anymore and don't change the status of the track and its telemetry for that. This removes false-positives related to the #121
When the user mutes the video, we don't get any RTPs. We don't assume this error anymore and don't change the status of the track and its telemetry for that. This removes false-positives related to the #121
After several sessions with OpenTelemetry it has become clear that these are caused by the browser not publishing higher levels (1) and videos being muted (2). (2) was addressed by a PR. See #131 for the related issue of missing RTP packets. |
A log line like this one is not uncommon during normal sessions:
It's not clear why there is an active subscription (with a low layer) that, despite being published, does not receive RTP frames with an intact publisher track. When the publisher track is gone, we remove all subscriptions associated with this track (check if we don't miss any edge cases).
It does not seem like this error has a big practical application (we did not observe any frozen subscription), yet it may point out to some bug in the SFU that must be resolved.
The text was updated successfully, but these errors were encountered: