Voice Platform Media Control Platform Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Mac||Solaris||Windows|
This release contains the following new features and enhancements:
Two new options are introduced in Media Control Platform (MCP):
- [sip]logmsg.allowed - Specifies whether or not logging SIP message is allowed. This option can disable SIP message logging regardless of the [log].verbose setting. By default, this option is set to true.
- [sip]logmsg.maskoption - Specifies the option to restrict SIP message logging. Each bit in the value, starting with the Least Significant Bit (LSB), indicates that a specific entity of the SIP message is masked. These bits can be logically OR'ed (or numerically added) and the final value is set. Currently the following bits are supported:
- value 1 - indicates that all the unknown headers (headers other than Via, From, To, Max-Forwards, CSeq, Call-ID, Contact, Content-Length, Content-Type, Record-Route, Route, Refer-To, Allow-Events, Subscription-State, Event, RSeq, and RAck) are masked.
- value 2 - indicates that all the user data headers (headers starting with X-Genesys- except X-Genesys-GVP-Session-Data, X-Genesys-GVP-Session-ID, and X-Genesys-CallUUID) are masked.
- value 4 - indicates that all the SIP message bodies are masked.
- value 8 - indicates that the SIP message bodies with the content type application/dtmf-relay or application/dtmf are masked.
- value 16 - indicates that the values of the Media Server Markup Language (MSML) tag gvp:param with the name starting with X-Genesys- in the SIP message bodies are masked.
- For example, to mask all the unknown headers and message bodies, set the value to 5 (i.e. 1 + 4). To mask all the user data headers and the values of the MSML tag gvp:param with the name starting with X-Genesys- in SIP message bodies, set the value to 18 (i.e. 2 + 16). The default value is 0, which means no masking at all.
This release contains the following resolved issues:
When the MCP Configuration parameter [msml]record.channels2 is set to 2, MCP now generates a stereo audio file. Previously, MCP generated a mono audio file by mistake. The bug was introduced in 9.0.026.26. (GVP-42210)
MCP now performs SDP negotiation against local SDP for the re-INVITE transaction initiated by 3rd-party recording server in order to avoid wrong encoding of recording streams. (GVP-41561)
During IVR recording, MCP no longer crashes with an assert if there is an error in parsing the command, for example, when there are spaces (which are not allowed) in a parameter value. An error.internal event is now thrown instead. (GVP-41246)
No special procedure is required to upgrade to release 9.0.042.31.