Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

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

  • 2 Mbohovái
  • 3 oguereko ko apañuãi
  • 2 Hecha
  • Mbohovái ipaháva prasad.dp5

prasad.dp5
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.

Opaite Mbohovái (2)

guigs
guigs
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]

prasad.dp5
prasad.dp5 Porandu apoha
more options

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

Problem still persists.