Release Note

Contents

Introduction

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 INDeX.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 8.0.x.
• Your T-Server’s name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

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

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

• Enhanced multi-site support for CallType propagation: T-Server now supports a CallType attribute propagation in multi-site deployments. This functionality can now be controlled with the propagated-call-type configuration option. See your T-Server Deployment Guide for details.

• Support for call release tracking: T-Server now provides information about which party initiated the release of a call. This can be valuable for different applications to provide historical and real-time call reporting. This can be configured using the new configuration option releasing-party-report.

• Support for failed route notification: T-Server now supports alarm messages for unsuccessful routing scenarios.

• Support for link bandwidth monitoring: T-Server now provides bandwidth monitoring on a CTI link and can notify the Genesys Management Layer when Configuration Layer limits are exceeded.

• Support for enhanced request handling: T-Server introduces two major new enhancements to queue handling: request conflict resolution and a new device queue.

• Enhancements to emulated agent functionality: The Emulated Agent feature has a number of enhancements, including:

  • Agent logout on client unregistering from a DN.
  • Changes to legal guard processing.
  • The addition of password functionality to agent-strict-id.
  • Synchronization of emulated after call work (ACW) for emulated agents.

• Enhancements to business call processing: A new configuration option, agent-only-private-calls, enables you to specify whether calls distributed from a device are considered as private or business calls.

• Improvements to T-Server logging performance have been implemented.

• T-Server now supports VMWare, but only the Windows 2000 and Windows 2003 operating systems are supported on T-Server for Avaya INDeX.

• T-Server now supports switch version 11.0.1 and 11.0.4.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:

The switch no longer generates unpredictable reactions to single-step transfer requests. (ER# 84235)

The switch now allows completion of a call transfer or a conference call for a picked-up call. (ER# 86433)

Top of Page

Known Issues and Recommendations

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

The PBX will release a call in the following scenario:

1. A call is made from DN1 to DN2.
2. The call is answered by DN2.
3. DN2 makes a consultation call to an Emulated Routing Point.
4. The Emulated Routing Point routes the call to a busy destination.

(ER# 241620391)

Customers who are using Management Layer 8.0 and want to run T-Server on Windows 2000 need to install LCA 7.6 on the T-Server host. (ER# 241919155)

T-Server does not create an EventDialing event when making a call to an InvalidDestination. In this scenario, the PBX does not provide sufficient call information to T-Server, which results in the creation of EventOffHook and eventually an EventError after a timeout occurs. (ER# 241155058)

In the following scenario, when using Supervised routing over a QSIG trunk to a Hunt Group (HG), and a HG member answers the call, the call remains on the Emulated Routing Point (ERP).

1. Supervised routing is set.
2. A call is made to the ERP.
3. The call is routed to a HG on a QSIG trunk, and rings on the HG members.
4. The call is answered after one toggle.
5. The call remains on the ERP.

Note: This limitation is applicable for Network Hunt Group only.

(ER# 241105776)

The installation of T-Server using the Wizard is not supported for this release. (ER# 241036451)

In scenarios where the primary T-Server is version 7.0 and the backup T-Server is version 8.0, there is no EventLinkConnected message on the backup T-Server when both the primary and backup T-Servers are started. This is a backward compatibility limitation between version 8.0 and 7.0 of T-Server. (ER# 240033237)

In the following scenario, no wrap-up time is applied for the real agent once the call is released.

Primary T-Server is version 8.0.
Backup T-Server is version 7.0.
wrap-up-time option is set to a value higher than 0.

1. Start primary and backup T-Server and wait for the EventLinkConnected message on both T-Servers.
2. Make business call to a real agent.
3. Switchover is performed on the T-Servers.
4. The call is answered.
5. The call is released.

This is a backward compatibility limitation between version 8.0 and 7.0 of T-Server. (ER# 240064900)

The partitioning feature is not supported on T-Server for Avaya INDeX. (ER# 176865731)

In the following scenario, T-Server incorrectly generates a RemoteConnectionFailed message for the first leg of the TMakeCall request in step 1 and 2 once the entire call has been released.

1. Agent1 on T-Server1 makes an ISCC call to agent1 on T-Server2.
2. Agent1 on T-Server2 answers the call (RemoteConnectionSuccess).
3. Agent1 on T-Server2 makes an ISCC-SST call to agent2 on T-Server1.
4. Agent2 on T-Server1 answers the call.
5. Agent2 on T-Server1 releases the call.

(ER# 240188479)

When duplicated locations are configured for different rule-sets implemented in a non-restrictive manner, T-Server accepts the first location, and issues a warning in the log about duplicated location configured. (ER# 240016801)

If the switch reboots and comes back in service while T-Server is running, clients will not be able receive calls or make calls (no switch devices can be used). T-Server must be restarted for clients to synchronize with the switch devices. (ER# 240702701)

CTI (computer-telephony integration) requests sent to the switch with the extension key ReasonCode are not supported. (ER# 240852030)

In the following scenario, where both a primary call to the Hunt Group (HG) is using a DPNSS trunk and the call is toggling between the HG members on the DPNSS trunk, incorrect reporting is received from the switch which creates incorrect events and party states on T-Server.

1. A call is made on a DPNSS trunk to a HG.
2. The call is ringing on the HG members (the call is not answered).
3. The call toggles between the HG members using the DPNSS trunk.

Note: This limitation is applicable for Network Hunt Group only.

(ER# 241105681)

It is not possible to snapshot devices on the INDeX PBX. Therefore if there is a call on a device at T-Server startup, T-Server cannot report it. (ER# 175007376)

Four-party conferences are not supported. A maximum of three parties can be conferenced via CTI. (ER# 178566824)

It is not possible to delete external parties from a conference. (ER# 180579039)

The PBX supports no queries (device states, agent states and so on) from T-Server. (ER# 176744014)

The PBX drops a call that has been redirected to an invalid device or a busy device. Consequently, any chained No-Answer Supervision call that involves either of these device states will result in the call being dropped rather than redirected to the next target in the chain. (ER# 176744028)

The INDeX PBX assumes that all DNs are monitored. So, T-Server does the same. As a result, creating a device in Configuration Manager with option register set to value false will result in T-Server ignoring the value and registering the device with the switch. Because of the way the switch behaves, such registrations will always be successful. (ER# 177611915)

Avaya INDeX T-Server is only available for Windows 2000 and Windows 2003 platforms. Support for WIndows NT is removed in 7.6. (ER# 84497, 176858735)

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. There are no discontinued support items for this product.

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 Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

• The Framework 8.0 T-Server for Avaya INDeX Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Avaya INDeX switch including configuration options, known limitations, and switch functionality.
  

• The Framework 8.0 Deployment Guide helps you configure, install, start, and stop Framework components.

• The Voice 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.

• 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.

Top of Page