Version 3.5.1

Improved admin control of the DTMF functionality
When the Call Control via DTMF feature is enabled, participants who join a conference are immediately told which button to press on their DTMF keypads to hear the call control options. However, if you already have DTMF controls available on your PBX or audio conferencing service, version 3.5.1 now allows you to completely disable this functionality using the VidyoGateway Admin UI.
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.

You must upgrade to VidyoGateway version 3.5.1 from VidyoGateway version 3.5.0. Therefore, if you have a VidyoGateway version 3.5.0 or earlier, you must first upgrade to 3.5.0 and then upgrade to 3.5.1.
Additionally, you can refer to the Upgrade Steps Lookup Tool article for information on how to upgrade to VidyoGateway version 3.5.1 from the version you are currently running. This article lists the steps you need to take for your particular version, including which Security Updates you may or may not need to install.
CAUTION: If enabling latching in VidyoGateway version 3.5.1, H.323 calls may produce large log files. Please contact the Vidyo Customer Support Team if you encounter any problems related to this issue. Please note that SIP calls do not result in elevated logging.
Starting with version 3.3.2, the VidyoGateway VE enforces capacity based on CPU reservation, not Virtual Machine configuration. If there is no resource reservation or minimal reservation, the capacity will default to one video call or ten audio-only calls.
VidyoGateway VE version 3.3.x uses more memory in order to run more efficiently than older versions of VidyoGateway VE, and therefore requires a minimum of 4 GB of memory. Because previous versions required less memory, you may need to increase the memory allocation on your VidyoGateway Virtual Machine before upgrading.

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

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

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

VidyoGateway version 3.5.1 - resolved issues
Key	Summary
VGW-2705	Some deadlock issues that occurred during very short duration H.323 calls have now been resolved.
VGW-2697	Some inconsistencies in configuring High Frame Rate sharing capabilities have been resolved.
VGW-2673	Content sharing failures that occurred on inbound SIP calls when latching was enabled have been resolved.
VGW-2662	For secure calls, H.224 is now correctly advertised as RTP/SAVP.
VGW-2632	GNU Gatekeeper gnu.gk log files now rotate weekly.

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