Some errors from Application Link trace logs

[cuneyt2919]

Hi again, Regarding CTI problems, some universal failure errors are retrieved on Application link Does anybody here know what they mean?

****************************************
InvokeId: 5476
value SnapshotDeviceArgument ::= snapshotObject : dialingNumber : "69856"
<Result>
Time: Wed Oct 13 14:35:37.741 2004

InvokeId: 5476
value UniversalFailure ::= subscribedResourceAvailabilityErrors : 4
<Success>
Wed Oct 13 14:35:37.741 2004
- Returning after sending request (76) to commQueue in hdlrq_wq.cpp
<Switch Data>
Wed Oct 13 14:35:37.741 2004
4.0.9.901 Switch data on IP Address 10.21.16.3
READ: a0 00 69 e5 04 ff ff ff 03 01 00 00 ff ff ff 07 11 13 50 f9
ff ff ff ff ff ff 5c 01 11 04 45 44 ff ff ff ff ff ff ff ff
00 ff ff ff ff ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff

**************************************************************

Other error...

InvokeId: 5466
value DivertCallArgument ::= divertInfo : deflect :
{
callToBeDiverted
{
call 284293,
device staticID : dialingNumber : "67267"
},
newDestination deviceIdentifier : deviceIdentifier : dialingNumber : "5410"
}
<Success>
Wed Oct 13 14:35:30.163 2004
- Sending request (divertCall) to ML : 1
<Success>
Wed Oct 13 14:35:30.163 2004
- Commmain Reading request (divertCall)
<Success>
Wed Oct 13 14:35:30.163 2004
- Sending Event (negativeResp) for device (67267) : 1
<Success>
Wed Oct 13 14:35:30.163 2004
- Returning after sending request (15) to commQueue in hdlrq_wq.cpp
<Result>
Time: Wed Oct 13 14:35:30.163 2004

InvokeId: 5466
value UniversalFailure ::= operationalErrors : 11
<Success>

***********************************************
other error
InvokeId: 4925
value SetFeatureArgument ::=
{
device dialingNumber : "67471",
feature aRequestedAgentState : loggedOut :
{
agentID '35333134'H
}
}
<Success>
Wed Oct 13 14:31:07.661 2004
- Sending request (agentLogout) to ML : 1
<Success>
Wed Oct 13 14:31:07.661 2004
- Commmain Reading request (agentLogout)
<Success>
Wed Oct 13 14:31:07.661 2004
- Sending Event (negativeResp) for device (67471) : 1
<Success>
Wed Oct 13 14:31:07.661 2004
- Returning after sending request (29) to commQueue in hdlrq_wq.cpp
<Result>
Time: Wed Oct 13 14:31:07.661 2004

InvokeId: 4925
value UniversalFailure ::= operationalErrors : 1
<Success>
Wed Oct 13 14:31:07.661 2004
- Waiting for Request
<Request>
Time: Wed Oct 13 14:31:07.771 2004

 

[fidde]

Well it's hard to say it would help if you added the read/write data from MD.

For the fisrt one I wold say that there is an outstanding request for that extension, IE the same or another client has send a command. MD can only handle one.

The InvokeId: 5466, there I'm pretty sure that the caller has hangup it indicates the wrong callid.

 

[FCVV]

Hi,

MD110 BC10, APPLLINK 4, SP 11.

It Seems that we are having the same problem, please see:

