Partners Blog Contact Us

VidyoGateway: Releases

Follow

This article describes the new features, important notices, and resolved issues for each of the VidyoGateway™ releases. Also included are the files needed and browser and platform compatibility  information.

Additionally, this article includes the following topics:

 


2020 Releases


 

VidyoGateway: About Version 20.2.0

What's New in This Release

  • Video Mute Options via DTMF
    • Users joining a call with video can now use DTMF control keys to mute and unmute their video and/or audio. Prior to this release, only audio-only users joining a call could use DTMF control keys to mute and unmute their audio.
    • Admins can enable and disable this feature using the "Enable video control keys" checkbox on the General Prompts page of the VidyoGateway Admin portal. 
      • You can also use this page to change the welcome message that video users will see when joining a call, select how long in seconds you want the messages to display, and select how opaque the messages will appear on the screen.

        VG1.jpg

    • To learn more, refer to the "Configuring Prompts and Call Control via DTMF Tones" section of version 20.2.0 of the VidyoGateway Administrator Guide.
  • Ability to Enable and Disable Avatars
    • You now have the ability to enable or disable the avatar that displays when a participant has their video  source muted (that is, when that participant is in audio-only mode).
      • When enabled, if a participant’s video source is muted during a call, an avatar with the first three letters of their name appears on their tile.
      • When disabled, if a participant’s video source is muted during a call, their video tile does not display at all.
    • Easily configure this setting using the new "Use Avatar" checkbox on the General Advanced page of the VidyoGateway Admin portal. 

      VG2.jpg

    • To learn more, refer to the "Configuring Advanced Settings" section of version 20.2.0 of the VidyoGateway Administrator Guide.
  • Updates for Experimental Features
    • The Experimental Features section of the VidyoGateway Admin portal General > Advanced page allows you to send API requests to the VidyoGateway (after you’ve authenticated using an API key).
      • These API requests can now be sent via https. Prior to this release, only http was supported.
    • You can also use Experimental Features to enable RTMP streaming via API.
      • Starting with version 20.2.0, you can use RTMPS when establishing a stream via the VidyoGateway. To do so, simply enter “rtmps” in the stream destination. 

        VG3.jpg
    • To learn more, refer to the Using VidyoGateway Experimental Features article on the Vidyo Help Center. 
  • Audio Quality Improvements
    • For even better-quality audio, the audio sample rate for and RTMP streaming is automatically negotiated at 48 kHz instead of 16 kHz. 
  • System Updates
    • For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
  • Resolved Issues
    • Enghouse Vidyo fixed an issue where certain outbound TLS calls were not negotiating video on the remote side.
    • We've also fixed a number of other issues to enhance the reliability and usability of the VidyoGateway.

 

Important Notices

  • You must upgrade to VidyoGateway version 20.2.0 from VidyoGateway version 20.1.0 or later. Therefore, if you have a VidyoGateway version earlier than 20.1.0, you must first upgrade to 20.1.0 and then upgrade to version 20.2.0. Please refer to the “Upgrade a VidyoGateway 20.1.0 Cluster to Version 20.2.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.2.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 3.5.x and 20.2.0. Please review the Notable Changes section below before upgrading.
  • If you have installed a previous VidyoGateway version 20.2.0 beta, you should first downgrade your VidyoGateway to 20.1.0 using the Recovery Utility on the System Console, and then upgrade directly to the GA 20.2.0 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 20.2.0 is compatible with VidyoPortal version 18.4.0 and later. 

 

Files 

This file... Should be applied on top of...
gw-TAG_GW_20.2.0.066-bundle-v3013.vidyo
VidyoGateway version 20.1.0

 

Upgrade a VidyoGateway 20.1.0 Cluster to Version 20.2.0

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

You can also refer to the Upgrade Steps Lookup Tool article for information on how to upgrade your VidyoGateway 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.

 

Resolved Issues

The following table lists the resolved issues in VidyoGateway versions 20.2.0:

VidyoGateway Version 20.2.0 - Resolved Issues
Key Summary
XGW-648

Enghouse Vidyo resolved an issue where sometimes SIP endpoints did not get the IVR. 

XGW-627

Enghouse Vidyo fixed an issue where certain outbound TLS calls were not negotiating video on the remote side due to an SRTP error.

