Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
8.0.100.18 [01/25/11] – General | X |
As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.
This release note applies to all 8.0 releases of T-Server for Mitel MiTAI.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.07. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of T-Server for Mitel MiTAI.
This release requires Mitel MN3300 PBX version 4.1.SP1 with active software load 10.
Support for call type prediction: On occasions when the CTI information is either insufficient or arrives too late for T-Server to assign a definite call type, T‑Server can now use a call type prediction procedure to assign call type based on configurable rules.
Support for call release tracking: T-Server now provides information about which party initiated the release of a call. This can be valuable for different applications to provide historical and real-time call reporting. This can be configured using the new configuration option releasing-party-report
.
Support for failed route notification: T-Server now supports alarm messages for unsuccessful routing scenarios.
Support for link bandwidth monitoring: T-Server now provides bandwidth monitoring on a CTI link and can notify the Genesys Management Layer when Configuration Layer limits are exceeded.
Support for enhanced request handling: T-Server introduces two major enhancements to queue handling: request conflict resolution and a new device queue.
Enhancements to business call processing: A new configuration option, agent-only-private-calls
, enables you to specify whether calls distributed from a device are considered as private or business calls.
Enhancements to emulated agent functionality: The Emulated Agent feature has a number of enhancements, including:
agent-strict-id
.
Improvements to T-Server logging performance have been implemented.
The Windows 2008 operating system is now supported.
New installation procedure for T-Server 8.0.100.xx: See the T-Server 8.0.100.xx installation procedure in the T-Server for Mitel MiTAI Deployment Guide for details.
There are no corrections and modifications in this initial 8.0 release.
This section provides the latest information on known issues and recommendations associated with this product.
After a PBX reboot, the PBX may not report a back-in-service event for ACD Queue devices. (ER# 254821758)
Found In: MiTAI 13 | Fixed In: |
When a call is made to a busy destination from an analog device, the PBX might provide inconsistent Global Call ID reporting in events, therefore, T-Server cannot track this scenario correctly. (ER# 255450101)
Found In: MiTAI 13 | Fixed In: |
Due to PBX reporting, T-Server might not to provide correct reporting for calls that are redirected to HCI Reroute groups. (ER# 264720867)
Found In: MiTAI 13 | Fixed In: |
Due to PBX reporting issues, T-Server might not provide correct reporting for calls that are redirected to external destinations. (ER# 264814816)
Found In: MiTAI 13 | Fixed In: |
Switch reporting of Alternate Call scenarios that involve a conference is inconsistent. This might lead to inconsistent T-Server behavior in these scenarios. (ER# 264913491)
Found In: MiTAI 13 | Fixed In: |
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: MiTAI 13 | Fixed In: |
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: MiTAI 13 | Fixed In: |
A SingleStepConference
to an external party DN and a SingleStepConference
from an external party DN are not supported. (ER# 256982069)
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: |
A call transfer cannot be completed on an analog device through CTI if this device is registered in Configuration Manager with a switch specific type value of 1
. It is recommended to configure analog DNs as switch specific type 8
or as a VTO port to enable TCompleteTranfer
. (ER# 260487886)
Found In: 8.0.100.18 | Fixed In: |
T-Server is not correctly updated after an analog device performs a SingleStepTransfer
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, a MuteTransfer
and a SingleStepTransfer
will always fail.
The completion of a call transfer is possible only by hanging up an analog device manually. Trying to complete a transfer through CTI will result in an unpredictable behavior.
(ER# 257494837)
Found In: 8.0.100.18 | Fixed In: |
If the GCTI_FORWARD_INTERNAL
Extensions is not passed when call forward on busy is set, or when call forward no answer is set, the PBX will accept calls when they are received from other T-Server (external destination). Also, if setting call forward on a busy destination, or setting call forward no answer with GCTI_FORWARD_INTERNAL
set to a value of 3
, the PBX will accept only calls when received from other T-Servers (external destination). GCTI_FORWARD_INTERNAL
must be set to a value of 3
to set call forward on both an internal call and a call from other T-Servers. (ER# 258989889)
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 a queue. (ER# 264177524)
Found In: 8.0.100.18 | Fixed In: |
T-Server generates a RemoteConnectionFailed
when a route consultation call is completed, after the call arrived on a Native Routing Point (HCI Reroute type groups), from an external party on one PBX to a destination on another PBX through an ISCC, with CastType
set to direct-ani
. (ER# 264872374)
Found In: 8.0.100.18 | Fixed In: |
T-Server does not support the Hot Desking Feature. (ER# 266562580)
Found In: 8.0.100.18 | Fixed In: |
T-Server generates an EventReleased
and an EventError
on the conference initiator in the following scenario:
(ER# 266325684)
Found In: 8.0.100.18 | Fixed In: |
After installing the Mitel USDK 4.0 and T-Server 8.0, you must restart the machine on which they are hosted in order for T-Server to function correctly. (ER# 209099751)
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 option retain-call-tout
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. 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, option rel-cons-reconnect
is now disabled.
(ER# 204272215, 197141605, 201895191, 207143301
Found In: 7.2.001.13 | Fixed In: |
Reporting of conferences is incorrect (multiple EventPartyChanged
events are generated) in a
scenario in which a transfer from a conference is completed after an intrusion.
(ER# 208151035)
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.0.204 | Fixed In: |
EventNetworkReached
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: |
On the MN-3300 PBX, it is not possible to redirect an internal call from a device which has an agent logged into it, to an external device. The redirect request is rejected by the PBX. (ER# 202265421)
Found In: MN-3300 8.0.10.7_1 | Fixed In: |
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: MN-3300 8.0.10.7_1 | Fixed In: |
On the MN-3300, it is not possible to set forwarding on a device that has an agent logged in, to an external device. The request to set forwarding is rejected by the PBX. (ER# 202265486)
Found In: MN-3300 8.0.10.7_1 | Fixed In: |
T-Server rejects the release of an alerting
consultation call with error Incorrect object
state
. (ER# 204279904)
Found In: 7.2.001.13 | Fixed In: |
In a supervised single-step conference, the supervisor is unexpectedly released if another conference party initiates a consultation call. (ER# 200968201)
Found In: MN-3300 8.0.10.7_1 | 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: |
On IP phones only, the PBX does
not report a conference after a split conference is conferenced again. (ER#
200993001)
Found In: MN-3300 8.0.10.7_1 | Fixed In: |
The PBX reports Error: Privilege violation on specified device
on a
Routing Point when a call is routed from HCI Reroute-type groups to an external
destination. After a delay the call is routed. (ER# 200993024)
Found In: MN-3300 8.0.10.7_1 | Fixed In: |
When a device monitors an established call by issung
TSingleStepConference
, and the origination of
the established call then releases, the PBX sends a CallOriginatedEvent
to T-Server for the monitoring
device instead of a CallClearedEvent
. (ER#
113485366)
Found In: MN-3300 7.1.3.4_2, SX-2000 34.2.5.3 | Fixed In: |
It is not possible to divert/deflect/redirect an inbound call via CTI to an outbound destination on MN-300. (ER# 108891433)
Found In: MN-3300 7.1.3.4_2, SX-2000 34.2.5.3 | Fixed In: |
To divert/redirect on the Mitel the destination device number must be issued in the request. The switch cannot redirect to a Login ID. (ER# 113432647)
Found In: Unspecified | Fixed In: |
ConnID is not maintained when making a single-step transfer with COF enabled. (ER# 99231703)
Found In: 7.2 | 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 | 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 consult call.
Therefore T-Server can only generate one ConnID for this device. (ER#
101322958)
Found In: 7.2 | Fixed In: |
It is not possible to issue TRouteCall with RouteTypeReject on a consultation call to a native Routing Point. (ER# 104788451)
Found In: 7.2 | Fixed In: |
It is not possible to release a call that is on a queue or Routing Point after a link reconnection or after a T-Server restart. (ER# 203307391)
Found In: 7.2 | Fixed In: |
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 | 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
. (ER# 111503170)
Found In: 7.2 | Fixed In: |
The MN-3300 PBX fails to report correctly if a transfer
is made from an analog device, answered, then the analog devices tries to clear
the consult, either by TReconnectCall
or TReleaseCall
. (ER# 40947000)
Found In: PBX 6.1.5.4 | Fixed In: |
On the MN-3300, an established internal call is manually
conferenced to an external device. When the conference is completed manually on
the telset, 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: PBX 6.1.5.4 | Fixed In: |
In the following scenario:
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, so T-Server
cannot report correctly when those devices leave the conference. (ER#
102739442)
Found In: SX2000 version 34.2.5.3 and MN3300 version 7.1.3.4_2. | Fixed In: |
When an internal call is transferred externally to an HCI Reroute Group (configured in Genesys as a Routing Point), the PBX sends incorrect events. This will result in the following incorrect call flow on the transferring device:
EventReleased
EventError (call has
disconnected)
is distributed in response to the TCompleteTransfer
.
On the Routing Point the following incorrect call flow occurs:
EventQueued
EventRouteRequest
EventAbandoned
EventQueued (PBX reports
new call therefore new ConnID
)
EventRouteRequest (new
ConnID)
(ER# 104521930)
Found In: SX2000 version 34.2.5.3 and MN3300 version 7.1.3.4_2. | Fixed In: |
It is not possible to release a conference party after a conference that has been split is conferenced again. (ER# 104521923)
Found In: SX2000 version 34.2.5.3 and MN3300 version 7.1.3.4_2. | Fixed In: |
The timer configured in option prd-dist-call-ans-time
is not backwardly compatible
if a switchover is performed from a primary 7.0 T-Server to a backup 7.2
T-Server. In this instance the timer will never expire. (ER# 104511141)
Found In: 7.2 | Fixed In: |
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 value
recall
should not be used when routing from
emulated Routing Points. (ER# 100891071)
Found In: SX2000 version 34.2.5.3 and MN3300 version 7.1.3.4_2. | Fixed In: |
Call treatment while in ACD queue is not supported via CTI (ER# 86424, 86742).
Found In: MiTAI 11 | Fixed In: |
Due to switch reporting (MN-3300), in this scenario we
do not get an EventPartyDeleted
on DN2 when
external DN3 releases the call.
Due to switch reporting (MN-3300), on the second
alternate we do not get EventHeld
or EventRetrieved
, even though the call has actually
alternated. (ER# 4712093).
Found In: 7.0.203.01 | Fixed In: |
In single-step transfer to a DN with immediate
forwarding set, no Forwarded
call state in the
EventRinging
is reported, only the Transfer
call state. (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 an event cause of DivertedNoAnswerFrom
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 external, the
remote T-Server has not seen the RequestRouteCall
being made, therefore does not know
that the call was routed, hence the call state is 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 RequestAnswerCall
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 dialled to DN2. It is not
possible to answer the ringing Callback on DN1 via CTI, because T-Server
generates an EventDialing
instead of EventRinging
. 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 this situation, the PBX sends an EventDestinationBusy
on DN1 for the dialing call followed by an EventAbandoned
on DN2 and it does not provide a
Released
event for the Dialing call for DN1.
(ER# 97462, 96898)
Found In: 7.0.202.03 | Fixed In: |
The switch completes a four-party conference when DN 3
attempts to alternate after DN 4 has answered. The alternate
request is not performed and EventError
is generated. (ER# 53235, 86560)
Found In: 6.5.3 | Fixed In: |
RequestCallForwardSet
on BusyNoAnswer
produces the following
sequence of events:
RequestCallForwardSet
EventForwardSet
EventForwardCancel
EventForwardSet
The forward is set and works correctly after this. (ER# 67195, 86623)
Found In: 7.0.200.00 | Fixed In: |
In the following scenario:
After establishing the consult call, release the consult call and then 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: |
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: MiTAI 11.0.1.6 | Fixed In: |
If configuration
option agent-no-answer-overflow
is set to the
value recall
, the switch will not return the call
to the first distribution point. (ER# 42707)
Found In: | Fixed In: |
When a call is made from DN 1 to DN 2
and overflowed on no-answer, after an interval the switch releases DN
but reports call state redirected
on DN
2, instead of OK. (ER# 42715, 86612)
Found In: 6.5.200.01 | Fixed In: |
In the following scenario, Mitel camp-on functionality is unreliable:
route
(call B)
2003
RequestAnswerCall
on Call B: rejected by the switch.
2003
RequestReleaseCall
on Call A: the call is dropped.
EventReleased
on Call A, EventAbandoned
, then EventRinging
on Call B. The EventRinging
is with a new connection ID:
therefore ISCC is not working correctly.(ER# 41969, 86482)
Found In: 6.5.200.02 | Fixed In: |
Genesys strongly discourages use of the secondary buttons of the monitored DNs. Although the 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: MiTAI 11 | Fixed In: |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.
There are no discontinued features or functions for this product.
Information in this section is included for international customers.
There are no known internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Framework 8.0 T-Server for Mitel MiTAI Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for Mitel MiTAI including configuration options and switch functionality.
Framework 8.0 Deployment Guide helps you configure, install, start, and stop Framework components.
The Voice Platform SDK 8.0 .NET (or Java) API Reference and the Genesys 7 Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.
Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
Product documentation is also provided on a Documentation Library DVD, which is produced monthly. The New Documents on this DVD page on the DVD indicates the DVD production date. Because the DVD is produced monthly, documentation on the Technical Support website may be more up-to-date than that on the DVD. To verify the latest version of a document, check the version number, located on the second page in PDFs and on the "About This File" topic for Help files.