Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
8.0.001.21 [02/26/13] – General | X | X | X | X | X | X |
8.0.000.20 [04/10/12] – Hot Fix | X | |||||
8.0.000.19 [03/23/12] – Hot Fix | X | X | ||||
8.0.000.18 [02/17/12] – Hot Fix | X | |||||
8.0.000.18 [02/17/12] – Hot Fix | X | |||||
8.0.000.17 [02/09/12] – Hot Fix | X | X | X | X | X | X |
8.0.000.15 [02/09/11] – Hot Fix | X | X | ||||
8.0.000.14 [10/26/10] – General | X | X | X | X | X | X |
8.0.000.13 [04/01/10] – Hot Fix | X | |||||
8.0.000.12 [01/25/10] – Hot Fix | X | X | X | X | X | X |
8.0.000.11 [12/16/09] – General | X | 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.0 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.0.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 technical support representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.13.
This release is available on all supported platforms.
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.13.
This release includes the following corrections and modifications:
When IVR Server is operating in the In-Front mode, and a call is not in the routing state, a Call Timeout timer transition in the Release Management state machine now issues an EventReleased
message for the call. (ER# 294634002)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.13.
This release includes the following corrections and modifications:
IVR Server is built with PGF that includes the corrected TSCP issue:
When the resource-allocation-mode
option is set to circular
, the TSCP now correctly allocates resources in a circular manner within each epn
partition (known to the TSCP by the partition name provided in the epn
option in the Annex
tab of any access resource DN). Previously, the TSCP allocated resources in a circular manner in a combined list of resources belonging to all partitions, which could result in a biased selection within any particular partition. (ER# 296731309)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.13.
This release includes the following corrections and modifications:
When operating in the In-Front mode, IVR Server no longer sends an EventAbandoned
message after receiving an XML EndCall "Abandoned"
message from the XML client. IVR Server now sends EventReleased
in this scenario. (ER# 294712717)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.12.
This release includes the following corrections and modifications:
IVR Server now only sends CallStatus (Released)
and EndCall
messages when it receives the EventReleased
message for the primary call Connection ID. Previously, IVR Server incorrectly sent CallStatus (Released)
and EndCall
messages when the consultation call was released in the Dialing call state. (ER# 277185760, 293796003)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.12.
This release includes the following corrections and modifications:
When operating in a non-NTS mode, during a routing transaction, IVR Server no longer loops within itself if a client sends a ConnectedFailed
message after a default routing has occurred. (ER# 267073131)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of IVR Server.
This release of IVR Server is built with PGF version 8.0.000.12.
A new configuration option, source-encoding
, provides the capability to pass client UTF-8 characters to T-Server in their UTF-8 format. To enable this feature, set this option to UTF-8
in the XmlSap
section of the TServer_IVR
application.
UTF-8
UTF-8
, client UTF-8 characters will be passed to T-Server in their UTF-8 format.(ER# 255115291)
This release includes the following corrections and modifications:
IVR Server now properly processes the route-in-place feature when a treatment is active and a TRouteCall
request is received from Universal Routing Server (URS). (ER# 247586751)
IVR Server now properly maintains connection to a redundant pair of Configuration Servers (or Configuration Server Proxies). (ER# 248578741)
IVR Server no longer becomes unstable if it is configured incorrectly and must log invalid UTF-8 characters. (ER# 251939721)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
This release of IVR Server is built with PGF version 8.0.000.11.
This release includes the following corrections and modifications:
IVR Server, operating in Network mode, now correctly handles the EndCall
processing after a RouteResponse
has been issued and an EndCall
has been received. The EventAbandoned
event is no longer issued as a result of the EndCall
. (ER# 248435621)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release of IVR Server is built with PGF version 8.0.000.11.
IVR Server now supports Windows Server 2008 R2.
This release includes the following corrections and modifications:
This release of IVR Server corrects the internal issue which prevented the autologin of agents. (ER# 243193217)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of IVR Server.
This release of IVR Server is built with PGF version 8.0.000.11.
Support for IVR Server in Hot Standby mode for high availability: In release 8.0, IVR Server supports Hot Standby mode for high availability for in-front, behind, and network modes. Release 8.0 of IVR Driver supports IVR Server Hot Standby mode for in-front and behind modes.
Client-side port definition: Release 8.0 of IVR Server and IVR Driver
support client-side port definition, which enables a driver application to
define the connection port that it will use to connect to the Configuration
Server. If the driver application is located behind a firewall, that firewall
may be configured with the known port that the driver application will be
using. This is configured in the driver's .in
i file. After the driver
application connects to the Configuration Server, you may also configure
the client-side port(s) that the driver application will subsequently use for
its connection(s) to your IVR Server(s). These are configured in the
driver's application in Configuration Manager. Please refer to the
Genesys Security Deployment Guide documentation for more details,
including supported platforms.
Peer support for agent login/logout under IVR Server control in
load-balanced configurations: In release 8.0, A feature has been added
that will allow IVR Server to correctly log-out agents even when multiple
IVR Servers are being used in the LoadBalance
mode. Previously, there was
a problem in that stopping any one of the IVR Servers would cause that
IVR Server to log-out agents even though remaining IVR Servers would be
servicing the IVR clients. This made the maintenance of an IVR Server
difficult in those cases where Load Balancing and IVR Server controlled
agent login/logout was desired.
This problem can now be avoided in this scenario. The group of IVR Servers will now send messages to each other, so that any IVR Server that is commanded to stop can now conditionally logout agents if and only if there are no other running IVR Servers left in the group.
Support for new operating systems: In release 8.0, several new operating
systems are supported. These systems are listed below. Please refer to the
Supported Operating Environment Reference Manual for full details.
Addition of XML UDataGetAll: In release 8.0, the user data interface has
been extended to include data retrieval associated with all keys in a single
request. Previously, only data retrieval from a single key was supported.
The new XML element is UDataGetAll
. Please refer to the IVR SDK 8.0
XML Developer's Guide for further details.
This release includes the following corrections and modifications that were made between release 7.5 or earlier releases and the initial 8.0 release:
The GLI server port now reopens after a switchover. (ER# 233678207, 235977033, 180605121)
IVR Server, previously used for ISCC type of transfers, now works properly when it is requested to stop through the SCI interface. Previously, IVR Server stopped functioning, and it would then loop within itself at termination instead of cleanly exiting. This issue only applied to an IVR Server that was installed on an AIX operating system. (ER# 136584283)
IVR Server, previously used for ISCC type of transfers, now works properly when it is requested to stop through the SCI interface. Previously, IVR Server stopped functioning, and it would core at termination instead of cleanly exiting. This issue only applied to an IVR Server that was installed on a Solaris 64-bit operating system. (ER# 145049119)
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.0 IVR Server System Administrator's Guide incorrectly includes the call-cleanup section in Chapter 10: T-Server Common Configuration Options (page 258). IVR Server does not support the call-cleanup functionality. (IVR-2896)
The current version of the 8.0 IVR Server System Administrator's Guide contains incomplete information in the DN Availability for IVR-In-Front Mode section (page 30). 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 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 7.5.x.
Found In: 6.5.200.11 | Fixed In: |
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 Windows 2000 operating system is no longer supported.
Discontinued As Of: 8.0.000.11 |
The HP-UX 11.00 operating system is no longer supported.
Discontinued As Of: 8.0.000.11 |
The Solaris 7 operating system is no longer supported.
Discontinued As Of: 8.0.000.11 |
The AIX 4.x operating system is no longer supported.
Discontinued As Of: 8.0.000.11 |
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 Technical Support website. The following documentation also contains information about this software. Please consult the System Administrator's Guide first.
The IVR Interface Option 8.0 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 Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD.
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 Technical Support 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.