• 2023 Releases
  • Version 22.5.1 General Availability

• 2022 Releases
  • Version 21.6.4 General Availability
  • Version 22.4.9 General Availability
  • Version 22.4.7 General Availability
  • Version 22.4.5 General Availability
  • Version 21.6.2 General Availability
  • Version 22.4.3 General Availability
  • Version 22.4.1 General Availability
  • Version 22.3.1 General Availability
  • Version 22.2.1 General Availability
  • Version 22.1.1 General Availability
  • Version 21.6.1 Limited Availability
  • Version 21.6.0 General Availability
• 2021 Releases
  • Version 21.5.1 Limited Availability
  • Version 21.5.0 General Availability
  • Version 21.4.1 Limited Availability
  • Version 21.4.0 General Availability
  • Version 21.3.1 Limited Availability
  • Version 21.3.0 General Availability
  • Version 21.2.1 Limited Availability
  • Version 21.2.0 General Availability
  • Version 21.1.1 Limited Availability
  • Version 21.1.0 General Availability
  • Version 20.1.6 General Availability
• 2020 Releases
  • Version 20.2.1 Limited Availability
  • Version 20.2.0 General Availability
  • Version 20.1.5 Limited Availability
  • Version 20.1.3 Limited Availability
  • Version 20.1.1 Limited Availability
  • Version 20.1.0 General Availability
• 2019 Releases
  • Version 19.3.0 General Availability
  • Version 19.2.0 General Availability
  • Version 19.1.0 General Availability
• 2018 Releases 
  • Version 18.4.0 General Availability
  • Version 18.3.1 General Availability
  • Version 18.2.1 General Availability
  • Version 18.2.0 General Availability
  • Version 18.1.0 General Availability
• 2017 Releases 
  • Version 17.3.0 (38) Rev B General Availability
  • Version 17.2.0 General Availability
  • Version 17.1.0 General Availability
  • Version 3.4.6 General Availability
• Important Upgrade Notices for On-Premises Customers
• Compatibility 
• Known Issues 

 

---

2023 Releases

---

VidyoPortal and VidyoRouter: About Version 22.5.1 General Availability (GA)

What's new in this release

• Closed captioning support
  • Users can now enjoy the benefits of low-latency closed captioning during their calls.
  • Closed captioning can be enabled/disabled via a simple button click.
  • Other configuration options include the ability to set parameters such as font size and background color.
  • Note: This feature is currently only available for VidyoCloud customers.
    • For on-premises customers, please contact Vidyo Support.
    • For VidyoCloud customers, please check the VidyoCloud status page for when this feature will be available to your platform.

• Important bug fixes
  • In this release, we've addressed some important issues to improve usability and reliability. Please see the Resolved issues section.

• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files

This file...	Is for...
vidyo-portal-TAG_VC22_5_1_8053-bundle-v5700.vidyo	VidyoPortal version 21.2.0 or later
vidyo-router-TAG_VC22_5_1_8053-bundle-v5701.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.5.1:

VidyoPortal and VidyoRouter version 22.5.1 - Resolved issues
Key	Summary
VIDPTL-426	We updated the Swagger libraries to the latest version to address multiple issues.
VIDPTL-288	Error messages no longer incorrectly display in Dutch when the System Language is set to German.
VIDPTL-143	Epic CAL Integration fix: We addressed the null display name when the FirstName and LastName variables were not included in the extData.
VIDPTL-137	Users are now able to log into the Tenant Admin Portal using Safari on iOS or iPadOS devices.
VIDPTL-59	The Status Notification feature now properly reports when a legacy device joins or leaves a conference.
VIDROUTER-64	We fixed a rare issue where the VidyoRouter would unexpectedly drop conferences.
VIDROUTER-39	We updated the default negotiation parameters for certain requests.

 

Known issues

There are no new known issues in this release.

 

---

2022 Releases 

VidyoPortal and VidyoRouter: About Version 21.6.4 General Availability (GA)

What's new in this release

• Version format

  • The format of the VidyoPortal version in the GetPortalVersion API request is now displayed consistently across the user interface. For example:

    • VidyoConferencing-22.4.7(4067)

• Important bug fixes
  • In this release, we've addressed some important issues to improve usability and reliability. Please see the Resolved issues section.

• 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 and later. You must upgrade your VidyoGateway and/or VidyoReplay to version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files

This file...	Is for...
vidyo-portal-TAG_VC21_6_4_4067-bundle-v5676.vidyo	VidyoPortal version 21.2.0 or later
vidyo-router-TAG_VC21_6_4_4067-bundle-v5677.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 21.6.4.

VidyoPortal and VidyoRouter Version 21.6.4 - Resolved Issues
Key	Summary
VIDPTL-755 and VIDPTL-751	We have fixed all Login APIs to work or without JSON Web Tokens (JWT).
VIDPTL-721 and VIDPTL-720 and VIDPTL-719 and VIDPTL-714	We fixed the failing login for users and guests if no JSON Web Token (JWT) secret was configured.
VIDPTL-717 and VIDPTL-711	We have changed the way the portal version is displayed. It is now more consistent across the different ways to access it.
VIDPTL-701 and VIDPTL-700	We’ve added JSON Web Token (JWT) access to GetPortalFeatures for guest and user web service APIs.

 

Known issues

There are no new known issues in this release.

 

---

VidyoPortal and VidyoRouter: About Version 22.4.9 General Availability (GA)

What's new in this release

• Version format

  • The format of the VidyoPortal version in the GetPortalVersion API request is now displayed consistently across the user interface. For example:

    • VidyoConferencing-22.4.7(4067)

• Important bug fixes
  • In this release, we've addressed some important issues to improve usability and reliability. Please see the Resolved issues section.

• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files

This file...	Is for...
vidyo-portal-TAG_VC22_4_9_7033-bundle-v5682.vidyo	VidyoPortal version 21.2.0 or later
vidyo-router-TAG_VC22_4_9_7033-bundle-v5683.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.4.9:

VidyoPortal and VidyoRouter Version 22.4.9 - Resolved Issues
Key	Summary
VIDPTL-754 and VIDPTL-753	We have fixed all Login APIs to work or without JSON Web Tokens (JWT).
VIDPTL-723 and VIDPTL-722 and VIDPTL-712 and VIDPTL-699	We fixed the failing login for users and guests if no JSON Web Token (JWT) secret was configured.
VIDPTL-716 and VIDPTL-710	We have changed the way the portal version is displayed. It is now more consistent across the different ways to access it.
VIDPTL-702 and VIDPTL-698	We’ve added JSON Web Token (JWT) access to GetPortalFeatures for guest and user web service APIs.

 

Known issues

There are no new known issues in this release.

 

---

 

VidyoPortal and VidyoRouter: About Version 22.4.7 General Availability (GA)

What's new in this release

• Important resolved issue and update for Vidyo Epic Context Aware Linking (CAL) Integration customers

  • In this release, we've addressed an issue where "SetExternalConnectionStatus" Disconnect notifications were not sent consistently with WebRTC participants.

  • It is highly recommended that all Epic Context-Aware Linking enabled customers that are using WebRTC upgrade to this version as soon as possible.

• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

 

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

 

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options. 

 

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files

This file...	Is for...
vidyo-portal-TAG_VC22_4_7_7028-bundle-v5614.vidyo	VidyoPortal version 21.2.0 or later
vidyo-router-TAG_VC22_4_7_7028-bundle-v5615.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issue

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.4.7:

VidyoPortal and VidyoRouter Version 22.4.7 - Resolved Issues
Key	Summary
VIDPTL-12	We resolved an issue where the Epic CAL Disconnect notification was not being sent consistently with WebRTC participants.

 

---

 

VidyoPortal and VidyoRouter: About Version 22.4.5 General Availability (GA)

What's new in this release 

• Separate configuration for Epic Hardware Test
  • Administrators can now configure the Epic Hardware Test Interconnect server separately via the Tenant Admin.
    
  • To use this feature, you must have:
  • Version 22.3.0 or later of VidyoConnect for Desktop, Mobile, or WebRTC.
  • Version 22.4.5 or later of the VidyoPortal.
  • Version 22.2.1 or later of the Vidyo Epic Service.
• Join via Browser button is no longer displayed on Firefox
  • The option to join via Native WebRTC no longer displays for Firefox browsers.
• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options. 

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files

This file...	Is for...
vidyoportal-TAG_VC22_4_5_7024-bundle-v5592	VidyoPortal version 21.2.0 or later
vidyorouter-TAG_VC22_4_5_7024-bundle-v5593.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.4.5:

VidyoPortal and VidyoRouter Version 22.4.5 - Resolved Issues
Key	Summary
VIDPTL-571	We have integrated the latest Swagger UI updates that address multiple Document Object Model (DOM) issues.
VIDPTL-410	The “Join via browser” button is not displayed for Firefox as it is not supported on this release for Native WebRTC.
VIDPTL-392	We have fixed an issue where the admin was unable to re-open the “Edit Room” page in Google Chrome.
VIDROUTER-25	We fixed an issue, where under rare circumstances, the VidyoRouter may have abruptly stopped during the processing of a Real-time Transport Protocol (RTP) packet.

 

---

VidyoPortal and VidyoRouter: About Version 21.6.2 General Availability (GA)

What's new in this release 

• Resolved issues
  • In this release, we've addressed several issues to improve usability and security.
• 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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files

This file...	Is for...
vidyoportal-TAG_VC21_6_2_4063-bundle-v5580.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_6_2_4063-bundle-v5581.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.6.2 GA:

VidyoPortal and VidyoRouter Version 21.6.2 - Resolved Issues
Key	Summary
VIDPTL-392	We have fixed an issue where the admin was unable to re-open the “Edit Room” page in Google Chrome.
VIDPTL-571	We have integrated the latest Swagger UI updates that address multiple Document Object Model (DOM) issues.

 

---

 

VidyoPortal and VidyoRouter: About Version 22.4.3 General Availability (GA)

What's new in this release 

• Resolved VidyoConnect for Mobile disconnect notification issue for Epic
  • In this release, the Epic Interconnect Server now properly receives notifications when VidyoConnect for Mobile iOS users disconnect from a call. This fixes an issue where, in some cases, Epic was not notified when a mobile call ended.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options. 

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files

This file...	Is for...
vidyoportal-TAG_VC22_4_3_7019-bundle-v5536.vidyo	VidyoPortal version 21.2.0 or later
vidyorouter-TAG_VC22_4_3_7019-bundle-v5537.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.4.3:

VidyoPortal and VidyoRouter Version 22.4.3 - Resolved Issues
Key	Summary
VIDPTL-345	Disconnected calls are now properly registered on the Epic Interconnect Server for VidyoConnect for Mobile (iOS and Android).

 

---

VidyoPortal and VidyoRouter: About Version 22.4.1 General Availability (GA)

What's new in this release 

• Important resolved issue for Epic customers who have experienced intermittent 404 errors when joining Epic CAL conferences
  • Prior to this release, some cloud-based and on-premises customers with Epic integrations (or other API integrations) may have experienced a rare issue with failed calls. These customers may have seen a 404 or “call/room not found” error when attempting to connect to a call.
    • This issue was caused when the API service incorrectly selected a disabled Admin on the Tenant to process a request. If the request went to an enabled Admin, it was processed correctly; if the request went to a disabled Admin, it could not be provisioned and the error would occur.
  • In this release, the selection process has been updated to select only valid Admin users.
• Epic Hardware Test
  • This release adds the infrastructure support for integrating with the SetHardwareTest functionality in Epic.
  • Administrators can now include a parameter in their FDI record that enables the Hardware Test workflow on endpoints prior to allowing those endpoints to join a conference.
  • To use this feature, you must have: 
    • Version 22.3.0 or later of VidyoConnect for Desktop, Mobile, or WebRTC
    • Version 22.2.0 or later of the Vidyo Epic Service
• Inactivity timer custom parameter
  • The new "InactivityTimer" custom parameter enables Tenant Admins to set a timeout value for guests and/or registered users. After the specified amount of time during which a participant is alone in a call, VidyoConnect disconnects the guest or registered user.
    
    • The Tenant Admin can set up this parameter for guest and registered users separately.
    • For VidyoConnect for Desktop, this feature applies only to Epic users. For VidyoConnect for WebRTC, this feature applies to all users.
  • To use this feature, the Tenant Admin must configure it on the VidyoPortal and end users must be running VidyoConnect for Desktop or VidyoConnect for Native WebRTC version 22.3.0 or later.
    • For information about how to configure the Tenant Admin Portal for this feature, refer to the "Configuring Custom Parameters" section the VidyoPortal and VidyoRouter Administrator Guide version 21.4.0 or later.
      
      
      
      
• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options. 

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC22_4_1_7018-bundle-v5505.vidyo	VidyoPortal version 21.2.0 or later
vidyorouter-TAG_VC22_4_1_7018-bundle-v5506.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.4.1:

VidyoPortal and VidyoRouter Version 22.4.1 - Resolved Issues
Key	Summary
VIDPTL-194	The API service has been updated to select only valid Admin users, thereby preventing a rare issue for Epic customers where they could receive a 404 error when attempting to connect to an Epic CAL conference.
VIDPTL-23	Participants who connect to a VidyoConnect call via a legacy endpoint can now be successfully muted using the Mute button on the Participants panel.
VPTL-13479	An issue was fixed where audio-only (PSTN) participants could not be muted from the Control Meeting page.
VPTL-13452	An issue where the CSS margins were not correct on a customized Portal after updating to Chrome/Edge 98 has been resolved.;

 

---

VidyoPortal and VidyoRouter: About Version 22.3.1 General Availability (GA)

What's new in this release 

• Automatic CAL link expiration for ad-hoc calls using the Epic Timestamp parameter 
  • Admins using the Epic CAL integration can now increase security by automatically expiring ad-hoc CAL links based on a new parameter: Timestamp=.
    • This parameter expects a UNIX timestamp (in seconds) that is generated on demand by your FDI record in Epic.
    • Admins may use the LinkValidityPeriod parameter in the CRYPTSTRING to customize in minutes the length of time the Epic link is valid.
  • To use this feature:
    • You must have the Vidyo and Epic CAL integration. For information about this integration and how to configure it, refer to the Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article.
    • Tenant Admins must enable the feature on the Epic Integration page in the Tenant Admin portal. For information about how to do so, refer to the "Automatic Epic CAL Link Expiration for Ad-Hoc Rooms" section in the  Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article.
    • You must have access to Epic’s App Orchard marketplace. For information about how to obtain access, contact your Epic representative and your Vidyo sales or account representative. 
• Minimum endpoint version: per-Tenant allowed endpoint list
  • Admins can now configure their Tenants to allow only certain applications to connect or log in.
  • This feature can be configured using a new REST API that enables endpoints to be rejected based on:
    • ApplicationName
    • EndpointType
• Resolved issues
  • In this release, we've addressed several issues to improve usability and security.
• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in VidyoPortal version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options. 

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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC22_3_1_6038-bundle-v5395.vidyo	VidyoPortal version 21.2.0 or later
vidyorouter-TAG_VC22_3_1_6038-bundle-v5396.vidyo	VidyoRouter version 21.2.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.3.1:

VidyoPortal and VidyoRouter Version 22.3.1 - Resolved Issues
Key	Summary
VPTL-13166	The api_usage table now automatically gets cleaned and will hold a max of 180 days of records. Prior to this release, the table could grow large enough to degrade service.
VPTL-12759	An issue was fixed where certain notification queues could run out of memory causing Status Notifications not to be sent.

 

---

 

VidyoPortal and VidyoRouter: About Version 22.2.1 General Availability (GA)

What's new in this release 

• Quick and easy install workflow for first-time mobile users
  • Mobile users can now go from clicking a room link to installing the VidyoConnect Mobile app to joining a conference in one seamless workflow.
  • This feature is available for VidyoCloud customers automatically. For on-premises customers, please contact Vidyo Support.
• Epic InviteID workflow improvement
  • When inviteID is used in an Epic CAL link, the auto-disconnect feature now automatically invalidates the used room link.
  • This improvement provides additional security especially for workflows where users re-use the CSN for dialing out to rooms.
• Auto-moderator PIN for Epic CAL workflows
  • The auto-moderator PIN explicitly enables multiple Providers to moderate the same conference via a parameter.
  • In order to use the auto-moderator PIN for Epic, your VidyoConnect endpoint must support it. Version 22.2.0 of the VidyoConnect desktop app will be the first version that supports this feature.
• Resolved issues
  • In this release, we've addressed several issues to improve usability and security.
• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
• Vidyo Epic Service and Event Service updates
  • The Vidyo Epic Service and the Vidyo Event Service have also undergone security and stability updates as part of this release. For more information, refer to the Vidyo Epic Service: Release Notes and the Vidyo Event Service: Release Notes.

Important compatibility information

