Version 20.1.0 GA

What's new in this release?

  • VidyoPortal support for Safari as a WebRTC browser
  • Along with the Chrome and Firefox browsers, the VidyoPortal now recognizes Safari as a supported WebRTC browser.
  • VidyoConnect desktop users can log in and join calls with WebRTC when using Safari on macOS.
  • Your WebRTC cluster must be upgraded to 20.1.0 or later to use this; consequently,Safari support is not enabled by default. If you are interested in this feature, contact Vidyo Support and they can advise you based on your deployment.
  • Update for Epic Context-Aware Linking (CAL) Users
  • When a user who does not yet have the VidyoConnect desktop application installed clicks an Epic CAL link to a meeting, that user will no longer automatically join the meeting after the VidyoConnect installation is completed.
  • Instead, after installation, the VidyoConnect desktop application will display this message: "Please go back to the browser to restart the page with room link".
  • Note: You must upgrade to version 20.1.2 or later of the VidyoConnect desktop application in order for this update to take effect.
  • Important bug fixes
  • In this release, we've addressed some important issues to improve usability and reliability.
  • System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
  • The default MTU size has been changed to 1460 to address network overhead in some virtualized environments.
  • Logging has been improved for multiple components.

Important changes and new requirements

  • VidyoPortal VE version 19.2.0 and later requires 12GB memory allocation at a minimum for production use. Prior versions only required 8GB of memory.
  • ACTION TO TAKE: Make sure to review your configuration and adjust the memory allocation if necessary.
  • VidyoPortal version 20.2.x and later requires you to set the SOAPAction header for all SOAP requests; otherwise, requests may fail.
  • ACTIONS TO TAKE: Inspect any API integrations that may use the Vidyo Web Services APIs and validate that this header is appropriately set. We also highly recommend that you test any API integrations in a lab environment prior to upgrading to your production environment.
  • VidyoGateway versions 3.5.x and VidyoReplay versions 3.1.x do not work with VidyoPortal and VidyoRouter version 21.6.x. You must upgrade your VidyoGateway and/or VidyoReplay to version 20.2.0 or later in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later.

Important notes

  • You can only upgrade to VidyoPortal and VidyoRouter version 21.6.8 from version 19.2.0 or later. You cannot upgrade directly from any previous versions as these versions are not supported.
  • DO NOT reboot your system during the upgrade as this could result in permanent loss of data.
  • ACTION TO TAKE: As with any major update, we highly recommend that you back up your database before upgrading.
  • If you are using VidyoPortal and VidyoRouter Virtual Edition (VE), we recommend that you take a full system snapshot prior to upgrading.

Files

Files

This file...

Is for...

vidyoportal-TAG_VC20_1_0_0184-bundle-v2504.vidyo

VidyoPortal version 19.2.0 or later

vidyorouter-TAG_VC20_1_0_0184-bundle-v2505.vidyo

VidyoRouter version 19.2.0 or later

Resolved issues

The following table lists the issues we have resolved in VidyoPortal and VidyoRouter version 20.1.0.

VidyoPortal and VidyoRouter version 20.1.0 - resolved issues

Key

Summary

VPTL-10441

Fixed an issue when clicking an Epic CAL link and the client was downloaded for the first time via a CDN, the Epic CAL parameter was not always passed.

VPTL-10371

Fixed an issue where an empty notification was sent to the Epic Interconnect server if the extData had spaces between the field names.

VPTL-10354

Fixed an issue where VidyoRouters could crash during an upgrade of the VidyoPortal.

VPTL-10343 and VPTL-10275

An issue was resolved where, when using Epic, the HTTP 400 LOCK-FAILED error message was returned when a Disconnect message was received with no corresponding Connect message. Starting with this release, the error message returned will now be 400 USER-NOT-CONNECTED.

VPTL-10318

An issue was fixed for Safari on iOS 13+ where the join parameters were missing from the downloaded file for the VidyoConnect desktop application.

VPTL-10317

Fixed an issue where the desktop UI was incorrectly displayed on an iPad in some cases.

VPTL-10309

An issue where Epic CAL notifications were sent out with a two- to five-minute delay has been resolved.

VPTL-10252

An issue was resolved where the Interconnect server locked accounts after several incorrect password retries.

VPTL-10250

An issue where the CDR was not generated on joinConference in the CONNECTING state has been fixed.

VPTL-10224 and VPTL-10223

The VidyoConnect mobile application for Android and iOS now both consistently have a "Join via the app" button and a "Join via the browser" button.

VPTL-10204

An issue was fixed where when sending status notifications (REST or SOAP), if there was a non-HTTP error message, the process could occasionally stop.

VPTL-10188

VidyoConnect for WebRTC labels are now localized.

VPTL-10145

Fixed an issue where changing the “Web SSL/TLS Settings” mode did not always get applied successfully.

VPTL-10131

Fixed an issue where access to the Client Installations table was no longer allowed from the CDR access user.

VPTL-10130

Fixed an issue where under certain load patterns with low memory, the underlying OS (kernel) would become non-responsive.

VPTL-10092

A memory issue was fixed to improve usability and performance.

VPTL-9975

Fixed an issue where localization for certain fields in the Super and Tenant Admin were missing.

VPTL-9919

Fixed an issue where a valid email address with consecutive special characters was not allowed.

VPTL-9449

Fixed an issue where when creating a Public Room via VidyoConnect would fail if it was similar to a previously existing room.

VPTL-7688

Fixed a UI inconsistency where the “Allowed to log in to user portal” was not clickable in certain cases.

Known issues

There are no new known issues for this release.