Table Of Contents

Preparing Subscribers, Operators, and Support Desk Personnel to Work with Cisco Unity

Overview: Subscriber, Operator, and Support Desk Orientation

Subscriber Orientation

Operator Orientation

Support Desk Orientation

Preparing Subscribers, Operators, and Support Desk Personnel to Work with Cisco Unity

---

Overview: Subscriber, Operator, and Support Desk Orientation

Subscribers and operators in your organization need information about Cisco Unity that is specific to your installation. In addition, if your organization has a support desk, the staff will need to be prepared to answer the questions that subscribers may ask, and need to be aware of the resources that are available to assist them in answering subscriber questions. This chapter reviews the preparations for orienting and training subscribers, operators, and support desk employees to Cisco Unity.

See the following sections:

•Subscriber Orientation

•Operator Orientation

•Support Desk Orientation

Subscriber Orientation

After you create subscriber accounts and set up the client applications that subscribers will use to access Cisco Unity from their phones and computers, use the following task list to acquaint subscribers with Cisco Unity. If you are planning supplemental Cisco Unity training, also consider reviewing the potential subscriber concerns and misconceptions listed in the "Support Desk Orientation" section.

1. Give each subscriber a Cisco Unity User Guide, a Cisco Unity at a Glance card, a Cisco Unity Phone Menus and Shortcuts card, and/or the URLs to the document(s). All subscriber documentation is provided in Unified Messaging and Voice Messaging versions. In addition, the Cisco Unity at a Glance and Cisco Unity Phone Menus and Shortcuts cards are provided in standard conversation and Optional Conversation 1 versions. (Cards are not available for any other conversation styles.) Subscriber documentation is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html.

Depending on the conversation style that subscribers in your organization are familiar with, you may want to provide them with a list of phone menu differences between Cisco Unity and a former voice messaging system—especially if you chose not to offer them an alternative to the standard conversation style, which is specified by default in {Default Subscriber} template.

2. Give subscribers the phone numbers that they dial to access Cisco Unity from within your organization and from outside the organization. As applicable, show subscribers which button or key to use on their desk phones to access Cisco Unity.

Also give them the name and extension of the Cisco Unity system administrator and any support desk contact information. There are spaces to record phone numbers and contacts in the Cisco Unity User Guide, the Cisco Unity at a Glance, and the Cisco Unity Phone Menus and Shortcuts card.

3. Provide subscribers with their initial phone passwords. Alternatively, tell subscribers to log on to the Cisco Personal Communications Assistant (PCA) website to set their phone passwords before they call Cisco Unity to complete first-time enrollment. (Subscribers are not required to enter an existing phone password in order to change it in the Cisco PCA.)

When they have not done so already in the Cisco PCA, subscribers are prompted to change their phone password during first-time enrollment.

4. Make sure that subscribers know to complete first-time enrollment. Subscribers do not need to refer to any Cisco Unity documentation during enrollment. Cisco Unity indicates when the enrollment process is complete. If subscribers hang up before they have completely enrolled, none of their changes are saved and the first-time enrollment conversation plays again the next time that they log on to Cisco Unity.

The "Getting Started: Enrolling on Cisco Unity" chapter in the Cisco Unity User Guide details the tasks that subscribers are asked to complete as part of enrollment.

5. Give subscribers the URL to the Cisco PCA website: http://<Cisco Unity server name>/ciscopca. There are spaces to record this URL in the Cisco Unity User Guide, the Cisco Unity at a Glance, and the Cisco Unity Phone Menus and Shortcuts card.

Subscribers can use the Cisco PCA website to access the Cisco Unity Assistant and the Cisco Unity Inbox, as applicable. Subscribers enter their Windows domain account user names and passwords to log on to the Cisco PCA.

Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA; the Cisco Unity Inbox was known as the Visual Messaging Interface, or VMI. Subscribers who use bookmarked ActiveAssistant and VMI URLs will be redirected automatically to the Cisco PCA website.

