Troubleshooting Guide for Cisco Unity Connection Release 9.x
Troubleshooting Messages in Cisco Unity Connection 9.x
Downloads: This chapterpdf (PDF - 111.0KB) The complete bookPDF (PDF - 3.63MB) | Feedback

Troubleshooting Messages in Cisco Unity Connection 9.x

Table Of Contents

Troubleshooting Messages in Cisco Unity Connection 9.x

Message Quota Enforcement: Responding to Full Mailbox Warnings in Cisco Unity Connection 9.x

Troubleshooting Undeliverable Messages in Cisco Unity Connection 9.x

Messages Appear to Be Delayed in Cisco Unity Connection 9.x

Some Messages Seem to Disappear in Cisco Unity Connection 9.x

User Has a Full Mailbox

Undeliverable Messages Have Not Been Forwarded to Recipients

Users Assigned to Cisco Unity Connection Entities Were Deleted and No Replacements Were Assigned

Cisco Unity Connection Is Unable to Relay Messages

Message Audio Cannot Be Played in Outlook Web Access

Troubleshooting Recorded Messages Not Being Allowed to Exceed 30 Seconds in Length in Cisco Unity Connection 9.x


Troubleshooting Messages in Cisco Unity Connection 9.x


See the following sections:

Message Quota Enforcement: Responding to Full Mailbox Warnings in Cisco Unity Connection 9.x

Troubleshooting Undeliverable Messages in Cisco Unity Connection 9.x

Messages Appear to Be Delayed in Cisco Unity Connection 9.x

Some Messages Seem to Disappear in Cisco Unity Connection 9.x

Message Audio Cannot Be Played in Outlook Web Access

Troubleshooting Recorded Messages Not Being Allowed to Exceed 30 Seconds in Length in Cisco Unity Connection 9.x

Message Quota Enforcement: Responding to Full Mailbox Warnings in Cisco Unity Connection 9.x

When users hear a prompt related to a full mailbox, it means that one or more of the three quotas that limit the size of voice mailboxes has been reached:

If a mailbox has reached the size of the warning quota, the user hears a warning that the mailbox is almost full.

If a mailbox has reached the size of the send quota, the user is unable to send messages and hears a warning that messages cannot be sent. If the user mailbox contains deleted messages, Cisco Unity Connection offers the option to remove all deleted messages.

If a mailbox has reached the size of the send/receive quota:

The user is unable to send messages.

The user hears a warning that messages cannot be sent.

Unidentified callers are not allowed to leave messages for the user.

Messages from other users generate nondelivery receipts to the senders.

If the user mailbox contains deleted messages, Connection offers the option to remove all deleted messages. If necessary, the user can also remove saved or new messages individually until the mailbox size is below the quotas.

Troubleshooting Undeliverable Messages in Cisco Unity Connection 9.x

Occasionally, messages cannot be delivered to the recipient that the caller intended to reach. The system behavior in this case depends on the type of sender and the reason that the message could not be delivered.

In general, if Connection cannot deliver the message because of issues that are not likely to be resolved (for example, the caller was disconnected before addressing the message, or the recipient mailbox has been deleted), the message is sent to the Undeliverable Messages distribution list, and Connection sends a nondelivery receipt (NDR) to the sender.

Note that the sender does not receive a nondelivery receipt in the following cases:

When the sender of the original message is an unidentified caller

When the sender is a user, but the user is configured to not accept NDRs

While the mailstore of the user is offline (in this case, the NDR is delivered when the database becomes available)

However, if the original message is malformed, rather than sending the message to the Undeliverable Messages list, Connection places the message in the MTA bad mail folder (UmssMtaBadMail). This folder is automatically checked nightly by the Monitor Bad Mail Folders task, and if messages are found, an error is written to the application event log indicating troubleshooting steps.

Messages Appear to Be Delayed in Cisco Unity Connection 9.x

Use the following task list to troubleshoot the possible causes for the apparent delay of messages.

Task List for Troubleshooting Delay in Appearance of Messages

1. To verify the arrival times of messages, generate a user message activity report for the user. For more information, see the "Generating and Viewing Reports in Version 9.x" section in the "Using Reports in Version 9.x" chapter of the Administration Guide for Cisco Unity Connection Serviceability Release 9.x, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/serv_administration/guide/9xcucservagx.html.

2. See the applicable information in the "Orientation Task List for Cisco Unity Connection 9.x Users" section in the "User Orientation in Cisco Unity Connection 9.x" chapter of the User Workstation Setup Guide for Cisco Unity Connection Release 9.x, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/user_setup/guide/9xcucuwsx.html.

Some Messages Seem to Disappear in Cisco Unity Connection 9.x

See the following troubleshooting steps for investigating messages that are not being delivered to the intended recipients.

Confirm that users who are assigned to the Undeliverable Messages distribution list have been forwarding messages to the intended recipients. See the "Undeliverable Messages Have Not Been Forwarded to Recipients" section.

Confirm that the user mailbox is not full. See the "User Has a Full Mailbox" section.

Confirm that you or another administrator did not inadvertently delete a user who was assigned to review the messages for Cisco Unity Connection entities. See the "Users Assigned to Cisco Unity Connection Entities Were Deleted and No Replacements Were Assigned" section.

Review message aging settings. See the "Changing a Message Aging Policy" section in the "Controlling the Size of Mailboxes in Cisco Unity Connection 9.x" chapter of the System Administration Guide for Cisco Unity Connection Release 9.x, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx.html.

