Unity MWI Lamp Status

Unanswered Question
Sep 22nd, 2008
User Badges:

We have had an issue resulting (we think) from a Domain message store defrag we did on Saturday where some of our end users MWI indication is out of synch. The issue is intermittant and we would be able to address it more proactively if we could determine who's acct is out of synch and who's acct is not. Is there anyway to diagnose this so we can see who has the issue and who doesn't? I tried in unity data link explorer but I am not able to see the failed accts.

Any advice would be greatly appreciated.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Brandon Buffin Wed, 09/24/2008 - 07:14
User Badges:
  • Purple, 4500 points or more


Have you tried to resynch the MWIs? Go to the Tools Depot Switch Integration Tools > Telephone Integration Manager > Your Integration > Properties > Resynchronize Now. You can also schedule the resync.

Hope this helps.


tim.giles Mon, 10/06/2008 - 09:58
User Badges:
  • Silver, 250 points or more

Hi Vicky,

What version of CallManager are you using?

If it's on a Windows server using SQL you can use SQL Query analyzer and run a query for DN's and see if the "tklampblinkrate_messagewaiting" value is (1) or (2) . If it's 2 it means it's ON

Basically run the following command:

SELECT * FROM NumPlan WHERE tkLampBlinkRate_MessageWaiting = '2'

You can also do a more basic search in CallManager (on all CCM versions) on the individual phones (CCMAdmin > Device > Phones). Just click on their MAC address and the details will show you the status of the message waiting indicator.

According to this previous NetPro post there's a similar query you can run on CCM 6.x (will probably apply to v5 as well):


As per the other post here (5* for you), it's probably worth doing a sync out of hours from the Integration manager.

MWI can generally be attributed to the following problems:

* CSS and Partition misconfiguration

* Permissions issues in Exchange (have you moved these users to a different mail store recently?)

* Misconfigured voicemail ports in CallManager (check in Ingration manager to see if they are all enabled for MWI dialout)

* Misconfiguration of MWI ON/OFF numbers in CCM

Hope this helps.

Please rate useful posts...


This Discussion