Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.700.14 [07/26/13] – General (Under Shipping Control) | X | X | ||||
8.1.601.95 [12/19/12] – General (Under Shipping Control) | X | X | ||||
8.1.502.62 [04/20/12] – General (Under Shipping Control) | X | X | ||||
8.1.410.04 [08/24/11] – General (Under Shipping Control) | X | X | ||||
8.1.401.05 [04/29/11] – General (Under Shipping Control) | X | 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.1 releases of Genesys Voice Platform (GVP) MRCP Proxy.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Contact your customer care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of MRCP Proxy.
No corrections or modifications were made in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of MRCP Proxy.
This release includes the following corrections and modifications:
The following problem is solved: When MRCP Proxy was configured as HA pair (active-standby) and during initialization, MCP connected to the standby MRCP Proxy first, the proxy instance accepted the MCP connection and then immediately disconnected (as running on standby mode). However, as MCP was not fully initialized yet, it failed to handle the disconnect. As a result MCP was not aware of the disconnect and did not perform failover to the active MRCPProxy. (ER# 304105231, 304105221)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of MRCP Proxy.
This release includes the following corrections and modifications:
When the Genesys Voice Platform MRCP Proxy is started, the build information is printed in its log file in the following order:
Note that in the Linux operating system, if the ident
utility
is not installed, then the MRCP Proxy versions are not printed. (ER# 284220141)
The Genesys Voice Platform MRCP Proxy no longer creates a Windows registry entry each time it is started. Now, one entry is created the first time that MRCP Proxy starts after it has been installed. (ER# 281806924)
The Genesys Voice Platform MRCP Proxy no longer incorrectly sets the port to
zero in the outgoing INVITE
's Via
header when sip.transport.x
is configured with an actual IP address. (ER# 281245911)
The Genesys Voice Platform MRCP Proxy now sends a 404
response
to Media Control Platform (MCP) as soon as the PING
request to
MRCP servers fail and MCP sends TEARDOWN
to MRCP Proxy. Previously,
when the MRCP Proxy was connected directly to the MRCP server and the connection
failed, it did not immediately notify the MCP of the failure. Therefore, the
MCP did not immediately generate an ASR/TTS error. (ER# 270328551)
MRCP Proxy now sends a 404
response to Media Control Platform
(MCP) as soon as the PING
request to MRCP servers fail and MCP
sends TEARDOWN
to MRCP Proxy. Previously, when the MRCP Proxy was
connected directly to the MRCP server and the connection failed, it did not
immediately notify the MCP of the failure. Therefore, the MCP did not immediately
generate an ASR/TTS error. (ER# 270328551)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this initial release of Voice Platform MRCP Proxy.
No corrections or modifications have been made in this release.
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 this initial release of Voice Platform MRCP Proxy.
This release includes the following corrections and modifications:
The logging path for the ccilib.*.log
has been changed in the
log.all
configuration option so that logs are now stored in a non-GVP
directory. (ER# 268953628)
This section provides the latest information on known issues and recommendations associated with this product.
In RHEL 6.x, MCP and MRCP Proxy should not co-exist in the same machine. Performance suffers.
Workaround: Specify that the MRCP Proxy listen on a port that doesn't conflict with other ports / port ranges in various GVP components residing on the same machine. (GVP-20268)
Found In: 8.1.700.14 |
Fixed In: |
When Nuance Speech Servers are overloaded and are running out of licenses,
they return the message 500 Server Internal Error
for any subsequent
requests from MRCP Proxy or MCPand the request fails.
Workaround: Provision Nuance licenses based on the expected capacity of the deploymentthe number of peak concurrent GVP ports that use ASR and TTSso that the Nuance Speech Servers do not run out of concurrent licenses. (ER# 303031051)
Found In: 8.1.502.62 | Fixed In: |
When MRCP Proxy is configured as an HA pair (active-standby), and MCP connects to the standby MRCP Proxy first during initialization, the proxy instance accepts the MCP connection and then immediately disconnects (because it is running on standby mode). However, because MCP is not fully initialized yet, it fails to handle the disconnect correctly. As a result MCP is not aware of the disconnect and does not perform a failover to the active MRCP Proxy. (ER# 304105221)
Found In: 8.1.410.04 | Fixed In: |
When MRCP Proxy is loaded with heavy traffic and Nuance MCRP and License Server(s) are re-started, the proxy may terminate while cleaning up existing sessions with the disconnected servers. Genesys recommends that you alter licenses or other configurations for the Nuance Servers when MRCP Proxy is not loaded (e.g., during off-business hours or a maintenance window). (ER# 303370657)
Found In: 8.1.502.62 | Fixed In: |
When the MRCP Proxy is connected directly to the MRCP server and the connection fails, it does not notify the Media Control Platform of the failure immediately. Therefore, the Media Control Platform does not generate an ASR/TTS error immediately. (ER# 270328551)
Found In: 8.1.401.05 | Fixed In: 8.1.502.62 |
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 Customer Care website. The following documentation also contains information about this software. Please consult the Genesys Voice Platform 8.1 Deployment Guide first.
Framework 8.1 Deployment Guide, which provides information about configuring, installing, starting, and stopping Framework components.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.
Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.