Voice Platform Media Control Platform Release Notes
|Release Date||Release Type||Restrictions||AIX||HP-UX PA||HP-UX IPF||Linux||Solaris||Windows|
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.
- Additional features in support of the Genesys Interaction Recording (GIR) Solution:
- Call Recording Encryption Support.
- Stereo MP3 encoding for call recording.
- Submission to S3 storage and webDAV support.
- Interactions with GIR.
Corrections and Modifications
This release also includes the following corrections or modifications:
The Media Control Platform no longer terminates in a race condition when a SIP INFO message is sent before a VXML session was terminated, but the response to that message was received after the termination. (GVP-20939. 20937, 20773, 20704, and 20699)
The Media Control Platform no longer terminates when it fails to send a SIP response due to a network failure. Previously in this scenario, the MCP would run into an infinite loop and eventually terminate when it ran out of stack space. (GVP-20882)
MCP no longer changes the cookie during a call. Previously, MCP applied the cookies from cached files (from other sessions) in error. (GVP-20824)
The Media Control Platform no longer drops the buffered DTMF digits that are supposed to be sent to an off-board DTMF recognizer, when moving to the next input field without any prompt. (GVP-20820)
MCP no longer terminates while handling an ASR reply. (GVP-20794)
A new timer prevents a conference recording from continuing when the call disconnects before anyone joins the conference. (GVP-20758)
The MCP no longer tries to decode an intentional % character in an HTTP URL. (GVP-20735)
MCP no longer terminates during mp3 recording. Previously, this situation was caused by the encoder generating multiple frames at a lower bitrate. (GVP-20734)
The MCP now ignores uppercase and lowercase differences between a pathname and a prompt when fetching (for example, pathname/prompt.wav and PATHname/PRompt.wav). Previously in this scenario, the MCP might be unable to play the file when the play cache was enabled. (GVP-20731 and 20808)
MCP now supports specifying one recdest or recdest2 through MSML RURI and the other through gvp:param. Previously, both recdest or recdest2 needed to be specified either through MSML RURI or through gvp:param. (GVP-20683)
Now, more than one stream can be recorded when both PCMU and PCMA negotiate in one of multiple call legs before a conference is created. (GVP-20677)
The default encoding bitrate for mp3 recording was changed from 128kbps to 32kbps. (GVP-20671)
Recordings from MCP in GSM format no longer contain intermittent static. The GSM library has been updated to use the new thread-safe version of the library with no impact to the original recording quality. (GVP-20660)
Unknown IDs no longer occur under the default setting in the MF Sink Metrics Filter, because the metrics log entries 133 and 136-141 have been removed. (GVP-20656)
MCP no longer returns unknown after a successful media redirect transfer is terminated by the far end. Previously in this scenario, MCP sent a Re-INVITE to bring the inbound call back, and if there was a delay for the remote to send back 200OK to the Re-INVITE, then a race condition occurred with the new outbound call request of the next transfer. (GVP-20640 and 20644)
The MCP can now log the correct prompt status as barge-in when a DTMF digit is buffered before the prompt file is fetched. (GVP-20572)
When custom headers are added, MCP no longer ignores the INVITE from Resource Manager due to a logic error when parsing the Content-Length header. (GVP-20528)
During multiple Media Redirect transfers from within the same application, subsequent transfers no longer fail due to race conditions in the MCP. (GVP-20526)
During GQM recording, if the MCP triggered a session reINVITE at the same time that the recorder triggered a reINVITE, the result could be the MCP terminating unexpectedly. (GVP-20421)
In some rare race conditions, typeahead DTMFs or RRU data is now transmitted properly to the ASR engine. (GVP-20417)
The MCP no longer terminates in an HA mode when a destination could not be reached. (GVP-20409)