We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

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 wotmołwa
  • 4 maja tutón problem
  • 4 napohlady
  • Poslednja wotmołwa wot 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.

Wšě wotmołwy (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!