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

• 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 Communication Manager page in the Genesys Supported Operating Environment Reference Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 8.1.x.
• Your T-Server’s name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see More Release Information/Legal Notices for T-Servers. Please contact your Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

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

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

Corrections and Modifications

This release includes the following corrections or modifications:

This version of T-Server adds support for processing second-call-as-consult on the ASAI Originated Event report in addition to processing it on the Initiated Event report. You can disbale this feature by using the new semi hidden option second-call-as-consult-on-originated. Previously, the linking of manual consult calls to a primary held call, when the second-call-as-consult option was enabled, was only processed on the Initiated Event report. However, in some cases the Initiated Event report was not propagated by ASAI for all types of DNs.

To control processing the second-call-as-consult feature on the Originated Event report, a new option has been introduced:

second-call-as-consult-on-originated

Setting: [TServer] section
Default: true
Valid values: true, false
Changes take effect: immediately

When both the second-call-as-consult-on-originated and second-call-as-consult options are set to true, T-Server attempts to link manual consult calls to a primary held call on both the Initiated and Originated Event reports. Setting this option to false doesn't process the second-call-as-consult feature on the Originated Event report. (TS-12229)

Top of Page

Supported Operating Systems

New in This Release

This release was promoted to Update on May 6, 2022.

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 use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or 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-12107) (TS-12112)

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 use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

When the originating inbound party has an unknown party ID and an unmonitored service observing party is added to the call, T-Server now ensures the correct party ID is assigned to the originating party, using a query for releasing information associated with a dropped call. Previously in this scenario, some call flows might have shown incorrect releasing party information. (TS-12055)

To process party ID information from the query, a new option was introduced:

query-for-party-id-correction

Setting: T-Server application object, Options tab, [TServer] section
Default: true
Valid values: true, false
Changes take effect: immediately

When this option is set to true, T-Server processes the party ID information from the query to ensure all parties on the call have the correct party ID assignment. (TS-12061)

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.23. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

• Starting with this release, T-Server requires FlexNet Publisher License Manager version 11.16 or later.

• Support for Red Hat Enterprise Linux 8, 64-bit. See the Supported Operating Environment: T-Server Avaya Communication Manager page for more detailed information and a list of all supported operating systems.

• T-Server is now built with libraries supporting OpenSSL 1.1.1 and Genesys Security Pack 8.5.100.24+, which is based on OpenSSL 1.1.1 and supports TLS 1.3. (TS-11969)

Corrections and Modifications

This release includes the following corrections or modifications:

An improved party ID algorithm now helps to ensure that correct party IDs are assigned. T-Server now corrects and updates party IDs for parties on the call during call processing of take control and single-step conferences. (TS-11958)

Workspace Desktop Edition (WDE) no longer displays a conference leg after disconnect. (TS-12016)

Genesys Agent Desktop (GAD) now displays conference calls correctly. Previously, GAD showed the customer as being on hold and the two agents as on a consultation call. (TS-12004)

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.18. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer applies a RequestDeleteFromConference to the wrong party. Previously, in some cases, T-Server associated an unmonitored internal party with an incorrect party ID. (TS-11947)

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.06. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

• Support for the Windows Server 2019 operating system and Windows 2019 Hyper-V virtualization. See the Supported Operating Environment: T-Server Avaya Communication Manager page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes the following corrections or modifications:

This version of T-Server corrects a call model problem impacting service observing parties in conference scenarios. When a conference call is initiated and completed with an active service observing party, T-Server now generates an EventPartyAdded message for the observing party containing ThisDNRole set to RoleObserver. (TS-11201)

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.06. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly assigns PartyIds in call flows where a conference to a remote party completes before the remote party is reported to T-Server. Previously, the external party was created in T-Server and might be assigned an incorrect PartyId. Later when the remote party was reported with the correct PartyId, T-Server did not properly update the PartyId. This could lead to problems in correctly identifying this party to CTI requests, such as RequestDeleteFromConference. (TS-11723)

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.04. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer causes RequestListenDisconnect to incorrectly mute/unmute the wrong party. Previously, the problem occurred because of an incorrect mapping of partyIDs in some call flows involving RequestSingleStepConference. (TS-11599)

When the Call Release Tracking feature is enabled in T-Server, in some scenarios T-Server may incorrectly report the drop controller as the internal party when in fact the drop controller is the other party on the call. To avoid incorrect reporting in these call flows, T-Server flags the drop controller as "Unknown" because it cannot accurately determine the drop controller in all call flows.

