I have a customer that is running Unity Connection 2.0.1
and call manager 188.8.131.520-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.
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...