Quote:
Originally Posted by Barry-xlovecam
The problem with WebRTC is routing the NAT translations you need TURN and STUN servers like SIP (VOIP). Browser to browser is easy -- multi viewers becomes an issue.
The are quite a few SaaS PSaaS solutions but they ban anything related to pornography or explict/adult webcam use.
Even with source code you would need a to understand the TURN and STUN server protocols as well as using Nginx as a reverse proxy for Node.js < application server.
|
Hey Barry, I agree that there are complexities in using WebRTC (if you previously used flash). Where in flash you just needed to hook up a media server (wowza, red5, etc.) on a single IP, with WebRTC, because of it's peer to peer nature, you'll likely use some signalling over websockets, IP discovery using STUN and TRUN and will need about a half dozen ports.
So yes, there are complexities, but nothing that should stop people from adopting the technology.
It's a shame that Kurento (open source WebRTC server) is no longer a viable solution.
With regards to modelnet's offering, it isn't really what I'm after. I am specifically looking for a community chat application that allows audio/video communication.
Edited to add: I've not looked into this in any detail, but jitsi seems to be a stable option for a video conference server.