Release Note

T-Server for Aspect ACD

8.0.x

Genesys Telecommunications Laboratories, Inc. © 2009-2011

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
8.0.100.06 [01/18/11] – General X X X X X X
8.0.001.00 [09/22/09] – General X X X X X X

Link to 7.6 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


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 Aspect ACD.

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.


Release Number 8.0.100.06 [01/18/11] – General

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 8.0.101.08. 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.1 release of T-Server for Aspect ACD.

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:


T-Server now supports the configuration of Routing Points with the DN type RouteQueue in Configuration layer. Previously, this configuration was not supported. (ER# 245565589)


T-Server now uses the PBX message Call Intermediate Event Message (CINEM) to update the call information when the Call ID changes without notification. The CINEM message is generated when the Data Interlink protocol is set to a value of 7 or greater in the PBX configuration and the step New Transaction is used in the CCT programming. Previously, CCT programming required to wrap the New Transaction step with the Send Track Data steps in order to provide correct reporting in T-Server. (ER# 244890087)


T-Server now reports the extensions key PBXTimeStampS in events when the CTI events received from the PBX contains this information. Previously, this extension key was not reported.

Note: This information is provided by the PBX only when the Data Interlink protocol set to 8 in the PBX configuration. (ER# 214052699)


T-Server no longer supports the use-track-id configuration option. A Track ID (when reported by the PBX) is now automatically assigned to the relevant call as a Network Call ID. (ER# 260261894)


T-Server now rejects the registration of a DN of more than 100 characters in length with EventError 168:'Invalid origination address'. Previously, T-Server would fail when a client attempted to register a DN of more than 100 characters in length. (ER# 239556644)


T-Server now only rejects a routing service when in backup mode and a routing device is configured in Configuration Manager, or if it has clients registered to it. Previously, T-Server, in high-availability (HA) mode, always rejected routing whether a device was configured in Configuration Manager or not, or if it had clients registered to it. (ER# 261594054)


T-Server now prevents occasional failures when connecting to Contact Server. Previously, T-Server May have failed during the connection phase if the configuration was updated. (ER# 258096348)


Top of Page


Release Number 8.0.001.00 [09/22/09] – General

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 8.0.001.15. 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 Aspect ACD.

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:


T-Server now reacts on receiving event CCM/RINGING if all parties in the call are trunk parties. Scenarios involving at least one station device are reported correctly by the PBX (Call Offered Event message is generated) so they are not reacted upon in T-Server when connected to Contact Server. (ER# 221217535)


Top of Page


Known Issues and Recommendations

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


Due to hardware limitations, a Place Call Request to #8CCT fails when using 4 digit CCTs. All transfer CCTs must be in the in the 1-999 range. (ER# 261242111)

Found In: 8.0.100.06 Fixed In: 

An ISCC call transfer between T-Servers that are connected to two different PBXs with different CTI link versions result in Trunk Thromboning. Aspect T-Servers report more than one EventPartyChanged for the same DN when the transfer is completed. This scenario will only work correctly if three T-Servers are involved. (ER# 262261255)

Found In: 8.0.100.06 Fixed In: 

The Inter Server Call Control/Call Overflow (ISCC/COF) feature is not supported if the ISCC Call OverFlow Parameter property is set to match-ani. (ER# 263487783)

Found In: 8.0.100.06 Fixed In: 

Switch-specific behavior: If the configuration option route-call-method equals CIMR-and-redir, an outbound call cannot be diverted when transferred on to a Routing Point. (ER# 262361381)

Found In: 8.0.100.06 Fixed In: 

If the configuration option route-call-method, set in the TServer section, equals CIMR-and-redir, then the RCCR method of routing is not used for an internal or a consultation call to a Routing Point. (ER# 261997871)

Found In: 8.0.100.06 Fixed In: 

T-Server does not correctly support a connection to the Aspect PBX where the Data Interlink protocol is set to 7. (ER# 261069019)

Found In: 8.0.100.06 Fixed In: 

Switch-specific behavior: If the conguration option releasing-party-report, set in the TServer section, equals true, T-Server will report the ReleasingParty information based on the information provided by the PBX. Also, if the PBX reporting is inconsistant, the T-Server reporting of the ReleasingParty information will sometimes also be inconsistant. (ER# 260678041)

Found In: 8.0.100.00 Fixed In: 

When an unmonitored DN is used to make a call, the PBX releases the call. To avoid this, use the Agent ID logged on to that DN to make a call, instead of the DN number. (ER# 227117446)

Found In: 8.0.001.00 Fixed In: 

Initiating transfer of a conference call is not supported. (ER# 226425215)

Found In: 8.0.001.00 Fixed In: 

Only the 32-bit T-Server executable can be installed on the following 64-bit UNIX operating systems.

(ER# 224639193)

Found In: 8.0.001.00 Fixed In: 8.0.100.06

In the following scenario, a TAgentSetNotReady generates two EventAgentNotReady. One has a correct REASON, but the other one is wrong.

(ER# 228874763)

Found In: 8.0.001.00 Fixed In: 

In the following scenario, when upgrading 7.0 primary (T-Server1) and backup (T-Server2) T-Servers to 8.0, T-Server2 does not synchronize with T-Server1:

(ER# 229884491)

Found In: 8.0.001.00 Fixed In: 

In the following scenario, the ReleasingParty has an incorrect value when the External DN releases the call:

  1. The releasing-party-report option is set to true.
  2. DN1 CallEstablish with external DN.
  3. DN1 InitiateConference with internal DN3.
  4. DN3 answers and a conference is established.
  5. DN1 completes conference.
  6. DN1 releases the call. In EventReleased, the Attribute Extension ReleasingParty is 1 Local. This is correct.
  7. Now the external DN releases the call.
  8. But for DN3, in EventReleased, the Attribute Extension ReleasingPart is 1 Local, which is incorrect.

(ER# 234508947)

Found In: 8.0.001.00 Fixed In: 

Aspect Call Center responds to DN Status request message ESR with ESRR status value X = Busy/Other after a physical trunk disconnect. As ESRR status value X is also used for other unavailable states, such as dialing or releasing, T-Server will not generate EventDNOutOfService to clients. (ER# 16897903)

Found In: 7.1 Fixed In:

In the following scenario, retrieval of the call via CTI is not possible. It must be retrieved manually.

  1. Internal call is Established.
  2. Place the call on Hold.
  3. Start T-Server.
  4. When checking QueryAddress results, the Held device is reported as 0 (idle).

As a workaround, T-Server clients can use Private Service 'Free the line 0 and/or 1'.

(ER# 95703, ER# 95070)

Found In: 7.1 Fixed In:

When a manual consult call is made to an invalid internal device, T-Server distributes EventHeld, then EventDialing, but no other event is generated to indicate call failure, because the switch reports abandoned. (ER# 100889, ER# 100890).

Found In: 7.1 Fixed In:

In the following scenario, T-Server does not show any call information, but displays the agent as Not Ready:

  1. Agent logged in and Ready.
  2. Either establish a call or press one of the line buttons.
  3. Start T-Server.

(ER# 101005, ER# 101010)

Found In: 7.1 Fixed In:

When the Event Party Propagation (EPP) feature is activated and single-step transfer is used, Aspect T-Server does not distribute EventPartyChanged on a remote location. (ER# 91309, ER# 91778)

Found In: 7.0.203.06 Fixed In:

At startup, T-Server recognizes when trunk lines are unavailable. However, as no status change message is provided by the switch, T-Server cannot correctly reflect trunk synchronization. (ER# 97402, ER# 16897317)

Found In: 7.0.2 Fixed In:

The ISCC feature with cast type direct-ani is supported but limited. The supported scenarios are:

No other scenario is supported. (ER# 60848)

Found In: 7.0 Fixed In:


In release 9.1.1 and higher of the Aspect ACD, the default configuration parameters for consult calls have been changed. Previously, the default maintenance flag #9 was set to on (checked). From release 9.1.1 the default setting of maintenance flag #9 is off (unchecked).

With the 9.1.1+ default setting (off) it may be necessary to press a phoneset key at the end of a consult call in order to come out of permanent ACW, or before being able to continue.

Please note that this parameter can normally be changed only by Aspect Engineering personnel. (ER# 128670380)

Found In: Aspect ACD 9.1.1 Fixed In:

Alerting calls cannot be released in the Aspect switch. (ER# 35449788)

Found In: Aspect 9.1 CS 5.2 Fixed In:

On Aspect 9.x ACD, when one analog phone calls another, the switch does not report anything except CDEM when the phones are placed on hook. (ER# 33227139)

Found In: Switch version 9.1 Fixed In:

On Aspect 9.x ACD, TAgentNotReady when an agent is already in NotReady state places the agent into Ready state. (ER# 31945167)

Found In: Switch version 9.1 Fixed In:


Outbound calls from analog devices to invalid numbers might be reported as busy by the switch. (ER# 92766, ER# 92765)

Found In: Switch 8.4_SP01_CM03 Fixed In:

Calls via CTI from analog sets cannot be answered via CTI. (ER# 60770)

Found In: Switch version 8.4 Fixed In:

CTI monitoring and control of analog extensions is limited with the Aspect switch.

(ER# 60764, ER# 88368)

Found In: Switch R 8.4, CS 5.2 Fixed In:

In two-step transfer scenarios, the switch does not allow blind transfer. As a result, the consultation call has to be answered before the transfer can be completed. (ER# 78197, ER# 78271)

Found In: PBX 8.4, CS5.2 Fixed In:

The switch can only single-step transfer a call if at least one of the parties in the main call is a trunk party (for example, inbound call or outbound call followed by single-step transfer to an agent). (ER# 78198, ER# 78272)

Found In: PBX 8.4, CS 5.2 Fixed In:

Blind transfer, mute transfer, redirect, divert, forwarding and internal single-step transfer are not supported. Consultation calls to Routing Point (Inbound/Outbound only), and single-step transfer (Inbound/Outbound only) have limited support. (ER# 25000141)

Found In: Unspecified Fixed In:

DTMF cannot be sent from a conference controller. (ER# 107848526)

Found In: Unspecified Fixed In:

Four-party conference is not supported. (ER# 107848335)

Found In: Unspecified Fixed In:

Parties can only be deleted from conference with DN Number, not with Agent Login ID. (ER# 104162626)

Found In: Unspecified 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.


Application Bridge connectivity is no longer supported. Please use Contact Server for Genesys integrations.

The following configuration options in the TServer section have been removed and are no longer in use:

(ER# 264766171, 262979511)
Discontinued As Of: 8.0.100.06

HP-UX 11.00 is no longer supported.

Discontinued As Of: 8.0.001.00

Solaris 7 is no longer supported.

Discontinued As Of: 8.0.001.00

Windows 2000 is no longer supported.

Discontinued As Of: 8.0.001.00

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. Please consult the Deployment Guide first.

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.

Top of Page