To preserve backwards compatibility, a new option can enable this functionality:

strict-call-release-tracking

When true, applies a stick algorithm in determining the drop controller when an internal DN is alerting and the call is abandoned. Under these call flows, T-Server applies in AttributeExtensions a value of "3 Unknown" for the "ReleasingParty" key.

(TS-10768)

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.04. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

• A new configuration option, override-call-type, specifies a call type for internal calls that land on a routing point and have not been yet assigned a call type. This option addresses the need to assign a call type of outbound to calls initiated during predictive campaigns.

  override-call-type

  Setting: DN object, Annex tab, [TServer] section
  Default: 0 [no override]
  Valid values:

  • 0 [no override]
  • 3 [sets call type to outbound]
  Changes take effect: on the next call
  

  Sets the call type of internal calls arriving at the specified routing point.

  (TS-11663)

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.5.000.04. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

• This initial release of T-Server 8.1.5 adds support for Microsoft Visual Studio 2013 and withdraws support for Microsoft Visual Studio 2008 and earlier. (TS-11596)

  Important: This release is not available on the AIX and Solaris platforms.

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

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

• Support for Avaya Communication Manager 8.1 on Solaris 10, added February 13, 2020. See the Supported Operating Environment: T-Server Avaya Communication Manager page for more detailed information and a list of all supported operating systems. (TS-11897)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server's "query-on-timer" feature now correctly updates the query timer when an agent state changes through CTI. Previously, the lack of such an update could cause a longer query interval then expected based on the current agent state. (TS-11485)

A backup T-Server now populates AttributeAgentID in agent events following switchover even if it has received from the link a prior login message without the LogicalAgent element, which corresponds to the Genesys Agent ID. Previously, the backup T-Server would ignore the Agent ID on the agent synchronization message from the Primary T-Server if the agent was already logged in. (TS-11401)

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

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

• Support for the Windows 2016 operating system. See the Supported Operating Environment: T-Server Avaya Communication Manager page for more detailed information and a list of all supported operating systems.

• 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-11480)

  Important: Some caller-entered digits may appear in the hexadecimal encoding of unsolicited switch messages. You can disable printout of switch messages by setting the -sw flag in the log-trace-flags T-Server option.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer prevents proper generation of in-service and out-of-service events for DNs set to on-demand in Configuration Layer. (TS-11490)

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

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

Corrections and Modifications

This release includes the following corrections or modifications:

When the link aborts a DN monitor, T-Server now marks it as out-of-service. Previously, an agent DN could become unregistered without being marked as out-of-service, which could result in a failed TServer client request. For example, a call-related hold function could result in an EventError ("Invalid call identifier used or call does not exist"). (TS-11452)

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.03. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now reports correct releasing party information for the call release tracking feature. Previously, T-Server sometimes reported incorrect releasing party information if there was a delay in the processing of the release message. (TS-11386)

T-Server can now process call events properly for some merged call scenarios in which CallIDs were reused in Avaya Communication Manager in quick succession (within 2 seconds). (TS-11412)

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.03. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly processes outstanding client requests during certain internal error states. Previously, these states could result in mismatched requests and responses, including incorrect call types for consultation calls. (TS-11392)

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.02. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer unregisters the DN on the switch when a call is deleted within T-Server. Previously, under some conditions T-Server incorrectly unregistered the DN, causing the DN to go out of service. (TS-11383)

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.02. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

• Support for TLS 1.2 was added in May 2017. To use TLS 1.2, you must set the value of the security option sec-protocol to TLSv12 on the host, port, or application level at which the secure connection is defined. For more information, see Securing Connections Using TLS. (TS-11338)


• Support for the Red Hat Enterprise Linux 7.x, 64-bit operating system. See the Supported Operating Environment: T-Server Avaya Communication Manager page for more detailed information and a list of all supported operating systems. (TS-11336)


• 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-11251)

Corrections and Modifications

This release includes the following corrections or modifications:

When the epp-tout option is configured, T-Server now correctly suspends EventCallDeleted along with other call-related events when the consultation call is merged with the main call. (TS-11358)

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

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

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

