A simple MWI question !!!

pbarman · ‎08-03-2003

I have a wireless IP phone. I switch it off by the end of the day, and someone leaves a voicemail for me while it's switched off. I come back next morning and switch it on, the MWI doesnot lit on even though I have a new voicemail message! Is it working as desired?

adeolu_adeoye · ‎08-04-2003

I think the problem is that switching the phone off does not allow the MWI to sync properly when the message is sent. The issue is that the notification is sent through when the message is dropped but because the device is not registered, the light never comes on. Unity and CCM will not resend the notification as they believe that it is already there.

You can test this in a variety of ways. You can dial the code manually to find out if MWI is working; you can leave voice messages while the phone is off and check on the SA to see if MWi is on or off; leave voice messages when the phone is on to see if the lamp comes on.

If the tests above prove positive, then it is likely that the unregistering of the device is the main reason the lamp is not lighting up.

I have never used the wireless IP phones but is their power consumption really that high? Can you charge your phone and leave it on at the same time?

Regards,

ade

pbarman · ‎08-04-2003

Thanks for your reply. When I dial the code manually it works. When the phone is on, I never had the problem getting the correct MWI status.

I will check on the Unity SA if the phone is Off and someone leaves a voice message whats the MWI status showing.

Actually I donot have this wireless phone, its one of my customer :)

Partha

adeolu_adeoye · ‎08-04-2003

Hi Partha,

Based on your reply, it seems MWI is working perfectly on both Cisco Unity and CCM. The problem seems to be with the fact that the code is sent to an unregistered device and Unity will not resend an already sent code.

You could also try to resync MWIs (you will see this on the Switch Page of the SA) every morning when you switch the wireless phone on. If this clears the problem, you can automatically set this synching to occur every morning. Note that I do not really recommend this during production hours but if it is your only option, try it out.

Regards,

Ade

pbarman · ‎08-12-2003

I have a question here. When the IP phone is powered off, the phone is unregistered with the Callmanager. A VM message is left for the subscriber. Unity traces show that the MWI activation request is sent to CCM and status of subscriber MWI on Unity is ON.

Now......

1)Will Callmanager send a MWI ON message to the unregistered phone? Or, does the Callmanager wait until the phone gets registered again? Or, does it just discard the MWI message seeing that the phone is not registered?

2)Where is the MWI status of the IP phone stored, on the Callmanager or on the IP phone itself?

Upon powering on the phone, MWI is not lit on.

TIA,

Partha

afuller · ‎08-14-2003

If you have a 7960 that is registered to the same CallManager, remove its power, leave a voice mail, wait 10-20 minutes, then boot the phone back up, does its lamp come back on? On my CCM 3.2 box in my lab I get this in the CCM trace:

StationD(1, 92, 212) - Send StationOutputSetLamp in restart0_StationSoftKeySetReq

StationD: 14cb9e0c SetLamp stimulus=15(VoiceMail) stimulusInstance=1 lampMode=2(LampOn).

The lamp on my 7960 does indeed come on. Check your CCM trace for the same "Send StationOutputSetLamp" and LampOn messages. If you don't see it, then the problem is in CallManager. If you do see it, then the problem is in the phone load. You'll probably have to open a TAC case.

pbarman · ‎08-14-2003

So, does Callmanager resend the MWI activation stimulus to the IP phone, upon the IP phone registering back to CCM.

afuller · ‎08-14-2003

As witnessed by the CCM trace, it should. In CCM 3.2 the place to look in the database is the NumPlan table.

SELECT dNOrPattern, tkLampBlinkRate_MessageWaiting FROM NumPlan WHERE dNOrPattern = '5015'

Replace 5015 with your phone's extension. If the value of tkLampBlinkRate_MessageWaiting is 1, then CallManager thinks the lamp is off. If it's 2, then the lamp should be on.

So, if we leave a new message with the 7920 while it's switched off and we know Unity issued the MWIon request (via the Notifier traces), turn the phone on, and the MWI lamp doesn't light, the conclusions to draw from this are:

1. If tkLampBlinkRate_MessageWaiting is set to 1, CallManager fluffed.

2. If tkLampBlinkRate_MessageWaiting is set to 2, but when the phone registers we don't see that LampOn message sent, CallManager fluffed.

3. If tkLampBlinkRate_MessageWaiting is set to 2 and we see CallManager send the LampOn request, then the phone fluffed.

