One Message for all Public Distribution List members
we have a small call center, the call center number is realized with a Hunt Group in UCM 6.x. Now, they want to receive a voicemail when nobody answers the call. For the moment a Call Handler with a Public Distribution List in Unity works okay. But now a every member of the PDL will receive his own voicemail in his own mailstore. Would it be possible to configure one mailstore for a couple of PDL members? The goal is, when one call center members checks or deletes the voicemail the lamp should to turn off on the other phones.
Re: One Message for all Public Distribution List members
What you need is a single shared mailbox for voice messages from the call center. In Active Directory, create a group that contains all of the members in the call center. Then create the shared mailbox account that will be used as the Unity subscriber. Edit that account. On the Exchange Advanced Tab, Mailbox Rights, add the group. Give the group Full Mailbox access and also Send As permissions. From each agent's Outlook, you can then add the Unity account as a second mailbox. Since this is a "shared" view, when one agent handles the voice message, the MWI is turned off. If one agent deletes the message, it appears as deleted on all other agent views in Outlook. P.S. The Send As permissions is only required if the agents need to forward the voice message to someone.
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...