IP cameras support
OpenVidu now allows you to connect RTSP IP cameras to your Rooms. This feature has been included in our custom fork of the Ingress module, which is used to ingest media into a Room. Check out how to do it here.
IP cameras support has also been included into the v2 compatibility module. This means that if your OpenVidu 2 application is using IP cameras, you can now upgrade your deployment to OpenVidu 3 and keep using this feature.
OpenVidu Updater
You can now update the version of your OpenVidu deployment very easily using our new OpenVidu Updater module. OpenVidu Updater will take care of the whole process, from stopping the services to updating the configuration files. It will also manage backups to allow rollbacks in case of any issue. You can update your OpenVidu deployment from 3.0.0 to 3.1.0:
- Update your OpenVidu On Premises deployment: Update OpenVidu Single Node, Update OpenVidu Elastic, Update OpenVidu High Availability.
- Update your OpenVidu AWS deployment: for AWS deployment we recommend updating from 3.0.0 to 3.1.0 by redeploying the CloudFormation. From 3.1.0 onwards OpenVidu Updater will also be able to seamlessly update your AWS deployment.
mediasoup stability
We believe we have now reached the right point of maturity to take mediasoup as the internal RTC engine from experimental to production ready. There are still some limitations to take into account, but the general stability of the system is now considered production ready.
Configuring mediasoup as the internal RTC engine, you can achive maximum performance in your video Rooms, reaching up to 2x overall capacity in your hardware.
v2 Compatibility bug fixes
There have been several improvements to the compatibility between OpenVidu v2 applications and OpenVidu v3 deployments:
REST API
- Field
clientDataof the Connection object wasn't being properly set. Now it is.
Webhook
- Webhook event
webrtcConnectionCreatedwasn't being sent when an audio-only Publisher published to the Session. Now it is.
openvidu-browser-v2compatibility
- Event
videoElementCreatedwasn't being triggered for Subscriber participants. Now it is. - Event
streamCreatedwasn't being triggered by the Session object for Streams coming from audio-only Publishers. Now it is. - Event
streamPropertyChangedwasn't being triggered when an audio-only Publisher muted/unmuted its audio. Now it is.
If you have implemented an OpenVidu v2 application, you can easily upgrade it to make it compatible with an OpenVidu v3 deployment, and take full advantage of this new and improved version of OpenVidu. Learn how to do so here.
What’s coming next?
Now that the stability of version 3 is complete, subsequent releases will become more frequent. In the coming weeks we will be working on:
- Integrating the use of AI agents into the platform, simplifying their use within Rooms as much as possible and providing a pool of out-of-the-box agents, as well as facilitating the integration of custom agents. The first of these will be a speech-to-text agent!
- Native deployments on Azure, just as we support native deployments on AWS.
- A high-level OpenVidu mode of operation, close to low-code, specifically focused on video conferencing use cases. In this way, we believe we can provide a very high quality product, extremely functional, highly maintainable and customizable, aimed at users or organizations that need a video conferencing solution without the need for a dedicated development team or large investment of resources.
