| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 8.0.004.53 [09/30/08] – Hot Fix | X | |||||
| 8.0.004.49 [09/25/08] – Hot Fix | X | |||||
| 8.0.004.43 [06/27/08] – General (Under Shipping Control) | X |
As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.
This release note applies to all 8.0 releases of Voice Platform Media Control Platform.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
When fetching a DTMF grammar, the platform now correctly uses the timeout value that is set by the fetchtimeout property or the fetchtimeout attribute in the <grammar> tag in the VoiceXML application.
Previously, the timeout to fetch a DTMF grammar was hard-coded, with a value of 1 second;
therefore, attempts to fetch a DTMF grammar might fail. (ER# 208999651)
Within an Automatic Speech Recognition (ASR) session, the Media Control Platform now treats a prompt status of IDLE as if a prompt has not started playing.
As a result, the Media Control Platform no longer exits if a DTMF grammar fails to be fetched or parsed successfully within an ASR session.
The Next Generation Interpreter (NGI) sends a message to abort media play if it fails to fetch or parse a DTMF recognition grammar while it is also fetching audio.
Previously, the resulting prompt status signal to the ASR session was logically inconsistent with the prompt status of IDLE,
and this caused the Media Control Platform to throw an assertion error and exit. (ER# 206776986)
The NGI now correctly handles relative URIs that contain :// in the query string.
Previously, the function to determine a relative URI returned an incorrect result if a parameter in the query string contained ://, and the NGI would omit the
http://host part of relative URIs that it returned. (ER# 206950035)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This section describes new features that are introduced in this release of Voice Platform Media Control Platform.
The Media Server module of the Media Control Platform (MCP) now has an Inband Dual Tone Multi-Frequency (DTMF) detection and generation feature. Inband DTMF detection allows the platform to detect tones that are sent as audio tones in the media stream, unlike detection events through SIP INFO or RFC2833 that are prevalent in other detection mechanisms.
The Media Control Platform can now be configured to perform the following conversions (or pass the audio event along unchanged):
INFO DTMF events.
INFO DTMF events.
INFO DTMF events to inband DTMF events.
INFO DTMF events to RFC2833 events.
The Media Control Platform maintains the quality of inband DTMF detection by using and supporting only µLAW and ALAW codecs. Other codecs can be used, but the nature of the signaling process increases the chances of non-detection.
This release introduces the following configuration options in the [mpc] section of the MCP application to support the new functionality:
rtp.dtmf.receive
Default Value: SIPINFO INBAND
Valid Values: SIPINFO INBAND, SIPINFO, INBAND, NONE
Specifies the method by which DTMF is received in a Real Time Protocol (RTP) session if a telephone-event (RFC2833) is not negotiated in the Session Description Protocol (SDP) of the SIP INVITE message to the MCP. Use the following valid values for this option:
SIPINFO INBAND (the default value)—both the SIPINFO and the INBAND detection methods are enabled, but inband DTMF detection is not supported if a telephone-event is negotiated.
SIPINFO—only the SIPINFO detection is enabled, but SIPINFO detection is supported even if a telephone-event is negotiated.
INBAND—only the INBAND detection is enabled, but INBAND detection is not supported if a telephone-event is negotiated.
NONE—neither the SIPINFO nor the INBAND detection method is supported, which implies that only RFC2833 event detection is supported.
rtp.dtmf.send
Default Value: INBAND
Valid Values: SIPINFO, INBAND
Specifies the method by which the MCP generates DTMF events in an RTP session if a telephone-event (RFC2833) is not accepted in the SDP negotiation. This parameter should be set with only one value—either SIPINFO or INBAND. Setting this parameter with both values is not permitted. Use the following valid values for this option:
INBAND (the default value)—DTMF tones are generated and sent as audio tones in the media stream.
SIPINFO—DTMF events are sent through SIP INFO messages.
dtmf.minduration
Default Value: 0
Valid Values: >=0
Specifies the minimum duration, in milliseconds, of DTMF events—either Inband or RFC2833—required before a DTMF event is detected by the dialog. This option must have a value equal to or greater than 0 milliseconds.
dtmf.maxsilence
Default Value: 20
Valid Values: >=0, <=120
Specifies the maximum duration of silence allowed, in milliseconds, between inband DTMF tones of the same type until it is no longer considered part of the same DTMF tone. This option must have a value equal to or greater than 0 milliseconds and less than or equal to 120 milliseconds.
dtmf.detectedge
Default Value: 0
Valid Values: 0, 1
Specifies whether a DTMF is recognized on the rising edge (0), meaning the first RFC2833 packet is received, or on the falling edge (1), meaning one of the following events has occurred:
E bit set is received.
dtmf.gapsilence
Default Value: false
Valid Values: true, false
Specifies whether or not the duration of the gap set in the mpc.dtmf.gap option is used. If the dtmf.gapsilence option is set to true, the gap between the DTMF RTP packets is filled with silence data; if set to false, the gap is not filled with silence data. The silence data is based on the default audio format of the platform, but is transcoded to the appropriate audio output format.
(ER# 202084971)
This release does not include any corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is the first release for this product. This release is under shipping control. This section describes new features that were introduced in the initial 8.0 release of Voice Platform Media Control Platform.
This release includes the following corrections and modifications:
No corrections or modifications have been made in this release.
This section provides the latest information on known issues and recommendations associated with this product.
When using Nuance Speech Server 5.0.3 on both MRCPv1 and MRCPv2, the <audio> tag that references invalid audio files within a <voice> tag may cause the prompt to be cutoff. See Nuance ticket number ST806120161. (ER# 192976501)
| Found In: 8.0.004.43 | Fixed In: 8.1.001.82 |
A syntax error occurs when using a VoiceXML application to call a Nuance OSDM application that uses the default waveform parameter. This occurs because the OSDMs include the statement <var name="waveform" expr=""/> which is an invalid VoiceXML expression. To workaround this, update the OSDM JSP file to use the following syntax: <var name="waveform"/>, or <var name="waveform" expr="''"/> (single quotes within the double quotes). See Nuance ticket number ST806170211. (ER# 192949491)
| Found In: 8.0.004.43 | Fixed In: 8.1.001.82 |
Execution of a REFER with Replaces transfer to an agent will succeed only
if the caller supports REFER and the agent supports the
Replaces header (in other words, there is no fallback
mechanism for sending REFER with Replaces to an agent). (ER# 189274831)
| Found In: 8.0.004.43 | Fixed In: 8.1.001.82 |
During 96 channel load testing, Nuance Speech Server may fail to create recognizer instances after 12 hours. See Nuance ticket number ST805260061. (ER# 190852851)
| Found In: 8.0.004.43 | Fixed In: 8.1.001.82 |
When using MRCPv2 with TLS, Nuance fails to synthesize very large text. See Nuance ticket number ST803310161. (ER# 185264953)
| Found In: 8.0.004.43 | Fixed In: 8.1.001.82 |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.
There are no discontinued items for this release.
Information in this section is included for international customers.
There are no known internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Genesys Voice Platform 8.0 Deployment Guide, which provides information to install and configure GVP.
Genesys Voice Platform 8.0 User’s Guide, which provides information about the configuring, provisioning, and monitoring of GVP and its components.
Genesys Voice Platform 8.0 VoiceXML 2.1 Help, which provides information about developing VoiceXML applications. It presents VoiceXML concepts and provides examples that focus on the GVP implementation of VoiceXML.
Genesys Voice Platform 8.0 CCXML Reference Manual, which provides information about developing CCXML applications for GVP.
Genesys Voice Platform 8.0 Troubleshooting Guide, which provides information about SNMP MIBs and traps for GVP, as well as troubleshooting methodology.
Genesys Voice Platform 8.0 Configuration Options Reference, which replicates the metadata available in the Genesys provisioning GUI to provide information about all the GVP configuration options, including descriptions, syntax, valid values, and default values.
Genesys Voice Platform 8.0 Metrics Reference, which provides information about all the GVP metrics (VoiceXML and CCXML application event logs), including descriptions, format, logging level, source component, and metric ID.
Voice Platform Solution 8.0 Integration Guide, which provides information about integrating GVP 8.0 and SIP Server 7.6.
Composer Voice 8.0 Deployment Guide, which provides installation and configuration instructions for Composer Voice.
Composer Voice 8.0 Help, which provides online information about using Composer Voice, a GUI for the development of applications based on VoiceXML and CCXML.
Framework 8.0 Deployment Guide, which provides information to configure, install, start, and stop Framework components.
Framework 8.0 Genesys Administrator Help, which provides instructions for configuring and provisioning contact center objects using Genesys Administrator.
Framework 8.0 Configuration Options Reference Manual, which provides descriptions of configuration options for Framework components.
Framework 7.6 SIP Server Deployment Guide, which provides information to configure and install SIP Server.