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.

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');

Urg. Reverse that: Bad: https://bugzilla.mozilla.org/attachment.cgi?id=8360065 Good: https://bugzilla.mozilla.org/attachment.cgi?id=8360538

Breakpoint mxr.mozilla.org/mozilla-central/source/media/webrtc/trunk/webrtc/modules/rtp_rtcp/source/rtcp_receiver.cc#414

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.