MWI extensions are setup on the subscriber and are not message-source dependant. So you can have up to 10 MWI targets on a subscriber but ALL voice mail messages for that subscriber are going to trigger MWI ons for all of the MWI extensions you enter for them. there's no way to have messages trigger specific MWI extensions based on the source of the message.
I can answer for CallManager integration. The default Message Waiting Lamp policy is to set the lamp for the primary extension and display the envelope next to the user's primary DN. This setting is coded on the DN configuration page. Go to each user's phone DN configuration page and set the second DN to be "Light and Prompt" instead of System Policy. One caveat though, if you set the Lamp off on the primary DN, voicemail messages intended for each employee will not get the lamp. Here is a way I believe this could work, create a shared mailbox and voicemail enable with extension 1111 and alternate extension 2222. Add this user to each of the other's Outlook view. Voicemail going to the shared mailbox will trigger MWI for extensions 1111 and 2222. Plus, there is only one copy of the message. If user A handles the message and deletes, user B sees the message has been deleted. This is how we handle these type of situations in our environment.
But I think you could set the general number mailbox as a callhandler to take a message then route it a public distro group. The voicemail light can be triggered on everyone's phone that wants it, it just has to be an apperance next to the button.
So on a 7960 phone, we have the primary users VM light up and a message envelope show up for the share line vm box. We simply Line Text next the button "Group VM" or whatever it matches too. Do a shared line and voila... envlope for general mailbox.
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...