為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Is it possible to disable VP8 error concealment for WebRTC?

more options

Chrome appears to disable VP8 error concealment when rtcp-fb nack is negotiated when setting up a connection (SIP / SDP). I have not been able to get Firefox to disable error concealment. I am also unable get Firefox to enable rtcp-fb nack though I am not certain this will disable VP8 error concealment as on Chrome.

Chrome appears to disable VP8 error concealment when rtcp-fb nack is negotiated when setting up a connection (SIP / SDP). I have not been able to get Firefox to disable error concealment. I am also unable get Firefox to enable rtcp-fb nack though I am not certain this will disable VP8 error concealment as on Chrome.

被選擇的解決方法

From http://www.ietf.org/rfc/rfc2327.txt SDP: Session Description Protocol

6. SDP Specification

  Text records such as the session name and information are bytes
  strings which may contain any byte with the exceptions of 0x00 (Nul),
  0x0a (ASCII newline) and 0x0d (ASCII carriage return).  The sequence
  CRLF (0x0d0a) is used to end a record, although parsers should be
  tolerant and also accept records terminated with a single newline
  character.  By default these byte strings contain ISO-10646
  characters in UTF-8 encoding, but this default may be changed using
  the `charset' attribute.

Looks like the Firefox SDP parser requires a carriage return ('\r'), it is unable to process attributes ending in just a newline ('\n'). I guess the RFC does indicate SHOULD as opposed to SHALL.

從原來的回覆中察看解決方案 👍 1

所有回覆 (2)

more options

由 cor-el 於 修改

more options

選擇的解決方法

From http://www.ietf.org/rfc/rfc2327.txt SDP: Session Description Protocol

6. SDP Specification

  Text records such as the session name and information are bytes
  strings which may contain any byte with the exceptions of 0x00 (Nul),
  0x0a (ASCII newline) and 0x0d (ASCII carriage return).  The sequence
  CRLF (0x0d0a) is used to end a record, although parsers should be
  tolerant and also accept records terminated with a single newline
  character.  By default these byte strings contain ISO-10646
  characters in UTF-8 encoding, but this default may be changed using
  the `charset' attribute.

Looks like the Firefox SDP parser requires a carriage return ('\r'), it is unable to process attributes ending in just a newline ('\n'). I guess the RFC does indicate SHOULD as opposed to SHALL.