I set up a Unity Connection 7.0 the other day using a SIP trunk. The SIP security profile allows unsolicited notifications and MWI is defined for the user that I'm using to make my tests - yet the MWI lamp never turns on (it's a 7975 phone in SCCP mode) when somebody leaves a message.
I turned on traces to see what is going on, and sure enough, Unity Connection (10.145.206.104) does send the number of new voicemail messages to the CUCM (10.145.206.102). Here's an extract from the traces:
12/02/2008 01:12:53.534 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.145.206.104 on port 53183 index 8589 with 529 bytes:
12/02/2008 01:12:53.548 CCM|//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::20000>
12/02/2008 01:12:53.548 CCM|//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.145.206.104 on port 53183 index 8589
As you can see, UCx reports one new message, yet the MWI lamp doesn't turn on. Even a phone reboot doesn't change that. Also in the Unity Connection interface (Users - Edit - Message Waiting Indication) it shows that MWI is on.
If the user calls the voicemail, he's told there's a new message. Upon having listened to the message, the MWI status changes to off in the Unity Connection interface, and I see the following in the traces (I know.. the traces are older than the MWI on... but this is simply from an earlier attempt)
12/02/2008 01:10:21.809 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.145.206.104 on port 53183 index 8589 with 528 bytes:
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...