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

This release note applies to all 8.0 releases of T-Server for Alcatel A4400/OXE.

• 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 Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• 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.0.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 functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.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 section describes new features that were introduced in this release of T-Server.

• Support for Alcatel A4400/OXE switch release 10. (ER# 267333437)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly handles an agent logging into a pre-assigned state. Previously, T-Server incorrectly reported an EventAgentLogout event when an agent logged in with a pre-assigned state, and the PBX timer number 238 was set to a value greater than 11. (ER# 261524426)

T-Server now correctly unlocks a call on a device and releases it from memory in scenarios where a new account code handling is activated, and the account code is entered on the device, or times out on the PBX. Previously, T-Server sometimes left the call in memory until new activity occurred on the device. (ER# 266018801)

T-Server now correctly handles scenarios involving monitored multiline devices if the PBX does not report events for those devices after the previous call is disconnected, and a work-related call is initiated manually from another agent. Previously, T-Server might have created an origination party on the device the call initiated from, and generated an EventOffHook event, which left the device in an off hook state until the PBX reported a new call on that device. (ER# 264540557)

T-Server now correctly reports the GCTI_NETWORK_TIMESLOT extension in the EventNetworkReached event and consecutive events for outbound calls. Previously, T-Server added this extension to the party only after generating the event, so the extension was only reported in the EventReleased event. (ER# 266532382)

T-Server now reports the User Data key GCTI_CSTA_CORRELATOR in a manner compatible with reporting, and as used by T-Server 7.6. Previously, T-Server did not remove the GCTI_MAGIC_ID key from User Data if it was used to construct correlator data and this correlator data was reported by the PBX. (ER# 268483473)

T-Server now correctly reports scenarios that involve call routing where an internal call is returned to an RSI, then routed to another RSI followed by the PBX reporting two deliveries of the call on the origination. Previously, T-Server might have failed to report the AttributeThisQueue in EventRinging when the call was routed from the second Routing Point. (ER# 268297134)

T-Server no longer fails if the PBX does not report a CallBack scenario on the monitored device that initiated the scenario. Previously, T-Server sometimes failed if the PBX reported events only on the monitored destination of a CallBack. (ER# 268535811)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.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 does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer unexpectedly terminates in scenarios involving incoming calls to a Routing Services Interface (RSI) device if the calling party is unknown (not provided by the carrier), regardless of the order in which the events were reported by the PBX for the routing scenario. Previously, T-Server might have terminated unexpectedly after a routed call is answered and transferred from the routed destination if the PBX reported the delivery of a routed call to the destination before a successful route was confirmed. (ER# 264476026)

T-Server now provides correct reporting for a TQueryAddress request on a RSI device. Previously, T-Server incorrectly returned information in the query response about calls that were already successfully routed while a treatment was applied. Query response no longer contains this information. (ER# 264104449)

Top of Page

Supported Operating Systems

New in This Release

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

There are no restrictions for this release. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly reports scenarios when the prd-dist-call-ans-time option is set to a value of 0 and a TMakePredictiveCall is requested from an emulated Routing Point. Previously, T-Server might have incorrectly reported EventDiverted depending on the order of the events received from the PBX when the call transfer was completed on a predictive dialer, and the call was in a routable state. (ER# 26230411)

T-Server now correctly handles scenarios where a TMakePredictiveCall is requested from an RSI then answered by a customer and routed when the following conditions apply:

1. The prd-dist-call-ans-time option is set to a value of 0.
2. The Supervised Transfer flag is set to True on the PBX.

Previously, T-Server failed to add AttributeThisQueue to the events generated by T-Server on the routed destination. (ER# 260478871)

T-Server now consistently reports predictive scenarios that are requested with the extension AnsMachine equal to the RSI device regardless of the state of the flag Supervised Transfer set for that device in the PBX. Previously, T-Server reported CallStateAnsweringMachineDetected in EventQueued on the requesting device and on the device from the request extension if the Supervised Transfer flag was set to True on the PBX for RSI device from the request extension. (ER# 260542647)

T-Server can now perform a TRouteCall from an RSI device to the same RSI device. Previously, T-Server rejected such request with an EventError. (ER# 260673621)

T-Server now correctly reports scenarios involving TRouteCall with a Reject or a Disconnect type when AttributeOtherDN is provided in the request. Previously, T-Server incorrectly reported EventRouteUsed and EventDiverted with the AttributeThirdPartyDN equal to AttributeOtherDN from the request. (ER# 262062449)

T-Server now correctly reports a scenario where a transferred event on a destination party is reported earlier by the PBX than on the transferring device when a TCompleteTransfer or a TMuteTransfer is performed. Previously, T-Server might have reported EventReleased without AttributeOtherDN on the transferring device for the party of the consultation call in this scenario. (ER# 262114431)

T-Server now correctly reports scenarios that involve call routing where the call is returned to an RSI when there is no answer on the first routed destination. Previously, T-Server failed to report the AttributeThisQueue in EventRinging when the call was routed a second time. (ER# 262904092)

T-Server now correctly unlocks a call in scenarios where new account code handling is activated in T-Server and the account code is entered on a device, or the account code activation times out on the PBX. Previously, T-Server might have left a call, locked at the start of ACW phase, in memory until new activity occurred on the device. (ER# 261993057)

T-Server now correctly reports a scenario where an agent in the not-ready state receives or initiates a business call, and the call is established and released. Previously, T-Server reported three EventAgentNotReady events on the call release if agent ACW synchronization was activated (when the sync-emu-acw option is set to true). (ER# 262335391)

Top of Page

Supported Operating Systems

New in This Release

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

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

• T-Server now supports the Standard Account Code feature, which allows the account code to be added to the GCDR table in Call Concentrator after the call has been released from the device; this allows T-Server to report a call release when the conversation is finished, instead of waiting for the account code to be entered, thus resulting in correct call duration reporting. T-Server uses two new configuration options to enable this feature:
  
  acw-retain-call
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately
  
  This option instructs T-Server to retain the last agent business call while the agent is in an After-Call Work (ACW) period and allows user data updates to be added after the call has been released. This allows the account code to be attached to the previous call. When set to true, T-Server sends the account code in the EventUserEvent message, rather than the EventAttachedDataChanged message, to avoid confusing existing desktop applications.
  
  acw-retain-lock
  Default Value: 0
  Valid Values: Any positive integer
  Changes Take Effect: Immediately
  
  This option specifies the period of time, in seconds, for the call to remain locked in Call Concentrator after the call has been released. When this option is enabled, T-Server sends EventUserEvent with the key LockCall in AttributeExtensions and the value set by the option. Typically, this value should be greater than the ACW value.
  
  Note: To enable the Standard Account Code functionality in T-Server, both of these options must be enabled. In addition, the acw-retain-lock option must be set to a value equal to, or greater than, the value set on the PBX for the Account Code timeout. For further information on Call Locking, refer to the Call Concentrator 7 Reference Manual.
  

  (ER# 245565561)

• T-Server now supports enhanced ISCC/COF flexible call matching. (ER# 241920125)

• T-Server will now report a new key PBXTimeStampS in AttributeExtensions that corresponds to the PBX UTC time in seconds, if such information is provided by the PBX. (ER# 214052694)

• T-Server will now report information regarding Calling Line Name in respective events in a key CallerID of AttributeExtensions if such information is provided by the PBX. (ER# 213914945)

• T-Server has been modified to suppress reporting of call routing events in the scenario, where the OXE VAD feature is used for outbound dialing and Outbound Contact Server (OCS) is configured to request T-Server to automatically overflow calls detected as Fax and/or Answering Machine to another destination. Previously, T-Server reported an EventRouteRequest message followed immediately by EventRouteUsed when a Routing Point was used as the origination DN. This caused URS to immediately attempt to distribute this call which would fail as T-Server would be handling the overflow to the requested destination and therefore rejecting any routing requests for such calls. (ER# 251400948, 248435481)

• T-Server now supports configuring DNs of type Route Queue in the Configuration Layer. (ER# 245565584)

• T-Server now supports a new LMS event that will be generated if T-Server does not enable routing capabilities on a routing device:

  36104|STANDARD|GCTI_RQM_004|Device [device] route register failed, error code [error code]([error code string])

  Where:

  • [device] is the device in which the requested enablement of routing capabilities is rejected by the PBX
  • [error code] is the error code provided by the PBX
  • [error code string] is the corresponding error code string provided by the PBX

  (ER# 244550410)

• T-Server will now report a CallPickup key in AttributeExtensions with the value of the pickup device number, if the value is provided by the PBX; otherwise it puts the value unknown in the EventReleased message if the message is generated as a result of call pickup. (ER# 234702846)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly reconnects to the PBX when the PBX CPU is restarted. Previously in this scenario, T-Server sometimes stuck in a non-connected state, with T-Server connected to the PBX and the client connection generating an EventLinkDisconnected message. (ER# 253373088)

T-Server no longer reports the ANI attribute in call-monitoring events if the ani-distribution configuration option is set to suppressed. (ER# 249855060)

T-Server now retries the action defined in the no-answer-action option for an agent if the first attempt is rejected by the PBX. (ER# 247921247)

T-Server now correctly handles Routing Services Interface (RSI) registration in a high-availability (HA) environment. Previously, T-Server sometimes incorrectly re-registered the RSI mode during consecutive switchovers, causing the current primary T-Server to not receive events for RSI devices. (ER# 255103895)

T-Server now correctly reports the agent state after a call where race conditions for changing the agent state could be observed. Previously, T-Server did not report the proper agent state after the call was released, leaving the agent state desynchronized with the PBX. For example, the agent was reported in a Ready state while actually in a NotReady state due to ACW. (ER# 253404351)

T-Server now correctly handles scenarios where a call is made to an ABCF (Alcatel internal network) destination, returns back to RSI, is routed to another RSI, and finally to an agent. Previously, T-Server did not execute the No-Answer Supervision feature because of lost call information related to the last distribution point where routing occurred due to late reporting on the origination of the call. (ER# 255907194)

T-Server again supports Delete From Conference Using Requesting Device functionality. In versions 8.0.001.00 to 8.0.002.19, this functionality was disabled. (ER# 258945691)

The Default Values for the following T-Server options have been modified to the following:

• min-xfer-init-dly=500
• min-xfer-complete-dly=250
  

T-Server now correctly handles the scenario where the PBX acknowledges an initiation of the consultation call followed by clearance of the call. Previously, T-Server did not handle this scenario properly, which sometimes resulted in a stuck call in T-Server memory. (ER# 254438511)

T-Server now correctly reports a device as being out-of-service in the following scenario: T-Server is running in agent-substitution mode with smart monitoring enabled, a physical phone is connected with a real agent logged in, the set is then disconnected, and the real agent is logged out. Previously in this scenario, T-Server incorrectly reported the device as being in-service while it was reported as out-of-service by the PBX. (ER# 253297411)

T-Server now correctly processes a scenario where an agent transfers an inbound call back to the non-supervised RSI. Previously in this scenario, T-Server sometimes deleted a party and a call because of race conditions, thus losing attached user data. (ER# 258196218)

T-Server now correctly handles a TPrivateService request execution. Previously, T-Server sometimes became unstable if TPrivateService was executed and later an established business call released on an agent with After Call Work synchronization enabled. (ER# 256064255)

T-Server no longer generates multiple EventPartyChanged messages in scenarios involving calls transferred either between PBX nodes or between monitored and unmonitored devices. (ER# 255608162)

T-Server now correctly handles a situation where an access resource with the same name as an existing DN is added. Previously, this caused T-Server to incorrectly report the existing DN as out of service. (ER# 254061622)

T-Server now correctly reports a role of the device party in consecutive events if the TSingleStepTransfer request is executed to an invalid or unavailable destination. Previously, T-Server incorrectly reported the TransferredBy role for such a device. (ER# 245144097)

T-Server is now able to dynamically update the Register property in the device configuration in the Configuration Layer. Previously, when the Register property in the device was changed to false, T-Server incorrectly placed the device out of service if the change happened when T-Server was run. (ER# 215015703)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.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 does not contain any new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

Rapid call overflow between partitions that are processed by ISCC/COF no longer leads to stuck calls. (ER# 257308716)

Top of Page

Supported Operating Systems

New in This Release

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

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

• T-Server now supports the wait-delivered option, which specifies the period of time T-Server waits for a Delivered event from the switch when emulated service involving a transfer phase is executed. T-Server will execute the second step of emulated service either when the switch reports the event Delivered or when the configured delay expires.
  
  wait-delivered
  Default Value: 60000
  Valid Values: 0-60000
  Changes Take Effect: Immediately
  
  This option specifies the length of the time in milliseconds (initiated upon receiving the Originated or Network Reached event from the switch) that T-Server waits before proceeding to the next step in execution of emulated service that involves transfer completion.
  

  (ER# 252709213)

Corrections and Modifications

This release includes the following corrections and modifications:

Upon receiving an event Delivered from the switch, T-Server now correctly executes the transfer phase of emulated services and completes the transfer after the delay configured using min-xfer-complete-dly expires. In previous 8.0 versions, T-Server did not apply the delay configured by option min-xfer-complete-dly. (ER# 252709213)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This section describes new features that were introduced in this release of T-Server for Alcatel A4400/OXE.

• The make-call-morph option is introduced with this version of T-Server.
  
  make-call-morph
  Default Value: default
  Valid Values:

  Value	Description
  default	Currently defined default behavior
  transfer	Initiate transfer
  conference	Initiate conference
  makecall	Sends a Make Call request to the switch (no morphing)
  reject	Reject the request immediately without sending it to the switch

  Changes Take Effect: Immediately
  
  This option allows T-Server to send a Make Call request correction type to the switch when a device is already on a call.
  

  (ER# 249738979)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now reduces unnecessary traffic generated between T-Servers when backup and primary T-Servers lose agent state or device state synchronization. Previously, updates between primary and backup T-Servers may have generated a large amount of traffic until the device and agent states were synchronized. (ER# 251258049)

T-Server now correctly processes a treatment, requested for a consultation call on a Routing Services Interface (RSI) coming from an ABCF trunk (inter PBX network), when a call transfer is completed on the other node. Previously, T-Server did not complete the ongoing treatment, and as a result, did not continue the operation with the new treatment that was requested for the transferred call. (ER# 251239011)

T-Server now prevents possible failures that are observed when T-Server is shutdown before the PBX can respond to a request for connection closure. (ER# 251258041)

T-Server now correctly processes the execution of TSingleStepTransfer or TMuteTransfer to an external destination when the call reaches the network, but is not delivered within 60 seconds. Previously, T-Server attempted the transfer completion to a non-delivered destination on the expiration of the timeout, which was set to a value of 500 milliseconds. This could have resulted in a failed transfer completion (depending on the telephony provider). (ER# 248833547)

T-Server now correctly handles a request for RequestAgentNotReady when a device has a ringing call. T-Server may have become unstable in this scenario. (ER# 248881333)

As a workaround, T-Server now correctly handles the following PBX reporting scenario: a call is made to a PBX SIP interface, and it is returned to the RSI with different reported properties which incorrectly identify the call as being new and internal. Previously, T-Server may have become unstable during this scenario or at a later time when an agent performed a login or a logout on the device from which the call originated. (ER# 249078553)

T-Server now correctly identifies a device as being off-hook on a restart if a PBX snapshot returns an unknown call on the device without properties, or if optimized monitoring returns a busy state. Previously, T-Server reported the device as being in a on-hook state in this scenario. (ER# 248111362)

T-Server now correctly handles self-transition agent state changes. This includes situations where an agent state is desynchronized between T-Server and the PBX. Previously, T-Server may have reported an EventError when attempts to set the agent state resulted in only an acknowledgement from the PBX. (ER# 249738968)

T-Server now prevents an SCI alarm from being generated when a request to update or attach user data is not followed by an update to this user data on the PBX. Previously, T-Server generated alarm 36002: Request rejected: error code ... in these user data update scenarios. (ER# 248543355)

T-Server now correctly reports scenarios involving agent monitoring from a non-monitored supervisor. Previously, T-Server ignored events from the PBX, and did not generate events for these scenarios. (ER# 250868821)

T-Server now correctly handles predictive scenarios to busy destinations where the PBX cleans failed calls immediately. Previously, T-Server may have become unstable in such scenarios. (ER# 249459876)

T-Server now correctly identifies a call which allows it to process the private event Calling Line Identity (this functionality was incorrectly changed in version 8.0.002.12). Previously, T-Server ignored this event. (ER# 249738970)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now reports a result of CallStateSitNocircuit in a TMakePredictiveCall when a call is disconnected by the network before call it is delivered to its destination. Previously, T-Server reported CallStateRemoteRelease in this scenario. (ER# 248360845)

T-Server no longer becomes possibly unstable after the deletion of a device within Configuration Manager. (ER# 248360843)

T-Server now correctly reports scenarios where the transfer of an external call to an outbound destination is completed too quickly (before the call is delivered to the outbound destination). Previously in this scenario, T-Server may have had a stuck call without parties in its memory that could not be cleared. (ER# 248132248)

When the T-Server option agent-substitute is set to true and a native agent logs out on a ProACD device that is configured in Configuration Manager with the register flag set to false, T-Server could previously stop generating EventOnHook/EventOffHook in some situations. T-Server will now provide correct reporting in these situations. (ER# 247613278)

When the T-Server option agent-substitute is set to true, T-Server no longer becomes unstable when an agent device (ACD Position) corresponding to a logged in agent is deleted from Configuration Manager and a subsequent agent state change is requested. (ER# 248305489)

T-Server now correctly reports scenarios where the PBX omits the delivery of events for a CCD Pilot device when the PBX is under a heavy usage. Previously in this scenario, T-Server could have become unstable. (ER# 248305486)

T-Server now correctly completes the handling of TApplyTreatment (TreatmentPlayAnnouncementAndDigits) requests. Previously, T-Server did not remove from memory all data, associated with the execution of these requests, which lead to a potential increase in memory usage. (ER# 248423063)

T-Server, in a high-availability (HA) environment, now correctly handles synchronization between the primary and backup T-Server in predictive scenarios where synchronization updates arrive at the backup T-Server after the PBX has already initiated the call, and reported it to the backup T-Server. Previously, the backup T-Sever could become unstable as a consequence of incorrectly handling this synchronization scenario. (ER# 247468567)

This version of T-Server is built with the latest TSCP version. It corrects an ISCC issue where T-Server may have become unstable. See T-Server Common Part release 8.0.x for more information. (ER# 248415967)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server, in a high-availability (HA) environment, now correctly handles synchronization between the primary and backup T-Server in predictive scenarios where synchronization updates arrive at the backup T-Server after the PBX has already initiated the call, and reported it to the backup T-Server. Previously, T-Sever could become unstable as a consequence of incorrectly handling this synchronization scenario. (ER# 247468567)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server, in a high-availability (HA) environment, now correctly handles synchronization between primary and backup T-Server in scenarios where a consultation call from an ABCF trunk is transferred to a Routing Services Interface (RSI). Previously, T-Sever could become unstable as a consequence of incorrectly handling synchronization scenarios. (ER# 246965544)

T-Server now correctly handles scenarios where a native agent logs out while a ProACD device is off-hook by correctly synchronizing the device hook state with the PBX. (ER# 246973461)

T-Server now correctly handles scenarios where the PBX reports a new call with the same Call ID as a previous call that was previously queued, but the PBX did not generate any subsequent reporting for that previous call. T-Server, now clears this stuck Call ID, and correctly processes the subsequent call with the same Call ID. Previously, the scenario prevented T-Server from correctly handling the new call with the same Call ID. (ER# 247209748)

T-Server now correctly updates the status of dialer resources (VAD) used for predictive dialing scenarios in the backup T-Server in a high-availability (HA) environment. Previously, the backup T-Server could have left dialer resources marked as unavailable for calls at the end of predictive dialing scenarios due to incorrect handling of HA synchronization. As a result, after a switchover, the new primary T-Server used a reduced set of dialing resources. (ER# 247269193)

T-Server now correctly handles multiple initiated calls on a multiline agent device. Previously, T-Server incorrectly selected the first found initiated consultation call instead of another initiated call, which led to incorrect reporting in the subsequent events. (ER# 247283831)

T-Server now correctly selects the dialing resource if two TMakePredictiveCall requests occur simultaneously. Previously, T-Server could select the same dialing resource which would have led to a failure of the primary and backup T-Servers. This failure would occur if the second TMakePredictiveCall request was sent in the period of time between the acknowledgement of the first request arriving from the PBX and the arrival of the first events of the scenario. (ER# 246386588)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly reports scenarios where request extensions are pointed to a non-supervised Routing Services Interface (RSI). Previously, T-Server produced an incorrect report in predictive scenarios if the TMakePredictiveCall request had the extensions VoiceDest and/or AnsMachine pointing to a non-supervised RSI and the corresponding dialing results received from the PBX. When a predictive call progress resulted in the use of such non-supervised RSI from an extension, T-Server did not report the EventQueued event for the requesting device. T-Server also did not attach the user data key AnswerClass to EventQueued if the destination of the predictive call was an answering machine.

There are no issues when request extensions are pointed to supervised RSI, emulated Routing Points, or any type of ACD Pilots.

(ER# 246496530)

T-Server now correctly processes the logout of native agents when the agent-smart-monitor option is set to true or strict and the snapshot-on-start option is set to true. Previously, T-Server incorrectly executed the smart monitoring feature, and therefore did not request a device snapshot in order to get a synchronized state of the device. (ER# 246624211)

T-Server now correctly reports CallStateRemoteReleased in an EventReleased event when the network releases a predictive call without providing any cause. This is opposite to a scenario where a predictive call is released with CallStateNoAnswer when the network provides a cause. Previously, T-Server did not correctly report a scenario involving remote disconnection of an unanswered predictive call. (ER# 246624268)

T-Server now correctly adds the AttributeReferenceID and AttributeReason attributes to the EventAgentLogin event when a RequestAgentLogin is requested for a native agent. (ER# 245784714)

T-Server now correctly retrieves the request extension ReasonCode and sends it in requests made to the PBX. Previously, T-Server did not correctly retrieve extensions from the TAgentNotReady request, and therefore did not form a correct request to the PBX. (ER# 246657268)

T-Server now correctly processes synchronization updates from the primary T-Server. T-Server in HA mode ignores synchronization updates if there is a pending agent login, and will wait until the login timer expires. Previously, T-Server in backup mode incorrectly processed updates from the primary T-Server when a native agent was logged in. Synchronization updates canceled pending agent logins and prevented backup T-Server from correctly logging in agents. (ER# 246831561)

T-Server now attempts to synchronize again synchronization attempts that have failed. Previously, when the sync-emu-acw option was set to true, T-Server did not attempt to resynchronize emulated and PBX agent states when the initial synchronization attempt failed. (ER# 246832198)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly reports a call state of not answered (7) if a predictive call is not answered and T-Server disconnects the call due to timeout. Previously, T-Server incorrectly reported a call state of dropped (26) when a predictive call was not answered within the time specified in the TMakePredictiveCall request. (ER# 245064986)

T-Server now reports collected digits only in EventDigitsCollected and EventTreatmentEnd events that are generated as a result of the TApplyTreatment request. Previously, T-Server incorrectly saved collected digits permanently, which resulted in the digits being reported in all subsequent events sent for the call. (ER# 245073927)

T-Server now adds the AttributeReferenceID and AttributeReason to the EventAgentLogin when a RequestAgentLogin request is sent for a native agent. (ER# 244848039)

Top of Page

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This section describes new features that were introduced in this release of T-Server for Alcatel A4400/OXE.

• T-Server now allows a Voice Activity Detection state to be set for a predictive call to support the following scenarios (when TMakePredictiveCall is requested):

  • If an answering machine is detected, T-Server will add the user data key AnswerClass = AM.
  • If a TMakePredictiveCall has an extension of AnsMachine (or VoiceDest) with the value that corresponds to a monitored Queue or Routing Point, T-Server will take the call from a requesting device, and place the call to the monitored Queue or Routing Point when the answering machine (or human voice) is detected. If the extension corresponds to a non-monitored object or to an object with a different type, T-Server will ignore the extension key.

  Note: This feature is supported for AM identification only when the Voice Activity Detection board is in use, and an emulated MakePredictiveCall is requested. The following limitations do apply:

  • The A4400 PBX at this moment disconnects calls connected to a Fax Machine.
  • The A4400 PBX has to be configured to not disconnect calls connected to an Answering Machine.
  • Predictive calls placed from non-VAD devices will be reported as human voice detected.
  • T-Server is unable to distinguish between VAD and virtual devices.

  (ER# 243219079)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server no longer attempts to reference objects that cannot be found. Previously, T-Server became unstable in this scenario. (ER# 243733761)

T-Server no longer suspends the registration of Extensions devices when they are the only devices defined in Configuration Manager. (ER# 243286184)

Top of Page

Supported Operating Systems

New in This Release

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

There are no restrictions for this release. This section describes new features that were introduced in this release of T-Server for Alcatel A4400/OXE.

• When a call is delivered to a device, and the PBX event has information regarding the calling party name, T-Server will add the GCTI_PARTY_NAME extension to the calling party properties, and GCTI_OTHER_DEVICE_NAME to the alerted party.
  

  When a call is delivered to a device, and the PBX event has information regarding the alerting party name, T-Server will add the GCTI_OTHER_DEVICE_NAME extension to the calling party properties, and GCTI_PARTY_NAME to the alerted party.

  When the private event Calling Party Name is reported by the PBX, the following scenarios apply:
  

  • If a party that is about to be updated does not have information in the GCTI_OTHER_DEVICE_NAME extension, or the information for the party is not identical, T-Server will generate EventPrivateInfo with the AttributePrivateMsgID set to 1008 along with information related to the party. If the information for the party is identical, no private event is generated.
  • If an Other party is found (defined by the originating Connection field), T-Server will check the GCTI_PARTY_NAME extension which is held for that party. If the extension value is different, T-Server will update the extension, but will only generate the event if that party is on a monitored device. If the extension is identical, T-Server will not generate an event for that party.

  (ER# 131319012)

• T-Server now allows users to redefine the call state T-Server will report in EventReleased in a TMakePredictiveCall scenario when the call fails or is dropped. Using Configuration Layer it is possible to define a mapping from the cause provided in the CSTA Connection Cleared event sent by the PBX to the call state provided by T-Server in EventReleased. Please contact Genesys Technical Support for more information. (ER# 219133744)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now uses the assigned Global Call ID to determine how a call is processed. T-Server no longer selects a call by Call ID. (ER# 236779088, 220686560)

The following Known Issues have been corrected in this release: ER# 235609411, 235448131, 235609418, 235609445, 235673214, 235719521, 235774109, 237463081. See the Known Issues and Recommendations section for details.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.001.15. 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.0 release of T-Server for Alcatel A4400/OXE.

• Support for call type prediction: On occasions when the CTI information is either insufficient or arrives too late for T-Server to assign a definite call type, T‑Server can now use a call type prediction procedure to assign call type based on configurable rules.

• Support for call release tracking: T-Server now provides information about which party initiated the release of a call. This can be valuable for different applications to provide historical and real-time call reporting. This can be configured using the new configuration option releasing-party-report.

• Support for failed route notification: T-Server now supports alarm messages for unsuccessful routing scenarios.

• Support for link bandwidth monitoring: T-Server now provides bandwidth monitoring on a CTI link and can notify the Genesys Management Layer when Configuration Layer limits are exceeded.

• Support for enhanced request handling: T-Server introduces two major new enhancements to queue handling: request conflict resolution and a new device queue.

• Enhancements to emulated agent functionality: The Emulated Agent feature has a number of enhancements, including:

  • Agent logout on client unregistering from a DN.
  • Changes to legal guard processing.
  • The addition of password functionality to agent-strict-id.
  • Synchronization of emulated after call work (ACW) for emulated agents.

• Enhancements to business call processing: A new configuration option, agent-only-private-calls, enables you to specify whether calls distributed from a device are considered as private or business calls.

• Support for Twin Telephone Sets has been implemented.

• T-Server now takes in consideration pro_ACD devices when an agent logs in: T-Server now uses the result of the query device information from the switch to determine whether devices are able to login real agents or not. If a device does not support a real agent login, T-Server will always login an emulated agent if a client issues RequestAgentLogin, regardless of any settings in Configuration Manager.

• Support for Alcatel A4400/OXE Partitioning.

• T-Server reporting of pre-assigned agent and supervisor login has been enhanced to ensure correct statistics are available to StatServer. T-Server introduces the new configuration option preassign-agent-compat to specify whether to provide backward-compatible reporting for preassigned agents. (ER# 36994883)

• Support for Private Data in Route Requests on RSI: Starting with release R9.0 of the PBX, new private data in ROUTE_SELECT allows additional information to be sent to OXE. T-Server introduces the new configuration option rsi-bypass-fwd-dnd for this feature.

• Enhancements for devices that can have multiple calls: A new configuration option, rel-cons-reconnect, enhances the way T-Server works with devices that can have multiple calls.

• Support for Keep-Alive feature: Allows T-Server to actively check a link’s integrity to detect link failure and initialize alarm and recovery procedures.

• Improvements to T-Server logging performance have been implemented.

• Support for new operating systems: The following new operating systems are supported:

  • IBM AIX 64-bit version 6.1.
  • HP-UX/PA 64-bit version 11i v3.
  • Red Hat Enterprise Linux AS Edition on 32-bit Intel platforms, version 5.0.
  • Windows 2008.
  • VMWare.
  • Sun Solaris Containers.
  • IBM PowerVM LPAR.

Corrections and Modifications

This release includes the following corrections and modifications that were made between release 7.6 or earlier releases and the initial 8.0 release:

T-Server no longer becomes unstable because of memory allocation issues on AIX 5.3. (ER# 167162375)

Backup T-Server no longer deletes calls initiated due to execution of TMakePredictiveCall in primary T-Server (ER# 230371994)

T-Server now correctly synchronizes treatments when both T-Server and URS are running in high-availability (HA) mode. Previously T-Server could incorrectly send treatment related events to the backup URS instead of the primary URS after a T-Server switchover was performed. (ER# 219545460)

T-Server has been modified to correctly report EventDNBackInService when agent substitution is enabled and an agent is logged out while the phone is out of service, and then the phone comes back into service. (ER# 223284441)

T-Server now correctly handles the agent state NotReady with activation. In doing so, T-Server now rejects a RequestAgentNotReady when the value of the ReasonCode is different from the value that is reported in the agent event. Also, if a RequestAgentNotReady is missing the ReasonCode extension, T-Server uses the current value of ReasonCode. (ER# 216152182)

Top of Page

Known Issues and Recommendations

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

T-Server incorrectly handles agents that login in a pre-assigned state if the PBX timer 238 is set to value higher than 11. In order to avoid this issue, verify that the value of PBX timer 238 does not exceed a value of 11. (ER# 261524426)

When No-Answer Supervision is configured to use recall and a predictive call made from a supervised RSI is answered by a customer, then it is routed to an unanswered destination, T-Server does not return the call to the last distribution device. (ER# 260478871)

T-Server generates alarms on attach/update of user data in Solution Control Interface. (ER# 248543355)

T-Server occasionally may not be able to transfer a call using a SingleStepTransfer to an outbound destination if the network provider delivers the call to a destination in more than 500 milliseconds after the trunk is seized. Complete transfer on such non-delivered calls is not permitted. A possible workaround to this scenario is to set the min-xfer-complete-dly option to a value of 1000, which increases the timeout to 1000 milliseconds. (ER# 248833547)

T-Server may become unstable when requesting a change of agent state to not ready while on call. (ER# 248881333)

T-Server may become unstable when a call is initiated to A4400, which is integrated with GVP and SIP Server, and is returned to the RSI on the same PBX. This situation is caused by incorrect PBX behavior that exists on some of the last 8.x and 9.0 versions of the PBX. (ER# 249078553)

T-Server may become unstable when the number of channels selected for predictive dialing scenarios in OCS exceeds the number of available predictive devices. As a workaround, set the number of predictive channels to a value smaller than the available predictive dialer resources. (ER# 249459876)

On Occasion, after a logout is completed, T-Server incorrectly reports an EventOffHook event for the agent device instead of for the ProACD device. This will leave any T-Server client to see the DN as still on-hook. This can be rectified by physically taking the ProACD device off-hook and then placing it back on-hook. (ER# 246973461)

Beginning with release 8.0, T-Server has an improved CTI request pacing mechanism, which is controlled by the new option device-rq-gap. The default value of this option is 250 milliseconds, which limits the number of requests sent to the switch to 4 requests per second on any given device.

In scenarios where a version 8.0 T-Server is used in a high-load environment, which requires higher performance, Genesys recommends setting the device-rq-gap option to a lower value at an Application level, for a global effect on all DNs, or to set the DN-level option rq-gap to a lower value for a specific high-load Routing Point DN.

Note: Setting the device-rq-gap option to a value of 0 (zero) will disable this option, resulting in the same behavior as version 7.6 and older of T-Server.

(ER# 237463081)

When using ANI related ISCC strategies (direct-ani, match-ani) and a call is initiated or consultation initiated from an agent in substitution mode, T-Server will not be able to match calls. This is because the call is made from a substituted device (ProACD number), and delivered with the ANI of the agent device, which do not match. (ER# 235145471)

In the following scenario:

• A call is made to a pilot where the transaction code is enabled.
• The agent answers and performs a two-step transfer.
• On the transfer completion, the agent does not enter any transaction code.

When the switch times out, the transaction code that T-Server reports are two EventHeld/EventRetrieved events before the EventReleased. (ER# 235609411)

T-Server becomes unstable in the following scenario:

• Internal call from a virtual Z to a ProACD.
• ProACD mute transfers to a pilot.
• The agent answers and make a conference call to another pilot.
• The second agent answers and the first agent completes the conference.

The PBX reporting is incorrect as a result of a virtual Z being on the call, which leads to T-Server becoming unstable. T-Server will handle this scenario if no virtual Z is involved as the PBX reporting will be correct. (ER# 235609418)

T-Server incorrectly reports the following scenario as a conference.

• An internal call is made between two devices but is not answered.
• T-Server is restarted.
• The destination answers then releases.

When the destinations answers, the EventEstablished on the destination ThisDNRole is ConferenceMember, and the Call State is Conferenced.

When the destination releases, T-Server reports EventPartyDeleted in addition to EventReleased. (ER# 235609445)

When the switch sends a failed event for a PCM port (a device configured as switch-specific type 7 in Configuration Manager), T-Server is prompted to clear the call in order to free the port. This cleanup should not be visible. However, T-Server is incorrectly reporting the cleared call, and reports EventDialing, NetworkReached, DestinationBusy, and Released for the PCM port when in fact it should not.

This problem does not affect Outbound Contact Server (OCS). Outbound call results are correctly updated. (ER# 235673214)

If an inbound or an outbound call is single-step transferred to an RSI, and then routed, the Call State in EventRinging is incorrectly set to Forwarded. (ER# 235719521)

When performing an in-service upgrade to a version 8.0 T-Server, a growth in memory utilization can potentially occur while running a T-Server version 8.0 in primary mode and a T-Server 7.6 in backup mode.

This issue will not occur if both high-availability (HA) T-Servers are version 8.0. (ER# 235774109)

If a call is routed to an RSI where an inbound call is received on an emulated Routing Point, and supervised routing is enabled, T-Server will never complete the transfer on the Hunting Group (HG) member. Therefore, T-Server will not report EventRouteRequest on the RSI. When the timer expires the call is reconnected on the HG member. This problem only occurs on inbound calls. Internal calls are fine. (ER# 235448131)

In some circumstances, when routing a call from an emulated routing point with supervision, the switch will complete the transfer on the Hunt Group member before T-Server can request transfer completion or reconnection. The emulated route will be successfully performed, but this switch behavior will result in T-Server returning an EventError call has disconnected in addition to RouteUsed/Diverted on the emulated Routing Point. The RefID from the RequestRouteCall will be returned in the EventError and not the EventRouteUsed. (ER# 231294614)

If call forwarding is set on a remote extension to another internal device, and a call is made to the remote extension, the Call State is Ok instead of Forwarded when the call is delivered to the forward destination. (ER# 233146460)

T-Server 8.0 only supports the PBX starting with Release 7.1. (ER# 244001815)

If a call is made between two pro-ACD devices while T-Server is not running, and then T-Server is started, the PBX provides no information to T-Server's snapshot query for these devices. As a consequence, the call is invisible to T-Server. (ER# 208985444)

When reporting is required for Hunt Group members, T-Server does not support the use of parallel Hunt Groups. (ER# 107538491)

When reporting is required for Hunt Group members, the Hunt Group itself must not be configured in Configuration Manager. (ER# 107387229)

If a CCD agent that the PBX has placed in AfterCallWork (wrap-up) makes a call to another CCD agent that the PBX has placed in AfterCallWork, then the PBX does not send any CSTA events to T-Server for the origination of this call. Once the agents are out of AfterCallWork, the PBX reporting is correct. (ER# 103699875)

Prior T-Server release 8.0, TMakePredictiveCall cannot be made to an internal destination. (ER# 107590864)

There is an incompatibility between A4400 T-Server behavior regarding chained consult calls and the OCS option call_transfer_type = two_step. On the A4400 it is not possible to chain consult calls, therefore in that situation T-Server completes the transfer. However, when OCS is using two-step transfer and waiting for the agent to answer, it attempts to complete the transfer. This leads to the two applications clashing when agent-no-answer-overflow = recall to the queue.

With a consult call on the agent, agent-no-answer-timeout expires, and this forces T-Server to perform an emulated redirect. This involves answering the call on the agent, T-Server completing the transfer and then T-Server transferring the call back to the queue. However, because OCS sees an EventReleased on the consult call (due to completion of the transfer) it attempts to reconnect the call, assuming the call has failed. (ER# 36839060)

The PBX does not support Do Not Disturb (DND) functionality via CTI, so setting DND can only be done from the phoneset. The PBX also provides no CSTA reporting to T-Server when DND is set manually on a telset. (ER# 31943037)

Chained consultation calls are not supported by the PBX. (ER# 14800088)

Four-party and blind conferences are not supported by the PBX. (ER# 14800090, 14800092)

When a hot-standby pre-release 8.0 of T-Server is started, the status of active emulated agents is not accurately reported. (ER# 74180)

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.

HP-UX 11.00 is no longer supported.

Solaris 7 is no longer supported.

Windows 2000 is no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known restrictions specific to international customers.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software.

• The Framework 8.0 T-Server for Alcatel A4400/OXE Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Alcatel A4400/OXE switch including configuration options, known limitations, and switch functionality.
  

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

• The Voice Platform SDK 8.0 .NET (or Java) API Reference and the Genesys 7 Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.

• The Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of the guide, or contact Genesys Technical Support for additional information.

Product documentation is also provided on a Documentation Library DVD, which is produced monthly. The New Documents on this DVD page on the DVD indicates the DVD production date. Because the DVD is produced monthly, documentation on the Technical Support website may be more up-to-date than that on the DVD. To verify the latest version of a document, check the version number, located on the second page in PDFs and on the "About This File" topic for Help files.

Top of Page