Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

MWI error: HardFailure from lineDevSpecific.

The event viewer shows this error:<br><br>Component Miu: Thread 0x00000C18 had a Failure on Port 12 in Method CAvTSPAbstraction::Selsius_SetMWI()<br><br>DESCRIPTION: HardFailure from lineDevSpecific.<br>DETAILS: <br> DestAddress: 57703<br> Messages: 1<br> State: ON<br> ErrorCode: 0x80000048. <br><br><br>This error appears in my log 4 times today. The first error was on Tuesday 3/20. It looks like it means that it received an error from Call Manager when it instructed CM to turn on the MWI.<br><br>Here is another error that happens once or twice a day:<br>Component Miu: Thread 0x00000B98 had a Failure on Port 1 in Method CAvMiuLine::Drop()<br><br>DESCRIPTION: Timed-out waiting for DropCompletedEvent.<br>DETAILS: <br> HCALL: 0x00000000<br> CallState: LINECALLSTATE_UNKNOWN<br> Monitor HCALL: 0x00000000<br> Monitor CallState: LINECALLSTATE_UNKNOWN.<br>CALLINFO: <br> CallerID: Unknown<br> CalledID: Unknown<br> RedirectingID: Unknown<br> Origin: Internal<br> Reason: FwdNoAnswer<br> Trunk: 0.<br>CALL SEQUENCE:<br>[15:59:25:501 - 0x000001DC] LINE_APPNEWCALL(0x000107F8)<br>[15:59:25:501 - 0x000001DC] GetNewCall() - 0x0001045D<br>[15:59:25:501 - 0x000001DC] SetEvent(NewCall)<br>[15:59:25:501 - 0x000001DC] LINECALLSTATE_OFFERING(0x000107F8)<br>[15:59:25:501 - 0x000001DC] LINECALLSTATE_DISCONNECTED(0x000107F8 | Normal)<br>[15:59:25:501 - 0x000001DC] StopIO(TERM_DROPPED) entered<br>[15:59:25:501 - 0x000001DC] StopIO(TERM_DROPPED) - S_OK<br>[15:59:25:501 - 0x000001DC] SetEvent(ForceDisconnect)<br>[15:59:25:501 - 0x000001DC] ResetEvent(ForceDisconnect)<br>[15:59:25:501 - 0x000001DC] DropByMonitor() entered<br>[15:59:25:501 - 0x000001DC] Drop Iteration 1 Call State: LINECALLSTATE_DISCONNECTED<br>[15:59:25:501 - 0x000001DC] lineDrop(0x0001045D) - 0x0001075E<br>[15:59:25:501 - 0x000001DC] LINECALLSTATE_OFFERING(0x0001045D)<br>[15:59:25:501 - 0x000001DC] LINECALLSTATE_DISCONNECTED(0x0001045D | Normal)<br>[15:59:25:501 - 0x000001DC] LINECALLSTATE_IDLE(0x0001045D)<br>[15:59:25:501 - 0x000001DC] LINE_REPLY(0x0001075E | 0x00000000)<br>[15:59:25:501 - 0x000001DC] WaitFor(0x0001075E | IDLE) - IDLE<br>[15:59:25:501 - 0x000001DC] DropByMonitor() - S_OK<br>[15:59:25:501 - 0x000001DC] LINECALLSTATE_IDLE(0x000107F8)<br>[15:59:25:501 - 0x000001DC] StopIO(TERM_DROPPED) entered<br>[15:59:25:501 - 0x000001DC] StopIO(TERM_DROPPED) - S_OK<br>[15:59:25:501 - 0x000001DC] SetEvent(ForceDisconnect)<br>[15:59:25:501 - 0x000001DC] ResetEvent(ForceDisconnect)<br>[15:59:25:501 - 0x000001DC] lineDeallocateCall(0x000107F8) - 0x00000000<br>[15:59:25:501 - 0x000001DC] lineDeallocateCall(0x0001045D) - 0x00000000<br>[15:59:25:547 - 0x00000B98] Drop() entered<br>[16:00:25:547 - 0x00000B98] WaitFor(DropCompleted) - Timeout. <br>If I interpret it correctly, these errors appear when a call gets forwarded and Unity answers but they don't leave a message and immediately hang up but Unity waits for input.<br><br>Do either of these signify something critcical?<br><br>Thanks,<br><br>Vince<br><br><br><br>

8 REPLIES
Anonymous
N/A

