34 ms·
I rolled https://video.etherpad.org https://video.etherpad.org out within 5 minutes. It's a single command once Etherpad is installed (npm install ep_webrtc).
by Johnyma22 7y ago
I rolled https://video.etherpad.org https://video.etherpad.org out within 5 minutes. It's a single command once Etherpad is installed (npm install ep_webrtc).
There is one complication most people don't realize -- Failed Reverse NAT traversal: For this you need a TURN server (I'm intentionally ignoring STUN for obvious reasons).
TURN servers have to route the actual media (video / audio) from user a <> b <> c but only if the user(s) can't directly connect. We hit Tb's a day through our TURN server and it gets expensive.
But complexity wise, it's an absolute doddle! Give it a go, if you have nodejs installed 90% of your work is done!
- girvo 7y agoSilly question, because I tried to run Nextcloud Talk and ran into odd connection issues for a user who I believe is behind a corporate firewall and so I needed to stand up “coturn”: what’s the obvious reason for avoiding STUN? And what would you recommend as the simplest/best TURN server implementation?
- lioeters 7y agoThank you for mentioning it. Found the source (no dependencies!) at https://github.com/ether/ep_webrtc https://github.com/ether/ep_webrtc
- miyuru 7y agoif there is an NAT problem, why dont you add IPv6 support? It will solve that problem to at least some users. Your site is currently down, but it does does not show a AAAA record for video.etherpad.org
- EGreg 7y agoThe edge cases are hard. Like SDP offers between browsers which support different codecs.