Release Note

Contents

Introduction

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 T-Server for Nortel Communication Server 2000/2100.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The operating systems available for use with each component release are listed in the table at a high level only. For more detailed information about the supported operating environments, including requirements, supported versions, and any conditions or limitations, see the T-Server for Nortel Communication Server 2000/2100 page in the Genesys Supported Operating Environment Reference Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• 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.
• Your T-Server’s name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

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 More Release Information/Legal Notices for T-Servers. Please contact your Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for the Windows Server 2019 operating system and Windows 2019 Hyper-V virtualization (TCP/IP only). See the Supported Operating Environment: T-Server Nortel Communication Server 2000/2100 page for more detailed information and a list of all supported operating systems.

• Support for the Red Hat Enterprise Linux 7 operating system (TCP/IP only). See the Supported Operating Environment: T-Server Nortel Communication Server 2000/2100 page for more detailed information and a list of all supported operating systems.

• Support for the Windows Server 2016 operating system (TCP/IP only). See the Supported Operating Environment: T-Server Nortel Communication Server 2000/2100 page for more detailed information and a list of all supported operating systems.

• T-Server can now use a new option, strict-record, to delay recording until calls are established. Previously, T-Server always recorded upon ringing.

  Warning: Use this option only when requested by Genesys Customer Care.

  strict-record
  Values: true, false
  Default: false
  Effective: immediately
  

  When true, recording begins only after a call is established. When false, recording begins on ringing.

  (TS-11326)

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer rejects a client with an ApplicationDBID over 16383. Previously, T-Server set the ApplicationDBID as the default value of the option server-id and there was no limit for ApplicationDBID. If the ApplicationDBID was over 16383, T-Server rejected the client. (TS-11455)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains the following features or functionality:

• Support for the Red Hat Enterprise Linux 6 operating system, 64-bit and 32-bit versions (TCP/IP only). See the Supported Operating Environment: T-Server Nortel Communication Server 2000/2100 page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.010.87. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now distributes EventReleased when it receives NONCONTROLLER-RELEASED with a non-matching releasedDn, when the value of noncontroller-released-digits is zero. (TS-11173)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.010.68. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for Windows Server 2012, 64-bit native for TCP/IP links.

• T-Server now enables clients to request T-Server to stop recording new calls while the link is disconnected. (TS-11007)

• A new restricted configuration option, use-zero-noncontroller-released-digits, enables the use of the DV-NONCONTROLLER-RELEASED switch message to release a call with one branch even if the message contains no released digits.

  use-zero-noncontroller-released-digits
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  Normally, T-Server ignores DV-NONCONTROLLER-RELEASED if it contains no released digits. However, if this option is set to true and noncontroller-released-digits is zero, T-Server now uses the message to release one branch of a consultation call. The call will be released if it contains exactly two branches and the branch being released contains exactly one internal and one external party. Otherwise it is impossible for T-Server to determine which branch and party has been dropped.

  (TS-10921)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer quits unexpectedly when a main call with two or more associated consultation calls is retrieved and then immediately released. (TS-11017)

In backup mode, T-Server:

• no longer sends requests to the switch to start or stop recording.
• now synchronizes recording parmarmeters from primary to backup, enabling the new primary T-Server to correctly take over recording after a failover.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.76. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains no new features or functionality.

This hot fix supports only TCP connections to the link.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer distributes an extra EventPartyChanged when it receives DV-CALL-TRANSFERRED without an originating party. (TS-10819)

T-Server now includes Trunk information in EventQueued and EventDiverted extensions when a call is offered directly to an agent without first going through a queue. (TS-10820)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.76. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release contains the following new feature or functionality:

