I wonder how these compare to Jitsi and BigBlueButton. I've been using the hosted Jitsi instance at "meet.jit.si" and have been self-hosting bigbluebutton and both have been rock solid.
The problem with all of these is that different browsers such as firefox and safari have trouble with negotiating connections.<p>For example we built the software we use on <a href="https://intercoin.org/meeting" rel="nofollow">https://intercoin.org/meeting</a> or any website. It works across safari on ios and chrome and we even made a workaround for webviews:<p><a href="https://mobile.twitter.com/qbixapps/status/1156484156425039872" rel="nofollow">https://mobile.twitter.com/qbixapps/status/11564841564250398...</a><p>But the sdp connections between the browsers fail and A can hear B but C can’t. Weird.<p>Zoom or Google Hangouts doesn’t have such issues because they always assume one specific environment. Cross browser videoconferencing is not easy<p>But hey ours is open source and not locked into Twilio or these guys:<p><a href="https://github.com/Qbix/Platform" rel="nofollow">https://github.com/Qbix/Platform</a><p>Search for the string WebRTC
This looks perfect for a project I've been planning for a while, but the way the pricing works seems dangerous to base a small company on. They're pricing it per minute per core (even if idle), as if it's a service - except that they're not providing the service, I am. I'd much rather pay a flat fee than never know how much I'll have to pay.<p>If they want to charge for use, fine, charge ACTIVE time, not UPtime. Running a single dual-core EC2 instance should be no different than running a 10-core dedicated server at 20% load.
Hi there, I'm Juan, main developer of Kurento Media Server. I'll try to contextualize here what is OpenVidu and where it comes from.<p>Kurento [1] is a WebRTC server which you deploy in your cloud and then control through another application server, of which OpenVidu is one. While Kurento tries to provide generic building blocks to allow creating multiple types of applications, OpenVidu started as a project that builds on top of those capabilities and focuses on the most commonly requested use case: videoconference rooms.<p>From that initial premise, the amount of tasks to do in order to achieve a professional solution seems endless: easy configuration of producers and consumers, with roles and permissions; automatic scaling when the load requires it; dynamic distribution of media flows according to the needs; recording of the sessions; compatibility with different browsers, and also why not, with apps on mobile platforms; filtering the media to apply video effects; the list goes on.<p>Then, problems will happen. And troubleshooting WebRTC issues is difficult, because information is all disperse and nebulous, so one is expected to have all the tools in place beforehand to inspect logs and be able to have an explanation of why something went bad.<p>OpenVidu aims to provide an easy to use framework that can cover all those needs and then some. Its open-source part covers all the basics, and for the last months we've been working on the Pro offering, which tackles the targets of automatic scalability, session monitoring, and automatic instantiation of Kurento Media Server nodes to handle different amounts of sessions (i.e. "elasticity"), among other things. Some of the features listed in the Pro page [2] are ready for prime time, and some are a work in progress.<p>We just released OpenVidu version 2.12.0 [3], which is where a new license version for the Pro tier sees the light. Our team has been for quite a long time in the game of WebRTC, working and learning together with the open-source community while developing Kurento, and now I hope you find that OpenVidu is a nice value proposition and it helps you build your dream application!<p>It's late here but tomorrow morning I'll be hanging around here to answer any questions. See you!<p>[1]: <a href="https://www.kurento.org/" rel="nofollow">https://www.kurento.org/</a><p>[2]: <a href="https://openvidu.io/docs/openvidu-pro/" rel="nofollow">https://openvidu.io/docs/openvidu-pro/</a><p>[3]: <a href="https://medium.com/@openvidu/openvidu-2-12-0-a-new-chapter-for-openvidu-d31c78d22857" rel="nofollow">https://medium.com/@openvidu/openvidu-2-12-0-a-new-chapter-f...</a>
Another interesting open source software is Jami <a href="https://jami.net/" rel="nofollow">https://jami.net/</a><p>I'm using it and I'm quite happy with it.