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 Avaya TSAPI.

• 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 Avaya TSAPI 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 Guide.

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 T-Server Common Part (TSCP) release number 8.5.000.35. 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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 performs proper translation of the switch provided work mode, making it available for T-Server processing in login scenarios. Previously, when a client requested login through CTI, with the Agent ID field containing both the Agent ID and Agent Password values, T-Server did not use the switch provided work mode, and therefore did not reflect the true state of the agent. (TS-12202)

This version of T-Server addresses a problem which can prevent the proper processing of call events in some merged call scenarios. Previously, Avaya TSAPI Call IDs were sometimes reused in quick succession (within 2 seconds) for some merged call scenarios, which caused improper call event processing. (TS-12203)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.5.000.32. 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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 version of T-Server addresses a potential problem with routing, which may result in T-Server using an incorrect Routing cross-reference ID when routing a call, causing the route to fail. (TS-12178)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.5.000.30. 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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 tracks switch queues and ensures it performs a route-thru-queue function only on confirmed switch queues. This version of T-Server also performs DN initialization queries when the backup is promoted to primary for newly promoted T-Servers. This resolves the issue where T-Server incorrectly performs a route-thru-queue function on a non-switch queue. (TS-12127)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.5.000.30. 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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 specifies a positive integer or a null value for the sdn-licenses-in-use counter. Previously, in some rare cases, T-Server distributed a negative value causing an incorrect increase in the number of available SDN licenses. (TS-12116)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.5.000.29. 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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 incorrectly changes the state of a DN to in-service when the switch reports a device state as unknown. A new semi-hidden option is introduced for backwards compatibility.

Option name: map-unknown-device-service-state
Description: Allows mapping of the unknown device's state to out-of-service

Default: all-oos
Valid values:

• all-unknown turns this option off
• all-oos maps any DN that reports unknown device's state to out-of-service

T-Server now uses the timeout functionality to establish connection with the backup T-Server. Previously, the HA connection between the primary and backup T-Server might not, in all cases, transition to the established state, and the state was retained as 'connecting'. (TS-12108) (TS-12032)

Top of Page

Supported Operating Systems

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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 terminates unexpectedly while processing a RequestSingleStepConference, just after the requesting call is cleared. (TS-12104)

Top of Page

Supported Operating Systems

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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

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 can now process ATTEndpointUnregisteredEvent messages properly. Previously, T-Server did not process an ATTEndpointUnregisteredEvent message correctly, causing T-Server to not generate an EventDNOutOfService message, when this event was reported as dependencyMode dmMain. Additionally, T-Server did not update the device state correctly in T-Server, in cases where endpoint events were reported from a device which was not registered as dependencyMode main. T-Server now more strictly enforces endpoint event processing for those events specifically described as dependencyMode main, for the Endpoint Unregistered, Endpoint Registered, and endpoint registration info query responses. (TS-12088)

Top of Page

Supported Operating Systems

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.

Important: This version of T-Server requires TSAPI client 8.1.3 for Windows, and for Linux, client version 8.1.3 along with a patch to address a potential connection issue in TSAPI. Consult Avaya product support notices for more information.

There are no restrictions for this release. This section describes new features that were introduced in this release of T-Server for Avaya TSAPI.

• Starting with this release, T-Server requires FlexNet Publisher License Manager version 11.16 or later.
• T-Server now supports the callingDevice parameter when processing ATTDivertedEvent messages. Previously, in some forwarding scenarios, T-Server did not include a corresponding ANI attribute in T-Server messages. (TS-11992)
• Support for the following operating environments. See the Supported Operating Environment: T-Server Avaya TSAPI page in the Genesys Supported Operating Environment Reference Guide for more detailed information.
  • This release is built on TSAPI SDK 8.1.3 with Visual Studio 2019. (TS-11970)
  • Support for Red Hat Enterprise Linux 7 and 8, 64-bit. (TS-12044, TS-11999)
  • Support for Windows Server 2019.

• See also discontinued operating systems in the Discontinued Support section.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly processes unregister requests. Previously, T-Server sometimes did not unregister a DN, leaving the DN actively registered with TSAPI. This issue, in combination with re-registration of this DN, impacted T-Server�s ability to properly handle a number of call flows, including release scenarios. (TS-12036, TS-12035)