• This release is built with TSCP 8.1.001.76, which adds support for the Dialogic Eiconcard adapter using the x.25 protocol on the Windows 2008 platform, in 32-bit native, 64-bit native, and 64-bit compatibility modes. TSCP adds support for the newer ex25.dll while retaining support on existing installations for the obsolete x25nt.dll, which does not work with Windows 2008. A new configuration option, x25-dlls, specifies the dll list that ensures compatibility with your environment.

  x25-dlls
  Default: ex25.dll, x25nt.dll
  Valid values: an ordered, comma-separated list of x.25 DLL file names
  Changes take effect: at startup
  
  At startup, T-Server tries to load the dlls in the order listed and stops when it has either successfully loaded a dll or reached the end of the list without being able to load a dll. By default, T-Server loads x25nt.dll for Windows 2003 or ex25.dll for Windows 2008. If T-Server fails to load any of the dlls listed in this option's value, the link is not initialized.

  (TS-10751)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly allocates and frees InvokeIDs for internal requests such as queries. Previously, InvokeIDs could become stuck if these internal requests resulted in errors. (TS-10648)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.68. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server now correctly acquires Control Directory Numbers (CDN) Routing Points during startup. Previously, T-Server could neglect the acquisition of some of these DNs leaving them unusable, and the backup T-Server might fail to send an EventLinkConnected message. (TS-10483)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.42. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains the following new features or functionality:

• Support for the Windows operating system was added on July 3rd, 2013.

