Closed
Bug 960177
Opened 10 years ago
Closed 10 years ago
Not receiving audio RTCP Sender Reports unless streams are added in both directions
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 859971
People
(Reporter: jib, Unassigned)
Details
From Bug 947665 Comment 12: > I think I've uncovered a bug: a new specstats.html is needed to get audio > jitter reports. > > It appears we don't receive RTCP sender reports (w/audio jitter) unless a > stream is added to BOTH PeerConnections involved.
Reporter | ||
Comment 1•10 years ago
|
||
Good: https://bugzilla.mozilla.org/attachment.cgi?id=8360065 Bad: https://bugzilla.mozilla.org/attachment.cgi?id=8360538 Difference: line marked below function connect() { pc1 = new RTCPeerConnection(null); pc2 = new RTCPeerConnection(null); pc1.addStream(mystream, streamConstraints()); // Bug: a return stream seems needed or we get no RTCP audio jitter reports > pc2.addStream(mystream, streamConstraints()); log('PC1 creating offer');
Reporter | ||
Comment 2•10 years ago
|
||
Urg. Reverse that: Bad: https://bugzilla.mozilla.org/attachment.cgi?id=8360065 Good: https://bugzilla.mozilla.org/attachment.cgi?id=8360538
Reporter | ||
Comment 3•10 years ago
|
||
Breakpoint mxr.mozilla.org/mozilla-central/source/media/webrtc/trunk/webrtc/modules/rtp_rtcp/source/rtcp_receiver.cc#414
Reporter | ||
Comment 4•10 years ago
|
||
http://mxr.mozilla.org/mozilla-central/source/media/webrtc/trunk/webrtc/modules/rtp_rtcp/source/rtcp_receiver.cc#414
Comment 5•10 years ago
|
||
We've had this issue for a while, and fixing it is going to require some conduit refactoring. Duping to Bug 859971, although it's also related to Bug 861780.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•