• T-Server now supports a maximum of 64,000 client connections on Windows 2008 64-bit R2 servers, depending on CPU and memory.
• T-Server now supports resetting of the agent no-answer timer when T-Server detects a RequestAnswerCall on a party that has an active pending timer. Resetting the timer in this context helps to avoid situations where the agent no-answer timer fires too early (resulting in an agent no-answer action) while an existing RequestAnswerCall is already pending in T-Server. See the T-Server Deployment Guide for more information on GCTM support for the Agent No Answer feature. (TS-11196)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now properly adds unmonitored conference members to a call that results from a successful predictive call. Previously, T-Server did not properly add these members, possibly resulting in an incorrect number of reported parties on a call and leading to incorrect party mapping to inbound release messages (resulting in incorrect reporting of unmonitored party drops). (TS-11274)

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

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

• Support for Avaya Communication Manager 7.x. Communication Manager is supported with custom patch 23413 or a patch that includes patch 23413.
• Support for Mutual TLS connection to Message Server at the host level. (TS-11212)
• A new Avaya "replace CPN" protocol enables the sending of both UUI and a Calling Party Number within the UUI Information Element, over both SIP trunks and ISDN. T-Server supports:
  • Sending both CPN and some attached data over SIP trunks (but not ISDN, which still allows only a CPN or attached data but not both).
  • Setting the new CPN protocol for all RequestMakeCall, RequestMakePredictiveCall, and RequestRouteCall requests, or for individual requests. To set the new protocol for an individual request, set the CPN extension key:
    • CPN Extensions Key: CPNProtocol
    • Type: Int
    • Valid Values:
      • OLD PROTOCOL = 0
      • NEW PROTOCOL = 1
      • USE TS CONFIG = unspecified
    • Default: unspecified
  • The use of the UU_DATA key in extensions of the request, which is the recommended way to attach raw UUI data to a call during call creation and closing.

  A new configuration option enables the new protocol for all requests:

  cpn-protocol
  Enables or disables the new replace CPN protocol.
  Default: 0
  Valid values:

  • 0 uses the old CPN protocol
  • 1 enables the new CPN protocol
  Changes take effect: immediately
  

  (TS-10861, TS-11237)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now automatically synchronizes agent state, by query after start-up, when adding a DN to the configuration or registering a DN dynamically. Previously, T-Server did not attempt to obtain the agent state of a DN when adding a DN to the configuration or when registering a DN dynamically after startup. (TS-11182)

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

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly reports a service observing conference member's ThisDNRole as RoleObserver upon release. Previously, T-Server misreported the member as RoleConferenceMember. (TS-11171)

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

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

• T-Server optimizes agent extension (DN) registration in High Availability (HA) environments by eliminating unnecessary registrations, based on the agent login state. (TS-11023)

  Prerequisite: All queues used in your environment must be accurately represented in Configuration Database.

  A new configuration option, optimize-extension-registration, controls the new functionality. Genesys also recommends that you set a second option, allow-reg-unreg-on-link-disconnect, to true, to enable T-Server to process client RegisterAddress and UnregisterAddress requests when the CTI link is down.

  • optimize-extension-registration
    

    Allows T-Server to

    • conserve switch resources by preventing an extension DN from being registered when an agent is not logged into the configuring DN, and
    • unregister a DN automatically, when an agent logs out of the DN, as long as the extension is not on a call.

    You can set this option at the application level to apply it to all DNs, or at the DN level (on the DN annex tab). Note that a setting of off overrides any DN-level settings.

    Section: TServer (at application or DN level)
    Default: none
    Valid values:

    • none disables the feature for all DNs but does allow you to enable the feature for a specific DN, through the setting of the corresponding annex tab DN-level option.
    • off disables the feature for all DNs and does not allow DN-level enablement.
    • on-logout-backup-only tells T-Server to register the specified DN only when the DN is detected to be logged in. T-Server unregisters the DN when the DN is detected to be logged out, if T-Server is not tracking a call on this DN. This value applies only when T-Server is running in backup mode. You can override this setting at the DN level.
    • on-logout-always tells T-Server to register the specified DN only when the DN is detected to be logged in. T-Server will unregister the DN when the DN is detected to be logged out, providing T-Server is not tracking a call on this DN. This value applies when T-Server is running in either primary or backup mode. You can override this setting at the DN level.

    Changes take effect: immediately

  • allow-reg-unreg-on-link-disconnect

    Enables T-Server to process client RegisterAddress and UnregisterAddress requests when the CTI link is down.

    Section: TServer
    Default: true
    Valid values: true, false
    Changes take effect: immediately
    

