What's New in this Release
Here's 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.
Important Notices for On-Premise Customers
To ensure that your on-premise upgrade goes smoothly
- You must upgrade to VidyoPortal and VidyoRouter version 18.1.0 from version 17.x or 3.4.6. Upgrades from versions earlier than 3.4.6 are not supported. Therefore, if you have a VidyoPortal version that is earlier than 3.4.6, you must first upgrade to 3.4.6 and then upgrade to version 18.1.0.
- You must apply Security Update 17 (SU17) to your VidyoPortal before you upgrade to version 18.1.0. The SU17 package 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. 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 in this article before upgrading.
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 mode.
If your organization has an on-premise VidyoPortal (rather than a cloud subscription), refer to the Vidyo Compatibility Matrix article to determine which endpoint versions are compatible with your VidyoPortal release.
Resolved and Known 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|
|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.|
The following table lists the known issues in VidyoPortal and VidyoRouter version 18.1.0:
|VidyoPortal and VidyoRouter Version 18.1.0 - Known Issues|
|VPTL-8539||When both SAML and FIPS-mode are enabled, TLS 1.2-only mode does not work because the VidyoPortal is unable to communicate to the VidyoManager.|
|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-6905||When the tenant and user language are set to a language other than English and the VidyoDesktop™ language is also set to that language, the Control Meeting page as viewed from VidyoDesktop may appear in English rather than in the selected language.|
|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.|
When SSL is disabled, the VidyoPortal prompts for a reboot when a new server certificate is applied.
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.|
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.
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.
|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-1089||The Admin account receives a license expiration notification email twice (instead of once) when each of the 45, 15, 7, and 6 day increments are left for the license expiration.|
|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.|