What's New in this Release
Here's what's new in version 18.2.0:
- 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™.
The "From" header update is only required by certain Verint integrations using VidyoEngage.
- Resolved Issues
- We've resolved a number of issues for enhanced system usability. Refer to the resolved issues below.
- We've resolved a number of issues for enhanced system usability. Refer to the resolved issues below.
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.2.0.
- You must apply Security Update 18 (SU18) to your VidyoPortal before you upgrade to version 18.2.0. The SU18 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 modes.
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.2.0:
|VidyoPortal and VidyoRouter Version 18.2.0 - Resolved Issues|
|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.|
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.|
There were no new known issues in VidyoPortal and VidyoRouter version 18.2.0.
The following table lists the known issues in VidyoPortal and VidyoRouter version 18.2.0:
|VidyoPortal and VidyoRouter Version 18.2.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.|