T-Server now restricts the processing of device service states for endpoint registered/unregistered and query registration responses, except for the events that are reported as dmMain. Previously, T-Server did not restrict the processing of these responses, which caused T-Server to sometimes place a DN out of service incorrectly. (TS-12021)

Top of Page

Supported Operating Systems

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.

Important: This version of T-Server requires TSAPI client 7.x, 8.0, or 8.1 and is built with TSAPI SDK 8.1 for Windows operating systems.

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

• This release is built on TSAPI 8.1 SDK on Windows only. See the Supported Operating Environment: T-Server Avaya TSAPI 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 T-Server Common Part (TSCP) release number 8.1.011.11. 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.

Important: This version of T-Server requires TSAPI client 7.x, 8.0, or 8.1 and is built with TSAPI SDK 7.x for both Windows and Linux operating systems.

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

• Support for the TSAPI 8.1 client on all supported Windows versions. See the Supported Operating Environment: T-Server Avaya TSAPI page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer incorrectly initiates call cleanup, due to a failed call monitor, on the wrong call. Previously, this problem could occur in some cases of transfer/conference where T-Server processed a merge while the monitor request on the related original call was outstanding. (TS-11722)

Top of Page

Supported Operating Systems

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.

Important: This version of T-Server requires TSAPI client 7.x and is built with TSAPI SDK 7.x for both Windows and Linux operating systems.

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

• A new pdb file enables collection of diagnostics for analyzing certain exceptions. (TS-11677)

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 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.

Important: This version of T-Server requires TSAPI client 7.x and is built with TSAPI SDK 7.x for both Windows and Linux operating systems.

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

• Support for Windows Server 2016 running in 32-bit compatibility mode. See the T-Server Avaya TSAPI page in the Genesys Supported Operating Environment Reference Guide page for more detailed information and a list of all supported operating systems. (TS-11465)

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 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 about changes to the Common Part that may affect the functionality of your particular type of T-Server.

Important: This version of T-Server requires TSAPI client 7.x and is built with TSAPI SDK 7.x for both Windows and Linux operating systems.

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

• T-Server now enables greater control over internal logging of sensitive data in accordance with the T-Library debug option hide-tlib-sensitive-data. For a detailed description of this feature, see the Genesys Configuration Options Reference Manual, "Common Security Options" section, on the Genesys documentation website. (TS-11488)

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 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 about changes to the Common Part that may affect the functionality of your particular type of T-Server.

Important: This version of T-Server requires TSAPI client 7.x and is built with TSAPI SDK 7.x for both Windows and Linux operating systems.

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

• T-Server can now log out an agent when the client that requested the login is disconnected. If the agent has active calls, T-Server generates an EventAgentNotReady event when the client disconnects and postpones EventAgenLogout until the last call at the agent's DN is over. The following new configuration options control this feature. Note that since soft agents do not support auxiliary workmodes or reason codes, the options logout-on-agent-disc-notready-work-mode, logout-on-agent-disc-notready-reason, and logout-on-agent-disc-reason apply only to agents logged in at a switch ACD Queue.

  logout-on-agent-disc
  Allows T-Server to automatically log out or change the agent state of a particular DN when T-Server detects an abnormal client disconnection while logged in. This option overrides soft-logout-on-agent-disc. Setting this option to a value other than none impacts both soft and non-soft ACD features within T-Server. Note: The default value, not-used, instructs T-Server to continue to use the soft-logout-on-agent-disc option, which affects soft agents only.
  
  Default: not-used
  Valid values:

  • not-used tells T-Server to use soft-logout-on-agent-disc
  • none disables the feature
  • logout: if no calls are active on the logged in DN, T-Server attempts a RequestAgentLogout request. If calls are active on the DN, T-Server issues a RequestAgentNotReady request and postpones the logout request until all calls disappear from the DN.
  Changes take effect: immediately
  

  logout-on-agent-disc-notready-work-mode
  Specifies the work mode used when applying a Not Ready state change triggered by active calls at the time of client disconnection.
  
  Default: not-used
  Valid values:

  • after-call-work uses the after-call work mode
  • aux-work uses the aux work mode
  • not-used uses the default configured work mode
  Changes take effect: immediately
  

  logout-on-agent-disc-notready-reason
  Specifies the work mode used when applying a Not Ready state change triggered by active calls at the time of client disconnection. Note: ReasonCode applies only to aux work mode state changes.
  
  Default: 100 (uses no reason code)
  Valid values:

  • 0-99
  Changes take effect: immediately
  

  logout-on-agent-disc-reason
  Specifies the reason code used when applying a logout state change triggered by the disconnection of the requesting client. Note: ReasonCode applies only to aux work mode state changes.
  
  Default: 100 (uses no reason code)
  Valid values:

  • 0-99
  Changes take effect: immediately
  

  (TS-11340)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly reports AttributeOtherDN for agents and service observers (in the call model, see Service observer External party Releases First). (TS-11428, TS-11429)

