Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

Is it possible to disable VP8 error concealment for WebRTC?

Robert Kirnum
Robert Kirnum
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)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Maybe check out the Firefox source code about rtcp-fb nack.

글쓴이 cor-el 수정일시

Robert Kirnum
Robert Kirnum 질문자
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.