Version 21.3.1 LA
What's new in this release?
- Ability to invite another user to join a call via Epic CAL
- With Vidyo’s Epic Context-Aware Linking (CAL) integration, providers can now invite an additional registered user to their video call automatically upon invocation of a CAL link.
- Using the standard Epic CAL workflow, providers simply click an Epic CAL link to join a call, and the additional user will be simultaneously invited to the call.
- To specify the user to invite to the call, the Epic configuration must include the entityID of the user using the new InviteID field on the Settings > Feature Settings > Epic Integrations page in the Admin UI.
- To make testing easier, the Tenant Admin interface has been updated to allow an Admin to generate a sample URL with this parameter.
- Enter the entityID of the participant using the InviteID= parameter in the CRYPTSTRING.
- The default for the Admin UI InviteID field is no entityID being provided at all.
- Only providers can invite an additional user to their call; therefore, if the user type is not "Provider", the InviteID parameter is ignored.
- For more information about:
- How to use the new InviteID field on the Epic Integrations page in the Admin UI, see the VidyoConferencing Administrator Guide.
- How to configure Epic CAL integration, refer to the Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article. For compatibility information, refer to the Epic Compatibility with Vidyo Infrastructure article.
- 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 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.
- Mobile WebRTC for iOS and iPadOS now requires version 13.7 or later. If you use older versions, the "Join via the browser" option will not display on the Join page.
- VidyoGateway versions 3.5.x and VidyoReplay versions 3.1.x do not work with VidyoPortal and VidyoRouter version 22.2.x and later. You must upgrade your VidyoGateway and/or VidyoReplay to version 22.1.0 in order to be compatible with VidyoPortal and VidyoRouter version 22.2.x and later.
Important notes
- You can only upgrade to VidyoPortal and VidyoRouter version 21.3.1 LA from version 21.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.
- For information on how to upgrade to VidyoPortal and VidyoRouter version 21.3.1 LA from the version you are currently running, refer to the Upgrade Steps Lookup Tool article. This article lists the steps you need to take for your particular version, including which Security Updates you may need to install.
- 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_VC21_3_1_2607-bundle-v3978.vidyo |
VidyoPortal version 19.2.0 or later |
|
vidyorouter-TAG_VC21_3_1_2607-bundle-v3979.vidyo |
VidyoRouter version 19.2.0 or later |
Resolved issues
The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 21.3.1 LA.
|
VidyoPortal and VidyoRouter version 21.3.1 LA - resolved issues |
|
|---|---|
|
Key |
Summary |
|
VPTL-11828 |
An issue when Tenant Admins were unable to create, update, modify, or delete endpoint behaviors via API has been fixed. |
|
VPTL-11615 |
Hot Standby email notifications are now being correctly sent. |
|
VPTL-11558 |
VidyoPortal email notifications now support TLS 1.2 outbound connections for connecting to an SMTP server. |
|
VPTL-11557 and VPTL-11556 |
An issue that prevented member details from being created or updated when the portal language was set to Italian or Japanese has been resolved. |
|
VPTL-11542 |
An issue where the Epic SetExternalConnectionStatus leave notification was not being sent due to a race condition with WebRTC participants was fixed. |
|
VPTL-11070 |
An issue was fixed to prevent duplicate Epic SetExternalConnectionStatus leave notifications from being sent out when using mobile clients. |
Known issues
There are no new known issues for this release; however, to view the previous known issues, please see the known issues for VidyoPortal and VidyoRouter section.