OpenVidu Enterprise general availability
OpenVidu Enterprise edition has gone from beta to production-ready. OpenVidu Enterprise brings the best performance, improved media quality and better scalability for high-demand environments. Any OpenVidu CE or OpenVidu Pro application will be compatible out-of-the-box with it. Take a look at what OpenVidu Enterprise has to offer: Documentation.
The transition from Beta to General Availability means the following limitations in OpenVidu Enterprise are now overcome:
- Recording now available for High Availability deployments
- OpenVidu Inspector is now available
- Full support for Simulcast. Check Simulcast documentation section to learn more.
- VP9 support thanks to mediasoup. Check our new Media Codecs documentation section to learn more.
Support for any S3 provider for storing recordings
If you want OpenVidu to automatically store your recordings in a separate storage service, now you are not limited to AWS S3. Any S3-compatible provider can be used. See documentation.
IP cameras now support RTSP over SSL
You can now publish IP cameras with
rtsps protocol. See documentation.
More flexible ICE configuration
Now it is very easy to configure external TURN servers in the client-side. You can:
- Configure globally any TURN server. See configuration property
- Set TURN credentials user by user from you application’s server. See parameter
customIceServerswhen creating a Connection.
Before, this was only possible using the client-side library openvidu-browser (with
OpenViduAdvancedConfiguration.iceServers property), which always required more work on the developer side and had some limitations.
Allow users behind strict firewalls
In some occasions users may be located behind strict firewalls that only allow connections though port 443 (for example, in restricted corporate networks). Now OpenVidu may be configured with external TURN servers to overcome these situations. You can use our brand new TURN server appliance that can be deployed externally, or use a third-party TURN SaaS. See documentation here.
Strictly typed openvidu-browser events for TypeScript projects
Event objects of openvidu-browser client library are now strictly typed in TypeScript. This has also greatly improved openvidu-browser documentation, centralizing all of the available events in interfaces. You have a complete description of all events in one place:
- openvidu-browser : LocalRecorder better management for long recordings.
- Monitoring - Elastic stack: summary objects were lacking property
media_node_id, that is used to identify the Media Node in which the object lived. This is now fixed and the property does actually exist.
There is a small breaking change affecting recording IDs. These IDs (and recording default names) are different for consecutive recordings of the same session. Before, they where built with the session ID, plus a hyphen (
-) and a number. For example, for three consecutive recordings of session
ses_ABCD, the recording IDs would be:
Now the hyphen has been replaced by a tilde (
~) due to new restrictions that have arisen. Now the recording IDs would be:
ses_ABCD~2. This should not really affect your application, unless you are explicitly assuming the existence of a hyphen in your own logic.