Partners Blog Contact Us

VidyoPortal and VidyoRouter: About Version 19.1.0

Follow

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.

    ControlMeeting.png
    • 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 DisableVideoButton.png and mute audio MuteAudioButton.png 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.


Important Notices for On-Premises Customers

To ensure that your on-premises upgrade goes smoothly:

  • You must upgrade to VidyoPortal and VidyoRouter version 19.1.0 from version 18.x, 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 19.1.0.
  • You must apply Security Update 21 (SU21) to your VidyoPortal before you upgrade to version 19.1.0. The SU21 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, 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 in this article before 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.

If you are using this release of the VidyoPortal and VidyoRouter with VidyoGateway version 3.5.x, please note that if the conference moderator or a participant mutes the video of another participant in the call, all legacy participants in the call will see the last frozen frame of the participant whose video was muted.

This issue has been resolved in VidyoGateway version 4.2 and later.

 

Resolved and Known Issues

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.

 


Known Issues

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

VidyoPortal and VidyoRouter Version 19.1.0 - Known Issues
Key Summary
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.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.