6. Explain to subscribers how to secure their phone and Cisco PCA passwords so that they adequately protect their Cisco Unity mailboxes from unauthorized access. Detail the security guidelines for your organization. (Refer to the "Securing Access to Cisco Unity Applications: Password and Account Policy Management" chapter in the Cisco Unity Security Guide for best practice guidelines. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.)

Finally, make sure that subscribers understand that their Cisco PCA passwords are not related to their Cisco Unity phone passwords, nor are the passwords synchronized. Subscribers must use Windows to change their Cisco PCA passwords.

7. To help subscribers make the most of Unified Messaging, make sure that they understand how it works. For subscribers who like to manage voice mail and e-mail messages separately, remind them that they can turn on the Message Type menu so that they can pick which messages to hear by type ("Press 1 for voice messages, 2 for e-mails..."). Alternatively, subscribers can use the Cisco Unity Assistant to specify that Cisco Unity will play e-mail messages last when they check messages by phone. Finally, subscribers may want to create a folder in their e-mail client to store voice messages separately from other messages. Subscribers can also use the Copy to File option available from the Options menu on the Media Master to save voice messages as WAV files on their hard drives.

8. If you have AMIS, Internet, Bridge, or VPIM subscribers in your organization, review the Networking in Cisco Unity Guide and/or the Cisco Unity Bridge Networking Guide for information on how Cisco Unity behaves differently for these types of subscribers, and acquaint them with the applicable details.

Also, explain to regular subscribers how to address voice messages to other locations when they use the phone, ViewMail, and the Cisco Unity Inbox. As necessary for all subscribers, identify how addressing messages to other locations is different with Cisco Unity than it was with a former voice messaging system.

For detailed information, refer to the applicable guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html:

–The Networking in Cisco Unity Guide

–The Cisco Unity Bridge Networking Guide

9. Explain how full mailboxes work with Cisco Unity. See the "Support Desk Orientation" section for issues that subscribers may encounter. Refer subscribers to the Cisco Unity User Guide for similar information.

If your organization set up the Message Store Manager utility (available in Tools Depot) or a similar tool in Exchange to automatically purge deleted messages, make sure that you explain the deleted messages aging policy to subscribers who have class of service rights to manage their deleted messages. Otherwise, subscribers will assume that they have access to their deleted messages indefinitely.

10. If your organization has subscribers who will use TTY and the TTY prompt set, provide training on using TTY with Cisco Unity. For more information on TTY, see the "TTY Overview" section on page 8-5.

11. Make sure that subscribers who own call handlers or public distribution lists understand their responsibilities (if applicable). See the "How Cisco Unity Handles Messages Without a Specific Recipient" section on page 4-5.

12. As applicable, tell subscribers how to use the Cisco Unity Greetings Administrator and System Broadcast Administrator. See the "Recording Greetings and Names" section on page 5-2 and the "Sending System Broadcast Messages" section on page 5-5.

13. Provide training on how to personalize subscriber settings by using the phone or the Cisco Unity Assistant, as summarized in Table 7-1. In particular, subscribers may benefit from a hands-on demonstration of the Cisco Unity Assistant, as they may not be accustomed to using a web interface to set voice messaging options.

Subscribers can refer to the Cisco Unity User Guide or to the Cisco Unity Assistant Help for further guidance after orientation.

Table 7-1 Settings That Subscribers Can Change ¹

