Avatar for Username

搜尋 Mozilla 技術支援網站

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

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

While using WEBRTC, I am unable to get Firefox browsers on seperate networks to connect. I suspect there is an ICE agent issues with FF.

  • 1 回覆
  • 4 有這個問題
  • 4 次檢視
  • 最近回覆由 philipp

kbrooking
kbrooking
more options

I'm developing an application using WebRTC and Data channels. I have no problem connecting data channels in chrome browsers across separate networks but, unable to connect data channels in Firefox browsers across separate networks. I always get iceConnectionState failed. I'm parsing the ICE candidate information from the SDP's 'a=' record after issuing a peerConn.createOffer. I then send this ICE candidate data across the signaling channel. Upon receiving the ICE candidate information on the receiving end I perform peerConn.addIceCandidate(candidate). However, nothing I have tried for the past several days is allowing the two Firefox browsers to connect the datachannels via WebRTC. I am however able to make the same code work across two Firefox browsers if they are both on the same network.

I'm developing an application using WebRTC and Data channels. I have no problem connecting data channels in chrome browsers across separate networks but, unable to connect data channels in Firefox browsers across separate networks. I always get iceConnectionState failed. I'm parsing the ICE candidate information from the SDP's 'a=' record after issuing a peerConn.createOffer. I then send this ICE candidate data across the signaling channel. Upon receiving the ICE candidate information on the receiving end I perform peerConn.addIceCandidate(candidate). However, nothing I have tried for the past several days is allowing the two Firefox browsers to connect the datachannels via WebRTC. I am however able to make the same code work across two Firefox browsers if they are both on the same network.

所有回覆 (1)

philipp
philipp
  • Moderator
more options

hello kbrooking, this here is i primarily user-driven support forum, so i'm not sure if we could come up with a solution for this issue. if it's something reproducible, then i'd recommend filing a bug at bugzilla.mozilla.org - there it will get the attention of developers. thank you!