Partners Blog Contacts

Important Notices

When upgrading to VidyoPortal™ and VidyoRouter™ version 17.1.1, please refer to the following to ensure that your upgrade goes smoothly:

  • You must upgrade to VidyoPortal and VidyoRouter version 17.1.1 from version 17.1.0, 3.4.6, 3.4.5, or 3.4.4. Upgrades from versions earlier than 3.4.4 are not supported. Therefore, if you have a VidyoPortal version that is earlier than 3.4.4, you must first upgrade to 3.4.4 and then upgrade to version 17.1.1.
  • VidyoPortal Virtual Edition version 3.4.x 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.
  • Please review the Upgrade Notices, the Resolved issues in VidyoPortal and VidyoRouter version 17.1.1, and the Known issues in VidyoPortal and VidyoRouter version 17.1.1 articles before upgrading.

What’s New in This Release

Here's what's new in version 17.1.1:

  • Custom Invocation
    • Third-party partners, developers, and admins: starting with Vidyo Neo version 17.1, you can now customize the Vidyo Neo client experience and workflow. Vidyo Neo lets you easily choose which features and functionality you can enable and disable for your users. For example, you can use the Custom Invocation parameters to:
      • Bypass the Welcome and Login pages to provide users with direct access to a conference.
      • Muting all participants’ microphones or cameras upon entry into a call.
    • Partners and developers can also invoke Vidyo Neo with iFrames. iFrames are the pre-call, in-call, and post-call URLs that allow you to load content from your domain or a third-party system into Vidyo Neo per tenant. For example, you can use iFrames to:
      • Display content around the main in-call window.
      • Display a thank-you message at the end of each call.

      NewUI_iFrame.png

    • As a VidyoPortal Super Admin, you can use the Custom Roles setting to allow or restrict the tenants from receiving the customized Vidyo Neo features and attributes.

      CustomRoles.png

    • For more information about the powerful new Custom Invocation feature, see the Custom Invocation of Vidyo Neo Technical Note or the Using Custom Invocation article. For more information about configuring iFrames via the Vidyo Web Services APIs, see the Web Services API User Guide.

  • Redesigned Meeting Invitations
    • Starting with Vidyo Neo version 17.1 and this release of the VidyoPortal, in addition to plain text invitations, you can now send HTML invites via email.
    • By using the variables that we provide in the Admin Portal, you can easily add details to your meeting invitations, such as the user’s title, display name, avatar, tenant logo, and local and international dial-in numbers.

      EmailContentHTML.jpg

    • For complete information about how to create HTML invites as well as to get sample HTML code to create an invitation like the one shown below, see the Creating HTML meeting invitations  article.

      HTMLInvite.png

  • Removal of vr2conf
    • We’ve removed the vr2conf configuration page from the VidyoPortal.
    • Instead of having to get your VidyoRouter logs from vr2conf, whenever you extract your portal logs, you will now automatically get your router logs as well.

  • Security Enhancements
    • In this release, we’ve made significant security enhancements by introducing a Content Security Policy as well as by adding other security features.

Upgrade Notices

You must upgrade to VidyoPortal and VidyoRouter version 17.1.1 from version 17.1.0, 3.4.6, 3.4.5, or 3.4.4. Upgrades from versions earlier than 3.4.4 are not supported. Therefore, if you have a VidyoPortal version that is earlier than 3.4.4, you must first upgrade to 3.4.4 and then upgrade to version 17.1.1. In addition, please review the VidyoPortal and VidyoRouter Release Notes for version 3.4.2 before proceeding, as there are several important notices to take into advisory.

Before you begin the upgrade, please note the following:

Resolved and Known Issues

This section lists the resolved and known issues in this release of VidyoPortal and VidyoRouter.

 

Resolved Issues

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

VidyoPortal and VidyoRouter Version 17.1.1 - Resolved Issues
Key Summary
VPTL-7620 “Super Tenant” no longer erroneously displays in the Available Tenants list when the Super Admin creates or updates the tenant’s information from the Tenants page.
VPTL-7542 The International Dial In page now displays flags for Japan, Taiwan, and the Philippines.
VPTL-6949 Users can now set passwords that are longer than 40 characters from the VidyoDesktop Manage Account page.
VPTL-6801 If the Super Admin account is set to a language other than English, the Enable SSL option now changes when enabled and the Encryption button is now active.

 

Known Issues

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

VidyoPortal and VidyoRouter Version 17.1.1 - Known Issues
Key Summary
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-6138 When manually provisioning a user, email addresses with long suffixes are not accepted.
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-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.

 

Was this article helpful?
0 out of 0 found this helpful

0 Comments

Follow
Please sign in to leave a comment.