As a reminder, we made some significant updates to the Vidyo Compatibility Matrix in the previous VidyoPortal release, which was version 22.1.1. Please refer to the Vidyo Compatibility Matrix for On-Premises and the subsections below for more details.

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to version 22.1.1 or later if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options. 

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. 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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC22_2_1_5021-bundle-v5301.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC22_2_1_5021-bundle-v5302.vidyo	VidyoRouter version 19.2.0 or later
vidyo-event-service-22.1.0.1012-bundle-v5253.vidyo	Vidyo Event Service version 21.1.0 or later
vidyo-epic-22.1.0.0502-bundle-v5274.vidyo	Vidyo Epic Service version 21.1.0 or later

 

Resolved issues

The following table lists the issues we've resolved in VidyoPortal and VidyoRouter version 22.2.1:

VidyoPortal and VidyoRouter Version 22.2.1 - Resolved Issues
Key	Summary
VPTL-12986	VidyoReplay devices now properly lock out users who attempt to log in beyond the number entered in the “Number of failed login attempts before account is locked” field on the VidyoPortal Super Admin Settings > Security > Passwords page.
VPTL-12840	If a license cannot be uploaded because the number of licensed lines is lower than the allocated number of lines in the VidyoPortal tenant, the error message pop-up now tells you this. In the previous release, the error message pop-up was blank.
VPTL-12333	If a legacy device is assigned as a public room's room owner, the public room can now be searched and found via the VidyoConnect app.

 

---

VidyoPortal and VidyoRouter: About Version 22.1.1 General Availability (GA)

What's new in this release 

• General Availability of Native WebRTC
  • Enghouse Vidyo is happy to announce that Native WebRTC is now available for all customers.
  • This release is compatible with both VidyoConnect for Native WebRTC and VidyoClient JavaScript SDK for WebRTC.
• Royalty-free codec support
  • VidyoPortal and VidyoRouter version 22.1.1 includes support for royalty-free codec applications. This specifically includes:
    • VidyoConnect for Desktop 22.1.0 and later
    • VidyoClient 22.1.0 and later
  • This feature allows for seamless switching between H.264 and VP9 codecs dynamically, thereby preserving backwards compatibility for older versions of VidyoConnect and VidyoClient.
  • VP9 gets automatically set up when you upgrade to this version.
• Minimum endpoint version
  • The minimum endpoint version feature allows Administrators to reject endpoints based on the following criteria:
    • ApplicationName
    • EndpointType
  • This feature can be configured at a System or Tenant level via REST APIs. For more information, refer to the Web Services API User Guide.
• Vidyo Compatibility Matrix updates
  • We’ve made some significant updates to the Vidyo Compatibility Matrix in accordance with this release of the VidyoPortal. These are the recommended client versions:
    • VidyoConnect for Desktop: 22.1.0
    • VidyoConnect for Mobile: 22.1.0
    • VidyoConnect for WebRTC (Native): 22.1.0
    • VidyoConnect Room: 22.1.0
    • VidyoClient: 22.1.0
  • For more compatibility information, refer to the Vidyo Compatibility Matrix for On-Premises and the "Important compatibility information" section below.
• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Important compatibility information

Endpoint compatibility

Starting with VidyoPortal 22.1.1, the following endpoints are no longer supported:

• VidyoDesktop
• VidyoMobile
• VidyoRoom HD-200, HD-100, and HD-50
• VidyoClient 3.x-based applications

Healthcare compatibility

Do not upgrade to this version if you are using any of the following integrations:

• Epic Deep Integration
• Epic Monitor Deep Integration

If you are using any of the above endpoints or integrations, please contact Vidyo Support for migration options.

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.
• 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.1.x. You must upgrade your VidyoGateway and/or VidyoReplay to version 22.1.0 in order to be compatible with VidyoPortal and VidyoRouter version 22.1.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC22_1_1_4539-bundle-v5216.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC22_1_1_4539-bundle-v5217.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 22.1.0:

VidyoPortal and VidyoRouter Version 22.1.0 - Resolved Issue
Key	Summary
VMVR-116	Vidyo addressed an issue where, under high-load conditions, the VidyoRouter application would not cleanly close UDP ports.

 

---

VidyoPortal and VidyoRouter: About Version 21.6.1 Limited Availability (LA)

 

What's new in this release 

• CDR obfuscation profiles
  
  • Super Admins can now use REST APIs to define CDR obfuscation profiles on a per Tenant basis. An obfuscation profile indicates what data should be obfuscated in the CDR (Call Detail Record) for each Tenant.  
    • Super Admins can also create a default obfuscation profile via the REST APIs.
    • This customizability is especially useful for healthcare and GDPR customers who must follow strict guidelines on storing Personally Identifiable Information (PII).
  • For more information about the new APIs you can use to create CDR obfuscation profiles, refer to the "CDR Obfuscation Profiles" section of the Web Services API User Guide.
• Multiple custom SIP headers in the InviteToConference SOAP API
  • API users can now pass multiple SIP headers to a SIP endpoint when sending a conference invitation.
    • The header is accessible when dialing through the VidyoGateway™.
    • Prior to this release, only one parameter could be sent, which limited some use cases.
• 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.
• 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 21.6.x. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC21_6_1_4060-bundle-v5053.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_6_1_4060-bundle-v5054.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 21.6.1 LA:

VidyoPortal and VidyoRouter Version 21.6.1 LA - Resolved Issues
Key	Summary
VPTL-13048	An issue was resolved where, under certain high-load conditions, some users were unable to join conferences.

 

---

VidyoPortal and VidyoRouter: About Version 21.6.0 General Availability (GA)

What's new in this release 

• CDR obfuscation profiles
  
  • Super Admins can now use REST APIs to define CDR obfuscation profiles on a per Tenant basis. An obfuscation profile indicates what data should be obfuscated in the CDR (Call Detail Record) for each Tenant.  
    • Super Admins can also create a default obfuscation profile via the REST APIs.
    • This customizability is especially useful for healthcare and GDPR customers who must follow strict guidelines on storing Personally Identifiable Information (PII).
  • For more information about the new APIs you can use to create CDR obfuscation profiles, refer to the "CDR Obfuscation Profiles" section of the Web Services API User Guide.
• Multiple custom SIP headers in the InviteToConference SOAP API
  • API users can now pass multiple SIP headers to a SIP endpoint when sending a conference invitation.
    • The header is accessible when dialing through the VidyoGateway™.
    • Prior to this release, only one parameter could be sent, which limited some use cases.
• 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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC21_6_0_4060-bundle-v5051.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_6_0_4060-bundle-v5052.vidyo	VidyoRouter version 19.2.0 or later

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 21.6.0 LA:

VidyoPortal and VidyoRouter Version 21.6.0 GA - Resolved Issues
Key	Summary
VPTL-13048	An issue was resolved where, under certain high-load conditions, some users were unable to join conferences.

 

---

2021 Releases 

---

 

VidyoPortal and VidyoRouter: About Version 21.5.1 Limited Availability (LA)

 

What's new in this release 

• Native WebRTC moderation 
  • Native WebRTC users can now be moderated by normal moderation actions through VidyoConnect, HTML Control Meeting, and existing APIs. Native WebRTC moderation is powered by the Vidyo Event Service.
    • For more information about the Vidyo Event Service and how to configure this functionality, refer to the Vidyo Event Service Deployment Guide.
    • For more information about how to use this feature on the VidyoConnect app, refer to the “Using the Meeting Moderation Capability” section of the Using VidyoConnect: About Each Feature article. 

• Capture and save images during VidyoConnect calls with Epic CAL 
  
  • Auto-provisioned healthcare providers using the Epic CAL integration can now capture a snapshot of a patient's video or of a patient's shared content during a VidyoConnect call. Providers can then save the captured image to a patient's chart in Epic. 
  • This new feature utilizes Epic's SMART on FHIR authentication scheme.
    • The API that enables the provider to take a snapshot and send the image to Epic is the SaveMedia API. SaveMedia is used in conjunction with the TelemedicineConfiguration API, which checks whether the provider has permission to upload media.
    • In order to enable this feature for on-premises deployments, you must deploy the Vidyo Epic Service alongside your VidyoPortal. For more information on the Vidyo Epic Service, refer to the Vidyo Epic Service Deployment Guide.
  • To capture and save images during VidyoConnect calls with Epic CAL:
    • Tenant Admins must enable this feature on the Epic Integrations page in the Tenant Admin portal. For information about how to do so, refer to version 21.5.0 or later of the VidyoPortal and VidyoRouter Administrator Guide.
      
      
      
    • You must have a compatible VidyoConnect client, such as VidyoConnect for Desktop version 21.6.2 or later or VidyoConnect for WebRTC version 21.5.1 or later. For more information about how to use this feature on the VidyoConnect app, refer to the “Capturing Images of Participants' Video and Shared Content When Using Epic” section of the Using VidyoConnect: About Each Feature article. 
    • Your organization must use the Vidyo and Epic CAL integration. For information about how to configure the 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.
    • You must have access to Epic’s App Orchard marketplace. For information about how to obtain access, contact your Epic representative and your Vidyo sales or account representative. In order to enable support for this feature, you must request access to an updated Vidyo CAL Integration Application in the App Orchard marketplace – with an updated Epic-Client-ID.
• TLS 1.3 support for HTTPS traffic
  • Added support for the newer encryption protocol.
  • Added support for AES-GCM and additional PFS (Perfect Forward Secrecy) ciphers.
• System updates 
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
  • Updates for CVE-2021-44228, CVE-2021-45046, and CVE-2021-45105 are also included in 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.
• 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 21.5.x. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC21_5_1_3611-bundle-v4983.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_5_1_3611-bundle-v4984.vidyo	VidyoRouter version 19.2.0 or later

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 21.5.1 LA:

VidyoPortal and VidyoRouter Version 21.5.1 LA - Resolved Issues
Key	Summary
VPTL-12488	Fixed an issue where, under certain high-load situations, the database connection stopped running.
VPTL- 12349	Passwords beginning with the "@" character can now be used to log in to the portal.
VPTL-12278	When using VidyoConnect for Native WebRTC, connection failures no longer occur when the client's timestamp for the join request is more than 60 seconds behind the server time.
VPTL-12133	When users click certain links to join calls on an unsupported browser (such as Edge or Chrome on iOS or Firefox on Android), they are now properly redirected to the correct VidyoConnect WebRTC app so they can easily join the call.

 

---

VidyoPortal and VidyoRouter: About Version 21.5.0 General Availability (GA)

What's new in this release 

• Capture and save images during VidyoConnect calls with Epic CAL 
  
  • Auto-provisioned healthcare providers using the Epic CAL integration can now capture a snapshot of a patient's video or of a patient's shared content during a VidyoConnect call. Providers can then save the captured image to a patient's chart in Epic. 
  • This new feature utilizes Epic's SMART on FHIR authentication scheme.
    • The API that enables the provider to take a snapshot and send the image to Epic is the SaveMedia API. SaveMedia is used in conjunction with the TelemedicineConfiguration API, which checks whether the provider has permission to upload media.
    • To enable this feature for on-premise deployments, you must deploy the Vidyo Epic Service alongside your VidyoPortal. For more information on the Vidyo Epic Service, refer to the Vidyo Epic Service Deployment Guide.
  • To capture and save images during VidyoConnect calls with Epic CAL:
    • Tenant Admins must enable this feature on the Epic Integrations page in the Tenant Admin portal. For information about how to do so, refer to the VidyoPortal and VidyoRouter Administrator Guide.
      
      
      
    • You must have a compatible VidyoConnect client, such as VidyoConnect for Desktop version 21.6.2 or later or VidyoConnect for WebRTC version 21.5.1 or later. For more information about how to use this feature on the VidyoConnect app, refer to the “Capturing Images of Participants' Video and Shared Content When Using Epic” section of the Using VidyoConnect: About Each Feature article. 
    • Your organization must use the Vidyo and Epic CAL integration. For information about how to configure the 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.
    • You must have access to Epic’s App Orchard marketplace. For information about how to obtain access, contact your Epic representative and your Vidyo sales or account representative. In order to enable support for this feature, you must request access to an updated Vidyo CAL Integration Application in the App Orchard marketplace – with an updated Epic-Client-ID.
• TLS 1.3 support for HTTPS traffic
  • Added support for the newer encryption protocol.
  • Added support for AES-GCM and additional PFS (Perfect Forward Secrecy) ciphers.
• System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
  • Updates for CVE-2021-44228, CVE-2021-45046, and CVE-2021-45105 are also included in 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.5.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. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC21_5_0_3611-bundle-v4980.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_5_0_3611-bundle-v4982.vidyo	VidyoRouter version 19.2.0 or later

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 21.5.0 GA:

VidyoPortal and VidyoRouter Version 21.5.0 GA - Resolved Issues
Key	Summary
VPTL-12448	Fixed an issue where, under certain high-load situations, the database connection stopped running.
VPTL- 12349	Passwords beginning with the "@" character can now be used to log in to the portal.
VPTL-12133	When users click certain links to join calls on an unsupported browser (such as Edge or Chrome on iOS or Firefox on Android), they are now properly redirected to the correct VidyoConnect WebRTC app so they can easily join the call.

---

 

VidyoPortal and VidyoRouter: About Version 21.4.1 Limited Availability (LA)

 

 

What's new in this release 

• Automatically disconnect the last call participant when InviteID is used
  
  • In VidyoPortal and VidyoRouter version 21.3.1 LA, we introduced the ability to invite an additional registered user to a video call automatically upon invocation of an Epic CAL link. In this release, when there is only one participant remaining in such a call, that participant will be automatically disconnected.  
    • To specify the user to invite to the call, the Epic configuration has to include the entityID of the user using the InviteID field on the Settings > Feature Settings > Epic Integrations page in the Admin UI.
    • When a participant joins an epic call initiated with the InviteID, the system will automatically enable the "auto-disconnect on last participant" mode. There is a grace period of one minute before the last participant is disconnected. 
  • For information about 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.
• Manage CORS domains per tenant using APIs 
  • On-premises administrators can now manipulate the CORS entries stored in the database using REST APIs.
    • The new Tenant Admin REST APIs enable you to read, add, edit, and delete CORS domains.
  • For more information about the new APIs, refer to the Web Services API User Guide. 
• Play audio and video content to Epic CAL participants in a waiting room
  • Healthcare customers using Epic CAL can now play music or a video to patients who are waiting for their healthcare providers to join their VidyoConnect call. You can customize this feature so that patients in the waiting room can:
    • view a video.
    • listen to audio (with or without a background image).
    • see a background image (with or without audio).
  • Providers can specify the video, audio, and background image content to be played in the waiting room. They can select different content for different calls.
  • To use this feature, the Tenant Admin must configure it on VidyoPortal version 21.4.0 or later, and end users must be running VidyoConnect for Desktop version 21.5.0 or later or VidyoConnect for Native WebRTC version 21.4.0 or later.
    • For more information about the new configuration parameters for this feature, refer to the "Other Configuration Parameters" table in the Using VidyoConnect: Admin-Level Functions article.
    • For information about how to configure Epic CAL integration for this feature, refer to the "Playing Audio or Video Content to Epic CAL Participants in a Waiting Room" section of the Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article.
    • For information about how to configure the Tenant Admin Portal for this feature, refer to the "Configuring Custom Parameters" section the VidyoPortal and VidyoRouter Administrator Guide version 21.4.0 or later.
• 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.
• 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 21.4.x. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

Files 

This file...	Is for...
vidyoportal-TAG_VC21_4_1_3053-bundle-v4281.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_4_1_3053-bundle-v4282.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 21.4.1 LA:

VidyoPortal and VidyoRouter Version 21.4.1 LA - Resolved Issue
Key	Summary
VPTL-12257	Top-level domain limitations that were found in allowed CORS domains have been addressed.

 

---

VidyoPortal and VidyoRouter: About Version 21.4.0 General Availability (GA)

What's new in this release 

• Automatically disconnect the last call participant when InviteID is used
  
  • In VidyoPortal and VidyoRouter version 21.3.0 GA, we introduced the ability to invite an additional registered user to a video call automatically upon invocation of an Epic CAL link. In this release, when there is only one participant remaining in such a call, that participant will be automatically disconnected.  
    • To specify the user to invite to the call, the Epic configuration has to include the entityID of the user using the InviteID field on the Settings > Feature Settings > Epic Integrations page in the Admin UI.
    • When a participant joins an epic call initiated with the InviteID, the system will automatically enable the "auto-disconnect on last participant" mode. There is a grace period of one minute before the last participant is disconnected. 
  • For information about 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.
• Manage CORS domains per tenant using APIs 
  • On-premises administrators can now manipulate the CORS entries stored in the database using REST APIs.
    • The new Tenant Admin REST APIs enable you to read, add, edit, and delete CORS domains.
  • For more information about the new APIs, refer to the Web Services API User Guide. 
