Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

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.

Valgt løsning

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.

Læs dette svar i sammenhæng 👍 1

Alle svar (2)

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

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

Ændret af cor-el den

Robert Kirnum
Robert Kirnum Spørgsmålsstiller
more options

Valgt løsning

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.