I need your help to gain better visibility.
If you are developing something with WebRTC, there’s a good chance you are using existing tools and frameworks already. Be it signaling or messaging frameworks, a media engine in the backend, a third party mobile library.
As I work on my research around the tools enabling the vibrant ecosystem that is WebRTC, I find myself more than once wondering about a specific tool – how much is it used? What do people think about? Are they happy with it? What are its limitations? While I know the answers in some cases, in others not so much. This is where you come in.
If you are willing to share your story with a third party tool – one you purchased or an open source one – I’d like to hear about it. Even if it is only the name of the tool or a one liner.
Example: WebRTC Leak Test
Feel free to comment below or just use my contact form if you wish this to stay private between us.
I really appreciate your help in this.
I use socket.io for signalling and use rfc5766 as turn server. We have plans to use MCU later. For now, it is all we need for our application.
Thanks for sharing Sojharo!
I found out that the licode project does not support video manipulations (can’t combine steams or make modifications at real time).
we use frozen mountain(icelink, websync).
with callstats.io for monitoring, and evaluating testrtc for capacity tests.
I took the challenge to write my own signalling server and hosting it on IIS with websocket feature added.
We use PeerJS for live video/audio talk between chatters at http://www.rumbletalk.com .
It is one on one calls and the PeerJS works perfectly with thousands of live calls a day.