XGW-611
and
XGW-595
Enghouse Vidyo resolved an issue where DTMF tones did not send out of band in VidyoGateway conferences. 
XGW-586 VidyoGateway now properly displays the remote participant's display name as well as the Caller Name, Device Model, and Endpoint Public IP Address in the CDR.
XGW-583 Enghouse Vidyo fixed an issue where SIP/H.323 endpoints that were in a call with a Vidyo client would see non-English display names as garbled text. 
XGW-561
and
XGW-554
Enghouse Vidyo fixed an issue that caused SIP outbound calls to fail because the VidyoGateway SIP invite did not send the full SIP URI user@Domain/IP header.
XGW-531 Enghouse Vidyo fixed an issue where poor quality audio was received when the audio was sent via a content share device connected to a VidyoRoom system.

 


VidyoGateway: About Version 20.1.0

What's New in This Release

  • Major Platform Operating System (OS) Update
    • Enghouse Vidyo performed a major platform OS update, thereby enhancing the performance, stability, and security of the VidyoGateway.
    • Additional benefits include:
      • Updates to most third-party libraries.
      • Continual security updates to the underlying OS.
      • Streamlined patching of third-party software components.
  • 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).

        Zendesk_Exp_features.png
    • 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.

        VGW_AccessControlModes.png
    • To learn more about these modes, refer to the "Configuring Access Control Settings" section of version 20.1.0 of the VidyoGateway Administrator Guide.

 

Important Notices

  • You must upgrade to VidyoGateway version 20.1.0 from VidyoGateway version 4.2.1. Therefore, if you have a VidyoGateway version earlier than 4.2.1, you must first upgrade to 4.2.1 and then upgrade to version 20.1.0. Please refer to the “Upgrade a VidyoGateway 4.2.1 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 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.1 using the Recovery Utility on the System Console, and then upgrade directly to the GA 20.1.0 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 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.1

 

Upgrade a VidyoGateway 4.2.1 Cluster to Version 20.1.0

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

You can also refer to the Upgrade Steps Lookup Tool article for information on how to upgrade your VidyoGateway 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.

 

Notable Changes

As a reminder, there are many functional changes between VidyoGateway versions 3.5.2 and 4.2.1. Please make sure to review the Notable Changes section below before upgrading.

 

Resolved Issues

The following table lists the resolved issues in VidyoGateway versions 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.

 


2019 Releases


 

VidyoGateway: About Version 4.2.1

What's New in this Release

Here's what's new in this release:

  • Performance, Stability, and Security Improvements
    • Vidyo implemented enhancements to improve our network performance, reliability, and scalability, as well as our system security.
  • Resolved Issues
    • In this release, we've resolved a number of issues for enhanced system stability and usability. Refer to the list of resolved issues in the "Resolved Issues" section below.

 

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.

 

Compatibility

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

 

Files 

This file... Is for...
gw-TAG_GW_4.2.1.036-bundle-v1734.vidyo
VidyoGateway version 3.5.2 or 4.2

 

Do not install on a version earlier than the version listed in the preceding table. Also, if you upgrade to VidyoGateway 4.2.1, 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 

Refer to the "Upgrade to a 3.5.2 Cluster" section in VidyoGateway: About Version 4.2.

 

Notable Changes

Refer to the "Notable Changes" section in VidyoGateway: About Version 4.2.  

 

Resolved Issues

The following table lists the resolved issues in VidyoGateway versions 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.

 


 

VidyoGateway: About Version 4.2

What's New in this Release

Here's 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.
  • Log Consolidation
    • Cluster Controllers can now centrally pull standard logs.  
  • Performance, Stability, and Security Improvements
    • Vidyo implemented enhancements to improve our network performance, reliability, and scalability, as well as our system security.
  • Resolved Issues
    • In this release, we've resolved a number of issues for enhanced system stability and usability. Refer to the list of resolved issues in the "Resolved Issues" section below.

 

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.

 

Compatibility

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

 

Files 

This file... Is for...
gw-TAG_GW_4.2.332-bundle-v1485.vidyo 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:

  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, then upgrade the current Standby Controller.
  4. 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.
  5. When the former 3.5.2 Active Controller completes its upgrade, it will then become the 4.2 Standby Controller.

    If you do not perform the above steps in order; there will be cluster instability and/or configuration loss.

You can also refer to the Upgrade Steps Lookup Tool article for information on how to upgrade your VidyoGateway 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.

 

Notable Changes

