9.0.046.06
Voice Platform Media Control Platform Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 03/30/21 | General | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release includes only resolved issues.
Resolved Issues
This release contains the following resolved issues:
When Speech-to-Text (STT) sessions are closed using Google, the delay in receiving the closure acknowledgement response from Google no longer impacts new Google STT requests. (GVP-43030)
Media Control Platform (MCP) no longer shuts down unexpectedly when the pointer of the audio buffer for Google Speech-to-Text is invalid. Instead, an error is logged. (GVP-42935)
A solitary # character cannot be the value of the src attribute in a VXML application. MCP now detects the invalid solitary # and throws a semantic error. Previously, MCP shut down in such a scenario. (GVP-42817)
When tenant and/or IVR Profile names include “&”, “<”, or “>”, then Nuance may respond with an error if using MRCPv2. A new configuration parameter, [vrm]client.EscapeContent, has been introduced in MRCPv2 ASR/TTS Speech Resource configuration files. [vrm]client.EscapeContent is applicable only if the existing configuration parameters [vrm]client.SendSessionXML and [vrm]client.SupportForNuance11 are both set to true. The behavior is described as follows:
- If they are both set to true, MCP replaces the default company name and application name parameters with the Tenant name and IVR Profile name (chosen for the call) in the default session.xml file sent to Nuance (ASR or TTS). This is the existing behavior which remains unchanged.
- If [vrm]client.EscapeContent is set to true, the special characters "&", "<", and ">" are encoded in both the Tenant and IVR Profile names in the session.xml file sent to Nuance. Without encoding, Nuance may respond with a 503 error.
- If the value of [vrm]client.EscapeContent is not set, it defaults to false.
(GVP-42803)
The CallUUID is now appended into call_reference metrics. See the following example:
<metric id="56" label="call_reference">
<meaning>Call Reference</meaning>
<description>This maps the association between SIP Call-ID, GVP-SESSION-ID, GVP-Tenant-ID, IVRProfile Name and X-Genesys-CallUUID</description>
<format>
<field name="Network ID"/>
</format>
<field-description name="Network ID">SIP Call-ID, GVP-SESSION-ID,GVP-Tenant-ID, IVRProfile Name, X-Genesys-CallUUID</field-description>
<constant>VGLOG_CALL_REFERENCE</constant>
<example>call_reference NmRlODA5OWMwZWM2N2U0ZWQ0MzI4YmRlZmUzNTE4MGI.|F7966BC2-EA13-4829-7EB5-DF0BF04593D7|N/A|N/A|N/A</example>
<example>call_reference ZDc2ZDQ5ZjY0NTcxNDNiYzJiNjY3NGY4ZDAzMzcxMjQ.|21E26056-8F17-42F4-5A9A-4A47EB4F0D3C|tenant_B|IVRProfile_Y|01KMPL0B2GFPJBVNTR8KG2LAES013WER</example>
</metric>(GVP-42780)
MCP no longer fails an MRCPv2 session when the server responds with an SDP that lists the m=application line after the m=audio line. Previously, MCP failed the session in such a scenario. (GVP-42723)
When the MCP configuration parameter [fm]https_proxy is blank, MCP would previously use the Google proxy (set in the Google ASR/TTS RAP parameter vrm.client.resource.proxy) in error when fetching https files. Now, MCP no longer uses a proxy to fetch HTTPS files in this scenario. (GVP-42664)
Calls to the MCP, when it has an incorrect confidencelevel property set, no longer generates an additional, unnecessary parse_error. (GVP-42586)
MCP no longer sends an additional RTP stream as long as SRTP is negotiated. Previously, when MCP had the srtp mode enabled (except offer_selectable) and the remote server offered both RTP and SRTP, MCP would send two RTP streams using RTP and SRTP, respectively. (GVP-42488)
Upgrade Notes
No special procedure is required to upgrade to release 9.0.046.06 .