Settings That Can Be Changed by Using the Cisco Unity Assistant	Settings That Can Be Changed by Using the Phone Menus
Call Holding and Screening2 : •Select how Cisco Unity handles indirect calls when the subscriber phone is busy, including placing the caller on hold, prompting the caller to hold or leave a message, and sending the caller directly to the greeting •Select how Cisco Unity handles indirect calls, including telling the subscriber who the call is for, announcing that Cisco Unity is transferring the call, prompting the subscriber to accept or refuse a call, and prompting callers to say their names	Call Holding and Screening2: None
Call Transfers3 : •Transfer indirect calls to an extension or send to the greeting •Change extension	Call Transfers3: •Transfer indirect calls to an extension or send to the greeting •Change extension
Caller Options: •Allow callers to edit messages •Allow callers to mark messages urgent	Caller Options: None
Conversation Options: •Set speed and language for Cisco Unity prompts •Select full or brief Cisco Unity conversation menus •Select the action that Cisco Unity performs when the subscriber calls Cisco Unity, including greeting the subscriber by name and announcing the number of new messages by type •Specify alternative extensions	Conversation Options: Select full or brief Cisco Unity conversation menus
Greetings: •Record a personal greeting •Enable or disable greeting •Specify an expiration date for an enabled greeting •Switch between system prompt and personal greeting	Greetings: •Record a personal greeting •Enable or disable greeting •Specify an expiration date for an enabled greeting
Message Notification: •Enable or disable a notification device, and change its number •Specify dialing options •Select the types of messages and message urgency for which Cisco Unity will call a device •Set up a notification schedule, and specify what happens when a device does not answer, is busy, or fails	Message Notification: Enable or disable a notification device, and change its number
Message Playback: •Specify message playback order •Change the time format used for message time stamps •Select the action that Cisco Unity performs when messages are played, including announcing the name and number of the sender who left a message, whether the timestamp is played before or after the message, and the volume level at which messages are played •Specify whether Cisco Unity plays the Message Type menu	Message Playback: Speed and volume of message as it is played
Message Addressing: •Switch between addressing messages to other subscribers by name, or by extension •Specify order for addressing messages by name (last name followed by first name, or vice versa)	Message Addressing: Switch between addressing to other subscribers by name or by extension (by pressing ##)4
Personal Settings: •Record a name •Specify a fax delivery number •Change directory listing status •Change password	Personal Settings: •Record a name •Specify fax delivery number •Change directory listing status •Change password
Private Lists: •Enter a display name •Record a list name •Add and delete members	Private Lists: •Record a list name •Add and delete members

1 The Conversation settings that subscribers can change are detailed in the "How Subscribers Can Customize the Cisco Unity Conversation" section on page 5-38. 2 Call holding and screening options apply only to incoming calls that were routed to the subscriber from the automated attendant or a directory handler, and not on direct calls. Holding and screening options do not apply when an outsider caller or another subscriber dials a subscriber extension directly. In addition, holding and screening options are only available when supervised transfers are enabled. 3 Call transfer options apply only to incoming calls that were routed to the subscriber from the automated attendant or a directory handler, and not on direct calls. Transfer options do not apply when an outsider caller or another subscriber dials a subscriber extension directly. 4 Note that this depends on whether you have enabled spelled name addressing. See the "Configuration Settings" section on page 26-2 for details.

Operator Orientation

Operator orientation should address the same points as subscriber orientation, but in greater detail. Operators must be familiar with how subscribers use Cisco Unity. Depending on the size of your organization, the operator may be the person subscribers are likely to ask when they have questions about Cisco Unity.

In addition to the items discussed in the "Subscriber Orientation" section and the "Support Desk Orientation" section (as applicable), operators also need to understand the following concepts and tasks:

Roles of the Operator and the Automated Attendant

The way your organization uses the automated attendant determines what the operator responsibilities are. The automated attendant is a call handler that is used in place of a human operator to answer and direct calls by playing greetings and responding to touchtones. The automated attendant can provide a menu of options (for example, "For Sales, press 1; for Service, press 2."), and it can also provide information (for example, "Our normal business hours are Monday through Friday, 8 a.m. to 5 p.m.").

Directing Calls

Regardless of how your organization uses the automated attendant, many calls will go to the operator. The operator must know how to direct calls to voice mail and to subscriber phones. To direct calls to voice mail, the operator can dial Cisco Unity and at the Opening Greeting, dial the subscriber extension and then press #2. The subscriber phone does not ring, and the transferred caller hears the subscriber greeting.

You can also create a call handler for each subscriber to send calls directly to their greetings. For details on setting this up, refer to the techtip, "How to Transfer a Caller Directly into a Mailbox," available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html.

Forwarding Unaddressed Messages to Intended Recipients

If an operator also owns a call handler or public distribution list, make sure that the operator knows to review unaddressed messages frequently, and to forward them to the intended recipient(s). See the "How Cisco Unity Handles Messages Without a Specific Recipient" section on page 4-5.

Using the Cisco Unity Greetings Administrator

An operator who is responsible for changing call handler greetings for the organization can use the Cisco Unity Greetings Administrator when is not practical to change a greeting in the Cisco Unity Administrator. For example, if the office is unexpectedly closed because of bad weather, the operator can call from home to use the Cisco Unity Greetings Administrator to enable the alternate Opening Greeting, or to rerecord a call handler greeting stating that the office is closed. For more information, see the "Using the Cisco Unity Greetings Administrator to Change Call Handler Greetings" section on page 19-5.

Using the Cisco Unity Broadcast Message Administrator

If an operator will be responsible for sending recorded announcements to everyone in an organization (or to particular location(s) within an organization), explain how to access and use the Cisco Unity Broadcast Message Administrator to send broadcast messages. In particular, make sure that those who are able to send system broadcast messages to subscribers on multiple servers understand the meaning of each addressing option offered by the Cisco Unity Broadcast Message Administrator and understand how to address a message to reach subscribers on a particular group of servers. See the "Sending System Broadcast Messages" section on page 5-5.

Support Desk Orientation

Support desk orientation should address the same points as subscriber and operator orientation, but in greater detail. Support desk staff must be familiar with how subscribers and operators use Cisco Unity, and the common problems that subscribers may encounter when using Cisco Unity. Instead of using the Cisco Unity server, it may be helpful to set up a test server that support desk staff can use to browse to the Cisco Unity Administrator, and troubleshoot and test client applications.

---

Caution Do not install Outlook on the Cisco Unity server, or Cisco Unity may not notify subscribers of new messages.

---

To prepare for possible calls to the support desk at your organization, familiarize the support desk staff with the resources listed below, and with the potential subscriber concerns and misconceptions listed in the section that follows.

Support Desk Resources

•Subscriber documentation is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html. In particular, support desk staff may find the Cisco Unity at a Glance documents helpful in gaining a high-level visual understanding of the flow of the Cisco Unity conversation.

•The Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

•The "Setting Up Cisco Unity Applications on Subscriber Workstations" chapter provides information on how subscriber workstations should be set up, and describes how subscribers use Cisco Unity client applications.

•The "Cisco Unity Conversation" chapter summarizes the ways in which Cisco Unity administrators and subscribers can customize the conversation.

•The Cisco Unity Troubleshooting Guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.

In particular, the following chapters may be helpful when addressing support requests from Cisco Unity subscribers:

–For information on specific error messages, refer to the "Error Messages" chapter.

–To learn about MWIs, refer to the "Message Waiting Indicators (MWIs)" chapter.

–When subscribers have problems accessing or using the Cisco PCA, the Media Master, or ViewMail, refer to the "Subscriber and Administrator Access" chapter.

–For problems with SMS message notifications, refer to the "Message Notification" chapter.

–Additional procedures for troubleshooting the Cisco PCA and its components (including the Media Master control bar) are presented in the "Cisco Personal Communications Assistant" chapter.

•For descriptions and the URLs of all Cisco Unity documentation on Cisco.com, refer to Cisco Unity Documentation Guide. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.html.

Potential Subscriber Concerns and Misconceptions

The following table describes potential subscriber issues, which are typically based on misconceptions about how Cisco Unity works. Subscribers who encounter such issues are often those who are accustomed to another voice messaging system, were recently migrated from a previous version or a different configuration of Cisco Unity, have not yet completed Cisco Unity training, or are unaware of a new feature or functionality change to their existing system.

Table 7-2 Potential Subscriber Concerns and Misconceptions 

Potential Issue	Description
Cisco PCA security alert s when using SSL	If your organization set up Cisco Unity to use SSL, but did not add it to the Group Policy in order to distribute the certificate to the trusted root store for all users in the domain (or did not tell subscribers how to add the certificate to the trusted root store on their own computers), subscribers may be concerned about the security alert that will be displayed each time that they access the Cisco PCA. Tell subscribers that they can ignore the warning and proceed to use the Cisco PCA without doing any harm to their computers or the network. (To prevent the browser from displaying the security alert, see the "Configuring Subscriber Browsers to Use the Cisco PCA" section on page 6-6.)
Delayed messages	Subscribers may believe that their messages are delayed for the following reasons: •While listening to new messages, subscribers may skip a message and inadvertently mark it new. Later, when they check messages again, they hear the skipped message and believe that the message arrived after a delay. •Subscribers may skip more messages than they intend while listening to their messages, and later check messages again only to hear one or more of the skipped messages, and believe that the message(s) arrived after a delay. See the "Skipping messages" section in this table. •When settings are changed for a subscriber in Exchange, the new values may not be reflected immediately in Cisco Unity. Explain to the subscriber that the settings may take a few minutes to synchronize, causing a delay in receipt of messages.
Deleted messages	By default, when subscribers delete a new or saved message, Cisco Unity does not ask them to confirm the deletion. You may want to enable Cisco Unity to request confirmation from subscribers before proceeding with the deletion, especially if many subscribers do not belong to a class of service (COS) that allows them to retain and review their deleted messages. For details on setting up this functionality, refer to the Advanced Settings tool Help. The setting is called Conversation—Confirm Delete When Deleting a New or Saved Message. For information on deleted messages, refer subscribers to the "Deleting Messages" chapter in the Cisco Unity User Guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html.
Directory listing: Subscribers are not listed as expected	When subscribers do not have a recorded voice name, they are not listed in the phone directory and as a result, callers are not be able to find them when searching for them by name. By default, Cisco Unity prompts subscribers to record a voice name during first-time enrollment, but it does not prevent them from completing the enrollment process if they do not. To address this issue, consider the following options: •You can change whether recording a voice name is required to complete first-time enrollment. Refer to the Advanced Settings tool Help (in the Unity Settings list, click Conversation—First-Time Enrollment: Require Subscribers to Record Names). The Advanced Settings tool is available in Tools Depot. •You can provide voice names for subscribers on individual Subscriber > Profile pages in the Cisco Unity Administrator. •Subscribers with class of service rights can record their own names by using the Cisco Unity conversation or the Cisco Unity Assistant.
Fax: Attached files are not delivered to fax machines (fax integrations only)	Subscribers may be unaware that when they add attachments to an e-mail message and then send the message to a fax machine, Cisco Unity renders only those attachments with the file extensions specified during Cisco Unity setup. All other attachments are removed. To determine which file name extensions are currently specified or to specify new ones, refer to the "A Subscriber Did Not Receive an Attached File Delivered to a Fax Machine" section in the "Third-Party Fax Integration" chapter in the Cisco Unity Troubleshooting Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.
Mailbox fills up quickly	Subscribers may complain that their mailboxes are filling up too quickly, for any the following reasons: •Cisco Unity does not automatically delete messages when they reach a certain age. This means that subscriber messages are saved until the subscriber deletes them permanently. (For information on how to permanently delete messages, refer subscribers to the "Deleting Messages" chapter in the Cisco Unity User Guide which is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html.) •When Cisco Unity is set up to provide Unified Messaging, the messages in the Sent and Deleted Items folders in Microsoft Outlook are included in the total mailbox size. •When Unified Messaging subscribers receive nondelivery receipts (NDRs) to messages that they send, their mailbox can quickly increase in size—especially if the original message included large attachments. If their e-mail clients are configured to save their sent messages, the original message and attachments are stored in their Sent Items folders and another copy is sent to their Inboxes along with the NDR, increasing their mailbox size accordingly. •Subscribers may receive messages that have been forwarded many times over, which increases message size. The original message plus all recorded or written introductions that were added during forwarding equal the total message size. As a result, subscribers who have relatively few messages stored in their mailboxes may still find that their mailboxes exceed the storage limits. •Subscriber mailboxes can fill up while subscribers are on vacation or on an extended leave of absence. To prevent this, specify that Cisco Unity will prevent callers from leaving messages when subscribers have their alternate greetings enabled. For details, see the "Subscriber Template Greetings Settings" section on page 10-15 or the "Subscriber Greetings Settings" section on page 14-19, as applicable. For information on how Cisco Unity handles full mailboxes, see the "How Cisco Unity Handles Full Mailboxes" section on page 4-3. For ways in which you and subscribers can manage subscriber mailbox size, refer to the "Best Practices for Managing Subscriber Mailbox Size" section in the "Configuring Cisco Unity for Maintenance Tasks" chapter of the Cisco Unity Maintenance Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.
Managing multiple message types (Unified Messaging configurations only)	Subscriber who are new to Unified Messaging sometimes have a difficult time understanding how to manage multiple message types from a single Inbox. For example, when subscribers check messages by phone, they may try to "clean up" their "voice mailbox" by deleting all of their e-mail messages. They are surprised and frustrated when they later discover that the messages have also been deleted from their Outlook Inboxes. Other subscribers may request that Cisco Unity stop delivering e-mail messages to their "voice mailbox" altogether. To help subscribers make the most of Unified Messaging, make sure that they understand how it works. For subscribers who like to manage voice mail and e-mail messages separately, remind them that they can turn on the Message Type menu so that they can pick which messages to hear by type ("Press 1 for voice messages, 2 for e-mails..."). Alternatively, subscribers can use the Cisco Unity Assistant to specify that Cisco Unity will play e-mail messages last when they check messages by phone. Finally, subscribers may want to create a folder in their e-mail client to store voice messages separately from other messages. Subscribers can also use the Copy to File option available from the Options menu on the Media Master to save voice messages as WAV files on their hard drives.
Message notification: Repeat notification options	When a subscriber chooses not to have Cisco Unity restart notification each time a new message arrives, setting a long interval between repeat notification calls may lead the subscriber to believe that Cisco Unity is delaying notification. For recommended interval settings, refer to the "Repeat Notification Option Is Misunderstood" section in the "Message Notification" chapter of the Cisco Unity Troubleshooting Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.
MWIs	To gain an understanding of when MWIs turn on and off, what causes them to turn on and off, and what causes MWIs to behave differently than expected, refer to the "Message Waiting Indicators (MWIs)" chapter in the Cisco Unity Troubleshooting Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.
Passwords are not secure, or subscribers use the wrong password	Subscribers may assume that their phone and Cisco PCA passwords are the same or are synchronized. As a result, they may think that they are changing both passwords when Cisco Unity prompts them to change their phone password during first-time enrollment. Additionally, and they may try to use their phone password to log on to the Cisco PCA.
Private secure messaging: limitations	To set user expectations for this feature, it is important to tell subscribers, administrators, and help desk staff about the following limitations of the private secure messaging feature: •The following message types cannot be sent as private secure voice messages: –Voice messages for Cisco Unity subscribers that are left by outside callers. –Voice messages for anyone who is not a Cisco Unity subscriber. –Voice messages recorded by using Cisco Unity ViewMail for Microsoft Outlook or the Cisco Unity Inbox, even when the phone is used as a recording device. •Private secure voice messages cannot be played: –By using ViewMail for Outlook or the Cisco Unity Inbox, even when the phone is used as a playback device. –As WAV file attachments by using media player software. •Replies to private secure messages are automatically marked private and secure if private secure messaging is enabled for the subscriber who is replying to the message. In addition, replies to ordinary private messages are automatically marked private and secure if private secure messaging is enabled for the subscriber who is replying to the message. •Private secure voice messages cannot be forwarded. •A forwarded message (with or without an introduction) cannot be marked private and secure. •The private keys that are required to play private secure voice messages are not specific to individual subscribers or workstations. If a private secure voice message is misrouted, either by a subscriber mistake or by a system problem, the voice message can be played by the receiving Cisco Unity subscriber, even if the subscriber is not the original intended recipient of the voice message, as long as a valid private key is present on the Cisco Unity server. •If you have set up private secure messaging for subscribers, they no longer have the option of sending ordinary private messages. •Cisco Unity subscribers cannot send private secure voice messages to Cisco Unity Bridge, AMIS, or VPIM subscribers. Messages sent to Bridge or VPIM subscribers are either decrypted and sent as ordinary private messages, or are undeliverable and will generate an NDR. Private secure messages sent to AMIS subscribers are undeliverable and will generate an NDR in all cases. Note that the Cisco Unity conversation does not inform subscribers that their private secure message will be decrypted during the message delivery process. •Private messages from Bridge and VPIM subscribers that are sent to Cisco Unity subscribers can be encrypted, but only at the point at which they reach the Voice Connector, if the delivery location is configured for this functionality. For more information about private secure messaging, including setup instructions, refer to the "Private Secure Messaging (Cisco Unity Version 4.0(5) and Later)" section in the "Securing Subscriber Messages" chapter of the Cisco Unity Security Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.
Skipping messages (Standard conversion style only)	If you upgraded from Cisco Unity version 4.0(3) or earlier, and/or you customized the Cisco Unity standard conversation so that subscribers can press a single # key during message playback instead of pressing ## to skip a message, you may find that some subscribers do not easily adopt the new key mapping. As a result, you may find that: •Subscribers continue to press ## during message playback, intending to skip a single message as they did before. Instead, they unwittingly skip two messages—the message being played and the subsequent message. As a result, subscribers may report that they are missing messages, that their messages are delayed, or that their MWIs remain lit even after they have listened to "all" of their new messages. •Subscribers continue to use the old shortcuts during message playback, and report that they do not work as expected. For example, subscribers may press #4 during message playback, and find that instead of Cisco Unity skipping the rest of the message and allowing them to reply to the message as before, now Cisco Unity skips the message and begins playing the next message more slowly than the skipped one. To change the standard conversation back to the default key mapping, see the "Changing How Subscribers Skip Messages During Message Playback (Standard Conversation)" section on page 5-23.
Speed for elements of the Cisco Unity conversation varies	Subscribers may report that the speed at which Cisco Unity plays menus, voice names, greetings, and messages is inconsistent. For example, subscribers may report that when they listen to their messages, the message is played at a different speed than the voice names of subscribers who leave them messages and the message properties (timestamp, message number, etc.). Such inconsistencies are expected when you consider the following statements: •Cisco Unity plays recorded voice names and greetings at the speed at which they were recorded. Neither you nor subscribers can affect the playback speed of voice names and greetings. •The speed that you or a subscriber specifies for system prompts—the standard recordings that come with the Cisco Unity system, including prompts for message properties—does not affect the playback speed of messages. •The speed that subscribers specify for message playback does not affect system prompts. For information on how to change speed for system prompts or subscriber messages, refer to the "Setting the Speed Level of System Prompts" section and the "Setting the Speed Level for Subscriber Messages" section in the "Audio Quality" chapter of the Cisco Unity Troubleshooting Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.
Unsent messages	Depending on how Cisco Unity is set up at your organization, subscribers may be surprised at how Cisco Unity handles messages when calls are intentionally or unintentionally disconnected (for example, when a subscriber hangs up or when a cell phone loses its charge or signal) while subscribers are in the process of sending, replying to, or forwarding a message. Some subscribers may incorrectly assume that Cisco Unity offers a "draft" folder for unsent messages, which is not the case. See the "How Cisco Unity Handles Messages That Are Interrupted by Disconnected Calls" section on page 4-7 for details.