| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.008.02 [02/12/09] – General (Under Shipping Control) | X | X | ||||
| 7.6.007.03 [01/15/09] – General (Under Shipping Control) | X | X |
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 only to the 7.6 releases of T-Server for Avaya TSAPI that are specified in the Contents (above).
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
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This release is under shipping control. This section describes new features that were introduced in the initial 7.6 release of T-Server for Avaya TSAPI:
T-Server now supports the Flow Control feature.
The following Flow Control options support a new flow control mechanism to ensure that the number of requests sent to the link is limited to a given rate.
high-water-mark
Default Value: 1000
Valid Values: 50-10000
Changes Take Effect: Immediately
Specifies the maximum allowable number of outstanding messages in flow control before T-Server warns of a backlog. When message backlog increases above the high-water-mark value, T-Server generates the LMS message Flow Control: Above high water mark (x messages buffered). When message backlog drops to 50 messages fewer than the high-water-mark value, T-Server generates the LMS message Flow Control: Below high water mark (x messages buffered).
Note: The high-water-mark value is applicable for use-link-bandwidth values only.
use-link-bandwidth
Default Value: 0
Valid Values: 0-999
Changes Take Effect: Immediately
This option controls the number of messages that can be sent to the link within a one second period of time. A value of 0 (zero) disables flow control.
use-link-bandwidth-backup
Default Value: 0
Valid Values: 0-999
Changes Take Effect: Immediately
This option controls the number of messages that can be sent to the link within a one second period of time when T-Server is in backup mode. It allows the backup T-Server to use less bandwidth, preventing the combined primary and backup T-Servers from drawing too much bandwidth from the switch. If the value is 0 (zero), the use-link-bandwidth option will be used instead.
(ER# 213139988)
This release includes the following corrections and modifications:
The out-of-service-retry-interval option now works with Routing Point DNs. Previously, only regular DNs were able to use this option correctly, and Routing Points did not fully register. (ER# 212956382)
When the simulated-heartbeat-enabled option is set to true, the simulated heartbeat functionality is no longer disabled. (ER# 214184631)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This release is under shipping control. This section describes new features that were introduced in the initial 7.6 release of T-Server for Avaya TSAPI:
Avaya TSAPI library 4.1 or 4.2 must be installed on the T-Server host machine. To obtain the library, contact Avaya, or download the client from the Avaya Application Enablement Services Downloads online.
T-Server supports release 5.0 and 5.1 of the Avaya Communication Manager.
T-Server supports version 4.1 or higher of Avaya's Application Enablement Services (AES) server.
There are no corrections or modifications in this initial release.
This section provides the latest information on known issues and recommendations associated with this product.
Because of known problems with Avaya TSAPI messaging, T-Server does not receive ACD Split information from the switch for SIP phones. This results in missing EventQueued and EventDiverted messages for ACD Queue calls to SIP phones, and missing AttributeThisQueue attributes in all the events for the Agent DN. (ER# 189071409, 187728239)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, a predictive call to an ACD Queue specified in extensions with VoiceDest, AnsMachine and FaxDest results in delayed EventQueued and EventDiverted messages for that queue when the call is diverted to an agent. OCS cannot process the resulting event flow correctly. (ER# 200022171)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, the route-through-queue option does not work on the Windows platform. A RouteCall request will deliver the call to the target agent, but the call is not sent through the ACD Queue. (ER# 194726064)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, the Outstanding request limit exceeded, privilege violation on called device and No active call errors can occur in response to a request when multiple requests are sent to the switch in very quick succession. These errors can occur specifically for the TInitiateConference, TInitiateTransfer, TAnswerCall, TAlternateCall, and THoldCall requests. Repeating the request should achieve a successful result. (ER# 189555083, 188709468, 189555098, 198834235, 189236831, 189071403)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, if a consult call is made from an inbound call that has been routed to an H.323 phone, the original call is dropped by T-Server. (ER# 198310362)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, a transfer to a DN with a coverage path can result in the destination party being dropped when another party joins the call. (ER# 198809404)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, an ACD Queue is incorrectly dropped from a call after the calling party releases in a conference call that includes an ACD Queue, or after a call transfer to an ACD Queue. (ER# 196845001)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, if forwarding is set to a Routing Point, the AttributeCallState in EventQueued is CallStateOK instead of CallStateForwarded. (ER# 197648083)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, the disable-digits-collection option and the associated RouteCall request with extension CollectDigits do not work. No digits are collected, and EventDigitsCollected is not generated. (ER# 177939032)
| Found In: 7.6.007.03 | Fixed In: |
Because of known problems with Avaya TSAPI messaging, previously deleted parties in a call can incorrectly reappear in the call after a Routing Point routes to a party that sends a RequestRedirectCall, or after a party sends a RequestRedirectCall to redirect the call to a Routing Point. (ER# 186343982, 183965043, 184448962, 184448970, 197324963, 177650513)
| Found In: 7.6.007.03 | Fixed In: |
Unparking a parked inbound or outbound call will change the connection ID for the call. (ER# 193629372)
| Found In: 7.6.007.03 | Fixed In: |
The value for the ring-timeout option (or AttributeTimeout in RequestMakePredictiveCall) must be increased by the value of the ring-back-tout option to set the accurate timeout value. Also, the value for ring-timeout (or AttributeTimeout in RequestMakePredictiveCall) should be divisible by the ring-back-tout value, if not, the divisible portion is used and the remainder ignored. (ER# 181966251)
| Found In: 7.6.007.03 | Fixed In: |
The ISCC Call Overflow feature (COF) is not fully supported in this release. Support is limited to ANI-based ISCC/COF calls only. (ER# 198107401)
| Found In: 7.6.007.03 | Fixed In: |
A query address request on T-Server results in an error for queries with AddressInfoType set to AddressInfoNumberOfIdleTrunks or AddressInfoNumberOfTrunksInUse. (ER# 198770729)
| Found In: 7.6.007.03 | Fixed In: |
T-Server does not properly process the TCallCancelForward request with TForwardMode set to ForwardModeSendAllCalls, which makes it impossible to cancel the Send All Calls (SAC) switch feature through the T-Library request TCallCancelForward. (ER# 204938254)
| Found In: 7.6.007.03 | Fixed In: |
This section documents features that are no longer supported in this software. There are no discontinued features or functions for this product.
Information in this section is included for international customers. There are no known internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
The Framework 7.6 T-Server for Avaya TSAPI Deployment Guide contains detailed reference information for the Genesys Framework 7.6 T-Server for Avaya TSAPI, including configuration options and specific functionality.
The Framework 7.6 Deployment Guide helps you configure, install, start, and stop Framework components.
The Genesys 7 Events and Models Reference Manual contains an extensive collection of events and call models describing core interaction processing in Genesys environments.
The Voice Platform SDK 7.6 .NET (or Java) API Reference contains technical details of T-Library functions.
Genesys Supported Operating Systems and Databases contains information about supported operating systems and databases.