OpenVidu 2.14.0

New features

OpenVidu Call complete overhaul

  • Node backend added to make the app secure: OpenVidu Call didn’t have a backend, so OpenVidu secret needed to be included in the frontend code, making the app unsafe and not really prepared for a real production environment. Now OpenVidu Call has a simple Node backend, so any protected operation is now safely done in the server side.
  • Renewed landing page: the calling card of the application is its home page, and it has been redesigned with a better look-and-feel. Besides, now a random session name will be automatically generated for you to use it if you want.
Renovated OpenVidu Call landing page
  • Join a session without media devices: OpenVidu Call didn’t allow users join a session if they didn’t have a working camera and microphone. This proved to be too restrictive, so now users without media devices can still join a session to at least see and hear other participants.
  • Zoom in and zoom out in specific videos: users can now press a specific button available at the bottom right corner of each video to make it bigger or smaller in the layout. They can also full screen any video, or full screen the entire application if they want. All of this to ensure users focus their attention on what they prefer at all times.
  • Active speaker layout: a new option allows changing the main video to the active speaker automatically. This way the layout dynamically transforms to focus on the participant speaking, changing between participants as they take the floor. If any screen is being shared, this feature is disabled so as not to interfere with it.
  • Muted videos now won’t appear in the layout: users can mute their video whenever they want. Before, users would see a black square where the video used to be, which was inconvenient because some of the limited and valuable space was lost. Now any muted video will disappear from the layout.
  • New footer bar showing remote participants: at the bottom of the page users can see at a glance what other participants are connected to the session. This is especially useful now that users without a camera may join a session, as well as muted videos not showing up in the layout.
Participant summary always visible at the footer
  • Chat messages notification: we noticed that many times chat messages went unnoticed without a proper notification. Now a subtle notification will be shown when a new chat message is received.
Chat message displaying a notification
  • Reconnection alerts: OpenVidu 2.12.0 introduced automatic reconnection features for users losing their network connection while connected to a session. Now OpenVidu Call takes advantage of reconnection events and will warn the user in case they experience a network drop.
  • Smooth track replace when screen sharing: OpenVidu Call now uses the replaceTrack feature to provide a quicker and smoother transition whenever a user changes the screen being shared.

Change the port where OpenVidu is deployed

Limit connections to OpenVidu admin services to specific IPs

  • A)ALLOWED_ACCESS_TO_DASHBOARD : limits the ability to connect to OpenVidu CE dashboard and to OpenVidu PRO Inspector.
  • B)ALLOWED_ACCESS_TO_RESTAPI : limits the ability to consume OpenVidu REST API (both CE and PRO).

New automated upgrade process

Samsung Internet Browser supported in Android

New region for OpenVidu AWS deployments

New Kurento 6.13.2

Bug fixes

  • openvidu-server: possible avoidable exception when adding IceCandidates to recently created Subscriber WebRTC endpoints, for which sometimes an IceCandidate could arrive before the WebRtcEndpoint object is available for the Java code. Now accumulated IceCandidates are always added after the WebRtcEndpoint object is defined and available (issue 455)
  • openvidu-server: recordings bigger than 2.1 GB were throwing an exception when generating their metadata during their stop process. Now they don’t.
  • openvidu-browser: there was a memory leak in entities inheriting from interface EventDispatcher. This is fixed now (PR 437).
  • openvidu-browser: OpenVidu.enableProdMode was disabling all logging of browser. Now only disables openvidu-browser library log (issue 440).
  • openvidu-browser: fix when providing MediaStreamTracks as audioSource or videoSource when calling OpenVidu.initPublisher. Where being used when calling OpenVidu.getUserMedia, but not for OpenVidu.initPublisher (issue 456).
  • OpenVidu Pro: restarting OpenVidu Pro from Inspector or REST API may failed for AWS deployments due to a problem with system path. Now it doesn’t.
  • Installation process: more checks have been added to the production deployment script and the logging of the process has been improved to facilitate the correct installation and handling of possible errors when deploying OpenVidu.

Stay tuned for next iterations! You can follow us on Twitter and a Star in GitHub is always welcome :)




Easy videoconference in your web or mobile app

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The Journey through the Obstacle Course

Esquare — Responsive WordPress Blog Theme


CSS Alignment Made Simple

Configure an Android simulator to connect with Burp Suite Proxy

How I Use Git Branches in My Projects

Branching train tracks and electricity wires

Page builders might not be a good idea

Serverless Computing in a Nutshell

what happens when you type “” into your browser and hit enter?

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Easy videoconference in your web or mobile app

More from Medium

Build and Deploy your free 20GB Oracle Autonomous Database with NodeJS 1/2

Node-RED with Qubitro

Create an API Rest With NestJS and PostgreSQL

Sonoff IoT API’s