• Play audio and video content to Epic CAL participants in a waiting room
  • Healthcare customers using Epic CAL can now play music or a video to patients who are waiting for their healthcare providers to join their VidyoConnect call. You can customize this feature so that patients in the waiting room can:
    • view a video.
    • listen to audio (with or without a background image).
    • see a background image (with or without audio).
  • Providers can specify the video, audio, and background image content to be played in the waiting room. They can select different content for different calls.
  • To use this feature, the Tenant Admin must configure it on VidyoPortal version 21.4.0 or later, and end users must be running VidyoConnect for Desktop version 21.5.0 or later or VidyoConnect for Native WebRTC version 21.4.0 or later.
    • For more information about the new configuration parameters for this feature, refer to the "Other Configuration Parameters" table in the Using VidyoConnect: Admin-Level Functions article.
    • For information about how to configure Epic CAL integration for this feature, refer to the "Playing Audio or Video Content to Epic CAL Participants in a Waiting Room" section of the Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article.
    • For information about how to configure the Tenant Admin Portal for this feature, refer to the "Configuring Custom Parameters" section the VidyoPortal and VidyoRouter Administrator Guide version 21.4.0 or later.
• 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.4.x. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC21_4_0_3053-bundle-v4279.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_4_0_3053-bundle-v4280	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the issue we've resolved in VidyoPortal and VidyoRouter version 21.4.0 GA:

VidyoPortal and VidyoRouter Version 21.4.0 GA - Resolved Issue
Key	Summary
VPTL-12257	Top-level domain limitations that were found in allowed CORS domains have been addressed.

 

---

 

VidyoPortal and VidyoRouter: About Version 21.3.1 Limited Availability (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 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.
• 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 21.3.x. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

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 resolved issues 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.

 

---

VidyoPortal and VidyoRouter: About Version 21.3.0 General Availability (GA)

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 userto 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 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.3.x. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC21_3_0_2607-bundle-v3976.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_3_0_2607-bundle-v3977.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 21.3.0 GA:

VidyoPortal and VidyoRouter Version 21.3.0 GA - 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	The disconnect API is now getting sent properly when using Epic CAL.

 

---

VidyoPortal and VidyoRouter: About Version 21.2.1 Limited Availability (LA)

 

 

What's new in this release 

• Auto-provisioning of providers with Epic CAL
  • Using Vidyo’s Epic Context-Aware Linking (CAL) integration, providers can now be automatically provisioned into their Tenant.
  • Providers can now also perform moderation actions in their Epic CAL conferences, including:
    • Muting participants
    • Disconnecting participants
    • Inviting other users via links
    • Inviting other registered users to the conference
    • Dialing out to SIP or H.323 devices
  • Provisioned providers can be configured to be automatically logged out at the end of their conferences. For more information, refer to the “Endpoint Behavior Mode” section of the Web Services API User Guide.
  • This feature requires VidyoConnect version 21.1.0 or later.
  • For information about 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.
• Log level API
  • To make debugging issues easier, we’ve added a "logcategories” Super REST API to dynamically increase or decrease log levels on the web application.
  • For more information about the APIs, refer to the Web Services API User Guide.
• Pass-through of Custom Invocation parameters via URL
  • You can now customize the VidyoConnect end-user experience via links using Custom Invocation parameters.
  • A use case for this feature is to support Webinar mode in VidyoConnect version 21.1.0.
• VidyoInsights support
  • This version of the VidyoPortal and VidyoRouter supports the upcoming release of VidyoInsights.
  • VidyoInsights is a performance monitoring system and analytics tool for on-premises and private cloud administrators that provides the data needed to verify and track VidyoPlatform infrastructure components (VidyoPortal and VidyoRouter), applications, and events. VidyoInsights aggregates data from multiple components and generates visual dashboards for quick and accurate trend analysis.
• 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.
• 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 21.2.1. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC21_2_1_2053-bundle-v3545.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_2_1_2053-bundle-v3546.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 21.2.1 LA:

VidyoPortal and VidyoRouter Version 21.2.1 LA - Resolved Issues
Key	Summary
VPTL-11451 and VPTL-11286	The VidyoPortal now checks that the correct versions of macOS and Safari are being use on the Join page.
VPTL-10862	Getting cross-Tenant member data is allowed if the following conditions are met: Inter-Tenant communication is enabled The Tyto configuration for the current Tenant and the other Tenant are the same.
VPTL-10776	A rare issue that prevented users from being able to log in or join calls from guest links has been resolved.
VPTL-11415	Updates were made to speed up processing of WebRTC requests.
VPTL-11383	Newly created Tenants now correctly have VP9 enabled as the default on Native WebRTC.
VPTL-11462	When making changes to Router Pools & Rules and then activating those changes, the VidyoManager now properly restarts to apply the changes.

 

---

VidyoPortal and VidyoRouter: About Version 21.2.0 General Availability (GA)

What's new in this release 

• Auto-provisioning of providers via Epic CAL
  • Using Vidyo’s Epic Context-Aware Linking (CAL) integration, providers can now be automatically provisioned into their Tenant.
  • Providers can now also perform moderation actions in their Epic CAL conferences, including:
    • Muting participants
    • Disconnecting participants
    • Inviting other users via links
    • Inviting other registered users to the conference
    • Dialing out to SIP or H.323 devices
  • Provisioned providers can be configured to be automatically logged out at the end of their conferences. For more information, refer to the “Endpoint Behavior Mode” section of the Web Services API User Guide.
  • This feature requires VidyoConnect version 21.1.0 or later.
  • For information about 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.
• Log level API
  • To make debugging issues easier, we’ve added a "logcategories” Super REST API to dynamically increase or decrease log levels on the web application.
  • For more information about the APIs, refer to the Web Services API User Guide.
• Pass-through of Custom Invocation parameters via URL
  • You can now customize the VidyoConnect end-user experience via links using Custom Invocation parameters.
  • A use case for this feature is to support Webinar mode in VidyoConnect version 21.1.0.
• VidyoInsights support
  • This version of the VidyoPortal and VidyoRouter supports the upcoming release of VidyoInsights.
  • VidyoInsights is a performance monitoring system and analytics tool for on-premises and private cloud administrators that provides the data needed to verify and track VidyoPlatform infrastructure components (VidyoPortal and VidyoRouter), applications, and events. VidyoInsights aggregates data from multiple components and generates visual dashboards for quick and accurate trend analysis.
• 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.
• 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 21.2.0. You must upgrade your VidyoGateway and/or VidyoReplay to a version 20.2.0 in order to be compatible with VidyoPortal and VidyoRouter version 21.2.x and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC21_2_0_2053-bundle-v3543.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_2_0_2053-bundle-v3544.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 21.2.0 GA:

VidyoPortal and VidyoRouter Version 21.2.0 GA - Resolved Issues
Key	Summary
VPTL-11451	The VidyoPortal now checks that the correct versions of macOS and Safari are being use on the Join page.
VPTL-10862	Getting cross-Tenant member data is allowed if the following conditions are met: Inter-Tenant communication is enabled The Tyto configuration for the current Tenant and the other Tenant are the same.
VPTL-10776	A rare issue that prevented users from being able to log in or join calls from guest links has been resolved.

 

---

VidyoPortal and VidyoRouter: About Version 21.1.1 Limited Availability (LA)

 

 

What's new in this release 

• Mobile Universal and App Link Metadata Available on the VidyoPortal
  • To support deep linking to the VidyoConnect mobile app on both Android and iOS mobile devices, the VidyoPortal now advertises metadata files in a known URL path.
  • For any Tenant hosted on the portal, the portal provides the link to the assetlinks.json file for the Android app or to the apple-app-site-association file for the Apple app.
• Epic CAL CSN Added to the CDR
  • The Call Detail Record (CDR) of Epic CAL conference participants now includes the Contact Serial Number (CSN) in the ReferenceNumber field.
  • Epic uses the CSN to track unique telehealth visits. Therefore, providing this data via the CDR is useful for analytics and decision-making. 
• 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.0 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 20.2.0 and later. You must upgrade your VidyoGateway and/or VidyoReplay to a version newer than 3.5.x and 3.1.x, respectively, in order to be compatible with VidyoPortal and VidyoRouter version 20.2.0 and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC21_1_1_1524-bundle-v3338.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_1_1_1524-bundle-v3339.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 21.1.1 LA:

VidyoPortal and VidyoRouter Version 21.1.1 LA - Resolved Issues
Key	Summary
VPTL-11383	For Native WebRTC portals, the VP9 is now advertised as enabled automatically for all newly created tenants.
VPTL-11286	When using certain versions of iOS with Safari on a mobile device, the "Join via the browser" button now appears along with the "Join via the app" button so users can join via WebRTC.

 

---

VidyoPortal and VidyoRouter: About Version 21.1.0 General Availability (GA)

What's new in this release 

• Mobile Universal and App Link Metadata Available on the VidyoPortal
  • To support deep linking to the VidyoConnect mobile app on both Android and iOS mobile devices, the VidyoPortal now advertises metadata files in a known URL path.
  • For any Tenant hosted on the portal, the portal provides the link to the assetlinks.json file for the Android app or to the apple-app-site-association file for the Apple app.
• Epic CAL CSN Added to the CDR
  • The Call Detail Record (CDR) of Epic CAL conference participants now includes the Contact Serial Number (CSN) in the ReferenceNumber field.
  • Epic uses the CSN to track unique telehealth visits. Therefore, providing this data via the CDR is useful for analytics and decision-making. 
• 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.0 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 20.2.0 and later. You must upgrade your VidyoGateway and/or VidyoReplay to a version newer than 3.5.x and 3.1.x, respectively, in order to be compatible with VidyoPortal and VidyoRouter version 20.2.0 and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC21_1_0_1524-bundle-v3336.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC21_1_0_1524-bundle-v3337.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 21.1.0:

VidyoPortal and VidyoRouter Version 21.1.0 - Resolved Issues
Key	Summary
VPTL-11286	When using certain versions of iOS with Safari on a mobile device, the "Join via the browser" button now appears along with the "Join via the app" button so users can join via WebRTC.

 

---

VidyoPortal and VidyoRouter: About Version 20.1.6 General Availability (GA)

What's new in this release 

• VidyoPortal Security Fix
  • Our developers at Enghouse Vidyo are always working to make VidyoPortal server software secure and reliable. We perform security audits of our software on a regular basis, and as a result of the latest audit, we are issuing a critical security update.
  • Enghouse Vidyo highly recommends that you immediately upgrade to VidyoPortal version 20.1.6 if you are currently running version 20.1.0, 19.3.0, or 19.2.0 and cannot upgrade to 21.1.0 yet due to compatibility reasons.

Important notes

 

Files

This file...	Is for...
vidyoportal-TAG_VC20_1_6_0194-bundle-v3340.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC20_1_6_0194-bundle-v3341.vidyo	VidyoRouter version 19.2.0

 

Resolved issues   

No additional issues were resolved in version 20.1.6.

 

---

2020 Releases 

---

 

VidyoPortal and VidyoRouter: About Version 20.2.1 Limited Availability (LA)

What's new in this release 

• Join WebRTC Meetings Faster 
  • Admins can configure a new URL parameter that allows participants to quickly and easily join calls automatically by clicking the meeting link and bypassing the "Join via App" and "Join via Browser" pages.
  • If the participant's browser does not meet the requirements for a WebRTC meeting, the standard "Join via App" page will still display.  
• VidyoConnect™ Room Support
  • In this release, we’ve added server-side support for the VidyoConnect Room as our new and improved user interface (UI) for healthcare and general collaboration customers. VidyoConnect Room provides streamlined workflows and a branded modern appearance that models the same look and feel as our other video collaboration products. For more information about VidyoConnect Room, refer to the VidyoConnect Room and VidyoRoom: Releases article.
• New Custom Parameters
  • Custom application developers can now centrally store parameters per tenant to build deeper integrations using Vidyo API’s.
  • These authenticated and non-authenticated parameters can be queried via REST API’s for both guest and registered users.
  • To add, edit, and view custom parameters, go to Feature Settings > Custom Parameters. 
    
• Platform APIs
  • The Platform API suite is an SSH-based set of API's that allows remote, scriptable configuration, and centralized updates.
  • You can now access the “Platform API User” option on the System Console. 
  • For more details about all the Platform APIs and Using the PlatformAPI User Option on the System Console, refer to the Platform API Support on VidyoPortal and VidyoRouter article. 
• Increase Security By Expiring Epic CAL Links
  
  • To increase security, Admins using the Epic CAL integration can now automatically expire CAL links based on the AppointmentTime in the Default CAL link validity period (minutes) field.
  • Admins may use the LinkValidityPeriod parameter in the CRYPTSTRING to customize in minutes the length of time the Epic link is valid.
  • From the Feature Settings > Epic Integrations configuration page, there is an option under the Epic Integration section to specify minutes for the Default CAL link validity period (minutes). 
  • For more information on how to use this feature, please see: Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article. 
    
    
  • For compatibility information, refer to the Epic Compatibility with Vidyo Infrastructure article.  
• Added a Retry Button to Quickly Reload Join Page 
  
  
  • Due to an existing bug in Chromium, the pop-up to open a room link with VidyoConnect may not always appear. (To access the Chromium bug, click here). In such cases, Vidyo has added a Retry button to allow users to quickly refresh the page to invoke the VidyoConnect app again.
  • As Microsoft Edge and Google Chrome are both based on Chromium, they are both affected by this bug. If you are a Chrome or Edge Chromium user, you will have an option to select the Retry button from the splash page. 
• Translations Fixed
  • Vidyo fixed several translation issues.  

Important changes and new requirements

• The VidyoPortal VE version 19.2.0 or 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.0 requires you to set the SOAPAction header for all SOAP requests or request may fail.
  • ACTIONS TO TAKE: Make sure to inspect any API integrations that may use the Vidyo Web Services API’s and validate that this header is appropriately set.
    • Also, it is highly recommended 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 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 20.2.0 and later. You must upgrade your VidyoGateway and/or VidyoReplay to a version newer than 3.5.x and 3.1.x, respectively, in order to be compatible with VidyoPortal and VidyoRouter version 20.2.0 and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article.

Important notes

 

Files

This file...	Is for...
vidyoportal-TAG_VC20_2_1_0647-bundle-v3195.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC20_2_1_0647-bundle-v3196.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 20.2.1:

VidyoPortal and VidyoRouter Version 20.2.1 - Resolved Issues
Key	Summary
VPTL-10915	An issue was resolved where the VidyoRouter would crash under a rare timing condition.
VPTL-11100	A timeout error was corrected by increasing the read timeout when connecting to slow responding Epic Interconnect servers.
VPTL-11068	An issue was fixed where the VidyoPortal incorrectly encoded %2B as a "+" in the extData after clicking the Join via browser button.
VPTL-10945	An internal configuration issue was fixed where emails were not sent for certain SMTP configurations.
VPTL-10925	An issue was resolved where the leaveConference SOAP API did not disconnect a Native WebRTC client and resulted in a 500 error. This also caused the Disconnect button for an individual participant not to function correctly via the VidyoConnect app.
VPTL-10828	After launching an Epic CAL link, some customers sometimes would receive a "404 page not found" when using an iPad with a Safari browser. This issue has since been corrected.
VPTL-10827	A bug was fixed where unsupported Samsung browsers would erroneously be presented with the Join via browser option.
VPTL-10805	An issue was resolved where the tomcat log files grew larger than was configured and took up excessive disk space.
VPTL-10776 and VPTL-10423	An issue was resolved where the VidyoManager got backed up and stopped responding during a sharp spike in join conference requests.
VPTL-10699 and VPTL-10541	An issue was fixed in VidyoPortal where the tomcat log folder included a recursive reference.
VPTL-10684	The getEntityByRoomKey response object no longer returns an incorrect 'video' field value when using hard video muting in the Control Meeting UI.
VPTL-10656	A bug was fixed where participants clicked the meeting link and were incorrectly directed to the Google Play Store instead of the meeting when using a Samsung browser.
VPTL-10571	A rare timing issue was resolved where the VidyoManager process could crash and cause conferences to drop.
VPTL-10538	A bug was resolved where sometimes a recording failed to start.
VPTL-10358	An issue was corrected and now when Hot Standby is enabled, the SNMP trap called vidyoPortalLineConsumptionThresholdExceeded is sent when triggered.
VPTL-10336	Text was localized in multiple areas.
VPTL-10319	An intermittent 500 error was fixed for SAML enabled tenants and for the Epic CAL integration.
VPTL-10213	An issue was corrected and now when Hot Standby is enabled, the SNMP vidyoPortalMgmnt OID will become available.
VPTL-9860	A bug was resolved where a SAML Portal URL launch of Outlook Add-In caused the VidyoConnect application to sign out.
VPTL-9859	An issue was corrected where only one recording started even though two recordings were initiated to the VidyoPortal via different rooms.

 

---

VidyoPortal and VidyoRouter: About Version 20.2.0 General Availability (GA)

What's new in this release 

• VidyoConnect™ Room Support
  • In this release, we’ve added server-side support for the VidyoConnect Room as our new and improved user interface (UI) for healthcare and general collaboration customers. VidyoConnect Room provides streamlined workflows and a branded modern appearance that models the same look and feel as our other video collaboration products. For more information about VidyoConnect Room, refer to the VidyoConnect Room and VidyoRoom: Releases article.
• New Custom Parameters
  • Custom application developers can now centrally store parameters per tenant to build deeper integrations using Vidyo API’s.
  • These authenticated and non-authenticated parameters can be queried via REST API’s for both guest and registered users.
  • To add, edit, and view custom parameters, go to Feature Settings > Custom Parameters. 
    
• Platform APIs
  • The Platform API suite is an SSH-based set of API's that allows remote, scriptable configuration, and centralized updates.
  • You can now access the “Platform API User” option on the System Console. 
  • For more details about all the Platform APIs and Using the PlatformAPI User Option on the System Console, refer to the Platform API Support on VidyoPortal and VidyoRouter article.
• Increase Security By Expiring Epic CAL Links
  
  • To increase security, Admins using the Epic CAL integration can now automatically expire CAL links based on the AppointmentTime in the Default CAL link validity period (minutes) field.
  • Admins may use the LinkValidityPeriod parameter in the CRYPTSTRING to customize in minutes the length of time the Epic link is valid.
  • From the Feature Settings > Epic Integrations configuration page, there is an option under the Epic Integration section to specify minutes for the Default CAL link validity period (minutes). 
  • For more information on how to use this feature, please see: Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) article. 
    
  • For compatibility information, refer to the Epic Compatibility with Vidyo Infrastructure article.  
