Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.004.02 [06/22/18] – Hot Fix | X | X | ||||
8.1.004.01 [02/07/18] – General | X | X | X | X | ||
8.1.003.02 [02/16/17] – General | X | X | X | X | ||
8.1.003.01 [01/17/17] – Hot Fix | X | X | ||||
8.1.003.00 [03/20/15] – General | X | X | X | X | ||
8.1.002.02 [10/23/14] – General | X | X | X | X | X | X |
8.1.001.06 [04/04/13] – Hot Fix | X | X | ||||
8.1.001.04 [10/19/12] – Hot Fix | X | |||||
8.1.001.03 [04/20/12] – Hot Fix | X | |||||
8.1.001.02 [03/27/12] – General | X | X | X | X | X | X |
8.1.000.06 [11/29/11] – Hot Fix | X | |||||
8.1.000.05 [11/03/11] – General | X | X | X | X | X | 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.genesys.com for more details.
This release note applies to all 8.1 releases of T-Server for Aastra MXONE CSTA I (formerly T-Server for Ericsson MD110).
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see T-Servers. Please contact your Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
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 does not contain any new features or functionality.
This release includes the following corrections or modifications:
T-Server no longer sends an EventReleased and an EventError with the same reference ID to the T-Server client when the agent and customer release a call simultaneously. (UKTS-17672)
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.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.
There are no restrictions for this release. This release contains the following new features or functionality:
Support for Windows Server 2016 running in native (64-bit) mode. See the T-Server Aastra MX-ONE page in the Genesys Supported Operating Environment Reference Guide page for more detailed information and a list of all supported operating systems. (UKTS-17617)
DTMF data in T-Lib messages is now hidden in the T-Server log when the configuration option log-filter\hide-tlib-sensitive-data is set to true. (UKTS-17580)
This release includes the following corrections or modifications:
T-Server now correctly includes a ReferenceID in an EventDialing event after a RequestMakeCall request. Previously, the missing ReferenceID could result in a failed call. (UKTS-17610)
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.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.
There are no restrictions for this release. This release contains the following new features or functionality:
Support for Red Hat Enterprise Linux (RHEL) 6.x and 7.x.
This release includes no corrections or modifications.
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.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.
There are no restrictions for this release. This release does not contain any new features or functionality.
This release includes the following corrections or modifications:
T-Server no longer becomes unstable after receiving the CSTA event ConnectionCleared with a valid dialingNumber in the CSTA Connection structure and a releasingDevice of notKnown : NULL
. (UKTS-17512)
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.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.
There are no restrictions for this release. This release contains the following new features or functionality:
Support for Windows Server 2012.
T-Server now enables you to specify different rules for internal and external call forwarding. T-Server matches the forwarding destination number against a set of rules and forwards calls accordingly.
Configure any number of rules in a configuration section called fwd-type-rules, using the following format:
rule-1 as pattern=AAA;type=external
...
rule-N as pattern=AAAA;type=internal
For pattern definition, use Augmented Backus-Naur Form (ABNF) notation. See RFC-2234 and the "Number Translation Rules" chapter in the T-Server Deployment Guide for more information.
If the pattern specified in the rule matches the forwarding destination, then T-Server applies the specified forwarding type, "external" or "internal".
If no rules are configured or the forwarding destination number does not match any configured rule, then T-Server determines the forwarding type using the maximum length of the monitored number (which is the old behavior).
(UKTS-17255)
This release includes no corrections or modifications.
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.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.
There are no restrictions for this release. This release contains the following new features or functionality:
This release includes no corrections or modifications.
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.1.001.60. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This release does not contain any new features or functionality.
This release includes the following corrections or modifications:
T-Server now supports backwards compatibility for the 7.6 version of T-Server for Ericsson MD110 in emulated After-Call Work (ACW) scenarios for real agents. Previously, T-Server sometimes did not apply the emulated ACW for an agent in such scenarios.
Note: The name of T-Server for Ericsson MD110 changed to T-Server for Aastra MXONE CSTA I in version 8.1.
(ER# 316553663)
If a call is transferred from a CAS port to a monitored extension by default (the analog-transfer
configuration option is set to 1
), T-Server no longer keeps the CAS port in off-hook state.
Note: This issue was corrected for Solaris.
(ER# 297294252)
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.1.001.47. 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.
This release includes the following correction or modification:
T-Server now supports the sip-trunk-id
configuration option, which allows T-Server to make a difference between calls that have the SIP trunk ID as the value that is specified in the sip-trunk-id
option. This option is set in the TServer
section of the T-Server Application object.
sip-trunk-id
Default Value: An empty string
Valid Values: A comma-separated list of SIP trunks (as reported by the PBX), or use "*"
to indicate that all trunks are SIP trunks.
Changes Take Effect: Immediately
Specifies that T-Server should treat calls that have the same SIP trunk ID as the value specified in the sip-trunk-id
option as separate calls. The PBX generates the SIP trunk ID by using the following format: a three digit routing number, a three digit server number, and a three digit trunk number.
Previously, T-Server might have reported multiple calls from the SIP trunk as one call. (ER# 306754470)
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.1.001.38. 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.
This release includes the following corrections or modifications:
If a call is transferred from a CAS port to a monitored extension by default (the analog-transfer
configuration option is set to 1
), T-Server no longer keeps the CAS port in off-hook state. (ER# 297294252)
Note: This issue was corrected for Windows.
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.1.001.38. 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.
This release includes the following corrections or modifications:
T-Server now restores party information using the CSTA Conferenced event. Previously, issues could happen when the PBX reported an external party release for the party that actually remained on the call. (ER# 289953954)
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.1.000.25. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer occasionally becomes unstable when the PBX reports a CSTA Transferred
event with an incomplete list of new connections (such as, the device identifier in the connection list is missing). (ER# 287221753)
The following Known Issues have been also corrected: ER# 243487529, 243723721, 243487697, and 243516834.
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.1.000.25. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of T-Server for Aastra MXONE CSTA I.
background-processing
configuration option has been changed to true.
- heartbeat-period
- hangup-restart
(ER# 214052846)
This release also includes the following corrections and modifications:
T-Server now correctly reports events in the scenario where an incoming call has the same originator (ANI) as a DN monitored on the switch. (ER# 277149838)
T-Server now operates correctly when DNs are disabled and enabled in Configuration Manager in quick succession. Previously, T-Server might have entered a continuous processing loop in such a scenario. (ER# 281536991)
T-Server no longer becomes unstable after transfer is completed to an emulated Routing Point with supervised routing in progress. (ER# 278712725)
The option kpl-loss-rate
has been removed from T-Server. (ER# 275364174)
This section provides the latest information on known issues and recommendations associated with this product.
PBX limitation: outbound calls made through an ISDN trunk cannot be routed through the same trunk. (UKTS-17220)
Found In: | Fixed In: |
When agents makes multiple (chained) consultation calls during inbound or outbound calls, the switch may fail to report events for Reconnect or Retrieve call. PBX failure to report such events may affect Emulated Predictive Call and Agent No Answer supervision functionality in T-Server. (UKTS-17221)
Found In: | Fixed In: |
Switches do not support blind transfer completion if the other party in a transferring call is On Hold. (UKTS-17222)
Found In: | Fixed In: |
When a consultation call is mute transferred or blind transferred to a routing point, consecutive routing to the new destination produces a new call in the switch. This incorrect reporting causes the loss of Genesys-specific data attached to the call prior the routing. (UKTS-17223)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.1 SP3). The PBX does not send a CSTA ConnectionCleared
event for releasing a call on the origination DN in the following scenario:
Route
(at the same site as the first extension through an ISDN Trunk). The call diverts to an agent. The initiator completes the transfer before the agent answers.ConnectionCleared
event on releasing the call.As a result, the call becomes stuck. This behavior does not affect the primary T-Server, which is able to clear stuck calls using the snapshot. However, it may cause the backup T-Server to become unstable. To avoid this, the T-Server call-cleanup mechanism needs to be set to stop stuck calls from accumulating in memory. (ER# 296278209)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.1 SP 3). T-Server does not report an EventReleased
message in the following scenario:
After the agent releases the call, T-Server does not report EventReleased
, because the PBX does not report ConnectionCleared
on the agent. (ER# 287562523)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.1 SP 3). T-Server incorrectly reports an EventAbandoned
message in the following scenario:
TRouteCall
request) routes the call to another extension on Site 2.EventAbandoned
, because the PBX sends EventError
and ConnectionCleared
messages on the Hunt Group member. (ER# 287562433)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.1 SP 3, AL7 SP2). T-Server is not able to set or cancel call forwarding to an external device via CTI. (ER# 284960631)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.1 SP 3, AL7 SP2). T-Server incorrectly reports an EventAbandoned
message in the following scenario:
After the call redirects back to the ACD Group, T-Server reports EventAbandoned
to the agent instead of EventReleased
, because the switch reports trunk optimization after the transfer, but fails to report that the call was returned back to the ACD Group. (ER# 284960640)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.1 SP 3, AL7 SP2). T-Server does not report an EventPartyChanged
message in the following scenario:
There is no EventPartyChanged
reported on the monitored extension, because the switch does not report unmonitored transfer completion to T-Server of monitored extensions. The switch reports that the call was released and established with a new connection ID instead of a transfer event. T-Server is unable to use this report. (ER# 284960647)
Found In: | Fixed In: |
When a group of T-Server DNs is disabled and enabled in configuration multiple times, multiple monitors on the same DN may be requested on the switch. T-Server functionality is not affected, but this scenario may result in a resource leak on the switch. (ER# 284960678)
Found In: 8.1.000.05 | Fixed In: |
An Agent No Answer
action may not be executed when a request for No Answer
supervision on that Agent is in progress. Use the option agent-emu-login-on-call = true
when a workaround is required. (ER# 284960684)
Found In: 8.1.000.05 | Fixed In: |
PBX limitation (AL7). When an agent has immediate call forward set to a CTI Group, and a call is made to the agent, T-Server reports an incorrect CallState
of Ok
on the CTI Group. The reason for this is that for the CTI Group, the PBX incorrectly reports a cause of redirected
instead of a cause of CallForwardAlways
, which is reported on the originator.
The cause that is reported on a CTI Group should be the same as the cause on the originator (CallForwardAlways
). In the scenario above, T-Server cannot use the cause for Reporting since the cause on the originator and on the CTI Group are different. (ER# 267335717)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.2 SP2). An incorrect ConnID
is generated on EventRinging
for a destination DN on an internal call, and the switch reuses the Call ID from an outbound call for an inbound call in the following scenario:
The cast-type
option is set to route
.
The event-propagation
option is set to list
.
The consult-user-data
option is set to separate
.
The use-data-from
option is set to consult-user-data
.
RequestInitiateTransfer
is made from the agent on ODN2 to a native Routing Point (divert from the Queue) through ISCC.
RequestCompleteTransfer
is performed by the agent on ODN2.
T-Server generates an incorrect ConnID
for EventRinging
on DN1, and T-Server generates a call state of Redirected
on DN1 instead of Ok
because the switch reuses the Call ID from the outbound call (made through the outbound Trunk) for the inbound call (from the incoming Trunk). (ER# 229341751)
Found In: | Fixed In: |
PBX limitation (MX-ONE 4.0, AL4 SP21). When setting an Absence code on an IP Phone (via RequestDNDOn
), the request times out because there is no reporting from the switch. (ER# 243481471)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.2 SP2). Supervised routing of a call to a DN does not work if the call is made from a SIP DN in the following scenario:
The supervised-route-timeout
option is set to 5
.
The CSTA error: systemResourceErrors : generic
is received.
(ER# 234796352)
Found In: | Fixed In: |
MX-ONE: T-Server generates an incorrect EventAbandoned
instead of an EventReleased
on an ADN in the following scenario:
T-Server generates an incorrect EventAbandoned
instead of EventReleased
on ADN3 with a call state of Forwarded
. (ER# 243487529)
Found In: 8.0.002.00 | Fixed In: 8.1.000.06 |
MX-ONE: T-Server generates an incorrect releasing party in the following scenario:
T-Server generates ReleasingParty
:1 Local
instead of 2 Remote
on ODN1. (ER# 243723721)
Found In: 8.0.002.00 | Fixed In: 8.1.000.06 |
MX-ONE: T-Server generates incorrect call state of Forwarded
instead of Ok
in the EventAbandoned
on the Emulated Routing Point in the following scenario:
(ER# 243487697)
Found In: 8.0.002.00 | Fixed In: 8.1.000.06 |
MX-ONE: The release call on ADN1 is not reported in the following scenario:
(ER# 243516834)
Found In: 8.0.002.00 | Fixed In: 8.1.000.06 |
PBX limitation. The MX-ONE PBX only supports one distribution method to Hunt Group members:
Sequential Searching - Linear Hunt Group, where a new call always goes to member Number1, if free. If Number1 is busy, then it goes to Number2, if Number1 and Number2 are busy, then it goes to Number3. (ER# 230165672)
Found In: | Fixed In: |
The following is a statement from Aastra (previously Ericsson):
In order to maintain the same call ID during a whole Call Deflect scenario, every involved device, including logical devices such as ACD groups, must be monitored. For example, if a PBX group is involved in the deflect scenario, the Call ID may change because PBX groups cannot be monitored.
Regarding Genesys:
In Genesys, this will cause problems in some Emulated Routing scenarios, as Hunt Groups cannot be monitored. Therefore, T-Server may not be able to maintain the Call ID and, as a result, attached data will be lost. (ER# 71793929)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). An unexpected extra transfer event from the Application Link/switch
causes an unexpected EventPartyChanged
on the transfer destination in the
following scenario:
(ER# 195627900)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The switch does not support treatments. (ER# 211241912)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The switch does not support call parking. Hold call functionality is used instead. (ER# 211241748)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The switch does not provide the relevant CTI events across the link to support the Intrude feature. (ER# 211241776)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Four-party conferences are not supported via CTI, but can be created manually via the handset. (ER# 211241969)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The lock/unlock status of ODN-only devices is not reported by the Application Link at monitor start. Therefore, T-Server reports the status of these devices as unknown. (ER# 211241884)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Consultation calls are always made from the ODN. If the primary call is on ODN, then the consultation call is made from the same ODN.
If the primary call is on an ADN, then the consultation call is made from the associated ODN. (ER# 211242017)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Reporting of conference events from the Application Link is incomplete when a conference party is unmonitored. When devices are released, they have different Call IDs. (ER# 211241411)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Application Link reports In/Out of Service events when VoIP agents log in manually. Only emulated agents are supported by T-Server with these devices. (ER# 211242119)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The destination for Forward On Busy and Forward On No Answer cannot be dynamically set via CTI. (ER# 211242054, 211242081)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). It is not possible to redirect or route a call to a DN which has Immediate Forwarding set. (ER# 211242156)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). When there is a call on an ADN and another call on the ODN,
the request TAlternate
has to be made from the active call leg, because
this is the only way to populate a Reference ID on the correct event. (ER# 211242203)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). To complete a conference, when the conference initiator is an ADN, it is necessary to alternate the primary and consultation call, so that the primary call becomes the active call (primary call on ADN), and then complete the conference. The one exception to this rule is when the primary call is Outbound. In this situation it is possible to complete the conference without alternating the call. However, the call that remains after conference completion is the consultation call that was on the ODN - the primary call on the ADN will be released. (ER# 211242285)
Found In: | Fixed In: |
PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The Application Link does not report conference calls when queried after the switch link disconnects and then reconnects. (ER# 211076244)
Found In: | Fixed In: |
Emulated Redirect from an ADN or an analog device is not supported. T-Server will attempt to use a native redirect with these devices. (ER# 60333842, 60333836)
Found In: 7.2 | Fixed In: |
A call's position in queue is cleared when
one party places the call on Hold
. In addition, an Initiate Transfer
also clears the position. See the Maintain Position in Queue section of the Deployment Guide for more
details. (ER# 45841606, 50549339)
Found In: 7.2 | Fixed In: |
An incompatibility exists between T-Server and URS when T-Server option call-retain-in-queue
is set to keep
and the Maintain Position in Queue feature
is enabled (see the Deployment Guide).
Any time an attempt is made to transfer a call back to the Routing Point,
the request fails. This prevents the keep
value being useful
for the following scenarios:
transfer-to-agent = false
(ER# 49581107)
Found In: 7.2 | Fixed In: |
The MD110 switch does not support a native RequestClearCall
. It
is only supported within T-Server when used in conjunction with the Maintain
Position in Queue feature to drop a call completely. (ER# 50549313)
Found In: 7.2 | Fixed In: |
Conference reporting is unreliable when used in conjunction with the Maintain Position in Queue feature. (ER# 45841618)
Found In: 7.2 | Fixed In: |
The Application Link does not report conference calls when queried after the switch link disconnects and then reconnects. (ER# 40142095)
Found In: 7.2 | Fixed In: |
OCS does not have separate Ready/NotReady
states for DNs on
a place. It has OffHook/OnHook
states for DNs only. After receiving EventAgentReady
OCS considers that the agent is ready to take an
outbound call. OCS does not know which DN is responsible for receiving an
outbound call. If the Position DN works with outbound calls, use only this DN to
change agent status (Ready/NotReady
). (ER# 72251)
Found In: 7.0.2 | Fixed In: |
PBX limitation (BC12 SP5, AL 4 SP 9). If an analog or CAS port is left in an off-hook state without a
call, after a switch timeout, the switch will issue a Connection Cleared
followed by OutOfService
. T-Server then issues EventOnHook
and EventDNOutOfService
. To get the device back in service, you must place the
analog or CAS port back on-hook. (ER# 89117)
Found In: | Fixed In: |
PBX limitation (BC12 SP5, AL 4 SP 10 HF 03). In the following scenario, the switch does not report devices as held, but reports them as established. Switch reporting is correct if only one of the devices is held.
(ER# 97473, 97474)
Found In: | Fixed In: |
PBX limitation (BC12 SP5, AL 4 SP 10 HF 06). In the following scenario, the switch does not report the dialing party on startup, and reports
the alerting party with call ID=1
.
TQueryInfoDNStatus
.
After the call is answered, the switch
assigns a new call ID=2 to the call, and stops reporting for call ID=1
. (ER# 99612, 99611)
Found In: | Fixed In: |
PBX limitation (BC12 SP5, AL 4 SP 10 HF 03). Because of switch reporting,
T-Server cannot report Call State Redirected
on Diverted
and Ringing
after a call arrives from a
Queue. (ER# 92193, 92194)
Found In: | Fixed In: |
PBX limitation (BC12 SP5, AL 4 SP 10 HF 03). In the following scenario, the switch does not report transfer events on ADN B.
(ER# 93262, 91361)
Found In: | Fixed In: |
PBX limitation (BC 11, AL 4 SP 8 HF 02). In the following scenario,
the switch only issues Connection Cleared
for the consultation
destination. No Connection Cleared
is issued for consultation call on
the CAS port. Eventually the switch places the CAS port in and out of
service to clear the device.
(ER# 83171, 83170)
Found In: | Fixed In: |
PBX limitation (BC 11, AL 4 SP 8). When T-Server performs login using
option use-makecall-login
set to true,
Application
Link indicates that the device is on hook. However the line where login is
requested remains in an off-hook state. It remains in this state until the
switch times out or another CTI request (for example, Ready
or NotReady
) is made. (ER# 77661, 75195)
Found In: | Fixed In: |
PBX limitation (BC 11, AL 4 SP 8 HF 02).The Genesys call model requires that if a call is forwarded
to a device, then the first event on that device should have call state Forwarded
. The Ericsson MD110 does not always report the call as Forwarded
, so T-Server cannot reliably report this.
In such cases T-Server reports forward state as OK
. (ER#
77143, 77144)
Found In: | Fixed In: |
PBX limitation (BC 11, AL 4). Genesys cannot guarantee the following at T-Server start/restart:
Ready/NotReady
status for ODNs/ADNs.
Ready/NotReady
status for ODNs only.
NotReady
state for ADNs when ODN Ready
and ADN NotReady
. All
other ODN/ADN combinations for Ready
can be synchronized. In an ODN-only
place, T-Server cannot synchronize if the ODN is logged in when T-Server is
started. You must manually logout the ODN in order to be able to use CTI
functionality.(ER# 77779, 77780)
Found In: | Fixed In: |
PBX limitation (BC 11, AL 4, SP 7). Application Link does not report conference completion correctly when all parties are internal and the conference controller is an unmonitored device. (ER# 66300, 77666)
Found In: | Fixed In: |
OCS two-step transfer causes problems when a call is established on
emulated Routing Points. When the call is routed with either supervised
routing or RouteTypeReject
, upon the call being established, OCS tries to complete the transfer.
(ER# 14896377)
Found In: | 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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.
The Red Hat Enterprise Linux 3.0 operating system is no longer supported.
Discontinued As Of: 8.1.000.05 |
The Solaris 8 operating system is no longer supported.
Discontinued As Of: 8.1.000.05 |
The Tru64 UNIX operating system is no longer supported.
Discontinued As Of: 8.1.000.05 |
The AIX 5.1 and 5.2 operating systems are no longer supported.
Discontinued As Of: 8.1.000.05 |
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 Customer Care website. The following documentation also contains information about this software.
The Framework 8.1 T-Server for Aastra MXONE CSTA I Deployment Guide contains detailed reference information for the Genesys Framework 8.1 T-Server for Aastra MXONE CSTA I including configuration options and specific functionality.
The Framework 8.1 Deployment Guide helps you configure, install, start, and stop Framework components.
The Platform SDK 8.x .NET (or Java) API Reference and the Genesys Events and Models Reference Manual contain the T-Library API, information on TEvents, and an extensive collection of call models.
The Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Customer Care for additional information.
The Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Customer Care for additional information.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. 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.