Chrome sends PLI even when remote description doesn't negotiate it
Reported by
jonathan...@gmail.com,
Apr 18 2017
|
|||||||||||
Issue descriptionWhat steps will reproduce the problem? 1. Start a WebRTC session with a video stream. 2. Send a remote description which has a=rtcp-fb:NN nack and a=rtcp-fb:NN ccm fir, but not a=rtcp-fb:NN nack pli. (Where NN is the payload type.) 3. Wait for loss on the stream being received by Chrome. What is the expected result? Chrome does not send PLI; instead it sends either NACK or FIR. What do you see instead? Chrome sometimes sends PLI anyway. What version of the product are you using? On what operating system? Chrome 57.0.2987.133; macOS 10.11.6. Please provide any additional information below.
,
Apr 24 2017
,
Apr 24 2017
,
Apr 24 2017
,
Apr 25 2017
jonathan.lennox42@ Could you please help us with the test url to verify this issue from TE-End. Thank You...
,
May 31 2017
Unfortunately our test environment is currently internal-only. I will see if I can get a version I can make public. I would imagine this could be tested by a mechanical stripping out of the "a=rtcp-fb:NN nack pli" from the SDP of one of the WebRTC examples, however.
,
May 31 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 5 2017
,
Jun 7 2017
I notice in the source that the RtpRtcp class has a SetKeyFrameRequestMethod, which can be set either to PLI or FIR, and by inspection it looks like ModuleRtpRtcpImpl would do the right thing if this were set to FIR. However, nothing ever calls this method.
,
Jul 11 2017
Changing component to "Video" for triage, as the "Network" category here only encompasses ICE/DTLS.
,
Aug 9 2017
,
Nov 21 2017
We have to integrate our webRTC Gw with a media server that only supports FIR. Do we have an idea when we plan on fixing this bug? Thanks, Luis
,
Nov 21
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 22
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by kjellander@chromium.org
, Apr 24 2017