• Added a Retry Button to Quickly Reload Join Page 
  
  
  • Due to an existing bug in Chromium, the pop-up to open a room link with VidyoConnect may not always appear. (To access the Chromium bug, click here). Vidyo has added a Retry button to allow users to quickly refresh the page to invoke the VidyoConnect app again.
  • As Microsoft Edge and Google Chrome are both based on Chromium, they are both affected by this bug. If you are a Chrome or Edge Chromium user, you will have an option to select the Retry button from the splash page. 
• Translations Fixed
  • Vidyo fixed several translation issues.  

Important changes and new requirements

• The VidyoPortal VE version 19.2.0 or 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.0 requires you to set the SOAPAction header for all SOAP requests or request may fail.
  • ACTIONS TO TAKE: Make sure to inspect any API integrations that may use the Vidyo Web Services API’s and validate that this header is appropriately set.
    • Also, it is highly recommended 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 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 20.2.0 and later. You must upgrade your VidyoGateway and/or VidyoReplay to a version newer than 3.5.x and 3.1.x, respectively, in order to be compatible with VidyoPortal and VidyoRouter version 20.2.0 and later. For help with how to upgrade, refer to the Upgrade Steps Lookup Tool article. To obtain the software package you need to download, refer to the VidyoGateway Packages or VidyoReplay Packages article. 

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC20_2_0_0647-bundle-v3193.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC20_2_0_0647-bundle-v3194.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved Issues

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 20.2.0:

VidyoPortal and VidyoRouter Version 20.2.0 - Resolved Issues
Key	Summary
VPTL-11100	A timeout error was corrected by increasing the read timeout when connecting to slow responding Epic Interconnect servers.
VPTL-11068	An issue was fixed where the VidyoPortal incorrectly encoded %2B as a "+" in the extData after clicking the Join via browser button.
VPTL-10945	An internal configuration issue was fixed where emails were not sent for certain SMTP configurations.
VPTL-10925	An issue was resolved where the leaveConference SOAP API did not disconnect a Native WebRTC client and resulted in a 500 error. This also caused the Disconnect button for an individual participant not to function correctly via the VidyoConnect app.
VPTL-10828	After launching an Epic CAL link, some customers sometimes would receive a "404 page not found" when using an iPad with a Safari browser. This issue has since been corrected.
VPTL-10827	A bug was fixed where unsupported Samsung browsers would erroneously be presented with the Join via browser option.
VPTL-10805	An issue was resolved where the tomcat log files grew larger than was configured and took up excessive disk space.
VPTL-10776 and VPTL-10423	An issue was resolved where the VidyoManager got backed up and stopped responding during a sharp spike in join conference requests.
VPTL-10699 and VPTL-10541	An issue was fixed in VidyoPortal where the tomcat log folder included a recursive reference.
VPTL-10684	The getEntityByRoomKey response object no longer returns an incorrect 'video' field value when using hard video muting in the Control Meeting UI.
VPTL-10656	A bug was fixed where participants clicked the meeting link and were incorrectly directed to the Google Play Store instead of the meeting when using a Samsung browser.
VPTL-10571	A rare timing issue was resolved where the VidyoManager process could crash and cause conferences to drop.
VPTL-10538	A bug was resolved where sometimes a recording failed to start.
VPTL-10358	An issue was corrected and now when Hot Standby is enabled, the SNMP trap called vidyoPortalLineConsumptionThresholdExceeded is sent when triggered.
VPTL-10336	Text was localized in multiple areas.
VPTL-10319	An intermittent 500 error was fixed for SAML enabled tenants and for the Epic CAL integration.
VPTL-10213	An issue was corrected and now when Hot Standby is enabled, the SNMP vidyoPortalMgmnt OID will become available.
VPTL-9860	A bug was resolved where a SAML Portal URL launch of Outlook Add-In caused the VidyoConnect application to sign out.
VPTL-9859	An issue was corrected where only one recording started even though two recordings were initiated to the VidyoPortal via different rooms.

 

---

VidyoPortal and VidyoRouter: About Version 20.1.5 Limited Availability (LA)

 

 

What's new in this release 

• Epic CAL Users on iPad® No Longer Receive 404 Errors
  • On some versions of iOS, if an iPad user clicked an Epic CAL link to join a VidyoConnect™ call, a 404 error may have been displayed. This is due to the Apple® Safari® browser switching user-agents dynamically under certain conditions. In this release, this case is accounted for by the VidyoPortal, and the user sees the Join Conference splash page rather than a 404 error.
• Correct Options Displayed for Samsung Mobile Browsers
  • Although Vidyo does not support mobile WebRTC on the Samsung browser, users were erroneously given the option to join a conference on this browser. Starting with this version, the appropriate join options are now displayed for Samsung mobile browsers.
• TURNS Support for macOS®, iPadOS®, and iOS Devices
  
  • When using the Apple Safari browser to join a conference via WebRTC, connections over secure TURN will now succeed without a certificate error.
• System Updates
  
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
  • We’ve restricted TLS/SSL cipher suite support over the Websockets and TURN interfaces in order to use AES-GCM only.

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC20_1_5_0193-bundle-v2897.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC20_1_5_0193-bundle-v2898.vidyo	VidyoRouter version 19.2.0 or later

 

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 20.1.5 LA:

VidyoPortal and VidyoRouter Version 20.1.5 LA - Resolved Issues
Key	Summary
VPTL-10847	An issue was fixed where the TURN configuration certificate was advertising an incomplete certificate chain which caused issues with Apple Safari browsers.
VPTL-10828	On some versions of iOS, if an iPad user clicked an Epic CAL link to join a VidyoConnect call, a 404 error may have been displayed. This is due to the Apple Safari browser switching user-agents dynamically under certain conditions. In this release, this case is accounted for by the VidyoPortal, and the user sees the Join Conference splash page rather than a 404 error.
VPTL-10827	Samsung mobile browsers are no longer incorrectly given the option to “Join via the browser” (WebRTC).

 

---

VidyoPortal and VidyoRouter: About Version 20.1.3 Limited Availability (LA)

 

 

What's new in this release 

• Fixed Issue with Google Chrome™ 85
  • Users can now successfully join calls when using Google Chrome version 85. Previously, some Google Chrome version 85 users experienced issues joining calls or staying connected to calls, or they received timeout errors.  
• Join Calls via a Browser on Android Devices 
  
  • Users of Android devices can now choose to join calls via their browser instead of being directly taken to the Google Play store.  

Important notes

 

Files 

This file...	Is for...
vidyoportal-TAG_VC20_1_3_0189-bundle-v2752.vidyo	VidyoPortal version 19.2.0 or later
vidyorouter-TAG_VC20_1_3_0189-bundle-v2753.vidyo	VidyoPortal version 19.2.0 or later

 

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 20.1.3 LA:

VidyoPortal and VidyoRouter Version 20.1.3 LA - Resolved Issues
Key	Summary
VPTL-10685	Enghouse Vidyo corrected an issue so users can successfully join calls when using Google Chrome version 85. Previously, some users experienced issues on Google Chrome version 85 when connecting to calls and may have received 404 timeout errors.
VPTL-10656	Android users are now given the option to join call via a browser instead of being directly taking to the Google Play store.

 

---

VidyoPortal and VidyoRouter: About Version 20.1.1 Limited Availability (LA)

 

 

What's new in this release 

• Support for Native WebRTC™
  • Enghouse Vidyo is proud to introduce Native WebRTC browser support for these mobile and desktop platforms:
    • Google Chrome™ on Windows, macOS, and Android™
    • Safari® on iOS and macOS 
  • Enabling Native WebRTC
    • To enable Native WebRTC Version 20.1.1 and later, refer to the Configuring Native WebRTC for VidyoPortal Version 20.1.1 article.  
  • Admin UI Updates
    • A Tenant Admin can configure mobile support from the Settings>Feature Settings>VidyoConnect for WebRTC page by selecting the Enable VidyoConnect for WebRTC for guests checkbox as illustrated in the screenshot below.
      
      
        
  • Benefits of Native WebRTC Support
    • Reduced costs and decreased deployment complexities without the need for a separate transcoding infrastructure.  
    • Increased density of concurrent WebRTC conferences.
    • Ability to easily conduct high participant calls without having to allocate resources in advance. 
    • Increased speed and performance to quickly join and connect WebRTC participants.
    • Improved interoperability for VidyoConnect (desktop and mobile) participants with WebRTC participants when joining calls from different browsers and platforms.
    • Support for VP9-SVC codec to automatically switch between VP9 and H.264 as needed when using VidyoConnect (desktop and mobile) version 20.1.0 or later.
• 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 1420 to address network overhead in some virtualized environments.
  • Logging has been improved for multiple components.
• 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.
• Bug Fixes and Stability Improvements
  • For more information, please refer to the "Resolved Issues" section below.  

Important notes

 

Files 

This file...	Is for...
Vidyoportal-TAG_VC20_1_1_0184-bundle-v2507.vidyo	VidyoPortal version 19.20 or later
Vidyorouter-TAG_VC20_1_1_0184-bundle-v2508.vidyo	VidyoPortal version 19.20 or later

 

Resolved issues   

The following table lists the resolved issues 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.

 

---

VidyoPortal and VidyoRouter: About Version 20.1.0

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.
• 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.
• 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.
• Resolved Issues
  • In this release, we've addressed a number of issues to improve performance, security, and internationalization. For more information, see the "Resolved Issues" section below.

Important notes 

 

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

 

Resolved issues   

The following table lists the resolved issues 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.

 

---

2019 Releases 

---

 

VidyoPortal and VidyoRouter: About Version 19.3.0 General Availability (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 for Your Needs
  
  • 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 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 iPad® OS and macOS Catalina
  • The most recent version of Apple’s Safari® for iPad OS 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.
• Bug Fixes and Stability Improvements
  • For more information, please refer to the Resolved Issues section below.
    
    

Important notes

 

Files 

This file...	Is for...
VidyoPortal-19.3.0.335-bundle-v2208c.vidyo	VidyoPortal version 19.3.0
VidyoRouter-19.3.0.335-bundle-v2210c.vidyo	VidyoRouter version 19.3.0

 

Resolved issues   

The following table lists the resolved issues 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.

 

---

VidyoPortal and VidyoRouter: About Version 19.2.0 General Availability (GA)

What's new in this release 

• Major Platform Operating System (OS) Update 
  • Enghouse Vidyo performed a major platform OS update to improve security, stability, and performance.
  • Additional benefits include:
    • Updates to most third-party libraries.
    • Continual security updates to the underlying OS.
    • Streamlined patching of third-party software components.
  • Security Update 22 was also applied in this release.
• Healthcare Feature: Moderation Support for Epic Contextual Aware Linking (CAL)
  • This version enables authenticated clinicians to invoke moderation capabilities when using the Epic CAL integration. For more information please refer to the following articles:
    • Using the Moderation Capability in the VidyoConnect for Desktop Application
    • Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL)
    • Vidyo Telehealth Solutions | Epic Integration
• Bug Fixes and Stability Improvements
  • For more information, please refer to the Resolved Issues section below.
    

Important notes

 

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 19.2.0:

VidyoPortal and VidyoRouter Version 19.2.0 - Resolved Issues
Key	Summary
VPTL-9660	Enghouse Vidyo resolved an issue so room owners are displayed in public meeting rooms.
VPTL-9659	An issue was resolved so now users can successfully click a meeting room link and get access to a call. Previously users clicked on a meeting room link, received an error, and the page didn't load.
VPTL-9619	The silenceSpeakerServerAll API no longer returns an unknown error when joining a room.
VPTL-9618	An issue was resolved that corrected the Conference Control Service dependencies to inject properly so now the silenceSpeaker APIs no longer return errors.

 

---

VidyoPortal and VidyoRouter: About Version 19.1.0 General Availability (GA) 

What's new in this release 

• TytoCare™ Integration Improved Error Messages and Logs
  
  TytoCare is a cloud-based telehealth solution that simulates a comprehensive physical examination using a portable WiFi-enabled diagnostic device. The Tyto device allows medical professionals to examine a patient at the Point of Care (POC) and broadcast the exam data to a remote clinician. When used in conjunction with the VidyoConnect™ desktop application, the remote clinician can virtually meet with the POC users via secure and reliable video conferencing.
  
  In VidyoPortal and VidyoRouter version 19.1.0, we've improved the TytoCare integration by:
  • Adding more informative error messages. For example, we now display the relevant error codes when the Connection Test is run.
  • Adding more details to the TytoCare Audit and App logs. For example, we now log the HTTP status codes for all Tyto REST API calls.

  The TytoCare integration requires version 18.4.0 or later of the VidyoPortal and VidyoRouter as well as version 19.1.0 or later of the VidyoConnect desktop application. If you are an on-premises customer, refer to the Configuring TytoCare Integration article for information about how to configure your VidyoPortal Super Admin and Tenant Admin portal for TytoCare integration.

• Control Meeting Page Icon Updates
  
  The Control Meeting page enables you to control meeting functions, such as disconnecting participants, muting participants, adding PINs, and more.
  
  
  
  • The Control Meeting page that you access from the VidyoPortal now includes the same icons that you will see in upcoming releases of the VidyoConnect application. For example, we've updated the icons that enable you to disable video  and mute audio  for all participants without allowing them to re-enable.
• Custom Invocation Support for Direct Dialing
  
  Custom Invocation enables third-party partners and developers to customize the VidyoConnect client and invoke it from their platform. With version 19.1.0, Custom Invocation now supports:
  
  • Directly dialing online users. Applications integrating with the VidyoConnect app can now embed the direct-dial links for registered users in the VidyoPortal and use those links to initiate direct-dial video calls. For more information about how to enable this workflow, see the "Direct Dial Parameter" section of the Using Custom Invocation article.
  • This feature requires version 19.2.0 or later of the VidyoConnect application.
• Resolved Issues
  
  In this release, we've resolved a number of issues, including many issues that notably enhance security and usability, such as this:
  
  • We've corrected an issue with orphaned records that occurred on the Control Meeting page. Prior to this fix, the display names of participants would turn into orphaned records 10 to 15 minutes after they joined a call. Since these records could no longer be referenced in the database, call moderators were unable to mute the participants' microphones or speakers or disconnect the participants from the calls via the Control Meeting page.

Resolved issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 19.1.0:

VidyoPortal and VidyoRouter Version 19.1.0 - Resolved Issues
Key	Summary
VPTL-9504	The VidyoPortal User and Admin API startRecording commands have been updated to prevent a recorder from joining a conference that has no other participants and to prevent more than one recorder from joining the same conference.
VPTL-9494	The VidyoReplay API getLogoForTenant Request now properly returns a logo.
VPTL-9491	On the VidyoPortal Manage Endpoint Software and Endpoint Software Versions pages, the labels were changed from "VidyoDesktop Mac OS" to "VidyoDesktop/VidyoConnect Mac OS".
VPTL-9490	Super service APIs have been optimized for increased performance with concurrent requests.
VPTL-9417	The response of the VidyoPortal Admin API GetMembers Request now contains the "proxyName" parameter.
VPTL-9382	On the Control Meeting page, the display names of participants no longer turn into orphaned records 10 to 15 minutes after the participants join a call. Since these records are no longer orphaned and can be referenced in the database, call moderators are now able to mute the participants' microphones and speakers and disconnect the participants from the calls via the Control Meeting page.
VPTL-9327	Users who log in to the portal as Operator users can now see the proper number of created users on the Admin page.
VPTL-4818	The VidyoPortal Super API updateTenant now responds properly when the tenant includes gateway information.
VPTL-1089	The Admin account receives a license expiration notification email only once (instead of twice) when each of the 45, 15, 7, and 6 day increments are left for the license expiration.

 

