Voice Platform Media Control Platform Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
MCP now sends the SIP CANCEL message to terminate the MRCPv2 transaction if the remote server cannot send a 200 OK response before the configured duration for receiving the final response expires. (GVP-41144)
Google limits the size of each context phrase sent to it via the VoiceXML property “speech_context” to 100 characters. A delimiter "|" is introduced to separate the phrases set in this property. The Google limit for number of phrases is 5000. For example:
<property name = "com.genesyslab.asr.speech_context" value = "first phrase | second phrase" />
Note that each individual phrase among the phrases delimited by "|" is still subjected to the 100-character limit. (GVP-41013)
MCP no longer terminates unexpectedly during a gRPC TTS session that is aborted due to a call hangup. Previously, in a few rare occurrences in similar scenarios, MCP terminated. (GVP-40994)
gRPC sessions no longer stop responding for a long time when there is a connectivity issue with the gRPC server. For GSR/STT, a noinput timeout or a VRM gRPC client timeout gives control back to the VoiceXML application by throwing a noinput or error.internal event. Previously, at times, the VoiceXML session was stuck with GSR for a considerable duration in such scenarios. For GTTS, a VRM client timeout will continue to trigger the error.tts event in VoiceXML, as usual.
A new configuration option, [vrm] client.grpc.timeout, is added for changing the gRPC client timeout. (GVP-40654)
No special procedure is required to upgrade to release 9.0.036.53.