The following list includes notable changes for VidyoGateway versions 4.2, 4.2.1, and 20.1.0: 

  • 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
    • In VidyoGateway 4.2 and later, 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. To determine the capacity of your VidyoGateway, refer to the VidyoGateway Admin Guide.
  • 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.

 

Resolved Issues

The following table lists the resolved issues in VidyoGateway version 4.2:

VidyoGateway Version 4.2 - Resolved Issues
Key Summary
VGW-2862 An issue where content share may be delayed from a H.323 device has been resolved.
VGW-2833 Users are now able to remove an SNMP v3 destination and will no longer receive the message, "unable to remove notification”.
VGW-2824 Vidyo addressed an issue where asymmetric bandwidth calculations were not being honored by the VidyoGateway.
VGW-2823 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.
VGW-2806 Vidyo addressed a rare issue where a crash can occur when there are multiple H.323 calls.
VGW-2802 Vidyo fixed an issue where calls routed from a Gatekeeper may be rejected.
VGW-2799 Users can now use the number pad to enter a user password in the CLI menu.
VGW-2794 Users can now successfully reboot the VidyoGateway from the Web Interface with RADIUS configured.
VGW-2790 Administrators can now enter SIP Proxy/H323 GK with more than 4 levels.
VGW-2288 Vidyo fixed an issue when a call is made with 30ms audio packetization, the audio on the Vidyo endpoint sounds choppy.
VGW-585 Vidyo fixed an issue when LIFO content sharing does not work if shared content is already present in the conference.
VGW-315 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.
VGW-311 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.
VGW-308 Users can now successfully download audit logs from the VidyoGateway Admin page.
VGW-280 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.
VGW-279 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.
XGW-252 Vidyo addressed an issue where VidyoGateway participants may not be able to hear other participants that have special characters in their display name.
XGW-139 An issue was resolved where the VidyoGateway was unable to send or receive 1080p content from certain Cisco devices
XGW-90 Vidyo fixed an issue so now the content share statistics display correctly.

 


2018 Releases


 

VidyoGateway: About Version 3.5.2 

Important Notices

  • You must upgrade to VidyoGateway™ version 3.5.2 from VidyoGateway version 3.5.1. Therefore, if you have a VidyoGateway version earlier than 3.5.1, you must first upgrade to 3.5.1 and then upgrade to 3.5.2.
    Additionally, you can refer to the Upgrade Steps Lookup Tool article for information on how to upgrade to VidyoGateway version 3.5.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.
  • 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.

 

What's New in this Release

Here's what's new in this release:

  • Resolved Issues
    • We’ve fixed several issues to enhance both the security and usability of the VidyoGateway as noted in the "Resolved and Known Issues" section below.

 

Compatibility

To determine which version of the VidyoPortal™ your VidyoGateway release is compatible with, do one of the following:

 

Resolved Issues

The following table lists the resolved issues in VidyoGateway version 3.5.2 (402):

VidyoGateway Version 3.5.2 - Resolved Issues
Key Summary
VGW-2771 Entering a value in the H.245 Min TCP Port and H.245 Max TCP Port fields no longer causes H.323 calls to fail.
VGW-2766 H.323 calls no longer require multiple connect attempts with certain multipoint control units (MCUs).
VGW-2764 When the VidyoGateway is inactive for at least 15 minutes, the Login page now displays and the user is forced to log back in.
VGW-2746 VidyoGateway version 3.5.1 (450) no longer fails when calls are placed from VidyoDesktop™ to the Sony® PCS-VCS-MCU.

  


 

VidyoGateway: About Version 3.5.1 

Important Notices

  • 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.

 

What's New in This Release

Here's what's new in this release:

  • 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.
  • Resolved Issues
    • We’ve fixed a number of issues to enhance both the security and usability of the VidyoGateway.

 

Resolved Issues

The following table lists the resolved issues in VidyoGateway™ version 3.5.1 (450):

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.

  

 


 

Known Issues

The following table lists the known issues for VidyoGateway versions 20.1.0 and earlier:

