Is there a way to restrict access to a VM box if someone else is already in it?
This is a mailbox that several nurses check, depending on who is available. Since they are located in different areas, they aren’t aware when somebody else is accessing the mailbox, and multiple people are able to get into the box at the same time.
There is no available setting in Unity Connection to limit this access
If you are setting up a "Group" mailbox type setup many people use
You can use the dispatch message feature to send a message to a distribution list ***(from either a call handler or interview handler). The message is configured such that only one user in the group needs to act on the message. When listening to a dispatch message, users are given the option to accept, postpone, or decline the message.
Dispatch messages are handled as follows:
•If a user chooses to accept the message, all other copies of the message are removed from the mailboxes of the other members of the distribution list, regardless of whether the other users have listened to and postponed the message.
•If a user chooses to postpone the message, it remains as an unread message in the mailbox of that user and in the mailboxes of the other members of the distribution list.
•If the user chooses to decline the message, it is removed from the mailbox of that user, but copies of the message remain as unread in the mailboxes of the other members of the distribution list.
•If there is only one copy of the dispatch message remaining, and no user has yet chosen to accept the message, the final user whose mailbox it is in must accept it. That user is not given the option to decline the message.
Dispatch messaging is useful in situations where a team is available to respond to issues, but only one member of the team needs to respond. For example, an IT department may want to set up a call handler to take messages from employees who need assistance, and then send the messages as dispatch messages to a distribution list comprised of IT department staff. All of the members of the distribution list receive a copy of each message. Team members can then decide whether to accept or decline a message; declined messages are then picked up by other team members.
Do one of the following procedures to set up dispatch messaging:
•To Configure Dispatch Messaging for Messages Left for a Call Handler
•To Configure Dispatch Messaging for Messages Left for an Interview Handler
Also see the "Dispatch Messaging Limitations and Behavioral Notes" section.
To Configure Dispatch Messaging for Messages Left for a Call Handler
Dispatch Messaging Limitations and Behavioral Notes Revised May 2009 •Only voice messages can be flagged for dispatch. Email and fax messages cannot be flagged for dispatch.
•The handling of dispatch messages is supported only in the phone interface. If a user opens a dispatch message when using the Cisco Unity Inbox, Cisco Unified Personal Communicator, an IMAP client, or an RSS client, the user is not forced to postpone, decline, or accept the message. Those clients treat dispatch messages as normal voice messages. It is important to make users aware that they must use the phone interface for dispatch messaging to be effective. When using clients other than the phone interface, the only indication that a message is marked for dispatch is when the subject line of the message has been configured to display special text. (For details on configuring subject line formats, see the "Message Subject Line Formats" section.) We recommend that you configure subject line formats to indicate that a message is a dispatch message, as this helps to remind users that they need to access the messages by using the phone interface.
•When using an IMAP client to play dispatch messages, it is not possible to delete or mark the messages as read. At first it may appear that a user can successfully delete or save a dispatch message, but the next time the IMAP client refreshes the message list, the dispatch message displays as a new message. This is true even if the user is using Microsoft Outlook or IBM Lotus Notes with ViewMail. The message is removed only if the user uses the phone interface to decline the message or if another user uses the phone interface to accept the message.
•If there is only one copy of a dispatch message left, it is possible for the user with that last copy to delete it when using either the Cisco Unity Inbox or Cisco Unified Personal Communicator. It is important to make users aware that they must use the phone interface for dispatch messaging to be effective.
•During playback of a dispatch message, if a user presses the phone keypad key that is mapped to the "skip" or "delete" menu options, Connection interprets that key press as "postpone" or "decline" respectively.
•Dispatch messages are not sorted separately from normal voice messages. If you want users to hear their dispatch messages first, the call handler or interview handler that is configured to mark the message for dispatch delivery should also be configured to mark the message as urgent. By default, urgent messages are presented to users first.
•If a user declines a dispatch message, a copy of the dispatch message is not kept in the deleted items folder of that user.
•When a user accepts the message, that user is the only person who has a copy of the message in his or her mailbox.
•When a dispatch message is accepted by a user, the dispatch property is removed and it is treated as a normal voice mail message. If the user subsequently saves the message as new, the message is presented in the phone interface just like any other new message and is not announced to the user as a dispatch message. (Note that the subject line is not altered, so depending on the subject line format used, it may contain a string indicating that the message was originally flagged for dispatch. However, the subject line is not played in the phone interface.)
•It is not possible to forward a dispatch message. A user must first accept the message, which removes the dispatch property. Then the user can forward it as a normal voice mail message.
•When configuring message notification rules to include dispatch messages, make users aware that by the time users receive the notification and call in to retrieve the message, it may be gone from their mailboxes because another user has already accepted the message.
•Dispatch messaging is not supported with digital networking. If remote users are members of a distribution list that is the recipient of a call handler that is configured to mark messages for dispatch delivery, those remote users receive the message as a normal voice message. They are not offered the option to accept, postpone, or decline the message.
•If Connection is configured as a cluster, it is possible for two different users to call into the different servers and accept the same dispatch message when more than one server has the Primary status (known as a "split brain" condition). After the split brain condition has been resolved, the user who last accepted the dispatch message becomes the final recipient and the message is removed from the mailbox of the other user.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...