Hacker News new | ask | show | jobs
by xrjn 3258 days ago
We recently started using WebRTC to transmit video from Raspberry Pi's where I work. There were a lot of gotchas that weren't obvious to someone who's never worked with VOIP or related technology: STUN and TURN servers[0], 300 seconds idle timeouts that shouldn't affect the connection but killed the video stream regardless, and dropped calls which forced us to reboot the Pi.

In the end we managed to get something smooth working with UV4L[1] on a RPi costing us a fraction of the previous solution.

[0] http://numb.viagenie.ca/ has a free one

[1] https://www.linux-projects.org/

1 comments

If your devices have real IP connectivity, you can skip TURN/STUN.
Do you still need a server for signaling or is it actually P2P at that point?
There needs to be some mechanism to tell you what the other P2P endpoints are and what address/port pairs they are listening to. It doesn't have to be a server necessarily, could be just a copy-paste string.