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

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

For an introduction to the new site, click here. And see here for current known issues.

New Member

MWI issues with Unity Connection

Hello there,

I have a customer that is running Unity Connection 2.0.1

and call manager

They upgraded to 6.1 just a few weeks ago.

Here is my issue.

Yesterday they added another remote site this this call manager (currently have 8 other remote sites)

Everything works fine but the MWI on the phones. When you get a voicemail the light does not come on. You can dial the MWI light extension and make the light go on and off and the Calling Search Space for the voicemail ports does have the new location Partitions in them.

All other sites the MWI work fine.

After digging and testing, it seems that any user we added since the upgrade to call manager 6.1 the MWI does not work.

I can put an old number from another location (that was built prior to the upgrade) on a phone at the new location and the light works perfectly.

If i build a brand new extension and voicemail it does not. So i know its not a network issue, or CSS issue

It seems to just point to any new phones/mailboxes we create.

Anyone seen this before?


Re: MWI issues with Unity Connection

The reasons for this may be:

Incorrect Unity or Callmanager Parameter Configuration

Cisco Callmanager CSS Misconfiguration

Error Message in the Application Event Log Viewer

Please follow these documents for the solution.

New Member

Re: MWI issues with Unity Connection

I'm seeing the same issues on a cm 4.1 with unity. I can't seem to get the mwi to light up. The only issue is that I can't put the partition they are in into the same css as unity because the cm tries to route calls out the remote pri at the remote office.