---

2018 Releases 

---

 

VidyoPortal and VidyoRouter: About Version 18.4.0 General Availability (GA)

 What's new in this release 

• TytoCare™ Integration 
  
  • TytoCare is a cloud-based telehealth solution that simulates a comprehensive physical examination using a portable WiFi-enabled diagnostic device. The Tyto device allows medical professionals to examine a patient at the Point of Care (POC) and broadcast the exam data to a remote clinician.
  • When used in conjunction with the VidyoConnect™ desktop application, the remote clinician can virtually meet with the POC users via secure and reliable video conferencing.
    • The integration enables the TytoCare solution to act as a robust extension of the remote clinicians’ diagnostic capabilities by allowing them to see and speak with patients while conducting virtual stethoscope, otoscope, skin, and other basic medical exams. Combined, the TytoCare Professional (TytoPro/TytoClinic) solution and the Vidyo telehealth solution provide a single cohesive workflow for telehealth providers.
  • If you are an on-premises customer, refer to the Enabling the TytoCare Integration in the Super Admin Portal and the Enabling the TytoCare Integration in the Tenant Admin Portal for information about how to configure your VidyoPortal for TytoCare integration.

  The TytoCare integration requires version 18.4.0 of the VidyoPortal and VidyoRouter as well as version 19.1.0 of the VidyoConnect desktop application.

• Epic Context-Aware Linking Integration Enhancement
  • Tenant Admins can now directly configure the Epic Context-Aware Linking (CAL) integration via the Tenant Admin portal. You are no longer required to be a Super Admin to configure Epic CAL for your Tenant.
    • For more information about Epic CAL, refer to the Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) for On-Premises and Cloud article.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.4.0:

VidyoPortal and VidyoRouter Version 18.4.0 - Resolved Issues
Key	Summary
VPTL-9354	The status of public rooms now updates properly in the VidyoDesktop contact list; therefore, users can correctly determine whether a room is in use.
VPTL-9351	The VidyoPortal Web Services Admin addMember API now supports alphanumeric values in addition to numeric values for the extension.
VPTL-9297	A VidyoPortal issue that was preventing the upgrade of VidyoDesktop clients when the upgrade prompt was displayed has been fixed.
VPTL-9279	The VidyoPortal Web Service addMember API has been corrected so a password is not mandatory.
VPTL-9259	The “Enable Encryption” button is available on the VidyoPortal Super Admin Settings > Security page regardless of the language selected for the UI.
VPTL-9258	Exporting a security bundle on VidyoPortal version 18.3.1 no longer results in an error.
VPTL-9230	Issues that occurred when endpoint updates via the Super Admin (such as timeouts or slow updates) have been resolved.
VPTL-9131	When a user joins a room with a legacy device, they can now be reliably disconnected using the leaveConference API.
VPTL-9019	User extensions that start with a 0 can now be imported properly via CSV.
VPTL-8832	In the Call Detail Records, VidyoReplay always appears as calling from the default Tenant even if a recording is initiated from more than one Tenant.
VPTL-8818 and VPTL-8348	The Status Notification server now works properly and no longer sends erroneous error messages.

 

---

VidyoPortal and VidyoRouter: About Version 18.3.1 General Availability (GA)

What's new in this release 

• Support for Opus Audio 
  
  • If you’re a healthcare provider, you’ll be happy to know that Opus audio now powers our healthcare workflows. The Opus codec is a high-quality, highly versatile codec that supports full-band audio with sampling rates up to 48 khz. In order to use the Opus audio feature, your VidyoConnect™ endpoint must support it.
• Enhanced Security
  • At Vidyo, we continually review and implement practices and procedures to safeguard your security when using our application(s). In this release, we’ve specifically made some protection improvements.
• getMembers API 
  • The query parameter in this method now only searches on the member name and not on the room extension and the room name. As an alternative, use the searchMembers API method to search for room extension and room name. Refer to pages 61-63 of the latest Web Services API User Guide.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.3.1:

VidyoPortal and VidyoRouter Version 18.3.1 - Resolved Issues
Key	Summary
VPTL-9057	An issue was fixed where VidyoDesktop/SAML login works correctly when CDN download is enabled for that Tenant.
VPTL-9056	An issue was fixed where under certain circumstances, in the Admin user interface, the Users' tab check boxes would not display.
VPTL-9053	Users can now successfully generate a meeting in a scheduled room with the correct PIN in VidyoDesktop, Chrome Plugin, etc. When joining the meeting and going into the Moderate Call page; the original email invite will have the correct extension and PIN.
VPTL-9050	When using the Epic integration notification server and modifying the notification password via the Tenant Admin UI now correctly gets saved.
VPTL-8864	The web services API’s “createRoom” from the VidyoPortalUserService and “addRoom” from the VidyoPortalAdminService now properly enforces character set validation for the "name" attribute. Requests using incorrect character sets will be rejected.
VPTL-8944	In the Current Calls page within the Super interface, the extension numbers correctly display.
VPTL-8875	The email field that is used when adding a user has been updated to prevent the Admin UI from freezing when long or complex email addresses are added.
VPTL-8839	When the VidyoDesktop™ client is downloaded from VidyoPortal version 18.1.0, it no longer gets flagged for quarantine by Symantec.
VPTL-8752	The jQuery version used by the VidyoPortal was updated as part of standard security updates.
VPTL-8747	Email addresses for user accounts are now accepted as valid when they use both upper and lower case letters (such as Test-USER@useraccount.org).
VPTL-8586	The notification users receive about their Port license expiration now includes the remaining number of days as well as the IP address. The notifications have been updated in English and in other localized languages (e.g. Traditional and Simplified Chinese, Korean, Thai).
VPTL-8577	In an effort to mitigate security vulnerabilities, CSV exports are sanitized in order to prevent Excel from executing malicious content.
VPTL-8574	An issue was fixed so users can now log in successfully after updating SAML metadata with new certificate without restarting the VidyoPortal.
VPTL-8404	An exported User csv file now correctly displays Chinese characters.
VPTL-7820	VidyoPortal audit logs now record when edits or modifications are made to existing legacy users in the system.
VPTL-6998	The WebcastURL created from VidyoPortal UI now corresponds to the result returned on a GetWebcastURLRequest call instead of displaying as blank.
VPTL-6905	When the tenant and user language are set to a language other than English and the VidyoConnect™ language is also set to that language, the Control Meeting page as viewed from VidyoConnect now appears in the selected language rather than in English.
VPTL-6407	The CSV file now correctly displays the 2 byte Chinese characters when the data is exported.
VR-814	An issue was fixed where VidyoRouters can leave up a stale TCP connection that may eventually lead to a cascade broken alert.
VR-809	A rare VidyoRouter crash that occurred due to a timing issue when participants left the conference has been resolved.
VR-807	You can now properly generate a Certificate Signing Request (CSR) from the VidyoRouter Security tab.
VR-783 and VR-780	A rare VidyoRouter crash that occurred when the system was being restarted while active calls were up has been resolved.
VR-779 and VR-757	An issue where some participants on cascaded routers experienced one-way audio no longer occurs.
VR-762	When content is shared during a call, that content no longer appears blurry when it is received by legacy systems.
VR-761	Vidyo resolved an issue where some participants in a call were occasionally unable to see all of the other participants in the call.

  

---

VidyoPortal and VidyoRouter: About Version 18.2.1 General Availability (GA)

What's new in this release 

• Enabling Integration With Your Epic Electronic Health Record (EHR) System
  
  • The Epic integration feature for Vidyo gives healthcare providers the ability to access VidyoConnect™ meetings from within their Epic EHR (Electronic Health Record) system.
  • The Super Admin can enable this feature in the Super Admin portal and then configure it for each tenant that's going to use the feature. For more information, see the Enabling Integration With Your Epic Electronic Health Record (EHR) System article.
  • Alternatively, you can enable the Epic integration feature using REST APIs. For more information, refer to version 18.2.1 of the Vidyo Web Services API User Guide.
• Resolved Issues
  • This release resolves a number of issues to improve security and usability. For more information, see the "Resolved Issues" section below.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.2.1:

VidyoPortal and VidyoRouter Version 18.2.1 - Resolved Issues
Key	Summary
VPTL-8839	When the VidyoDesktop™ client is downloaded from VidyoPortal version 18.1.0, it no longer gets flagged for quarantine by Symantec.
VPTL-8752	The jQuery version used by the VidyoPortal was updated as part of standard security updates.
VPTL-8747	Email addresses for user accounts are now accepted as valid when they use both upper- and lower-case letters (such as Test-USER@useraccount.org).
VPTL-8586	The notification users receive about their Port license expiration now includes the remaining number of days as well as the IP address. The notifications have been updated in English and in other localized languages (e.g. Traditional and Simplified Chinese, Korean, Thai).
VPTL-8577	In an effort to mitigate security vulnerabilities, CSV exports are sanitized in order to prevent Excel from executing malicious content.
VPTL-6905	When the tenant and user language are set to a language other than English and the VidyoConnect™ language is also set to that language, the Control Meeting page as viewed from VidyoConnect now appears in the selected language rather than in English.

 

---

VidyoPortal and VidyoRouter: About Version 18.2.0 General Availability (GA)

What's new in this release 

• Customizing the SIP "From" Header: InviteToConference Admin AP
  
  • You now have the ability to customize the Session Initiation Protocol (SIP) "from" header using the InviteToConference Admin or User API's. The "From" header is accessible when dialing through our VidyoGateway™.

• Resolved Issues
  • We've resolved a number of issues for enhanced system usability. Refer to the resolved issues below.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.2.0:

VidyoPortal and VidyoRouter Version 18.2.0 - Resolved Issues
Key	Summary
VPTL-8652	VidyoGateway users can now join a scheduled meeting room when entering a PIN.
VPTL-8641	When an extension is changed (e.g., telephone number) which is auto-mapped to a user; the system updates the extension correctly.
VPTL-8635	When a VidyoDesktop tenant creates a new user by enabling password complexity rules; the new user can now successfully change the password from the Password reset page.
VPTL-8634	When password complexity rules are enabled by an Administrator, a new user can now be created successfully.
VPTL-8567	When sending a VidyoRoom calendar invite with a PIN; the VidyoRemote will display Settings and the Calls tab with the correct Conference Name and Scheduled Room Extension.
VPTL-8551	The inviteToConference Admin API now works properly allowing a VidyoConnect client to initially decline a call and then accept the next notification to a call.
VPTL-8502	Select the following link to access all the articles contained within this guide: VidyoConferencing Administrator Guide.
VPTL-8477	When password complexity rules are enabled by an Administrator; users can now successfully change passwords when using browsers: Google Chrome, Firefox and Edge.
VPTL-8471	Users can now select the "Contact Support" link from the bottom section of the Vidyo Portal version 17.3.0 website: vidyocloud.com.
VPTL-8432	When using VidyoDesktop and adding members to the contact list; users can  utilize isInMyContacts parameter from searchByEntityID to have they system return only 1 contact result.
VPTL-8413	The system will now accept first names, last names and email addresses with apostrophes in the names such as O'Hara and D'Artagnan.
VPTL-8346	When sending an email invite through VidyoConnect; the email generated will display a logo image rather than an error message if a default logo was not previously uploaded for a tenant.

 

---

VidyoPortal and VidyoRouter: About Version 18.1.0 General Availability (GA)

What's new in this release 

• Fewer Digits for Scheduled Room Extensions
  
  • We've reduced the number of digits used for the scheduled room extensions that appear in the text of call invitations. Shorter extensions make it less likely for users to make a mistake when dialing.
  • For more information about this feature, see the Using the Shorter Scheduled Room Extensions Available with Portal Version 18.1.0 article.
• Performance Improvements
  
  • In this release, we’ve improved system performance, stability, and security. Additionally, we resolved some minor issues and applied fixes.

Resolved issues  

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.1.0:

VidyoPortal and VidyoRouter Version 18.1.0 - Resolved Issues
Key	Summary
VM-165	A deadlock issue that prevented users from logging in to the VidyoPortal has been fixed.
VPTL-8456	TLS 1.2-only mode can now be enforced for VidyoManager and VidyoRouter ports.
VPTL-8455	When a user makes a direct call from VidyoConnect™ and their name contains more than one space, the createScheduledRoom API no longer breaks.
VPTL-8399	The location tag now updates accordingly when the corresponding SAML attribute is modified.
VPTL-8382	Clicking the Email button within the HTML Control Meeting page to regenerate a webcast link no longer invalidates the previous webcast link. Therefore, users can now generate more than one webcast email invitation.
VPTL-8355	Public rooms can now be assigned to more than 25 users without causing the Owner field to reset.
VPTL-8353	When sending HTML and text invites, the appropriate space now displays in the organizer’s display name instead of ‘x20’,
VPTL-8347	Users no longer have to click the Moderate Call button twice within public rooms that they own to get the HTML Control Meeting page to display without prompting them for their credentials.
VPTL-8336	Corrupted characters no longer display when selecting Japanese as the default system language for both Super and Tenant Admins.
VPTL-8322	Semicolons are no longer added to the end of the VidyoDesktop™ .exe filename, which prevents tenants, who are using Internet Explorer, Windows 7, or VidyoCloud Content Delivery Networks (CDNs), from downloading it from the Settings > Manage Endpoint Software page within the Admin portal.
VPTL-8187	Fixes an issue where licenses would fail to upload.
VPTL-8181	When searching for users via the Users page in the Admin portal, the system no longer displays duplicate records in the search results on various pages.
VPTL-8166	When setting the “proxyName” parameter to any VidyoProxy, the response for the GetMembers API now includes it.
VPTL-7864	When attempting to sort users that have an “Enabled” status listed in the Enabled column via the Users page in the Admin portal, the system no longer sorts them based on the Member Name column.
VPTL-1337	SAML authentication now works when FIPS-mode is enabled.

 

---

2017 Releases

---

 

VidyoPortal and VidyoRouter: About Version 17.3.0 (38) Rev B General Availability (GA)

What's new in this release 

• Introducing VidyoConnect™
  
  • Vidyo Neo™ is now VidyoConnect, our enterprise meeting solution for team collaboration. Therefore, you’ll no longer see the Vidyo Neo name or logo in our Tenant Admin or Super Admin interface; instead, you’ll now see the new VidyoConnect name and logo.
    
    
• Resolved Issues
  
  • In this release, we’ve resolved issues to enhance system performance.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 17.3.0 (38):

VidyoPortal and VidyoRouter Version 17.3.0 (38) - Resolved Issues
Key	Summary
VPTL-8372	Meeting invitations no longer display invalid characters when the organizer’s name contains non-alphanumeric or foreign characters.
VPTL-8367	Issues that occurred when adding or creating a public meeting room (such as being able to assign a public room to only the first 25 users) have been resolved.
VPTL-7865	Email notifications are now sent when the display name contains a comma for new users that are created in the Tenant Admin portal.

    

---

VidyoPortal and VidyoRouter: About Version 17.2.0 General Availability (GA)

 What's new in this release  

• User Group Management and Room Access Control APIs
  
  • A new set of APIs lets you create, delete, and update groups, and assign the groups to rooms. Only users who belong to a group that is assigned to a room can then access that room.
    
    • For example, let’s say you create a group called the “Marketing Group” and that you have a room called the “Marketing Roadmap” room. You can assign the Marketing Group to the “Marketing Roadmap” room. By doing so, everyone who is part of the Marketing Group will be able to join conferences in the “Marketing Roadmap” room, but anyone who is not part of the Marketing Group will be denied access to that room.
  • We’ve synced this up with SAML; therefore, if you have groups configured with your third-party identity provider, we can authenticate those users through SAML and thereby provide them with access to the proper rooms.
• Enhanced Load and Capacity Endurance
  
  • In this release, we’ve made significant enhancements to ensure that our system performance and stability remains satisfactory even under peak conditions.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 17.2.0:

VidyoPortal and VidyoRouter Version 17.2.0 - Resolved Issues
Key	Summary
VPTL-8020	After an upgrade on a portal that is not multi-tenant, a new system license can now be applied without receiving the erroneous error message “License you are trying to upload is not valid for a multi-tenant system.”
VPTL-7956	Tomcat has been updated to optimize health check.
VPTL-7955	Apache server performance has been improved.
VPTL-7947	Room table queries no longer take three or more seconds to complete when the system is in an extremely busy state (such as during a sustained load test).
VPTL-7942	A UNIQUE_ID module, which will be used for correlating requests, has been added to the Apache access log and the Tomcat access log.
VPTL-7933	The font files have been replaced with optimized smaller font sizes and the mime-types have been updated to set the proper content-type headers.
VPTL-7908	Exporting and importing a portal database now preserves the SAML JKS file; therefore, the previously configured tenants for SAML are recognized.
VPTL-7901	Customized logos can now be successfully uploaded, viewed, and removed on the Super and Admin portals.
VPTL-7896	When creating a user with an email address that contains the “@” symbol, such as j.doe@company.global, the “not a valid email address” error no longer appears and the user is successfully created.

  

