Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

turn server

  • 1 antwoord
  • 4 hebben dit probleem
  • 10 weergaven
  • Laatste antwoord van philipp

more options

Web RTC in a Symmetric NAT situation does not work on FF, Aurora and Nightly because TURN is not supported/buggy.

I have tried setting media.peerconnection.turn.disable flag at "about:config" for both peers to true, however it does not solve it.

To reproduce it, go to apprtc.appspot.com using the 3 browsers and try to join using another peer on a different network using one of the browsers mentioned.

The Web RTC reference application only works as intended if and only if the peers are on the same network. On Wireshark logs, I do not see TURN requests to any TURN server.

The Web application works perfectly on Chrome.

Web RTC in a Symmetric NAT situation does not work on FF, Aurora and Nightly because TURN is not supported/buggy. I have tried setting media.peerconnection.turn.disable flag at "about:config" for both peers to true, however it does not solve it. To reproduce it, go to apprtc.appspot.com using the 3 browsers and try to join using another peer on a different network using one of the browsers mentioned. The Web RTC reference application only works as intended if and only if the peers are on the same network. On Wireshark logs, I do not see TURN requests to any TURN server. The Web application works perfectly on Chrome.

Alle antwoorden (1)

more options

hello, thanks for reporting that issue - coming up with a solution to that is probably beyond the capabilities of this (primarily user/volunteer-run) forum. i'd recommend to file a bug for it at bugzilla.mozilla.org, then the issue should get the attention of developers who can come up with a fix.