Version 4.2.0

What's new in this release?

  • Welcome message
  • Vidyo now provides support for adding a custom welcome message prompt when voice-only participants join a conference.
  • Avatars for voice-only participants
  • Avatars will now display for voice-only participants that join calls using VidyoPortal and VidyoRouter version 18.3.1 or later.
  • Cluster configuration
  • The cluster controller now automatically replicates the configuration details instead of having to apply individual configuration changes to each cluster node.
  • SIP Protocols
  • Previously, SIP protocol support could be configured per direction (Inbound or Outbound). In VidyoGateway version 4.2 and later, this configuration is bi-directional. For example, if the UDP protocol is enabled or disabled, it is automatically enabled or disabled for both directions. The VidyoGateway Web Admin has been updated to reflect this.
  • H.323 support
  • Support for H.323 latching is no longer supported in VidyoGateway 4.2 or later.
  • H.323 Gatekeeper registration is no longer supported. Only H.323 Neighboring is supported (in both clustered and standalone mode).
  • Audio
  • Disabling AGC and configuring the AGC Target Level is no longer supported. The VidyoGateway now automatically enables this function.
  • Video
  • The Video Loopback option is no longer supported and has been removed from the VidyoGateway Admin web interface.
  • Prompts
  • There is now a new prompt available for configuring a Welcome Message for audio-only participants.
  • Media ports
  • The minimum port number for media traffic must now be a number between 3001 and 65535. The recommended value is 3001. Therefore, the Media Min UDP Port has changed from 1 to 3001. This update will automatically occur upon upgrade.
  • Display option in CDR
  • Previously the administrator could configure how the display name would be logged in the CDR (E.164 format or Display Name). In VidyoGateway 4.2 and later – if a legacy endpoint has an E.164 number configured, then this will automatically be set in the CDR.
  • Auto disconnect of last participant
  • The last participant timer has been replaced by two options:
  • Maximum call duration: This option specifies the maximum length of a VidyoGateway call. This value defaults to 720 minutes (12 hours). This can be increased or decreased as needed.
  • Auto disconnect last participant: In order to be more efficient at resource management, if there is only one VidyoGateway participant left in the conference, then this user will be automatically disconnected. This option can be turned off by an administrator ifs desired.
  • Resource reservation
  • Selecting between Static and Dynamic is no longer supported. The VidyoGateway will dynamically accept or reject calls based on current CPU configuration and utilization.
  • Access control
  • The option to “Automatically block IP addresses with Whitelist and Blacklist overrides” is no longer available. All other existing modes are supported.
  • Service configuration
  • The “Enable Crop” option is no longer supported.
  • The “Send DTMF Signaling” option is no longer available. DTMF Signaling is now always enabled for endpoints that support it per RFC 4733/2833 for SIP and via signaling for H.323.
  • IVR
  • The default IVR recordings have been changed. If you prefer to use the existing VidyoGateway version 3.5.2 recordings, you may download them and upload them after upgrading to VidyoGateway version 4.2 and later. Note: If you have replaced the default IVR recordings with your own version, these will be preserved after upgrade.
  • The “Jump to IVR if wrong extension is entered” option is no longer available to turn off. This behavior is always enabled.
  • The "Call Disconnecting" IVR prompt is no longer available.
  • 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 from VidyoGateway version 3.5.2. Therefore, if you have a VidyoGateway version earlier than 3.5.2, you must first upgrade to version 3.5.2 and then upgrade to version 4.2. 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. 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 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. Please review the Notable Changes section in VidyoGateway: About Version 4.2 in detail before upgrading if you have installed a previous VidyoGateway version 4.2 Beta.
  • 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 version. For more information, please refer to "Running the Recovery Utility" in the Performing Advanced Configuration section of the VidyoGateway Admin Guide.


  • VidyoGateway version 4.2 is compatible with VidyoPortal version 18.3.1 or later.


This file...

Should be applied on top of...


VidyoGateway version 3.5.2

Do not install on a version earlier than the version listed in the preceding table. Also, if you upgrade to VidyoGateway 4.2, you do not need to install Security Update (SU20) or Security Update 21 (SU21). SU20 and SU21 are already included as part of the upgrade package.

Upgrade to a 3.5.2 Cluster

To upgrade a 3.5.2 cluster, 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, proceed to upgrade the Active Controller. The previous Standby Controller will now become the 4.2 Active Controller.
  • When the former 3.5.2 Active Controller completes its upgrade, it will then become the 4.2 Standby Controller.

Resolved issues

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

VidyoGateway Version 4.2.0 - resolved issues




An issue where content share may be delayed from a H.323 device has been resolved.


Users are now able to remove an SNMP v3 destination and will no longer receive the message, "unable to remove notification”.


Vidyo addressed an issue where asymmetric bandwidth calculations were not being honored by the VidyoGateway.


If a clustered GW is disconnected from the GW Controller (removed from cluster or DOWN or disconnected from the network); the Controllers Status view will now display all active calls.


Vidyo addressed a rare issue where a crash can occur when there are multiple H.323 calls.


Vidyo fixed an issue where calls routed from a Gatekeeper may be rejected.


Users can now use the number pad to enter a user password in the CLI menu.


Users can now successfully reboot the VidyoGateway from the Web Interface with RADIUS configured.


Administrators can now enter SIP Proxy/H323 GK with more than 4 levels.


Vidyo fixed an issue when a call is made with 30ms audio packetization, the audio on the Vidyo endpoint sounds choppy.


Vidyo fixed an issue when LIFO content sharing does not work if shared content is already present in the conference.


Vidyo has fixed an issue where H.323 endpoints attempting to use the G.722 audio codec will now send and receive audio through the VidyoGateway.


Vidyo resolved an issue so that Cisco endpoints that have updated to the CE version now no longer experience degraded audio using the Opus codec.


Users can now successfully download audit logs from the VidyoGateway Admin page.


A previous 4.2 Beta issues was fixed and now when a P2P call invite is made with a VidyoDesktop user; it is now successfully received.


A previous 4.2 Beta issue was addressed and now the VidyoGateway Web Admin does not allow a user to save an incorrect minimum UDP port.


Vidyo addressed an issue where VidyoGateway participants may not be able to hear other participants that have special characters in their display name.


An issue was resolved where the VidyoGateway was unable to send or receive 1080p content from certain Cisco devices.


Vidyo fixed an issue so now the content share statistics display correctly.

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.