Release Note

T-Server for Nortel Communication Server 2000/2100

7.6.x

Genesys Telecommunications Laboratories, Inc. © 2008–2009

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
7.6.013.02 [10/16/09] – Hot Fix           X
7.6.013.01 [09/29/09] – Hot Fix X     X   X
7.6.013.00 [07/24/09] – Hot Fix           X
7.6.012.02 [06/05/09] – Hot Fix   X   X    
7.6.011.01 [04/09/09] – Hot Fix       X    
7.6.011.00 [01/13/09] – Hot Fix X X        
7.6.010.00 [11/17/08] – Hot Fix X          
7.6.009.00 [09/25/08] – General X X X X X X
7.6.008.00 [08/08/08] – Hot Fix X          
7.6.007.02 [07/03/08] – General X X X X X X
7.6.006.02 [03/24/08] – General X X X X X X
7.6.006.01 [01/30/08] – General X X X X X X

Link to 7.5 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.genesyslab.com for more details.

This release note applies to all 7.6 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 functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.


Release Number 7.6.013.02 [10/16/09] – 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 7.6.008.18. 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 corrections and modifications:


There is no longer an increase in T-Server memory utilization when agent state messages are received from the switch for the current state of agents. (ER# 236307328)


Top of Page


Release Number 7.6.013.01 [09/29/09] – 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 7.6.008.18. 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 corrections and modifications:


T-Server now correctly reconnects to Configuration Server or Configuration Proxy and receives updates of configuration data. Previously, in some scenarios, T-Server failed to reconnect to Configuration Layer components, which resulted in a loss of configuration data updates. (ER# 235270160)


T-Server includes the walkaway reason code in a DV-SET-FEATURE NotReady event if, and only if, a ReasonCode is included in the Extensions attribute on a TAgentNotReady request. Previously, T-Server included the walkaway reason code if any extension was included in the request. (ER# 234648621)


Top of Page


Release Number 7.6.013.00 [07/24/09] – 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 7.6.008.12. 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 corrections and modifications:


T-Server now correctly sends the DV_APPL_LOGON switch message when T-Server switches from primary to backup when running in Dual CTI Links mode. Previously, under some circumstances, T-Server did not issue the DV_APPL_LOGON switch message. (ER# 229848397)


Top of Page


Release Number 7.6.012.02 [06/05/09] – 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 7.6.008.14. 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 section describes new features that were introduced in this release:

Corrections and Modifications

This release does not contain any corrections and modifications.

Top of Page


Release Number 7.6.011.01 [04/09/09] – 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 7.6.008.09. 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 corrections and modifications:


T-Server now populates LastForwardingDN in the attribute Extensions with the same value as ForwardingDN, if there is no lastForwarding information in the switch message. (ER# 221518664)


Top of Page


Release Number 7.6.011.00 [01/13/09] – 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 7.6.008.09. 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 section describes new features that were introduced in this release:

Corrections and Modifications

This release does not contain any corrections and modifications.

Top of Page


Release Number 7.6.010.00 [11/17/08] – 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 7.6.008.09. 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 corrections and modifications:


T-Server now correctly routes calls from a Supplementary Routing Point. (ER# 213448575)


T-Server no longer takes Virtual Queues and Virtual Routing Points out of service. (ER# 213486756)


Top of Page


Release Number 7.6.009.00 [09/25/08] – 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 7.6.008.09. 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 now sends DV-DN-QUERY messages to the switch if it is not in backup mode, and for addresses with a DN type of Extension. Previously in this scenario, this message was sent for both Extension and Position DN types, whether in backup mode or not. (ER# 199122884)


Top of Page


Release Number 7.6.008.00 [08/08/08] – 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 7.6.008.09. 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 corrections and modifications:


T-Server now performs default routing for routing requests of type RouteTypeDefault to an unspecified destination (when the selected target DN is empty) without distributing a timeout error. Previously, T-Server distributed EventError (Timeout) for these routing requests.

Note: Default routing for routing requests of other RouteTypes, including RouteTypeUnknown, to an unspecified target DN may still result in T-Server distributing a timeout error. The call is routed properly in these cases.

(ER# 199456228)


T-Server now immediately frees the InvokeID for any switch request upon receiving the return result for that request. This reduces the likelihood of using up all available InvokeIDs. Previously, T-Server delayed the freeing of the InvokeID for certain requests, such as RequestRouteCall, and RequestApplyTreatment. This may have led to situations where InvokeIDs were temporarily unavailable for sending other switch requests. (ER#s 199456228, 199467211, 199456240)


Top of Page


Release Number 7.6.007.02 [07/03/08] – 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 7.6.008.09. 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 now releases all calls for a specific address when a CALL-RELEASED message is received for specific addresses of type AddressTypeDN, or AddressTypePosition. Previously, T-Server released all calls on an address for any address type which resulted in calls being released from a Queue or a Routing Point when a CALL-RELEASED message was received for only one call. (ER# 187705085)


T-Server distributes EventAgentNotReady with AttributeAgentWorkMode 3 (AfterCallWork) when an agent performs a TAgentNotReady request with AttributeAgentWorkMode 3 (AfterCallWork) while on a call. If the call is released, T-Server receives an unsolicited notification from the switch that the agent is still not ready.

T-Server now leaves the agent in AfterCallWork mode after the call is released. Previously, the scenario above caused T-Server to distribute a second EventAgentNotReady, without AttributeAgentWorkMode 3 (AfterCallWork). In doing so, the agent was taken out of the proper work mode. (ER# 182466761)


T-Server no longer sends a DV_CALL_RECORD message for a DN that has been released following a transfer. (ER# 189097651)


T-Server now completes a mute transfer immediately when receiving a CALL-PROGRESS FarEndAnswered message from the switch. (ER# 195007611)


Top of Page


Release Number 7.6.006.02 [03/24/08] – 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 7.6.008.06. 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 has been built with the latest libraries.


Top of Page


Release Number 7.6.006.01 [01/30/08] – 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 7.6.008.04. 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 7.6 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 7.5 or earlier releases and the initial 7.6 release:


T-Server now correctly cleans up calls using the call cleanup feature even when clients issue QueryCall requests. Previously, these requests caused T-Server to restart the cleanup timers, thus delaying or preventing the calls from being cleaned up. (ER# 154742821)


T-Server no longer distributes EventLinkDisconnected when it is shut down through Solution Control Interface. Previously, this would cause unexpected alarms. (ER# 149021710)


Top of Page


Known Issues and Recommendations

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


T-Server, under some circumstances, does not send the DV_APPL_LOGON switch message when T-Server switches from primary to backup while using X.25 links running in hot standby redundancy mode. (ER# 232106184)

Found In: 7.6.013.00 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: 

T-Server may not hold or retrieve the correct leg of a consultation call from a position due to a problem in the CALL-HELD and CALL-UNHELD switch messages. This may affect IP Call Recording scenarios or other similar scenarios. (ER# 122870887)

Found In: 7.5.015.03 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 consult 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 consult was done manually, or
  2. connected state if the consult was done via CTI and the controller did not itself cause the release by manually releasing, or
  3. the ringing state if the consult 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: 

In order to correctly process a client changing an agent's state to ready during switch wrap-up time, both the postCallStatus field of call-released and the agent-setaction message must be provided in the messaging from the switch.

Found In: 7.0.1 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.


The Solaris 2.6 operating system is no longer supported.

Discontinued As Of: 7.6.006.01

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 Technical Support website. The following documentation also contains information about this software.

Top of Page