Version 19.3.0 GA

What's new in this release?

  • Vidyo's Epic Context-Aware Linking (CAL) integration now available in Epic's App Orchard Marketplace
  • Starting with the Epic February 2019 release, Epic requires the inclusion of an Epic-Client-ID for all third-party integrations that use their APIs. 
  • In order to support Epic's new requirements, Enghouse Vidyo has obtained its own unique Epic-Client-ID and enrolled the Vidyo Context-Aware-Linking (CAL) integration app in Epic's App Orchard marketplace. 
  • Starting with this release, the Epic CAL integration will support sending the Epic-Client-ID whenever the SetExternalConnectionStatus API is called.
  • To ensure that your cloud or on-premises CAL deployment will continue to work successfully with the Epic February 2019 release, you must:
  • Contact your Epic representative to obtain access to Epic’s App Orchard marketplace.
  • Contact Vidyo Sales or your Vidyo account representative once you have requested Vidyo's CAL app via the App Orchard site.
  • Refer to the following articles:
  • Epic Compatibility with Vidyo Infrastructure to verify compatibility between your Epic and Vidyo versions.
  • Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) to configure your Epic CAL integration using the Super Admin and Tenant Admin portals.
  • New connection test for configuring the Epic Interconnect Server
  • Enables administrators to more quickly identify and resolve Epic CAL configuration issues.
  • Generate helpful HTTP status notifications such as 408 - Request Timeout, 404 - Not Found, and 401 - Bad Credentials.
  • Use this information to debug Epic CAL configuration issues.
  • Sample URL generator for test calls
  • Helps administrators easily conduct test calls.
  • Generate sample Epic CAL URL links and use the links to:
  • Join test calls.
  • Compare the sample URL extData with the extData generated from Epic.
  • Multi-server Epic Interconnect support With a single tenant
  • Configure multiple Epic Interconnect servers on a single Vidyo tenant by using an "orgID" to differentiate each server. 
  • Simplify your Epic CAL configuration, especially if you’re a healthcare entity with multiple Epic installations due to mergers, etc.
  • Reduce the costs associated with maintaining multiple environments.
  • Ability to select the Epic mode required
  • Set your Epic CAL integration to Production, Test, or Legacy mode:
  • Select Production when configuring and deploying in a production environment.
  • Select Test when configuring a lab environment.
  • Select Legacy when debugging and using systems running versions earlier than Epic February 2019.
  • API usage reports
  • Download CSV files with data about usage of the SetExternalConnectionStatus API with your Epic Interconnect Server.
  • Select the start date and end date for each report.
  • Additional REST API for Epic CAL
  • Programmatically invoke the CAL workflow for embedded applications.
  • Per-tenant status notifications for third-party integrations
  • Simple REST/JSON format for lightweight processing.
  • Receive rich status notification messages for:
  • Login and logout user events
  • Join and leave conference events
  • Epic CAL events
  • Updated landing pages for iPadOS and macOS Catalina
  • The most recent version of Safari for iPadOS and macOS Catalina advertises the same user-agent. Therefore, the VidyoPortal cannot determine if an iPad or a desktop are connecting.
  • To remedy this issue, VidyoPortal version 19.3.0 provides landing pages that allow the user to select the device with which to join conferences or download the app.
  • 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.

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-19.3.0.335-bundle-v2208c.vidyo

VidyoPortal version 19.3.0 or later

vidyoRouter-19.3.0.335-bundle-v2210c.vidyo

VidyoRouter version 19.3.0 or later

Resolved issues

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

VidyoPortal and VidyoRouter version 19.3.0 - resolved issues

Key

Summary

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-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-10092

A memory issue was fixed to improve usability and performance.

VPTL-9952

An issue was fixed for a MySQL schema error that could occur after upgrade.  

VPTL-9731

An issue was corrected where when a user force quits a conference call and then rejoins the conference in a fast succession, a 500 error will no longer occur.  

VPTL-9597

A JavaScript bug was resolved for the roomKey-query parameter.

VPTL-9415

An issue was fixed with the addMember API so that the Admin group assignments work correctly. This was due to cache keys overlapping in certain rare cases.  

VPTL-9862

A fix was made to the log rotation configuration for Apache and other miscellaneous logs.

Known issues

There are no new known issues for this release.