Partners Blog Contact Us

VidyoClient for WebRTC JavaScript Library (3.x Adapter): Releases


This article describes the new features, functionality, and resolved issues for each of the VidyoClient for WebRTC JavaScript Library: 3.x Adapter releases beginning in 2020 (subsequent to the VidyoClient API 3.x releases). 

2020 Releases


2020 Releases


VidyoClient for WebRTC JavaScript Library: 3.x Adapter 20.3.1—Aug 2021

What's new in this release

  • Enables unified plan support on Google Chrome 93+
There are no resolved or known issues in this release.


VidyoClient for WebRTC JavaScript Libary: 3.x Adapter 

What's New in This Release

  • Resolved Browser Compatibility Issue
    • In this release, Enghouse Vidyo resolved an issue where customers using custom applications built with VidyoClient™ JavaScript Library version 3.x for WebRTC can join calls while using Google Chrome™ version 85 or Firefox® version 78 and later.
    • Prior to this release, customers had issue joining calls, staying connected after joining a call, and  timeout errors.  
    • This issue specifically impacted the following customers/platforms: 
      • VidyoWorks™
      • VidyoWorks Health
      • On-premises customers.
  • Requirements for This Release
    • Deploy Version 19.2.0 VidyoServer for WebRTC (OVA)
      • Deploy a new Vidyo Server for WebRTC (transcoded) .OVA file version 19.2.0. To access this file, please contact your local support location as listed in this Contact Us article.   

        NOTE: You cannot upgrade your existing Vidyo Server for WebRTC version 3.x.  Instead, you must create a new transcoding server cluster.  With this new deployment, you may use the same FQDNs as your existing cluster. However, if you use different FQDNs, you will need to update the reference in your application(s) to this new cluster. 
      • Helpful Articles
    • Update Your Application
      • You must update your application to use a new VidyoClient for WebRTC Javascript library: 3.x Adapter. You can access this file from the VidyoWorks (3.x) API Downloads page.  Based on your deployment, you can either update your application with the VidyoCloud Hosted Helper files, or the Self-Host the Helper files. 
      • VidyoCloud Hosted Helper Files
        • In your application, you must replace the vidyo.client.js file with the version 20.3.0 of the 3.x Adapter. The vidyo.client.js library automatically loads the following additional helper JavaScript files:
          • 4.x.plugin.js
          • VidyoClientDispatcher.js
          • VidyoClientTransportWebRTC.js
        • By default, these files are retrieved and loaded from a VidyoCloud hosted server during initialization. If you would like to self-host these files, see below.
      • Self-Hosted Helper Files
        • Similar to above, you must replace the vidyo.client.js file with the version 20.3.0 of the 3.x Adapter. However, if you would like to self-host the dynamically loaded helper files, you must directly pass the following parameters into the configuration object: 
          • LoadLocalJSLibtrue 
          • LocalJSLibRelativePathpathtodir 
            • Refer to the below example:

              let vcconfig = {
              loadLocalJSLib : true,
              localJSLibRelativePath : `${getWebAppPath()}/scripts/vidyowebrtc`
              //vcconfig=null;//picking latest package from static server
              if (getVidyoClient().start(vcconfig)) {


  • Notable Changes
    • WebRTC Server Session Timeout 
      • When using the previous 3.x version of the Vidyo Server for WebRTC, the server maintained a connection for as long as the library remained initialized and connected with the session manager.
      • When using the current WebRTC server version 19.2.x or later, the server is optimized to ensure no connection takes away from the overall capacity and so after ~15 minutes of inactivity the connection is torn down.
      • Therefore, when going through the VidyoClient for WebRTC JavaScript Libary: 3.x Adapter, if any application initializes the library, remains idle and does not join a call for more than 15 minutes a failed connect can result if there is an attempt by the client to try to join a call.
      • In such a situation, with the latest VidyoClient for WebRTC JavaScript Libary: 3.x Adapter update, the application will have to reinitialize itself before the session times out.
    • Important Considerations 
      • The VidyoClient for WebRTC JavaScript Libary: 3.x Adapter does not support these   features at this time.
        • Private Chat
        • Lecture Mode and Presenter Mode
        • Multi-Share


Resolved Issues

The following table lists the resolved issue in VidyoClient for WebRTC JavaScript Library: 3.x Adapter version 20.3.0:

VidyoClient for WebRTC JavaScript Library: 3.x Adapter Version 20.3.0 - Resolved Issues

Key Summary


Enghouse Vidyo fixed issues affecting VidyoClient for WebRTC JavaScript Libary: 3.x Adapter users who had issues joining calls and staying connected to calls while using Google Chrome version 85 and Firefox version 78 and later. 


Known Issues

The following table lists the known issues in VidyoClient for WebRTC JavaScript Library: 3.x Adapter version 20.3.0:

VidyoClient for WebRTC JavaScript Library: 3.x Adapter Version 20.3.0 - Known Issues

Key Summary


The VidyoClient for WebRTC 3.x adapter no longer uses or needs the Chrome Extension in order to share content; instead, it uses the native browser API to start sharing. Therefore, if you plan to support sharing, update your app as needed. 


No error message displays when a user is dropped from a call due to loss of the network connection.  


When video from a mobile participant is viewed, the video may appear cropped. For example, certain CSS styles on the video element could cause a portrait-oriented video to get cropped. If this occurs, consider updating the CSS style of the video element.
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.