Release Note

T-Server for Siemens Hicom 300/HiPath 4000 CSTA I

7.6.x

Genesys Telecommunications Laboratories, Inc. © 2008–2013

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
7.6.010.10 [11/22/13] – Hot Fix           X
7.6.010.09 [04/29/13] – Hot Fix           X
7.6.010.08 [06/10/10] – General X X X X X X
7.6.010.06 [02/09/10] – Hot Fix X         X
7.6.010.03 [02/17/09] – Hot Fix           X
7.6.010.02 [08/14/08] – General X X X X X X
7.6.009.02 [07/09/08] – General X X X X X X
7.6.008.00 [03/27/08] – General X X X X X X
7.6.007.01 [01/30/08] – General X X X X X X

Link to 7.5 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 7.6 releases of T-Server for Siemens Hicom 300/HiPath 4000 CSTA I.

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. Please contact your Customer Care representative if you have any questions.


Release Number 7.6.010.10 [11/22/13] – Hot Fix

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 7.6.008.22. 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 correction and modification:


Primary and backup T-Servers now run correctly according to their roles if, during a switchover, the primary and backup T-Servers get disconnected, and the primary to backup connection is restored first. Previously in this scenario, the backup T-Server incorrectly notified its clients that its role changed to primary while it remained running in backup mode. (UKTS-16717)


Top of Page