---

VidyoPortal and VidyoRouter: About Version 17.1.0 General Availability (GA)

What's new in this release 

Easily select the web SSL/TLS security level that’s right for you

• You can now update your web SSL/TLS settings quickly and easily using your System Console.
• We provide three security level settings, so you can choose the one that’s the right fit for your configuration:
  • Modern (TLS 1.2 or Higher): If you don’t need backward compatibility, and only need to be compatible with modern clients (such as Firefox® 27 and later and Chrome™ 30 and later), then this is the option for you. It provides a higher level of security.
  • Intermediate (TLS 1.0 or Higher): Choose this if you need to support a wide range of clients. It provides compatibility with clients as old as Firefox 1, Chrome 1, and Safari® 1.
  • Default (Default Cipher Suite/TLS 1.0 or Higher): You should choose this only if you have legacy clients and need to ensure backward compatibility. This option is compatible with clients all the way back to Windows® XP/IE6.
    
    
  • For more information, see https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility and the VidyoConferencing Administrator Guide.

Resolved issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 17.1.0:

VidyoPortal and VidyoRouter Version 17.1.0 - Resolved Issues
Key	Summary
VPTL-7346	The Admin Console now waits until the maintenance process is completed before returning back to Hot Standby menu, thereby preventing the menu from displaying the incorrect status.
VPTL-7255	The Audit logs now capture changes made on the Super Admin portal Settings > Manage Endpoint Software page.
VPTL-7170	The status-notify.log in the TCP streaming server properly updates when muting or unmuting the audio or video from the HTML Control Meeting page.
VPTL-6915	Searches for meeting room names that contain a hyphen now return results that are consistent and reliable.
VPTL-6346	After a database restore, the server does not need to be restarted in order to see the actual settings.

  

---

VidyoPortal and VidyoRouter: About Version 3.4.6 General Availability (GA)

What's new in this release 

• Support for Many More Tenants
  
  • We’ve extended the prefix length from 3 digits to 7 digits to allow for more tenants on the VidyoPortal. Now your VidyoPortal can support up to 10 million tenants instead of only 999!
• Web Service Enhancements
  
  • We now offer a new authentication method for tenants: REST Web Service authentication. This new authentication method is being offered in addition to the current SOAP authentication method.
  • For your convenience, one Super Admin user can now invoke Admin Web Services across multiple tenants.
• Notable Performance and Stability Improvements
  
  • In this release, we’ve made significant performance and stability improvements, resulting in the most stable VidyoPortal we’ve ever offered.
• Event Streaming
  
  • User-level and room-level events (like logging in, joining a room, or adding a room) can be published on a TCP stream.
  • You no longer need to poll the VidyoPortal to see what’s going on. Instead, events get pushed to you in real-time so you can immediately apply business rules to those events.
  • If you have your own conference monitoring system, this feature is especially beneficial because you can use the information for reporting, analysis, and more.
• Resolved Issue
  
  • An issue that caused the VidyoManager to enter a deadlock state under certain circumstances has been resolved.

Resolved issues  

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 3.4.6:

VidyoPortal and VidyoRouter Version 3.4.6 - Resolved Issues
Key	Summary
VM-143	An issue that caused the VidyoManager to enter a deadlock state under certain circumstances has been resolved.
VPTL-7340	When an endpoint or client is deleted from the admin/tenant side, the file no longer gets deleted; therefore, the endpoint or client is not deleted from the other tenants on the VidyoPortal.
VPTL-7331	SAML support is now available for VidyoMobile when Vidyo Neo for Desktop is uploaded and VidyoPortal version 3.4.5 or later is being used.
VPTL-7253	When the CDN is configured for a SAML tenant, the VidyoDesktop™ download now works.
VPTL-7122	The rsync2 log is being properly purged and is no longer growing at an erroneous rate.
VPTL-7115	The “offline” status now gets updated in the notification server when a user is logged out from VidyoDesktop.
VPTL-7111	Web Services authentication now works as expected, including getting a response from the VidyoPortal and being able to save the configuration.
VPTL-7101	The VidyoPortal now properly sends out New Account Notification and Forgot Password emails.
VPTL-7064	The erroneous “The page is no longer supported” message no longer appears when a user quits VidyoDesktop, clicks on a guest link to join a call, and then launches VidyoDesktop.
VPTL-7004	Deploying SAML metadata no longer causes a 500 server error.
VPTL-6468	When a new user account is created, the email notification is now received.
VR-684 and VR-683	If a user joins a call after the content has been shared from a VidyoRoom™ system, they can now see video as well as the shared content.

  

---

Important Upgrade Notices for On-Premises Customers

---

 

  To ensure that your on-premises upgrade goes smoothly:   

• For information on how to upgrade your VidyoPortal and VidyoRouter 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
• If you need to install any Security Updates, the SU packages and documentation are available from the Security Update Packages section on the Help Center.
• If you have 10,000 to 15,000 endpoints that need to download the new version from the VidyoPortal, Vidyo recommends that you host the installer on a CDN (Content Delivery Network) so your endpoints can download them from there. Since CDNs can be geo-located, downloads are typically faster. Additionally, for large-scale client distributions, impact on the VidyoPortal performance is significantly reduced.
• VidyoPortal Virtual Edition version 3.4.x and later uses more memory in order to run more efficiently than VidyoPortal Virtual Edition version 3.3.x, and therefore requires a minimum of 8 GB of memory, although 12 GB is the recommended memory allocation. Because previous versions required less memory, you may need to increase the memory allocation on your VidyoPortal Virtual Machine before upgrading.
• Refer to the Upgrading your VidyoPortal System Software article for information about how to perform the upgrade.
• Please review the "Resolved and Known Issues" section for your particular version before upgrading.
• For any major update, it is highly recommended that you back up your database before upgrading.
• If you are using VidyoPortal and VidyoRouter Virtual Edition (VE), it is recommended that you take a full system snapshot prior to upgrading.

 

---

Compatibility

---

 

Internet Browser Compatibility 

Internet Explorer®: 

• Important: When upgrading the VidyoPortal using Internet Explorer, please use version 10 or later. Alternatively, you can use another browser, such as Chrome or Firefox.
• IE 10 and 11 are supported in non-compatibility modes.   

Version Compatibility   

If your organization has an on-premises VidyoPortal (rather than a cloud subscription), refer to the Vidyo Compatibility Matrix article to determine which endpoint versions are compatible with your VidyoPortal release.

If you are using VidyoGateway version 3.5.x, please read the note below.

 

---

Known Issues

---

 

The following table lists the known issues in VidyoPortal and VidyoRouter:

VidyoPortal and VidyoRouter - Known Issues
Key	Summary
VPTL-9782	When upgrading to version 19.2.0.63, the Diagnostic Report displays the incorrect DNS server.
VPTL-9568	When selecting the Reboot button from the Super Admin (Settings>Maintenance>Restart), a "Failed to restart the Web Server" error message displays incorrectly. The system should restart instead of showing the failed message.
VPTL-9269	TytoCare integration does not work when the VidyoPortal is in FIPS mode. To avoid this issue, disable FIPS mode on the VidyoPortal in order to use the TytoCare integration.
VPTL-8852	If a new user downloads VidyoConnect for desktop from a room link, Internet Explorer may truncate the filename of the VidyoConnect installer download, thereby preventing the application from automatically connecting to the meeting after installing the application. To connect to the meeting, the user must click the guest link again.
VPTL-8539	When in FIPS mode, enabling TLS 1.2 only mode is currently not supported.
VPTL-7966	Search queries are unable to retrieve restricted groups that have special characters (such as ~, %, @, etc.) in the group name.
VPTL-7940	When a user is created locally and that user logs in to Vidyo Neo using their LDAP credentials, the user details are not imported from LDAP; therefore, if the user belongs to a restricted group, the restricted group is not created when the user logs in.
VPTL-7309	The status-notify.log in the TCP streaming server does not properly update when audio or video is muted from the HTML Control Meeting page.
VPTL-7269	If the Guest Group, Guest Proxy, and Guest Location Tag are set on the Settings > Guest Settings page, and then those values are deleted from the VidyoPortal, the Guest Group and Guest Proxy fields should then display “Default” and the Guest Proxy field should display “No Proxy”; however, all three fields display numeric values.
VPTL-7172	The status-notify.log in the TCP streaming server does not capture the Presenter Mode enable/disable status.
VPTL-7168	The status-notify.log in the TCP streaming server does not capture SAML user and room status (such as logging in and creating rooms).
VPTL-7162	The status-notify.log in the TCP streaming server does not capture creating a scheduled room.
VPTL-7160	The status-notify.log in the TCP streaming server does not capture creating a public room.
VPTL-7147	The TCP streaming server is unable to keep up with the logging of user events.
VPTL-6938	On the Settings > Maintenance > Database page in the Super Admin portal, when the Factory Defaults button is pressed, the database is restored to the factory defaults but an erroneous “Failure” error message appears.
VPTL-6900	The Cancel button does not work on the Admin portal CDR Access page.
VPTL-6862	If the Added or Uploaded drop-downs are selected on the Settings > Endpoint Software Versions page, the “Sort Ascending” and “Sort Descending” options are grayed out.
VPTL-6851	If a user clicks the Activate or Delete button on the Settings > Endpoint Software Versions page when there is nothing in the “External CDN URL” list, the erroneous message “Please select only one External URL” appears instead of a message indicating that there is no URL present or that the user must add a URL.
VPTL-6818	If an invalid External CDN URL is entered on the Endpoint Software Versions page and the user clicks the Save button, the URL is not saved; however, the system does not display an error message indicating that the URL is invalid and cannot be saved.
VPTL-6790	When the Thai language is selected as the system language, some messages continue to appear in English.
VPTL-6253	When SSL is disabled, the VidyoPortal prompts for a reboot when a new server certificate is applied.
VPTL-6199	Performing a factory default deletes the FQDN from the VidyoManager. Workaround: Restore the FQDN by going through the network interface configuration in the System Console.
VPTL-6196	When auto-provisioned LDAP users who are currently logged in get deleted from the Admin > Users page, those users should get logged off and deleted; however, occasionally, some of the users do not get logged off and/or do not get deleted.
VPTL-6143	After starting a "Force Standby" action, the Force Standby button should be inactive, but is still active.
VPTL-6071	On the Hot Standby page, the Peer Status is only updated when the page is loaded at login or when it is reloaded. Navigating to another menu on the Super Portal does not update that status indicator.
VPTL-6032	When the management interface on the VidyoGateway™ is on an alternate port (e.g., 8443), there is an extra "/" character inserted before the port number in the hyperlink on the VidyoPortal Component page.
VPTL-5392	When SSL is enabled, the erroneous message “Super Security SSL Settings have been reset…” is displayed rather than the correct “Restart is pending…” message when a reboot is cancelled after applying a client CA certificate.
VPTL-5366	When SSL is enabled, the user is not prompted to reboot the server after regenerating a self-signed certificate.
VPTL-4978	If media encryption is disabled on the VidyoPortal, it does not prompt to reboot although it must be rebooted for the setting to take effect.
VPTL-4907	When performing a restore to factory defaults, no progress bar appears. In addition, after the factory defaults are restored, the VidyoPortal does not get automatically logged off.
VPTL-4753	On the Settings > Hot Standby > Operation page, if OK is selected for Force Standby, the system stays on the Operation page after the force standby instead of navigating to the login page.
VPTL-4666	The Cancel button does not revert back to the last saved state for VidyoWeb™, VidyoMobile™, and VidyoProxy search options and syslog. Workaround: Refresh the page or click on a different tab to revert to the last saved state.
VPTL-4344	On the VidyoGateway/VidyoReplay/VidyoRecorder Components page, the Save button is disabled even after the user enters all mandatory fields. Workaround: To enable the Save button, click anywhere on the page after entering the mandatory fields.
VPTL-4133	The same legacy device cannot be added to two different tenants. The legacy device must be deleted from one tenant in order to add it to another tenant.
VPTL-4120	When a user joins a conference via IPC, that user’s status shows as Busy (as expected) but room names for that user are erroneously listed in the Room column.
VPTL-3677	Forgot Password does not function for locally authenticated Normal users if the admin or operators are LDAP authenticated.
VPTL-3623	The system restart message does not display after refreshing the browser on the Super Admin portal > Settings > Security page.
VPTL-2766	The Group Limit is not enforced when a user invites all of the participants at once.
VPTL-2444	If an existing tenant is edited to change the prefix to 0, the erroneous message “Cannot use prefix “0”. Please choose another Tenant Ext. Prefix” appears.
VPTL-2338	When a VidyoRoom™ SE is added to the VidyoPortal, it does not appear on the VidyoPortal Manage VidyoRooms page.
VPTL-1568	The Super and Admin UIs do not display the "Forgot Password" link when LDAP authentication is enabled and none of the users are selected for LDAP authentication.
VPTL-1098	After enabling the "Enforce password complexity rules", the Super Admin and Operator user types are not forced to change their passwords. Workaround: Manually update the passwords for these user types.
VPTL-976	The Audit logs may be captured in a non-sequential date and time order, may not capture log outs due to session time out, and may not capture or may incorrectly capture actions performed from the Components or Maintenance tabs.
VPTL-867	The Audit logs do not capture changes made to some of the tabs on the Settings page.
VPTL-237	When a direct call is made from a legacy device to a VidyoDesktop user and the call times out because the VidyoDesktop user does not answer, the user status is not updated to RingNoAnswer.

 

Content Sharing Known Limitation 

The following table lists the lists the known OS limitation when sharing content with VidyoConnect:

Content Sharing Known Limitation
OS	Limitation
Windows 10 and 8.1	Universal Window Platform (UWP) applications that are displayed in a window on the desktop cannot be shared. Applications that render all or part of their window’s content using Microsoft DirectComposition, such as Chrome 50 and Firefox 46, cannot be shared. Instead, the user must share the entire display.

 

VidyoPortal and VidyoRouter: About Version 19.2.0 

What's New in This Release 

• Major Platform Operating System (OS) Update 
  • Enghouse Vidyo performed a major platform OS update to improve security, stability, and performance.
  • Additional benefits include:
    • Updates to most third-party libraries.
    • Continual security updates to the underlying OS.
    • Streamlined patching of third-party software components.
  • Security Update 22 was also applied in this release.
• Healthcare Feature: Moderation Support for Epic Contextual Aware Linking (CAL)
  • This version enables authenticated clinicians to invoke moderation capabilities when using the Epic CAL integration. For more information please refer to the following articles:
    • Using the Moderation Capability in the VidyoConnect for Desktop Application
    • Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL)
    • Vidyo Telehealth Solutions | Epic Integration
• Bug Fixes and Stability Improvements
  • For more information, please refer to the Resolved Issues section below.
    

Important Notes

 

Resolved Issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 19.2.0:

VidyoPortal and VidyoRouter Version 19.2.0 - Resolved Issues
Key	Summary
VPTL-9660	Enghouse Vidyo resolved an issue so room owners are displayed in public meeting rooms.
VPTL-9659	An issue was resolved so now users can successfully click a meeting room link and get access to a call. Previously users clicked on a meeting room link, received an error, and the page didn't load.
VPTL-9619	The silenceSpeakerServerAll API no longer returns an unknown error when joining a room.
VPTL-9618	An issue was resolved that corrected the Conference Control Service dependencies to inject properly so now the silenceSpeaker APIs no longer return errors.

 

---

 

VidyoPortal and VidyoRouter: About Version 19.1.0 

What's New in This Release 

• TytoCare™ Integration Improved Error Messages and Logs
  
  TytoCare is a cloud-based telehealth solution that simulates a comprehensive physical examination using a portable WiFi-enabled diagnostic device. The Tyto device allows medical professionals to examine a patient at the Point of Care (POC) and broadcast the exam data to a remote clinician. When used in conjunction with the VidyoConnect™ desktop application, the remote clinician can virtually meet with the POC users via secure and reliable video conferencing.
  
  In VidyoPortal and VidyoRouter version 19.1.0, we've improved the TytoCare integration by:
  • Adding more informative error messages. For example, we now display the relevant error codes when the Connection Test is run.
  • Adding more details to the TytoCare Audit and App logs. For example, we now log the HTTP status codes for all Tyto REST API calls.

  The TytoCare integration requires version 18.4.0 or later of the VidyoPortal and VidyoRouter as well as version 19.1.0 or later of the VidyoConnect desktop application. If you are an on-premises customer, refer to the Configuring TytoCare Integration article for information about how to configure your VidyoPortal Super Admin and Tenant Admin portal for TytoCare integration.

