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.genesys.com for more details.

This release note applies to all 8.1 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 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.1.x.

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 T-Servers. Please contact your Customer Care 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.1.011.12. 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 release contains the following new features or functionality:

• Support for the Red Hat Enterprise Linux 8 operating system. See the Supported Operating Environment: T-Server Siemens HiPath 4000 CSTA III page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release does not include any corrections.

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.1.001.74. 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 version was first released as a Hot Fix on 09/14/16. This release contains the following new features or functionality:

• Support for the Windows Server 2019 operating system and Windows 2019 Hyper-V virtualization (added December 2020). See the Supported Operating Environment: T-Server Siemens HiPath 4000 CSTA III page for more detailed information and a list of all supported operating systems.

• Support for Red Hat Enterprise Linux 6 and 7 operating systems, in 32-bit and 64-bit modes. See the Supported Operating Environment: T-Server Siemens HiPath 4000 CSTA III page for more detailed information and a list of all supported operating systems. (UKTS-17438)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly generates EventPartyChanged on the origination DN of the main call when a consultation is made to a routing pilot, routed to another pilot within the same RCG, and then transfer is completed. Previously on transfer completion, T-Server generated EventPartyChanged only for the routing device. (UKTS-17476)

T-Server now properly handles scenarios where calls that are retained after leaving T-Server scope return to scope before being cleared from T-Server. Previously in such a scenario, T-Server might have failed. (UKTS-17422)

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.1.001.74. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly handles PBX events with two or more entries in private extensions fields. Previously, T-Server might have failed when processing such events. (UKTS-17410)

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.1.001.74. 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 contains the following new features or functionality:

• This release adds support for Windows Server 2012, in 64-bit native and compatibility modes. (UKTS-10302)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly handles errors in scenarios involving supervised routing and recovers immediately. Previously, T-Server might provide incorrect errors in such scenarios and recovered from errors only on the expiration of supervision timeout. (UKTS-17402)

T-Server now correctly performs a Check Call cleanup when an inbound trunk snapshot does not provide the expected information. Previously, T-Server deleted checked calls due to rejection of snapshot call functionality requested for such calls. (UKTS-17392)

T-Server now provides reporting that is compatible with Interaction Concentrator (ICON) requirements:

• Previously, when a call passed a non-monitored device or a device that was not defined in Configuration Database, T-Server reported EventQueued/EventRinging with CallStateRedirected, which affected ICON and InfoMart reporting. (UKTS-17394)
• In scenarios involving No-Answer Supervision and redirection to an ACD, T-Server previously reported AttributeCallState with value Redirected in EventQueued on RCG, and AttributeCallState with value Forwarded under No-Answer Supervision scenarios, which led to inaccurate reporting in ICON. (UKTS-17373)

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.1.001.71. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly reports routing on native Routing Points when no information regarding a calling device is available and a transfer is performed on another PBX node. Previously, T-Server did not report EventRouteUsed and EventDiverted events for a second routing after:

• a transfer was performed while the call was on a Routing Point, and
• the call was routed to another native Routing Point, and
• the second routing was executed.

(UKTS-17258)

T-Server now correctly handles forwarding to Emulated Routing Points (RPs). Previously, when a consultation call was made to a device that had forwarding to an Emulated RP enabled, with the call routed and transfer completed, T-Server did not report of an EventPartyChanged event for a device where monitoring originated. (UKTS-17239)

T-Server now correctly handles Emulated Routing Points (RP) after restoring connection to the PBX. Previously, T-Server incorrectly deleted the association of the Emulated Routing Point with its members when the link was reconnected, which resulted in loss of routing functionality to that Emulated RP. (UKTS-17111)

T-Server now correctly handles the restart of a link and reports an agent as logged out, when an agent disconnects the phone from the network while T-Server is disconnected. Previously, T-Server considered that agent as logged in. (UKTS-17109)

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.1.001.71. 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 contains the following new features or functionality:

• A new option, failed-call-rls-dly, enables a delay in the automatic disconnection of failed dialed calls. Previously, T-Server immediately disconnected such calls.

  failed-call-rls-dly
  Default value: 1
  Changes take effect: Immediately
  Valid values:
  • 0 - T-Server does not automatically clean up a call in the failed state
  • 1...30 - T-Server starts a timer and automatically cleans up a failed call if the call is still present on timeout expiration

  When the PBX reports event Failed as a result of dialing to a busy or unobtainable destination, this option defines the delay (in seconds) that T-Server applies to the execution of the recovery service. The option applies only to regular devices such as extensions and voice treatment ports.

  (UKTS-17244)

