Release Note

Top of Page

Known Issues and Recommendations

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)

T-Server may reuse the TMakeCall request properies for the next call in the following scenario:

1. An agent makes an outbound call (EventOffHook), but the dialled number is not in service, and T-Server never generates Eventnetworkreached and EventDialing events.
2. The agent releases call (EventOnHook).
3. The agent makes a new outbound call using the handset (manual call).
4. The new call contains the attached user data from the first call.

(ER# 242393254)

MX-ONE: The switch does not report the Cause CallForwardNoAnswer in the following scenario:

The redistr-dly option is set to 2000.

1. A Predictive Call is made to ACD Queue1 on the MX-ONE switch using an ISDN Trunk to an MD110 switch.
2. The call is answered on Destination ODN1 on the MD110 switch.
3. The call is delivered to an agent on ADN1.
4. The call is not answered by the agent on ADN1.
5. The call is redistributed to the ACD Queue and is delivered the another agent on ADN2.

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)

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.

1. A call is made from an agent on ODN1 on an MX-ONE switch, to ODN2 on a MD110 switch.
2. A RequestInitiateTransfer is made from the agent on ODN2 to a native Routing Point (divert from the Queue) through ISCC.
3. A RequestCompleteTransfer is performed by the agent on ODN2.
4. The call is routed by the native Routing Point to the agent on DN1.

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)

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)

MX-ONE: The PBX does not report a call forwarded set on a SIP device in the following scenario:

1. A RequestCallForwardSet is made from SIP Device1 to SIP Device2.
2. The PBX does not report that call forward is set on the SIP Device.
3. SIP Device3 makes call to SIP Device1.
4. The call is forwarded to SIP Device2.

(ER# 234796310)

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:

1. An agent on SIP DN1 makes a call to an agent on SIP DN2.
2. The agent on SIP DN2 answers the call.
3. The agent on SIP DN2 performs a RequestInitiateTransfer to SIP DN3.
4. The agent on SIP DN2 performs a RequestCompleteTransfer.
5. The agent on SIP DN3 answers the call.
6. The agent on SIP DN3 performs a 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)

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.

1. An agent on SIP DN1 calls the Hunt Group (Emulated Routing Point).
2. The Hunt Group (Emulated Routing Point) performs a supervised route of the call to ODN1.

The CSTA error: systemResourceErrors : generic is received.

(ER# 234796352)

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.

1. A blind transfer of a conference call is made from a VoIP agent to an internal DN.
2. The VoIP conference controller does a reconnect on the call.

(ER# 211241465)

MX-ONE: An unexpected transfer event occurs in the following scenario:

1. An outbound call is made from an agent on ODN1 on MX-ONE to an agent ODN, on MD110 (ISDN).
2. The agent on ODN answers the call.
3. The agent on ODN1 initiates a consultation call to a Hunt Group with an available member.
4. The call arrives at the Hunt Group member.
5. The agent on ODN1 completes the call transfer.

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)

MX-ONE: T-Server generates an incorrect EventAbandoned instead of an EventReleased on an ADN in the following scenario:

1. An agent on ODN1 makes an outbound call to external DN1.
2. External DN1 answers the call.
3. The agent on ODN1 does an initiate transfer of the call to ACD Queue2 (ADN2)
4. The agent on ODN1 does a complete transfer of the call.
5. The agent on ADN2 answers the call
6. The agent on ADN2 does a mute transfer to emulated Routing Point1
7. Emulated Routing Point1 routes the call to emulated Routing Point2
8. Emulated Routing Point2 routes the call to ACD Queue3 (ADN3)
9. External DN1 releases the call

T-Server generates an incorrect EventAbandoned instead of EventReleased on ADN3 with a call state of Forwarded.

(ER# 243487529)

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)

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

1. An internal call is made from the agent on DN1 to the agent on DN2.
2. The agent on DN2 routes the call with the extension CallRetainInQueue = keep or divert.
3. The CAS extension answers the call.
4. The internal agent on DN1 releases the call.

(ER# 238419540)

MX-ONE: T-Server generates an incorrect EventReleased on an agent in the following scenario:

1. An outbound call is made from an agent on DN1 to an external agent on DN2.
2. The external agent on DN2 answers the call.
3. The agent on DN1 performs a blind transfer to the native Routing Point.
4. The native Routing Point routes the call to the ACD Queue.
5. The external agent on DN2 releases the call before another agent answers the call.

T-Server incorrectly generates an EventReleased instead of an EventAbandoned on the agent.

(ER# 239046461)

MX-ONE: The EventError with the message Call has disconnected is generated after a multiline DN complete conference is executed in the following scenario:

1. The agen on ODN1 makes a calls the the ACD Queue (ADN2 with ODN2).
2. The call arrives on the agent on ADN2.
3. The agent on ADN2 answers the call.
4. The agent on ADN2 initiates a conference call to ODN3 (the call has been initiated from ODN2).
5. The agent on ODN2 completes the conference call.

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)

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.

1. The agent on ODN1 makes a calls to ACD Queue (ADN2 with ODN2).
2. The call arrives on the agent on ADN2.
3. The agent on ADN2 does not answer the call.
4. The value set for the 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)

MX-ONE: T-Server does not generate an EventPartyDeleted after an external DN releases from an outbound conference call in the following scenario:

1. The agent on ODN1 makes a call to to an agent on ODN2.
2. The agent in ODN2 answers the call.
3. The agent on ODN2 initiate a conference call to an external DN.
4. The external DN answers the call.
5. The agent on ODN2 completes the conference call.
6. The external DN releases from the call.

T-Server does not generate an EventPartyDeleted on ODN1 and on ODN2.

(ER# 243680411)

MX-ONE: T-Server uses the incorrect connection ID for EventPartyChanged after a complete call transfer in the following scenario:

1. The agent on ODN1 makes an outbound call to an agent on ODN2.
2. The agent on ODN2 answers the call.
3. The agent on ODN2 makes an outbound RequestInitiateTransfer to a native Routing Point.
4. The native Routing Point routes the outbound call back to ODN3.
5. The agent on ODN3 answers the call.
6. The agent on ODN2 performs a 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)

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)

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)