• Control Meeting Page Icon Updates
  
  The Control Meeting page enables you to control meeting functions, such as disconnecting participants, muting participants, adding PINs, and more.
  
  
  
  • The Control Meeting page that you access from the VidyoPortal now includes the same icons that you will see in upcoming releases of the VidyoConnect application. For example, we've updated the icons that enable you to disable video  and mute audio  for all participants without allowing them to re-enable.
• Custom Invocation Support for Direct Dialing
  
  Custom Invocation enables third-party partners and developers to customize the VidyoConnect client and invoke it from their platform. With version 19.1.0, Custom Invocation now supports:
  
  • Directly dialing online users. Applications integrating with the VidyoConnect app can now embed the direct-dial links for registered users in the VidyoPortal and use those links to initiate direct-dial video calls. For more information about how to enable this workflow, see the "Direct Dial Parameter" section of the Using Custom Invocation article.
  • This feature requires version 19.2.0 or later of the VidyoConnect application.
• Resolved Issues
  
  In this release, we've resolved a number of issues, including many issues that notably enhance security and usability, such as this:
  
  • We've corrected an issue with orphaned records that occurred on the Control Meeting page. Prior to this fix, the display names of participants would turn into orphaned records 10 to 15 minutes after they joined a call. Since these records could no longer be referenced in the database, call moderators were unable to mute the participants' microphones or speakers or disconnect the participants from the calls via the Control Meeting page.

Resolved Issues   

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 19.1.0:

VidyoPortal and VidyoRouter Version 19.1.0 - Resolved Issues
Key	Summary
VPTL-9504	The VidyoPortal User and Admin API startRecording commands have been updated to prevent a recorder from joining a conference that has no other participants and to prevent more than one recorder from joining the same conference.
VPTL-9494	The VidyoReplay API getLogoForTenant Request now properly returns a logo.
VPTL-9491	On the VidyoPortal Manage Endpoint Software and Endpoint Software Versions pages, the labels were changed from "VidyoDesktop Mac OS" to "VidyoDesktop/VidyoConnect Mac OS".
VPTL-9490	Super service APIs have been optimized for increased performance with concurrent requests.
VPTL-9417	The response of the VidyoPortal Admin API GetMembers Request now contains the "proxyName" parameter.
VPTL-9382	On the Control Meeting page, the display names of participants no longer turn into orphaned records 10 to 15 minutes after the participants join a call. Since these records are no longer orphaned and can be referenced in the database, call moderators are now able to mute the participants' microphones and speakers and disconnect the participants from the calls via the Control Meeting page.
VPTL-9327	Users who log in to the portal as Operator users can now see the proper number of created users on the Admin page.
VPTL-4818	The VidyoPortal Super API updateTenant now responds properly when the tenant includes gateway information.
VPTL-1089	The Admin account receives a license expiration notification email only once (instead of twice) when each of the 45, 15, 7, and 6 day increments are left for the license expiration.

 

---

2018 Releases 

---

 

VidyoPortal and VidyoRouter: About Version 18.4.0

 What's New in this Release 

• TytoCare™ Integration 
  
  • TytoCare is a cloud-based telehealth solution that simulates a comprehensive physical examination using a portable WiFi-enabled diagnostic device. The Tyto device allows medical professionals to examine a patient at the Point of Care (POC) and broadcast the exam data to a remote clinician.
  • When used in conjunction with the VidyoConnect™ desktop application, the remote clinician can virtually meet with the POC users via secure and reliable video conferencing.
    • The integration enables the TytoCare solution to act as a robust extension of the remote clinicians’ diagnostic capabilities by allowing them to see and speak with patients while conducting virtual stethoscope, otoscope, skin, and other basic medical exams. Combined, the TytoCare Professional (TytoPro/TytoClinic) solution and the Vidyo telehealth solution provide a single cohesive workflow for telehealth providers.
  • If you are an on-premises customer, refer to the Enabling the TytoCare Integration in the Super Admin Portal and the Enabling the TytoCare Integration in the Tenant Admin Portal for information about how to configure your VidyoPortal for TytoCare integration.

  The TytoCare integration requires version 18.4.0 of the VidyoPortal and VidyoRouter as well as version 19.1.0 of the VidyoConnect desktop application.

• Epic Context-Aware Linking Integration Enhancement
  • Tenant Admins can now directly configure the Epic Context-Aware Linking (CAL) integration via the Tenant Admin portal. You are no longer required to be a Super Admin to configure Epic CAL for your Tenant.
    • For more information about Epic CAL, refer to the Vidyo and Epic Integration with VidyoConnect Context-Aware Linking (CAL) for On-Premises and Cloud article.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.4.0:

VidyoPortal and VidyoRouter Version 18.4.0 - Resolved Issues
Key	Summary
VPTL-9354	The status of public rooms now updates properly in the VidyoDesktop contact list; therefore, users can correctly determine whether a room is in use.
VPTL-9351	The VidyoPortal Web Services Admin addMember API now supports alphanumeric values in addition to numeric values for the extension.
VPTL-9297	A VidyoPortal issue that was preventing the upgrade of VidyoDesktop clients when the upgrade prompt was displayed has been fixed.
VPTL-9279	The VidyoPortal Web Service addMember API has been corrected so a password is not mandatory.
VPTL-9259	The “Enable Encryption” button is available on the VidyoPortal Super Admin Settings > Security page regardless of the language selected for the UI.
VPTL-9258	Exporting a security bundle on VidyoPortal version 18.3.1 no longer results in an error.
VPTL-9230	Issues that occurred when endpoint updates via the Super Admin (such as timeouts or slow updates) have been resolved.
VPTL-9131	When a user joins a room with a legacy device, they can now be reliably disconnected using the leaveConference API.
VPTL-9019	User extensions that start with a 0 can now be imported properly via CSV.
VPTL-8832	In the Call Detail Records, VidyoReplay always appears as calling from the default Tenant even if a recording is initiated from more than one Tenant.
VPTL-8818 and VPTL-8348	The Status Notification server now works properly and no longer sends erroneous error messages.

 

---

 

VidyoPortal and VidyoRouter: About Version 18.3.1 

What's New in this Release 

• Support for Opus Audio 
  
  • If you’re a healthcare provider, you’ll be happy to know that Opus audio now powers our healthcare workflows. The Opus codec is a high-quality, highly versatile codec that supports full-band audio with sampling rates up to 48 khz. In order to use the Opus audio feature, your VidyoConnect™ endpoint must support it.
• Enhanced Security
  • At Vidyo, we continually review and implement practices and procedures to safeguard your security when using our application(s). In this release, we’ve specifically made some protection improvements.
• getMembers API 
  • The query parameter in this method now only searches on the member name and not on the room extension and the room name. As an alternative, use the searchMembers API method to search for room extension and room name. Refer to pages 61-63 of the latest Web Services API User Guide.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.3.1:

VidyoPortal and VidyoRouter Version 18.3.1 - Resolved Issues
Key	Summary
VPTL-9057	An issue was fixed where VidyoDesktop/SAML login works correctly when CDN download is enabled for that Tenant.
VPTL-9056	An issue was fixed where under certain circumstances, in the Admin user interface, the Users' tab check boxes would not display.
VPTL-9053	Users can now successfully generate a meeting in a scheduled room with the correct PIN in VidyoDesktop, Chrome Plugin, etc. When joining the meeting and going into the Moderate Call page; the original email invite will have the correct extension and PIN.
VPTL-9050	When using the Epic integration notification server and modifying the notification password via the Tenant Admin UI now correctly gets saved.
VPTL-8864	The web services API’s “createRoom” from the VidyoPortalUserService and “addRoom” from the VidyoPortalAdminService now properly enforces character set validation for the "name" attribute. Requests using incorrect character sets will be rejected.
VPTL-8944	In the Current Calls page within the Super interface, the extension numbers correctly display.
VPTL-8875	The email field that is used when adding a user has been updated to prevent the Admin UI from freezing when long or complex email addresses are added.
VPTL-8839	When the VidyoDesktop™ client is downloaded from VidyoPortal version 18.1.0, it no longer gets flagged for quarantine by Symantec.
VPTL-8752	The jQuery version used by the VidyoPortal was updated as part of standard security updates.
VPTL-8747	Email addresses for user accounts are now accepted as valid when they use both upper and lower case letters (such as Test-USER@useraccount.org).
VPTL-8586	The notification users receive about their Port license expiration now includes the remaining number of days as well as the IP address. The notifications have been updated in English and in other localized languages (e.g. Traditional and Simplified Chinese, Korean, Thai).
VPTL-8577	In an effort to mitigate security vulnerabilities, CSV exports are sanitized in order to prevent Excel from executing malicious content.
VPTL-8574	An issue was fixed so users can now log in successfully after updating SAML metadata with new certificate without restarting the VidyoPortal.
VPTL-8404	An exported User csv file now correctly displays Chinese characters.
VPTL-7820	VidyoPortal audit logs now record when edits or modifications are made to existing legacy users in the system.
VPTL-6998	The WebcastURL created from VidyoPortal UI now corresponds to the result returned on a GetWebcastURLRequest call instead of displaying as blank.
VPTL-6905	When the tenant and user language are set to a language other than English and the VidyoConnect™ language is also set to that language, the Control Meeting page as viewed from VidyoConnect now appears in the selected language rather than in English.
VPTL-6407	The CSV file now correctly displays the 2 byte Chinese characters when the data is exported.
VR-814	An issue was fixed where VidyoRouters can leave up a stale TCP connection that may eventually lead to a cascade broken alert.
VR-809	A rare VidyoRouter crash that occurred due to a timing issue when participants left the conference has been resolved.
VR-807	You can now properly generate a Certificate Signing Request (CSR) from the VidyoRouter Security tab.
VR-783 and VR-780	A rare VidyoRouter crash that occurred when the system was being restarted while active calls were up has been resolved.
VR-779 and VR-757	An issue where some participants on cascaded routers experienced one-way audio no longer occurs.
VR-762	When content is shared during a call, that content no longer appears blurry when it is received by legacy systems.
VR-761	Vidyo resolved an issue where some participants in a call were occasionally unable to see all of the other participants in the call.

  

---

 

VidyoPortal and VidyoRouter: About Version 18.2.1 

What's New in this Release 

• Enabling Integration With Your Epic Electronic Health Record (EHR) System
  
  • The Epic integration feature for Vidyo gives healthcare providers the ability to access VidyoConnect™ meetings from within their Epic EHR (Electronic Health Record) system.
  • The Super Admin can enable this feature in the Super Admin portal and then configure it for each tenant that's going to use the feature. For more information, see the Enabling Integration With Your Epic Electronic Health Record (EHR) System article.
  • Alternatively, you can enable the Epic integration feature using REST APIs. For more information, refer to version 18.2.1 of the Vidyo Web Services API User Guide.
• Resolved Issues
  • This release resolves a number of issues to improve security and usability. For more information, see the "Resolved Issues" section below.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.2.1:

VidyoPortal and VidyoRouter Version 18.2.1 - Resolved Issues
Key	Summary
VPTL-8839	When the VidyoDesktop™ client is downloaded from VidyoPortal version 18.1.0, it no longer gets flagged for quarantine by Symantec.
VPTL-8752	The jQuery version used by the VidyoPortal was updated as part of standard security updates.
VPTL-8747	Email addresses for user accounts are now accepted as valid when they use both upper- and lower-case letters (such as Test-USER@useraccount.org).
VPTL-8586	The notification users receive about their Port license expiration now includes the remaining number of days as well as the IP address. The notifications have been updated in English and in other localized languages (e.g. Traditional and Simplified Chinese, Korean, Thai).
VPTL-8577	In an effort to mitigate security vulnerabilities, CSV exports are sanitized in order to prevent Excel from executing malicious content.
VPTL-6905	When the tenant and user language are set to a language other than English and the VidyoConnect™ language is also set to that language, the Control Meeting page as viewed from VidyoConnect now appears in the selected language rather than in English.

 

---

 

VidyoPortal and VidyoRouter: About Version 18.2.0 

What's New in this Release 

• Customizing the SIP "From" Header: InviteToConference Admin AP
  
  • You now have the ability to customize the Session Initiation Protocol (SIP) "from" header using the InviteToConference Admin or User API's. The "From" header is accessible when dialing through our VidyoGateway™.

• Resolved Issues
  • We've resolved a number of issues for enhanced system usability. Refer to the resolved issues below.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.2.0:

VidyoPortal and VidyoRouter Version 18.2.0 - Resolved Issues
Key	Summary
VPTL-8652	VidyoGateway users can now join a scheduled meeting room when entering a PIN.
VPTL-8641	When an extension is changed (e.g., telephone number) which is auto-mapped to a user; the system updates the extension correctly.
VPTL-8635	When a VidyoDesktop tenant creates a new user by enabling password complexity rules; the new user can now successfully change the password from the Password reset page.
VPTL-8634	When password complexity rules are enabled by an Administrator, a new user can now be created successfully.
VPTL-8567	When sending a VidyoRoom calendar invite with a PIN; the VidyoRemote will display Settings and the Calls tab with the correct Conference Name and Scheduled Room Extension.
VPTL-8551	The inviteToConference Admin API now works properly allowing a VidyoConnect client to initially decline a call and then accept the next notification to a call.
VPTL-8502	Select the following link to access all the articles contained within this guide: VidyoConferencing Administrator Guide.
VPTL-8477	When password complexity rules are enabled by an Administrator; users can now successfully change passwords when using browsers: Google Chrome, Firefox and Edge.
VPTL-8471	Users can now select the "Contact Support" link from the bottom section of the Vidyo Portal version 17.3.0 website: vidyocloud.com.
VPTL-8432	When using VidyoDesktop and adding members to the contact list; users can  utilize isInMyContacts parameter from searchByEntityID to have they system return only 1 contact result.
VPTL-8413	The system will now accept first names, last names and email addresses with apostrophes in the names such as O'Hara and D'Artagnan.
VPTL-8346	When sending an email invite through VidyoConnect; the email generated will display a logo image rather than an error message if a default logo was not previously uploaded for a tenant.

 

---

 

VidyoPortal and VidyoRouter: About Version 18.1.0  

What's New in this Release 

• Fewer Digits for Scheduled Room Extensions
  
  • We've reduced the number of digits used for the scheduled room extensions that appear in the text of call invitations. Shorter extensions make it less likely for users to make a mistake when dialing.
  • For more information about this feature, see the Using the Shorter Scheduled Room Extensions Available with Portal Version 18.1.0 article.
• Performance Improvements
  
  • In this release, we’ve improved system performance, stability, and security. Additionally, we resolved some minor issues and applied fixes.

Resolved Issues  

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 18.1.0:

VidyoPortal and VidyoRouter Version 18.1.0 - Resolved Issues
Key	Summary
VM-165	A deadlock issue that prevented users from logging in to the VidyoPortal has been fixed.
VPTL-8456	TLS 1.2-only mode can now be enforced for VidyoManager and VidyoRouter ports.
VPTL-8455	When a user makes a direct call from VidyoConnect™ and their name contains more than one space, the createScheduledRoom API no longer breaks.
VPTL-8399	The location tag now updates accordingly when the corresponding SAML attribute is modified.
VPTL-8382	Clicking the Email button within the HTML Control Meeting page to regenerate a webcast link no longer invalidates the previous webcast link. Therefore, users can now generate more than one webcast email invitation.
VPTL-8355	Public rooms can now be assigned to more than 25 users without causing the Owner field to reset.
VPTL-8353	When sending HTML and text invites, the appropriate space now displays in the organizer’s display name instead of ‘x20’,
VPTL-8347	Users no longer have to click the Moderate Call button twice within public rooms that they own to get the HTML Control Meeting page to display without prompting them for their credentials.
VPTL-8336	Corrupted characters no longer display when selecting Japanese as the default system language for both Super and Tenant Admins.
VPTL-8322	Semicolons are no longer added to the end of the VidyoDesktop™ .exe filename, which prevents tenants, who are using Internet Explorer, Windows 7, or VidyoCloud Content Delivery Networks (CDNs), from downloading it from the Settings > Manage Endpoint Software page within the Admin portal.
VPTL-8187	Fixes an issue where licenses would fail to upload.
VPTL-8181	When searching for users via the Users page in the Admin portal, the system no longer displays duplicate records in the search results on various pages.
VPTL-8166	When setting the “proxyName” parameter to any VidyoProxy, the response for the GetMembers API now includes it.
VPTL-7864	When attempting to sort users that have an “Enabled” status listed in the Enabled column via the Users page in the Admin portal, the system no longer sorts them based on the Member Name column.
VPTL-1337	SAML authentication now works when FIPS-mode is enabled.

 

---

2017 Releases

---

 

VidyoPortal and VidyoRouter: About Version 17.3.0 (38) Rev B

What's New in this Release 

