the main flow of this is after the message arrives to exchange, exchange sends a TABLE_ROW_ADDED (you can use the MBXSuite to see this) event to the subscriber, this triggers the MWI behavior in unity and then unity uses one of it's out ports to send the MWI signal (you can use the port status monitor to see this)
in port status monitor you do not see if it's to set it on or off, you only see the Dialing MWI(DN) message
it hits one of the MWI DNs in CCM, which then dials the users DN and sets MWI on or off
VM ports reach MWI DNs, MWI DNs reach user DN
you can see all this in the traces but i think the link i posted is a good explanation without the need to read thru traces
BTW, the way this integrates is via skinny, think of the VM ports as virtual phones
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...