Corrections and Modifications

This release includes no corrections or modifications.

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.1.001.71. 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 includes the following corrections and modifications:

During transfers, T-Server now properly initializes transferring parties whose CallerIDs the switch has hidden. Previously, a crash could result. (UKTS-17179)

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.1.001.71. 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 includes the following corrections and modifications:

RCG (Routing Point or ACD Queue) devices monitored via the r prefix notation must be parsed into integer device identifiers in requests to the switch. This translation occurs at the point of reading from the configuration. Previously, in version 8.1.000.09, T-Server incorrectly cleared the translated device identifiers from its memory on CTI link failure. When the link was restored, T-Server sent the incorrect string r identifiers in requests to the switch. T-Server now caches the device identifiers so that RCG devices can be re-monitored successfully after CTI link failure. The RCG group monitor *888 is unaffected. (UKTS-16721)

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.1.001.60. 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 includes the following corrections and modifications:

T-Server now correctly processes the callback-dn configuration option on no-answer supervision. Previously, T-Server might have incorrectly processed the redirect for the call including a hidden (unknown) originator identity with a call back DN. (ER# 317899989)

T-Server now correctly populates the AttributePreviousConnectionID attribute value in EventPartyChanged and sends the next DN-related event in the following scenario:

• A call in a multi-site Call Overflow (COF) scenario arrived and was successfully matched by the COF at a site where call monitoring was turned on.
• The value of the T-Server report-local-connid-changes configuration option was set to true.

Warning! Do not use the report-local-connid-changes option unless you are instructed to do so by Genesys Customer Care.

Previously in this scenario, T-Server generated an EventPartyChanged event with the AttributePreviousConnectionID attribute value incorrectly set to ffffffffffffffff and failed to generate the first DN-related event for the call (EventRinging, EventQueued, or EventRouteRequest events, depending on the type of DN at which the call arrived).

(ER# 316888704)

T-Server now correctly handles call events from a switch that have a blank Call ID. In addition, the monitored device that detects a blank Call ID is put out of service to reflect this unexpected DN condition. The device is then restored back to service after receiving a CSTA connection cleared event that has null local connection information that corresponds to a Genesys EventOnHook event. Previously, T-Server unexpectedly terminated in these scenarios. (ER# 317676930)

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.1.001.45. 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 includes the following corrections and modifications:

T-Server now correctly decodes CSTA call events that contain empty CallID attribute fields. Previously, T-Server sometimes became unstable when it received these CSTA call events from the PBX. (ER# 300934995)

T-Server now correctly reports the OtherDN attribute after the call is redirected (routed and/or forwarded) from an unmonitored DN. Previously, T-Server might not have properly tracked the OtherDN attribute changes. (ER# 299507145)

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer sends an EventNetworkReached message on an Alerted device. (ER# 284945511)

T-Server no longer occasionally goes into an infinite loop in scenarios where DNs are disabled and enabled in quick succession in the configuration environment. (ER# 283242602)

T-Server no longer shuts down if it fails to obtain an ISCC license. (ER# 278678036)

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.1.000.19. 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.1 release of T-Server for Siemens HiPath 4000 CSTA III.

• T-Server no longer connects to applications that have disabled status in the configuration environment.
• The default value of the background-processing configuration option has been changed to true.
• T-Server now supports the Unresponsive Process Detection feature. The following configuration options enable this feature:

  • heartbeat-period
  • hangup-restart

  See option descriptions in your T-Server Deployment Guide. For more information, refer to the Framework 8.0 Management Layer User�s Guide.
• T-Server now supports IPv6. For more information, refer to the Framework 8.1 Deployment Guide.
• T-Server now supports vSphere 4 Hypervisor.
• T-Server now supports Acresso FLEXNet Publisher 11.9 license manager.
• T-Server is now supported on the following platforms:

  • AIX 7.1 64-bit
  • HP-UX Itanium (version 11i v3)
  • Red Hat Enterprise Linux 5 64-bit

• T-Server now supports account codes.
• T-Server now supports a new Application-level option, bsns-call-dev-types which allows inclusion of External Routing Points to the list of devices that business call handling is applied to. T-Server now accepts the AttributeExtensions key BusinessCallType in the request TRouteCall. Previously, T-Server excluded External Routing Points from the list of devices where business call handling was applied to and did not accept the BusinessCallType key. (ER# 274104710)

Corrections and Modifications

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

Reporting of EventReleased after a failed Two-Step Transfer has been corrected to fix the other party DN. (ER# 236640888)

Reporting of Single-Step Transfer to an Emulated Route Point has been corrected to remove the incorrect third-party DN in the related events. (ER# 226594679)

Reporting of Single-Step Transfer to a Route Point and/or Queue has been corrected to remove the incorrect third-party DN in the related events. (ER# 100976)

T-Server now ignores unsupported agent workmodes for native agent requests, no longer failing not-ready self-transition requests when such workmodes are used. (ER# 221762854)

T-Server no longer passes empty strings to ASN encoder. Previously, T-Server would terminate operation under Windows in this scenario. (ER# 271030661)

The option kpl-loss-rate has been removed from T-Server. (ER# 274704653)

Top of Page

Known Issues and Recommendations

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

To ensure backward compatibility, T-Server provides two options that define how many licenses T-Server can check out:

• num-of-licenses defines the max number of licenses that T-Server can check out.
• num-sdn-licenses defines the actual number of licenses that T-Server does check out, up to the maximum value specified by option num-of-licenses.

When the values of the two options are different, then T-Server applies the lower one, so Genesys recommends that you leave the option num-sdn-licenses at the default value max and set the option num-of-licenses to the actual number of licenses that you want T-Server to check out. Alternatively, you can set both options to the same value.

• num-of-licenses
  Default Value: max (equivalent to 9999 licenses)
  Valid Values: max (equivalent to 9999) or any integer
  Changes Take Effect: Immediately
  Specifies the maximum number of DN licenses T-Server can check out. The values max or 0 (zero) is equal to exactly 9999 licenses. To check out any other number of licenses, specify the value as an integer, up to the number of seats supportable in your environment. The sum of all num-of-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.

• num-sdn-licenses
  Default Value: max (all DN licenses are seat-related)
  Valid Values: String max (equal to the value of num-of-licenses) or any integer.
  Changes Take Effect: Immediately
  Specifies how many seat-related licenses T-Server checks out. A value of 0 (zero) means that T-Server does not grant control of seat-related DNs to any client, and it does not look for seat-related DN licenses at all. A value of "max" means that T-Server checks out the number of licenses defined in option num-of-licenses. The sum of all num-sdn-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.

T-Server might improperly report the field OtherDN in events for consultation calls or incompletely report scenarios involving the transfer of an internal call to an external destination, because of incorrect interpretation of a missing network destination in PBX reporting when the following scenario is executed:

• an internal call is established
• a consultation call is initiated to a routing point and routed to an agent
• the agent redirects a routed call to an ISDN destination, and
• the transfer is completed

Workaround: Configure outbound trunks in PBXs so that the information from the PBX contains the correct remote destination.

T-Server does not apply values of the restart-period configuration option other than 10 seconds. (ER# 285626365)

T-Server shuts down if it fails to obtain an ISCC license. (ER# 278678036)

Currently, the Framework 8.1 T-Server for Siemens HiPath 4000 CSTA III Deployment Guide omits the following option description. The next published version of the document will include this information.

legal-guard-reason
Default Value: 0
Valid Values: 0–254
Changes Take Effect: Immediately

Specifies the value of the Reason Code key in AttributeExtensions that T-Server will report in an EventAgentNotReady message that is sent as a consequence of the legal pause phase.

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 attempted to an invalid destination via a trunk. Consequently, the operation often times out.

(ER# 76010842)

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)

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 scenario, 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).

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)

When operating with HiPath 4000 UV6, T-Server is unable to support ACD configurations that contain *888. RCG devices must be explicitly configured in the configuration environment. (ER# 285626452)

When operating with HiPath 4000 UV6, T-Server is unable to provide correct reporting for calls that are abandoned while they are parked because of insufficient switch reporting. (ER# 285626414)

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)

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 synchronization problems. (ER# 88084618)

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)

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)

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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

The following operating systems:

• Windows Server 2008
• Red Hat Enterprise Linux 6
• Red Hat Enterprise Linux 5
• AIX (all versions)
• Solaris (all versions)

Windows Server 2003 is no longer supported.

Solaris 9 is no longer supported.

The HP-UX PA and HP-UX IPF operating systems are no longer supported.

The Red Hat Enterprise Linux 3.0 operating system is no longer supported.

The Solaris 8 operating system is no longer supported.

The Tru64 UNIX operating system is no longer supported.

The AIX 5.1 and 5.2 operating systems are 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 Cloud Services, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

• The Framework 8.1 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.1 Deployment Guide  helps you configure, install, start, and stop Framework components.

• The Platform SDK 8.x .NET (or Java) API Reference and the Genesys Events and Models Reference Manual contain 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 Customer Care for additional information.

• The Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Customer Care for additional information.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up to date than what is available on disc immediately after a product is released or updated.

Top of Page