Partners Blog Contacts

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.
  • 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 and Known Issues

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 in VidyoGateway™ version 3.5.1 (450):

VidyoGateway Version 3.5.1 - Known Issues
Key Summary
VGW-2706 SIP calls from some Avaya™ Scopia endpoints do not work; however, H.323 calls do.
VGW-2698 The hardware version of the product may sometimes display the incorrect processor type.
VGW-2663 In some cases, when a Vidyo endpoint has muted its audio, the VidyoGateway might still show its audio as enabled.
VGW-2566 Whitelisted and blacklisted IP addresses fail to download when using the Apple® Safari® browser.
VGW-2534 In some cases, H.323 participants joining Vidyo calls via audio-only service may hear announcements regarding DTMF tones for muting/unmuting their lines, but they will not be able to act upon them.
VGW-2277 The Admin UI does not prevent admins from downgrading a build.
VGW-2094 When hundreds of trusted certificate authority certificates are imported, the Security page Advanced tab takes a long time to load. In some cases, the browser may warn that the server is unresponsive.
VGW-1975 Enabling the IVR requires a default prefix; however, the Services page allows the default prefix to be deleted when the IVR is enabled.
VGW-1380 If a Polycom® HDX endpoint is receiving shared content from VidyoDesktop™ and then tries to send content, VidyoDesktop will not receive the content and, moreover, the HDX will stop showing the content being shared from VidyoDesktop.
VGW-843 DTMF tones are not detected on IVR calls using the Sony® PCS-XG80.
VGW-842 When VidyoGateway rejects calls on services that do not offer SRTP media encryption, the call is rejected with a "603 decline" message when a "488 not acceptable" message should appear instead.
VGW-585

LIFO content sharing does not work if shared content is already present in the conference. 

Workaround: If the queue is changed at all (the shared content is removed, added, or changed), LIFO works as expected.

 

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

0 Comments

Follow
Please sign in to leave a comment.