• This version of T-Server adds support for cause: Network out of order (CS0/38). In T-Server, this cause is translated to AttributeErrorCode: TERR_ASAI_NETWORK_OUT_OF_ORDER. (TS-11059)

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.72. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

This release of T-Server is built with TSCP 8.1.010.72, which adds these improvements to multisite scenario handling:

• ISCC now successfully supports Party Events propagation and User Data update propagation for calls that are not delivered to the requested transaction destination but have been successfully matched at the destination site. Previously, ISCC cancelled User Data update propagation when a transaction failed because the requested transaction destination could not be reached.
• ISCC now activates Party Events propagation as soon as a call is matched on the destination T-Server. Thus the next T-Event includes all updates provided from the origination side after the matching.
• This release improves the synchronization of IS-Link states between T-Servers in unsuccessful scenarios with inaccessible destination numbers. It eliminates a race condition in the processing of historical information. This improvement, however, may interfere with historical reporting for failed multisite calls.

(TS-10946)

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.68. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly maps party IDs in call flows where:

• a transferred message is received on behalf of an external party controller, and
• one internal unmonitored extension and one external party is reported remaining on the call.

T-Server no longer quits unexpectedly during unusual race conditions that could occur when a call was being destroyed and a client simultaneously issued a related call request. (TS-11026)

Lists of queues that are associated with an agent DN in T-Server are now synchronized with the switch. Previously, list desynchronization could impact call flows and features, such as "route-thru-queue", that depended on correct representation of such queue lists. (TS-10853)

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.66. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections or modifications:

In certain multi-site scenarios involving trunk optimization after a call is routed back from a second site to the original site, T-Server now correctly deletes internal objects that it created for event propagation paths. Previously, T-Server did not delete those objects, which caused memory growth. TSCP version 8.1.010.51 originally corrected this problem by implementing the path optimization feature. To achieve the correct behavior, set path-optimization=true in the ISCC Protocol Parameters of the Switch Access Codes for both the local and the remote switch. (TS-10963)

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

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

Corrections and Modifications

This release includes the following corrections or modifications:

This release improves the way DN registrations are counted. Previously, after a link start or restart, T-Server could mishandle DN registration, resulting in a missing EventLinkConnected. (TS-10807)

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

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

Corrections and Modifications

This release includes the following corrections or modifications:

In call flow scenarios involving a manual off-hook condition followed by a CTI TMakeCall request, T-Server now correctly applies stuck call detection logic. Previously, a call might be destroyed and recreated during the initiation phase of a call, inadvertently impacting high-availability (HA) scenarios by preventing the backup T-Server from correctly synchronizing the call connection ID to the backup. The resulting problem could later prevent control of the call and proper synchronization of User Data after HA switchover. T-Server now ensures that stuck call detection logic does not apply to calls initiated by single parties. (TS-10791)

A new configuration option enables you to partially or completely disable stuck call detection logic. You do not need to change its value to resolve the scenario above.

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

reused-call-id-detection
Enables or disables stuck call detection logic.
Default: true
Valid values:
true enables stuck call detection for all cases
false disables stuck call detection for all cases
proceed-only applies stuck call detection only on a CTI proceed message
initiated-only applies stuck call detection only on a CTI initiated message
Changes take effect: immediately

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

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

• You can now configure default work modes for TAgentLogin, TAgentReady, and TAgentNotReady requests when clients do not specify valid work modes. T-Server previously hard-coded these values, which remain the default values for three new configuration options:

  default-work-mode-login
  Specifies the default work mode for TAgentLogin requests.
  Default: aux-work
  Valid values: after-call-work, auto-in, aux-work, manual-in
  Changes take effect: immediately
  
  default-work-mode-ready
  Specifies the default work mode for TAgentReady requests.
  Default: auto-in
  Valid values: auto-in, manual-in
  Changes take effect: immediately
  
  default-work-mode-notready
  Specifies the default work mode for TAgentNotReady requests.
  Default: aux-work
  Valid values: after-call-work, aux-work
  Changes take effect: immediately
  

  (TS-10762, TS-10574)

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.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

