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 7.6 releases of T-Server for EADS Intecom M6880.

• 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 Systems and Databases 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 7.6.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 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 release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now attempts to reconnect to the link if the switch rejects the opening of the DB channel by sending the DB_REJECTION message. Previously, during the reconnection process, T-Server incorrectly analyzed this switch message, and did not attempt to reconnect to the link. (ER#s 184294459, 166068400)

T-Server now correctly processes the following scenario:

1. DN1 of type ACD Position or Extension is incorrectly registered in the Configuration Layer as a DN of type ACD Queue or Routing Point.
2. An internal call is initiated from DN1 to an ACD Queue.
3. The ACD Queue diverts the call to a local agent.

Top of Page

Supported Operating Systems

New in This Release

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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly processes a malformed CIM: XFER_REVERT switch message with the mandatory CallID attribute missing. Previously, when processing the transfer reversion scenario, T-Server could not resolve such a malformed switch message, and became unstable if it had a stuck call at a DN from which a transfer was initiated. (ER# 176848282)

When processing a malformed CIM: XFER_CANCEL switch message with missing mandatory attributes, such as transferred call party information and CallID, T-Server no longer becomes unstable. It now validates the presence of mandatory attributes and ignores such malformed switch messages. If such a malformed message refers to an existing call, a stuck party may be left in T-Server's memory. (ER# 175152430)

T-Server now processes blind transfers from remote agents even when CIM: ON_HOOK switch messages for trunks are not sent. Previously, if there were calls on trunks that could not be resolved because of missing CIM: ON_HOOK switch messages, T-Server could process the blind transfer incorrectly and became unstable. (ER# 175403441)

Top of Page

Supported Operating Systems

New in This Release

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

• Support for Call Parking. T-Server now supports the Call Parking feature that allows users to park a call on a special device called a parking channel. Refer to your T-Server Deployment Guide for more information.

• A new configuration option, on-hook-after-parking, has been added in this release of T-Server to support Call Parking.

• Support for Ring-No-Forward. T-Server now supports the Ring-No- Forward (RNF) feature that can be configured on an ACD pilot. With this feature enabled, if a call is sent to an available agent and the agent fails to answer the call within a predefined time period, the call is placed back in the queue and the agent is signed out.

• Enhanced single-step call transfer functionality. T-Server now supports TSingleStepTransfer requests for internal calls from IVR ports.

Corrections and Modifications

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 no longer becomes unstable after receiving the CIM: CALL_QUEUED switch message when a call is initiated from an extension, that is mistakenly configured as a DN of type ACD Queue in Configuration Manager, to another DN of type ACD Queue. (ER# 156451361)

T-Server now correctly processes sequences of two or more TRouteCall requests and reports the ReferenceID attribute in the EventRouteUsed messages. (ER#s 161438159, 162929612)

When an agent is in the Not Ready state and a client sends the RequestAgentNotReady with another ReasonCode, T-Server now rechecks the agent state on the switch and updates the ReasonCode data. Previously, T-Server sent the TAgentSetNotReady request, which was ignored by the switch, and as a result, the ReasonCode updates were delayed. (ER# 22378670)

T-Server no longer incorrectly distributes the EventEstablished message instead of EventDiverted or EventRouteUsed, if the destination of a predictive call is an agent DN forwarding calls to a Queue or a Routing Point. (ER# 103687874)

Top of Page

Known Issues and Recommendations

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

In call-pickup scenarios, the following issues have been found:

• T-Server distributes the EventAbandoned message instead of EventReleased with AttributeCallState set to Pickedup.
• T-Server correctly processes RequestAnswer, but it incorrectly distributes EventError in a response.

(ER# 73494922)

Switch limitation: The SPEAKER function cannot be activated for a call that was answered or retrieved via a CTI application if the handset is in the off-hook position. (ER# 43932107)

With some switch configurations, T-Server may not report messages properly in this scenario:

1. Agent A makes a call to Agent B.
2. Agent A attempts to make a conference with Agent B on a second line.
3. Agent B puts the first call on hold, and answers the second call.
4. Agent B puts the second call on hold.

After T-Server attempts to release both calls, the phone of Agent A may become connected to itself. The phone can then only be restored to an idle state manually. (ER# 88072)

When a call is forwarded automatically by the switch because of a no-answer time-out setting, T-Server generates EventAbandoned instead of EventReleased. (FR# 48926)

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.

The Solaris 2.6 operating system is no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers. There are no known internationalization issues for this product.

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.

• The Framework 7.6 T-Server for EADS Intecom M6880 Deployment Guide contains detailed reference information for the Genesys Framework 7.6 T-Server for EADS Intecom M6880, including configuration options and specific functionality.

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

• The Genesys 7 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.6 .NET (or Java) API Reference contains technical details of T-Library functions.

• The Genesys 7 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 7 Supported Operating Systems and Databases contains information about supported operating systems and databases.

Top of Page