| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.014.02 [12/16/10] – Hot Fix | X | X | ||||
| 7.6.013.00 [09/29/09] – Hot Fix | X | X | X | |||
| 7.6.012.00 [07/16/09] – Hot Fix | X | X | ||||
| 7.6.011.00 [03/19/09] – Hot Fix | X | |||||
| 7.6.010.00 [12/12/08] – General | X | X | X | X | X | X |
| 7.6.009.01 [07/24/08] – Hot Fix | X | X | ||||
| 7.6.008.02 [05/22/08] – Hot Fix | X | |||||
| 7.6.008.01 [04/23/08] – General | X | X | X | X | X | X |
| 7.6.007.02 [03/25/08] – General | X | X | X | X | X | X |
| 7.6.007.00 [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 Nortel Communication Server 1000 with SCCS/MLS.
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.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 does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly processes an ISCCRequestGetCallInfo request containing a NetworkCallID attribute, the value of which is coincidentally the same as a NetworkCallID from a previous unrelated call. Previously in this situation, T-Server sometimes became unstable. (ER# 263766920)
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:
T-Server now distributes EventQueued and EventDiverted events for controlled DNs (CDNs) managed by the software on the switch, if they are configured as type ACD Queue, and have a switch-specific Type property set to 2. (ER# 232540431)
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:
T-Server no longer registers DNs with the Register flag set to false. Previously, T-Server treated DNs, with the Register flag set to false, the same as DNs with the Register flag set to On Demand. (ER# 225133935)
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 now correctly processes a call to an external party where the switch reports the external digits as unknown. Previously, this scenario could have resulted in a dropped call and missing events when the external party completed a transfer. (ER# 220390461, 215502962)
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 release does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer receives a memory access violation for calls that use internal DNs that are not configured in Configuration Manager. (ER# 211840620)
T-Server now correctly registers addresses after a link goes down and comes back up. Previously, T-Server incorrectly throttled registration requests due to an internal tracking problem with pending requests. (ER# 210793181)
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 is a hot fix for this product. This section describes new features that were introduced in this release:
In this release, a new Switch-Specific Type of 8 has been introduced. Any DN of type Extension, which has a Switch-Specific Type of 8, will not automatically generate an EventOnHook when a call transfer or a conference call is completed.
For this new DN type, an EventOnHook is now generated only when the switch sends an on-hook event. This solves a problem with dialogic port controlled DNs, that sometimes leave a DN in an off-hook state for several seconds after a call transfer is completed. This causes synchronization issues when T-Server generates EventOnHook immediately after a call transfer or a conference call.
Note: This new DN type acts the same as the Voice Treatment Port when the vtport-generate-hook-events option is set to false.
This release does not contain any corrections and modifications.
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.07. 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 no longer incorrectly drops a call when a client disconnects from a backup T-Server, and the call is in treatment on a Routing Point. (ER# 187732438)
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.07. 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 vtport-generate-hook-events was added to T-Server:
vtport-generate-hook-events
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
When set to false, DNs configured in Configuration Manager as Voice Treatment Ports will send EventOffHook and EventOnHook only when the switch sends these events. When set to true, these DNs will behave like regular DNs and T-Server will generate EventOnHook when all parties for the DN have released, and EventOffHook when a party on the DN changes to an active state.
This release includes the following corrections and modifications:
T-Server no longer becomes unstable when performing AlternateCall when the option enable-consult-swap is set to false.
Note: T-Server will still drop parties if this option is not configured properly.
(ER# 172896821)
T-Server now sends EventLinkConnected when at least one DN registration is successful, even if a DN returns the error 202b. Previously, if a DN returned the error 202b on registration, T-Server did not send EventLinkConnected. (ER# 177513730)
T-Server now restarts the link to the switch after 30 seconds if the switch does not respond to any of the DN registration requests at startup. Previously, T-Server would only restart the link after attempting to register all DNs based on the value set for the max-attempts-to-register option. (ER# 38392753)
T-Server is built with TSCP version 7.6.008.07, which corrects ER# 182338909. For more details about the correction, see T-Server Common Part release 7.6.x. (ER# 182880793)
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 now sends an EventDestinationBusy message with a Call State of CallStateSitInvalidnum for a Progress message with a connection of Unassigned Number status type. (ER# 174888496)
T-Server now sends a release for all acquired CDNs at switchover to allow the new primary T-Server to acquire these CDNs. Previously, when a manual switchover was made, the primary T-Server did not always release all the acquired CDNs, which prevented the new primary T-Server from acquiring these CDNs. (ER# 179787061)
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. This section describes new features that were introduced in the initial 7.6 release of T-Server for Nortel Communication Server 1000 with SCCS/MLS:
T-Server now supports the Timed After Call Work (ACW) feature.
T-Server now supports the MLS IP Call Recording feature.
The new option set-discovery was added to T-Server:
set-discovery
Default Value: false
Valid Values: true, false
Changes Take Effect: After T-Server restart
When set to true, this option enables set information discovery on DN registration. If the option is set to false, T-Server will not be able to gain terminal number (TN) information at registration time. TN information is required for MLS IP Call Recording and Timed After Call Work.
Note: This option requires that Set Information Discovery is supported on the switch.
This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:
This version of T-Server incorporates changes to ensure that the Terminal Number (TN) will be properly set at login time, and for updates of agent state change notification. TN will also be automatically set if the set-discovery option is enabled and supported. These changes will help eliminate the need to configure TN for the soft wrap-up time feature. (ER# 168456874)
T-Server now properly cancels the Timed After Call Work (ACW) timer. Agents are not made Ready by T-Server if they are using the Timed After Call Work feature in HA mode after manually transitioning from Ready back to NotReady (after-call-work) after a call is released. Previously, T-Server would incorrectly change the agent state to Ready after the wrap-up time expired. (ER# 167182925)
T-Server no longer experiences problems when a consultation call to a position is reconnected within 500 milliseconds of being distributed to that position. (ER# 123699633)
T-Server now properly populates AttributeCallType and AttributeDNIS in EventPartyChanged when an inbound call is transferred from an unmonitored DN (for example, a call-pilot DN) to a monitored DN. (ER# 147265227, 162553754)
T-Server corrects a potential problem with T-Server’s party-cleanup logic for processing multiple routing requests for the same call. Previously, in some specific cases of processing a Routing Point party cleanup, it may have been possible for T-Server to enter into an infinite processing loop. (ER# 169292981)
When switching over from primary T-Server to backup T-Server, T-Server now releases calls in treatment on a Routing Point from both T-Servers. Previously, the calls would not be released in this scenario, resulting in a stuck call on the Routing Point. (ER# 72103393)
This section provides the latest information on known issues and recommendations associated with this product.
If a backup T-Server has the option enable-consult-swap set to false, and the switch has this feature enabled, backup T-Server may become unstable during a transfer completion that is performed after an AlternateCall request is processed for the consultation call. Genesys recommends that enable-consult-swap be set to true if this switch feature is enabled, and AlternateCall requests are performed. (ER# 172896821)
| Found In: 7.6.007.00 | Fixed In: 7.6.008.01 |
T-Server now supports Network Skills-Based Routing, with the following exceptions:
autoanswer
on agent DNs.| Found In: 7.0.202.00 | Fixed In: |
The option merged-user-data
specifies data that is attached to the resulting call after a call transfer,
conference, or merge completion. But when this option is set to its default
value (main-only), T-Server may lose user data after Trunk
Anti-Tromboning (TAT) if the call was initiated or transferred from an
unmonitored DN. See merged-user-data in the Framework 7.6 T-Server for
Nortel Communication Server 1000 with SCCS/MLS Deployment Guide for details.
| Found In: 7.0.202.00 | 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 that 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.101.56 | Fixed In: |
The installation script on UNIX cannot update configuration data for applications whose host computers
contain a dot (".") in their names. Therefore, when configuring a Host
object in the Configuration Database, avoid using dots in the value for
the Host Name property on the General tab.
If you have to 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 tells 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 an application you installed on this host as follows:
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.001.47 | 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.007.00 |
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 Nortel Communication Server 1000 with SCCS/MLS Deployment Guide contains detailed reference information for the Genesys Framework 7.6 T-Server for Nortel Communication Server 1000 with SCCS/MLS, 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 detailed 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.