Tue Jun 21 11:06:40.000 2005
4.0.11.1 Switch data on IP Address 172.16.1.60
WRITE: b3
<Request>
Time: Tue Jun 21 11:06:45.078 2005
InvokeId: 2278
value DivertCallArgument ::= divertInfo : deflect :
{
callToBeDiverted
{
call 15738,
device staticID : dialingNumber : "7062"
},
newDestination deviceIdentifier : deviceIdentifier : dialingNumber : "7401"
}
<Success>
Tue Jun 21 11:06:45.078 2005
- Sending request (divertCall) to ML : 1
<Success>
Tue Jun 21 11:06:45.078 2005
- Commmain Reading request (divertCall)
<Success>
Tue Jun 21 11:06:45.078 2005
- Sending Event (negativeResp) for device (7062) : 1
<Success>
Tue Jun 21 11:06:45.078 2005
- Returning after sending request (15) to commQueue in hdlrq_wq.cpp
<Success>
Tue Jun 21 11:06:45.078 2005
- Waiting for Request
<Result>
Time: Tue Jun 21 11:06:45.078 2005
InvokeId: 2278
value UniversalFailure ::= operationalErrors : 11
<Switch Data>
Tue Jun 21 11:06:46.062 2005
4.0.11.1 Switch data on IP Address 172.16.1.60
READ: a0 00 0f b5 01 01 a3 b8 12 ff 0f 05 ff ff ff 0a 36 99 59 58
54 ff ff ff ff ff 05 02 14 04 47 10 ff ff ff ff ff ff ff ff
00 ff ff ff ff ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
ff ff
<Success>


CROSS REFERENCE ID: 000f
CROSS REFERENCE ID CONTROL: b5
LIM: 1
QUEUE REFERENCE ID: 01a3
QUEUE REFERENCE ID CONTROL: b8
STATE: QUEUED
SUB STATE: SUBSEQUENT TIMES.
DIVERSION INFO: NOT DIVERTED
KEY NUMBER: ADN
MESSAGE DIV. ABSENT CODE: NOT APPLICABLE
MESSAGE DIVERSION TIME OR DATE: NO INFORMATION TO DISPLAY
CONNECTED/CALLING NUMBER: 6399958545
TRUNK ID, ROUTE NUMBER: 5
TRUNK ID, LIM NUMBER: 2
TRUNK ID, TRUNK NUMBER: 20
DIALLED NUMBER: 7401
DIVERTED NUMBER: NO DIVERSION NUMBER
CID NUMBER: NO CID NUMBER
KEY NUMBER FOR FREE ON SECOND ACCESS:NO INFORMATION.
FREE ON SECOND ACCESS INDICATION:NOT USED.
DIVERSION WITH HIGEST PRIORITY, FOLLOW-ME, ECF, DIRECT OR ICS DIVERSION:NOT USED.


== Application link data details of odd csta call scenario (and another one): == "Time: Tue Jun 21 14:05:00.656 2005"
== - call id 16186 detected over queue 7401
== "Time: Tue Jun 21 14:05:01.015 2005"
== - Deflect call from queued 7401 to extension device 7061.
== - Deflect call positive response
== - csta Diverted event
== - MISSING csta Delivered event over extension 7061 (crid 214).
== "Time: Tue Jun 21 14:05:21.781 2005"
== - Deflect call extension device 7061 to queued 7401
== - Deflect call negative response by error 11 - INVALID_CSTA_CALL_IDENTIFIER. It seens that the call has been cleared but no event was issued over the csta link.
== "Time: Tue Jun 21 14:50:11.312 2005"
== - new csta call id 16377 over queue 7401
== "Time: Tue Jun 21 14:50:11.546 2005"
== - another attempt to deflect the call from queue 7401 to extension 7061 and it succeeds.
== - Positive response
== - csta Diverted event
== - csta Delivered event over the target device - extension 7061
== "Time: Tue Jun 21 14:50:32.343 2005"
== - Deflect call from extension device 7061 to queued 7401
== - Positive response
== - csta Diverted event
== - MISSING csta delivered and queued event over the queue device - 7401.
== - No other csta event over call id 16377.
==

It seems that the call has been cleared between the moments (17:05:55 21/06/2005) and (17:06:16 21/06/2005), but no activity is reported in csta link - missing csta connection cleared event. ==

== It seems that the device 7061 has temporarly lost its monitor between the moments (17:05:55 21/06/2005) and (17:06:16 21/06/2005) and no activity is reported over the device. ==

Is This a APPL LINK Bug ?