In manual consultation calls, T-Server now correctly matches the consultation call to the original call. (TS-11425, TS-11426)

When a route point DN is disabled and re-enabled in the configuration database, T-Server now correctly re-acquires the route point. (TS-11370)

T-Server no longer incorrectly registers DNs on the DMCC link before the DMCC link is fully connected. (TS-11368)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.97. 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.

Important: This version of T-Server requires TSAPI client 7.x and is built with TSAPI SDK 7.x for both Windows and Linux operating systems.

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

• T-Server now supports Linux 6.x. (TS-11022)


• T-Server now supports advanced configurations for changing an agent state when a corresponding agent DN goes out of service (for the soft agent feature only). The advanced configuration enables changing an agent state to the specified state (and work mode) and the ability to apply a delay to the agent state change when a corresponding agent DN goes out of service. After T-Server changes the state, the agent cannot log in until the corresponding DN goes back in service. (TS-11247)

  Three new configuration options, soft-state-change-on-oos, soft-state-change-on-oos-delay, and soft-logout-on-agent-disc, enable this functionality:

  soft-state-change-on-oos
  Default Value: logout
  Valid Values: none, logout, notready, acw, walkaway
  Changes Take Effect: Immediately
  Description: T-Server automatically changes the agent state to the specified state (work mode) when the corresponding agent DN goes out of service (OOS). You can delay the agent state change by specifying a delay in the related option soft-state-change-on-oos-delay. After T-Server changes the state, the agent cannot log in until the corresponding DN goes back in service.
  Valid option values are:
  
  • none-No agent state change is performed.
  • logout-The agent is automatically logged out. This is equivalent to setting the existing option logout-on-out-of-service to true.
  • notready-The agent is automatically made not ready.
  • acw-The agent is automatically made not ready with work mode AgentAfterCallWork.
  • walkaway-The agent is automatically made not ready with work mode AgentWalkAway.
  
  soft-state-change-on-oos-delay
  Default Value: 0
  Valid Values: Integer from 0 to 3600000
  Changes Take Effect: Immediately
  Description: Specifies the period of time, in milliseconds, that T-Server waits before changing the agent state specified by the soft-state-change-on-oos option. If the corresponding agent DN comes back in service before the delay is completed, T-Server does not change the agent state. This avoids the automatic agent state changes if a DN goes out of service (OOS) for only a short time.
  
  soft-logout-on-agent-disc
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately
  Description: When set to true, T-Server automatically logs out the soft agent on client disconnection, if this client has previously logged in through the soft-acd feature.
  


• T-Server now supports Enhanced Service State Reporting for extensions at the port level and reports DNs as out-of-service when a DN is detected to be out-of-service; conversely, T-Server reports a DN as in-service, when a DN is detected to be in-service. (TS-11227)
  Important: Due to the current level of reporting of DN port service states in TSAPI, T-Server cannot guarantee real-time reporting of these messages for all cases.

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 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 about changes to the Common Part that may affect the functionality of your particular type of T-Server.

Important: This version of T-Server requires TSAPI client 6.3.3 or later.

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

• Support for Avaya Communication Manager 7.x was added November 10, 2016.

  Important: To effect inter-PBX transfers to VDNs under Communication Manager 7, ensure that you include at least one second of music or an announcement as your first wait step, not silence. These values ensure that, for the transferring side, all appropriate messaging is generated to enable the transfer to complete in a timely fashion.

Corrections and Modifications

This release includes the following corrections or modifications:

Previously, in cases where multiple outstanding pending requests were active on a DN, including a consultation call type request, T-Server might not find the original outstanding consultation request, associated with the DN, when creating the call. This could prevent T-Server from linking a call to its original call and prevent the classification of this call as a consultation. T-Server now corrects this problem with improved searching for consultation type requests. (TS-11188)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.81. 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.

