Release Note

T-Server for Mitel MiTAI

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2012–2018

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.1.000.13 [09/27/18] – Hot Fix           X
8.1.000.12 [08/13/18] – Hot Fix           X
8.1.000.11 [06/04/18] – Hot Fix           X
8.1.000.10 [12/19/16] – General           X
8.1.000.09 [05/12/14] – Hot Fix           X
8.1.000.07 [09/14/12] – General           X

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

This release note applies to all 8.1 releases of T-Server for Mitel MiTAI.

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.


Release Number 8.1.000.13 [09/27/18] – 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 8.1.001.79. 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 and modifications:


T-Server now correctly reports the scenario where:

Previously, due to incomplete reporting from PBX, an EventCallDeleted was not reported after the call involved in the scenario was disconnected from a device with a free-seating agent. (UKTS-17702)


Top of Page


Release Number 8.1.000.12 [08/13/18] – 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 8.1.001.79. 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 and modifications:


T-Server now correctly reports the EventCallDeleted event when an originating call is disconnected during a Single Step Transfer to a distribution device. Previously, due to incomplete reporting from the PBX, the EventCallDeleted was not reported after the call was disconnected. (UKTS-17689)


Top of Page


Release Number 8.1.000.11 [06/04/18] – 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 8.1.001.79. 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:

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server provides a workaround for the scenario where an inbound call is disconnected on origination while in the process of being transferred via Single Step Transfer to a routing point or a distribution point and PBX does not provide sufficient reporting to clean up the existing call. T-Server now deletes such a call automatically. (UKTS-17644)


Top of Page


Release Number 8.1.000.10 [12/19/16] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.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 version was first released as a Hot Fix on 08/06/14. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server now recognizes when it can publish an EventAgentReady or EventAgentNotReady message without waiting for a possible busy (reason) code event from the switch. When waiting is necessary, it also applies a lower limit to the wait duration to avoid long delays. Previously, T-Server sometimes waited unnecessarily for a busy code event from the switch before publishing the message. (UKTS-17134)


Top of Page


Release Number 8.1.000.09 [05/12/14] – 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 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:


When processing inbound call divert scenarios, including call forwarding and routing, where the originator DN ANI is absent, T-Server no longer creates duplicate call objects. Previously, this issue resulted in stuck calls or failures invoking call requests. (UKTS-17060)


Top of Page


Release Number 8.1.000.07 [09/14/12] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.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.

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

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:


