Jump to: navigation, search

8.5.140.88

Voice Platform Supplementary Services Gateway Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
08/31/15 General X X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • SSG now supports including custom HTTP response headers in the HTTP responses to HTTP requests. Enable this behavior with the [http]ResponseHeaders configuration parameter. Enter the value in this format: Header1:Value1|Header2:Value2
      Notes:
    • If your value includes the characters | or :, precede them with a backslash (\| or \:).
    • The default value for this parameter is X-Frame-Options:DENY—part of Genesys software defense against “clickjacking”.
    • This also applies to accessing the SSG root page.



    Resolved Issues

    This release contains the following resolved issues:


    Voice Platform Supplementary Services Gateway (SSG) now strict-checks the case of TenantName before accepting a trigger action request. Previously, not checking for the correct case meant that Genesys Administrator did not display tenant-related and IVR profile-related stats in the SSG dashboard.

    Notes:

    • Allow all DB requests to process completely before upgrading. Any unprocessed old requests present in the DB after the upgrade may get expired.
    • SSG now returns a single ResponseElement (with the failure reason) after receiving a POST trigger action request with an incorrect tenant name. Previously, SSG responded that way to every outbound request in the HTTP POST body.

    (GVP-22449)


    The first SNMP GET to the SSG now succeeds—it previously timed out. (GVP-21749)


    The version of OpenSSL library that the Supplementary Services Gateway uses was updated from the previous version 0.9.8q, to 0.9.8zb, to address a security vulnerability. (GVP-21728)




    Upgrade Notes

    No special procedure is required to upgrade to release 8.5.140.88. However, you must ensure that all DB requests have processed completely before upgrading. Any unprocessed old requests that are present in the DB after the upgrade may become expired.

  • Feedback

    Comment on this article:

    blog comments powered by Disqus
    This page was last modified on August 31, 2015, at 10:37.