znerol

> STUN is used to figure out if TURN is needed or not. You'll want to avoid using TCP over TURN if it is not necessary. True. However, TURN is...

Screenshot of the Firefox console warnig I was referring to: 

@basisbit is there a chance that this gets merged at some point? Do you need more information on the subject? Otherwise I'll close this PR.

I'm using it in production with Chromiums, Firefoxes and Safaris.

Btw, you can also check what other applications are doing by pulling up `about:webrtc` in Firefox and then look for `iceServers`. E.g., meet.jit.si only specifies *one* turn URL: ``` iceServers:...

> If you do not set a STUN entry in the stun: dictionaries, the browser won't generate srflx candidates. I've actually tested this. Both, Chromium and Firefox *do* generate srflx...

> You're actually suggesting to include a turn:3478 UDP (which does generate srflxs and udp relays) endpoint in place of the STUN entry and the turn:443-tcp on the server rather...

@ffdixon there seems to be a misunderstanding here. Kurento can use `coturn` in two different ways. Either `stunServerAddress` and `stunServerPort` can be configured. In that case there is no authentication...

Thanks for filing this PR. Honestly, I'm on the edge on this one. The [Prometheus Default port allocations](https://github.com/prometheus/prometheus/wiki/Default-port-allocations) wiki page currently lists two existing ZFS exporters. It isn't unlikely that...

I'm observing that too. In my case it would be perfect if `mc` would exit with a non-zero status code if the connection to the bucket is lost. Browsing through...