Release Note

• Introduction
• Release Number
  • 7.0.000.08 [10/29/04] - General
  • 7.0.000.05 [05/28/04] - General
• Link to 6.5 IVR Driver Release Note (Cumulative)
• Known Issues and Recommendations
• Internationalization
• Additional Information

Introduction

This release note applies to all 7.0 releases of IVR Driver for WVR for Windows. Information will be added to this release note as subsequent versions of the component are released. To help you identify the specific differences in releases, the release note includes new features and corrections and modifications for each release. Links in the Contents section enable you to access information regarding a specific release.

The Known Issues and Recommendations section is a cumulative list with the most recent items at the top of the list. This list includes information on when individual items were found and, if applicable, corrected.

The IVR Library is common code used by all Genesys IVR Drivers. The Genesys IVR SDK for C uses a subset of the functionality in the IVR Library. You can find information about changes and corrections to functionality common to all products that use the IVR Library in the release note for IVR Library 7.0.x.

New In This Release

This release of the IVR Driver is built with IVR Library release number 7.0.000.47.

This is a general release for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

Several IVR Library problems that affected this IVR Driver have been fixed. See the IVR Library Release Note for details.

Migration Note: While the 6.5 IVR Driver returns the string Not Available when an application requests GetCallInfo and no information is available to send, the 7.0 IVR Driver returns Null in this circumstance. (ER# 79113)

Before you can start the IVR Driver, you must perform these steps:

1. Install the Genesys Local Control Agent (LCA) on the same system as the IVR Driver, and reboot the system. LCA is then enabled and starts automatically during system startup.
2. Create a Host object for your IVR in Configuration Manager.
3. On the Server Info tab of the IVR Driver application, enter in the Name field the same IVR host name that you specified when you created the IVR's Host object.
4. Configure a log file name that is valid for the operating system on which the IVR Driver runs.

Note: If you omit any of these steps, the IVR Driver does not run or log properly. (ER# 85518)

In the WVR for Windows interface's User Server—Add/Change dialog box, you must enter the value DTNTIsvr in the Server name field exactly as shown here. The Server name field is case sensitive. (ER# 85519)

In the location variable in the ctp.trx file, you must enter the exact application name assigned to your T-Server in Configuration Manager. This instruction has been added to the ctp.trx file. (ER# 85520)

An IVR Library problem has been fixed that sometimes prevented the IVR Driver from connecting to the IVR Server. See ER 87264 under release 7.0.000.41 in the IVR Library release note. (ER# 90724)

For these IVR Driver APIs, the output variable in which a router response is returned has been increased in size: (ER# 91240)

• TSRVNextService variable for the RouteRequest API
• TSRVRouteReqstID variable for the GetRequest API
• TSRVDstDN variable for the CallInit API

Top of Page

New In This Release

This release of the IVR Driver is built with IVR Library release number 7.0.000.32.

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.0 release of this IVR Driver.

• The new IVR Interface Option Wizard allows you to define and configure IVR Server and IVR Driver applications, IVRs, ports and DNs. You can use this wizard to upgrade IVR Interface Option 6.5 objects to release 7 and to configure an entire range of IVR ports and DNs at once rather than individually. For more information about the wizard, see the IVR Interface Option Wizard Advisory and the IVR Interface Option 7 IVR Server System Administrator's Guide.

  Note: IVR Driver, IVR and port configuration information previously provided in the System Administrator's Guide for your IVR Driver is now provided in the IVR Interface Option 7 IVR Server System Administrator's Guide.

• A new IVRDriver application is required for use with IVR Interface Option 7. The IVRDriver application provides access to centralized logging and other IVR Interface Option 7 functions. For information about importing the IVR_Driver application template and configuring the IVRDriver application, see the Pre-Installation Setup chapter of the IVR Interface Option 7 IVR Server System Administrator's Guide.

• New configuration steps are required for the IVR Driver configuration file. For information on how to configure the configuration file, see the IVR Interface Option 7 IVR Driver for WVR for Windows System Administrator's Guide.

• Some new configuration options are required for IVR Driver 7, and some previous options have been changed or made obsolete. For example, the IVR Driver configuration options previously configured in the DataTransport section on the Annex tab of the IVR object's Properties dialog are now configured on the Options tab of the new IVRDriver application's Properties dialog. For details, see the IVR Interface Option 7 IVR Server System Administrator's Guide and the IVR Interface Option chapter of the Genesys 7 Migration Guide.

• New statistics for retrieving the position in queue and the estimated wait time for calls are available for IVR Driver 7 through attached user data from Universal Routing Server (URS). See the Universal Routing 7 Reference Manual for more information.

• The RouteDone function is not supported in IVR Interface Option 7. Instead, the IVR Server sends a route used message to the Universal Routing Server (URS). For more information, see the IVR Interface Option 7 IVR Driver for WVR for Windows System Administrator's Guide.

• The StatGet function is not supported in IVR Interface Option 6.5 or 7. You should use StatPeek instead. See the IVR Interface Option 7 IVR Driver for WVR for Windows System Administrator's Guide.

• IVR Library and IVR Server log events are now available through the Genesys Message Server when you configure centralized logging. To enable this feature in your IVR Driver, you must use the new configuration parameters in the IVR Driver configuration file. The new log events are available in the latest Combined Log Events Help, which you can download from the Genesys Technical Support website. For these log events to be available in Solution Control Interface (SCI), you must download the Combined Log Events Help files into the SCI installation folder.

• IVR Driver 7 requires the use of IVR Server 7 and Genesys Framework 7. Genesys 7 licensing is also required.

• To use the new features provided in IVR Interface Option 7, you must use Genesys Management Layer 7 and Configuration Server release 7.0.100.05 or higher.

• Important: The NotifyCallStart function must be used at the start of each call instance, typically after the Answer function in the script. The next calls must be GetCallinfo(EventName) and GetReply, and these calls must return a valid Genesys event (EventEstablished, EventAttachedDataChanged, or EventPartyChanged) before any other function calls (besides NotifyCallEnd) can be used. The NotifyCallEnd function must be called as the last function in the script. There should be only one NotifyCallStart and one NotifyCallEnd function per call. For more information on how to use NotifyCallStart, see the System Administrator's Guide for your IVR Driver. (ER# 85792)

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.

Issuing a CallConsultTransfer immediately following a CallConsultInit without any delays may cause incorrect results because the IVR Library currently uses the Held event to determine whether to allow the CallConsultTransfer to flow to the IVR Server and receiving the Held event is not sufficient to insure that the CallConsultTransfer will succeed. (ER# 65802)

In release 6.1, the maximum key length for key-value pairs is 415 bytes. (ER# 43227) In release 7, the combined key-value pairs (including delimiters) on a given call instance can total no more than 410 bytes. The length of any individual key or value string is limited only by this total. The 410-byte constraint is from the IVR itself, and therefore cannot be changed by the IVR Driver.

Top of Page

Internationalization

Information in this section is included for international customers.

Internationalization is not supported for this release of IVR Driver.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software.

• IVR Interface Option 7 IVR Driver for WVR for Windows System Administrator's Guide describes how to install, configure, and use the IVR Driver. It also describes the Genesys function calls provided for this IVR Driver.

• For information about installing and configuring IVR Server, see the IVR Interface Option 7 IVR Server System Administrator’s Guide.

• If you are upgrading or migrating to IVR Interface Option 7, refer to the Genesys 7 Migration Guide for specific upgrade and migration information.

Top of Page