The notifier (which does the MWI and notification device triggers) is getting events directly from Exchange about changes in your inbox. When we get a notice that something changed we truck out there and see if you have any new voice mail messages or other new message types listed to fire delivery triggers for that account. If so, we pull the trigger.
We have no way of knowing where that message came from or how it got there so we wouldn't be able to make special provisions about messages send to public distribution lists. Exhange "flattens" the DL list for us and it's sent out just as if you had individually addressed each user in the list (see other posts on Exchange's "single instance message scheme" for more on this if you're really bored or curious).
Can I ask why this is desirable? Just curious what the application here is and if maybe there's a different solution.
seems kinda weird though... if the message went to a DL and landed in my inbox as a voice mail and my lamp didn't go on, would you assume that the voice mail system dropped the ball? What if that message were important (i.e. like "the building is on fire, you might want to make your way to the exits")?
Seems like introducing a "low priority" message concept might be a better solution. Don't assume that messages going to DLs are all low priority but if the sender marks any message as "low" (individual or to a DL) don't light the lamp (or trigger outdials). Seems more consistent.
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...