Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

webrtc SDP re-negotiation(reoffer/answer) fails in mozilla

  • 2 respostas
  • 3 têm este problema
  • 7 visualizações
  • Última resposta de prasad.dp5

more options

I have written a webrtc client in which re-negotiation(re-offer/answer) is required after call gets established. Scenarios such as 1) upgrade calls from audio to video 2)Downgrade call from video to audio 3)Hold the established call 4) Retrieve the held call

I see mozilla/firefox has issues with re-negotiation of SDP( it fails in setting remote description). Any idea why is this a constraint in Mozilla and has no issues with Chrome.

I have written a webrtc client in which re-negotiation(re-offer/answer) is required after call gets established. Scenarios such as 1) upgrade calls from audio to video 2)Downgrade call from video to audio 3)Hold the established call 4) Retrieve the held call I see mozilla/firefox has issues with re-negotiation of SDP( it fails in setting remote description). Any idea why is this a constraint in Mozilla and has no issues with Chrome.

Todas as respostas (2)

more options

https://developer.mozilla.org/en-US/d.../WebRTC_basics

Are you taking about the state change?: https://developer.mozilla.org/en-US/d.../RTCPeerConnection.onsignalingstatechange

Are you establishing a new connection then tearing down the old one as renegotiating, or are you reusing the existing stream? [Bug 834038 - SDP renegotiation should re-use existing streams when possible]

more options

Yes, I was referring to statechange. I am re-using the same stream on same peerconnection object.

Problem still persists.