05-23-2008 05:48 AM - edited 03-15-2019 10:50 AM
Hello there,
I have a customer that is running Unity Connection 2.0.1
and call manager 6.1.1.2000-3
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?
05-29-2008 10:34 AM
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.
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_tech_note09186a008027fa9f.shtml
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a0080711ae3.shtml
11-21-2008 08:52 AM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide