Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
7.6.008.04 [10/16/09] – Hot Fix | X | |||||
7.6.008.03 [10/02/09] – Hot Fix | X | |||||
7.6.008.02 [10/31/08] – Hot Fix | X | |||||
7.6.008.01 [03/14/08] – General | X | X | X | X | X | X |
7.6.007.03 [02/28/08] – Hot Fix | X | |||||
7.6.007.02 [01/30/08] – 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.genesyslab.com for more details.
This release note applies to all 7.6 releases of T-Server for Ericsson MD110.
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 7.6.008.14. 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:
The Advanced Disconnect Detection Protocol (ADDP) now works correctly between the primary and backup T-Servers operating in Hot Standby
mode. (ER# 237430723)
T-Server now correctly handles incorrect CallBack reporting from the PBX (call back requestor and call back destination are reported in reverse order). (ER# 237474560)
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 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.
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 now correctly synchronizes the native agent state with the switch when an agent, in the not-ready
state, requests a ready
state during (unsynchronized) emulated after-call work (ACW). (ER# 236545714)
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 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.
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:
Processing of events ForwardSet/ForwardCancel
for
non-ACD ODNs (extensions with switch-specific type 9
) has
been changed to ensure that T-Server correctly generates EventAgentReady/EventAgentNotReady
for those devices. Previously, when issuing
manual “not-ready” from a non-ACD ODN, T-Server did not generate EventAgentReady/EventAgentNotReady
events. (ER# 207501415)
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 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.
This section describes new features that were introduced in this release:
This release includes the following corrections and modifications:
T-Server has been built with the latest libraries. (ER# 178717061)
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 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 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 has been corrected to ensure that when an ODN diverts to itself using a switch-defined destination,
T-Server will interpret this messaging as DNDOn
when emulated agents are logged in.
If no emulated agents are logged in, T-Server will not report DNDOn.
(ER# 176718264).
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 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 Ericsson MD110.
clid-withheld-name
has been introduced.clid-withheld-name
PRIVATE
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
none
none, ext, rsn
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
.kpl-loss-rate
10, 100
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.wrap-up-theshhold
0
queue-return-dly
1000
0-5000
This release includes the following corrections and modifications that were made between the most recent 7.5 release and the initial 7.6 release:
T-Server processing of Request Not Ready (WorkMode=Unknown)
during emulated ACW has been amended to ensure correct propagation of Reference ID. (ER# 149455291)
T-Server has been modified to deal with the unexpected change of Call ID where two Established
events are generated by the switch. Now, T-Server checks for a second Established
event in this scenario and does not create a new call. Previously, this was leaving the DN stuck on hold. (ER# 161322165)
T-Server has been modified to enable emulated agent devices to be set into Not Available
mode when manual Divert is set on the phone set.
Manual Divert can be cancelled only manually. (ER# 153599063)
A problem with synchronization of ready/notready
states between T-Server and the PBX after a call is released has been corrected in T-Server. (ER# 162519589)
This section provides the latest information on known issues and recommendations associated with this product.
In a scenarios where the switch may stop monitoring some of the DNs (only part of the monitored DNs receives a StopMonitor
from the switch), T-Server may change a set of DNs to the OutOfService
mode, and doesen't bring them back to service.
(ER# 243283111)
Found In: 7.6.007.02 | Fixed In: |
T-Server may reuse the TMakeCall
request properies for the next call in the following scenario:
EventOffHook
), but the dialled number is not in service, and T-Server never generates Eventnetworkreached
and EventDialing
events.
EventOnHook
).
(ER# 242393254)
Found In: 7.6.007.02 | Fixed In: |
MX-ONE: The switch does not report the Cause CallForwardNoAnswer
in the following scenario:
The redistr-dly
option is set to 2000
.
The switch does not report the Cause CallForwardNoAnswer
message on the first agent when the ACD Queue redistributes the call to another agent. This causes T-Server to generates the new call to another agent with a new ConnID
.
(ER# 232394572)
Found In: MX-ONE 3.2 SP2 | Fixed In: MX-ONE 4.0 |
MX-ONE: 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: MX-ONE 3.2 SP2 | Fixed In: |
MX-ONE: 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: MX-ONE 4.0, AL4 SP21 | Fixed In: |
MX-ONE: The PBX does not report a call forwarded set on a SIP device in the following scenario:
RequestCallForwardSet
is made from SIP Device1 to SIP Device2.
(ER# 234796310)
Found In: MX-ONE 3.2 SP2 | Fixed In: |
MX-ONE: A call remains stuck on a consultation controller after a blind transfer and a transfer to another DN. See the following scenario for an example:
RequestInitiateTransfer
to SIP DN3.
RequestCompleteTransfer
.
RequestSingleStepTransfer
(or other transfer types where the PBX completes the call before the destination answers) to SIP DN4.
After the final call transfer, the call still remains on SIP DN3
(ER# 234796335)
Found In: MX-ONE 3.2 SP2 | Fixed In: MX-ONE 4.0 |
MX-ONE: 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: MX-ONE 3.2 SP2 | Fixed In: |
MX-ONE: In the following scenario, parties are dropped when a VoIP conference controller attempts to reconnect a failed blind transfer:
The agent is the VoIP DN conference controller.
(ER# 211241465)
Found In: MX-ONE 3.1 SP4 | Fixed In: |
MX-ONE: An unexpected transfer event occurs in the following scenario:
The application link issues two transfer complete events. The first event has the correct attributes, but the second event has the transferring device as the external party which is incorrect.
(ER# 210098061)
Found In: MX-ONE 3.2 SP2 | Fixed In: MX-ONE 4.0 |
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: 7.6.008.04 | Fixed In: |
MX-ONE: T-Server does not distribute an EventAgentReady
after emulated agent login (AutoIn
) when the sync-emu-agent
option is set to true
.
(ER# 239564897)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: The CallRetainInQueue = keep or divert
extension on the VTO Port is missing, and the Inbound
call type on the VTO Port is incorrect in the following scenario:
The CAS extension is equal to the VTO Port
CallRetainInQueue = keep or divert
.
(ER# 238419540)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: T-Server generates an incorrect EventReleased
on an agent in the following scenario:
T-Server incorrectly generates an EventReleased
instead of an EventAbandoned
on the agent.
(ER# 239046461)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: The EventError
with the message Call has disconnected
is generated after a multiline DN complete conference is executed in the following scenario:
An EventError
with the message Call has disconnected
is generated on ODN2, and a CSTA error: operationalErrors : invalidCSTACallIdentifier
is generated when the agent on ADN2 does a RequestReleaseCall
.
(ER# 243487527)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: T-Server generates an incorrect EventAbandoned
instead of EventReleased
after the NAS timeout expires in the following scenario:
The agent-no-answer-timeout
option is set to 4
.
The agent-no-answer-overflow
option is set to ODN3
.
agent-no-answer-timeout
option expires.
The call should now be released on ADN2 and ringing on ODN3, but T-Server generates an incorrect EventAbandoned
instead of EventReleased
on ADN2.
(ER# 243517019)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: T-Server does not generate an EventPartyDeleted
after an external DN releases from an outbound conference call in the following scenario:
T-Server does not generate an EventPartyDeleted
on ODN1 and on ODN2.
(ER# 243680411)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: T-Server uses the incorrect connection ID for EventPartyChanged
after a complete call transfer in the following scenario:
RequestInitiateTransfer
to a native Routing Point.
RequestCompleteTransfer
for the call.
T-Server incorrectly uses the EventEstablished
connection ID for the EventPartyChanged
connection ID for ODN3. T-Server should be using the same connection ID as the consultation call.
(ER# 243680548)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ON: When setting an Absence code on an IP Phone (with RequestDNDOn
), the request times out because the reporting from the switch is missing.
(ER# 242851462)
Found In: MX-ONE 4.0, AL4 SP21 | Fixed In: |
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: MX-ONE | Fixed In: |
MX-ONE: T-Server cannot complete a conference call on an ADN in the following scenario:
After ADN 1 completes the conference, the CSTA error: systemResourceErrors : generic from the PBX
error is generated. Also, a complete conference on ODN 2 generates the Call has disconnected
error on ODN 2.
(ER# 238129011)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: No EventPartyAdded
is generated after an ODN completes a conference call in the following scenario:
After ODN 2 completes the conference call, no EventPartyAdded
is generated.
(ER# 238129020)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: An EventError
Call has disconnected
is generated on an ADN after the ADN completes a transfer in the following scenario:
After ADN 1 transfers the call, T-Server generates EventError
Call has disconnected
.
(ER# 238129031)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: T-Server does not generate EventPartyChanged
after an ODN (multiline DN) completes a transfer in the following scenario. This is a PBX transfer issue.
T-Server does not generate EventPartyChanged
on ODN 1, and EventError
Call has disconnected
is generated for ODN 2.
(ER# 238129045)
Found In: 7.6.008.04 | Fixed In: |
In the following scenario, T-Server does not generate EventPartyAdded
since there is no information from the PBX to indicate that all parties are in the conference call after the complete conference.
RequestInitiateConference
from ADN 1 to ODN 3.
RequestAlternateCall
on ODN 2.
RequestCompleteConference
on ADN 1.
(ER# 238129067)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: No EventError
Answer timer expired
is generated after a supervised route switchover, and the timeout expires, in the following scenario:
The supervised-route-timeout
option is set to 5
.
(ER# 238129120)
Found In: 7.6.008.04 | Fixed In: 8.0 |
MX-ONE: There is an incorrect EventHeld
message after the primary T-Server fails in the following scenario:
hot standby
redundancy type (backup T-Server starts with main and consultation established calls on ODN).
After ODN answers, there is an EventHeld
on ODN.
(ER# 238208277)
Found In: 7.6.008.04 | 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 therefore attached data will be lost. (ER# 71793929)
Found In: MX-ONE, MD110 | Fixed In: |
MX-ONE: 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: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: The switch does not support treatments. (ER# 211241912)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: The switch does not support call parking. Hold call functionality is used instead. (ER# 211241748)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: The switch does not provide the relevant CTI events across the link to support the Intrude feature. (ER# 211241776)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: Four-party conferences are not supported via CTI, but can be created manually via the handset. (ER# 211241969)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: The lock/unlock status of ODN-only devicesis not reported by the Application Link link at monitor start. Therefore T-Server reports the status of these devices as unknown. (ER# 211241884)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: 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: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: 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: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: 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: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: The destination for Forward On Busy and Forward On No Answer cannot be dynamically set via CTI. (ER# 211242054, 211242081)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: It is not possible to redirect or route a call to a DN which has Immediate Forwarding set. (ER# 211242156)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: When there is 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: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: To complete a conference, when the conference initiator is an ADN, it is necessary to alternate the primary and consult 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: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
MX-ONE: The Application Link does not report conference calls when queried after the switch link disconnects and then reconnects. (ER# 211076244)
Found In: MX-ONE 3.1 SP3, AL4 SP20 | Fixed In: |
The PBX reports
ConnectionCleared
instead of Diverted
after a Divert has been executed from a
Hunt Group member (used in Genesys emulated routing). T-Server can handle this
scenario for internal routing, but for routing to external destinations, no
additional events are available to correct the PBX reporting. (ER#
168288268)
Found In: 7.6 | Fixed In: AL4 SP20 HF03 |
The switch releases the second party in a call after the first party performs single-step transfer after trunk optimization over an ISDN trunk. AN example scenario is:
(ER# 38361689)
Found In: 7.2 | Fixed In: AL4 SP20 HF03 |
Conference reporting can be unreliable where all three parties are internal, the conference controller is an ADN and the call is handled by different lims on the switch. (ER# 170794578, 171454089)
Found In: AL 4 SP 18, HF 05 | Fixed In: AL4 SP19, BC13 SP04 |
The switch/link issues a Connection Cleared
event instead of a Deflect
after deflecting from a Hunt Group to a CTI group. (ER# 105239037)
Found In: Unspecified | Fixed In: AL4 SP19, BC13 SP04 |
The switch reports an unexpected error after a two-step transfer when
one party is external on a QSIG trunk. The error is reported on
transfer completion and, in turn, T-Server does not issue EventPartyChanged
.
(ER# 105239074)
Found In: BC13 SP1, AL 4, SP 14 | Fixed In: AL4 SP19, BC13 SP04 |
In the following scenario:
T-Server gets some call information from the Application Link, but not
enough to properly synchronize. When transfer is completed, no PartyChanged
events are propagated because T-Server
does not know that two calls are linked, and only one EventReleased
is propagated. (ER# 94492, 94491)
Found In: 7.1 | Fixed In: AL4 SP19, BC13 SP04 |
In transfer scenarios from an unmonitored DN, withheld CLIDs are revealed after transfer completion. Physically the phone still shows the party as anonymous, but the Application Link exposes all CLIDs after calls have passed via an unmonitored DN. (ER# 170794592)
Found In: 7.6 | Fixed In: 7.6.008.02 |
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: Unspecified | Fixed In: |
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: BC12 SP5, AL 4 SP 9 | 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: |
In the following scenario:
Connection Cleared
events for the analog or CAS devices
are reported.
Connection Cleared
is generated but it has incorrect
reporting, so it cannot be associated with the external party. These problems were observed when using trunks which did not provide the A-number. (ER# 4292880)
Found In: BC12, SP7 | Fixed In: MX-ONE 4.0 SP2, Al4 SP21 |
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: BC12 SP5, AL 4 SP 10 HF 03 | Fixed In: |
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: BC12 SP5, AL 4 SP,10 HF 06 | Fixed In: |
Because of switch reporting,
T-Server cannot report CallState Redirected
on Diverted
and Ringing
after a call arrives from a
Queue. (ER# 92193, 92194)
Found In: BC12 SP5, AL 4 SP 10 HF 03 | Fixed In: |
In the following scenario, the switch does not report transfer events on ADN B.
(ER# 93262, 91361)
Found In: BC12 SP5, AL 4 SP 10 HF 03 | 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: |
In the following scenario,
the switch only issues (ER# 83171, 83170)
Connection Cleared
for the consult
destination. No Connection Cleared
is issued for consult call on
the CAS port. Eventually the switch places the CAS port in and out of
service to clear the device.
Found
In: BC 11, AL 4 SP 8 HF
02
Fixed In:
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: BC 11, AL 4 SP 8 | Fixed In: |
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: BC 11, AL 4 SP 8 HF02 | Fixed In: |
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 synchronised. In an ODN-only
place, T-Server cannot synchronise 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: BC 11, AL 4 | Fixed In: |
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: BC 11, AL 4, SP 7 | 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.
The Solaris 2.6 operating system is no longer supported.
Discontinued As Of: 7.6 |
Information in this section is included for international customers. There are no known restrictions specific to international customers.
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.
The Framework 7.6 T-Server for Ericsson MD110
Deployment Guide provides detailed
reference information for the Genesys Framework T-Server for the Ericsson MD110 switch including configuration options, known limitations, and switch
functionality.