Version 20.1.0

What's new in this release?

  • OPUS Support with VidyoConnect
  • When registering to the VidyoPortal, the VidyoGateway checks the system's capabilities, and then one of the following occurs:
  • If the VidyoPortal supports Opus audio, the VidyoGateway configures itself to use Opus audio on the SVC side so when a gateway participant joins a VidyoConnect call, the conference continues to use Opus.
  • If the VidyoPortal does not support Opus audio, the VidyoGateway configures itself to use SPEEX/RED on the SVC side.
  • Media relay support for H.323 and SIP endpoints
  • This version supports media relay for H.323 and SIP endpoints. 
  • Admin UI support for experimental features
  • In the Experimental Features section of the VidyoGateway Admin UI General > Advanced page, you can enable the following:
  • The API Interface checkbox which allows API requests to go through to the VidyoGateway (but only after you’ve authenticated using the API key). 
  • RTMP streaming (via API only).
  • To learn more about these features, refer to the "Configuring Advanced Settings" section of version 20.1.0 of the VidyoGateway Administrator Guide.
  • Access control modes for allowing or blocking whitelisted and blacklisted IP addresses
  • The VidyoGateway Admin UI General > Access Control page includes three Access Control modes that enable you to:
  • Allow all incoming calls to reach the VidyoGateway.
  • Allow incoming calls only from whitelisted IP addresses.
  • Block incoming calls from blacklisted IP addresses.
  • 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.

Upgrade notes

  • You must upgrade to VidyoGateway version 20.1.0 from VidyoGateway version 4.2.0. Therefore, if you have a VidyoGateway version earlier than 4.2.0, you must first upgrade to 4.2.0 and then upgrade to version 20.1.0. Please refer to the Upgrade a VidyoGateway 4.2.0 Cluster to Version 20.1.0 section below. 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 20.1.0 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 4.2.0 and 20.1.0. Please review the Notable Changes section below before upgrading.
  • If you have installed a previous VidyoGateway version 19.1.0 beta and 20.1.0 beta, you should first downgrade your VidyoGateway to 4.2.0 using the Recovery Utility on the System Console, and then upgrade directly to the GA 20.1.0 version. For more information, refer to "Run the recovery utility" section of the VidyoGateway Administrator Guide.

Compatibility

  • VidyoGateway version 20.1.0 is compatible with VidyoPortal version 18.3.1 and later.

Files

This file...

Should be applied on top of...

gw-TAG_GW-20.1.0.014-upgrade-signed.vidyo

VidyoGateway version 4.2.0

Upgrade a VidyoGateway 4.2.0 cluster to version 20.1.0

To upgrade a VidyoGateway 4.2.0 cluster to version 20.1.0, 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 20.1.0 Active Controller.
  • When the former 4.2.0 Active Controller completes its upgrade, it will then become the 20.1.0 Standby Controller.

Notable changes

As a reminder, there are many functional changes between VidyoGateway versions 3.5.2 and 4.2.0.

Resolved issues

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

VidyoGateway Version 20.1.0 - resolved issues

Key

Summary

XGW-558

The incoming call notification on legacy devices now properly indicates the display name of the VidyoConnect user; prior to this release, "sip Gateway IP" would appear as the caller ID for incoming calls from the VidyoConnect application.

XGW-544

Enghouse Vidyo fixed an issue where changing the Voice Repeat Interval value on the VidyoGateway Admin UI IVR > General page had no effect; therefore, entering a new value now properly changes the time elapsed between repeated voice responses.

XGW-536

Enghouse Vidyo fixed an issue where the correct CDR information was not being sent to the VidyoPortal when a call to a legacy device did not connect properly.

XGW-528

Enghouse Vidyo fixed an issue where DTMF tones were not consistently being registered when dialing out via SIP TCP to a Cisco VCS.

XGW-523

An issue where the VidyoGateway was not responding to SIP re-invites has been fixed.

XGW-519

Adding a neighbor gatekeeper with an FQDN no longer prevents the local GNU gatekeeper from running.

XGW-515

Enghouse Vidyo fixed an integration issue that was caused by the incorrect payload type selection when no attributes were specified for a certain codec.

XGW-501

Enghouse Vidyo fixed an issue where Vidyo users could not share content in calls with certain Polycom endpoints.

XGW-487

Enghouse Vidyo fixed an issue where Vidyo users who had made outbound calls could not see content that was shared from endpoints using H.263.

XGW-463

Enghouse Vidyo fixed an issue where VidyoGateway was failing to connect incoming calls with a SIP Delayed Offer.

XGW-429

When an outgoing call is made using an FQDN (such as yourname@gateway123.vidyo.lo), the VidyoGateway no longer disregards the data after the “@” sign, and is therefore able to connect to the correct room.

XGW-425

Enghouse Vidyo fixed an issue where shared content was not sent and/or received in calls that were connected with certain MCUs.

XGW-417

An issue where DTMF tones were not consistently being registered when dialing out via H.323 has been fixed.

XGW-348

The VidyoPortal CDR “EndpointPublicIPAddress” field, which was displaying incorrectly as “N/A” for VidyoGateway calls when certain VidyoGateway versions were used, now properly displays the endpoint public IP addresses.

XGW-347

The VidyoPortal CDR “DeviceModel” field, which was displaying incorrectly as “N/A” for VidyoGateway calls when certain VidyoGateway versions were used, now properly displays device model information.

NEP-13109

Two or more legacy endpoints are now able to join the same VidyoConnect conference.

Known issues

There are no new known issues for this release.