• T-Server now supports the restricted configuration option call-state-old-overflowed, which specifies the AttributeCallState attribute as the CallStateRedirected attribute in an EventReleased message for an agent that is released by the switch due to no answer (switch release reason: Overflowed.) This option is set in the TServer section of the T-Server Application object.

  call-state-old-overflowed
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If this option is set to true, T-Server specifies the AttributeCallState attribute as a CallStateOverflowed attribute in an EventReleased message for an agent. If this option is set to false, T-Server specifies the AttributeCallState attribute as a CallStateRedirected attribute in the EventReleased message for an agent.

  Warning! Use this option only when requested by Genesys Technical Support.

  (ER# 302930502)

Corrections and Modifications

This release includes the following correction and modification:

T-Server now correctly acquires Control Directory Numbers (CDN) Routing Points when the flow control mechanism is activated. Previously, T-Server would neglect the acquisition of these DNs and would avoid distributing EventLinkConnected, if the flow control was activated during registration. (ER# 301882561)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.42. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains the following new features or functionality:

• T-Server now supports the restricted configuration option use-notready-request-workmode, which causes T-Server to use the AttributeAgentWorkMode attribute from the TAgentNotReady request in the EventAgentNotReady event, even if the work mode is different from the switch. This option is set in the TServer section of the T-Server Application object.

  use-notready-request-workmode
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If this option is set to true, T-Server uses AttributeAgentWorkMode from the TAgentNotReady request to set the work mode of the agent. If this option is set to false, T-Server uses AttributeAgentWorkMode in the EventAgentNotReady event to set the work mode of the agent.

  Warning! Use this option only when requested by Genesys Technical Support.

  (ER# 271046310)

• T-Server now supports the restricted configuration option ignore-notready-to-notready-switch, which causes T-Server to ignore the DV-AGENT-NOT-READY switch messages, if the agent state is already one of the NotReady states. This option is set in the TServer section of the T-Server Application object.

  ignore-notready-to-notready-switch
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If this option is set to true, T-Server ignores the DV-AGENT-NOT-READY switch messages, if the agent state is already in one of the NotReady states. If this option is set to false, T-Server processes the DV-AGENT-NOT-Ready messages sent from the switch even if the agent state is already in one of the NotReady states.

  Warning! Use this option only when requested by Genesys Technical Support.

(ER# 271046310)

• T-Server now supports the restricted configuration option notready-before-logged-out, which causes T-Server to distribute the EventAgentNotReady event before the EventAgentLoggedOut event, if the agent is not already in the NotReady state. This option is set in the TServer section of the T-Server Application object.

  notready-before-logged-out
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If this option is set to true, T-Server distributes the EventAgentNotReady event before distributing the EventAgentLoggedOut event, if the agent is not already in one of the NotReady states. If this option is set to false, T-Server only distributes the EventAgentLoggedOut event.

  Warning! Use this option only when requested by Genesys Technical Support.

(ER# 301641481)

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.40. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in this release of T-Server for Nortel Communication Server 2000/2100.

• T-Server now supports the restricted configuration option change-dnis in order to turn on or off the updating of the DNIS attribute during the life of the call. This option is set in the TServer section of the T-Server Application object.

  change-dnis
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If this option is set to true, the DNIS attribute is updated every time a call arrives at a Queue or a Routing Point. If this option is set to false, the DNIS attribute is not updated when a call arrives at a Queue or a Routing Point.

  Warning! Use this option only when requested by Genesys Technical Support.

  (ER# 297905251)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly reassociates a CDN Routing Point with the switch after a link is successfully reconnected. Previously, if the link disconnected before the successful registration of the CDN, T-Server did not reassociate that DN. (ER# 296852828)

T-Server now correctly reassociates DNs when a link is re-established with the switch after losing and then recovering the link connection because of receiving a LINK_DOWN_PACKET message followed by a LINK_UP_PACKET message. Previously, T-Server did not reassociate the DNs. (ER# 283893971)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.000.25. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer sends a return result in response to a CALL-RECEIVED switch message if CALL-QUEUED is subsequently received on the same Routing Point. (ER# 279132793)

T-Server now reassociates addresses when a backup becomes primary if the re-assoc flag was set in the appl_logon return result. In addition, T-Server ensures that all DNs are put in service once they are registered. Previously, this reassociation would not occur if the appl_logon result was received when T-Server was still in backup mode. (ER# 282837616)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.000.24. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

This release of T-Server corrects two problems that are related to a link connectivity cycle:

• T-Server now prevents positions and extensions from being placed in an OutOfService state after an EventLinkDisconnected/EventLinkConnected cycle.

• A change in Call ID occurring due to link disconnection followed by link reconnection no longer results in a stuck call. Once the link is reconnected, T-Server clears the call from memory and distributes EventReleased in response to a TReleaseCall. Previously, the call was released from the switch but was not cleared from memory, nor was an EventReleased issued. (ER# 277953559)

T-Server no longer shuts down if it fails to obtain an ISCC license. (ER# 278678036)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.000.19. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of T-Server for Nortel Communication Server 2000/2100.

• T-Server no longer connects to applications that have disabled status in the configuration environment.
• The default value of the background-processing configuration option has been changed to true.
• T-Server now supports the Unresponsive Process Detection feature. The following configuration options enable this feature:

  • heartbeat-period
  • hangup-restart

  See option descriptions in your T-Server Deployment Guide. For more information, refer to the Framework 8.0 Management Layer User's Guide.
• T-Server now supports IPv6. For more information, refer to the Framework 8.1 Deployment Guide.
• T-Server now supports vSphere 4 Hypervisor.
• T-Server now supports Acresso FLEXNet Publisher 11.9 license manager.
• T-Server is now supported on the following platforms:

  • AIX 7.1 64-bit
  • HP-UX Itanium (version 11i v3)
  • Red Hat Enterprise Linux 5 64-bit

• T-Server now supports EventDNBackInService and EventDNOutOfService events for Supplementary Queue DNs and Routing Points. Two new configuration options have been introduced to turn these events on and off:

  • primary-qrp
  • relate-primary-supp-qrp

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 8.0 or earlier releases and the initial 8.1 release:

If a switchover from primary to backup T-Server occurs, T-Server no longer creates an extra call after receiving the CALL-PROGRESS message if the values for the set-call-type-with-dialing and new-call-for-unknown-dest configuration options are both set to true. (ER# 268185141)

Top of Page

Known Issues and Recommendations

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

To ensure backward compatibility, T-Server provides two options that define how many licenses T-Server can check out:

• num-of-licenses defines the max number of licenses that T-Server can check out.
• num-sdn-licenses defines the actual number of licenses that T-Server does check out, up to the maximum value specified by option num-of-licenses.

When the values of the two options are different, then T-Server applies the lower one, so Genesys recommends that you leave the option num-sdn-licenses at the default value max and set the option num-of-licenses to the actual number of licenses that you want T-Server to check out. Alternatively, you can set both options to the same value.

• num-of-licenses
  Default Value: max (equivalent to 9999 licenses)
  Valid Values: max (equivalent to 9999) or any integer
  Changes Take Effect: Immediately
  Specifies the maximum number of DN licenses T-Server can check out. The values max or 0 (zero) is equal to exactly 9999 licenses. To check out any other number of licenses, specify the value as an integer, up to the number of seats supportable in your environment. The sum of all num-of-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.

• num-sdn-licenses
  Default Value: max (all DN licenses are seat-related)
  Valid Values: String max (equal to the value of num-of-licenses) or any integer.
  Changes Take Effect: Immediately
  Specifies how many seat-related licenses T-Server checks out. A value of 0 (zero) means that T-Server does not grant control of seat-related DNs to any client, and it does not look for seat-related DN licenses at all. A value of "max" means that T-Server checks out the number of licenses defined in option num-of-licenses. The sum of all num-sdn-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.

T-Server shuts down if it fails to obtain an ISCC license. (ER# 278678036)

If a switchover from primary to backup T-Server occurs, T-Server might create an extra call after receiving the CALL-PROGRESS message if the values for the set-call-type-with-dialing and new-call-for-unknown-dest configuration options are both set to true.

Workaround: To prevent an extra call, set the value for the set-call-type-with-dialing configuration option to false.

(ER# 268185141)

The Framework 8.x T-Server for Nortel Communication Server 2000/2100 Deployment Guide omits the following information:

agent-state-return-result
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

If this option is set to true, when the agent is on a call, T-Server changes the agent state based on the return result of the DV_SET_FEATURE message. If the agent is not on a call, then the return result is not used. If this configuration option is set to false, agent requests may timeout if the call lasts longer than the duration specified by the request-timeout configuration option.

Note: Use this option only when requested by Genesys Technical Support.

(ER# 240452039)

Setting the option agent-no-answer-overflow to any value other than none may result in EventHardwareError. T-Server only supports a value of none for this option. (ER# 225440797)

When running a high-availability pair of pre-7.6 T-Servers in hot-standby mode, upgrading only the backup T-Server to a 7.6 version with a rolling upgrade prevents the backup T-Server from starting and it remains in a Service Unavailable state. A pre-7.6 T-Server and a 7.6 T-Server cannot run as a hot-standby pair. (ER# 200067043)

If an agent goes NotReady while on call using a CTI (RequestAgentNotReady) request, and then manually changes the agent state to Ready, T-Server will remain in NotReady state after the call ends. Genesys recommends not changing agent state with both CTI and manually on the telephone set. (ER# 155483699)

Due to a switch problem, T-Server may receive an invalidCallState error in response to a DV-CALL-RECORD message on a position when initiating a call transfer or a conference call.

The following is an example of a scenario that can cause this issue:

1. DN1 calls an ACD Queue that diverts the call to Position1.
2. DN1 is placed on hold.
3. Position1 initiates a consultation call to DN2 and requests IP Call Recording.
4. T-Server sends a DV-CALL-RECORD message for Position1. The switch responds with an invalidCallState error.
5. DN2 answers the call.
6. T-Server successfully resends a DV-CALL-RECORD message.

(ER# 122871014)

For Windows only: T-Server may be unable to connect to an X.25 link. As a workaround, the following parameter should be added to the command line when starting T-Server:

-conn-provider select

(ER# 107803398)

In an AlternateCall scenario where one branch of a consultation call is released, there is no messaging from the switch to indicate the state of the controlling party (held, connected, or ringing). The switch vendor has provided rules for determining the state, specifically, that after the release, the controlling party is in the:

1. held state if the consultation call was done manually, or
2. connected state if the consultation call was done via CTI and the controller did not itself cause the release by manually releasing, or
3. the ringing state if the consultation call was done via CTI and the controller itself did cause the release by manually releasing.

To determine the correct state after the release, T-Server follows rules (1) and (2) but not (3). This is a limitation caused by the fact that it is difficult or impossible to determine if it was the controller that manually released the call branch. Therefore, in cases where the controller manually releases one branch of a CTI consulted call, T-Server will incorrectly place the controlling party in the connected state, instead of the ringing state. That is, it will distribute EventRetrieved (if necessary), but not EventRinging.

Top of Page

Discontinued Support

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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

The Red Hat Enterprise Linux 3.0 operating system is no longer supported.

The Solaris 8 operating system is no longer supported.

The Tru64 UNIX operating system is no longer supported.

The AIX 5.1 and 5.2 operating systems are no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

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

• The Framework 8.1 T-Server for Nortel Communication Server 2000/2100 Deployment Guide contains detailed reference information for the Genesys Framework 8.1 T-Server for Nortel Communication Server 2000/2100 including configuration options and specific functionality.

• The Framework 8.1 Deployment Guide helps you configure, install, start, and stop Framework components.

• The Platform SDK 8.x .NET (or Java) API Reference and the Genesys Events and Models Reference Manual contain the T-Library API, information on TEvents, and an extensive collection of call models.

• The Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Customer Care for additional information.

• The Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Customer Care for additional information.

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.

Top of Page