MX-ONE: T-Server cannot complete a conference call on an ADN in the following scenario:

1. Make a call from ODN 1 to ADN 1.
2. Answer call on ADN 1.
3. Initiate a conference call from ADN 1 to ODN 2.
4. Answer the call on ODN2.
5. Complete the conference call on ADN 1.

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)

MX-ONE: No EventPartyAdded is generated after an ODN completes a conference call in the following scenario:

1. Make an inbound call from ODN 1 to an ACD queue.
2. Answer the call on ADN 1.
3. Initiate a conference call from ADN 1 to ODN 2.
4. Answer the call on ODN 2.
5. Complete the conference call on ODN 2.

After ODN 2 completes the conference call, no EventPartyAdded is generated.

(ER# 238129020)

MX-ONE: An EventError Call has disconnected is generated on an ADN after the ADN completes a transfer in the following scenario:

1. Make an inbound call from DN 1 to the ACD queue.
2. Answer the call on ADN 1.
3. Transfer the call from ADN 1 to a Native Routing Point.
4. The Native Routing Point routes the call to external DN 1.
5. Answer the call on external DN 1.
6. Complete the transfer on ADN 1.

After ADN 1 transfers the call, T-Server generates EventError Call has disconnected.

(ER# 238129031)

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.

1. Make a call from ODN 1 to the ACD queue.
2. Answer the call on ADN 1 (ODN 2).
3. Initiate a transfer from ADN 1 to external DN 1.
4. Answer the call on external DN 1.
5. Complete the transfer on ODN 2.

T-Server does not generate EventPartyChanged on ODN 1, and EventError Call has disconnected is generated for ODN 2.

(ER# 238129045)

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.

1. Make an inbound call from ODN 1 to the ACD Queue.
2. Answer the call on ADN 1 (ODN 2).
3. Make a RequestInitiateConference from ADN 1 to ODN 3.
4. Answer the call on ODN 3.
5. Make a RequestAlternateCall on ODN 2.
6. Make a RequestCompleteConference on ADN 1.

(ER# 238129067)

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.

1. DN 1 calls Emulated Routing Point 1.
2. Emulated Routing Point 1 routes to DN 2.
3. A switchover is performed.

(ER# 238129120)

MX-ONE: There is an incorrect EventHeld message after the primary T-Server fails in the following scenario:

1. Start a primary and backup T-Servers with the hot standby redundancy type (backup T-Server starts with main and consultation established calls on ODN).
2. Complete the transfer on ODN.
3. Inbound call to Emulated Routing Point.
4. Primary T-Server fails.
5. Emulated Routing Point performs a supervised route to ODN.
6. Answer the call on ODN.

After ODN answers, there is an EventHeld on ODN.

(ER# 238208277)

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)

MX-ONE: An unexpected extra transfer event from the Application Link/switch causes an unexpected EventPartyChanged on the transfer destination in the following scenario:

1. An outbound call from MX-ONE is made to an external device which answers.
2. The outbound originator makes an emulated single-step transfer to an internal queue.
3. The call is delivered to an ADN.

(ER# 195627900)

MX-ONE: The switch does not support treatments. (ER# 211241912)

MX-ONE: The switch does not support call parking. Hold call functionality is used instead. (ER# 211241748)

MX-ONE: The switch does not provide the relevant CTI events across the link to support the Intrude feature. (ER# 211241776)

MX-ONE: Four-party conferences are not supported via CTI, but can be created manually via the handset. (ER# 211241969)

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)

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)

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)

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)

MX-ONE: The destination for Forward On Busy and Forward On No Answer cannot be dynamically set via CTI. (ER# 211242054, 211242081)

MX-ONE: It is not possible to redirect or route a call to a DN which has Immediate Forwarding set. (ER# 211242156)

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)

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)

MX-ONE: The Application Link does not report conference calls when queried after the switch link disconnects and then reconnects. (ER# 211076244)

1. Create a call on ADN and initiate a transfer to get a related consult call on ODN
2. Restart T-Server.

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)