Jump to: navigation, search


Section: fm
Default Value: 1
Valid Values: Choose between: 0 or 1
Changes Take Effect: At start/restart

The purpose of this parameter is to try to minimize the number of small packets on the network (where "small packets" means TCP segments less than the Maximum Segment Size (MSS) for the network). If set to 1, small data segments are sent without delay (that is, without waiting for acknowledgement from a peer). Nagle algorithm will be disabled.


Section: mpc
Default Value: 7
Valid Values: A number between 1 and 9 inclusive.
Changes Take Effect: Immediately/session

This parameter can be used to specify the quality level of the mp3 file from the current encoder, with 1 the highest and 9 the lowest quality. This parameter takes effect only when [mpc].mp3.use_current_encoder is true.


Section: mpc
Default Value: true
Valid Values: Choose between: true or false
Changes Take Effect: Immediately/session

This parameter can be used to specify the type of the current MP3 transcoder. When set to true, an integer implementation is used. If set to false, a floating point implementation is used. This parameter takes effect only when [mpc].mp3.use_current_encoder is true.


Section: mpc
Default Value: false
Valid Values: Choose between: true or false
Changes Take Effect: Immediately/session

This parameter can be used to specify whether to use the current encoder for Stereo MP3 Encoding or not. If not, the Legacy version will be used.


Section: mpc
Default Value: 0
Valid Values: Choose between: 0, 2, 15, 16, 17 or 18.
Changes Take Effect: Immediately/session

This parameter specifies CPA result if no ringback is detected before postconnect event arrives. Default is none, that is, no CPA result returned. 0 - none 2 - busy 15 - human 16 - machine 17 - fax 18 - no_media

Voice Platform Media Control Platform Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
09/15/17 General X X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • Media Control Platform (MCP) no longer sends the swirec.secure_context or swirec.mute_wcr property to the ASR server through MRCPv1. Nuance Recognizer does not support these parameters with MRCPv1.
  • A new MCP configuration option cpa.no_ring_result specifies the call progress analysis (CPA) result if no ringback is detected before the postconnect event arrives. The default option value is none (0), that is, postconnect CPA proceeds normally after the postconnect event arrives. Other valid values are busy (2), human (15), machine (16), fax (17), and no_media (18). If this option value is set to any one of these values, the specified CPA result is returned immediately after the postconnect event arrives, and no further CPA occurs.
  • MCP now supports MRCP 201 response. Previously, MCP was sending an error response for 201 responses.
  • MCP now supports a new codec library for MP3 encoding/decoding. Using this codec library resolves the issue where MCP unexpectedly terminates in specific environments while performing MP3 recording using the earlier MP3 encoding library. As this issue occurs only in specific environments, Genesys recommends continuing with the existing default configuration if no issues are observed while performing MP3 recording. The legacy codec continues to be available and is set as the default option.
The default option can be changed using the parameter mp3.use_current_encoder. The other new parameters are:
Note: The legacy codec has a bug when writing MP3 format audio, and it is not being evolved by Intel. Prototyping has indicated that the new codec does not exhibit this behavior, but does have somewhat lower performance.
  • MCP now supports configuring the TCP_NODELAY option for LibCurl. Enabling enabletcpnodelay (default) causes small segments of data to be sent without delay (disabling the Nagle algorithm).

Resolved Issues

This release contains the following resolved issues:

MCP no longer crashes during heavy load IVR Recording scenarios. Previously, during some extreme scenarios, the VXML call leg was terminated before the IVR recording started, due to delays in the media layer. (GVP-24088)

MCP now terminates the call and throws a trap when the allocated JS memory limit for the call is exceeded. Previously, MCP continued processing the call and terminated after running out of JS memory. (GVP-24192)

MCP now respects the value in msml.record.amazonpostmode parameter used to perform the Get bucket location request required for the Amazon Web Services (AWS) V4 signature. Previously, the AWS Get bucket location request required for the V4 Signature did not respect the msml.record.amazonpostmode configuration, and used HTTP, even when it was configured to use HTTPS. (GVP-24007)

When Voiceprint CPD is enabled with a short postconnecttimeout value, MCP returns cpd.silence as the CPD result if it does not detect the actual CPD result. Previously, MCP sent cpd.preconnect_timeout as the CPD result when the postconnect event arrived. (GVP-23943)

MCP now validates the namelist elements of the send tag by evaluating them. If an element is found to be a Document Object Model (DOM) object, MCP returns an error and does not process the namelist further. Previously, MCP crashed when the DOM object was sent as a namelist property. (GVP-23874)

Timestamps of Real-time Transport Protocol (RTP) packets sent to a third-party recording server now reflect the real-time stream when DTMF interleaves with audio packets. Previously, when MCP forwarded audio/DTMF interleave packets to a third-party recording server, the timestamps that the recording server relied on, were disarrayed. This resulted in the caller's audio stream becoming unsynchronized in the recorded file. (GVP-23821)

MCP now reuses the SIP request’s TCP connection when responding to the request. Previously, MCP tried to initiate a new TCP connection to the FQDN or IP (and port) present in the VIA header of the request. As a result, MCP failed to send a SIP response to the request if the remote did not accept a new TCP connection (for example, if the remote was a F5 load balancer or Genesys Composer). (GVP-35065)

Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on October 23, 2017, at 10:12.
Comments or questions about this documentation? Contact us for support!