Version 23.2.1

What's new in this release?

  • OpenSSL update
  • This release includes a major update of the OpenSSL libraries to version 3.0.
  • Metadata timestamps for per-participant audio
  • We enhanced the metadata timestamps of the per-participant audio feature to include milliseconds for increased accuracy.
  • Important bug fixes
  • In this release, we've addressed some important issues to improve usability and reliability.
  • System updates
  • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.

Files

This file...

Should be applied on top of...

rp-TAG_RP_23_2_1_70-bundle-v6339.vidyo

VidyoReplay version 22.2.0 or later

Important notices

  • You must apply VidyoReplay version 23.2.1 on top of VidyoReplay version 23.2.0. If you have a VidyoReplay version earlier than 19.1.0, you must first upgrade to 19.1.0, then incrementally upgrade versions to version 23.2.1. Once you have done so, refer to the Upgrade a VidyoReplay Cluster to 23.2.1 section below. These steps must be completed in order.
  • Multiple Super users can be managed only from the Active Controller in a VidyoReplay cluster.

Upgrade a VidyoReplay cluster to 23.2.1

To upgrade an existing VidyoReplay cluster:

  1. Upgrade all recording nodes in the cluster. Note: You cannot log in to recorder nodes until the entire cluster upgrade is completed.
  2. Log in to each controller and reconfigure them as standalone.
  3. Log in to each standalone cluster and perform the upgrade.
  4. Log in to the old active controller and reconfigure it in cluster mode. The machine will reboot. Check the portal to see if the machine is properly registered.
  5. Once registered, you can log in with the default user (‘super’). The Users tab should be visible. The Settings > Cluster > Component Status page should show the current machine as an active controller with all the recorders present.
  6. Log in to the old standby controller and reconfigure it in cluster mode. The machine will reboot.
  7. The active controller page located at Settings > Cluster > Component Status should now show the successful replication and that both controllers are currently online.
  8. You can now log in via the UI on any machine in the cluster.

Notes:

  • We recommend taking a snapshot of the machines using VidyoConsole, or via VMware if using a virtual machine.
  • It is mandatory to perform the above procedure step-by-step. Failure to do so may result in unexpected results, including the inability to log in. In such cases, you can revert to a previous snapshot.
  • If a recorder node is reconfigured as standalone, the Users database is cleared and the default username/password combination may be used to log in.
  • If a controller is reconfigured as standalone, the Users database remains untouched.

Compatibility

VidyoReplay version 23.2.1 is compatible with VidyoPortal versions 20.1.x and later.

If your organization has an on-premises VidyoPortal (rather than a cloud subscription), refer to the Vidyo compatibility matrix to determine which endpoint versions are compatible with your VidyoReplay release.

Resolved issues

The following table lists the issues we have resolved in VidyoReplay version 23.2.1.

VidyoReplay version 23.2.1 - resolved issues

Key

Summary

VIDRPLY-249

Fixed a GUI issue where the VidyoReplay registration status showed as “Not Registered” even though it was functioning properly.

VIDRPLY-231

Fixed an issue where there could be up to a five-second delay in a recording starting.

VIDRPLY-217

Fixed an issue where, under a certain race condition, the recording did not get finalized properly and the recording did not play to the end.

VIDRPLY-188

Fixed an issue where, when upgrading from an older FLV-based VidyoReplay version, the MP4 conversion could get stuck processing certain videos.

VIDRPLY-142

Fixed an issue where very short recordings (<15 secs) would be truncated.

VIDRPLY-77

Fixed an issue where an erroneous disk space email alert would be sent when the NAS got unmounted due to connectivity issues.

Known issues

There are no new known issues for this release.