VidyoPortal and VidyoRouter known issues

When upgrading to version 19.2.0.63, the Diagnostic Report displays the incorrect DNS server.

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.

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.

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.

When in FIPS mode, enabling TLS 1.2 only mode is currently not supported.

Search queries are unable to retrieve restricted groups that have special characters (such as ~, %, @, etc.) in the group name.

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.

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.

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.

The status-notify.log in the TCP streaming server does not capture the Presenter Mode enable/disable status.

The status-notify.log in the TCP streaming server does not capture SAML user and room status (such as logging in and creating rooms).

The status-notify.log in the TCP streaming server does not capture creating a scheduled room.

The status-notify.log in the TCP streaming server does not capture creating a public room.

The TCP streaming server is unable to keep up with the logging of user events.

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.

The Cancel button does not work on the Admin portal CDR Access page.

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.

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.

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.

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.

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.

After starting a "Force Standby" action, the Force Standby button should be inactive, but is still active.

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.

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.

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.

When SSL is enabled, the user is not prompted to reboot the server after regenerating a self-signed certificate.

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.

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.

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.

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.

Forgot Password does not function for locally authenticated Normal users if the admin or operators are LDAP authenticated.

The system restart message does not display after refreshing the browser on the Super Admin portal > Settings > Security page.

The Group Limit is not enforced when a user invites all of the participants at once.

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.

When a VidyoRoom™ SE is added to the VidyoPortal, it does not appear on the VidyoPortal Manage VidyoRooms page.

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.

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.

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.

The Audit logs do not capture changes made to some of the tabs on the Settings page.