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 Siemens HiPath 4000 CSTA III.

• 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.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 Siemens HiPath 4000 CSTA III.

• Support for Siemens HiPath 4000 UV5.0 is announced in this release.

• Support for call type prediction: On occasions when the CTI information is either insufficient or arrives too late for T-Server to assign a definite call type, T‑Server can now use a call type prediction procedure to assign a call type on a "best possible guess" basis.

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

• Support for new operating systems: The following new operating systems are supported:

  • IBM AIX 64-bit version 6.1.
  • HP-UX/PA 64-bit version 11i v3.
  • Red Hat Enterprise Linux AS Edition on 32-bit Intel platforms, version 5.0.
  • Windows 2008.
  • VMWare.
  • Sun Solaris Containers.
  • IBM PowerVM LPAR.

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 correctly handles delayed link startup (ha-sync-dly-lnk-conn set to true). Previously T-Server sent EventLinkConnected properly but did not set its internal status to link connected. Because of this, when the backup T-Server became primary, and the link went down, it did not send link disconnected. (ER# 228935318)

T-Server no longer becomes unstable when an internal request is reinvoked. (ER# 221258705)

A single-step transfer to an external destination no longer produces two NetworkReached events. (ER# 32164520)

T-Server now reports the correct conference states and roles on the remote T-Server when a conference is created using ISCC, with Event Party Propagation activated. (ER# 105674573)

Top of Page

Known Issues and Recommendations

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

Beginning with release 8.0, T-Server has an improved CTI request pacing mechanism, which is controlled by the new option device-rq-gap. The default value of this option is 250 milliseconds, which limits the number of requests sent to the switch to 4 requests per second on any given device.

In scenarios where a version 8.0 T-Server is used in a high-load environment, which requires higher performance, Genesys recommends setting the device-rq-gap option to a lower value at an Application level, for a global effect on all DNs, or to set the DN-level option rq-gap to a lower value for a specific high-load Routing Point DN.

Note: Setting the device-rq-gap option to a value of 0 (zero) will disable this option, resulting in the same behavior as version 7.6 and older of T-Server.

(ER# 237463091)

Because of incorrect switch reporting of an unmonitored transfer, in the following scenario, T-Server cannot link the transfer to the outbound consultation leg of the initial transfer. As a result, T-Server creates a new call to represent the unknown secondary call and performs a standard two-step unmonitored transfer to the newly created unknown call. When the first part of the chained transfer is completed, this unknown call is the final result.

• An inbound call is made to monitored DN1 and DN1 answers.
• DN1 transfers the call to unmonitored DN2 and DN2 answers.
• A chain consultation call is made to monitored DN3 and DN3 answers.
• DN2 completes the transfer.
• DN1 completes the transfer.

(ER# 234758803)

Switch reporting does not provide any information about call forwarding before the call arrives at the final destination. The forwarding DN is never referred to in any  events and the event causes are always reported as single-step transfer. Consequently, T-Server cannot detect this scenario nor correct it. (ER# 206778801)

When a conference is initiated to a Routing Point and then routed to an external DN, once the conference is established, the conferenced-in party releases. In this case the PBX may not always provide the correct information to T-Server and therefore sometimes T-Server may not generate EventPartyDeleted. (ER# 172756104)

When an unmonitored device makes a transfer to a monitored device, there are three EventPartyChanged events reported, one of which has a new connection ID. This is caused by the switch reporting the unmonitored transfer in two steps, and in each step only one primary old call is reported. Therefore when the first transferred event is received, T-Server creates the missing other call and performs a partial transfer. The second event completes the transfer, and the partial transfer party and call are destroyed, leading to three EventPartyChanged events. (ER# 172146007)

In the following scenario, the PBX reports that the failed party is blocked, and no event is generated by T-Server. The Release request times out. The agent can release the blocked party using the Reconnect function.

1. The agent initiates a transfer to a busy destination.
2. The switch reports dialing and then destination busy.
3. The agent tries to release the dialing party on the transferring device.

(ER# 171703324)

DTMF can only be attached on an outbound call. (ER# 67256051)

It is not possible to make a chained consult call to a queue or native Routing Point. (ER# 84098421)

The following limitations apply when dialing invalid numbers:

Make call to invalid
When an invalid destination is dialed over a trunk, in some cases T-Server generates EventDestinationBusy with a call state of SitInvalidNumber. However, on some trunk types, the PBX does not provide enough messaging to generate this.

Consult Call to invalid
On a call of type consult, the PBX does not provide enough information to generate EventDestinationBusy with a call state of SitInvalidNumber.

Route/single-step transfer/redirect to invalid
The PBX does not always provide a failed event when one of the above requests is attemped to an invalid destination via a trunk. Consequently, the operation often times out.

(ER# 76010842)

When an inbound call using Q931 trunk arrives at an extension, a CTI single-step transfer request to a QSIG trunk is rejected by CAP. Two-step transfer is not affected. (ER# 66570914)

T-Server may not always report the correct conference states and roles on the remote T-Server when a conference is created using ISCC, with Event Party Propagation activated. (ER# 105674573)

When an external call, made over a Cornet trunk, is transferred to a third site, T-Server may generate the following events on the H4000: EventHeld, EventPartyChanged and EventRetrieved. This is due to switch reporting. (ER# 105416852)

This problem occurs due to incorrect reporting from Siemens. If DND and/or Forwarding are set, on startup, T-Server is unable to display the correct status for these features for VoIP telephones. (ER# 67187437)

A single-step transfer to an external destination produces two NetworkReached events. (ER# 32164520)

The One Number Service (ONS) allows two phone sets to be linked together so that if either number is dialed, both phone sets will ring. The numbers are set up so that one is Primary and one is a Slave.

This feature has the following CTI limitations:

• When either number is dialed, in CTI, only a Ringing is received on the Primary. It is therefore possible to answer the call only on the Primary via CTI.
• If one device is busy and either number is dialed, then the free device does not ring. Instead an EventDestinationBusy is received.
• It is not possible to set Call Forward from the primary to the slave and vice versa.

(ER# 71255199)

When using an emulated Routing Point as the voice transfer destination of a campaign that uses CPDServer with a digital Dialogic board, the OCS option call_transfer_type must be set to one_step. If it is set to two_step the outbound call can not be successfully transferred to an agent. (ER# 47736513)

After a call is redirected externally, the PBX reports the call state on the external T-Server as Forwarded rather than OK. This also occurs if the call is redirected to a Routing Point and then routed externally. (ER# 52594028)

A consult call, routed from an emulated Routing Point to a GVP port, cannot be transferred. (ER# 40762866)

Releasing a device in Ringing state generates an EventError, because the switch reports a Diverted event instead of ConnectionCleared, and the Divert is not matched with the EventReleased.

See the following scenario as an example:

Main T-Server (H4000 CSTA III)
Remote T-Server (H300h)

• 2101 MakeCall to External 2004
• 2004 AnswerCall
• 2101 Initiate Transfer to RP 4151
• Routing Point 4151 RouteCall 4152
• 2101 CompleteTransfer
• Routing Point 4152 RouteCall 2102
• 2102 ReleaseCall

In this scenarion, 2102 is released (EventReleased has Call State: NoAnswer), however an EventError is generated.

(ER# 40682589)

The PBX does not allow a recalled call to be redirected, so it is not possible to use No-Answer Supervision on calls that have been recalled. (ER# 34840571)

In the following scenario, when DN1 drops the call, an EventReleased is generated on DN3 but not on DN1. Another RequestReleaseCall is required on DN1 in order to get an EventReleased. However, then the Consult call remains in a Held state on DN1 and it is not possible to do anything with it (Release/Retrieve/Reconnect) via CTI. It has to be dropped by DN2 or manually. Setting the configuration option auto-reconnect-on-fail to true will prevent this issue.

1. DN1 MakeCall to DN2. DN1 InitiateTransfer to DN3. DN3 AnswerCall. DN1 AlternateCall.
2. DN1 Drop active call (to DN2) using ReleaseCall.

(ER# 30533702)

ISCC/COF only works with already initiated calls. Examples of call flows that T-Server is able to handle with the COF feature are:

• Calls that are routed externally from native or emulated Routing Points
• Calls that are overflowed by the PBX's ACD Overflow function.

In release 7.2, new configuration options (cof-ci-defer-create, and cof-ci-defer-delete) control the operation of COF, resolving some of the previous limitations, but the following restriction still applies:

• Any call which is transferred to the external T-Server using an emulated or native single-step transfer will be treated as a normal inbound call.

(ER# 101805,101544 )

When making a single-step transfer via ISCC with cast-type set to direct-ani the token used by ISCC is the origination of the primary call and not the destination. This does not match the ANI and the remote connection fails. (ER# 74387, 55715)

Chained consult calls are not supported on an analog line. Also single-step transfer of the destination of a consult call from an analog line is not supported. This affects VTO scenarios where a consult call is made to a Routing Point then routed to a VTO port. (ER# 87207, 86812).

Forwarding to DNIT is reported as forwarding to an RCG number by the switch. It is not possible to cancel forwarding without providing the old number. When the number is provided in the CancelFwd request in the form as reported by the switch, the request is rejected. (ER# 74379, 63786)

At start-up, T-Server tries to snapshot configured devices so it can restore call configuration. However, due to the way the Snapshot service is implemented in CAP v1.0, it is not possible to distinguish established state from originated/dialing. T-Server therefore treats dialing parties as established at startup. (ER# 75739, 75740)

CAP v1.0 sometimes fails to report the end of agent wrap-up state. The agent may remain in wrap-up state for CTI applications, while in fact he is ready to accept new calls. The agent must log off and log on again to clear this situation. (ER# 75741, 75742)

If a direct call is made to an emulated Routing Point and not routed, after a while the switch moves the call to another Hunt Group member. When this happens the switch provides a Connection Cleared event but does not tell T-Server that the call has been diverted. This means that on the emulated Routing Point, T-Server generates EventQueued and EventRouteRequest followed by an EventAbandoned and then a new EventQueued and EventRouteRequest. T-Server will retain the same ConnID unless retain-call-tout is not configured. If retain-call-tout is not set or set too low then T-Server will generate a new ConnID on the new EventQueued and EventRouteRequest. (ER# 102221966)

When QSIG Path optimization is used to transfer calls to an extension (for example, from an IVR connected to such a trunk), the PBX does not report the call delivery to the transfer destination correctly. T-Server is expecting a Delivered event but instead receives a ServiceInitiated event. This means that T-Sever cannot generate the ringing event until the call has been answered manually. (ER# 66570904)

It is not possible for primary and backup T-Servers to synchronize call information when a backup T-Server starts after a call was created. In this case, call control will not be maintained by T-Server after switchover, and therefore ACW behavior cannot be predicted. Setting configuration option ha-sync-dly-lnk-conn to true will prevent call synchronisation problems. (ER# 88084618)

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.

HP-UX 11.00 is no longer supported.

Solaris 7 is no longer supported.

Windows 2000 is no longer supported.

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 Siemens HiPath 4000 CSTA III Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Siemens HiPath 4000 CSTA III 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.