Release Note

T-Server for EADS Telecom M6500 Succession

7.5.x

Genesys Telecommunications Laboratories, Inc. © 2007–2015

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
7.5.001.03 [02/03/12] – Hot Fix           X
7.5.001.02 [07/15/08] – General X X X X X X
7.5.000.09 [02/15/08] – Hot Fix       X   X
7.5.000.07 [12/13/07] – Hot Fix       X   X
7.5.000.05 [07/20/07] – General X X X X X X

Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

This release note applies to all 7.5 releases of T-Server for EADS Telecom M6500 Succession.

Note: Genesys follows applicable third party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties.


Release Number 7.5.001.03 [02/03/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.5.010.05. 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.

Corrections and Modifications

This release includes the following corrections and modifications:


This release of T-Server corrects the following TSCP issue:

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, 291052074)


Top of Page


Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.5.010.02. 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 contains the following new features and functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server has been modified to handle unexpected switch reporting for calls transferred between DNs that are monitored by different T-Servers connected to the same switch. Now, T-Server will not fail in this scenario and will attempt to correct the reporting. (ER# 193496670)


T-Server has been modified to ensure that agent states remain correctly synchronized between T-Server and the switch after the release of a business call. (ER# 194154065)


A workaround has been implemented in T-Server to ensure correct release of a held connection irrespective of the completeness of switch reporting. (ER# 193524128)


Monitor Stop functionality has been implemented in T-Server. (ER# 190522551)


Top of Page


Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.5.010.02. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server has been modified to correct a problem with inbound calls being seen as outbound when they come from an IVR. Now, when a call is transferred from an unmonitored device, T-Server will create a new call with type Unknown (if required) and will keep the type until the call is disconnected. Also, if, during a transfer to a monitored device, the origination party of the primary call is changed (for example, due to unexpected PBX reporting) T-Server will not change the reported digits of the external party. (ER# 170748179)


Top of Page


Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.5.010.02. 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 contains the following features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server has been modified to correct a problem with incorrect call types after TCompleteTransfer when a call is transferred via ISCC. Previously, the call arriving at the remote destination was being reported with call type Unknown, and has now been corrected to show call type Inbound. (ER# 166707395)


A problem with an incorrect call state in call release scenarios has been corrected. Previously, when a party resided on a VTO-type device in established state and the call was released remotely, T-Server reported CallStateRemoteRelease in EventReleased. Now, in such scenarios, EventReleased is reported with CallStateOk. (ER# 150481157)


Support for private data has been implemented in order to enable UUI data to be provided in events. If an event reported by the PBX contains a private data field, T-Server will attach the key GCTI_MATRA_PRIVATE_DATA to the call related to the event. Due to a limitation in the CSTA protocol, the maximum size of the key value is 32 characters. Additional characters will be cut. T-Server trims the string from the private data field, removing trailing blanks, then adds the key to User Data. (ER# 165683007)


A problem with failure of THoldCall has been corrected. Now, T-Server makes additional checks on party states in processing Hold requests. (ER# 165730728)


Top of Page


Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.5.009.00. 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 section describes new features that were introduced in the initial 7.5 release of T-Server for EADS Telecom M6500 Succession:

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


The PBX does not allow a chained consult call to be answered. (ER# 176600493)

Found In: 7.5 Fixed In:


An unexpected EventError (Internal T-Server timeout) is generated when a correct EventReleased event arrives after a consult call is released. This is caused by T-Server requesting Release Call when the PBX has already released the call.

Because there is no mechanism to distinguish between the release of a call due to request and the release of a call by the PBX, T-Server clears the request using EventError. (ER# 141446967)

Found In: 7.5 Fixed In:


T-Server generates an extra EventRouteRequest when moving a call between Hunt Group members. (ER# 136383048)

Found In: 7.5 Fixed In:


You cannot send a parked call to other devices. (ER# 128861814)

Found In: 7.5 Fixed In:


The switch Secret Identity feature is only applicable at the switch level, and is not applicable via the CTI link. (ER# 123331822)

Found In: 7.5 Fixed In:


CallForward does not report call state Forward in EventRinging on the destination DN. (ER# 88098999)

Found In: 7.5 Fixed In:


No events are generated over the link to indicate a CallBack in Progress scenario. (ER# 94388683)

Found In: 7.5 Fixed In:


Call control is lost if the call is created before the backup T-Server is started, then switchover takes place. (ER# 119670378)

Found In: 7.5 Fixed In:


It is not possible to snapshot devices on the PBX. Therefore if there is a call on a device at monitor start, T-Server is unable to report it. (ER# 85298668)

Found In: 7.5 Fixed In:


When an analog phone is left off hook for 3 minutes, the switch generates a Connection Cleared event, triggering an OnHook message from T-Server. However the DN is still off hook and cannot receive calls. (ER# 124682008)

Found In: 7.5 Fixed In:


ConnID is not maintained on a remote T-Server:

Found In: 7.5 Fixed In:


IP hard phones are not supported. (ER# 84489)

Found In: Not applicable Fixed In:


The switch does not report any event when a phoneset is unplugged or plugged in. Hence, T-Server cannot provide events such as EventDNBackInService and EventDNOutOfService. (ER# 59151)

Found In: 7.0 Fixed In:


Top of Page


Discontinued Support

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.


Solaris 2.6.

Discontinued As Of: 7.5


Top of Page


Internationalization

Information in this section is included for international customers. There are no known restrictions specific to international customers.

Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

  • The Framework 7.5 T-Server for EADS Telecom M6500 Succession Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the EADS Telecom M6500 Succession switch including configuration options, known limitations, and switch functionality.

  • The Framework 7.5 Deployment Guide provides instructions for installing and configuring Framework 7.5 components and provides instructions for starting and stopping the Framework 7.5 components either using the Management Layer or manually.

  • The Voice Platform SDK 7.5 .NET (or Java) API Reference and the Genesys 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 the guide, or contact Genesys Technical Support for additional information.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

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.

Top of Page