McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 146

↗ View in doc context
page
146
source
unity-connection/v15/design-guide/design-guide.md
chunk_id
unity-connection::v15::design-guide::design-guide::131

• User to User Voice Messages: The messages left by Unity Connection users to another users or distribution lists are identified or user to user voice messages. Users can reply or forward messages from other users. Consider a user calls another user extension, the called user does not answer and the call is forwarded to user mailbox where the caller leaves a voice message. In this case, if Identified User Messaging is enabled and supported by phone system, and the user calls from primary extension or an alternate device, Unity Connection recognizes that the calling extension is associated with a user or identified user. The identified user messaging is enabled by default. It can be disabled using the Disable Identified User Messaging Systemwide setting on the System Settings > Advanced > Conversations page. Unity Connection does not perform caller authentication or verification when an identified caller leaves a voicemail for another user. • Email Messages in Exchange Server: Users can access emails stored in the user mailboxes on an Exchange server. The Exchange emails can be accessed using the Text-to-Speech feature. For more information, see the Unified Messaging, on page 145 section. • System Broadcast Messages: The recorded announcements sent to everyone in an organization are system broadcast messages. Users must listen to each system broadcast message in its entirety before listening to other new and saved messages or changing setup options. They cannot fast-forward or skip a system broadcast message. For more information, see the Broadcast Messaging, on page 135 section. By design, system broadcast messages do not trigger message waiting indicators (MWIs) on user phones. Note • Text or HTML Notifications: Message notifications are sent in the form of text messages to email addresses, text pagers, and text-compatible mobile phones. When a new voicemail is delivered to users, they receive SMTP based HTML notifications. For more information, see the Notifications, on page 173 chapter. • Receipts: A user can request a read receipt when sending a message. The sender receives a message receipt when the recipient listens to the message. New receipts turn on the message waiting indicator on the user phone and can trigger message notifications. When a voice message cannot be delivered, if the sender is configured to accept receipts, Unity Connection alerts the sender with a nondelivery receipt (NDR). A user can re-send the NDR to a different recipient at a later time. The NDR contains a copy of the original message. • Interview Handler Messages: Interview handlers collect information from callers by playing a series of questions that you have recorded and then recording the answers offered by callers. When all the answers have been recorded, they are forwarded as a single voice message, with beeps separating the answers, to the recipient (user or distribution list) that you designate in the interview handler configuration. • Dispatch Messages: The dispatch message is sent to a distribution list with the message configured in such a way that only one user responds to that message. A user can accept, decline, or postpone the dispatch message. For more information, see the Dispatch Messages, on page 129 section. • Live Record Messages: The messages recorded during a live conversation between a user and a caller are the live record messages. The recorded messages are stored in the user mailbox. The user can access the messages at any time or forward it another user or group of users. For more information, see the Live Record, on page 134 section. System Administration Guide 128 Messaging Types of Messages