• This release adds support for Windows Server 2012, in 64-bit native and compatibility modes. (TS-10725)

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.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer creates an incorrect mapping between UCID (Universal Call ID) and internal call objects for transfer and conference calls when the switch reports a transfer or a conference call with a UCID persisting from the consultation call. Previously, such an incorrect mapping could cause the flexible call matching call overflow (COF) feature to fail in some call scenarios. (TS-10560)

This release is built with TSCP 8.1.001.74, which contains the correction of issues fixed in 8.1.3 Framework libraries. (TS-10716)

T-Server now correctly maintains User Data propagation after successful DNIS-pooling transactions to load-balanced destinations. Previously, User Data propagation could fail after such transactions. (TS-10675)

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

• Support for the Linux operating system was added November 22, 2013.

Corrections and Modifications

This release includes the following correction and modification:

T-Server now correctly handles UCID (Universal Call ID) propagation between internal call objects for transfer and conference calls. Previously, T-Server did not correctly update the original call's UCID when the switch reported a transfer or a conference call with a UCID persisting from the consultation call. This issue could result in call overflow (COF) failing in some call scenarios. (TS-10533)

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

• Support for the AIX, Solaris, and Linux operating systems was added September 6, 2013.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now distributes EventCallDeleted and EventEstablished messages in the proper order. Previously, in blind transfer scenarios to a DN with auto-answer enabled, T-Server postponed the propagation of EventCallDeleted events for approximately 15-30 milliseconds (ms), which could cause this event to arrive after the EventEstablished event during the completion of the transfer. (TS-10116)

T-Server now improves the handling of predictive calling. Previously, in scenarios involving predictive calls, T-Server could incorrectly process a predictive call request, where the resulting destination agent DN (from a previous predictive call) is incorrectly configured in the configuration environment. (TS-10112)

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 contains the following new features or functionality:

