Closed
Bug 1496533
Opened 6 years ago
Closed 3 years ago
WebRTC RTCP stats timestamps should be reception time, not query time
Categories
(Core :: WebRTC, enhancement, P2)
Core
WebRTC
Tracking
()
RESOLVED
DUPLICATE
of bug 1729455
People
(Reporter: ng, Assigned: ng)
References
(Blocks 1 open bug)
Details
Right now we, like Chrome, use the query time for the timestamp of the RTCP stats. We should adhere to spec by using the packet reception time (or as close as possible).
|
||
Comment 1•5 years ago
|
||
Bug 1588588 is going to improve this somewhat, but it won't quite get us where we want to be. In bug 1588588, we will start recording timestamps whenever an RTCP packet is received, but we will not keep separate timestamps for SR and RR, nor will we keep separate timestamps for each SSRC. Doing this will require parsing each RTCP packet, and this parse code will need to support compound RTCP.
|
Assignee | |
Comment 2•5 years ago
|
||
This really needs to be handled in libwebrtc. If we go about fixing this it should be in a patch that can be submitted upstream to libwebrtc.
|
||
Comment 3•3 years ago
|
||
I am fixing this in bug 1729455.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•