/mcp• The handling of dispatch messaging is supported only over the phone interface. If you handle the dispatch messages from any other client interface, such as Web Inbox or Cisco Unified Personal Communicator, the user cannot postpone, accept, or decline the message. The handling of dispatch messaging is not supported with Visual Voicemail. Note • The dispatch messages are not synchronized between Unity Connection and Exchange server if single inbox has been configured. For information on single inbox, see the Unified Messaging, on page 150 section. • The dispatch messages can never be transcribed even if SpeechView has been enabled for the recipients. • A user can delete the last copy of a dispatch message using Web Inbox or Cisco Unified Personal Communicator. • During playback of a dispatch message, if a user presses the phone keypad key that is mapped to the “skip” or “delete” menu options, Unity Connection interprets the “skip” key press as “postpone,” and the “delete” key press as “decline.” • The recipient who accepts the dispatch message is the only user to have a copy of that message in his/ her mailbox. The recipient can select to hear the dispatch messages first, during the playback of all voice messages using phone interface. • The copy of a dispatch message is not stored in the Deleted Items folder if the recipient declines a dispatch message. • A dispatch message once accepted by a user is treated as a general voice message. Therefore, a dispatch message once accepted cannot be forwarded to another user. The message is presented to the phone interface like a voice message and not announced as a dispatch message. • If message notification rules are configured for dispatch messages, by the time users receive the notification and call in to retrieve the message, the accepted dispatch messages are gone from the recipient mailboxes. • The dispatch messaging is not supported for digital networking. For more information on digital networking, see the Networking, on page 125 chapter. • For a Unity Connection cluster configuration, two different users can call into the publisher and subscriber servers to accept the same dispatch message if the cluster is stuck in a split brain condition. The split brain condition refers to the time when both publisher and subscriber servers are stuck in Primary state. After the split brain condition has been resolved, the user who last accepted the dispatch message is the final recipient and the message is removed from the mailbox of the other user. Message Delivery When a message is delivered by Unity Connection, the recipient is either the Unity Connection Messaging system for unidentified messages or the recipient listed in the identified messages. Message Delivery and Sensitivity Settings The message delivery and sensitivity settings allow the users to control the delivery time of a message, the users who can access it, and if the messages can be forwarded to other users. System Administration Guide 135 Messaging Message Delivery