• T-Server now supports the restricted process-monitor-interval option that configures the time interval in which T-Server prints the object instance statistics for selected T-Server objects. This functionality can help diagnose abnormal memory growth problems in T-Server. This option is set in the gctm section.

  process-monitor-interval
  Default Value: 0 (zero)
  Valid Values: Any positive integer ranging from 1000—3600000
  Changes Take Effect: Immediately

  Specifies the time interval (in milliseconds) in which T-Server prints the object instance statistics for selected T-Server objects, if this option is set to a value greater than (>) or equal (=) to 1000. A value of 0 (zero) means that this option is disabled.

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

  (ER# 302409641, TS-502)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer terminates unexpectedly if the destination T-Server in an ISCC transaction receives two or more events propagated by ISCC followed by ISCCEventCallDeleted while the transaction is still in progress. Previously, T-Server could loop, using 100% of the CPU and triggering an Out of Memory error. (ER# 323648027, TS-864)

T-Server now correctly specifies either a positive integer or a null value for the EventServerInfo event's Extensions attribute, sdn-licenses-available. Previously, T-Server distributed a negative integer value for the number of available SDN licenses in this Extensions attribute for certain types of license files. (ER# 320403474, TS-833)

T-Server now correctly deletes old log files according to the value set in the expire option setting. Previously, when the number of files to be deleted exceeded that internal limit, some older files were not deleted. (ER# 316865205, TS-760)

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.55. 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 can now disable the reading of hosts files. To disable the reading of these hosts files, set the GCTI_DNS_USE_HOSTSFILE environment variable to 0 (zero). (ER# 309979773)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly handles certain scenarios using the Agent No Answer Supervision feature by ensuring that only valid Extensions attribute information for TRouteCall requests overrides the default Agent No Answer Supervisor configuration information for a call. Previously, in scenarios where the Agent No Answer Supervision feature was enabled in the configuration environment and a TRouteCall request was sent with unrelated Extensions attribute information, it was possible that this information could cause T-Server to overwrite the default Agent No Answer Supervision information for the call, disabling this feature. (ER# 314894837)

T-Server now correctly processes a TMuteTransfer request to a remote location, if the destination switch delays the distribution of CTI messages. Previously, T-Server did not correctly process such requests, which sometimes led to incorrect call reporting. For correct call processing, ensure that the epp-tout configuration option is set to a non-zero value. (ER# 266258691)

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now allocates enough buffer room to hold the maximum amount of Device, Media, Call Control (DMCC) messages, when the DMCC link is enabled. Previously, a problem for DMCC-enabled T-Servers that happened primarily at startup caused the DMCC link to drop and reset within T-Server. (ER# 310909489)

T-Server now correctly handles a stability problem, which impacts T-Server’s functionality when the value for the restricted route-thru-queue-ssfix configuration option is set to true. Previously in some scenarios, if the route-thru-queue-ssfix option was enabled, the TRouteCall request failed and an EventError message was returned, which caused T-Server to become unstable. (ER# 307715011)

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 correction and modification:

T-Server now includes the ConnID attribute in the EventAddressInfo event in response to a TQueryAddress (AddressInfoCallsQuery) request for the active call on the DN. In addition, T-Server now includes the PreviousConnID attribute in the EventAddressInfo event in response to a TQueryAddress (AddressInfoCallsQuery) request when there is a consultation call on the DN. Previously in these scenarios, T-Server would omit these attributes in the EventAddressInfo event. (ER# 305692323)

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 is built with the TSCP that corrects the following issue of this T-Server:

T-Server now has improved handling of Inter Service Call Control (ISCC) transactions. Previously, delays in the processing of ISCC transactions increased as the number of DNs in the configuration environment grew. (ER# 303893150)

T-Server now has improved high-availability (HA) switchover performance. During a CTI-link disconnect, T-Server generates an EventLinkDisconnected event before starting the cleanup of internal resources . Previously, this resource cleanup could occur before an EventLinkDisconnected event was generated, which could potentially slow down an HA switchover. (ER# 303326710)

T-Server is built with the TSCP that corrects the following issue of this T-Server:

T-Server now correctly addresses an issue in the build process. Previously, T-Server could become unstable due to previous builds using non-thread-safe libraries. (ER# 300463099)

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.45. 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 encodes TMakeCall requests containing large amounts of uui data. Previously, when these requests were incorrectly encoded, it resulted in an error response from the switch. (ER# 302741249)

T-Server now correctly routes calls in multi-site call scenarios. Previously, in some multi-site call flows, T-Server did not properly route a call from one site to another and then back again to Avaya Communication Manager. (ER# 300110009)

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

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

• The default value for the asai-protocol-version configuration option has been modified. T-Server now supports the default value of 4. (ER# 297157986)

• T-Server now supports the restricted configuration option abort-route which provides T-Server with the ability to terminate outstanding route request associations. This option is set in the TServer section.

  abort-route
  Default Value: never
  Valid Values: never, on-unmonitored-route, on-out-of-service, all
  Changes Take Effect: Immediately

  Ensures that outstanding route requests can be terminated in scenarios where T-Server cannot process the route request. If this option is set to never, T-Server will not terminate outstanding route requests in cases of unmonitored or out-of-service Routing Points. If this option is set to on-unmonitored-route, T-Server terminates outstanding route request associations in scenarios where the Routing Point is not monitored, or if it becomes unmonitored. If this option is set to on-out-of-service, T-Server terminates outstanding route request associations for any parties whose Routing Points become out-of-service. If this option is set to all, T-Server includes both of the on-unmonitored-route and on-out-of-service values.

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

  (ER# 295593129)

• T-Server now supports the restricted configuration option clear-calls-on-register to ensure that the EventReleased and EventAbandoned messages are generated under the following conditions:

  1. A DN is in an out-of-service condition.
  2. A party on this out-of-service DN is cleared by T-Server.

  This option is set in the TServer section of the T-Server Application object.

  clear-calls-on-register
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately

  Ensures that the EventReleased and EventAbandoned messages are generated when a party on an out-of-service DN is cleared. If this option is set to true, T-Server generates the EventReleased and EventAbandoned messages when a party is cleared. If this option is set to false, T-Server does not generate the EventReleased and EventAbandoned messages when a party is cleared.

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

  (ER# 294918870)

Corrections and Modifications

This release includes the following corrections and modifications:

This version of T-Server addresses a problem, which resulted in the omission of T-Events on the Vector Directory Number (VDN) when a call passed through a VDN to an unmonitored automatic call distribution (ACD) Queue. Previously, T-Server did not properly support an unmonitored ACD Queue in this call flow. (ER# 297042900)

T-Server now prevents existing call data (originating from a stuck call) from being incorrectly associated with any new calls that are initiated by T-Server. Previously, T-Server sometimes incorrectly associated old call data with a newly initiated call. (ER# 296855744)

T-Server is built with the TSCP that corrects the following issue of this T-Server:

In checking whether a digit string falls within the DN Range of the Switch configuration object that is defined in the configuration environment, T-Server now takes the length of the digit string into account. Previously, a simple lexicographic comparison was used that could produce false positive results for digit strings longer than the ones defining the DN Range.

Note: To ensure the correct CallType classification for calls involving unmonitored internal DNs, the DN Range field of the Switch configuration object for an Avaya Communication Manager switch can be used to specify the DNs that are not part of the Genesys environment, but are still considered internal. All unmonitored local DNs should be configured as a DN Range in Configuration Manager to ensure the correct CallType classification for such calls. Since this method of call type determination is not always reliable, Genesys strongly recommends that all local DNs that are used in calls be explicitly configured in Configuration Manager.

(ER# 282838050)

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.40. 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 is built with the TSCP that corrects the following issue of this T-Server:

• In multi-site scenarios involving the pullback ISCC transaction type, T-Server now distributes EventCallDeleted and EventAbandoned in the correct order in scenarios where the transaction expires at the origination site due to the call having already ended at the destination location of the transaction. (ER# 297522212)

• In multi-site scenarios involving the pullback ISCC transaction type, T-Server now correctly distributes the EventDiverted, EventReleased (on the abstract DN), and EventCallDeleted messages in the proper order. Previously, T-Server distributed EventReleased on the abstract DN and EventCallDeleted to clients earlier than EventDiverted. This resulted in inaccurate historical call reporting. (ER# 296811795)

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# 289977631)

• 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 restricted option serialize-predictive-calls to true.

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

  When set to true, T-Server serializes all TMakePredictiveCall requests for a particular DN: it sends a subsequent request to the switch only after receiving a response to the previous request. When set to false, T-Server does not serialize TMakePredictiveCall requests.

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

  (ER# 289729847)

• This version of T-Server enhances support of the DropCRV feature (currently documented in the Deployment Guide for this T-Server). It is now possible to drop any Call Reference Value (CRV). To perform a "force drop" on any CRV with the link, a T-Client should send a TRegisterAddress request (on any DN) with an integer key value equal to the CRV that should be dropped included in the extensions data of the request. T-Server uses 2-byte CRVs. For T-Server side CRVs, the high-order bit of the CRV should be cleared. For switch side CRVs (routes), the high bit-order bit of the CRV should be set. (ER# 276683009)

• A 64-bit T-Server build is now supported on 64-bit Windows Server 2008.

• T-Server is now supported on Linux 6 32- and 64-bit platforms. A native 64-bit T-Server executable is now included in the Linux package and is supported on 64-bit Linux 5 and Linux 6 platforms.

• 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 supports the route-thru-queue-ssfix configuration option.

route-thru-queue-ssfix
Default Value: false
Valid Values: false, true
Changes Take Effect: Immediately

When this option is set to true, if a call is routed to the DN of an agent who is logged in and ready while the route-thru-queue option is enabled, the EventRouteUsed message is delayed by 500 milliseconds and the ThirdPartyDN attribute is set to the agent DN instead of the automatic call distribution (ACD) queue. This results in the EventRouteUsed message being distributed after the EventRinging message for the agent.

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

T-Server is built with the TSCP that corrects the following issue of this T-Server:

T-Server no longer provides an incorrect access number for an External Routing Point after Access Codes have been modified at a remote switch. (ER# 281432690, 281406151)

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:

T-Server no longer delays processing of the TP_CallEnded switch message containing the Cause attribute set to C_NORMAL_UNSPECIF. Previously, this delay sometimes led to an incorrect call model flow for call scenarios involving ISCC/COF with switch configurations involving the Lookahead Interflow feature. (ER# 285630101)

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer generates an EventPartyChanged message on a Routing Point during routing call flows involving an external party disconnect. Previously, in some routing call flows, if RouteEnd was followed by an external party disconnect, T-Server could incorrectly identify the call flow as a Single-Step Transfer. T-Server now correctly identifies the call flow as a routing call flow and no longer generates an incorrect EventPartyChanged message. (ER# 280315474)

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, 278820171)

In rare scenarios, involving dynamic update of Host objects in the configuration environment, T-Server could become unstable. (ER# 278117022)

T-Server no longer becomes unstable if it receives corrupt messages over the CTI link. (ER# 276247878)

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 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 Avaya Communication Manager.

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

  • heartbeat-period
  • hangup-restart

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

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

• 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 Communication Manager Deployment Guide for details. (ER# 270335740)
• T-Server adds support for HA synchronization of Agent Ready/Agent Not Ready work modes from a primary T-Server to its backup. (ER# 272149422)

Corrections and Modifications

This release includes the following corrections and modifications:

This version of T-Server addresses a problem which can result in a stuck call in call flows where a call is pending deletion by timer in T-Server and the result of a call query reports the call active on the switch. The reported active call cancels the delete timer and the timer is not subsequently reset (when the call in T-Server is in the abandoned state). This version corrects this problem by restarting the timer for this case, ensuring the call will be later deleted. (ER# 267343511, 259860017)

This version of T-Server addresses a problem with coverage scenarios which could previously cause T-Server to interpret redirect notification of the principle station as a drop of both the principle and covering station, resulting in incorrect T-Event generation. (ER# 214050931, 229367441, 268525765)

T-Server no longer becomes unstable while processing ISCC call overflow transactions that involve previously deleted calls. (ER# 262158051, 262218732)

When the call release tracking feature is enabled, T-Server now correctly reports AttributeCtrlParty in EventCallPartyDeleted for the releasing party controller and in EventCallPartyDeleted for the noncontroller parties dropping from the call. (ER# 260578641)

Previously, T-Server only considered VDNs configured as Routing Points, when adding AttributeOtherQueue on supported call events when the vdn-as-other-queue configuration option was set to true. This version of T-Server extends the functionality around 7.2 backwards compatibility option vdn-as-other-queue, to include VDNs configured as ACD Queues (with the switch-specific type 2). (ER# 269670623)

This version of T-Server addresses a potential stability issue which has been found to occur in some call scenarios involving parties which were improperly configured in the configuration environment. (An Extension DN was configured as a Routing Point DN). (ER# 269850165)

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.

In some 4-party conference call flows, T-Server ignores the disconnect message from the PBX when the external party releases from the conference. (TS-11958)

T-Server for Avaya Communication Manager 8.1.500.14 and later requires FlexNet Publisher License Manager version 11.13+. (TS-11853)

To ensure the correct CallType classification for calls involving unmonitored internal DNs, the DN Range field of the Switch configuration object for an Avaya Communication Manager switch can be used to specify the DNs that are not part of the Genesys environment, but are still considered internal. All unmonitored local DNs should be configured as a DN Range in Configuration Manager to ensure the correct CallType classification for such calls. Since this method of call type determination is not always reliable, Genesys strongly recommends that all local DNs that are used in calls be explicitly configured in Configuration Manager.

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.

RequestCancelReqGetAccessnumber is not supported and returns an error. (TS-10974)

T-Server maintains an incorrect mapping between UCID (Universal Call ID) and internal call objects for transfer and conference calls when the switch reports a transfer or a conference call with a UCID persisting from the consultation call. This mapping is used by the flexible call matching call overflow (COF) feature and causes it to fail in some call scenarios. (TS-10560)

Using the Ctrl-C key combination to stop T-Server when it was started from a batch file, leads to a Windows error message on the Microsoft Windows operating system. (ER# 303502951)

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)

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)

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)

There is a slight behavior change in the generation of T-Events for agent logout between 7.2 and 7.5 T-Server. Starting with 7.5, T-Server will report the reference ID, and any associated reasons, in the EventQueueLogout message, rather than EventAgentLogout. (ER# 221411083)

Some call parking scenarios may result in the loss of call visibility in T-Server, causing possible call deletion when calls are parked, as well as new call creation (and deletion of UserData) when calls are unparked. (ER# 193692091 )

When T-Server starts, if a phone is already in a dialing state, it will be incorrectly reported by T-Server as in Established state. This problem only occurs on startup and is temporary. It will be resolved when the dialing DN is either released or established. (ER# 150380481)

When a backup T-Server becomes primary, it will send agent status queries in the background for all agents that are logged 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 AIX 6.1 operating system is no longer supported.

The Solaris 9 operating system is no longer supported.

The Windows 2003 operating system is no longer supported.

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

The Solaris 8 operating system is no longer supported.

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

The Tru64 UNIX operating system is no longer supported.

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

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys 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 Communication Manager Deployment Guide contains detailed reference information for the Genesys Framework 8.1 T-Server for Avaya Communication Manager 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. To determine the version of a document, check the version number that is located on the second page in PDFs.

Top of Page