| Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 8.1.001.03 [02/27/15] – Hot Fix | X | |||||
| 8.1.001.02 [05/01/14] – Hot Fix | X | |||||
| 8.1.001.01 [01/14/14] – General | X | X | X | X | X | |
| 8.1.000.13 [09/20/13] – Hot Fix | X | |||||
| 8.1.000.12 [08/16/13] – Hot Fix | X | |||||
| 8.1.000.11 [06/27/13] – Hot Fix | X | |||||
| 8.1.000.08 [02/15/13] – Hot Fix | X | |||||
| 8.1.000.06 [10/11/12] – Hot Fix | X | |||||
| 8.1.000.05 [08/16/12] – General | X | X | X | 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.genesys.com for more details.
This release note applies to all 8.1 releases of IVR Server.
TServer_IVR and
TServer_IVR_Network applications. You can find information about
changes and corrections to functionality common to all T-Servers in the
release note for
T-Server
Common Part Release 8.1.x. Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.23.
This is a hot fix for this product. This release contains no new features or functionality.
IVR Server now correctly sends CallStateOk in EventReleased after receiving an EndCall message with Endcause = Normal from an IVR. Previously in this scenario, IVR Server sent CallStateRemoteRelease. (IVR-2823)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.23.
This is a hot fix for this product. This release contains no new features or functionality.
When operating on a Linux operating system, IVR Server no longer occasionally terminates while processing the following log message:
StatConn::dispatchHandler: Server disconnected. Will retry in xx seconds
(IVR-2798)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.22.
There are no restrictions for this release. This release contains no new features or functionality.
There are no corrections or modifications in this release of IVR Server.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.19.
This is a hot fix for this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
IVR Server now correctly handles the scenario in which the call to the returned access number failed. This is accomplished by use of a configurable timeout value.
The TServer_IVR configurations must have the following timer added in the Options tab (must be the same for all TServer_IVRs):
Section:Timers
Wait For Remote Connection Timeout
Default Value: 5000 ms
Valid Values: Any positive integer
Changes Take Effect: Immediately
Specifies the amount of time (in milliseconds) that TServer_IVR will wait for an indication that the remote transfer has completed or failed.
If no indication has been received in the time specified, TServer_IVR will process the timer expiration as a remote connection failure.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.19.
This is a hot fix for this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
This is a fix for the new feature that was introduced in 8.1.000.11: when IVR Server is operating in InFront mode, and either an AccessNumGet request is made or a RouteRequest that results in a multi-site transfer, the result of the transfer will now be reported in new call status events.
To use this feature with Orchestration or URS, you must configure additional items. Since TServer IVR operating in the InFront mode receives no TEvents, you must add a Virtual Queue to the Virtual Switch configured for TServerIVR. This Virtual Queue must also be used in the routing strategy loaded on the Route Point on the Virtual Switch for which the XML client RouteRequest is received. In addition, on the target switch, in a multi-site transfer, an intermediate RoutePoint must be configured, on which either a URS strategy or and Orchestration application is loaded. This strategy or application must attach the following key-value pair to the user data:
_IVR_REMOTE_CONNECTION_STATUS, values ( SUCCESS, FAILED )
These are case sensitive and must be added exactly as shown. The remaining portion of the strategy or application may complete the routing at the destination switch, to an agent for example.
(IVR-2706)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.19.
This is a hot fix for this product. This release contains the following new feature or functionality:
When IVR Server is operating in InFront mode, and either an AccessNumGet request is made or a RouteRequest that results in a multi-site transfer, the result of the transfer will now be reported in new call status events.
The asynchronous CallStatusXML event has two new status elements:
RemoteConnectionSuccess and RemoteConnectionFailure.
These new elements apply only to the InFront mode.
Reporting of these new status elements is enabled by using the following
new configuration option:
Section: InFront
enable-enhanced-call-status
Default Value: false
Valid Values: true, false
Changes Take Effect: After restart
Specifies whether the enhanced CallStatus events are issued by TServer IVR.
When set to false (the default), this functionality is disabled.
To use these new elements with AccessNumGet requests, no additional configuration is required.
To use them with URS, you must configure additional items. Since TServer IVR operating in the InFront mode receives no TEvents, you must add a Virtual Queue to the Virtual Switch configured for TServerIVR. This Virtual Queue must also be used in the routing strategy loaded on the Route Point on the Virtual Switch for which the XML client RouteRequest is received. To enable TServer IVR to handle events for this Virtual Queue, configure the following new option on the IVR Server Application object:
Section: InFront
UseVirtualQueue
Default Value: No default value
Valid Values: Any valid VirtualQueue DN configured on the VirtualSwitch
for the TServer IVR
Changes Take Effect: After restart
(IVR‑2701, ER# 324736494)
There are no corrections or modifications in the release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of IVR Server is built with PGF version 8.1.000.19.
This is a hot fix for this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
IVR Server now maintains correct connections to Stat Server, including when Stat Server is operating in HA mode. (ER# 316443459)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of IVR Server is built with PGF version 8.1.000.18.
This is a hot fix for this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
IVR Server no longer receives the OS exception 0xC0000005. The issue was within the TSCP, related to memory pool initialization. This version of IVR Server is built with TSCP version 8.1.001.50, which corrects this issue. (ER# 309222260)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of IVR Server is built with PGF version 8.1.000.17.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of IVR Server.
Support for IPv6. For more information, refer to the Framework 8.1 Deployment Guide.
Limitations:
Support for retrieval of AttributeThirdPartyDN.
Configurable definition of return content for All: The previously existing call information of type All, may now
be configured to also return either UUID and/or ThirdPartyDN.
Support for Unresponsive Process Detection.
Support for hiding user data within the logs.
Support for new operating systems: In release 8.1, several new operating
systems are supported. These systems are listed below. Refer to the
Supported Operating Environment Reference Manual for details.
There are no corrections or modifications in the initial 8.1 release of IVR Server.
This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the document.
The current version of the 8.1 IVR Server System Administrator's Guide incorrectly includes the call-cleanup section in Chapter 10: T-Server Common Configuration Options (page 204). IVR Server does not support the call-cleanup functionality. (IVR-2896)
The current version of the 8.1 IVR Server System Administrator's Guide contains incomplete information in the DN Availability for IVR-In-Front Mode section (page 27). It must include the following:
For IVR-In-Front configurations that are operating in Warm Standby, Hot Standby, or stand-alone mode, you can configure IVR Server to report DN status events (EventDNOutOfService and EventDNBackInService).
This section provides the latest information on known issues and recommendations associated with this product.
The strategy that is employed with URS to perform the dnis-pool access resource allocation on TServer_IVR must use the IRD TargetBlock. TRoute will not perform the correct resource allocation. (ER# 309516852)
| Found In: 8.1.000.06 | Fixed In: |
The 7.5 Configuration Wizard is included with 8.0 IVR Server. It can help you configure the IVR object, IVR Server applications, the IVR Driver application, and other associated objects. When you are using the Wizard, the banner displayed is that of the 7.5 Wizard. Disregard this banner—the Wizard will configure the 8.0 IVR Server successfully. (ER# 253134179)
| Found In: 8.0.000.11 | Fixed In: |
The sustained average call rate supported by IVR Server is no more than 25 cps (calls per second), with short duration peaks limited to 50 cps. Short duration is in the order of seconds, not several minutes. (ER# 233855528)
| Found In: 8.0.000.11 | Fixed In: |
When operating in Hot Standby In-Front mode, the IVR Server's backup instance may have a memory leak. The leak is 0.07 bytes per call, with a call rate of 30 cps, over a 10-hour run duration. (ER# 223413295)
| Found In: 8.0.000.11 | Fixed In: |
IVR Server has a problem handling duplicate requests. (ER# 102228130)
| Found In: 7.5.008.00 | Fixed In: |
If an IVR port is configured as a trunk, the IVR Server generates a
TRelease request. T-Server rejects this request and generates an
error message, which states that an unexpected request for trunks was made, and
sends the message to IVR Server. This behavior does not affect the client-side
call model. (ER# 87485)
| Found In: 7.1.002.00 | Fixed In: |
A call on an IVR port cannot transfer to, or conference with, another IVR port using the same IVR Server. (ER# 83874)
| Found In: 6.5.315.01 | Fixed In: |
XML is the messaging protocol used between IVR Server and client applications
that communicate with IVR Server (such as Genesys IVR Drivers, Genesys Voice
Platform, and driver applications created with the IVR XML SDK). Certain
character codes are not valid in an XML document. Characters with a value less
than hexadecimal number 0x20 are not valid, except the characters
0x09, 0x0A, and 0x0D. These exceptions correspond to
ASCII control characters TAB, LINE FEED, and CARRIAGE RETURN. No other ASCII
control characters are allowed. Therefore, the keys or values in application
user data must not contain any of these disallowed character codes. Any keys or user
data sent or received (including after the transcoding thereof) must be no more
than two bytes per character.
| Found In: 6.5.309.03 | Fixed In: |
Running IVR Server on some operating systems requires the installation of operating system patches. For details, refer to the release note for Programmable Gateway Framework 8.1.x.
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.
The Solaris 8 operating system is no longer supported.
| Discontinued As Of: 8.1.000.05 |
The RHEL version 3 operating system is no longer supported.
| Discontinued As Of: 8.1.000.05 |
The HP Compaq Tru64 Alpha operating system is no longer supported.
| Discontinued As Of: 8.1.000.05 |
The AIX 5.1 and 5.2 operating systems are no longer supported.
| Discontinued As Of: 8.1.000.05 |
Information in this section is included for international customers.
Internationalization is not supported for this release.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.
The IVR Interface Option 8.1 IVR Server System Administrator's Guide describes how to install and configure the IVR Server.
The Genesys Migration Guide provides specific upgrade and migration information.
The Genesys Licensing Guide provides specific licensing information required for IVR Server.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.
Note: For the DVD, the New Documents on this DVD 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.