Jump to: navigation, search

Voice Platform Media Control Platform Release Notes

Release Date Release Type Restrictions AIX HP-UX PA HP-UX IPF Linux Solaris Windows
12/18/14 General X X

Helpful Links

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Voice Platform Media Control Platform.

  • This release adds support for MP3 encoding at 16kbps (default) and 24kbps, via the existing session configurable configuration parameter [mpc]mp3.bitrate.

Corrections and Modifications

This release also includes the following corrections or modifications:

Now Media Control Platform can be stopped gracefully, even when a Reporting Client is blocked from sending data to Reporting Server.
This new configuration option controls this behavior:
Option: rc.amq_thread_exit_timeout
Section: grpReporting
Valid Value: An integer greater than 0, in seconds
Default Value: 60
Takes effect: At start
Specifies in seconds the maximum time to wait for the AMQ thread to exit gracefully, after a shutdown is triggered. If not configured, the graceful exit may slow down or never complete. (GVP-21938)

Media Control Platform no longer terminates when the play cache contains an ASSERT. (GVP-21920)

Media Control Platform no longer terminates when the recording server responds to a re-INVITE with a 611 Busy Everywhere, after receiving a 491 response from MCP. (GVP-21901)

Now Media Control Platform does not revalidate an HTTP response that contains a must-revalidate directive until it has become "stale" (expired). (GVP-21865)

Media Control Platform and Resource Manager may log incorrect port information when DNS SRV records are configured. For example, SetHostUnavailble for dest[] port[5060] - port 5060 is incorrect in this log message. (GVP-21853)

Media Control Platform no longer uses a transport that is different from the original SIP request, while sending a CANCEL SIP request. (GVP-21851)

Resource Manager, Media Control Platform, Call Control Platform, and CTI Connector all now send a CANCEL request using the same transport that is used when sending an INVITE request. (GVP-21850)

Media Control Platform now correctly changes the CSeq number to 1 once it reaches the maximum of 2147483647. Previously, MCP began sending a negative CSeq number when the CSeq went above 2147483647. (GVP-21828)

Media Control Platform now retries posts during Genesys Interaction Recording (GIR) correctly, by obeying the setting in the configuration parameter [mpc].recordpostretrybackoff. Previously, MCP did not obey this setting, and sometimes took a long time to retry posts. (GVP-21823)

Media Control Platform no longer terminates when the MRCP ASR Server returns an ASR result with slot variables in an unexpected format. (GVP-21759)

MCP now correctly handles interleaved audio/DTMF packets in direct bridging mode, by dropping the interleaved audio packets. (GVP-21708)

Media Control Platform is now able to fetch files correctly, when the web server redirects it to a different address with a 302 response and Squid is used as a proxy. (GVP-21655)

Call sessions no longer become "stuck" because Media Control Platform now cleans them up properly. Previously, MCP's failure to properly clean up caused some call sessions to become stuck in MCP, which prevented a graceful shutdown of MCP by the Solution Control Interface (SCI). (GVP-21653)

To improve security, OpenSSL library (used by MCP) was updated to version 0.9.8zb (from version 0.9.8q). (GVP-21652)

Media Control Platform now detects SIT tones correctly during Call Progress Detection (CPD). Previously, MCP sometimes detected SIT tones as no answer or answering machine.
This new configuration option control this behavior: Option: cpa.enable_alternate_signals Section: grpMedia Valid Values: true, false (default) Takes effect: On start Set to true to enable CPA alternate signals checking— for when a SIT tone (or a voice following a SIT tone) arrives 100 or fewer milliseconds after a ring tone. (GVP-21651)

The SIP stack is now able to send its first message on the TCP/TLS connection. Previously, the SIP stack sometimes failed to send the first message properly. (GVP-21626)

You must follow these steps to enable inline grammar access by URL:

Windows IIS Environment

1. Verify that IIS is installed and started, and that MCP is installed.

2. Create and add the directory inlinetmp under C:\Program Files\Common Files\GCTI\www\gvp\mcp\<MCP_application>\grammar\.

The final two steps are automatically performed by the MCP installation in a Windows 32-bit environment:

3. Add the application mcp in IIS, which points to C:\Program Files\Common Files\GCTI\www\gvp\mcp.

4. Enable Directory Browsing and add the MIME type application/octet-stream for the extension * to the application mcp in IIS.

Linux Environment

1. Verify that MCP is installed.

2. Create the virtual directory /var/www/gvp/mcp/ by adding these lines of code to the file /etc/http/conf/httpd.conf:

Alias /mcp/ "/var/www/gvp/mcp/"
<Directory "/var/www/gvp/mcp/">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
    ExpiresActive On
    ExpiresDefault "now plus 5 minutes"

3. Enable the httpd service
(run chkconfig and specify level 345 httpd on)

4. Start the httpd service
(run start in the directory /etc/init.d/httpd)

5. Add the directory inlinetmp, and grant read and access permission to all files and directories beneath /var/www/gvp/mcp/<MCP_application>/grammar/ (GVP-21625)

Prompt playback no longer fails when the Media Control Platform logs the ERROR message Invalid Media - Cache track header not valid for media type audio. (GVP-21511)

The first SNMP GET to the Media Control Platform now succeeds—it no longer times out. (GVP-21357)

Media Control Platform no longer fails to copy a recording file to a drive where MCP is not installed. (GVP-21342)

Media Control Platform now correctly interprets a caller-inputted DTMF. Previously, MCP failed this task, in the Polish language. (GVP-21297)

This page was last edited on January 13, 2015, at 20:07.
Comments or questions about this documentation? Contact us for support!