Release Note

Contents

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 Siemens HiPath DX.

• 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 Guide.
• 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 third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.

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.101.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 any new features or functionality.

Corrections and Modifications

This release also includes the following correction and modification:

T-Server now correctly reports the remote endpoint in the reported OtherDN attribute in events after an EventNetworkReached event for consultation calls to external parties. Previously, T-Server reported the Trunk ID as the OtherDN attribute after an EventNetworkReached event, instead of the remote endpoint in the OtherDN attribute. (ER# 317186337)

T-Server now ignores any released parties in newly created service initiated calls. Previously, T-Server was confused by a party from a previously released call (the Call Locking feature) in the creation of a new consultation call. (ER# 316801394)

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly handles a scenario where a native agent returns from an unsynchronized ACW. The required event is now generated when the requested agent state already matches the agent's event on the switch. Previously, T-Server treated this return as an extend ACW request and incorrectly generated EventAgentNotReady with workmode = 3 (AgentAfterCallWork). (ER# 266384636)

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 8.0.101.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 section describes new features that were introduced in the initial 8.0.1 release of T-Server for Siemens HiPath DX.

• T-Server now supports the synchronization of emulated agent states with the switch. (ER# 99749341)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly reports the work mode in EventAgentNotReady when TAgentNotReady/ACW is requested from the idle state. Previously, in the same scenario, T-Server reported AttributeAgentWorkMode with the value Unknown. (ER# 260468752)

T-Server now provides a workaround for the correct reporting information when the switch reports duplicate Not Ready events as a result of executing TAgentNotReady on a native agent. T-Server now disregards the second message if it is a duplicate. Previously, T-Server reported two EventAgentNotReady messages based on the switch reporting. (ER# 243990743)

T-Server now correctly supports a scenario where a call is routed from a device that is defined as a Routing Point in Configuration Manager, but represents a station device in the switch configuration. Previously, T-Server rejected TRouteCall requests from such a device with the EventError message: not supported. (ER# 253813691)

T-Server now correctly handles the self-transition of agent states from Logout to Logout on Agent DNs. Previously, T-Server reported an EventError message if an AttributeThisQueue attribute was specified in a TAgentLogout request. (ER# 253617321)

T-Server now correctly handles the self-transition of agent states from NotReady to NotReady on Agent DNs. Previously, T-Server may have omitted adding an AttributeReferenceID attribute to the resulting event and provided the incorrect agent work mode. (ER# 263235088)

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

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

With the configuration option use-native-routing set to a value of true, T-Server now maintains the correct behavior so that EventRouteRequest is not sent to T-Server clients until the PBX reports that the routing dialogue is open. Previously, after a DN reconfiguration, T-Server would incorrectly start to send EventRouteRequest before the PBX reported the routing dialogue as open, and any request to route the call prior to the routing dialogue being opened would be rejected by T-Server by responding with an Unsupported operation error. (ER# 261559709)

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 8.0.101.01. 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 Siemens HiPath DX. Refer to Framework 8.0 T-Server for Siemens HiPath DX Deployment Guide for feature descriptions.

• T-Server now supports enhanced business call processing. This can be configured using the configuration option agent-only-private-calls.

• T-Server now supports enhanced emulated agent functionality.

• T-Server now supports a call type prediction procedure to assign a call type on a "best guess" basis in those scenarios where the CTI information is either insufficient or arrives too late for T-Server to assign a definite call type.

• T-Server now supports call release tracking to provide information about which party initiated the release of a call. This can be configured using the releasing-party-report configuration option.

• T-Server now supports alarm messages for unsuccessful routing scenarios.

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

• T-Server now supports two major new enhancements to queue handling: request conflict resolution and a new device queue.

• T-Server now supports improvements to logging performance.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.2 or earlier releases and the initial 8.0 release of T-Server for Siemens HiPath DX:

T-Server now reports the correct agent status for real agents if the registration or query was performed during the agent login stage. Previously, T-Server may have reported the key AgentStatus with a value of 0 (zero) in EventRegistered/EventAddressInfo if the registration or query was performed before an agent was logged in and assigned a state in the PBX. (ER# 224176157)

T-Server now reports the correct call state in EventNetworkReached on origination when a call is redirected to an external destination. Previously, T-Server incorrectly reported CallStateRedirected. (ER# 179268185)

T-Server now correctly handles TAgentLogin with Hot Desking when AgentID conversion is enabled. The valid value for the configuration option convert-otherdn must be set to +agentid to enable this conversion. Previously, T-Server sometimes became unstable. (ER# 137373915)

T-Server now reports the key AgentStatus in AttributeExtension for EventRegistered and EventAddressInfo as 0 (zero) (logged out) after the start-up for an extension with a logged-out agent. Previously, T-Server sometimes reported a value of -1 (unknown). (ER# 135788851)

T-Server now correctly handles the No-Answer Supervision list of overflow destinations according to the specifications set in the configuration option agent-no-answer-overflow. Previously, T-Server did not stop processing of overflow targets if the current target was none. (ER# 132710851)

T-Server now correctly processes mute transfer requests from a trunk. Previously, T-Server used two-step transfers for trunk devices that were not configured in Configuration Manager or configured as Extensions. (ER# 122252067)

T-Server now correctly deletes parties from a device going into an idle state. Previously, T-Server sometimes became unstable when a device went on hook and the device party was deleted immediately after. (ER# 109641333)

T-Server now correctly rejects TAttachUserData and TUpdateUserData requests from an idle agent where AttributeConnID was set to 0 (zero). Previously, T-Server incorrectly suppressed the EventError. (ER# 109641316)

T-Server now correctly rejects TPrivateService for setting account code (0xcb03) with EventError if the execution of private service is disabled by the configuration option accode-privateservice. Previously, T-Server executed the request regardless of the option value and did not generate a corresponding event for the client. (ER# 109641029)

The primary T-Server now synchronizes the emulated agents that are logged in to a backup T-Server when it starts. T-Server also synchronizes the emulated agents if there is an interruption of the connection between the primary and backup T-Servers. (ER# 99749271)

This release corrects the following Known Issues: ER# 84286831, 52615583, 52605982, 49227348, 99954759, 86395598, 85649716, 123332962, 93245, 7504601, 50839, and 93170.

Top of Page

Known Issues and Recommendations

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

Framework 8.0 T-Server for Siemens HiPath DX Deployment Guide currently states that a single Virtual DN can be used as a Routing Point. T-Server for Siemens HiPath DX currently does not support this functionality. (ER# 253813691)

Switch-specific behavior: If an attempt is made to pick up a call from hold, it may result in a stuck call in the PBX that T-Server is not able to recover or control. (ER# 253749295)

Switch-specific behavior: The PBX may send unsolicited EventHeld and EventRetrieved events on the routing destination in the following scenario:

1. A call is made from one PBX node to another.
2. The call arrives at the destination node.
3. The call is transferred by using a single-step transfer to a Routing Point on the destination node.
4. The call is then routed back to the origination node.

(ER# 253749287)

Switch-specific behavior: The PBX may drop the call in the following scenario:

1. A call is made from one PBX node to another.
2. The call arrives at the destination node.
3. The call is transferred by using a two-step transfer to a Routing Point on the destination node.
4. The call is then routed back to the origination node.

(ER# 252636621)

Switch-specific behavior: In a scenario where a conference controller on PBX node 1 has created a conference with two participants on PBX node 2, and then the conference controller hangs up, the PBX may update the call information for one or both remaining parties resulting in a T-Server Connection ID change. (ER# 252514828)

Switch-specific behavior: If a call is made from DN1 on PBX node 1 to DN2 on PBX node 2, and then DN1 executes a single-step transfer to DN3 on node 2, the PBX may incorrectly report the call ringing on DN3. (ER# 252514786)

Switch-specific behavior: The PBX distributes EventHeld after:

• A conference is completed
• After a complete transfer and release on any primary call

(ER# 123332962)

When a nonsupervised route is made from an emulated Routing Point, the PBX replies with the following incorrect sequence to T-Server:

1. PBX sends an acknowledgement for service.
2. PBX sends an event OnHook for the member of a Routing Point.
3. PBX sends an event Diverted.

Switch-specific behavior: It is incorrect to send OnHook before the Diverted. The Diverted event should come before the OnHook. This error causes T-Server to report that the call has been abandoned on the Routing Point rather than EventRouteUsed/Diverted. (ER# 84286831)

Switch-specific behavior: Sometimes the switch does not generate EventDiverted after a redirect, when a non-supervised call is routed externally, but reports EventError instead. (ER# 52615583)

In the following scenario before step 5 (DN2 TAnswerCall), T-Server generates EventReleased for External DN1:

1. DN1 TMakeCall to external DN1.
2. External DN1 RequestAnswerCall.
3. DN1 RequestMuteTransfer to internal Routing Point.
4. Routing Point RequestRouteCall to DN2.
5. DN2 TAnswerCall.
6. T-Server generates EventEstablished for DN2.

(ER# 52606096)

Switch-specific behavior: In the following scenario (conference from external DN to Routing Point), the call on the destination is recreated by the switch:

1. External DN1 makes call to External DN2.
2. External DN2 TInitiateConference to CDN1 and routes to DN2.
3. DN2 answers.
4. External DN1 completes.
5. External DN1 releases the call.

At this point, External DN1 releases the call, DN2 reports EventReleased, EventDialing, EventNetworkReached and EventEstablished.

(ER# 52605982)

Switch-specific behavior: The switch does not report agent status correctly after a switch reboot, unless the call is made to a DN that is logged in and ready. (ER# 49227348)

Inter Server Call Control/Call Overflow (ISCC/COF) with a single-step transfer is not supported on the T-Server. T-Server only supports emulated single-step transfer, not native single-step transfer. (ER# 49174651)

Switch-specific behavior: The primary call leg is not reported after a link disconnect/reconnect. The PBX protocol is limited and does not report correctly the state of the party on the origination device (when the other is on hold) to T-Server, thus the primary call between DN1 and DN2 is not reported. (ER# 99954759)

Switch-specific behavior: When an inbound call is redirected to a queue, the PBX fails to provide DN3 in the redirect response to T-Server's request. (ER# 86395598)

Switch-specific behavior: When an inbound call is redirected to an ACD Queue the PBX fails to provide DN3 in the redirect response to T-Server's request. This means that if an inbound call is routed without supervision from an emulated Routing Point, T-Server generates the following call flow on the Routing Point:

1. TRouteCall (RefID nn)
2. EventRouteUsed (no RefID)
3. EventDiverted
4. EventError 'call has disconnected' (RefID nn)

(ER# 85649716)

Switch-specific behavior: In the redirect and route scenarios below, either the primary outbound or inbound leg is released, then goes into Dialing state.

Redirect scenario:

1. A makes outbound call to B
2. B answers.
3. A single-step transfers to internal C.
4. C redirects to internal D.
5. Primary outbound leg (A) is released, then goes into Dialing state.
6. D answers.
7. Call established with A.

Routing scenario:

1. A makes outbound call to B.
2. B answers.
3. A mute-transfers to CDN.
4. CDN routes to internal C.
5. Primary inbound leg (B) is released, then goes into Dialing state.
6. B answers.
7. Call established with C.

(ER# 55716)

Switch-specific behavior: Unsolicited events on a predictive dialing device are reported as-is, because after the predictive call request is completed, there is no more information about the Queue/Routing Point on which the call has been requested. (ER# 93245)

Switch-specific behavior: Whenever a call (internal, inbound, outbound or consultation) is routed to an ACD Queue, or whenever a call is routed to an external number, no EventRouteUsed is distributed. After the TRouteCall, the call is released between the calling DN and the Routing Point and also abandoned on the Routing Point. This means that a new call is generated against the queue/external number and no EventRouteUsed is distributed. It also means that any attached data is lost. (ER# 7504601)

Switch-specific behavior: When you log out a personal number, set the device out of service, then initiate a single-step transfer to that personal number, the switch distributes EventRinging for the personal number, when physically the device is not ringing. (ER# 50839)

Switch-specific behavior: Call Forward can only be activated manually on the phone set on the HiPath PBX so T-Server is unable to report callstate=Forwarded on EventReleased and EventRinging. However, T-Server does report callstate=Redirected or callstate=OK. (ER# 52615622)

Switch-specific behavior: T-Server reports EventReleased at the primary origination DN when answering an externally routed call in the following scenario:

1. B makes an inbound call to A.
2. A answers the call.
3. A single-step transfers the call internally to a native Routing Point.
4. A completes the transfer.
5. The native Routing Point routes externally to C.
6. C answers the call.
7. B reports EventReleased even though the device is still on the call and the PBX sends a Connection Cleared event.

(ER# 771135)

Switch-specific behavior: The two following scenarios cause problems with phantom calls and the call states of dropped calls:

Scenario A:

• Make an outbound call.
• Single-step transfer the outbound leg to an emulated Routing Point.
• Route to an internal DN.
• Before the supervised route timeout expires, drop the external party.

If the call is not dropped immediately, when calls are cleared, a phantom call is left on the Routing Point.

Scenario B:

• Make a predictive call.
• Answer the call.
• The call is queued because all agents are busy.
• Release the external party.

The call is not dropped on the queue until the timeout in prd-dist-call-ans-time expires, and then drops with call state Dropped. The call should be dropped immediately with call state OK.

(ER# 93170)

When T-Server attaches user-to-user information (UUI) data to a consultation call request, then sends the UUI data to the destination side, the received UUI data does not correspond to that on the origination side. (ER# 253739081)

Switch-specific behavior: The Trunk ID information is missing in the second mute-transfer request in the following scenario:

1. A call comes from the external trunk to the native Routing Point.
2. A call is routed to DN1 on another PBX (PBX1) via the internal trunk.
3. DN1 answers and requests a mute-transfer back to the native Routing Point.
4. T-Server reports a transfer from the external trunk instead of the internal trunk.
5. A call is routed back to DN2 on PBX1 via the internal trunk.
6. DN2 answers and requests a mute-transfer back to the native Routing Point. At this point, the mute-transfer fails because the correct Trunk ID is missing.

(ER# 149454413)

Call tracking can be lost when a call without Automatic Number Identification (ANI) is routed. The Connection IDs can change when routing occurs before switch optimization of call circuits takes place. (ER# 41514)

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 features or functions for this product.

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.

• Framework 8.0 T-Server for Siemens HiPath DX Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for Siemens HiPath DX including configuration options and specific functionality.

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

• The Platform SDK 8.0 .NET (or Java) API Reference and the Genesys Events and Models Reference Manual contains the T-Library API, information on TEvents, and an extensive collection of call models.

• Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

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