| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.5.010.05 [01/20/12] – Hot Fix | X | X | X | X | X | X |
| 7.5.010.04 [05/29/08] – Hot Fix | X | X | X | X | X | X |
| 7.5.010.02 [08/06/07] – Hot Fix | X | |||||
| 7.5.010.01 [07/30/07] – Hot Fix | X | X | ||||
| 7.5.010.00 [06/29/07] – Hot Fix | X | X | ||||
| 7.5.009.02 [06/29/07] – General | X | X | X | X | X | X |
| 7.5.009.01 [05/28/07] – General | X | X | X | X | X | X |
| 7.5.009.00 [04/21/07] – General | X | X | X | X | X | X |
| 7.5.008.03 [03/21/07] – Hot Fix | X | X | ||||
| 7.5.008.02 [03/07/07] – General | X | X | X | X | X | X |
| 7.5.008.01 [03/07/07] – General | X | X | X | X | X | X |
| 7.5.008.00 [03/07/07] – General | X | X | X | X | X | X |
This release note applies to all 7.5 releases of T-Server Common Part (TSCP).
Note: Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections or modifications:
In an environment where a premise T-Server is connected to load-balanced Network T-Servers, the premise T-Server now correctly propagates user data related to a multi-site call originating from the premise T-Server and received by one of the Network T-Servers after a transaction using the dnis-pool transaction type. Previously, the premise T-Server sometimes propagated user data to a Network T-Server different from the one that actually received the call. (ER# 292429271)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections or modifications:
T-Server no longer incorrectly sends an extra response to the TSendEvent request
when the option handle-vsp, in the extrouter section, is set to all
or events. (ER# 183511148)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections or modifications:
The Advanced Disconnect Detection Protocol (ADDP) now works correctly
between the primary and backup T-Servers operating in Hot Standby mode. (ER# 142870445)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new feature:
This release introduces the ani-distribution configuration option, which controls the distribution
of the ANI information in TEvent messages. This option is configured in the TServer section.
ani-distribution
Default Value: inbound-calls-only
Valid Values: inbound-calls-only, all-calls, suppressed
When this option is set to all-calls, the ANI attribute will be reported for all calls
for which it is available.
When this option is set to suppressed, the ANI attribute will not be reported for any calls.
When this option is set to inbound-calls-only, the ANI attribute will be
reported for inbound calls only.
(ER# 136390582)
This release includes the following corrections or modifications:
The active-data-original-call value of the use-data-from configuration option
now works correctly for consultation calls routed from a local Routing Point to a remote destination.
(ER# 136390534)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new feature or functionality:
The use-data-from configuration option in the extrouter section of
T-Server now includes the new valid value active-data-original-call. This option specifies the
call from which the values for the UserData and ConnID
attributes are taken for a consultation call that is routed or transferred to a remote location.
When the use-data-from option is set to active-data-original-call,
the value of UserData attribute is taken from the consultation call and
the value of ConnID attribute is taken from the original
call. For a complete description of the option, consult your T-Server Deployment Guide.
Note: The option value active-data-original-call is restricted to certain
call scenarios. See Known Issues and Recommendations for details. (ER# 136390534)
This release does not include any corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
A problem with incorrect handling of client disconnection on exit has been resolved. Previously, this could cause memory corruption and T-Server failure. (ER# 135504686)
A problem with disconnection of ISCC internal clients has been resolved. This problem could cause ISCC to become unresponsive when a client connected to T-Server on Windows using a single specific file-descriptor value. (ER# 126252934)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer becomes unstable when cleaning up its internal timers during the shutdown process. (ER# 126842556)
T-Server's behavior of error handling has been modified as follows:
TERR_ISCC_LOCATION_IS_DISCONNECTED.TERR_ISCC_REMOTE_LINK_IS_DISCONNECTED.ISCCRequestGetCallDataXferService message to all connected
T-Servers. Those T-Servers constitute a set called {participated-server-set}.{participated-server-set}.
For each T-Server, one of the following occurs:{successful-server-set}.ISCCRequestCancelCallDataXferService message to the T-Servers remaining in
{participated-server-set}. Then the transaction is terminated.{participated-server-set}
is the same as {successful-server-set}, a T-Server in {participated-server-set}
is disconnected or its CTI link is disconnected, that T-Server is removed from {participated-server-set}
and removed from {successful-server-set} if it belongs to them.{participated-server-set}, ISCC responds with EventError
TERR_ISCC_BAD_LOCATION_SPECIFIED. Then the transaction is terminated.
{participated server set} have responded positively, meaning that
{participated-server-set} is the same as {successful-server-set},
ISCC requests the origination T-Server to route a call in question.{participated-server-set}
is disconnected or its CTI link is disconnected, that T-Server is removed from {participated-server-set} and
removed from {successful-server-set}.{participated-server-set},
ISCC responds with EventRemoteConnectionFailed.
Then the transaction is terminated.ISCCEventCallDataXferFailed message from a T-Server in {participated-server-set},
ISCC responds with EventRemoteConnectionFailed and then sends the
ISCCRequestCancelCallDataXferService message to the T-Servers remaining in
{participated-server-set}.ISCCEventCallDataXferServiceSucceeded message from a T-Server in {participated-server-set},
ISCC responds with EventRemoteConnectionSucceeded and
sends ISCCRequestCancelCallDataXferService to the T-Servers remaining in
{participated-server-set}.(ER# 124325601)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer becomes unstable when a client attempts to connect to a T-Server's compatibility port
specified by the compatibility-port configuration option. This option, provided for clients that were built with
T-Library SDK 3.x, is no longer supported. Genesys recommends that you do not use the compatibility-port
option in your T-Server configuration.
(ER# 109894061)
T-Server is now able to periodically attempt binding a specific socket address to its socket. Previously, T-Server only attempted to bind the socket address once. If this attempt was unsuccessful, T-Server kept running and had to be restarted manually or its server port had to be reconfigured.
The option of dynamic port reconfiguration became available in release 7.5; before then, T-Server would restart automatically when it could not bind the socket address on the first attempt. (ER# 114565005, ER# 99747829)
Supported Operating Systems
New in This Release
Corrections and Modifications
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:
In a multi-site environment with the ISCC/COF feature enabled, T-Server may sometimes process a call more than once, which could result in mismatching call data. (ER# 112541265)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
This release of T-Server Common Part corrects an internal issue that may impact Network T-Servers.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
This release of T-Server Common Part is built with the version Common Library that corrects an issue related to X.25 links.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 7.5 release of T-Server Common Part.
Support for Transport Layer Security (TLS). T-Server can now be configured for secure data exchange with the other Genesys components that support this functionality. Refer to the Genesys 7.5 Transport Layer Security Deployment Guide for details.
Support for optimization of User Data distribution. Distribution of user data can be optimized where user data is communicated in a few selected events, as opposed to all DN events. See your T-Server Deployment Guide for details.
Enhanced ISCC routing support for T-Servers using load balancing. This support applies to T-Servers that
use the dnis-pool transaction type for call routing in a multi-site environment.
See your T-Server Deployment Guide for details.
The Keep-Alive Protocol (KPL) backward compatibility is no longer supported. If you have used the KPL with previous versions of Genesys, consider using ADDP after upgrading to 7.5. For more information on ADDP, see your T-Server Deployment Guide.
This release includes the following corrections and modifications that were made between release 7.2 or earlier releases and the initial 7.5 release:
This release fixes the issue that occurred in a multi-site environment with the Event Party Propagation feature enabled where T-Server could continuously generate party events for a call until that call was released. (ER# 53137681, ER# 3166571)
T-Server no longer duplicates NetworkCallState events distributed for an origination DN in call
scenarios involving the Network Attended Transfer/Conference feature. (ER# 4551832)
This section provides the latest information on known issues and recommendations associated with this product.
Starting with release 7.5, T-Server no longer supports the network-provided-address
configuration option. The option became obsolete with introduction of multiple ports configuration.
Framework 7.5 T-Server Deployment Guide incorrectly documents this option as supported. (ER# 99731719)
The active-data-original-call value of the use-data-from configuration option
does not work for consultation calls routed from a local Routing Point to a remote destination. (ER# 136390534)
| Found In: 7.5.010.00 | Fixed In: 7.5.010.01 |
T-Server may become unstable when a client attempts to connect to a T-Server's compatibility port
specified by the compatibility-port configuration option. This option, provided for clients that were built with
T-Library SDK 3.x, is no longer supported. Genesys recommends that you do not use the compatibility-port
option in your T-Server configuration. (ER# 109894061)
| Found In: 7.5.008.00 | Fixed In: 7.5.009.00 |
In release 7.5, the Configuration Layer introduces the possibility to configure multiple ports. For applications that run on the Windows platform, you need to restart an application in order for changes made to its port properties to take effect. Alternatively, you can delete the port and then re-create it with the correct settings. (ER# 99747829)
| Found In: 7.5.008.00 | Fixed In: 7.5.009.00 |
In a multi-site environment with switch partitioning or intelligent trunks, enabling the ISCC/Event
Party Propagation (ISCC/EPP) feature may result in duplicate EventPartyAdded,
EventPartyChanged, and EventPartyDeleted messages.
Since duplicate events are known to cause problems in other Genesys solutions, ISCC/EPP
is not currently supported in such environments. (ER# 92590894)
| Found In: 7.5.008.00 | Fixed In: 8.0 |
In a multi-site environment with the Event Party Propagation feature enabled, T-Server may report
incorrect values for DNRole attributes
in EventPartyAdded, EventPartyChanged, and EventPartyDeleted messages.
(ER# 77026025)
| Found In: 7.5.008.00 | Fixed In: |
In a multi-site environment with the ISCC/COF feature enabled, T-Server may sometimes process a call more than once, which could result in mismatching call data. (ER# 107168816)
| Found In: 7.5.008.00 | Fixed In: |
When running on a Solaris platform in 32-bit mode, T-Server may consume 100 percent of the CPU time while attempting to connect a 1024th client. This is Solaris-specific behavior. To avoid this situation, the total number of T-Server connections must not exceed 1023.
Note: This limitation does not apply to T-Servers running on a Solaris platform in 64-bit mode. (ER# 40579)
| Found In: 6.5.1 | Fixed In: |
Even though the attribute ThirdPartyDN is documented as always
being present in EventPartyAdded, EventPartyDeleted, and
EventPartyChanged messages, T-Server sometimes does not include it with these
events when they are propagated to remote T-Servers (ISCC's Party Events propagation).
In addition, although OtherDN is an optional attribute, it
is also not included in these events. (ER# 100376)
| Found In: 7.1.006.00 | Fixed In: |
If a TNetworkConsult request is made while a previously initiated
TNetworkConsult operation is still in progress, and the second request
specifies a different destination DN than the first request, subsequent
EventNetworkCallStatus messages will report incorrect values for
AttributeNetworkOrigDN and AttributeNetworkDestDN.
(ER# 15366731)
| Found In: 7.1.007.01 | 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.
AIX 4.x operating system is no longer supported.
| Discontinued As Of: 7.5.x |
Keep-Alive Protocol (KPL) backward compatibility is no longer supported.
| Discontinued As Of: 7.5.x |
Windows NT operating system is no longer supported.
| Discontinued As Of: 7.2.x |
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.
The Framework 7.5 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 Voice Platform SDK 7.5 .NET (or Java) API Reference contains technical details of T-Library functions.
Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.
Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support 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 or on the About This File topic in Help files.