Important: This version of T-Server requires TSAPI client 6.3.3 or later.

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

• T-Server adds support for TSAPI Private Data up to and including version 12.

Corrections and Modifications

This release includes the following corrections or modifications:

When the DMCC link is in use, T-Server can make use of an agent status query to determine the reason code when manually switching the phone set to not ready aux. T-Server previously utilized an invoke ID of 0 for this query. This can lead to a potential collision of invoke IDs in T-Server, which can cause T-Server to fail to properly notify clients of not ready aux state changes (for manual state changes). T-Server corrects this problem by ensuring proper invoke ID assignment for this query. (TS-11170)

This version of T-Server addresses a problem with the processing and translation of CTI acknowledgments (CSTAHoldCallConfEvent and CSTARetrieveCallConfEvent) from outstanding RequestRetrieveCall and RequestHoldCall requests. Previously, T-Server did not process positive responses to RequestRetrieveCall and RequestHoldCall, instead waiting for unsolicited retrieve (CSTARetrievedEvent) and unsolicited held (CSTAHeldEvent) events. This failed processing of proper acknowledgment on these requests can lead to a mismatch of requests and responses in the case of multiple outstanding requests (RequestRetrieveCall/RequestHoldCall) on the same DN. This version of T-Server addresses this problem by translating CSTAHoldCallConfEvent and CSTARetrieveCallConfEvent to EventHeld and EventRetrieved, respectively. (TS-11168)

This version of T-Server corrects a problem with the use of deviceIDType in TSAPI messages. Previously, T-Server did not properly consider deviceIDType, which could cause T-Server to misclassify a party as internal rather than external. In some scenarios this might cause T-Server to misclassify the calltype as internal rather than inbound. (TS-11143)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.81. 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 or modifications:

T-Server corrects a problem which sometimes caused requests on a particular DN to fail, in cases where T-Server made use of the DMCC link and where the DMCC link was also unstable. This instability, in combination with failed outstanding DMCC requests, could have caused unrelated normal CTI requests to inadvertently queue indefinitely within T-Server. (TS-11125)

Top of Page

Supported Operating Systems

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 or modifications:

T-Server corrects an issue in certain forwarding scenarios, where T-Server incorrectly released a party, leading to problems controlling the call. (TS-10959)

Under some registration conditions in large environments, T-Server no longer prematurely drops the link. (TS-10920)

Previously, under some conditions, T-Server might not receive a confirmation from an open call to TSAPI. In these cases, T-Server would not attempt to retry the open request, potentially leading to T-Server not starting properly. This version of T-Server adds support for recovering from a non-responding TSAPI open request. T-Server now waits a default maximum of 90 seconds for an open confirmation, before aborting the previous open request and retrying. (TS-10912)

A new option can change this timeout:

Option Name: tsapi-open-conf-timeout
Valid Values: 0-3600; 0 disables the timer
Default Value: 90
Description: This option provides a timeout (in seconds) for the TSAPI open request call. When attempting to open a connection to TSAPI, T-Server waits the specified amount for an open confirmation before aborting the open request and retrying.

This version of T-Server corrects a potential problem which could cause event distribution, by timer, to occur out of order. In some situations, this problem could lead to an incorrect call model. (TS-10883)

During a call cleanup query, T-Server no longer deletes the wrong call on the wrong call ID. (TS-10846)

Top of Page

Supported Operating Systems

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 or modifications:

In routing scenarios where a call is routed to a second routing point, T-Server now sets the correct CallState (CallStateOk) in an EventQueued event. Previously, T-Server might have set the CallState to CallStateForwarded rather than CallStateOk.

A new restricted option can restore the previous behavior:

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

Option Name: filter-third-party-on-vdn-redirect
Valid Values: true, false
Default Value: true
Description: When the value is true, T-Server ignores the NewDestination attribute in translating a CSTADivertedEvent for routing point DNs. To restore previous behavior, set the option to false.

(TS-10893)

Top of Page

Supported Operating Systems

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:

