05-12-2006 09:28 PM - edited 03-18-2019 05:54 PM
Found previous bug, CSCeb66120, on this condition but it saids fixed in 7.0x TSP. No other errors/warnings/etc in log except for these at the times. CCM is 4.0(2a)SR2b.
Event Type: Error
Event Source: CiscoUnity_Miu
Event Category: Error
Event ID: 549
Date: 5/12/2006
Time: 11:01:44 AM
User: N/A
Computer: UNITY
Description:
Cisco Unity's telephony component has encountered a serious error.
EXPLANATION:
No reponse was received on port 3 while waiting for an incoming call to be answered. This is a serious failure, and most likely parties involved in the call will be disconnected. In some cases, further calls on this port will not be handled correctly.
TECHNICAL DETAILS:
Thread 0x0000179C had a failure on port 3 in method CAvMiuLine::Answer()
DESCRIPTION: Timed-out waiting for LINECALLSTATE_CONNECTED after lineAnswer.
DETAILS:
HCALL: 0x00010688
CallState: LINECALLSTATE_OFFERING.
CALLINFO:
CallerID: x
CalledID: 1500
RedirectingID: 1500
Origin: Internal
Reason: FwdUncond
Trunk: 0.
CALL SEQUENCE:
[11:00:58:453 - 0x0000178C] Drop() - S_OK
[11:01:14:421 - 0x0000159C] LINE_APPNEWCALL(0x00010688)
[11:01:14:421 - 0x0000159C] SetEvent(NewCall)
[11:01:14:421 - 0x0000159C] SetEvent(CallInfoArrived)
[11:01:14:593 - 0x0000179C] Answer() entered
[11:01:14:593 - 0x0000179C] lineAnswer(0x00010688) - 0x00010677
[11:01:14:593 - 0x0000159C] LINE_REPLY(0x00010677 | 0x00000000)
[11:01:14:640 - 0x0000159C] SetEvent(CallInfoArrived)
[11:01:44:593 - 0x0000179C] WaitFor(0x00010677 | CONNECTED) - Timeout.
Then a couple minutes later, a 559 error
Event Type: Error
Event Source: CiscoUnity_Miu
Event Category: Error
Event ID: 559
Date: 5/12/2006
Time: 11:26:34 AM
User: N/A
Computer: UNITY
Description:
Cisco Unity's telephony component has encountered a serious error.
EXPLANATION:
A serious failure has occurred on port 3 while dropping a call. In some cases, further calls on this port will not be handled correctly.
TECHNICAL DETAILS:
Thread 0x0000177C had a failure on port 3 in method CAvMiuLine::Drop()
DESCRIPTION: Drop() called lineDrop() 0 times with result E_MIU_TIMEOUT..
DETAILS:
HCALL: 0x0001059A
CallState: LINECALLSTATE_OFFERING.
CALLINFO:
CallerID: x
CalledID: 1300
RedirectingID: 1300
Origin: Internal
Reason: FwdNoAnswer
Trunk: 0.
CALL SEQUENCE:
[11:02:14:609 - 0x0000179C] Drop() - E_MIU_TIMEOUT
[11:25:34:625 - 0x0000159C] LINE_APPNEWCALL(0x0001059A)
[11:25:34:625 - 0x0000159C] SetEvent(NewCall)
[11:25:34:625 - 0x0000159C] SetEvent(CallInfoArrived)
[11:25:34:843 - 0x0000177C] Answer() entered
[11:25:34:843 - 0x0000177C] lineAnswer(0x0001059A) - 0x00010293
[11:25:34:843 - 0x0000159C] LINE_REPLY(0x00010293 | 0x00000000)
[11:26:04:843 - 0x0000177C] WaitFor(0x00010293 | CONNECTED) - Timeout
[11:26:04:843 - 0x0000177C] Answer() - E_MIU_TIMEOUT
[11:26:04:843 - 0x0000177C] Drop() entered
[11:26:04:843 - 0x0000177C] Drop Iteration 1 Call State: LINECALLSTATE_OFFERING
[11:26:04:843 - 0x0000177C] Answer() entered
[11:26:04:843 - 0x0000177C] lineAnswer(0x0001059A) - 0x000107AA
[11:26:04:843 - 0x0000159C] LINE_REPLY(0x000107AA | 0x00000000)
[11:26:34:843 - 0x0000177C] WaitFor(0x000107AA | CONNECTED) - Timeout
[11:26:34:843 - 0x0000177C] Answer() - E_MIU_TIMEOUT
05-12-2006 10:01 PM
You'll probably need CCM traces and Unity TSP diags to determine why Unity isn't getting the expected response when attempting to answer the call. CSCsc26421 is another fix that addressed one possible cause of this.
-Eric
05-13-2006 11:01 AM
We also do have the ES3 for TSP 8.01b, I'll turn up the unity traces for skinny. The bug CSCsc26421 doesn't have a fix listed in bug toolkit for 4.05. Is there a ES or does the newer TSP 8.1(2) have fix or got to go to 4.1(1) or 4.2?
05-13-2006 01:35 PM
I'm fairly certian the CSCsc26421 fix made it into 8.1(2) even though it seems to be missing from the Release Notes.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide