Unity errors when lighting MWI

bradwelch · ‎08-28-2003

Currently Unity is unable to consistently light MWI lamps.

A typical scenario is:

I call a subscriber and leave a message. According to what I see Unity can immediately tell when a VM lands in a mailbox. Via status monitor, I can see Unity almost instantaneously attempts to dial the MWI for the ext. For some reason Unity fails to light the lamp. The mwi process normally takes about a second. When watching status monitor I see this taking closer to 30 seconds, at which time Unity writes a failure event to the application log then reattempts the process. Eventually Unity succeeds after several attempts, sometimes it doesn't succeed at all and the lamp is never lit. Any ideas what might cause this?

Unity 3.1(5)

CM 3.3(2)spc

TSP 7.02

Exchange 5.5 sp4

lindborg · ‎08-28-2003

can you post the full text of the error message you're seeing in the event log?

bradwelch · ‎08-28-2003

Here is the message from the event log (event ID 521):

Component Miu: Thread 0x000009E4 had a Failure on Port 8 in Method CAvTSPAbstraction::Selsius_SetMWI()

DESCRIPTION: HardFailure from lineDevSpecific.

DETAILS:

DestAddress: 2713

Messages: 1

State: ON

ErrorCode: 0x00000102.

bradwelch · ‎08-28-2003

Here are some lines I pulled from the TSP micro traces. Do you see anyting interesting in these?

10:55:17:250 (CiscoUnity_TSP,116,SkinnyTSP,11) [Thread 0x000008CC] [Device 11] Sending DevSpecific(SetMwi) LINE_REPLY 00010140 Code 00000000.

10:57:50:437 (CiscoUnity_TSP,116,SkinnyTSP,18) [Thread 0x000000A0] [Device 11] CAvTapiLine::SetMwi: szExtension 1014 fMWIon 0.

10:57:50:437 (CiscoUnity_TSP,116,SkinnyTSP,13) [Thread 0x000000A0] [Device 11] CSkinny::SendOffHookWithCgpn 1014.

10:58:50:421 (CiscoUnity_TSP,116,SkinnyTSP,12) [Thread 0x000006F4] [Device 7] StationCallInfoMessage: CalledID = 1014 CallerID = 1014 nCallType = 3 (ForwardCall).

10:58:50:422 (CiscoUnity_TSP,116,SkinnyTSP,24) [Thread 0x000006F4] [Device 7] CSkinny::SignalCallProgress CallerID 1014 CalledID 1014.

10:58:50:421 (CiscoUnity_TSP,116,SkinnyTSP,19) [Thread 0x000006F4] [Device 7] CAvTapiCallHandler::StoreCallInfo: szCallerID 1014 szCalledID 1014

10:58:50:422 (CiscoUnity_TSP,116,SkinnyTSP,19) [Thread 0x000006F8] [Device 7] CAvTapiCallHandler::GetCallInfo: dwReason 00000002 CallerID 1014 CalledID 1014 RedirectingID 1014.

10:58:50:422 (CiscoUnity_TSP,116,SkinnyTSP,19) [Thread 0x000000A0] [Device 7] CAvTapiCallHandler::GetCallInfo: dwReason 00000002 CallerID 1014 CalledID 1014 RedirectingID 1014.

10:58:50:468 (CiscoUnity_TSP,116,SkinnyTSP,12) [Thread 0x000006F4] [Device 7] StationCallInfoMessage: CalledID = 1014 CallerID = 1014 nCallType = 1 (InBoundCall).

10:58:50:469 (CiscoUnity_TSP,116,SkinnyTSP,12) [Thread 0x000006F4] [Device 7] More CallInfo: CalledVM = 1014 CallerVM = RedirectReason = 1 (ForwardBusy).

10:58:50:469 (CiscoUnity_TSP,116,SkinnyTSP,24) [Thread 0x000006F4] [Device 7] CSkinny::SignalCallProgress CallerID 1014 CalledID 1014.

10:58:50:468 (CiscoUnity_TSP,116,SkinnyTSP,19) [Thread 0x000006F4] [Device 7] CAvTapiCallHandler::StoreCallInfo: szCallerID 1014 szCalledID 1014.

10:59:09:219 (CiscoUnity_TSP,116,SkinnyTSP,21) [Thread 0x000000A0] [Device 12] CSkinny::SetMWIOn szMWIOn szExtension.

10:59:09:218 (CiscoUnity_TSP,116,SkinnyTSP,13) [Thread 0x000000A0] [Device 12] CSkinny::SendOffHookWithCgpn 1014.

10:59:27:812 (CiscoUnity_TSP,116,SkinnyTSP,11) [Thread 0x0000094C] [Device 7] Sending Answer LINE_REPLY 00010141 Code 00000000.

10:59:45:015 (CiscoUnity_TSP,116,SkinnyTSP,18) [Thread 0x0000094C] [Device 12] CAvTapiLine::SetMwi: szExtension 1014 fMWIon 1.

10:59:45:015 (CiscoUnity_TSP,116,SkinnyTSP,13) [Thread 0x0000094C] [Device 12] CSkinny::SendOffHookWithCgpn 1014.

jcampbell · ‎09-09-2003

I have seen this with installing new phones. The problem seems to occur when installing a new phone. The DN receives voice-mail before the phone has registered. I just delete and recreate the voice-mail box since it is using Exchange for the message store.