Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

turn server

  • 1 antwurd
  • 4 hawwe dit probleem
  • 10 werjeftes
  • Lêste antwurd fan 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 antwurden (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.