On Mon, Jul 1, 2013 at 8:25 PM, <[email protected]> wrote: > Thank you. > > Chrome sends RR on a newly established connection, even when no data is > being received yet. I don't see FF (22 or nightly) doing this, and I don't > know what the right behavior is. >
Hmm... I just ran a call under Wireshark, and I do see RTCP packets. We won't send any data prior to DTLS session establishment. What phase of the connection are you in? When I set up FF 22 as a sender (to my mcu) I see that it sends out audio > packets, but stops after a short time. Nightly does not stop sending data. > Does Firefox 22 need to receive binding refreshes or RRs in order to keep > sending data? > I'm not aware of any difference here, but I haven't tried it lately. -Ekr > > On Mon, Jul 1, 2013 at 8:12 PM, Eric Rescorla <[email protected]> wrote: > >> >> On Mon, Jul 1, 2013 at 5:17 PM, <[email protected]> wrote: >> >>> I'm testing webrtc with the latest nightly and I have a couple of >>> questions. >>> >>> Although Firefox completes a DTLS handshake on both the RTP and RTCP >>> ports, I don't see any traffic over the RTCP port. Is this expected >>> behavior? In the same setup, Chrome does send SR and/or RR. >>> >> >> It should be sending RR. There's a bug and so we currently are not >> sending SR. >> >> >> >>> Also, after the initial ICE and DTLS-SRTP handshake, I do not see >>> Firefox issue periodic STUN bind requests as Chrome does. Is this expected? >>> >> >> There has been discussion at IETF about doing this, but I don't >> believe it's currently completely specified. We'll presumably >> do it eventually. >> >> -Ekr >> >> > _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
