On 2/5/2015 2:34 PM, Kannan Murali wrote:
I am trying WebRTC H264 video with FF 35.0.1 version. My FF WebRTC
client is gets into a loop where it requests certain number of video
packets which got dropped in the network and there is no way of
re-transmission (as the other side client is non WebRTC client which
doesn't do re-transmission) of those packets. The WebRTC client never
gets recovered even after sending FIR packets (in fact, there is a
periodic request/transmission of FIR). How could I get the WebRTC
client recover from this state??? -KMurali
Looks like there are few packets missing from the FF WebRTC client source
itself - This is clear from the wireshark trace captured from the source WebRTC
client. Is there any known reason that the source Firefox WebRTC client could
drop the packets? Could be related to any bitrate calculation? If so, how to
handle (or adjust the bitrate) in the FF?
I'm having a little trouble understanding your second message in
detail. "missing from the FF WebRTC client source itself" means exactly
what?
a) what are the recovery options negotiated? All a=rtcp-fb messages on
each side for the selected codec. Did the far end (non-browser) say it
does NACK when it doesn't?
b) (UDP) packets can always be dropped (even in the driver or HW, such
as due to buffer overflow).
c) am I correct in reading your description as "FF 35 sent RTCP FIR
packets, but never recovered successfully"? Did the sending side send a
keyframe/IDR in response? Were they FIR or PLI packets?
d) Bitrate is automatically adjusted using the bandwidth estimation code
and data from the far side in RTCP in media/webrtc/trunk/webrtc, and
bandwidth data is also provided to the far side to adjust their sending
rate via RTCP. This uses the same messages and algorithms as Chrome is
currently.
It would help a lot to file a bug with a relevant snippet of the
Wireshark, and also logs. See
https://wiki.mozilla.org/Media/WebRTC/Logging - we'd be interested in
Signaling and Media logging. Note Media logs wrap quickly (10MB max,
and a LOT gets logged), so kill the browser shortly after showing what
happens.
--
Randell Jesup, Mozilla
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
