Expose jitter buffer stats

NEW
Unassigned

Status

()

Core
WebRTC
P3
normal
a year ago
3 months ago

People

(Reporter: drno, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox50 affected)

Details

(Reporter)

Description

a year ago
In case of bug 1273652 RTP packets actually made it successfully all the way into the jitter buffer. But because of wrong initialization of the jitter buffer it threw away the incoming data (at least that is my understanding). Therefore the stats we expose so far reported no loss at all.

Is it possible to expose stats from the jitter buffer about things like:
- packets which arrived too late
- packets which got discarded by the jitter buffer for whatever reason
- missing packets from the point of view of the jitter buffer
to make it easier in the future to detect similar issues earlier next time?
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.