• T-Server for Avaya TSAPI adds the option enable-ucid-swap, which controls the UCID byte order. (TS-10862)

  Option Name: enable-ucid-swap
  Valid Values: false, true
  Default Value: false
  Description: T-Server for Avaya TSAPI receives UCIDs in host order. The default value, false, reports the UCID value in AttributeExtensions in the same order. Setting the value to true reports UCIDs in network order (reversing the host order).

  Synchronizing UCIDs between Avaya TSAPI and Avaya Communication Manager T-Servers: T-Server for Avaya TSAPI receives UCIDs in host order (0011...EEFF, for example), while T-Server for Avaya Communication Manager receives UCIDs in network order (FFEE...1100, for example). To synchronize the values reported to clients by T-Server, you must set the opposite value for enable-ucid-swap in each server. To report UCIDs in host order (the default), set the value in T-Server for Avaya TSAPI to false and the value in T-Server for Avaya Communication Manager to true. To report UCIDs in network order, set the value in T-Server for Avaya TSAPI to true and the value in T-Server for Avaya Communication Manager to false.

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 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 does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

For EventQueued events where the reporting call is not yet created, T-Server now filters, by default, the cause ecRedirected. The resulting call state is CallState 0, replacing CallStateForwarded. (TS-10858)

A new restricted option can restore the previous behavior:

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

Option Name: enable-callstate-forwarded-on-first-queued
Valid Values: true, false
Default Value: false
Description: When set to true, the option filters the ecRedirected cause for EventQueued events, resulting in the call state CallStateForwarded.

T-Server no longer distributes DN-related events to a client that sends a RequestRegisterAddress request for a DN to T-Server but receives EventError in response. Previously, after such failed registration requests, T-Server would continue to distribute events for a DN even after a failed registration attempt. (TS-10855)

Top of Page

Supported Operating Systems

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.

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

• Support for Windows Server 2012, 64-bit, running 32-bit executables in compatibility mode. (TS-10752)

• Support for the TSAPI 6.3.3 SDK required for Windows Server 2012.

Corrections and Modifications

This release includes the following corrections or modifications:

Previously, under some call flows, the backup T-Server could incorrectly process a message from the primary T-Server, rendering the backup T-Server unstable. This version of T-Server corrects the problem. (TS-10737)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.71. 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 release tracking now correctly reports the first party to release the call when such information is available. Previously, in some call flows involving Routing Points, release tracking reported the releasing party as unknown. (TS-10677)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.71. 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 addresses a potential problem for the feature that sets the AttributeCallType attribute at the time a call is dialed for manually initiated calls (see the second-call-as-consult configuration option ) and corrects it by properly processing the TSAPI version 8 Service Initiated messages. Previously, in call flows where TSAPI returned a version 8 Service Initiated message, T-Server failed to recognize this message, and would not properly link an original call to the initiated consultation for manually initiated calls where second-call-as-consult was enabled. (TS-10622)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.66. 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 includes the program database (PDB) file for the Windows' distribution package. This PDB file contains the essential debug symbols that can be used in diagnosing future stability problems. (ER# 322368937, TS-856)

