Revision as of 18:53, December 8, 2015 by Sschlich (talk | contribs) (What's New)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

8.5.140.00

Voice Platform Media Control Platform Release Notes

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

Helpful Links

What's New

This release contains the following new features and enhancements:

  • You can now direct Resource Manager to not reapply RURI capability when falling back to VXML after CTIC returns a 404 error. Previously, reapplying RURI capability caused the fallback to fail.
    Use a new configuration option in the Gateway LRG section in order to achieve this functionality:

    remove-ruri-capability-on-fallback
    Section: Gateway Resource group section
    Valid Values: true or false (default)
    Set to true to disable Resource Manager's use of the gvp.rm.resource-req option's capability during VXML fallback after a CTIC 404 error.
    Set to false, to enable Resource Manager's use of the gvp.rm.resource-req.
    Note: This option is NOT available during configuration of a Gateway Resource Group via Genesys Administrator. Specify this parameter manually in the Gateway Logical Resource Group (GW LRG) section, using the format remove-ruri-capability-on-fallback = true (or = false).
    • Use the option mediamgr.recordmp3audiobuffer to configure duration of the MP3 recording buffer.

      mediamgr.recordmp3audiobuffer
      Section: mpc
      Valid Values: an integer 2000 or greater
      Default: 4000
      Takes effect: At start/restart.
      Specifies the duration of the audio buffer for MP3 recording, in milliseconds.
      • The Media Control Platform's NGI VXML interpreter supports caching of JavaScript (JS) content, which improves performance. Use the following configuration options to set the values for this functionality: maximum count of cached script, maximum cache size, minimum cached script size, and enable or disable script caching:

        compiled_script_cache.max_cached_scripts_count
        Section: vxmli
        Valid value: An integer 0–1,000,000
        Default: 10,000
        Takes effect at start/restart. Specifies the maximum number of scripts that may be cached concurrently.

        compiled_script_cache.max_cache_size
        Specifies the maximum size, in bytes, of all concurrently cached scripts.
        Section: vxmli
        Valid value: An integer 0-50,000,000
        Default: 2,000,000
        Takes effect at start/restart.

        compiled_script_cache.min_cached_script_size
        Specifies the minimum size, in bytes, of a script to be cached.
        Section: vxmli
        Valid value: An integer 0- 1,000,000,000
        Default: 200
        Takes effect at start/restart.

        compiled_script_cache.enable
        Enables/disables ECMAScript caching in the VoiceXML interpreter.
        Section: vxmli
        Valid value: false (default) or true
        Takes effect at start/restart.
        • MCP now supports mono-channel recording during MSML GIR recording for all file formats. Use these configuration parameters to specify the channel information:
          (The two IVR profile parameters below are in the gvp.service-parameters section of the IVR profile record.)

          recordingclient.channels
          Specifies the number of channels that MCP must use for MSML GIR recording.
          Valid values: fixed, 1 (mono) or 2 (stereo, the default)
          Takes effect immediately.

          recordingclient.channels2
          Specifies the number of channels that MCP must use for MSML GIR recording.
          Valid values: fixed, 1 (mono) or 2 (stereo, the default)
          Takes effect immediately.

          If the above parameters are missing from the IVR profile configuration, then MCP uses the parameters below as substitutes, to determine the type of recording (mono or stereo).

          msml.record.channels
          Specifies the number of channels that MCP must use for MSML recording to dest.
          Valid values: 1 (mono) or 2 (stereo, the default) Takes effect immediately.

          msml.record.channels2
          Specifies the number of channels that MCP must use for MSML recording to dest2.
          Valid values: 1 (mono) or 2 (stereo, the default)
          Takes effect immediately.
        • The Media Control Platform supports DTMF clamping (also known as masking) while agent and caller are in conference with IVR. See MCP release 8.5.130.93 for details.
          • 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.
          • The Media Control Platform supports mp3 compression at 8kbps for mono recording. The default compression remains 16kbps. Use the setting [mpc]mp3.bitrate=8 to enable 8kbps mono recording.
          • The Media Control Platform supports 100 percent recording (success) on as many as 1,000 concurrent recordings on a single physical server.
          • Resource Manager now supports dynamic updating of a child tenant name change.



          Resolved Issues

          This release contains the following resolved issues:


          Third-party recording applications no longer consume excessive memory. (GVP-22567)


          The Resource Manager thread no longer freezes due to an internal error when RM retries an INVITE with a different MCP target. (GVP-22561)


          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 ResponseElement (with the failure reason) only after receiving a POST trigger action request with an incorrect tenant name. Previously, SSG responded that way to every outbound request.

          (GVP-22449)


          The description of the new parameter [fm]revalidatestaleresponse is incorrect inside the MCP configuration XML file (mcp.xml). You can find the correct description in the What's New section of the MCP 8.5.130.93 Release Note. (GVP-22421)


          The Media Control Platform no longer terminates unexpectedly when it encounters a socket error while sending the response to a SIP message that has no branch in the via header. (GVP-22412)


          MCP no longer terminates during a bridge transfer from a caller with a display name that contains the symbol <. (GVP-22411)


          MCP no longer provides anonymous download access to recording files uploaded to Amazon Simple Storage Service (S3) during MSML GIR recording. (GVP-22395)


          The Media Control Platform no longer terminates after a call transfer failure. (GVP-22368)


          The Resource Manager no longer terminates unexpectedly when it encounters a socket error while sending the response to a SIP message that has no branch in the via header. (GVP-22293)


          MCP no longer terminates after application connections were updated. (GVP-22292)


          Media Control Platform no longer terminates when a URL ends with the fragment separator #. (GVP-22284)


          SIP INFO DTMF messages generated by Media Control Platform during a conference now conform to the standard format, which enables third-party software to read these messages. (GVP-22259)


          Difficulties when sending SIP responses no longer cause MCP to leak calls. (GVP-22258)


          The Resource Manager now correctly calculates usage-limits even when the gvp.site weight property for the RM site is empty or set to 0. (GVP-22222)


          When falling back to VXML after CTIC returns a 404 error message, Resource Manager no longer uses the capability specified in the cti-capability-requirement option to select a VXML resource. (GVP-22221)


          The Media Control Platform can now correctly expose a header with multiple dots (.) in its name, when comparing the header with a key from session_vars. (GVP-22216)


          The MRCPv1 client now correctly picks an alternate port once it reaches the edge of the port range. (GVP-22215)


          Now, when the Media Control Platform is configured with connections to a primary and backup MRCP Proxy, MCP can use the MRCP Proxy backup server if it is needed when the Configuration Server is not accessible and the local configuration file of the MCP is used. (GVP-22213)


          [ems]rc.certificate is now a default parameter of the Resource Manager application template (GVP_RM.tpl). This parameter identifies the TLS Certificate for Reporting Client. The TLS Certificate file name is required to be in PEM format, for connection to the Reporting server (ActiveMQ) over TLS. (GVP-22191)


          Resource Managers that are configured in a high availability pair no longer stop unexpectedly because a socket in a race condition closed while one of them was sending data. (GVP-22163)


          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)


          When handling SRTP packets, the Media Control Platform no longer terminates calls with the error message Error 7 decrypting an SRTP packet. (GVP-21498)


          When in a high availability configuration, the Resource Manager node now reports the status of SIP, and the status of SIPS AOR of a physical resource, separately to the other RM node. (GVP-21068)


          The Resource Manager (RM) MIB data (which is stored in a scalar table) for an active-active deployment mode now reflects the correct call statistics when RM is run in a high availability active-active configuration. (GVP-20257)




          Upgrade Notes

          No special procedure is required to upgrade to release 8.5.140.00.

          This page was last edited on December 8, 2015, at 18:53.
          Comments or questions about this documentation? Contact us for support!