Release Note

T-Server for NEC NEAX/APEX

8.1.x

Genesys Cloud Services, Inc. © 2011–2021

Contents

Introduction

Release Number AIX Linux Solaris Windows
8.1.500.03 [11/09/21] – Update   X   X
8.1.500.02 [06/18/21] – Update   X   X
8.1.011.06 [06/03/20] – Update X X X X
8.1.010.05 [05/18/18] – Update X X X X
8.1.010.03 [03/26/18] – Hot Fix   X   X
8.1.010.02 [01/09/18] – General X X X X
8.1.001.14 [03/29/16] – Hot Fix       X
8.1.001.13 [01/21/16] – Hot Fix   X   X
8.1.001.12 [08/28/15] – Hot Fix       X
8.1.001.11 [08/04/15] – Hot Fix   X X  
8.1.001.08 [03/31/15] – General X X X X
8.1.001.07 [03/11/15] – Hot Fix       X
8.1.001.06 [01/15/15] – Hot Fix     X X
8.1.001.05 [07/10/14] – General X X X X
8.1.001.04 [05/12/14] – Hot Fix     X  
8.1.000.35 [12/14/12] – Hot Fix     X X
8.1.000.34 [11/16/12] – Hot Fix     X X
8.1.000.29 [08/23/12] – Hot Fix       X
8.1.000.27 [06/14/12] – Hot Fix     X  
8.1.000.26 [03/14/12] – General X X X X
8.1.000.24 [01/18/12] – Hot Fix     X  
8.1.000.19 [10/20/11] – General X X X X
8.1.000.18 [10/14/11] – Hot Fix       X
8.1.000.17 [10/07/11] – General X X X X
8.1.000.15 [08/04/11] – General X X X X
8.1.000.12 [07/22/11] – General X X X X
8.1.000.09 [06/27/11] – General X X X X

Link to 8.0 Product Release Note (Cumulative)
Documentation Corrections
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 NEC NEAX/APEX.

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 T-Servers. Please contact your Customer Care representative if you have any questions.


Release Number 8.1.500.03 [11/09/21] – Update

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 T-Server Common Part (TSCP) release number 8.5.000.25. TSCP is the shared software that all T-Servers and SIP Server 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 an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server no longer ignores the release message from the switch during a race condition involving RequestReconnectCall followed immediately by RequestRedirectCall. (TS-12086)


Top of Page


Release Number 8.1.500.02 [06/18/21] – Update

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 T-Server Common Part (TSCP) release number 8.5.000.25. TSCP is the shared software that all T-Servers and SIP Server 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 an update for this product. This release contains the following new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Hot Standby high-availability functionality now works correctly. Previously, starting with version 8.1.011.06, the Hot Standby HA was incorrectly disabled by an internal setting. (TS-12053)


Top of Page


Release Number 8.1.011.06 [06/03/20] – Update

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 T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server now distributes EventOnHook on receiving SMFN 3 for an off-hook device, even if the corresponding party is no longer on the call. One scenario where this could happen is when a call is released while one of its legs is on hold and a second call arrives on one of the DNs involved. You can disable this behavior by setting the new option onhook-without-party to false. (TS-11934)


Top of Page


Release Number 8.1.010.05 [05/18/18] – Update

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 T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly generates an EventOnHook message after previously generating an EventOffHook message, when a DN returns to the onhook state. This issue applied to a scenario where an internal DN dials another internal DN which also has the call waiting feature enabled. (TS-11541)


Top of Page


Release Number 8.1.010.03 [03/26/18] – 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 T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now supports the call model Rejected Call (Route Point). See Rejected Call in the Events and Models Reference. Previously, T-Server did not properly specify CallStateDropped in the EventDiverted event for this call model. (TS-11562)


Top of Page


