Release Note

T-Server for Nortel Communication Server 2000/2100

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2011–2018

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.1.002.08 [03/16/18] – General X     X X X
8.1.002.07 [07/24/17] – Hot Fix       X    
8.1.002.06 [03/24/17] – Hot Fix       X    
8.1.002.04 [11/17/16] – Hot Fix X     X X X
8.1.002.03 [12/04/15] – General X     X X X
8.1.001.14 [11/15/14] – Hot Fix       X X  
8.1.001.13 [10/14/14] – General X X X X X X
8.1.001.08 [08/28/13] – Hot Fix X     X   X
8.1.001.04 [06/27/12] – Hot Fix         X X
8.1.001.03 [06/18/12] – Hot Fix         X  
8.1.001.02 [04/23/12] – General X X X X X X
8.1.000.14 [10/24/11] – General X X X X X X
8.1.000.11 [09/09/11] – General X X X X X X
8.1.000.06 [06/27/11] – General X X X X X X

Link to 8.0 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


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.

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.


Release Number 8.1.002.08 [03/16/18] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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:

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page


Release Number 8.1.002.07 [07/24/17] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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


Release Number 8.1.002.06 [03/24/17] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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:

Corrections and Modifications

This release includes no corrections or modifications.


Top of Page


Release Number 8.1.002.04 [11/17/16] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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


Release Number 8.1.002.03 [12/04/15] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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:

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:

(TS-11003)


Top of Page


Release Number 8.1.001.14 [11/15/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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


Release Number 8.1.001.13 [10/14/14] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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:

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


Release Number 8.1.001.08 [08/28/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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


Release Number 8.1.001.04 [06/27/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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:

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


Release Number 8.1.001.03 [06/18/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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:

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page


Release Number 8.1.001.02 [04/23/12] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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.

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


Release Number 8.1.000.14 [10/24/11] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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


Release Number 8.1.000.11 [09/09/11] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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 no longer shuts down if it fails to obtain an ISCC license. (ER# 278678036)


Top of Page


Release Number 8.1.000.06 [06/27/11] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

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.

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.


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

Found In: 8.1.000.06 Fixed In: 8.1.000.11

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)

Found In: 8.0.101.11 Fixed In: 8.1.000.06

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)

Found In: Document version 80fr_dep-ts_ncs2000_09-2009_v8.001.00 Fixed In: 

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)

Found In: 8.0.005.02 Fixed In: 

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)

Found In: 7.6.006.01 Fixed In: 

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)

Found In: 7.6.006.01 Fixed In: 

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)

Found In: 7.5.015.03 Fixed In: 

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)

Found In: 7.5.014.00 Fixed In: 

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.

Found In:  Fixed In: 

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.

Discontinued As Of: 8.1.000.06

The Solaris 8 operating system is no longer supported.

Discontinued As Of: 8.1.000.06

The Tru64 UNIX operating system is no longer supported.

Discontinued As Of: 8.1.000.06

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

Discontinued As Of: 8.1.000.06

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.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

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