Again, opening a case with TAC may be the way to go here. (Tell 'em about this post so they give me credit for the bug. ;)

adam

pbarman · ‎08-21-2003

Hi Adam,

Thanks for your reply, it really helped. I have addedd my trace analysis here, and it looks like the Callmanager is the problem as it doesnot send the LampOn message when the phone plugs backs on.

---------------------------------------------------

THE EXTN 1131 WAS UNPLUGGED FROM THE NETWORK.

HERE A CALL IS MADE FROM EXTN 1415 TO EXTN 1131 AT 13:38

-------------------------------------------------------------

08/20/2003 13:38:08.206 CCM|Digit analysis: match(fqcn="2128041415", cn="1415", pss="NY-911:NY-TollFree:NY-US:NYDID:NYInternal", dd="1131")|<:STANDALONECLUSTER><:10.39.2.2><:2><:10.39.2.9><:SEP00907A00E88B>

-----------------------------------------------------------------------

CALL GOES TO EXTN 1131's VOICEMAIL BOX, AND A VOICEMAIL LEFT FOR 1131

-----------------------------------------------------------------------

08/20/2003 13:38:22.271 CCM|Digit analysis: Changed VoiceMailBox = 1131

08/20/2003 13:38:22.286 CCM|StationD: 000000579 CallInfo callingPartyName='Wai Fong' callingParty=1415 cgpnVoiceMailbox= calledPartyName='Voicemail' calledParty=1400 cdpnVoiceMailbox=1400 originalCalledPartyName='' originalCalledParty= originalCdpnVoiceMailbox= originalCdpnRedirectReason=0 lastRedirectingPartyName='Gene Raytsin' lastRedirectingParty=1131 lastRedirectingVoiceMailbox=1131 lastRedirectingReason=0 callType=2(OutBound) lineInstance=1 callReference=33572591. version: 0x0|<:STANDALONECLUSTER><:10.39.2.2><:2><:10.39.2.9><:SEP00907A00E88B>

--------------------------------------------------------------------------------------------

ON SQL DATABASE "NUMPLAN" TABLE THE "tkLampBlinkRate_MessageWaiting" FIELD SHOWS A VALUE OF "2" FOR THE EXTN 1131, WHICH IS CORRECT BECAUSE THE EXTN 1131 HAS A NEW VOICEMAIL/MWI

AT THIS POINT THE PHONE 1131 IS PLUGGED BACK INTO THE NETWORK AT 13:51. CALLMANAGER SHOULD HAVE ISSUED A LAMPON MESSAGE TO PHONE TO LIT MWI, BUT IT DOESN'T DO SO. MWI STILL OFF ON PHONE, AS WELL AS IN PHONE PROPERTIES WEBPAGE

--------------------------------------------------------------------------------------------

08/20/2003 13:51:16.406 CCM|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP000BBED800F5, TCPHandle=000000603, IPAddr=10.39.1.251, Port=49797, Device Controller=[2,89,591]|<:STANDALONECLUSTER><:10.39.2.2><:2><:10.39.1.251><:SEP000BBED800F5>

08/20/2003 13:52:18.854 CCM|StationInit: 000000603 Stimulus stimulus=15(VoiceMail) stimulusInstance=1.|<:STANDALONECLUSTER><:10.39.2.2><:2><:10.39.1.251><:SEP000BBED800F5>

------------------------------------------------------------------------------------------

NOW EXTN 1131 CALLS VOICEMAIL AND FINDS A NEW MESSAGE, MWI STILL OFF. USER READS THE MESSAGE BUT DOESN'T SAVE IT, SO THE MESSAGE IS STILL NEW. USER HANGS UP AT 13:53. IMMEDIATELY AFTER HANGING UP THE MWI ON 1131 LITS "ON"

-------------------------------------------------------------------------------------------

08/20/2003 13:52:18.870 CCM|StationD: 000000603 CallInfo callingPartyName='Gene Raytsin' callingParty=1131 cgpnVoiceMailbox= calledPartyName='Voicemail' calledParty=1400 cdpnVoiceMailbox=1400 originalCalledPartyName='Voicemail' originalCalledParty=1400 originalCdpnVoiceMailbox=1400 originalCdpnRedirectReason=0 lastRedirectingPartyName='' lastRedirectingParty= lastRedirectingVoiceMailbox= lastRedirectingReason=0 callType=2(OutBound) lineInstance=1 callReference=33573332. version: 0x80000004|<:STANDALONECLUSTER><:10.39.2.2><:2><:10.39.1.251><:SEP000BBED800F5>

08/20/2003 13:53:21.709 CCM|StationInit: 000000603 Stimulus stimulus=15(VoiceMail) stimulusInstance=1.|<:STANDALONECLUSTER><:10.39.2.2><:2><:10.39.1.251><:SEP000BBED800F5>

08/20/2003 13:53:29.446 CCM|StationD: 000000603 SetLamp stimulus=15(VoiceMail) stimulusInstance=1 lampMode=1(LampOff).|<:STANDALONECLUSTER><:10.39.2.2><:1><:><:>

08/20/2003 13:54:02.476 CCM|StationD: 000000603 SetLamp stimulus=15(VoiceMail) stimulusInstance=1 lampMode=2(LampOn).|<:STANDALONECLUSTER><:10.39.2.2><:1><:><:>

pbarman · ‎09-07-2003

Its is a bug with CCM, and is fixed in CCM 3.3.2 ES32 and CCM 3.3.3

Bug ID# CSCeb27709