These are chat archives for andyet/SimpleWebRTC

17th
May 2018
Philipp Hancke
@fippo
May 17 2018 12:08
@myxoh you will need a turn server, without it you will get around 20% failures.
Nicolas Klein
@myxoh
May 17 2018 13:50
Thanks @fippo! That's news (and sad news) to me.
So you guys have a general approach to make sure you have no delay turn servers for every regional location? Would I need to provide an array of turn server ips or how do you guys generally handle this scenario?
We need to make sure we are not rerouting two peers on the same region through some turn on the other side of the world
Nicolas Klein
@myxoh
May 17 2018 13:55
(Also if you know any commercial turn servers running across regions that you can recommend)?
Philipp Hancke
@fippo
May 17 2018 14:12
the typical approach if you want to do it yourself is to use region-based dns like aws route 53. you just give a single dns name to the peerconnection
both tokbox and twilio offer TURN as a service. even though I am amused that twilio seems to run all its european turn server in ireland which costs them a few milliseconds
Nicolas Klein
@myxoh
May 17 2018 14:18
I'll look more into that, thanks for the support @fippo!
jcortesebustos
@jcortesebustos
May 17 2018 16:34
hey!
it's socket.io server down?
take a look to this: RTCPeerConnection constructor passed invalid RTCConfiguration - malformed URI: $STUNSERVER_URL
edtarber
@edtarber
May 17 2018 21:15
got the same problem, always getting the following error: simplewebrtc-v3.js:7871 Uncaught DOMException: Failed to construct 'RTCPeerConnection': '$STUNSERVER_URL' is not a valid URL.
but signaling server seems to work: https://sandbox.simplewebrtc.com/socket.io/
edtarber
@edtarber
May 17 2018 21:37
addition: it seems to be a problem with the signaling server ... I did overwrite the $STUNSERVER_URL and got a working connection between peers, but this connection only lasts a couple of seconds and is then interrupted