Version 4.2.1
What's new in this release?
- 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.
Important notices
- You must upgrade to VidyoGateway version 4.2.1 from VidyoGateway version 3.5.2 or 4.2 (332). Therefore, if you have a VidyoGateway version earlier than 3.5.2, you must first upgrade to 3.5.2 and then upgrade to version 4.2.1. Please refer to the “Upgrade to a 3.5.2 Cluster” section in VidyoGateway: About Version 4.2 to upgrade from VidyoGateway 3.5.2 to version 4.2.1. These steps must be done in order.
- Additionally, you can refer to the Upgrade Steps Lookup Tool article for information on how to upgrade to VidyoGateway version 4.2.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.
- There are functional changes between VidyoGateway version 3.5.2 and 4.2.1. Please review the Notable Changes section in VidyoGateway: About Version 4.2 in detail before upgrading.
- Important Note: If you have installed a previous VidyoGateway version 4.2 beta, you should first downgrade your VidyoGateway to 3.5.2 using the Recovery Utility on the System Console, and then upgrade directly to the GA 4.2.1 version. For more information, please refer to "Running the Recovery Utility" in the Performing Advanced Configuration section of the VidyoGateway Admin Guide.
- feature
Compatibility
- VidyoGateway version 4.2.1 is compatible with VidyoPortal version 18.3.1 or later.
Files
|
This file... |
Should be applied on top of... |
|---|---|
|
gw-TAG_GW_4.2.1.036-bundle-v1734.vidyo |
VidyoGateway version 3.5.2 or 4.2.0 |
Upgrade a VidyoGateway x cluster to version x
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.
Resolved issues
The following table lists the issues we resolved in VidyoGateway version 4.2.1.
|
VidyoGateway version 4.2.1 - resolved issues |
|
|---|---|
|
Key |
Summary |
|
XGW-464 |
Enghouse Vidyo resolved a memory leak issue addressing multiple scenarios. Previously the memory space used increased over time. |
|
XGW-430 |
Vidyo fixed an issue where the VidyoGateway would periodically leak memory in certain call scenarios. |
|
XGW-416 |
Vidyo fixed an issue so now calls work with Avaya after updating from version 3.5.2 to version 4.2.1. The IVR is now available for Avaya SIP trunk. |
|
XGW-412 |
Vidyo resolved an issue so when an active speaker changes during a content share; the content in the screen share will no longer flicker. |
|
XGW-403 |
Controllers can now be switched allowing for successful outbound SIP calls. |
|
XGW-391 |
Vidyo fixed an issue with the VidyoGateway GWCC process so that it no longer crashes and drops calls. |
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.