Release Number 8.1.010.02 [01/09/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.

Note: This version was first released as a Hot Fix on December 13, 2017.

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.001.14 [03/29/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 T-Server Common Part (TSCP) release number 8.1.001.78. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server no longer becomes unstable when processing OAI acknowledge messages for SCF FID=8 (OAI_SCF_CONFERENCE_CALL) requests, after the corresponding TSingleStepConference request is destroyed in memory. (TS-11104)


Top of Page


Release Number 8.1.001.13 [01/21/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 T-Server Common Part (TSCP) release number 8.1.001.78. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly processes TReconnectCall requests by correctly specifying the third-party parameter of the OAI SCF10 request, when such a request follows call redirection via OAI SCF10 where the third-party parameter is required. Previously, the switch rejected erroneous SCF 10 call reconnection requests. (TS-11082)


The distribution of the ANI attribute is now enabled for internal calls to a Split Routing Point device and is controlled by the common T-Server option ani-distribution. By default, this option allows the ANI attribute for only inbound calls. Setting this option to all-calls enables ANI to be distributed for internal calls to a Split RP. Previously, T-Server didn't distribute the ANI attribute for such calls. (TS-11011)


Top of Page


Release Number 8.1.001.12 [08/28/15] – 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 T-Server Common Part (TSCP) release number 8.1.001.78. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server no longer specifies an unexpected 3rd-Party Information parameter in the OAI SCF 10 (Ringstop) message to the PBX in processing a TRedirectCall request. Previously, an unexpected parameter could have been inherited from the previous SCF 10 request, causing the PBX to reject the subsequent SCF 10 request with the invalid parameter. (TS-10958)


Top of Page


Release Number 8.1.001.11 [08/04/15] – 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 T-Server Common Part (TSCP) release number 8.1.001.78. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly handles MakePredictiveCall requests from a Split device. Previously, T-Server used the split instead of the pilot number in the 1st-Party Terminal Info of the OAI SCF Trunk Call request, causing the switch to reject such requests. (TS-10935)


T-Server no longer deletes ISCC calls when two parties simultaneously update UserData with the same key and value, and the option consult-user-data has the value joint. Previously, T-Server treated this situation as a data propagation loop, resulting in ISCC call deletion. (TS-10913)


T-Server now correctly processes an unsuccessful single-step transfer of a consultation call, when the PBX sends an OAI SMFN 3 (Release) message for the transfer originator but the call never reaches the transfer destination. Previously, T-Server misinterpreted this scenario, causing the DN initiating the transfer to remain in the off-hook state when the call was released. (TS-10875)


Top of Page


Release Number 8.1.001.08 [03/31/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 T-Server Common Part (TSCP) release number 8.1.001.77. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly handles OAI SMFN FID=2 (Answer) on the call origination party in the following scenario:

  1. An agent (DN1) makes a call to a Routing Point (RP1).
  2. The routing strategy issues a TGiveMusicTreatment request.
  3. The PBX sends SMFN FID=2 (Answer) for the agent DN (DN1) when the agent is connected to music treatment.
Previously, a CTI event at step 3 triggered an erroneous EventRouteUsed in violation of the Genesys call model. (TS-10897)


Top of Page


Release Number 8.1.001.07 [03/11/15] – 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 T-Server Common Part (TSCP) release number 8.1.001.77. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly handles OAI SMFN FID=2 (Answer) messages with empty 2nd-party information on an Attendant Console device. Previously, such messages caused an invalid call ID mapping inside T-Server, which eventually led T-Server to terminate abnormally. (TS-10878)


Top of Page


Release Number 8.1.001.06 [01/15/15] – 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 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 about 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 corrections and modifications:


For Handyphone devices reported as type "a" (ACD position), T-Server no longer tries to look up sub-line association in Infolink Iq and IW messages. Previously, T-Server ignored such messages. (TS-10802)


Top of Page


Release Number 8.1.001.05 [07/10/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 T-Server Common Part (TSCP) release number 8.1.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly handles Agent state synchronization messages sent by the backup T-Server. Previously, after a switchover, incorrect handling caused the backup T-Server to lose the ReasonCode extension in EventAgentNotReady. (TS-10701)


Top of Page


Release Number 8.1.001.04 [05/12/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 T-Server Common Part (TSCP) release number 8.1.001.73. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 accepts up to 9999 seat licenses newly issued by License Manager when the option num-sdn-licenses is changed from a previous finite value to max. Previously, T-Server did not accept these new licenses. (TS-10640)


In multisite scenarios, T-Server now properly propagates EventPartyAdded when an Observer party connects to the call. Previously, T-Server propagated EventPartyAdded in conference calls only. (TS-850)


T-Server no longer incorrectly generates a second EventError with the same ReferenceID when two agents simultaneously disconnect from a consultation call. (TS-10618)


T-Server now correctly applies dynamic changes for string array options. Previously, T-Server might have incorrectly applied dynamic changes for these options. (TS-9629, ER# 256449305)


Top of Page


Release Number 8.1.000.37 [04/19/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 T-Server Common Part (TSCP) release number 8.1.001.54. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 specifies the second-party terminal information parameter in SCF FID=2 (Release Call) OAI requests in single-step transfer scenarios, when T-Server sends an SCF FID=2 (Release Call) OAI request before the call reaches the transfer destination party. Previously, this OAI request failed and an EventError event was sent with the following error message: Connection terminal mismatch - 1st to 2nd mismatch. (ER#  310123981)


T-Server now implements the enhanced handling of transfer-reconnect and transfer-complete scenarios when establishing a consultation call between an Attendant Console device and a transfer destination. Previously, T-Server was unable to differentiate these scenarios and handled these reconnections as call transfers, causing a call state de-synchronization between T-Server and the actual state on the switch. (ER#  295615201)


Top of Page


Release Number 8.1.000.35 [12/14/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 T-Server Common Part (TSCP) release number 8.1.001.54. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 no longer prevents its clients from registering DNs of type Unknown that are not configured in the Configuration Layer. However, T-Server still restricts DN registration of types Extension, ACD Position, ACD Queue, and Routing Point that are not configured in the Configuration Layer. (ER# 302652935)


T-Server now correctly generates an EventRetrieved message after a TReconnectCall request from a monitored DN. (ER#  310123981)


Top of Page


Release Number 8.1.000.34 [11/16/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 T-Server Common Part (TSCP) release number 8.1.001.50. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


This release of T-Server is built with TSCP 8.1.001.50, which corrects the following issue:

T-Server now correctly sends Local Control Agent (LCA) heartbeat messages. Previously, in scenarios where T-Server was built with TSCP version 8.1.001.47, T-Server could become unstable, if it was running on the same host as LCA 8.1.0 operating in Unresponsive Process Detection mode. (ER#  309597081, ER# 308202408)


Top of Page


Release Number 8.1.000.30 [08/30/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 T-Server Common Part (TSCP) release number 8.1.001.47. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 and modifications:


T-Server now correctly performs User Data propagation for Inter Server Call Control (ISCC) calls in deployments where two or more T-Servers monitor DNs on the same switch and have the value of the match-call-once configuration option set to false. Previously, T-Server stopped the User Data propagation for the ISCC calls. (ER# 302446516)


T-Server now enables more efficient monitored DN deletion processing. Previously, in environments with a large set of DNs under the switch, DN deletion caused T-Server to use an excessive amount of the central processing unit (CPU) resources, which resulted in an overload. (ER# 299721798, ER# 299626400)


Top of Page


Release Number 8.1.000.29 [08/23/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 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 about 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 correction and modification:


T-Server now correctly handles backup synchronization message processing in the following scenario:

  1. The primary and backup T-Servers both operate in primary mode due to a network connection failure.
  2. The backup synchronization connection between the T-Servers is restored.

Previously in this scenario, the synchronization messages for an agent in the Ready state were incorrectly processed, which led to the agent state being incorrectly reported as NotReady. (ER# 305838728)


Top of Page


Release Number 8.1.000.27 [06/14/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 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 about 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 and modifications:


T-Server now correctly distributes an EventRetrieved event for the original call after the following scenario is complete:

  1. Party A calls party B.
  2. Party B initiates a two-step transfer to party C.
  3. Party C answers the call.
  4. Party C puts the call on hold, and then retrieves the call.
  5. Party B reconnects to party A, and then drops the consultation call.

Previously, T-Server did not distribute an EventRetrieved event after a call reconnection attempt.

(ER# 299025227, 296563839)


Top of Page


Release Number 8.1.000.26 [03/14/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 T-Server Common Part (TSCP) release number 8.1.001.36. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 also includes the following corrections and modifications:


When a T-Server running as a Windows service is stopped, the snapshot log is now correctly deleted. Previously, when a T-Server running as a Windows service was stopped from the Solution Control Interface and no links to the PBX were open, the snapshot log was not deleted. (ER# 262180943)


When TRouteCall disconnects a call with AttributeRouteType 7 (RouteTypeReject), T-Server now correctly generates an EventOnHook message. (ER# 281618625)


T-Server now correctly decodes "1st Party information" of an SMFN message when the DN length is 2 bytes. Previously, following a TSingleStepTransfer request, T-Server skipped the decoding of 2-byte DNs (analog station 8#, for example), causing incorrect OAI message processing and consequently stranding the DN On-Hook. (ER# 276564146)


Top of Page


Release Number 8.1.000.24 [01/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 T-Server Common Part (TSCP) release number 8.1.000.31. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 corrections and modifications:


This release of T-Server is built with TSCP 8.1.000.31, which corrects the following issue:

In multi-site conference scenarios involving call path (trunk) optimization at one of the call locations, T-Servers at other call locations now correctly generate EventPartyDeleted messages when an external party leaves the conference. (ER# 291027891, 284077422)


This release of T-Server also includes the following corrected TSCP issue:

In a multi-site environment, when due to delays in messaging between sites, T-Server simultaneously receives two different user data updates for the same call or for a consultation call and its main call, and if the consult-user-data option is set to joint, T-Server no longer alters the internal structures that determine the sequence in which call data updates are performed. Previously, in the rare case of such a collision, T-Server could alter these structures in order to prevent an incorrectly detected data propagation loop and this could break down subsequent user data updates for this call or for this pair of a consultation and a main call. Note the colliding updates are rejected as before, since it is impossible to determine their order of precedence. An important but extremely infrequent limitation: when such user data updates have identical contents, they cannot be distinguished from an actual data propagation loop and a breakdown of subsequent user data updates remains possible. (ER# 286135992, 285906677)


When operating in backup mode, T-Server no longer sends a JL (query agent data) request if the agent logon ID is unknown. (ER# 274734657)


T-Server now sends an EventOnHook message in the following scenario:

  1. An inbound call is answered on a URS-controlled DN A.
  2. URS requests a single-step transfer to an internal party B.
  3. T-Server initiates the transfer using the SCF FID=7 (OAI_SCF_TRANSFER_CALL) OAI request.
  4. Party B answers the call, T-Server sends EventOffHook and EventEstablished messages for party B.
  5. Party B drops the call before T-Server is able to send the SCF FID=2 (Release call) request.
Previously in this scenario, T-Server did not send EventOnHook after Step 5. (ER# 275403500)


Top of Page


Release Number 8.1.000.19 [10/20/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 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 about 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 no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


The primary T-Server now correctly synchronizes Agent states and DN statuses with the backup T-Server. Previously, after a switchover, the new primary T-Server (former backup) reported invalid Agent states and DN statuses in response to respective queries from T-Server clients. This issue only applied to T-Server version 8.1.000.16 and later. (ER# 283834041)


Top of Page


Release Number 8.1.000.18 [10/14/11] – 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 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 about 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 contain any corrections or modifications.

Top of Page


Release Number 8.1.000.17 [10/07/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 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 about 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:

Corrections and Modifications

This release also includes the following corrections and modifications:


T-Server now correctly parses Infolink IV (Call Transfer) messages if a message contains the call identifier attribute. Previously, an error parsing such messages caused incorrect message handling when a party was released from a conference and T-Server received a SMFN3 (Release) event followed by IV (Call Transfer). The reverse order of events did not result in a problem. (ER# 282998601)


A T-Server in backup mode now correctly handles the IW z (Forced Logoff) message from a switch in “dual-redundancy” mode when there is no Primary server with a connected link and an agent state is reset. Previously, this message was ignored, leaving an incorrect agent state. (ER# 283442822)


Top of Page


Release Number 8.1.000.15 [08/04/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 T-Server Common Part (TSCP) release number 8.1.000.23. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release of T-Server is built with TSCP 8.1.000.23, which corrects the following issue:

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


Top of Page


Release Number 8.1.000.12 [07/22/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 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 this release of T-Server for NEC NEAX/APEX.

Corrections and Modifications

There are no corrections or modifications for this release.

Top of Page


Release Number 8.1.000.09 [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 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 NEC NEAX/APEX.

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:


T-Server now properly distributes EventRetrieved events for a transferred party on the original call in a two-step transfer call scenario. Previously in this scenario, T-Server failed to properly distribute EventRetrieved events. (ER# 265305044)


T-Server now encodes the reason parameter of the RLRQ (0x62) OAI message as a one byte integer field. Previously, T-Server encoded this parameter as a two-byte field. (ER# 263418864)


T-Server no longer becomes unstable when an ACD Position object associated with an Extension is removed from the configuration layer, and another ACD Position object associated to the same Extension is subsequently added. (ER# 268759489)


T-Server now correctly specifies the UserData attribute in SingleStepTransfer scenarios. Previously, T-Server incorrectly attached user data from the second call in scenarios where two consecutive calls utilized a SingeleStepTransfer, and the first call failed, because the transferred party hung up. (ER# 265534053)


T-Server now re-sends requests for the monitoring of Hold notifications, (SMFR FID=0x85 (HOLD)), if the previous request has failed. The SMFR FID=0x85 notification is sent during the DN registration process of the link startup when the configuration option oai-hold is set to a value of true. (ER# 264457048)


T-Server now correctly reports the ReferenceID attribute within the EventError event in the following scenario:

  1. An agent, (Agent-1) establishes a consultation call with a peer (Agent-2).
  2. Agent-1 invokes a TReconnectCall request at the same time that Agent-2 hangs up.
  3. The switch rejects the request to reconnect the call, and T-Server generates EventError.
  4. Agent-1 then places the caller on hold using the THoldCall request.

Previously in this scenario, T-Server generated an EventError event containing the ReferenceID from the Hold request (Step 4), and the EventHeld event at Step 4 was missing the ReferenceID attribute. The EventError and EventHeld events now contain the correct ReferenceID attribute from the matching requests.

(ER# 270635613)


Top of Page


Documentation Corrections

This section provides corrections and updates for issues found in currently released documentation for this product.


The following limitation is added:

AttributeCallState may not be propagated according to the call model as CallStateBridged in TEvents in supervision scenarios that involve multiple T-Servers. Typically, CallStateOk will be used instead. This is because this T-Server does not fully support cross-site supervision. (TS-12098)


The configuration options cleanup-idle-tout and notify-idle-tout use values in seconds.


In the Switch Configuration Requirements section of the Switch-Specific Configuration chapter of the T-Server for NEC NEAX/APEX Deployment Guide, step 1 (Enable Answer (Connection) Notification for external trunks) incorrectly instructs you to set Bit 3. The correct setting is Bit 7.


In Table 19, Setting the DN Properties for the NEC NEAX/APEX Switch, of the T-Server for NEC NEAX/APEX Deployment Guide, the entry for SPLIT_ROUTE_POINT incorrectly states "Do not use this type of Routing Point for External Routing Points." You can in fact use SPLIT_ROUTE_POINT for an External Routing Point.


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:

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.


If a DN puts an active call on hold and tries make another call, the switch sends an error message. (TS-10680)

Found In: 8.1.001.02 Fixed In: 

When a single-step conference is requested to a DN where forwarding is set, the call rings at the destination of the request rather than at the forwarding target. (TS-10679)

Found In: 8.1.001.02 Fixed In: 

On NEC 2000 systems, the release of a consultation call by the external party results in a ringing call that cannot be answered through a CTI request. (TS-10629)

Found In:  Fixed In: 

T-Server does not support single-step conferencing to external numbers. (TS-11114)

Found In: 8.1.000.09 Fixed In: 

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

Found In: 8.1.000.09 Fixed In: 8.1.000.15

Switch limitation: The RequestAlternateCall is not supported by T-Server working with an SV8500 switch. (ER# 257517024)

Found In: 8.0.300.09 Fixed In: 

T-Server may improperly clean an internal Call ID table when T-Servers operate in high-availability mode and a primary-to-backup switchover coincides with a switch link failure. (ER# 164945761)

Found In: 7.6.003.03 Fixed In: 

Switch limitation: Because of a limitation of CTI support of the Recall call scenarios on Large-System NEC NEAX/APEX switches, T-Server may incorrectly report the state of a telephony device. (ER# 25873710)

Found In: 7.2.004.00 Fixed In: 

In some configurations of the NEC NEAX SV7000 PABX and CallWorX (an external ACD), there is a known deficiency of ACD behavior during an attempt to route a call to a busy destination from a SPLIT_ROUTE_POINT device via an Infolink IF request. T-Server receives a positive acknowledgement from the ACD, and thus cannot recognize a call routing failure. This behavior affects external call routing to default destinations specified in the extrouter-default-dn or router-default-dn options. (ER# 6372854)

Found In: 7.1.007.01 Fixed In: 

Because of deficient Infolink messaging, T-Server does not support the call-recovery feature on Large-System NEC NEAX/APEX switches where calls distributed from a Split to an agent and not answered within a timeout determined by the switch are re-queued to the Split. In this scenario, the Infolink does not notify T-Server that the call has been re-queued. (ER#  92841)

Found In: 7.1.001.01 Fixed In: 

Service Observing limitations include the following:

Found In: 6.5.200.03 Fixed In: 

If you must use an IP address (such as 180.170.9.150) or a full host name including the domain name (such as server.genesyslab.com), expect to receive a warning during the installation of any application on this host. The warning message informs you that the installation cannot find the specified object; as a result, the installation script does not update the configuration data for this application. If you see this warning, continue with the installation.

After completing the installation, update the configuration data for the application you installed on this host, as follows:

  1. Open the Properties dialog box for the Application object in Configuration Manager.
  2. Enter the correct values for Working Directory, Command Line, and Command Line Arguments on the Start Info tab.
  3. Click Apply and OK to save configuration updates.
  4. If you are using the run.sh file to start the application, verify that the Working Directory, Command Line, and Command Line Arguments are specified correctly in the run.sh file.
Found In: 6.5.100.04 Fixed In: 

In a T-Server multi-site environment where a call may be routed or transferred several times between different T-Servers, the T-Server where a previous instance of the call is still active may not preserve the Connection ID of the call when it arrives back at this T-Server. The original Connection ID is reported in the FirstTransferConnID attribute and can be used by T-Server, instead of the ConnID attribute when backward compatibility mode is enabled. In addition, the LastTransferConnID attribute contains the Connection ID of the call from the previous location.

Found In: 6.5.100.04 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 following operating systems:

Discontinued As Of: 8.1.500.02 as of June 18, 2021

Red Hat Enterprise Linux 5

Discontinued As Of: 8.1.010.02

Red Hat Enterprise Linux 3.0

Discontinued As Of: 8.1.000.09

Solaris 8

Discontinued As Of: 8.1.000.09

Tru64 UNIX

Discontinued As Of: 8.1.000.09

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 Cloud Services, 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.

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.

Top of Page