This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

turn server

  • 1 reply
  • 4 have this problem
  • 10 views
  • Last reply by philipp

theAnonymous
theAnonymous
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.

All Replies (1)

philipp
philipp
  • Moderator
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.