Version 23.2.1

What's new in this release?

  • Audio plugin updates
  • We’ve made improvements to the OPUS and SPEEX decoders to improve quality and audio latency.
  • Dynamic caller ID support with Epic CAL integration (cloud only)
  • If you use the Epic CAL integration, you can now dynamically change your caller ID for outgoing calls.
  • This feature is particularly useful when you have enabled on-click dial-out for your providers via the “dialOut” parameter.
  • Requires VidyoPortal 23.4.x or later.
  • OpenSSL update
  • This release includes a major update of OpenSSL libraries to version 3.0.
  • SSH update and configuration
  • This release includes an update to SSH as well as configuration updates to improve security by deprecating legacy protocols.
  • Prior to upgrading, please review the SSH configuration information section below in detail to ensure you have the right configuration to connect to the Vidyo appliances after upgrade.
  • Bug fixes
  • In this release, we've addressed some 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.

SSH configuration information

SSH configuration information

In this version, the SSH configuration has been updated to improve security. Because of these changes, only modern SSH clients that support the configurations below will typically be able to successfully connect.

  • Supported host keys: RSA,ED25519
  • Key exchange algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group18-sha512,diffie-hellman-group16-sha512,curve25519-sha256,sntrup761x25519-sha512@openssh.com,curve25519-sha256@libssh.org
  • MACs: hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-128-etm@openssh.com
  • Encryption ciphers: Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com

Prior to upgrading, we recommend that you:

  • Update your SSH client to the latest version.
  • Confirm your client supports the above configurations.
  • Take a backup (snapshot) of your virtual machine.
  • Upgrade a single machine first to confirm connectivity and then proceed to the others.

Important notices

  • You must upgrade to VidyoGateway version 23.2.1 from VidyoGateway version 23.1.0 or later. Therefore, if you have a VidyoGateway version earlier than 23.1.0, you must first upgrade to 23.1.0 and then upgrade to version 23.2.1. Please refer to the “Upgrade a VidyoGateway 23.1.0 cluster to 23.2.1” section below for more information. These steps must be completed in order.
  • If you have installed a previous VidyoGateway version 23.2.1 beta, you should first downgrade your VidyoGateway to 23.1.0 using the Recovery Utility on the System Console, and then upgrade directly to the GA 23.2.1 version. For more information, please refer to "Running the Recovery Utility" in the Performing Advanced Configuration section of the VidyoGateway Administrator Guide.

Compatibility

VidyoGateway version 23.2.1 is compatible with VidyoPortal version 21.6.x and later.

Files

This file...

Should be applied on top of...

gw-TAG_GW_23_2_1_88-bundle-v6536.vidyo

VidyoGateway version 22.2.x or later

Upgrade a VidyoGateway 23.1.0 cluster to 23.2.1

To upgrade a VidyoGateway 23.1.0 cluster to version 23.2.1, please perform the following steps in order:

  1. Place all Cluster Nodes into Maintenance mode.
  2. Upgrade all the Cluster Nodes.
  3. When the Cluster Node upgrades are completed and back online, upgrade the current Standby Controller.
  4. When the Standby Controller upgrade is complete, upgrade the Active Controller. The previous Standby Controller will now become the Active Controller.
  5. When the former Active Controller completes its upgrade, it will then become the Standby Controller.

Resolved issues

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

VidyoGateway version 23.2.1 - resolved issues

Key

Summary

VIDGW-355

We fixed an issue where the API key became invalid after a reboot.

VIDGW-347

Duplicate or extra SIP headers are no longer sent to a SIP proxy under specific configurations with a SIP trunk.

VIDGW-323

When the FQDN of the server is set via the System Console, the FQDN is now properly applied to the system.

VIDGW-271

We resolved an issue where an internal process could deadlock in certain rare cases causing future calls to fail.

VIDGW-269

We fixed an issue where the VidyoGateway would attempt to register excessively when incorrectly configured.

VIDGW-268

We addressed an issue where, under certain conditions, there was an audio lag with dial-out audio-only participants (via SIP Proxy).

VIDGW-252

We addressed an issue where audio could lag behind video under certain cases.

Known issues

There are no new known issues for this release; however, to view the previous known issues, please see the known issues for VidyoGateway section.