I rolled 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!
Silly 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?
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!