T-Server now addresses an issue related to unacquiring a Routing Point DN and ensures that any unsolicited unacquire requests are processed and any unacquire requests resulting in an invalidCrossRefId error are reinterpreted as unacquired. Previously, failure to properly unacquire a DN could result in T-Sever not attempting to retry the registration of a DN. (ER# 321867077, TS-853)

Top of Page

Supported Operating Systems

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 does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly handles TSAPI-link delays when registering Routing Points. Previously, a race condition could occur which disrupted the synchronization between T-Server and the switch in the control of a route point, causing T-Server to be unable to route calls. (ER# 303690060)

T-Server can now control the serialization of TMakePredictiveCall requests. By default, T-Server does not serialize these requests. In order for T-Server to serialize TMakePredictiveCall requests, set the value of the restricted configuration option, serialize-predictive-calls, to true.

serialize-predictive-calls
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If the value of this option is set to true, T-Server serializes all TMakePredictiveCall requests for a particular DN and it sends a subsequent request to the switch only after receiving a response to the previous request. If the value of this option is set to false, T-Server does not serialize TMakePredictiveCall requests.

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

(ER# 289729847)

T-Server now supports a new Application-level configuration option, req-distrib-event-support, in the TServer section, to resolve backward compatibility issues.

This option controls the content of the T-Events, propagation of which is requested by RequestDistributeEvent. The scope of the distribution depends on the presence and the values of AttributeClientID and AttributeReferenceID, as follows:

• If the value of this option is set to check-client and if the AttributeClientID attribute is not present in the RequestDistributeEvent message, T-Server does not include the AttributeReferenceID attribute in the event distributed to clients. If the AttributeClientID attribute is present in the RequestDistributeEvent message and a client is connected with that ClientID, T-Server sends the event containing the AttributeReferenceID attribute to this client and sends the event without the AttributeReferenceID attribute to the other clients.

• If the AttributeClientID attribute has a value of -2 and the AttributeReferenceID attribute has a value of -2, T-Server sends the event with the AttributeClientID and AttributeReferenceID attributes to all clients registered for ThisDN. If the AttributeClientID attribute has a value of -2 and the AttributeReferenceID attribute has a value other than -2, T-Server sends the event without the AttributeReferenceID attribute to all clients registered for ThisDN.

• If the AttributeClientID attribute has a value other than -2 and no client is connected with that ClientID, T-Server sends an EventError response to the client that sent the RequestDistributeEvent message and the requested event is not distributed to clients.

• If the option is set to no-check, T-Server does not check for clients that are subscribed for RequestDistributeEvent messages and reports the AttributeReferenceID attribute in event messages (backward compatible mode).

(ER# 299869422, 303203071)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.37. 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:

• This version of T-Server adds a new LMS message for the Agent No Answer Supervision feature. In cases where the Agent No Answer Supervision feature is triggered, T-Server now generates a STANDARD-level message in the following format:

  AgentNoAnswer (%d): Queue %s, AgentId %s, for party %s:%s -> Overflow %s

  where, from left to right:

  %d—represents the number of seconds of waiting before this feature was engaged.
  %s—represents the queue (or N/A) which distributed the call to this party.
  %s—represents the agent ID (or N/A) logged into the provided queue.
  %s—represents the connection ID of the call.
  %s—represents the party which triggered the overflow condition.
  %s—represents the overflow DN (or N/A) where T-Server will attempt to redirect this call.
  

  (ER# 289977641)

• T-Server is now built with TSAPI SDK 6.1.1 for both Windows and Linux operating systems.

• Limited display of sensitive information: In logs, new options enable sensitive data in logs to be marked for post-processing by the user, such as deletion, replacement, or hiding. See the Genesys 8.1 Security Deployment Guide for details.

• Compliance with FIPS: TLS as implemented by Genesys meets the Federal Information Processing Standards (FIPS).

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now reports the calling party number in the OtherDN attribute of EventRouteRequest when the calling party number is provided by the switch. (ER# 291968447)

The default value of the use-link-bandwidth configuration option has been changed from 0 to 100. (ER# 284712700)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.000.26. 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:

This version of T-Server fixes an issue which can impact T-Server�s ability to route calls. Previously, in some cases of link disconnection, T-Server would sometimes indirectly process route point acquire responses, which sometimes led to failed routing with EventError (Invalid cross-reference ID). (ER# 284964591)

Top of Page

Supported Operating Systems

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 features or functionality.

• T-Server now supports use of Processor Ethernet connections between the PBX and TSAPI.

Corrections and Modifications

This release includes the following corrections and modifications:

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

HA T-Server or SIP Server no longer becomes unstable in an environment where a new application object is created with a connection to the running HA T-Server or SIP Server. This issue was applicable only to HA deployments, and could occur in any of the following scenarios:

• If an application created in the manner above was deleted or renamed from the configuration environment while HA T-Server or SIP Server was running.
• If a connection to HA T-Server or SIP Server was deleted from the application created in the manner above, while HA T-Server in question was running.
• If one of the HA T-Servers or SIP Servers was stopped via Solution Control Server (SCS) after the client's application and its connections were created dynamically.

Top of Page

Supported Operating Systems

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 does not contain any 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

Supported Operating Systems

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 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 section describes new features that were introduced in the initial 8.1 release of T-Server for Avaya TSAPI.

• 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 now supports the releasing-party-report configuration option to enable the Call Release Tracking feature, which provides information about which party initiated the release of the call. See the Framework 8.1 T-Server for Avaya TSAPI Deployment Guide for details.
• T-Server now supports the configurable mapping of cause codes to the CallState attribute for predictive dialing scenarios. See the Framework 8.1 T-Server for Avaya TSAPI Deployment Guide for details.
• T-Server now supports HA synchronization of Agent Ready/Agent Not Ready work modes from a primary T-Server to its backup. (ER# 229745757)
• T-Server adds support for automatically deleting a call, in T-Server memory, in conditions where RequestClearCall fails with an EventError indicating no active call. This feature is helpful in unusual scenarios where the link and T-Server would lose synchronization on a specific call (T-Server shows a call exists when in fact it does not); allowing the immediate correction of the problem. (ER# 262486321)
• T-Server adds support to dynamically enable and disable of DN registration over the DMCC link when the enable-dmcc option is set for a particular DN. (ER# 258807121)
• The list of valid values for the use-am-detection configuration option has been modified. T-Server now supports values of true, drop, connect, admin, false, and unspecified. See Framework 8.1 T-Server for Avaya TSAPI Deployment Guide for details. (ER# 270335581)
• T-Server now supports link status messages. T-Server now requests System status information from the switch and looks at the link status messages to determine link up or link down. In case of link down, T-Server will generate an appropriate EventLinkDisconnected. T-Server only attempts DN registration (and generates EventLinkConnected), when the link status indicates link up. (ER# 264397211)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now supports Service Observing from a trunk. Previously, if Service Observing was performed from a trunk, T-Server did not send the required EventPartyAdded message to note that Service Observing had started. These events are now sent as part of the standard Service Observing call model. (ER# 266981827)

Top of Page

Known Issues and Recommendations

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

On Avaya Aura 10.1, routing calls over a trunk might fail when UUI IE Treatment is set to shared. This would make it impossible to use outbound routing and UCID call overflow together. For details, please contact Avaya and reference DevConnect ticket number 35702.

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)

In scenarios in which T-Server is running with an active Device, Media, and Call Control API (DMCC) link, there is a potential race condition that can occur if the DMCC link and the primary CTI-link become out of sync. This race condition can potentially cause duplications of Agent level events during login, when login is followed by an immediate agent state change request. (ER# 259773691)

T-Server for Avaya TSAPI currently does not use the administrative treatment when the option use-am-detection is set to false or no or when the Extensions attribute key AMD (set to no) is present in the TMakePredictiveCall request. This behavior is different from the T-Server for Avaya Communication Manager, which follows the switch answering machine detection administration when the use-am-detection option is set to false or no or when the Extensions attribute key AMD (set to no) is present in TMakePredictiveCall. (ER# 246432571)

When making a conference call from a principal or bridged DN (in a bridging call flow), the resulting conference in T-Server will not result in the bridging DN being dropped from the call. This may create the impression that the bridging party is still a member of the call when in fact it may have been dropped by the switch. (ER# 227237951)

In scenarios where a call is redirected back to the same queue from which it had previously passed, the EventQueued and EventDiverted event sequences may be missing when the call diverts from the queue. This means that the first queued and diverted messages go back into the same queue, so instead of two sets of messages, only one message returns, and is diverted the second time. (ER# 225250782)

T-Server sometimes fails to update transitional agent states in the backup T-Server. (ER# 229745757)

The Outbound Contact Server (OCS) does not follow the correct call flow in cases where an EventRinging message is sent before EventQueued or EventDiverted. (ER# 235720427)

T-Server does not handle predictive dialing to ACD Queues correctly. It distributes the EventQueued message in the wrong sequence (after distributing the EventRinging to the agent) and without distributing the EventDiverted. (ER# 235720421)

The Transfer Connect Service does not work correctly when the call is connected to an announcement port. (ER# 234107441)

If there are conference members in different partitions, party events may not be reported correctly for single-step conferences. For correct event reporting on partitioned environments, use two-step conferences. (ER# 238262936, 238625235)

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:

• Windows Server 2012
• Windows Server 2008
• Red Hat Enterprise Linux 6
• Red Hat Enterprise Linux 5

Red Hat Enterprise Linux 4.0 operating system

Red Hat Enterprise Linux 3.0 operating system

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.

• The Framework 8.1 T-Server for Avaya TSAPI Deployment Guide contains detailed reference information for the Genesys Framework 8.1 T-Server for Avaya TSAPI including configuration options and specific functionality.

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

• The Genesys Events and Models Reference Manual contains an extensive collection of events and call models describing core interaction processing in Genesys environments.

• The Platform SDK 8.x .NET (or Java) API Reference contains technical details of T-Library functions.

• 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.

Top of Page