Release Number 7.6.010.09 [04/29/13] – Hot Fix

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 7.6.008.10. 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 handles single-step transfer scenarios to populate the ANI attribute information in situations where one of the DNs is a RCG switch device type. Previously, T-Server did not report the ANI attribute in EventCallPartyAdded events. (ER# 318685081)


Top of Page


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 7.6.008.18. 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 now correctly generates an EventRouteRequest message for each Routing Point when a call is diverted through multiple Routing Points on different Routing Control Groups (RCG). Previously in this scenario, T-Server did not generate a EventRouteRequest meesage. (ER# 226759489)


T-Server now properly executes a call check on the call that is transferred using a single-step transfer onto a distribution device. Previously, T-Server became unstable when it used the main call as the consultation call check, and the call was deleted during the handling of the call check result. (ER# 254061629)


In a call monitoring scenario, when an agent releases a call, T-Server now correctly generates EventReleased, EventCallPartyDeleted, and EventCallDeleted messages. Previously in this scenario, T-Server did not generate the EventCallDeleted message. (ER# 249451649)


T-Server now reports the correct value of AttributeOtherDN for an inbound consultation call that arrives to an agent over a trunk, and is transferred before the agent answers the call. Previously in this scenario, T-Server did not report the correct value for AttributeOtherDN. (ER# 208127879)


T-Server no longer becomes unstable in the following scenario:

  1. T-Server registers a large number of DNs that are not on the switch.
  2. An agent makes a call that is released by the switch due to an unknown switch error.
  3. While the release is in progress, the agent sends a TReleaseCall request for the same call.

(ER# 220522328, ER# 248925304)


T-Server no longer becomes unstable in a scenario where T-Server registers ten or more extensions that are valid extensions on the switch, but are not configured in Configuration Manager. (ER# 239996396)


Top of Page


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 7.6.008.10. 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 no longer reports an agent login event until the agent state event (EventAgentReady, EventAgentNotReady, AgentAfterCallWork, or EventAgentLogout) has been received from the PBX so as to prevent intervening call state events. Both the EventAgentLogin and agent ready state event are reported together. (ER# 236198815)


T-Server now correctly handles outstanding requests. Previously, it was possible to have a duplicate entry in internally queued requests which caused T-Server to become unstable. (ER# 244482104)


Top of Page


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 7.6.008.10. 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 has been modified to ensure that ISCC connections are correctly re-established after disconnection. (ER# 218628310)


Top of Page


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 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no new features in this release.\

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server reporting of After Call Work (ACW) has been corrected. Previously, T-Server was not always reporting the correct work mode in the EventAgentNotReady when the PBX applied after call work. Now T-Server reports AttributeWorkMode = AfterCallWork. (ER# 200021305, 198007625)


Top of Page


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 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no new features in this release.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server has been modified to ensure correct processing of snapshot requests issued against a trunk. (ER# 192545642)


T-Server handling of the deletion of transit calls has been amended to prevent memory corruption and consequent T-Server failure. (ER# 193155883, 192147673)


A new configuration option, cls-on-call-lcs-idle, has been implemented to enable call-release processing to be backwardly compatible with pre-7.5.002.00 T-Servers.

  • cls-on-call-lcs-idle
    Default Value: true
    Valid Values: true, false
    Changes Take Effect:  Immediately

    Defines whether pre-7.5.002.00 call clearing is used (value = false) or 7.6.009.00+ call clearing functionality is used (value = true).  With value true, when a release request is issued for an internal established call, the call is released upon receipt of CSTA Event Connection Cleared. With value false, when an internal call is released, it becomes "stuck" in T-Server and is cleared by Check Call functionality.

(ER# 193875902)


Top of Page


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 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no new features in this release.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server has been modified to ensure correct processing of snapshot requests issued against a trunk. (ER# 192545642)


T-Server handling of the deletion of transit calls has been amended to prevent memory corruption and consequent T-Server failure. (ER# 193155883, 192147673)


A new configuration option, cls-on-call-lcs-idle , has been implemented to enable call-release processing to be backwardly compatible with pre-7.5.002.00 T-Servers.

  • cls-on-call-lcs-idle
    Default Value: true
    Valid Values: true, false
    Changes Take Effect:  Immediately

    Defines whether pre-7.5.002.00 call clearing is used (value = false) or 7.6.009.00+ call clearing functionality is used (value = true).  With value true, when a release request is issued for an internal established call, the call is released upon receipt of CSTA Event Connection Cleared. With value false, when an internal call is released, it becomes "stuck" in T-Server and is cleared by Check Call functionality.

(ER# 193875902)


Top of Page


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 7.6.008.06. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no new features in this release.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server has been built with the latest libraries. (ER# 178717073)


T-Server handling of events for PickUp of a held call has been corrected. Previously, T-Server incorrectly handled this scenario as a temporarily created conference. Now, T-Server checks for, and supplies when found, the call originator to the Event trigger procedure, which fixes the T-Event reporting. (ER# 179274458)


Top of Page


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 7.6.008.03. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This section describes new features that were introduced in the initial 7.6 release of T-Server for Siemens Hicom 300/HiPath 4000 CSTA I.

  • Enhancement to Smart OtherDN Handling: In release 7.6, new configuration option clid-withheld-name has been introduced.

    • clid-withheld-name
      Default Value: PRIVATE
      Valid Values: Any string
      Changes Take Effect: Immediately
      Defines a name that replaces a withheld CLID. If no value is entered (empty string) the withheld CLID will be displayed.

  • Enhancement to No-Answer Supervision: In release 7.6, configuration option nas-indication has been introduced to enable T-Server to indicate in EventReleased whether an overflow has occurred as a result of No-Answer Supervision.

    • nas-indication
      Default Value: none
      Valid Values: none, ext, rsn
      Changes Take Effect: Immediately
      Specifies the reporting action in EventReleased when No-Answer Supervision overflows a call. With value none, no reason or extension is provided in EventReleased. With value ext, extension NO_ANSWER_TIMEOUT is supplied in EventReleased. With value rsn, reason NO_ANSWER_TIMEOUT is supplied in EventReleased.

  • Enhancement to Keep-Alive: In release 7.6, the Keep-Alive feature has been enhanced to include a configurable loss-rate counter.

    • kpl-loss-rate
      Default Value: 10, 100
      Valid Values: Single integer or comma-separated pair of integers. The first value in the pair is the failure value.
      Changes Take Effect: Immediately
      Specifies how many KPL positive responses are needed to decrement either the failure or warning tolerance counter. Value 0 (zero) disables this option. Two comma-separated values means T-Server will calculate both the failure counter and the warning counter. A single value means T-Server will calculate only the failure counter. See the Deployment Guide for full details.

  • Enhancements to After Call Work (ACW): In release 7.6:

    • A wrap-up threshold can now be applied to ACW processing.

      • wrap-up-theshhold
        Default Value: 0
        Valid Values: Any positive integer
        Changes Take Effect: Immediately
        Specifies the minimum period (in seconds) that a business call must last before emulated ACW is applied at the end of the call.

    • Emulated-agent handling of changes of party is updated to (re)calculate the ACW period only in cases where the consulted party was not considered business-related before the call was transferred.

    • The verification of agent work modes for emulated agents has been improved, especially for agent ready events. The agent work mode is now also added to agent events.

Corrections and Modifications

This release includes the following corrections and modifications that were made between the most recent 7.5 release and the initial 7.6 release:


A T-Server failure that caused the CTI link to fail has been corrected. This was caused by the release of the call while TQueryCall was outstanding for that call. (ER# 135777609)


A problem with incorrect targeting of agents in NotReady state has been corrected. This was caused by T-Server (emulated) agent states and PBX agent states being out of sync. (ER# 143472162)


A problem with reporting of incorrect call types has been corrected. T-Server has been modified to handle any RCG device as internal and to assign the correct call type for calls made to RCG devices. (ER# 154731065)


A problem with T-Server failure upon client disconnect/reconnect has been corrected. Previously, T-Server was not updating internal data structures where clients were monitored. (ER# 164506524)


Top of Page


Known Issues and Recommendations

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


When T-Server, running on Windows Server 2008 32-bit or 64-bit, exits due to a SIGBREAK, T-Server does not close the *.snapshot.log file before exiting. (ER# 254573795)

Found In: 7.6 Fixed In:


When installing T-Server on a 32-bit UNIX host, the installation procedure gives the option of installing a 32-bit executable or a 64-bit executable. Install the 32-bit executable on a 32-bit host. (ER# 254398026)

Found In: 7.6 Fixed In:


If a hunt group is used for emulated routing and the call is redistributed by the switch between the hunt group members, then the T-Server reporting is not correct. In order to avoid this issue, the hunt group should not be configured on the switch to redistribute between hunt group members. (ER# 196249221)

Found In: 7.6 Fixed In:


When a transfer is initiated to an invalid device through a trunk, the switch reporting in the connection cleared event for the consult leg is incorrect. If T-Server's call cleanup is configured for a very short period, this results in a snapshot being sent to the switch that returns the incorrect information to T-Server for the failed consult leg. As a result the held primary call cannot be retrieved. In order to work around the incorrect switch reporting, Genesys recommends that if call cleanup is enabled, then the periodic-check-tout option is set to the default value of 10 min. (ER# 195946749)

Found In: 7.6 Fixed In:


T-Server does not report EventPartyDeleted on an external DN, when a conference call is initiated using the ISCC (cast-type = direct-ani) to an emulated Routing Point. Subsequently, the emulated Routing Point internally routes the call. (ER# 172982695)

Found In: 7.6 Fixed In:

EventReleased is not generated on an external DN after the agent requests TReleaseCall on the ringing call. (ER#  173080160)

Found In: 7.6 Fixed In:

T-Server reports EventRemoteConnectionFailed when the origination DN makes a blind transfer to a native Routing Point, which then routes the call to an external DN via ISCC with cast type = direct-ani. (ER# 173080153)

Found In: 7.6 Fixed In:

When an inbound transferred call is released without an answer (from the Alerted state), the PBX returns the call back to the transferring device. (ER# 170898034)

Found In: 7.6 Fixed In:


If a client without registered DNs disconnects, T-Server might become unstable. Clients typically would monitor at least one DN, so the problem is unlikely to occur. (ER# 128651197)

Found In: 7.5 Fixed In: 7.6.009.01

Outbound Contact Server (OCS) loses control of a call if No-Answer Supervision (NAS) is activated in the following emulated redirect scenario:

  1. NAS is set on T-Server to recall the call after the timer expires.
  2. OCS is set to use two step transfer.
  3. An outbound call is made and answered.
  4. OCS initiates a consult call to a queue, which distributes the call.
  5. The NAS timer expires.
  6. T-Server performs an emulated redirect back to the queue.
  7. As this is an emulated redirect, the call is answered and transferred to the queue; however this causes OCS to complete the transfer prematurely.

(ER# 118335533)

Found In: 7.5 Fixed In:


EventEstablished is not generated on the origination DN when a call to an external DN with call forward set is forwarded to an internal DN.  (ER# 118870351)

Found In: 7.5 Fixed In:


The PBX drops the connection when an emulated redirect of a call is made to an external DN. (ER# 118870384)

Found In: 7.5 Fixed In:


The redirect might fail when call forward is set on the redirect device. (ER# 118870368)

Found In: 7.5 Fixed In:


Call Control is lost by Outbound Contact Server (OCS) during an outbound campaign when the OCS call_transfer_type option is set to a value of two_step and is used in conjunction with No-Answer Supervision (NAS). When the NAS timer expires, T-Server employs an emulated redirect to deflect a call. This in turn causes OCS to complete the transfer prematurely. (ER# 118335533)

Found In: 7.5 Fixed In:


When using emulated predictive dialing, if T-Server drops the call because the AttributeTimeout has expired, the call state is incorrectly reported as Dropped instead of NoAnswer. This also causes OCS to mark the call as Dropped instead of NoAnswer in cases where the call_wait_connect_timeout expires. (ER# 111503158)

Found In: 7.5 Fixed In:


Shutting down a primary T-Server via SCI may cause high-availability (HA) to fail with Genesys Desktop. To prevent this, switch T-Server over to Backup mode before shutting it down. (ER# 111925681)

Found In: 7.5 Fixed In:


The Hicom and HiPath PBXs do not support UUData for MakeCallService. (ER# 104382686)

Found In: 7.5 Fixed In:


On the Hicom 300 (UK), in scenarios where an inbound call is redirected externally to a device with call forwarding set, the call is not cleared on the redirecting device after the call redirect has taken place. (ER# 105239417)

Found In: Unspecified Fixed In:


On the H300 (US), the PBX sometimes recalls a call back to the device that just completed a transfer. (ER# 85331548)

Found In: PBX 6.5 & 6.6 (US) CAP 2 Fixed In:


On the Hicom 300 (UK), EventEstablished is not generated when a call is made to an External DN that has call forwarding set to an internal DN. (ER#  105239461)

Found In: 7.5 Fixed In:


There are several limitations in scenarios involving dialing to invalid destinations:

  • Making a call to an invalid destination
    When an invalid destination is dialed over a trunk, in most cases the PBX does not provide a failed event; therefore, the operation often times out (T-Server reports EventError - Timeout Performing Operation). In some cases, T-Server generates EventDestinationBusy with CallState = Busy. The PBX does not provide enough messaging to provide a CallState = SitInvalidNum.
  • Consultation call to an invalid destination
    On a consulation call, the PBX does not provide enough information to generate EventDestinationBusy with CallState = SitInvalidNumber. Using cornet trunks, EventDestinationBusy (CallState = Busy) is reported. Using all other trunks, no failed event is generated by the PBX, and T-Server times out.
  • Route/single-step transfer/redirect to an invalid destination
    The PBX does not always provide a failed event notice when one of these requests is attempted to an invalid destination via a trunk; therefore, the operation often times out (T-Server reports EventError - Timeout Performing Operation). (ER# 83613498)
Found In: 7.5 Fixed In:


T-Serverís Secret Identity feature cannot be configured on the Hicom 300 (US) switch. (ER# 71739842)

Found In: 7.5 Fixed In: 


The One Number Service (ONS) enables 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 a primary and one is a slave. This feature has the following CTI limitations on the HiPath 4000 CSTA I switch:

  • When either number is dialed, in CTI, only a Ringing event 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, 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 or vice versa. (ER# 71212183)
Found In: 7.5 Fixed In:


TSendDTMF support has the following limitations:

HiPath 4000

  • Internal calls are supported.
  • Outbound calls where a trunk is involved are supported.

Hicom 300 (UK)

  • Outbound calls where a trunk is involved are supported.
  • Inbound and internal calls are not supported.

Hicom 300 (US)

  • Inbound and outbound calls where a trunk is involved are supported.
  • Internal calls are not supported.

(ER# 64100943)

    Found In: 7.5 Fixed In:


    Because no switch reporting is provided in the following native single-step transfer scenarios on RCG-based devices, reporting is unreliable:

    • Single-step transfer to DN with immediate forward to RCG (Queue or Routing Point) is set.
    • Redirect to DN with immediate forward to RCG (Queue or Routing Point) is set.
    • Nonsupervised routing from an emulated Routing Point (when the value of the emu-sstr option is set to false)

    (ER# 73773451)

      Found In: 7.5, Hicom 300 (UK) Fixed In:


      The Hicom 300 (UK) cannot route consultation calls from an emulated Routing Point to an ACD Queue or a native Routing Point device. (ER# 105239581)

      Found In: 7.5 Fixed In:


      On the HiPath 4000 only, after transfer completion there are no events from the PBX that indicate any state changes for a camped-on call. (ER#  76342243)

      Found In: 7.5, PBX V3 CAP 2.2 Fixed In:


      Call Forwarding does not take place if a call is routed from a native Routing Point. Call Forwarding does not take place if the call arrives on the forwarding DN from an ACD Queue. (ER# 64108238)

      Found In: 7.5 Fixed In:


      The rel-cons-reconnect configuration option works only when the value of the correct-rqid configuration option is set to true. The correct-rqid option disables/enables request conversion in general, and the rel-cons-reconnect option controls the processing of a request release for a reconnect call. (ER# 105239480)

      Found In: 7.2, 7.5 Fixed In:


      The TRouteCall request from a native Routing Point with RouteType Reject is not supported on the Hicom 300 (US) PBX. (ER# 64151203) 

      Found In: 7.5 Fixed In:


      On the HiPath 4000 switch, an incorrect DN value is reported in events after an originating DN single-step transfers to a distribution device.

      Scenario 1: DN1 makes a call to a queue (or Routing Point). DN1 then single-step transfers to another queue. The events following this contain the queue as the first queue (or Routing Point) that the call was made to, and not the queue that the call was transferred to.

      Scenario 2: DN1 makes a call to a queue (or Routing Point). DN1 then single-step transfers to a Routing Point (if the original call was to a Routing Point then this should be a different Routing Point). In this case, the call is transferred to the original queue (or Routing Point) that the call was made to and not the Routing Point that the call was transferred to.

      Scenario 3: DN1 makes a call to a queue (or Routing Point). DN1 then mute (or blind) transfers to a Routing Point (if the original call was to a Routing Point then this should be a different Routing Point). In this case, an EventRouteRequest is generated in both the original queue (or Routing Point) that the call was made to, as well as on the Routing Point that it is transferred to. Only an EventQueued is generated on the original queue (or Routing Point). If the call was originally to a queue, then it does not get delivered from the queue, but it is possible to route it from the Routing Point that it was transferred to. However, no Diverted event is generated on the Routing Point and therefore, a phantom call is left on the Routing Point. A Diverted event is generated on the queue (or original Routing Point), so there is no phantom call there. After an interval, an internal T-Server timeout error is generated on the Routing Point. (ER# 68727423)

      Found In: Unspecified Fixed In:


      Long-distance authorization codes are only supported on the Hicom 300 (US) and the HiPath 4000. This feature is not supported on the Hicom 300 (UK).

      On the HiPath 4000, the switch provides incorrect messaging on TInitiateTransfer requests to external destinations. This causes the incorrect reporting of the consultation call. (ER# 93509748)

      Found In: 7.5 Fixed In:


      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, T-Server does not maintain call control after switchover, and therefore ACW behavior cannot be predicted. (ER# 86397191)

      Found In: 7.5 Fixed In:


      On the Hicom 300 (US) switch, the T-Server options, prd-dist-call-ans-time and supervised-route-timeout, cannot have a value of 0 (zero) both at the same time if an emulated Routing Point is used. If both options are set to 0, emulated predictive dialing does not work. This is because both emulated routing and emulated predictive dialing are based on Transfer. When the options' values are both 0, transfers in both cases are not completed. Chained consultation is not supported by the switch.(ER# 33100846)

      Found In: Unspecified Fixed In:


      THoldCall is not supported via CTI on the Hicom (UK) switch. (ER# 73619181)

      Found In: Unspecified Fixed In:


      The PBX does not generate OutOfService and BackInService events for devices. Therefore, if a device goes out of service while T-Server is running, there is no notification from the PBX, so T-Server and its clients are unaware of this. The devices is still seen as in-service from a Genesys point-of-view. (ER#  93643)

      Found In: 7.0 Fixed In:


      The switch reporting of calls only allows the Inter Server Call Control/Call Overflow (ISCC/COF) feature of T-Server to work with already initiated calls. This means that any call that is transferred to the external T-Server using a two-step transfer (this includes mute transfers, emulated single-step transfers, and calls routed through emulated Routing Points) are treated as normal Inbound calls. Examples of call flows that T-Server is able to handle with the COF feature are:

      • Calls that are routed externally from native Routing Points.
      • Calls transferred using Native Single Step transfer.
      • Calls that are overflowed by the PBX's ACD Overflow function.

      This issue also exists after transferring to a native Routing Point, then routing using COF to an external DN, then completing the transfer. If the transfer is completed before routing to an External DN, the COF is successfully made. (ER# 101536)

      Found In: 7.1, 7.6 Fixed In:


      HiPath 4000 Circular Hunt Group limitations: Forwarding from one Hunt Group member to another, or from a Hunt Group member to the Hunt Group itself, does not take place when a call is made to the Hunt Group. If the call is made directly to the member then forwarding does take place. (ER# 104382753)

      Found In: Fixed In:


      The OCS call_transfer_type option must be set to one-step when the Voice Transfer destination is an emulated Routing Point. With any other value, TCompleteTransfer is rejected and CPD releases the outbound campaign. (ER# 36489764)

      Found In: Unspecified Fixed In:


      It is not possible to initiate callback when a call is waiting on a Hunt Group member. (ER# 13216755)

      Found In: 7.1.001.01 Fixed In:


      The PBX does not allow account codes to be attached when the call is in a Ringing or Dialing state. Neither can Account codes be attached via CTI. (ER# 13216654)

      Found In: 7.1.001.01 Fixed In:


      The PBX does not allow a call to be camped-on to a device with a call ringing on it:

      • When a camped-on call is in a Queued state, it is not possible to answer it without the active call being released first.
      • When a camped-on call is in a Queued state, it is not possible to alternate between it and the active call.

      (ER# 13216699)

      Found In: 7.1.001.01 Fixed In:


      You cannot do the following:

      • Park a call via CTI.
      • Park a consultation call.
      • Park a call while on a conference call.
      • Park a call on a distribution device.

      The PBX does not allow both sides of a call to park the call. (ER# 13216791)

      Found In: 7.1.001.01 Fixed In:


      It is not possible to snapshot distribution devices. Therefore, if there is a call on a Routing Point or a queue when T-Server starts or the link reconnects, T-Server does not see this call. (ER# 13216809)

      Found In: 7.1.001.01 Fixed In:


      In the following scenario, the ThirdPartyDN of the EventQueued is the queue to which the call is transferred. However, it should be DN2 with a ThirdPartyDNRole of TransferredBy. This occurs irrespectively of the value of the emu-sstr option.

      1. DN1 MakeCall to DN2.
      2. DN2 AnswerCall.
      3. DN1 SingleStepTransfer to Queue.

      (ER# 101148, 98721)

      Found In: 7.1 Fixed In:


      It is not possible to reroute a consultation call to an external destination (via ISCC) when the first routing attempt has failed. Additionally, neither call can then be controlled via CTI. They must be manually released. The same problem occurs when trying to route from an emulated Routing Point to a native Routing Point. Routing attempts between emulated Routing Points are not affected. (ER# 101118, 99911).

      Found In: 7.1 Fixed In:


      When multiple lines are enabled, the devices are multiline and multi-DN. Via CTI, it is not possible to control calls made to any keys other than the primary key. However, tests of multiline devices show that T-Server correctly reports the events on all keys. (ER# 102166, 102163).

      Found In: 7.1 Fixed In:


      Due to PBX limitations (HiPath 4000 CSTA I only), when making emulated predictive calls from an emulated Routing Point, the T-Server prd-dist-call-ans-time option must be set to a value of 0 (zero) for T-Server to be able to route the call once it is established with the customer. (ER# 100641,  98817).

      Found In: 7.1 Fixed In:


      In the following scenario, the switch reports a normal internal call, as does T-Server. No indication about forwarding ever comes from the switch, and the switch does not report Established on the originator:

      1. DN1 on HiPath 4000 has call forward unconditional set to external DN 2 on H300 (UK). DN3 makes inbound call to DN1 (cornet trunk). DN2 EventRinging callstate is OK, instead of the correct state Forwarded. DN2 answers call, but no EventEstablished is reported on DN3.
      2. DN2 releases, and EventReleased is correctly reported for both DNs.

      (ER# 100705, 98993)

      Found In: 7.1 Fixed In:


      When the value of the emu-sstr option is set to false, an internal call redirected to an internal destination, with immediate forwarding to an external device, is successful; however, T-Server also returns a timeout error. (ER# 101062,  99710)

      Found In: 7.1 Fixed In:


      In the following scenario, no Abandoned event is generated for DN3. A Dropped Connection event from the PBX is generated but it is for the wrong DN (DN2 instead of DN3). This leaves a phantom call queued on DN3.

      1. DN1 Inbound call to DN2
      2. DN2 parks call to DN3
      3. DN1 Abandons call

      (ER# 99046, 91673)

      Found In: 7.1 Fixed In:


      (Hicom 300s only) When a call is camped-on to a DN, the PBX does not provide enough messaging for T-Server to report the camped leg of the call. Therefore, there are no events on the DN that the call has been camped onto until the main call has been released from that DN and the camped-on call is seen as ringing. (ER# 99257, 99247)

      Found In: 7.1 Fixed In:


      In the following scenario, the HiPath 4000 PBX drops both the initiated call to the queue/Routing Point and the consultation call.

      1. DN1 establishes call with DN2. DN2 establishes a consultation call with DN3.
      2. DN3 initiates transfer to a Queue or a Routing Point.

      This affects various emulated scenarios. For example, diverting a consultation call to a Queue or Routing Point with emulated single-step transfer enabled. (ER# 99825, 99826).

      Found In: HiPath4000 v 2.0 SA09 Fixed In:


      Using ISCC cast-type route-uui to make a native single-step transfer of a call to an external destination fails. The call remains on the external Routing Point. The emulated single-step transfer behaves correctly. (ER# 100034, 100035)

      Found In: CAP 2.0 Fixed In:


      Calls that have been single-step transferred to an ACD Queue/Routing Point cannot be synchronized between a pair of high-availability T-Servers. (ER# 50621, 80434)

      Found In: 6.5.301.00 Fixed In:


      The Hicom 300 (UK) sends the incorrect CSTA information whenever an outbound call is transferred to an ACD Queue or Routing Point. This causes T-Server to display an incorrect OtherDN in EventRinging, EventEstablished, EventReleased for the following scenario:

      1. Make outbound call.
      2. Answer call.
      3. Two-step transfer from originator to Routing Point.
      4. Route call.
      5. Answer call.
      6. Complete call.

      (ER# 80332, 79898, 78594, 43455)

      Found In:  H300 (UK) V1.0-SA05 CAP 2.0 Fixed In:


      When a call is single-step transferred off site, CallBridge does not distribute a trunk number. Consequently, a NetworkReached event is not distributed. (ER# 32510, 79905, 80321, 79773)

         
      Found In:  H300 (UK) V1.0-SA05 CAP 2.0, H300 (US) V6.6 with CAP 2.0, HiPath4000 CSTA I V1.0 SA10-6 with CAP 2.0 Fixed In:


      On the Hicom 300 (UK), if a party on an inbound/outbound call initiates a single-step transfer to a distribution device, a phantom call appears on this device (ACD Queue or Routing Point). (ER# 70157, 78582, 79888,  80354)

      Found In: 7.0.2, H300 (UK) V1.0-SA05 Fixed In:


      On the Hicom 300 (UK), the switch rejects a Transfer request and T-Server generates EventError(call has disconnected) in the following scenario:

      • Establish three-party conference
      • TInitiateTransfer or TInitiateConference from conference controller to a distribution device (ACD Queue or Routing Point)

      (ER# 62591, 79889, 78583, 80353)

      Found In: 7.0.2, H300 (UK) V1.0-SA05 Fixed In:


      On the Hicom 300 (UK) only, T-Server incorrectly reports two EventForwardCancels event (for OnBusy and OnNoAnswer) when setting CallFwdOnNoAnswer manually to a native Routing Point. (ER# 71626, 80435)

      Found In: 7.0.2 Fixed In:


      On the Hicom 300 (UK) only,T-Server reports an incorrect EventQueued call state on CallFwdOnNoAnswer to a native Routing Point. (ER# 71624, 80437) 

      Found In: 7.0.2 Fixed In:


      On the Hicom 300 (UK and US) only, the transferring party cannot release a call after an Alternate. The switch accepts the Release request, but does not execute it, so the Genesys request times out.

      (ER# 71421, 79792, 78060, 80355)

      Found In: 7.0.2, H300 (UK) V1.0-SA05, H300 (US) V6.6 CAP 2.0 Fixed In:


      Because of switch messaging issues, T-Server is unable to guarantee the correct propagation of user data from the primary call to a consultation call. The fault occurs because the first consultation call event is reported on the destination, where there is no chance for T-Server to tell that this is a consultation call. Normally, events should be first reported for the originating device where T-Server can put the calls together. (ER# 92475, 92476)

      Found In: 6.5.3 Fixed In:


      On the Hicom 300 (UK) only, because of a problem with CallBridge behavior in CSTA Transferred-Event information, if an incoming or outgoing (loopback) call is single-step transferred to a distribution device, T-Server will distribute EventQueued:
      1. When the PBX sends the transferred event.
      2. When the PBX sends a queued event, but this time with a new ConnID.

      (ER# 41841, 79904, 79772, 80324, 43507, 78591, 79897, 80333)

      Found In: H300 (UK) V1.0-SA05 Fixed In:


      On the Hicom 300 (UK) only, the following scenario (internal call, single-step transfer to busy outbound party) results in EventError due to faulty CallBridge reporting:

      • DN1 calls Routing Point (to make DN1 busy).
      • DN2 calls DN 3. DN3 answers.
      • DN2 initiates a single-step transfer to a busy external DN1.
      • EventReleased on DN1.
      • Attempt to release DN3 - receive EventError "InvalidCallIdentifier" (ErrorCode 1150).
      • On the second attempt to release DN3 - receive EventError "IncorrectObjectState" (ErrorCode 1161).

      (ER# 42238, 79900, 79769, 80331)

      Found In: H300 (UK) V1.0-SA05 Fixed In:


      On the Hicom 300 (UK) only, if a call is blind transferred to a Routing Point with DelayRingback, and the call is not routed before the timer expires, the PBX will recall the call to the transferring device. At this time, T-Server receives a queued event for this call on the transferring device, but does not send RouteEnd on the Routing Point, leaving a stuck call in T-Server. (ER# 41876, 79901, 79770, 80329)

      Found In: H300 (UK) V1.0-SA05 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.


      The Solaris 2.6 operating system is no longer supported.

      Discontinued As Of: 7.6

      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 Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

      • The Framework 7.6 T-Server for Siemens Hicom 300/HiPath 4000 CSTA Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Siemens Hicom 300/HiPath 4000 CSTA I, including configuration options and specific functionality.

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

      • The Platform SDK 7.6 .NET (or Java) API Reference and the Genesys 7 Events and Models Reference Manual contains 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 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 (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 Genesys Documentation 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