VidyoGateway - Known Issues
Key Summary
XGW-574 If a user has duplicate entries in their CA file, calls to legacy endpoints do not connect successfully.
XGW-573 H.323 calls that go through the gatekeeper do not show the EndpointPublicIPAddress correctly in the CDR.
XGW-560 If a user changes the settings on the VidyoGateway Admin UI Cluster > Roles tab and then clicks Save and Reboot, the erroneous message "Could not save cluster configuration" may appear; however, the new settings are actually updated and saved.
XGW-547 When an H.323 call is dialed out to a legacy device via a saved Legacy Endpoint Alias, the IP address of the device is displayed in the call rather than the device's alias.
XGW-539 If a user adds a service prefix on the "Add Service" pop-up on the VidyoGateway Admin UI Services tab and then clicks Save, the VidyoGateway sometimes reboots.
XGW-498

When participants first dial into a video conference, audio-only participants are audible to other participants during the welcome message and DTMF instructions (e.g., enable disable entry/exit and mute/unmute audio). The audio-only participant does not hear the other participants during this time (there is only one-way audio) and will only start to hear other participants when the instructions have fully played.

XGW-402 If audio-only participants join a call where all users are hard-muted, the audio-only participants are not muted but the UI on the portal moderation page shows them as muted.
Workaround: Confirm trusted CA bundle does not have duplicate entries. Once confirmed, re-upload trusted CA bundle.
XGW-364 When dialing to a Webex SIP address, video may not get negotiated correctly. Workaround: Use a H.323 service profile to join the conference.
XGW-337 The H.323 service will not start if the configured H.245 TCP port is lower than 1025.
Workaround: Configure the minimum H.245 TCP port to 1025 or higher.
XGW-284 SNMP MediaQualtiyThresholdAlert trap may not show the correct value for jitter.
VGW-2566 When a Safari® browser is used to export whitelisted and blacklisted IP addresses, the export may fail.
VGW-2094 When hundreds of trusted authority certificates are imported, the Security > Advanced tab takes a long time to load. In some cases, the browser may warn that the server is unresponsive.

 

 


 

VidyoGateway Interoperability Matrix

Vidyo does not officially support equipment that has been announced as End of Life by the OEM.


The following table lists the equipment that has been tested with VidyoGateway.

Vendor System Name Latest Version Tested Known Issues
Endpoint
Cisco® SX80 TC7.3.4  
Cisco/
Tandberg™
EX60 6.2.1  
Cisco/
Tandberg
C20 6.2.1  
LifeSize® Passport™ 4.7.0 (19)  
LifeSize Team 220™ 4.11.7 (3)
4.1.1 (17)
 
Mirial/
LifeSize
SoftPhone™ 8.1.12  
Polycom® RealPresence® Group 300/500 4.1.1-60400
4.1.3-111080
 
Polycom Classic ViewStation

128/H.323/SP/512/512MP
7.5.4
  • H.263 or H.263/H.264 modes only.

  • H.239 (content sharing) must be disabled.
Polycom VSX 6000A 9.0.6.2  
Polycom PVX Soft Client 8.0.2
8.0.4
8.0.16
In order for the Polycom PVX endpoint to interoperate correctly with the VidyoGateway, the H.264 codec must be enabled on the PVX client at all times.
Polycom HDX® 4000 3.1.0-23277 Artifacts may be observed at the Polycom endpoint for SD and HD calls in security mode.
Polycom HDX 6000 HD and
HDX 8000 HD
3.0.3.1 Artifacts may be observed at the Polycom endpoint for SD and HD calls in security mode.
Tandberg 3000MXP F9.0 Codec sends CIF for SD H.323/H.263 conference calls instead of SD.
Tely HD Pro v5.0.2-2  
Sony® PCS-1 3.41
  • H.323/H.263 call – color artifacts may occur.

  • H.323/H.264 CIF or SD call – occasionally results in flickering video.
Sony PCS-XG80 2.14.00 DTMF tones are not detected on IVR calls.
IP-PBX
Cisco CallManager 9.1.1.20000-5  
LG iPECS UCP100 1.0Ch DEC/14 Can only run CIF in non-encrypted mode.
Gatekeeper/Session Border Controller
Oracle (Acme-Packet) Net-Net 3820 SCX6.3.0 MR-2 Patch 2  
MCU
Cisco/
Codian™
MCU 4205 4.3(2.30)  
Cisco/
Codian
MCU 4501 4.3(2.30)  
Polycom DMA 7000 3.0.0_Build_5  
Polycom RPCS 800s 8.3.0.245  
Polycom RMX 2000 7.8.0.246  
Gatekeepers
Cisco VCS 7.1
8.1
 
Polycom DMA 2.4.8.1  
GNU GNUGK 3.8  

 

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.