| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.021.03 [08/19/11] – Hot Fix | X | X | X | |||
| 7.6.011.02 [08/24/09] – Hot Fix | X | X | X | |||
| 7.6.011.00 [05/26/09] – Hot Fix | X | |||||
| 7.6.004.05 [05/22/09] – Hot Fix | X | |||||
| 7.6.004.03 [05/12/09] – Hot Fix | X | X | ||||
| 7.6.004.02 [12/09/08] – General | X | X | X | X | X | X |
| 7.6.003.04 [03/17/08] – General | X | X | X | X | X | X |
| 7.6.003.03 [01/30/08] – General | X | X | X | X | 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 7.6 releases of T-Server for NEC NEAX/APEX.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.
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.20. 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.
The postpone-dn-registration-msec option has been introduced to implement a configurable timer between the last Facility Subscription response and the first SMFR/SSFM request.
postpone-dn-registration-msec
Default Value: 0
Valid Values: 0 - 180000
Changes Take Effect: Immediately
Specifies the timeout in milliseconds that T-Server waits before initiating DN registration on the switch upon link startup. In Fusion (FCCS) configuration, the switch propagates all of the Facility Subscription requests from T-Server to all of the Fusion nodes. T-Server must wait until the subscription propagation in the Fusion network has completed before initiating the DN registration. The recommended option value for Fusion configuration is 90000 milliseconds.
If, upon link re-start, the Facility Subscription response indicates "Fast restart" ReturnCode = 10, T-Server does not delay DN registration. If this option is set to 0, T-Server does not postpone DN registration.
This release includes the following corrections and modifications:
This T-Server release is built with Configuration Library 7.6.000.16, which ensures that addp parameters between T-Server and Configuration Server are not affected by switchovers of redundant pairs of Configuration Servers. T-Servers built with earlier releases of the Configuration Library lost the addp parameter values after two switchovers of a redundant pair of Configuration Servers, and the addp connection to Configuration Server was not restored after the second switchover. (ER# 280344724)
T-Server now implements immediate dynamic re-configuration of the TServer options flow-control-rate-startup and flow-control-rate-runtime. Previously, re-configuration of these options only took effect after T-Server was restarted. (ER# 248306047)
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.14. 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:
Backup T-Servers now maintain the same synchronization of the agent states as primary T-Servers. Previously, backup T-Servers did not do this, and showed a state that was inconsistent with primary T-Servers. (ER# 231647648)
T-Server now implements enhanced handling of consultation calls that are moved from one ACD Queue to another ACD Queue or Routing Point DN Type. Previously, T-Server could not handle this type of call scenario which caused invalid call processing. (ER# 230031566)
Backup T-Servers now correctly handle synchronization messages from primary T-Servers in single-step transfer scenarios. Previously, backup T-Servers could become unstable when operating in a high-availability (HA) configuration. (ER# 229991761)
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.12. 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 no longer incorrectly processes call reconnect scenarios.
Previously, call reconnect processing errors could cause subsequent THoldCall requests to expire with a timeout error.
Note: In a high-availability environment, both the primary and the backup T-Servers must be upgraded to the current release version.
(ER# 227452702)
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.12. 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:
This release corrects an internal issue, which in some rare cases caused T-Server to become unresponsive. This issue has been fixed. (ER# 221273991)
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.11. 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 no longer becomes unstable when decoding the OAI Reject message. (ER# 220300623)
T-Server now correctly decodes and encodes trunk digits when the Trunk Route or Trunk ID number exceeds 255.
Previously, such trunks were configured in Configuration Manager as a 12-digit number. For release 7.6.004.03 and greater, trunks with Trunk Route numbers above 255 are configured the same as trunks with Trunk Route numbers below 255. (ER# 221296205)
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.
There are no restrictions for this release. This section describes new features that were introduced in this release.
The new option monitor-call-using was added to T-Server.
monitor-call-using
Default Value: infolink
Valid Values: scf, infolink
Changes Take Effect: Immediately
The monitor-call-using option specifies which switch capability T-Server will use while executing TMonitorNextCall and TCancelCallMonitoring client requests.
(ER# 212173821)
This release includes the following corrections and modifications:
T-Server no longer incorrectly processes TDeleteFromConference requests by dropping from the call the party referred to by the AttributeThisDN attribute instead of the party referred to by the AttributeOtherDN attribute. (ER# 180463763)
T-Server now starts normally when DNs are incorrectly configured in Configuration Manager. (ER# 202473604)
T-Server no longer incorrectly handles responses to TMonitorNextCall and TCancelMonitoring requests. Previously, T-Server did not execute these client requests properly and they expired with a timeout error. (ER# 200966835)
T-Server no longer incorrectly releases memory objects while processing response messages from the switch. Previously, this resulted in a memory leak for T-Server. (ER# 209379453)
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.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 new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer becomes unstable when processing an OAI SMFN1 message with an empty information field for a second party. (ER# 178445023)
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.04. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. There are no new features introduced in the initial 7.6 release of T-Server for NEC NEAX/APEX.
This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:
T-Server now checks DN configuration integrity by verifying one-to-one subline and main-line association relationships. If misconfiguration is detected, T-Server sends a 01-20008 log message, and adjusts the line association, thus preventing many-to-one relationships between main-line and subline devices. Previously, T-Server did not verify the integrity of DN configuration, therefore misconfigured DNs (two sublines referring one main line) led to unexpected results that were hard to troubleshoot. (ER# 132227334)
T-Server no longer loses the ReasonCode sub-state of the agent’s AfterCallWork state, which is reported in the Extensions attribute of the EventAgentNotReady, after processing a client’s self-state transition in RequestAgentNotReady. (ER# 88620221)
T-Server no longer becomes unstable when processing agent data query responses for an Any Split agent. (ER# 120664859)
T-Server no longer becomes unstable if a T-Server client invokes a TQuerySwitch request on a configuration where no extensions are configured in Configuration Manager. (ER# 160476014)
T-Server now correctly handles call scenarios where a call queued at an ACD Queue is moved to another ACD Queue or a Routing Point. Previously, T-Server failed to properly track a call in such scenarios, which resulted in incorrect event reporting. (ER# 161868582)
T-Server now correctly handles a call transfer to an ACD Split device with an agent in Ready state if the transfer completion results in an SMFN3 OAI event coming before an Infolink IV message. Previously, T-Server incorrectly processed such event sequences, which resulted in the incorrect reporting of subsequent calls. (ER# 166774313)
This section provides the latest information on known issues and recommendations associated with this product.
Due to a known T-Server problem, a backup T-Server may become unstable when operating in a high-availability (HA) configuration when a single-step transfer is made. (ER# 229991761)
| Found In: 7.6.011.00 | Fixed In: 7.6.011.02 |
T-Server may improperly clean an internal Call ID table when T-Servers operate in high-availability mode and a primary-to-backup switchover coincides with a switch link failure. (ER# 164945761)
| Found In: 7.6.003.03 | Fixed In: |
Switch limitation: Because of a limitation of CTI support of the
Recall call scenarios on Large-System NEC NEAX/APEX switches,
Genesys T-Server may incorrectly report the state of a telephony device. (ER# 25873710)
| Found In: 7.2.004.00 | Fixed In: |
Because of a CTI limitation, T-Server offers limited support for calls managed via an Attendant Console. T-Server may incorrectly report T-Library events in certain call scenarios, such as call transfers between Attendant Consoles. (ER# 13283294)
| Found In: 7.0.202.02 | Fixed In: |
In some configurations of the NEC NEAX SV7000 PABX and CallWorX (an external ACD),
there is a known deficiency of ACD behavior during an attempt to route a call to a busy destination
from a SPLIT_ROUTE_POINT device via an Infolink IF request.
T-Server receives a positive acknowledgement from the ACD, and thus cannot recognize
a call routing failure. This behavior affects external call routing to default
destinations specified in the extrouter-default-dn or router-default-dn
options. (ER# 6372854)
| Found In: 7.1.007.01 | Fixed In: |
Because of deficient Infolink messaging, T-Server does not support the call-recovery feature on Large-System NEC NEAX/APEX switches where calls distributed from a Split to an agent and not answered within a timeout determined by the switch are re-queued to the Split. In this scenario, the Infolink does not notify T-Server that the call has been re-queued. (ER# 92841)
| Found In: 7.1.001.01 | Fixed In: |
Service Observing limitations include the following:
For correct call handling by T-Server, only one Observer may monitor a call at a time.
T-Server has limited support for conferences with Service Observing. When a call is monitored, a 3-way connection is established (caller, destination, and observer) via a TCT trunk, so a simultaneous conference (that is, an additional participant) is not possible without a multi-way conference card.
To activate Service Observing via the "ACD Supervisor" feature,
the supervisor must be off-hook and must not use the SPEAKER key of a Dterm
to monitor an agent.
| Found In: 6.5.200.03 | Fixed In: |
If you must use an IP address (such as 180.170.9.150)
or a full host name including the domain name (such as server.genesyslab.com), expect to receive
a warning during the installation of any application on this host.
The warning message informs you that the installation cannot find the specified
object; as a result, the installation script does not update the configuration
data for this application. If you see this warning, continue with the installation.
After completing the installation, update the configuration data for the application you installed on this host, as follows:
Properties dialog box for the Application object in Configuration Manager. Working Directory, Command Line, and Command Line Arguments
on the Start Info tab. Apply and OK to save configuration updates. run.sh file to start the application, verify that the Working Directory,
Command Line, and Command Line Arguments are specified correctly in
the run.sh file. | Found In: 6.5.100.04 | Fixed In: |
In a T-Server multi-site environment where a call may be
routed or transferred several times between different T-Servers, the T-Server where a previous
instance of the call is still active may not preserve the Connection ID
of the call when it arrives back at this T-Server. The original Connection ID is reported
in the FirstTransferConnID attribute and can be used by T-Server, instead
of the ConnID attribute when backward compatibility mode is enabled. In
addition, the LastTransferConnID attribute contains the Connection ID
of the call from the previous location.
| Found In: 6.5.100.04 | 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.
The Solaris 2.6 operating system is no longer supported.
| Discontinued As Of: 7.6.003.03 |
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.6 T-Server for NEC NEAX/APEX Deployment Guide contains detailed reference information for the Genesys Framework 7.6 T-Server for NEC NEAX/APEX, including configuration options and specific functionality.
The Framework 7.6 Deployment Guide helps you configure, install, start, and stop Framework components.
The Voice Platform SDK 7.6 .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 this guide or contact Genesys Technical Support for additional information.
Genesys Supported Operating Environment Reference Manual contains information about supported operating systems and databases.
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.