T-Server now works correctly in multi-site environments using Inter Server Call Control (ISCC) with T-Server version 8.0 and later. Previously, T-Server did not support these environments. (ER# 100356397)


T-Server now correctly supports the synchronization of Emulated Agent States (Soft Agent) with the PBX. Previously, T-Server did not support this synchronization. (ER# 99749321)


T-Server now correctly updates the high-availability (HA) redundancy pair in hot-standby mode with the pending synchronized requests upon shutdown. Previously, the primary T-Server may have canceled ongoing predictive call scenarios upon shutdown. (ER# 265372558)


Top of Page


Known Issues and Recommendations

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


Support for the Emulated Supervised Routing feature is not available for the 8.1 release of this T-Server. (ER# 308607112)

Found In: 8.1.000.07 Fixed In: 

T-Server does not support the Mitel external Hot Desking Feature. (ER# 266562580)

Found In: 8.1.000.07 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): In some cases, the PBX might fail to report a call transfer completion for outbound calls that are transferred to internal destinations. (ER# 266562574)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): T-Server reports the incorrect ReleasingParty extension key when the originator of a call (that is not answered) releases the call. (ER# 266429705)

Found In: 8.0.100.18 Fixed In: 

T-Server generates both EventReleased and EventError events in response to a TAlternateCall request in the following scenario:

  1. A conference call is initiated.
  2. The destination party answers the call.
  3. The conference initiator sends a TAlternateCall request.

(ER# 266325684)

Found In: 8.0.100.18 Fixed In: 

T-Server generates an EventRemoteConnectionFailed event when a consultation call to a Routing Point is completed in the following scenario:

  1. The call arrives on a Native Routing Point (HCIReroute-type Hunt Group), from an external party on one PBX to a destination on another PBX through an ISCC.
  2. The value of the cast-type option is set to direct-ani.

(ER# 264872374)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): Due to PBX reporting issues, T-Server might not provide the correct reporting for calls that are redirected to external destinations. (ER# 264814816)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): Due to PBX reporting, T-Server might not provide the correct reporting for calls that are redirected to HCIReroute Hunt Groups (HGs). (ER# 264720867)

Found In: 8.0.100.18 Fixed In: 

T-Server generates an incorrect call state of OK after a call is forwarded to an ACD Queue, because the PBX does not provide a cause that identifies it as being forwarded to an ACD Queue. (ER# 264177524)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): The PBX only reports one CallID attribute during a single-step transfer, so T-Server does not distribute the EventPartyChanged event. (ER# 262915716)

Found In: 8.0.100.18 Fixed In: 

A call transfer cannot be completed on an analog device through a computer-telephony integration (CTI) link, if this device is registered in Configuration Manager with a switch-specific type value of 1.

Workaround: It is recommended to configure analog DNs as a switch-specific type 8 or as a VTO port to enable the TCompleteTransfer request. (ER# 260487886)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): If a GCTI_FORWARD_INTERNAL Extensions attribute is not provided in a TCallSetForward request with a subtype of either OnBusy or OnNoAnswer, the PBX accepts calls from an external destination. GCTI_FORWARD_INTERNAL must be set to the default value of 3 to ensure that both internal and external calls are forwarded. (ER# 258989889)

Found In: 8.0.100.18 Fixed In: 

If a call on any primary device is dropped after a call intrusion is completed, the call on the other party will be dropped. (ER# 258945521)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): If a held call is released by the other party, the PBX might, in some cases, fail to report the release of the call on the device where the call was held. If a consultation call is present, the held call is cleaned up by T-Server when the consultation call is subsequently released. (ER# 258388016)

Found In: 8.0.100.18 Fixed In: 

T-Server is not correctly updated after an analog device sends a TSingleStepTransfer request to a busy external party DN. It is not possible to complete a call transfer on an analog device, regardless of the destination state of the party, therefore, TMuteTransfer requests and TSingleStepTransfer requests will always fail. The completion of a call transfer is possible only by manually hanging up an analog device. Trying to complete a transfer through a CTI link results in inconsistent T-Server behavior. (ER# 257494837)

Found In: 8.0.100.18 Fixed In: 

A TSingleStepConference request to an external party DN and a TSingleStepConference request from an external party DN are not supported. (ER# 256982069)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): When a call is made to a busy destination from an analog device, the PBX might provide inconsistent network-wide CallID reporting in events; therefore, T-Server cannot track this scenario correctly. (ER# 255450101)

Found In: 8.0.100.18 Fixed In: 

PBX Limitation (MiTAI v13 SDK or later): After a PBX reboot, the PBX may not report an EventDNBackInService event for ACD Queue devices. (ER# 254821758)

Found In: 8.0.100.18 Fixed In: 

After installing the Mitel MiTAI USDK V 4.0 and T-Server 8.0, you must restart the Mitel T-Server application in order for T-Server to function correctly. (ER# 209099751)

Found In: 7.2.001.13 Fixed In: 

An EventNetworkReached event is not reported when the call originator makes a single-step transfer to an external device. (ER# 208151089)

Found In: 7.2.001.13 Fixed In: 

The reporting of conference calls is incorrect (multiple EventPartyChanged events are generated) in a scenario in which a transfer from a conference call is completed after an intrusion. (ER# 208151035)

Found In: 7.2.001.13 Fixed In: 

If an inbound call is diverted to an external destination, and a second call appears on the same trunk within a few seconds, then the second call's connection ID is a duplicate of the first call's. The likelihood of this occurring can be reduced by setting the value of the retain-call-tout option to an interval smaller than the time between the divert of the first call and the initiation of the second call. (ER# 207897025)

Found In: 7.2.001.13 Fixed In: 

Processing of the release of consultation calls has been enhanced. The switch function SXCancelConsCall is now used instead of SXNewCall or SXClearCall. This change now means that the original main call is retrieved from hold (reconnected) when the consultation call is released on the originator.

Note: As a consequence of this change, the rel-cons-reconnect configuration option is now disabled. (ER# 207143301, 204272215, 201895191, 197141605)

Found In: 7.2.001.13 Fixed In: 

T-Server rejects the release of an alerting consultation call with an Incorrect object state error message. (ER# 204279904)

Found In: 7.2.001.13 Fixed In: 

In the following scenarios, the PBX reports calls incorrectly after a T-Server restart or link reconnection:

(ER# 203469554)

Found In: 7.2.001.13 Fixed In: 

T-Server rejects requests to release ringing calls on devices that are monitoring via single-step conference. (ER# 200773539)

Found In: 7.2.001.13 Fixed In: 

Three EventPartyChanged messages are generated when an unmonitored transfer to a queue is made. (ER# 99747836)

Found In: 7.2.001.13 Fixed In: 

It is not possible to release a call that is on an ACD Queue or Routing Point after a link reconnection or after a T-Server restart. (ER# 203307391)

Found In: 7.2.001.07 Fixed In: 

PBX Limitation (MN-3300 8.0.10.7_1): On the MN-3300 PBX, after a consultation call is released by the destination, the main call remains on hold. After the main call is released by the other party, the DN which was on hold remains off hook. (ER# 202657951)

Found In: 7.2.001.07 Fixed In: 

PBX Limitation (MN-3300 8.0.10.7_1): On the MN-3300 PBX, it is not possible to set call forwarding on a device that has an agent logged in, to an external device. The request to set call forwarding is rejected by the PBX. (ER# 202265486)

Found In: 7.2.001.02 Fixed In: 

PBX Limitation (MN-3300 8.0.10.7_1): On the MN-3300 PBX, it is not possible to redirect an internal call from a device that has an agent logged into it, to an external device. The redirect request is rejected by the PBX. (ER# 202265421)

Found In: 7.2.001.02 Fixed In: 

PBX Limitation (MN-3300 8.0.10.7_1): The PBX reports an Error: Privilege violation on specified device message on a Routing Point when a call is routed from HCIReroute-type Hunt Groups to an external destination. After a delay, the call is routed. (ER# 200993024)

Found In: 7.2.001.01 Fixed In: 

PBX Limitation (MN-3300 8.0.10.7_1): On IP phones only—the PBX does not report a conference call after a split conference is conferenced again. (ER# 200993001)

Found In: 7.2.001.01 Fixed In: 

PBX Limitation (MN-3300 8.0.10.7_1): In a supervised single-step conference, the supervisor is unexpectedly released if another conference party initiates a consultation call. (ER# 200968201)

Found In: 7.2.001.01 Fixed In: 

The Inter Service Call Control (ISCC) transaction type direct-ani fails when a call is routed to an external destination after the call originator completes a transfer to a Routing Point. (ER# 200066861)

Found In: 7.2.001.01 Fixed In: 

PBX Limitation (MN-3300 7.1.3.4_2 and SX2000 version 34.2.5.3): When an internal call is transferred externally to an HCIReroute-type Hunt Group (configured in the configuration environment as a Routing Point), the PBX sends incorrect events. This results in the following incorrect call flow on the transferring device:

  1. An EventReleased event is distributed.
  2. An EventError event (the call has disconnected) is distributed in response to a TCompleteTransfer request.
  3. The PBX will now not allow the held primary leg to be retrieved or released by the transferring device.

On the Routing Point, the following incorrect call flow occurs:

  1. EventQueued
  2. EventRouteRequest
  3. EventAbandoned
  4. EventQueued (the PBX reports the new call, therefore a new ConnID attribute)
  5. EventRouteRequest (a new ConnID attribute)

(ER# 104521930)

Found In: 7.2.001.01 Fixed In: 

PBX Limitation (MN-3300 7.1.3.4_2, SX-2000 34.2.5.3): When a device monitors an established call by issuing a TSingleStepConference request, and the origination of the established call then releases, the PBX sends CallOriginatedEvent to T-Server for the monitoring device instead of a CallClearedEvent. (ER# 113485366)

Found In: 7.2.001.00 Fixed In: 

When using Emulated Predictive Dialing, if T-Server drops the call because the AttributeTimeout has expired, then the call state is incorrectly reported as Dropped instead of NoAnswer. (ER# 111503170)

Found In: 7.2.000.03 Fixed In: 

PBX Limitation (MN-3300 7.1.3.4_2, SX-2000 34.2.5.3): It is not possible to divert/deflect/redirect an inbound call via CTI to an outbound destination on MN-300. (ER# 108891433)

Found In: 7.2.000.02 Fixed In: 

PBX Limitation (MN-3300 7.1.3.4_2 and SX2000 version 34.2.5.3): It is not possible to release a conference party after a conference that has been split is conferenced again. (ER# 104521923)

Found In: 7.2.000.02 Fixed In: 

It is not possible to issue a TRouteCall request with RouteTypeReject on a consultation call to a native Routing Point. (ER# 104788451)

Found In: 7.2.000.01 Fixed In: 

The timer configured in the prd-dist-call-ans-time configuration option is not backward-compatible, if a switchover is performed from a primary 7.0 T-Server to a backup 7.2 T-Server. In this scenario, the timer will never expire. (ER# 104511141)

Found In: 7.2.000.01 Fixed In: 

The PBX does not provide full snapshot information on T-Server start/link reconnection for devices on calls. Instead it only provides a call state. This is enough information for T-Server to generate a ConnID and device state (such as dialing and ringing), but not enough to match calls. Thus, each device on a call will have a unique ConnID. It also means there is no way to tell if a device has a primary and a consultation call. Therefore T-Server can only generate one ConnID for this device. (ER# 101322958)

Found In: 7.2.000.01 Fixed In: 

Genesys does not support configurations using a primary 7.2 T-Server and backup 7.0 T-Server. (ER# 10089112)

Found In: 7.2.000.01 Fixed In: 

PBX Limitation (MN-3300 7.1.3.4_2 and SX2000 version 34.2.5.3): The PBX does not distribute a call to a Hunt Group member after a redirect from an emulated Routing Point, leaving the call stuck on the emulated Routing Point. As a result, the no-answer-overflow option value recall should not be used when routing from emulated Routing Points. (ER# 100891071)

Found In: 7.2.000.01 Fixed In: 

To divert/redirect on the Mitel switch, the destination device number must be issued in the request. The switch cannot redirect to a Login ID. (ER# 113432647)

Found In: 7.2.000.01 Fixed In: 

The ConnID attribute is not maintained when making a single-step transfer with Call Overflow (COF) enabled. (ER# 99231703)

Found In: 7.2.000.01 Fixed In: 

PBX Limitation (MN-3300 6.1.5.4 and SX2000 -34.2.5.3): On the MN-3300, an established internal call is manually conferenced to an external device. When the conference call is completed manually on the telephone set, the PBX sends an Originated event against the conference controller before the Conferenced event. This prevents T-Server from correctly reporting the EventPartyAdded events. (ER# 40947030)

Found In: 7.2.000.01 Fixed In: 

PBX Limitation (MN-3300 6.1.5.4): The MN-3300 PBX fails to report correctly if a transfer is made from an analog device and answered, then the analog devices tries to clear the consultation call, either by sending a TReconnectCall request or a TReleaseCall request. (ER# 40947000)

Found In: 7.2.000.01 Fixed In: 

PBX Limitation (MN-3300 7.1.3.4_2 and SX2000 version 34.2.5.3): In the following scenario:

  1. Two unmonitored devices are on a call.
  2. A conference is made to a monitored device and completed.
  3. T-Server does not report on the CallConferencedEvent.

If one of the unmonitored devices drops, then T-Server does not report on the DeviceDroppedEvent. The switch omits the conferenced party information. The unmonitored origination of the call does not appear in the switch conference reporting that is distributed to the monitored conference destination. This makes it impossible to identify all the parties in the conference call, so T-Server cannot report correctly when those devices leave the conference. (ER# 102739442)

Found In: 7.0.204.00 Fixed In: 

PBX Limitation (MN-3300): Due to switch reporting (MN-3300), there is no EventPartyDeleted event attached to DN2 when the external DN3 releases the call in the following scenario:

  1. An external DN1 and an internal DN2 are established in a call (inbound or outbound).
  2. DN2 initiates a conference call to a Routing Point.
  3. The Routing Point routes to an external DN3.
  4. DN3 answers, and the conference call is completed.
  5. DN3 releases the call.

Due to switch reporting (MN-3300), on the second alternate there is no EventHeld or EventRetrieved generated, even though the call has actually alternated, in the following scenario:

  1. An external DN1 and an internal DN2 are established in a call (inbound or outbound).
  2. DN2 initiates a conference call to either the internal or external call.
  3. DN2 completes the conference call.
  4. DN2 splits the conference call.
  5. DN2 alternates the call.
  6. DN2 alternates the call again.

(ER# 4712093)

Found In: 7.0.203.01 Fixed In: 

PBX Limitation (MiTAI v11): Call treatment while in an ACD Queue is not supported via CTI. (ER# 86424, 86742)

Found In: 7.0.203.01 Fixed In: 

The PBX sends an EventDestinationBusy event on DN1 for the dialing call followed by an EventAbandoned event on DN2 and it does not provide a EventReleased event for the dialing call for DN1 in the following scenario:

(ER# 97462, 96898)

Found In: 7.0.202.03 Fixed In: 

In a single-step transfer to a DN with the call-forwarding set to immediate, no Forwarded call state in the EventRinging is reported, and only the Transfer call state is reported. (ER# 97404)

Found In: 7.0.202.03 Fixed In: 

When a call is routed to an external DN, T-Server provides a call state of Forwarded instead of OK in the EventRinging on the remote site. This is because the PBX provides a DivertedNoAnswerFrom event to T-Server on routing a call. Unless T-Server has seen the request being made, it cannot know what the correct call state should be, so it is marked as Forwarded. In the case of routing to an external DN, the remote T-Server has not seen the TRouteCall being made, therefore it does not know that the call was routed, hence the call state Forwarded. (ER# 97384)

Found In: 7.0.202.03 Fixed In: 

If a DN has two calls ringing on it (primary and camp-on), T-Server cannot distinguish between the two when sending the TAnswerCall to the PBX. (ER# 97053)

Found In: 7.0.202.03 Fixed In: 

If DN1 requests a callback to DN2, it is necessary to answer the ringing call on DN1 before the call gets dialed to DN2. It is not possible to answer the ringing callback on DN1 via CTI, because T-Server generates an EventDialing event instead of an EventRinging event. The call must be answered manually. Once this is answered, it is then possible to continue making requests via CTI on both DNs. (ER# 96944)

Found In: 7.0.202.03 Fixed In: 

Spurious EventAbandoned and EventRinging events are propagated by the PBX in some camp-on scenarios. (ER# 96891)

Found In: 7.0.202.03 Fixed In: 

In the following scenario:

  1. Make a call with ISCC to an external party.
  2. The external party answers the call.
  3. A call transfer is initiated back to a DN on the local PBX through ISCC from the external party.

After establishing the consultation call, release the consultation call and then release the primary call from the main site. The DN on the remote site remains off hook and has to be placed on hook either by releasing through CTI or manually. (ER# 85420, 85408)

Found In: 7.0.201.01 Fixed In: 

A TCallForwardSet request with a OnBusyAndNoAnswer request subtype produces the following sequence of events:

  1. TCallForwardSet
  2. EventForwardSet
  3. EventForwardCancel
  4. EventForwardSet

The call-forward is set and works correctly after this. (ER# 86623, 67195)

Found In: 7.0.200.00 Fixed In: 

The switch completes a four-party conference when DN3 attempts to alternate the call after DN4 has answered. The TAlternateCall request is not performed and an EventError event is generated. (ER# 86560, 53235)

Found In: 6.5.300.00 Fixed In: 

The Mitel camp-on functionality is unreliable in the following scenario:

T-Server A (2001 and 2002) and T-Server B (2003):

  1. Make an internal call from 2003 to another destination, but the call is not answered (Call A).
  2. Make a call from 2001 to 2003 via Inter Server Call Control (ISCC, formerly known as external routing) with cast type = route (call B).
  3. T-Server B (2003) sends a TAnswerCall request on Call B: rejected by the switch.
  4. T-Server B (2003) sends a TReleaseCall on Call A: the call is dropped.
  5. On T-Server B (2003), an EventReleased event is generated on Call A, then an EventAbandoned event, then an EventRinging event is generated on Call B. The EventRinging event has a new ConnID; therefore ISCC is not working correctly.

(ER# 86482, 41969)

Found In: 6.5.200.02 Fixed In: 

When a call is made from DN1 to DN2 and is overflowed on no-answer, after an interval the switch releases the DN, but reports the call state as redirected on DN2, instead of OK. (ER# 86612, 42715)

Found In: 6.5.200.01 Fixed In: 

PBX Limitation (MiTAI 11.0.1.6): Because of a MiTAI limitation, it is not possible to establish a monitor for a second time without restarting T-Server. (ER# 85625, 64030)

Found In: 6.5.200.01 Fixed In: 

If the value of the agent-no-answer-overflow configuration option is set to recall, the switch will not return the call to the first distribution point. (ER# 42707)

Found In: 6.5.200.00 Fixed In: 

PBX Limitation (MiTAI 11.0.1.6): Genesys strongly discourages any use of the secondary buttons of the monitored DNs. Although T-Server tries to make the most sensible reporting possible, use of such buttons can have adverse effects on real time statistics and historical reporting. (ER# 86637, 63096)

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


There are no discontinued features or functions for this product.


Top of Page


Internationalization

Information in this section is included for international customers.


There are no known internationalization issues for this product.


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

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