• Introducing VidyoConnect™
  
  • Vidyo Neo™ is now VidyoConnect, our enterprise meeting solution for team collaboration. Therefore, you’ll no longer see the Vidyo Neo name or logo in our Tenant Admin or Super Admin interface; instead, you’ll now see the new VidyoConnect name and logo.
    
    
• Resolved Issues
  
  • In this release, we’ve resolved issues to enhance system performance.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 17.3.0 (38):

VidyoPortal and VidyoRouter Version 17.3.0 (38) - Resolved Issues
Key	Summary
VPTL-8372	Meeting invitations no longer display invalid characters when the organizer’s name contains non-alphanumeric or foreign characters.
VPTL-8367	Issues that occurred when adding or creating a public meeting room (such as being able to assign a public room to only the first 25 users) have been resolved.
VPTL-7865	Email notifications are now sent when the display name contains a comma for new users that are created in the Tenant Admin portal.

    

---

 

VidyoPortal and VidyoRouter: About Version 17.2.0

 What's New in this Release  

• User Group Management and Room Access Control APIs
  
  • A new set of APIs lets you create, delete, and update groups, and assign the groups to rooms. Only users who belong to a group that is assigned to a room can then access that room.
    
    • For example, let’s say you create a group called the “Marketing Group” and that you have a room called the “Marketing Roadmap” room. You can assign the Marketing Group to the “Marketing Roadmap” room. By doing so, everyone who is part of the Marketing Group will be able to join conferences in the “Marketing Roadmap” room, but anyone who is not part of the Marketing Group will be denied access to that room.
  • We’ve synced this up with SAML; therefore, if you have groups configured with your third-party identity provider, we can authenticate those users through SAML and thereby provide them with access to the proper rooms.
• Enhanced Load and Capacity Endurance
  
  • In this release, we’ve made significant enhancements to ensure that our system performance and stability remains satisfactory even under peak conditions.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 17.2.0:

VidyoPortal and VidyoRouter Version 17.2.0 - Resolved Issues
Key	Summary
VPTL-8020	After an upgrade on a portal that is not multi-tenant, a new system license can now be applied without receiving the erroneous error message “License you are trying to upload is not valid for a multi-tenant system.”
VPTL-7956	Tomcat has been updated to optimize health check.
VPTL-7955	Apache server performance has been improved.
VPTL-7947	Room table queries no longer take three or more seconds to complete when the system is in an extremely busy state (such as during a sustained load test).
VPTL-7942	A UNIQUE_ID module, which will be used for correlating requests, has been added to the Apache access log and the Tomcat access log.
VPTL-7933	The font files have been replaced with optimized smaller font sizes and the mime-types have been updated to set the proper content-type headers.
VPTL-7908	Exporting and importing a portal database now preserves the SAML JKS file; therefore, the previously configured tenants for SAML are recognized.
VPTL-7901	Customized logos can now be successfully uploaded, viewed, and removed on the Super and Admin portals.
VPTL-7896	When creating a user with an email address that contains the “@” symbol, such as j.doe@company.global, the “not a valid email address” error no longer appears and the user is successfully created.

  

---

 

VidyoPortal and VidyoRouter: About Version 17.1.0 

What's New in this Release 

Easily select the web SSL/TLS security level that’s right for you

• You can now update your web SSL/TLS settings quickly and easily using your System Console.
• We provide three security level settings, so you can choose the one that’s the right fit for your configuration:
  • Modern (TLS 1.2 or Higher): If you don’t need backward compatibility, and only need to be compatible with modern clients (such as Firefox® 27 and later and Chrome™ 30 and later), then this is the option for you. It provides a higher level of security.
  • Intermediate (TLS 1.0 or Higher): Choose this if you need to support a wide range of clients. It provides compatibility with clients as old as Firefox 1, Chrome 1, and Safari® 1.
  • Default (Default Cipher Suite/TLS 1.0 or Higher): You should choose this only if you have legacy clients and need to ensure backward compatibility. This option is compatible with clients all the way back to Windows® XP/IE6.
    
    
  • For more information, see https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility and the VidyoConferencing Administrator Guide.

Resolved Issues 

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 17.1.0:

VidyoPortal and VidyoRouter Version 17.1.0 - Resolved Issues
Key	Summary
VPTL-7346	The Admin Console now waits until the maintenance process is completed before returning back to Hot Standby menu, thereby preventing the menu from displaying the incorrect status.
VPTL-7255	The Audit logs now capture changes made on the Super Admin portal Settings > Manage Endpoint Software page.
VPTL-7170	The status-notify.log in the TCP streaming server properly updates when muting or unmuting the audio or video from the HTML Control Meeting page.
VPTL-6915	Searches for meeting room names that contain a hyphen now return results that are consistent and reliable.
VPTL-6346	After a database restore, the server does not need to be restarted in order to see the actual settings.

  

---

 

VidyoPortal and VidyoRouter: About Version 3.4.6  

What's New in this Release 

• Support for Many More Tenants
  
  • We’ve extended the prefix length from 3 digits to 7 digits to allow for more tenants on the VidyoPortal. Now your VidyoPortal can support up to 10 million tenants instead of only 999!
• Web Service Enhancements
  
  • We now offer a new authentication method for tenants: REST Web Service authentication. This new authentication method is being offered in addition to the current SOAP authentication method.
  • For your convenience, one Super Admin user can now invoke Admin Web Services across multiple tenants.
• Notable Performance and Stability Improvements
  
  • In this release, we’ve made significant performance and stability improvements, resulting in the most stable VidyoPortal we’ve ever offered.
• Event Streaming
  
  • User-level and room-level events (like logging in, joining a room, or adding a room) can be published on a TCP stream.
  • You no longer need to poll the VidyoPortal to see what’s going on. Instead, events get pushed to you in real-time so you can immediately apply business rules to those events.
  • If you have your own conference monitoring system, this feature is especially beneficial because you can use the information for reporting, analysis, and more.
• Resolved Issue
  
  • An issue that caused the VidyoManager to enter a deadlock state under certain circumstances has been resolved.

Resolved Issues  

The following table lists the resolved issues in VidyoPortal and VidyoRouter version 3.4.6:

VidyoPortal and VidyoRouter Version 3.4.6 - Resolved Issues
Key	Summary
VM-143	An issue that caused the VidyoManager to enter a deadlock state under certain circumstances has been resolved.
VPTL-7340	When an endpoint or client is deleted from the admin/tenant side, the file no longer gets deleted; therefore, the endpoint or client is not deleted from the other tenants on the VidyoPortal.
VPTL-7331	SAML support is now available for VidyoMobile when Vidyo Neo for Desktop is uploaded and VidyoPortal version 3.4.5 or later is being used.
VPTL-7253	When the CDN is configured for a SAML tenant, the VidyoDesktop™ download now works.
VPTL-7122	The rsync2 log is being properly purged and is no longer growing at an erroneous rate.
VPTL-7115	The “offline” status now gets updated in the notification server when a user is logged out from VidyoDesktop.
VPTL-7111	Web Services authentication now works as expected, including getting a response from the VidyoPortal and being able to save the configuration.
VPTL-7101	The VidyoPortal now properly sends out New Account Notification and Forgot Password emails.
VPTL-7064	The erroneous “The page is no longer supported” message no longer appears when a user quits VidyoDesktop, clicks on a guest link to join a call, and then launches VidyoDesktop.
VPTL-7004	Deploying SAML metadata no longer causes a 500 server error.
VPTL-6468	When a new user account is created, the email notification is now received.
VR-684 and VR-683	If a user joins a call after the content has been shared from a VidyoRoom™ system, they can now see video as well as the shared content.

  

---

Important Upgrade Notices for On-Premises Customers

---

 

  To ensure that your on-premises upgrade goes smoothly:   

• For information on how to upgrade your VidyoPortal and VidyoRouter 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.
• If you need to install any Security Updates, the SU packages and documentation are available from the Security Update Packages section on the Help Center.
• If you have 10,000 to 15,000 endpoints that need to download the new version from the VidyoPortal, Vidyo recommends that you host the installer on a CDN (Content Delivery Network) so your endpoints can download them from there. Since CDNs can be geo-located, downloads are typically faster. Additionally, for large-scale client distributions, impact on the VidyoPortal performance is significantly reduced.
• VidyoPortal Virtual Edition version 3.4.x and later uses more memory in order to run more efficiently than VidyoPortal Virtual Edition version 3.3.x, and therefore requires a minimum of 8 GB of memory, although 12 GB is the recommended memory allocation. Because previous versions required less memory, you may need to increase the memory allocation on your VidyoPortal Virtual Machine before upgrading.
• Refer to the Upgrading your VidyoPortal System Software article for information about how to perform the upgrade.
• Please review the "Resolved and Known Issues" section for your particular version before upgrading.
• For any major update, it is highly recommended that you back up your database before upgrading.
• If you are using VidyoPortal and VidyoRouter Virtual Edition (VE), it is recommended that you take a full system snapshot prior to upgrading.

 

---

Compatibility

---

 

Internet Browser Compatibility 

Internet Explorer®: 

• Important: When upgrading the VidyoPortal using Internet Explorer, please use version 10 or later. Alternatively, you can use another browser, such as Chrome or Firefox.
• IE 10 and 11 are supported in non-compatibility modes.   

Version Compatibility   

If your organization has an on-premises VidyoPortal (rather than a cloud subscription), refer to the Vidyo Compatibility Matrix article to determine which endpoint versions are compatible with your VidyoPortal release.

If you are using VidyoGateway version 3.5.x, please read the note below.

 

---

 

Known Issues

---

The following table lists the known issues in VidyoPortal and VidyoRouter:

VidyoPortal and VidyoRouter - Known Issues
Key	Summary
VPTL-9782	When upgrading to version 19.2.0.63, the Diagnostic Report displays the incorrect DNS server.
VPTL-9568	When selecting the Reboot button from the Super Admin (Settings>Maintenance>Restart), a "Failed to restart the Web Server" error message displays incorrectly. The system should restart instead of showing the failed message.
VPTL-9269	TytoCare integration does not work when the VidyoPortal is in FIPS mode. To avoid this issue, disable FIPS mode on the VidyoPortal in order to use the TytoCare integration.
VPTL-8852	If a new user downloads VidyoConnect for desktop from a room link, Internet Explorer may truncate the filename of the VidyoConnect installer download, thereby preventing the application from automatically connecting to the meeting after installing the application. To connect to the meeting, the user must click the guest link again.
VPTL-8539	When in FIPS mode, enabling TLS 1.2 only mode is currently not supported.
VPTL-7966	Search queries are unable to retrieve restricted groups that have special characters (such as ~, %, @, etc.) in the group name.
VPTL-7940	When a user is created locally and that user logs in to Vidyo Neo using their LDAP credentials, the user details are not imported from LDAP; therefore, if the user belongs to a restricted group, the restricted group is not created when the user logs in.
VPTL-7309	The status-notify.log in the TCP streaming server does not properly update when audio or video is muted from the HTML Control Meeting page.
VPTL-7269	If the Guest Group, Guest Proxy, and Guest Location Tag are set on the Settings > Guest Settings page, and then those values are deleted from the VidyoPortal, the Guest Group and Guest Proxy fields should then display “Default” and the Guest Proxy field should display “No Proxy”; however, all three fields display numeric values.
VPTL-7172	The status-notify.log in the TCP streaming server does not capture the Presenter Mode enable/disable status.
VPTL-7168	The status-notify.log in the TCP streaming server does not capture SAML user and room status (such as logging in and creating rooms).
VPTL-7162	The status-notify.log in the TCP streaming server does not capture creating a scheduled room.
VPTL-7160	The status-notify.log in the TCP streaming server does not capture creating a public room.
VPTL-7147	The TCP streaming server is unable to keep up with the logging of user events.
VPTL-6938	On the Settings > Maintenance > Database page in the Super Admin portal, when the Factory Defaults button is pressed, the database is restored to the factory defaults but an erroneous “Failure” error message appears.
VPTL-6900	The Cancel button does not work on the Admin portal CDR Access page.
VPTL-6862	If the Added or Uploaded drop-downs are selected on the Settings > Endpoint Software Versions page, the “Sort Ascending” and “Sort Descending” options are grayed out.
VPTL-6851	If a user clicks the Activate or Delete button on the Settings > Endpoint Software Versions page when there is nothing in the “External CDN URL” list, the erroneous message “Please select only one External URL” appears instead of a message indicating that there is no URL present or that the user must add a URL.
VPTL-6818	If an invalid External CDN URL is entered on the Endpoint Software Versions page and the user clicks the Save button, the URL is not saved; however, the system does not display an error message indicating that the URL is invalid and cannot be saved.
VPTL-6790	When the Thai language is selected as the system language, some messages continue to appear in English.
VPTL-6253	When SSL is disabled, the VidyoPortal prompts for a reboot when a new server certificate is applied.
VPTL-6199	Performing a factory default deletes the FQDN from the VidyoManager. Workaround: Restore the FQDN by going through the network interface configuration in the System Console.
VPTL-6196	When auto-provisioned LDAP users who are currently logged in get deleted from the Admin > Users page, those users should get logged off and deleted; however, occasionally, some of the users do not get logged off and/or do not get deleted.
VPTL-6143	After starting a "Force Standby" action, the Force Standby button should be inactive, but is still active.
VPTL-6071	On the Hot Standby page, the Peer Status is only updated when the page is loaded at login or when it is reloaded. Navigating to another menu on the Super Portal does not update that status indicator.
VPTL-6032	When the management interface on the VidyoGateway™ is on an alternate port (e.g., 8443), there is an extra "/" character inserted before the port number in the hyperlink on the VidyoPortal Component page.
VPTL-5392	When SSL is enabled, the erroneous message “Super Security SSL Settings have been reset…” is displayed rather than the correct “Restart is pending…” message when a reboot is cancelled after applying a client CA certificate.
VPTL-5366	When SSL is enabled, the user is not prompted to reboot the server after regenerating a self-signed certificate.
VPTL-4978	If media encryption is disabled on the VidyoPortal, it does not prompt to reboot although it must be rebooted for the setting to take effect.
VPTL-4907	When performing a restore to factory defaults, no progress bar appears. In addition, after the factory defaults are restored, the VidyoPortal does not get automatically logged off.
VPTL-4753	On the Settings > Hot Standby > Operation page, if OK is selected for Force Standby, the system stays on the Operation page after the force standby instead of navigating to the login page.
VPTL-4666	The Cancel button does not revert back to the last saved state for VidyoWeb™, VidyoMobile™, and VidyoProxy search options and syslog. Workaround: Refresh the page or click on a different tab to revert to the last saved state.
VPTL-4344	On the VidyoGateway/VidyoReplay/VidyoRecorder Components page, the Save button is disabled even after the user enters all mandatory fields. Workaround: To enable the Save button, click anywhere on the page after entering the mandatory fields.
VPTL-4133	The same legacy device cannot be added to two different tenants. The legacy device must be deleted from one tenant in order to add it to another tenant.
VPTL-4120	When a user joins a conference via IPC, that user’s status shows as Busy (as expected) but room names for that user are erroneously listed in the Room column.
VPTL-3677	Forgot Password does not function for locally authenticated Normal users if the admin or operators are LDAP authenticated.
VPTL-3623	The system restart message does not display after refreshing the browser on the Super Admin portal > Settings > Security page.
VPTL-2766	The Group Limit is not enforced when a user invites all of the participants at once.
VPTL-2444	If an existing tenant is edited to change the prefix to 0, the erroneous message “Cannot use prefix “0”. Please choose another Tenant Ext. Prefix” appears.
VPTL-2338	When a VidyoRoom™ SE is added to the VidyoPortal, it does not appear on the VidyoPortal Manage VidyoRooms page.
VPTL-1568	The Super and Admin UIs do not display the "Forgot Password" link when LDAP authentication is enabled and none of the users are selected for LDAP authentication.
VPTL-1098	After enabling the "Enforce password complexity rules", the Super Admin and Operator user types are not forced to change their passwords. Workaround: Manually update the passwords for these user types.
VPTL-976	The Audit logs may be captured in a non-sequential date and time order, may not capture log outs due to session time out, and may not capture or may incorrectly capture actions performed from the Components or Maintenance tabs.
VPTL-867	The Audit logs do not capture changes made to some of the tabs on the Settings page.
VPTL-237	When a direct call is made from a legacy device to a VidyoDesktop user and the call times out because the VidyoDesktop user does not answer, the user status is not updated to RingNoAnswer.

 

Content Sharing Known Limitation 

The following table lists the lists the known OS limitation when sharing content with VidyoConnect:

Content Sharing Known Limitation
OS	Limitation
Windows 10 and 8.1	Universal Window Platform (UWP) applications that are displayed in a window on the desktop cannot be shared. Applications that render all or part of their window’s content using Microsoft DirectComposition, such as Chrome 50 and Firefox 46, cannot be shared. Instead, the user must share the entire display.