Thanks for the clarification! Until this is fixed, is it correct to assume that putting the RTCP SSRC in RTCP packets addressed to Firefox is the right thing to do? or does Firefox ignore them right now and only cares about what message (e.g., NACK, PLI, REMB, etc.) is received?
Il giorno giovedì 10 ottobre 2013 19:22:03 UTC+2, Randell Jesup ha scritto: > On 10/10/2013 11:28 AM, Lorenzo Miniero wrote: > > > To partially correct my previous statement, the SSRC does match in the > > audio RTP/RTCP, while it does not for video. > > > > Correct. This is caused by Firefox using two ViE channels for video > > (one for send, one for receive). We expect to resolve this soon. See > > bug 864654. > > > > > > > > Lorenzo > > > > > > > > > Il giorno giovedì 10 ottobre 2013 17:18:42 UTC+2, Lorenzo Miniero ha > > scritto: > > >> Hi, > > >> > > >> > > >> > > >> I'm using Nightly to test my WebRTC gateway implementation, and I've > >> noticed something weird. Apparently the SSRC Nightly puts in the RTCP > >> packets differs from the one that actually appears in RTP packets: I > >> verified this both by parsing the RTCP packets manually and sniffing the > >> unprotected RTCP headers in Wireshark. > > >> > > >> > > >> > > >> Is this a known issue, or is this unexpected? unlike Nightly my gateway > >> does not mux (and in fact the issue happens for both audio and video), as > >> it is negotiating RTP and RTCP candidates on different ports, may this be > >> the cause? _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