Re: MWI error: HardFailure from lineDevSpecific.

They could be serious... but we do see these types of events on ananog TAPI drivers, too... the driver doesn't send us a disconnect event or the events come out of order and we're left in a state where the port is burned or out of service for a while until it times out or the like.

What version of Unity/TSP/CM are you using here?

Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

New Member

Re: MWI error: HardFailure from lineDevSpecific.

on 3/19 we upgraded everything in one shot (I have another post on the forum relating to this "Unity Upgrade Problems from 2.4.0.120 to 2.4.6"):

Unity 2.4.0.120 to 2.4.6
CM 3.02d to 3.08
AvCiscoTSP 1.0.0.21 to 1.0.0.28


Here is another error we are getting:

AvPerfMonitorMsgs_MC

Thread [0x9BC]: Loop failure [0x80040200] in averager with hash string [S00000001].


Anonymous
N/A

Re: MWI error: HardFailure from lineDevSpecific.

yeah, you can ignore any perfmonitor error... they're meaningless and harmless. We're ripping the component out entirely in the next build or so since folks get stressed out seeing those errors in there.

it was a good idea that never panned out... it was supposed to figure out how "busy" the system was based on a whole bunch of variables and then average it over time. We were going to use this information to "throttle" non critical Unity functions such as reports, cleanup threads and the like. Unfortunately with various versions of Windows NT/2K it had problems keeping up with the API changes etc... and never really worked terribly well anyway. So, out it comes.


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

New Member

Re: MWI error: HardFailure from lineDevSpecific.

Ok. I will ignore the perfmon errors and I will stay tuned for info on the other errors.


Anonymous
N/A

Re: MWI error: HardFailure from lineDevSpecific.

The MIU guys looked over the errors for me. The MWI error didn't cause any concern. Apparently those are "normal" MWI failures that we see with CM on all versions. They are treated like other MWI failures on analog equipment and we try them again in a little while. No one here is sure exactly why the skinny interface is rejecting us at that point but it's should be causing any serious problems. Unless you're seeing them happen with great frequency (which doesn't appear to be the case here) I wouldn't worry about them too much.

The drop failure is more of a concern. We've seen these back in the early days with Dialogic and NMS as they developed their TSPs... these can be serious since the port states can get out of whack and a port can go out of service untill you restart the machine and reload the TSP. We're basically telling it the call is complete and to take the port back on hook and we're not getting a confirmation back. The developers are curious to know if the port recovers all the time from this or if the port in question goes out of service or takes a "nap" for a period of time before resetting or anything of the kind. Have you had any situations where ports were not being responsive? It may not be obvious that this is the case since it should just hunt right over it to the next port. If you could pay special attention (i.e. calling the ports that issued this error directly to see if they answer).

Unfortunately diagnosing these problems can be tedious and difficult. It'll involve getting CM traces, Unity traces and TSP traces all kicking out and then syncing up the information when an error is seen. Lots and and lots of slogging through file dumps to see who's missing an event or sending something out of order and the like.

If this happens regularly at your site (we haven't seen these on our front system or in the lab here so far as I know) it would be ideal if we could get hooked up with some CM folks and get the right traces turned on for them and perhaps load a debug version of the TSP and wait for it to happen again. If you want to pursue this (if it's hosing ports on your system, you really need to) I'd get hooked up with TAC and the CPR people here can get involved and we'll get the ball rolling.


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

Anonymous
N/A

Re: MWI error: HardFailure from lineDevSpecific.

As a follow up to this... Aaron indicated that you will get this timeout error if the caller hangs up just before Unity tries to answer.

Any chance that's the cause of these? Phantom calls are not uncommon (i.e. the voice mail system tells the user hears the call being forwarded to voice mail and just hangs up since they don't want to leave a message). If so, as long as the port is still taking calls afterwards, the error is benign.


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

New Member

Re: MWI error: HardFailure from lineDevSpecific.

From what you are saying in your replies, I think there is a very good probablity that these are errors from Phantom Calls. The ports are still answering calls and these errors don't occur that often. I will keep reviewing the logs. Thanks for all the info.



Anonymous
N/A

Re: MWI error: HardFailure from lineDevSpecific.

I am seeing this at the navsea site as well...the lindev errors.. every 20 to 30 minutes on different ports.
we are using 3.08 cm and 2.4.6 unity

266
Views
0
Helpful
8
Replies