The message may have been flagged for dispatch delivery. When users are members of a distribution list that is the recipient of a call handler that is configured to mark messages for dispatch delivery, it is possible for the users to receive a message, but then later find that the message has been removed from their mailboxes because another member of the distribution list accepted the message. See the "Dispatch Messages in Cisco Unity Connection 9.x" section in the "Messaging in Cisco Unity Connection 9.x" chapter of the System Administration Guide for Cisco Unity Connection Release 9.x, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx.html.

The user account may be configured to relay one or more message types to another SMTP address, but the message relay is failing. See the "Cisco Unity Connection Is Unable to Relay Messages" section.

User Has a Full Mailbox

If a user mailbox is no longer allowed to receive messages, Cisco Unity Connection handles the message in one of two ways:

By default, when an unidentified caller attempts to send a message to a user whose mailbox has exceeded the send/receive quota, Connection still delivers the message. You can instead configure Connection to indicate to the caller that the recipient mailbox is full, and prevent the caller from recording a message for that recipient. (In Cisco Unity Connection Administration, on the Message Storage > Mailbox Quotas page, check the Full Mailbox Check for Outside Caller Messages check box.)

If the recipient mailbox has not yet exceeded the send/receive quota at the time an unidentified caller records a message, but the quota is exceeded in the act of delivering the message, Connection delivers the message regardless of the quota.

When a user tries to leave a message for another user whose mailbox has exceeded the send/receive quota, Connection allows the user to record and send the message. However, if the mailbox for the recipient is full, he or she does not receive the message, and if the user account for the recipient is configured to send non-delivery receipts when message delivery fails, Connection sends the message sender a non-delivery receipt.

If the recipient mailbox has not yet exceeded the send/receive quota at the time a Connection user records a message, but the quota is exceeded in the act of delivering the message, Connection delivers the message regardless of the quota.

If a user whose voice mailbox has exceeded the send quota logs in to Connection and attempts to send a message to another user, Connection indicates that the send quota has been exceeded, and does not allow the sender to record the message. If the user calls another user and is forwarded to a voice mailbox, the user is able to leave a message, but the message is sent as an outside caller message.

Read receipts and non-delivery receipts are sent and delivered regardless of the status of the mailbox quota.

Encourage the user to dispose of messages promptly so that the Connection mailbox does not fill up, and explain to users on the Undeliverable Messages distribution list the importance of regularly checking for and forwarding undeliverable messages.


Caution If the mailboxes of the users who are assigned to check the Undeliverable Messages list exceed the send/receive quota, the messages sent to the Undeliverable Messages distribution list are lost. To avoid this problem, specify a generous value for the send/receive quota for at least one user who is a member of the Undeliverable Messages list, and encourage the user to dispose of messages promptly.

Undeliverable Messages Have Not Been Forwarded to Recipients

Messages returned to the Unity Messaging System mailbox are forwarded automatically to users whose names appear on the Undeliverable Messages system distribution list. The messages then must be forwarded to the intended recipients. Explain to users on the Undeliverable Messages distribution list the importance of regularly checking for and forwarding undeliverable messages.


Caution If the mailboxes of the users who are assigned to check the Undeliverable Messages list exceed the send/receive quota, the messages sent to the Undeliverable Messages distribution list are lost. To avoid this problem, specify a generous value for the send/receive quota for at least one user who is a member of the Undeliverable Messages list, and encourage the user to dispose of messages promptly.

Users Assigned to Cisco Unity Connection Entities Were Deleted and No Replacements Were Assigned

When you delete a user who was assigned to review the messages that are sent to any of the following Cisco Unity Connection entities, make sure that you assign another user or a distribution list to replace the deleted user; otherwise, messages may be lost.

Undeliverable Messages distribution list (by default, the UndeliverableMessagesMailbox user account is the only member of this distribution list)

Operator call handler

Opening Greeting call handler

Goodbye call handler

Example Interview call handler

Cisco Unity Connection Is Unable to Relay Messages

Cisco Unity Connection uses the settings on the Message Actions page for a user in Cisco Unity Connection Administration to determine how to handle the different types of messages that it receives for the user. The relay action instructs Connection to send all messages of a certain type to a relay address on a different messaging system (such as a corporate email server) for storage and user access.

If the relay address that is configured for a user matches one of the user SMTP proxy addresses that is configured on the system, Connection does not relay messages to the relay address, to avoid possible delivery loops. If Connection were to relay a message to a proxy address, it is possible that the proxy address would resolve back to the same Connection mailbox that relayed the original message, thus creating an infinite loop.

When configuring relay addresses for message relay, we recommend that you use the precise email address of the destination mailbox, for example, alias@mailserver.

Message Audio Cannot Be Played in Outlook Web Access

When Cisco Unity Connection is configured to relay messages to a Microsoft Exchange server (by using the Relay the Message or the Accept and Relay the Message action), users who use Outlook Web Access to access their Exchange mailboxes may not be able to play the message audio. When this occurs, the message header indicates that the audio attachment is available for the message, but the user cannot view or play the attachment when the message is opened. For a resolution to this issue in Microsoft Exchange 2007, refer to Microsoft Knowledge Base article 954684.

Troubleshooting Recorded Messages Not Being Allowed to Exceed 30 Seconds in Length in Cisco Unity Connection 9.x

If recorded voice messages are not being allowed to exceed 30 seconds, confirm that the Cisco Unity Connection license file has the LicMaxMsgRecLenIsLicensed license tag enabled. Do the following procedure.

To Confirm That the LicMaxMsgRecLenIsLicensed License Tag Is Enabled in the License File


Step 1 In Cisco Unity Connection Administration, expand System Settings, then select Licenses.

Step 2 On the Licenses page, under License Count, confirm that the value of Voice Message Recordings Longer Than 30 Seconds Allowed (LicMaxMsgRecLenIsLicensed) is set to Yes.