Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
8.0.101.06 [12/13/10] – Hot Fix | X | |||||
8.0.101.05 [09/14/10] – General | X | X | ||||
8.0.101.02 [06/16/10] – Hot Fix | X | |||||
8.0.101.01 [05/25/10] – General | X | X | ||||
8.0.006.12 [02/26/10] – General | X | X | ||||
8.0.006.09 [02/05/10] – Hot Fix | X | |||||
8.0.006.07 [01/14/10] – Hot Fix | X | |||||
8.0.006.03 [11/20/09] – General | X | X | ||||
8.0.005.04 [09/22/09] – General | 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 to all 8.0 releases of T-Server for Avaya TSAPI.
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 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 new features or functionality.
This release includes the following correction and modification:
Service observing scenarios involving a mix of monitored and unmonitored switch resources no longer cause stuck calls in T-Server. Previously in such scenarios, T-Server could ignore switch disconnect messages in such scenarios, which may have resulted in stuck calls. (ER# 263658307)
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 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 release contains the following new features or functionality:
This release of T-Server supports Linux 5.
This release includes the following corrections and modifications:
T-Server now corrects a problem which can prevent T-Server from unregistering a DN through the Computer Telephony Intergration (CTI) link. This problem is specific to cases where a DN is removed from Configuration Manager with active clients registered on that DN. Previously, T-Server did not unregister the DN through the CTI-link following the last T-Server client request to unregister the DN. (ER# 254888210)
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 8.0.101.01. 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 new features or functionality.
This release includes the following corrections and modifications:
T-Server now detects scenarios in which the switch performs a quick reuse of a CallID
by verifying that the previous call is removed from memory before processing the initiated event report. Previously, this scenario caused T-Server to ignore the initiated event report for a new call and displayed the DN status as idle. (ER# 254251860)
T-Server now adds the agentGroup
parameter to all TSAPI agent-level requests to the switch when the agent queue is provided by the T-Server client. Previously, T-Server would only add the agentGroup
parameter to agent-login requests. (ER# 254547509)
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 8.0.101.01. 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.1 release of T-Server for Avaya TSAPI.
Flexible call matching has been enhanced to resolve race conditions that previously could interfere with Inter Server Call Control/Call Overflow (ISCC/COF).
T-Server now supports Call Overflow (COF) interoperability between T-Server for Avaya Communication Manager and T-Server for Avaya TSAPI.
T-Server adds support for a new value of unspecified
for the treatment type with the use-am-detection
option, and to the extensions on RequestMakePredictiveCall
. Predictive calling using the unspecified
answering machine detection option value indicates that no answering machine treatment is specified. (ER# 246432571)
This release includes the following corrections and modifications:
T-Server now only diverts, from both a Vector Directory Numbers (VDN) and a Queue, after a call is redirected from the second Queue. Previously, T-Server diverted from a VDN when the call was queued to another skill. (ER# 243556478)
T-Server now can register VDNs with the flowPredictiveCallEvents
flag set to true
. This improves CallState
reporting on EventReleased
events for some predictive dialing call flows. (ER# 246387172)
T-Server no longer becomes unstable when processing a delivered message from the perspective of an unmonitored party. Previously, this could have invoked a search for related parties (which should be dropped from a call) and caused stability issues with T-Server. (ER# 251929694)
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 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server now improves the mapping of CSTA Cause Codes to Genesys Call States as shown in the following examples:
ecNetworkNotObtainable
now translates to CallStateSitNocircuit.
ecNetworkCongestion
now translates to CallStateSitReorder.
ecIncompatibleBearerService
now translates to CallStateFaxDetected.
ecVoiceUnitInitiator
now translates to CallStateAnsweringMachineDetected.
.
(ER# 244959461)
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 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.
This release includes the following corrections and modifications:
T-Server now generates an EventDiverted
event from both the VDN and the other queue simultaneously when the call is distributed to an available agent. Previously, T-Server generated an EventDiverted
event for a VDN (configured as type ACD Queue
with a switch-specific Type
property set to 2
) as soon as a call was redirected to another queue. (ER# 243908731)
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 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.
This release includes the following corrections and modifications:
T-Server now uses an alternate form of the private data function for route select service. Previously, the parameter list resulted in the private data function failing on the Windows operating system. This change impacts routing features dependant on this private data function such as: uui
, priority_calling
, and the route-thru-queue
option. (ER# 205956492)
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 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 release contains the following new features or functionality:
T-Server now supports switch partitioning so that multiple T-Servers can connect to the same physical switch.
T-Server now supports the new option enable-dmcc
, in order to selectively enable or disable DMCC support for specific DNs. This option is set in the TServer
section on the Annex
tab of a DN
configuration object in Configuration Manager.
enable-dmcc
Default Value: true
Valid Values: true
, false
Changes Take Effect: during next registration
When this option is set to true
, T-Server registers this DN over the DMCC link. Previously, during switchover to the primary T-Server, the new primary T-Server could invoke a registration on a DMCC-enabled DN when the DMCC link was not responding. This could inadvertently cause delays on the primary CTI link. Now T-Server ensures that DN registration on the DMCC link only takes place if the DMCC link is connected.
T-Server now supports two new values for the log-trace-flags
option:
Default Value: -tsapipoll
, -tsapierror
Valid Values (in any combination):
+/-tsapipoll
: Turns logging on or off before and after polling the TSAPI library for events.
+/-tsapierror
: Turns logging on or off for TSAPI return errors after polling or sending requests.
These are specific options for this T-Server, in addition to the other values of this option.
The following four new restricted options have been added to control the queue size parameters in the AcsOpenStream
request. These options are set in the tsapi-configuration
section.
send-q-size
Default Value: 0
Valid Values: 0
to 4294967294
Changes Take Effect: Immediately
This option controls the sendQSize
parameter in the AcsOpenStream
Request.
send-extra-bufs
Default Value: 0
Valid Values: 0
to 4294967294
Changes Take Effect: Immediately
This option controls the sendExtraBufs
parameter in the AcsOpenStream
Request.
recv-q-size
Default Value: 0
Valid Values: 0
to 4294967294
Changes Take Effect: Immediately
This option controls the recvQSize
parameter in the AcsOpenStream
Request.
recv-extra-bufs
Default Value: 0
Valid Values: 0
to 4294967294
Changes Take Effect: Immediately
This option controls the recvExtraBufs
parameter in the AcsOpenStream
Request.
Note: Use these options only when requested by Genesys Technical Support.
(ER# 263374630)
This release includes the following corrections and modifications:
T-Server now correctly generates the EventLinkConnected
event in startup scenarios where DNs are removed from Configuration Manager when Flow Control is enabled. Previously in this scenario, T-Server could fail to generate the event. (ER# 234636830)
T-Server now correctly handles routing to bridged parties. Previously, T-Server abandoned a bridged party after passing through a Routing Point. (ER# 228115953)
T-Server now corrects a problem where it could briefly take a DN out of service. This behavior is related to scenarios involving DNs that are manually registered (not part of Configuration Manager) and then later added to Configuration Manager with the same AddressType
. (ER# 219740672)
T-Server now corrects a routing problem that happens when two routes target the same Routing Point. The following is an example of that scenario:
Previously, when one route was issued and then within a short time frame (less than one second) a second route was issued with the same targeted route point, T-Server would store the new routing cross-reference ID incorrectly. This would cause the next RequestRouteCall
request to fail. (ER# 237111297)
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 8.0.001.15. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of T-Server for Avaya TSAPI.
T-Server now supports new log events to notify about failed routing attempts. Also, T-Server now supports a new log event to notify about failed ISCC transactions.
T-Server now supports Flow Control which was added in version 7.6.008.02.
T-Server now supports Real Time Agent State reporting using Device, Media and Call Control (DMCC).
T-Server now supports Call Overflow (COF) using the default-network-call-id-matching
option.
default-network-call-id-matching
Default Value: No default value
Valid Values: TSAPI
Changes Take Effect: Immediately
When this option is set to TSAPI
, T-Server will use the NetworkCallID
attribute for the ISCC/COF call matching.
To activate this feature, the cof-feature
option must be set to true
.
T-Server now supports ESS which provides enhanced availability and survivability for T-Server for Avaya TSAPI.
T-Server now supports link bandwidth reporting. Two new log events have been added, to handle alarm conditions that are triggered when the average link bandwidth exceeds or drops below a predefined threshold. The new log events are as follows:
20009 | STANDARD | Link bandwidth: [requests] requests per second exceeded alarm threshold [setting] requests per second on CTI link ID [id].
20010 | STANDARD | Link bandwidth: [requests] requests per second dropped below alarm threshold [setting] requests per second on CTI link ID [id]
T-Server now supports configurations of 10000 or more DNs.
This release includes the following corrections and modifications:
T-Server now correctly processes ACSUniversalFailureConfEvent
messages. Previously, T-Server ignored all ACSUniversalFailureConfEvent
messages, resulting in unnecessary delays when handling requests that result in this error. (ER# 232897662)
T-Server now correctly performs the acquire
operation for Routing Point
DNs on both primary and backup T-Servers during application startup. Previously, T-Server only performed the acquire
operation in the primary T-Server during client registration, causing unnecessary delays during a High Availability (HA) switchover.
Note: Separate Application Enablement Servers (AES) are required for HA deployments. (ER# 232605331)
T-Server now sends the correct number of messages per second over the CTI link. The message flow rate is configured using the use-link-bandwidth
option. Previously, T-Server sometimes sent more messages than the use-link-bandwidth
option allowed. (ER# 232674197)
This section provides the latest information on known issues and recommendations associated with this product.
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)
Found In: 8.0.101.05 | Fixed In: |
T-Server currently does not register VDNs with flowPredictiveCallEvents
set to true
. This issue impacts the reporting of predictive call events in some failed scenarios which can result in an unspecific CallState
on EventReleased
. (ER# 246387172)
Found In: 8.0.006.12 | Fixed In: 8.0.101.01 |
T-Server for Avaya TSAPI currently does not use the administrative treatment when the option use-am-detection
is set to false
or no
or when the Extensions
attribute key AMD
(set to no
) is present in the TMakePredictiveCall
request. This behavior is different from the T-Server for Avaya Communication Manager, which follows the switch answering machine detection administration when the use-am-detection
option is set to false
or no
or when the Extensions
attribute key AMD
(set to no
) is present in TMakePredictiveCall
. (ER# 246432571)
Found In: 8.0.006.12 | Fixed In: |
T-Server will not properly process single-step conference scenarios if:
1
.
(ER# 245875671)
Found In: 8.0.006.12 | Fixed In: 8.0.101.01 |
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)
Found In: 8.0.005.04 | Fixed In: |
In scenarios where a call is redirected back to the same queue from which it had previously passed, the EventQueued
and EventDiverted
event sequences may be missing when the call diverts from the queue. This means that the first queued and diverted messages go back into the same queue, so instead of two sets of messages, only one message returns, and is diverted the second time. (ER# 225250782)
Found In: 8.0.005.04 | Fixed In: |
T-Server sometimes fails to update transitional agent states in the backup T-Server. (ER# 229745757)
Found In: 8.0.005.04 | Fixed In: |
The Outbound Contact Server (OCS) does not follow the correct call flow in cases where an EventRinging
message is sent before EventQueued
or EventDiverted
. (ER# 235720427)
Found In: 8.0.005.04 | Fixed In: |
T-Server does not correctly handle routing to bridged parties. (ER# 228115953)
Found In: 8.0.005.04 | Fixed In: 8.0.006.03 |
T-Server does not handle predictive dialing to ACD Queues correctly. It distributes the EventQueued
message in the wrong sequence (after distributing the EventRinging
to the agent) and without distributing the EventDiverted
. (ER# 235720421)
Found In: 8.0.005.04 | Fixed In: |
T-Server does not handle coverage scenarios correctly. It distributes an EventReleased
message instead of EventBridged
. (ER# 227822952)
Found In: 8.0.005.04 | Fixed In: 8.0.101.01 |
The Transfer Connect Service does not work correctly when the call is connected to an announcement port. (ER# 234107441)
Found In: 8.0.005.04 | Fixed In: |
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)
Found In: 8.0.001.15 | Fixed In: |
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.
Windows 2000 operating systems is no longer supported.
Discontinued As Of: 8.0.005.04 |
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.
Framework 8.0 T-Server for Avaya TSAPI contains detailed reference information for the Genesys Framework 8.0 T-Server for Avaya TSAPI including configuration options and specific functionality.
Framework 8.0 Deployment Guide helps you configure, install, start, and stop Framework components.
The 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.
Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this 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.