-
Cisco Unity System Administration Guide (With Microsoft Exchange), Release 4.0(4)
-
Index
-
Preface
-
Introduction
-
Accessing the Cisco Unity Administrator
-
Using the Cisco Unity Administrator
-
Maintaining a Cisco Unity System
-
Manually Setting Up Cisco Unity to Use SSL
-
Default Accounts and Message Handling
-
Cisco Unity Conversation
-
Setting Up Client Applications
-
Preparing Subscribers, Operators, and Support Desk Personnel to Work with Cisco Unity
-
Enhanced Phone Security
-
Languages
-
Integrating a Fax Server with Cisco Unity
-
Subscriber Template Settings
-
Class of Service Settings
-
Creating Subscriber Accounts
-
Deleting Subscriber Accounts
-
Subscriber Settings
-
Hospitality and Property Management System Integration
-
Public Distribution List Settings
-
Account Policy Settings
-
Call Management
-
Call Handler Settings
-
Directory Handler Settings
-
Interview Handler Settings
-
Call Routing
-
Restriction Tables
-
Reports
-
Network Settings
-
System Settings
-
Glossary
-
Appendix A: Exiting and Starting the Cisco Unity Software and Server
-
Feedback
Table Of Contents
Setting Up Client Applications
Securing and Changing Cisco Unity Phone Passwords
Setting Up ViewMail for Microsoft Outlook
Deploying ViewMail for Outlook
Upgrading from an Earlier Version of ViewMail
Uninstalling ViewMail 2.4(6.x)
Customizing ViewMail for Optimal Performance
Understanding Cisco PCA Authentication and How to Secure Cisco PCA Passwords
How Authentication for the Cisco Personal Communications Assistant Works
Securing and Changing Cisco PCA Passwords
Defining Cisco PCA Logon, Password, and Lockout Policies
Setting Up the Cisco Personal Communications Assistant
How Subscribers Use the Cisco Personal Communications Assistant
Task List for Setting Up the Cisco Personal Communications Assistant
Configuring Subscriber Browsers to Use the Cisco PCA
Setting Up Subscriber Workstations So That Subscribers Can Use the Media Master
Determining Which Recording and Playback Devices Subscribers Will Use
What Happens When Subscribers Use the Phone as Their Recording and Playback Device
How Subscribers Specify Their Recording and Playback Device Preferences
Setting Up Text Message Notifications
SMS (SMPP) Message Notifications
Cisco Unity Inbox Message Notifications
Setting Up Client Applications
Overview: Client Applications
Cisco Unity subscribers can send and manage voice, fax, and e-mail messages by using a touchtone phone, or by using ViewMail for Microsoft Outlook. They can also send and manage voice and fax messages by using the Cisco Unity Inbox. In addition, the Cisco Unity Assistant lets subscribers personalize the Cisco Unity phone settings that control how they interact with Cisco Unity by phone.
This chapter reviews the preparations necessary for setting up subscriber phones and workstations so that subscribers can access and use Cisco Unity client applications. See the following sections for details:
•
Securing and Changing Cisco Unity Phone Passwords—This section summarizes how Cisco Unity phone passwords are assigned, secured, and changed.
•
•
•
•
•
•
Related Documentation
•
•
•
•
Securing and Changing Cisco Unity Phone Passwords
You can change the phone password for an individual subscriber on the Subscribers > Subscribers > Phone Password pages in the Cisco Unity Administrator at any time. Alternatively, you can use the Cisco Unity Bulk Import wizard to change the phone passwords for multiple subscribers at the same time. (Refer to the Cisco Unity Bulk Import Help for details.)
Each subscriber should be assigned a unique phone password. It is a good idea to specify a long—eight or more digits—and non-trivial password when you set subscriber phone passwords, and if you allow subscribers to change their own passwords, encourage them to do the same. For information on setting up the account policy that applies when subscribers access Cisco Unity by phone—including minimum phone password length, see the "Account Policy Settings" chapter.
When their accounts are configured to allow them to do so, subscribers can use the Cisco Unity phone conversation or the Cisco Unity Assistant to set their phone passwords. (See the "Subscriber Phone Password Settings" section on page 17-7 to set up subscriber accounts so that subscribers can change their own passwords.) Neither the Cisco Unity conversation nor the Cisco Unity Assistant require subscribers to enter their old phone passwords to reset them.
Subscriber template settings include an initial phone password for subscribers, which should have been changed either during installation or at the time that the subscriber accounts were created. See the "Phone Password Settings" section on page 13-6 for details. For suggestions on how to handle distributing initial phone passwords to subscribers, see the "Subscriber Orientation" section on page 9-1.
Note that AMIS, Bridge, Internet, and VPIM subscribers cannot log on to Cisco Unity by phone, use the Cisco Unity Assistant, or use the Cisco Unity Inbox.
Setting Up Subscriber Phones
As applicable, do the following tasks so that subscribers can access Cisco Unity by phone.
Set Up Cisco Unity to Handle Busy and Unanswered Calls
For each subscriber phone, enable call forwarding to Cisco Unity, so that busy and unanswered calls to the subscriber extension are transferred to Cisco Unity to handle. Cisco Unity then uses the call transfer settings for each subscriber to determine, for example, whether callers will be put on hold or sent directly to the subscriber greeting.
Specify a "Messages" Button
For each subscriber phone, enable the subscriber phone so that the subscriber can use a "Messages" button or a similar speed-dial button on the phone to dial the internal Cisco Unity phone number for your organization. This makes calling Cisco Unity to check messages or to change personal settings by phone quick and easy for the subscriber, as the subscriber does not have to dial the number for Cisco Unity from his or her desk phone.
Install TTY Prompts
A TTY prompt set, available in U.S. English (ENX) only, can be installed and used just like any other supported phone language. When the TTY prompt set is installed, subscribers and outside callers who use TTY can call Cisco Unity and use the same features that a hearing caller can use. However, note the following exceptions:
•
•
To install the TTY prompt set, see the "TTY Overview" section.
Setting Up ViewMail for Microsoft Outlook
By using ViewMail, Cisco Unity subscribers can send and manage voice, fax, and e-mail messages from their Outlook Inbox. Subscribers can use ViewMail to send voice messages to other subscribers, to non-Cisco Unity subscribers, and to public distribution lists. They can play and record voice messages by using the Media Master control bar, as depicted in Figure 8-1.
Figure 8-1 ViewMail for Microsoft Outlook
Note
ViewMail is not a licensed feature, nor does it require that you give subscribers special class of service (COS) privileges or passwords to use it. However, subscribers who use Outlook 98 with Window 2000 or Windows XP must have local administrative rights to their workstations in order to use ViewMail. (For more information, refer to caveat CSCeb51411. Bug Toolkit is available at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.)
Additionally, when a subscriber mailbox reaches the Prohibit Send And Receive limit in Exchange, ViewMail will not load when the subscriber starts Outlook because the ViewMail form cannot be published until the mailbox size is reduced.
To set up ViewMail for subscribers in your organization, see the following sections:
•
•
•
Deploying ViewMail for Outlook
You can install ViewMail for Outlook on subscriber workstations throughout your organization in a number of ways. Typically, organizations provide subscribers with network access to the ViewMail setup application so that they can set it up themselves.
Installation and deployment methods include:
•
•
Note
•
By default, ViewMail files are installed to the C:\Program Files\ViewMail directory. You can change this default, if desired. ViewMail installs and uses the following files and registry keys:
•
•
•
•
•
•
•
•
•
•
Extensions\ViewMail Extensions
1 Depending on the version of Windows, the files are installed in one of three directories: C:\Windows\System, C:\Winnt\System32, or C:\Windows\System32.
Use the following "To Install ViewMail from a Disc or from a Network Drive" procedure to install ViewMail on subscriber workstations. Before doing so, consider the following:
•
•
•
•
•
•
•
Caution
To Install ViewMail from a Disc or from a Network Drive
Step 1
Step 2
Step 3
Step 4
Note
Step 5
If you had previously installed ViewMail version 4.0(x), follow the on-screen prompts to remove it. When it is uninstalled, double-click the ViewMail.msi file again to install ViewMail.
Upgrading from an Earlier Version of ViewMail
When upgrading from an earlier version of ViewMail, consider the following:
•
•
•
•
Uninstalling ViewMail 2.4(6.x)
Any previously installed 2.4(6.x) version of ViewMail and the associated LightningFAX registry keys, if applicable, must be removed from client workstations before ViewMail is installed. The uninstall process removes ViewMail menu items and the ViewMail toolbar icon from the Outlook Inbox.
Note that the first time that the subscriber receives a voice message after ViewMail is uninstalled, the ViewMail icon identifies the message as a voice message. When the subscriber tries to open the message, Outlook displays a message informing the subscriber that the message form is not available. However, the error message does not prevent the subscriber from opening the message. Subsequent voice messages appear as e-mail with WAV attachments without the ViewMail icon, and no error message is displayed when the subscriber opens them.
To Remove ViewMail and Associated LightningFAX Registry Keys
Step 1
Step 2
Step 3
Step 4
Caution
Step 5
Step 6
•
CurrentVersion\App Management\ARPCache\LightningFAX 6.5 - PrintToMail.•
Monitors\LightningFAX.Step 7
Customizing ViewMail for Optimal Performance
When subscribers use ViewMail in a low bandwidth deployment (for example, with a slow modem or in a branch office), they should download messages before playing them for best performance and quality.
You can also customize ViewMail to reduce the amount of disk space needed for storing sent messages on subscriber workstations, so that it saves only the message headers for voice messages that subscribers send, and not the message recordings.
Use the following procedures to set up either of these options on subscriber workstations. Subscribers can also refer to the ViewMail Help or the Cisco Unity User Guide to set up these options on their own.
To Download Messages Before Playing Them
Step 1
Step 2
Step 3
Step 4
To Save Only Message Headers
Step 1
Step 2
Step 3
Step 4
Understanding Cisco PCA Authentication and How to Secure Cisco PCA Passwords
Cisco Unity offers application-level authentication to allow subscribers to access the Cisco Personal Communications Assistant (PCA). This means that IIS is configured so that the Cisco PCA uses Anonymous authentication, and therefore Cisco Unity authenticates the credentials that subscribers enter when they log on to the Cisco PCA. Note that unlike the Cisco Unity Administrator, you cannot change the authentication method used by the Cisco PCA.
Subscribers enter their Windows domain account user names and passwords to log on to the Cisco PCA. By default, when subscribers log on to the Cisco PCA, their user credentials are sent across the network to Cisco Unity in clear text. The information that a subscriber enters on the Cisco PCA pages is also not encrypted. For increased security, we recommend that you set up Cisco Unity to use the Secure Sockets Layer (SSL) protocol. See the "Manually Setting Up Cisco Unity to Use SSL" chapter for details.
As a best practice, we recommend that Cisco Unity administrators not use the same subscriber account to log on to the Cisco Unity Administrator that they use to log on to the Cisco PCA.
To learn more about Cisco PCA authentication and subscriber account policies, see the following sections:
•
•
•
How Authentication for the Cisco Personal Communications Assistant Works
1.
2.
3.
4.
5.
6.
7.
8.
If the Windows credentials cannot be authenticated, or if the subscriber account does not exist or does not have the proper COS rights, Cisco Unity presents a web page that indicates that the subscriber does not have permission to view the Cisco PCA website.
Securing and Changing Cisco PCA Passwords
You can change subscriber passwords by using Windows Active Directory for Users and Computers after you create subscriber accounts. Each subscriber should be assigned a unique Windows password. It is a good idea to specify a long—eight or more characters—and non-trivial password, and encourage subscribers to do the same. Subscribers cannot use the Cisco Unity phone conversation or the Cisco Unity Assistant to change their Cisco PCA passwords, nor can administrators change them in the Cisco Unity Administrator. Instead, subscribers can change their Cisco PCA passwords only in Windows by pressing Ctrl-Alt-Delete and then clicking Change Password. (If the Cisco Unity server is on a different domain than the one that subscribers typically access with their Windows passwords, subscribers will need to specify the domain name for the Cisco Unity server.)
Note
The initial password that subscribers use to access the Cisco PCA depends on how the subscriber accounts were created. See the "Password Settings for Cisco Unity Web Applications" section on page 13-6 for details.
Defining Cisco PCA Logon, Password, and Lockout Policies
The account policy that you specify on the Authentication page in the Cisco Unity Administrator determines how Cisco Unity handles situations when subscribers attempt to log on to the Cisco PCA and repeatedly enter incorrect passwords; whether subscribers can use blank passwords; the number of failed logon attempts that Cisco Unity allows before the subscriber account cannot be used to access the Cisco PCA; and the length of time that a user remains locked out. In addition, you can use the settings on the Authentication page to specify whether the Log On page for the Cisco PCA offers subscribers the following options:
•
•
•
When subscribers specify that Cisco Unity remember their user name, password, or domain, subscribers will not have to enter them the next time that they log on to the Cisco PCA. Instead, the fields are automatically populated in the Log On page.
Tip
To customize the logon, password, and lockout policies that Cisco Unity applies when subscribers use the Cisco PCA to access Cisco Unity, see the "Authentication Settings" section on page 29-12.
Setting Up the Cisco Personal Communications Assistant
See the following sections:
•
•
How Subscribers Use the Cisco Personal Communications Assistant
Subscribers use the Cisco Personal Communications Assistant (PCA) to access the Cisco Unity Assistant and the Cisco Unity Inbox. The Cisco Unity Assistant is a website that gives subscribers the ability to customize personal settings—including recorded greetings and message delivery options—on their workstations. The Cisco Unity Inbox website lets subscribers listen to, compose, reply to, forward, and delete voice messages, and with the fax option, manage fax messages. (The Cisco Unity Inbox is a licensed feature, and can be accessed only if it is purchased.)
Subscribers enter their Windows domain account user names and passwords to log on to the Cisco PCA. (Cisco PCA passwords are not related to Cisco Unity phone passwords, nor are they synchronized with them.)
The Cisco PCA is not a licensed feature, nor are subscribers required to have COS rights to access it. Any Cisco Unity subscriber can access the Cisco PCA at http://<Cisco Unity server>/ciscopca. (Note that the URL is case-sensitive.) However, subscribers do require proper COS rights to the Cisco Unity Assistant and/or the Cisco Unity Inbox.
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 the following ActiveAssistant URLs will be automatically redirected to the Cisco PCA website:
•
•
Likewise, subscribers who use http://<Cisco Unity server name>/web/vmi will also be automatically redirected to the Cisco PCA website.
Task List for Setting Up the Cisco Personal Communications Assistant
The Cisco PCA is installed on the Cisco Unity server during installation. To allow subscribers to access it, you do not need to install any additional files on subscriber workstations; however, you must complete the following tasks:
1.
2.
3.
4.
5.
Configuring Subscriber Browsers to Use the Cisco PCA
To allow subscribers to access the Cisco PCA, configure their browsers to:
•
•
•
•
•
Bookmarking Web Pages
When subscriber browser settings are set to cache temporary Internet pages automatically, subscribers can create a bookmark or Favorite to access a Cisco Unity Assistant or Cisco Unity Inbox web page, but the page will be read-only. Explain to subscribers that they should bookmark the Cisco PCA home page, rather than individual pages in the Cisco Unity Assistant and the Cisco Unity Inbox. (Subscribers should not change their browser settings as a workaround; when the browser is not set to automatically check for newer versions of temporary Internet files, the Media Master control is not displayed correctly.)
Managing Security Alerts When Using SSL Connections
If you set up Cisco Unity to use SSL, consider that the Cisco PCA website automatically uses an SSL connection every time that a subscriber points the browser to either website. However, until the digital certificate is added to the trusted root store on the subscriber workstation, the browser will display a message to alert the subscriber that the authenticity of the site cannot be verified, and therefore its content cannot be trusted.
To prevent the browser from displaying the security alert, you can distribute the certificate to the trusted root store for all users in the domain by adding it to the Group Policy, or you can tell subscribers how to add the certificate to the trusted root store on their own computers by providing them with the following "To Add the Cisco Unity Certificate to the Trusted Root Store on Subscriber Workstations" procedure. See the "Manually Setting Up Cisco Unity to Use SSL" chapter for additional details about SSL.
Depending on your organization, it may be a good idea to provide subscribers with the "To Add the Cisco Unity Certificate to the Trusted Root Store on Subscriber Workstations" procedure even if you distributed the certificate to the trusted root store for all users in the domain, as the browser will display the security alert any time that subscribers access the Cisco PCA from a workstation that does not belong to a trusted domain (for example, from a computer at home).
To Add the Cisco Unity Certificate to the Trusted Root Store on Subscriber Workstations
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Setting Up Subscriber Workstations So That Subscribers Can Use the Media Master
The Media Master control bar appears on each page of the Cisco Unity Assistant and the Cisco Unity Inbox where subscribers can make and play recordings—either by using the phone, or by using the computer microphone and speakers and clicking the Media Master controls.
Figure 8-2 Media Master Control Bar
The Media Master control bar relies on DCOM (Distributed Component Object Model), and does not work through a firewall that blocks DCOM communications. Keep this in mind when setting up subscribers for remote access. As an ActiveX control, subscribers must configure their browsers to download and run ActiveX controls, and they must have local administrative rights to their workstations in order for it to install properly. (When subscribers have local administrative rights to their workstations, the Media Master automatically installs the first time that subscribers open either a Cisco Unity Assistant or a Cisco Unity Inbox page that contains it. On subsequent visits to web pages that contain it, the Media Master is created from the locally installed copy.) Subscribers who do not have their browsers configured to download and run ActiveX controls or do not have the Media Master properly installed will see a red X instead of Figure 8-2.
Caution
To learn more about setting up subscriber workstations to use the Media Master, see the following sections:
•
•
•
Determining Which Recording and Playback Devices Subscribers Will Use
When determining the recording and playback devices that you want subscribers to use, consider the following:
•
•
•
What Happens When Subscribers Use the Phone as Their Recording and Playback Device
When subscribers use the phone as a recording and playback device in the Cisco Unity Administrator, the Cisco Unity Assistant, the Cisco Unity Inbox, or ViewMail, the following occurs:
a.
b.
c.
d.
When playing a recording, the subscriber answers the phone, and the client application asks Cisco Unity to play the message. Cisco Unity streams the recording over the phone.
Note that subscribers must manually change the server name field during failover and failback. Refer to the Cisco Unity Failover Configuration and Administration Guide for details. The guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/fail/fail401/ex/index.htm.
What Happens When Subscribers Use a Computer Microphone and Speakers as Their Recording and Playback Device
When subscribers use a computer microphone and speakers as a recording and playback device in the Cisco Unity Administrator, the Cisco Unity Assistant, the Cisco Unity Inbox, or ViewMail, the following occurs:
a.
b.
When playing a recording, Cisco Unity streams the message to the client application. Streaming occurs on demand, regardless of network traffic. The client application begins to play the message through the speakers as soon as a few seconds of the message are buffered in memory on the subscriber workstation.
How Subscribers Specify Their Recording and Playback Device Preferences
Subscribers can set their own recording and playback device preferences. For example, the Media Master Options menu allows subscribers to choose their own recording and playback devices. Media Master recording and playback settings are saved per user, per workstation. This means that:
•
•
•
Setting Up Text Message Notifications
Cisco Unity can send message notifications in the form of text messages to text pagers, text-compatible cell phones, and e-mail addresses. When a message arrives that matches the criteria selected in the message notification settings, the Cisco Unity Messaging System sends a text message entered by you or the subscriber, such as "Urgent message for Technical Support."
There are three types of text message notifications available with Cisco Unity. See the following sections for a summary of each type, and information on what you need to do before you can enable text message notifications for subscribers or offer them as options that subscribers can set up themselves in the Cisco Unity Assistant.
•
•
SMTP Message Notifications
By using SMTP, Cisco Unity can send text message notifications to text pagers that support SMTP when subscribers have received a new voice, e-mail, or fax message. Cisco Unity can also use SMTP to send a text message notification to an e-mail address. This is especially useful when subscribers use text-compatible cell phones or other devices that have been assigned an SMTP address by their wireless or mobile service provider.
In order for subscribers to receive SMTP message notifications from Cisco Unity, your site must have an SMTP gateway. When the gateway is set up, you can use the Text Pager 1 or Text Pager 2 options on the Subscribers > Subscribers > Message Notification page to enable Cisco Unity to send text message notifications by using SMTP. Alternatively, subscribers can enable the same devices on the Notification Devices page in the Cisco Unity Assistant.
Note that when a site without an SMTP gateway attempts to deliver text message notifications, the notification attempt fails and a nondelivery receipt (NDR) is sent to the Cisco Unity Messaging System and then routed, by default, to the Unaddressed Messages distribution list. (For more information, see the "How Cisco Unity Handles Messages Without a Specific Recipient" section.)
To enable SMTP message notifications for subscribers, see the "Subscriber Template Message Notification Settings" section on page 13-25 or the "Subscriber Message Notification Settings" section on page 17-26, as applicable. If the service provider that most subscribers use for their cell phones or other devices simply convert incoming SMTP message notifications to SMS messages, consider using SMS (SMPP) message notifications instead. The following "SMS (SMPP) Message Notifications" section details the advantages of using SMS messaging.
SMS (SMPP) Message Notifications
With the services and information provided by a wireless carrier, mobile messaging service provider or similar company, Cisco Unity can use the Short Message Peer-To-Peer (SMPP) protocol to send message notifications in the Short Message Service (SMS) format to GSM cell phones and other SMS-compatible devices when subscribers receive a new voice, e-mail, or fax message. SMS is a "store and forward service," which means that messages are not sent directly to the device used by the message recipient. Instead, an application like Cisco Unity—known as an External Short Message Entity (ESME)—submits a message to the SMS Center (SMSC). The SMSC then forwards the message to the device.
Advantages Over SMTP Message Notifications
An advantage of using SMS is that the subscriber device receives message notifications much faster than when using SMTP. The subscriber device does not have to be on the GSM network at the time that Cisco Unity sends the message to the SMSC, nor when the SMSC forwards it. The GSM network holds the SMS messages until the device is available; when the device is available, the delivery of the queued messages to the device takes just a few seconds. In addition, you can configure Cisco Unity so that each notification message replaces the previous one. Note that this functionality may not be supported by all mobile service providers.
SMS Message Length Limitations
An SMS message is a short text message. The acceptable message length for an SMS message varies depending on the service provider, the character set used to compose the message text, and the specific characters used in the message text. In general, you can use the following table to determine how long SMS messages can be:
7-bit
160 alphanumeric characters
8-bit
140 alphanumeric characters
16-bit
70 alphanumeric characters
Because Cisco Unity supports all three of the above character sets, the Cisco Unity Administrator and the Cisco Unity Assistant allow subscribers to enter up to 160 characters of message text. However, depending on the character set you configure Cisco Unity to use, messages that are shorter than 160 characters may be truncated. The text of the message and the message count (assuming subscribers choose to include the message count) constitute total message length.
Cost Considerations
When setting up SMS (SMPP) message notifications, consider that service providers typically charge for each SMS message or group of messages sent. Thus, the more SMS (SMPP) message notifications that Cisco Unity sends to subscriber devices, the higher the costs to your organization. For this reason, you may want to restrict the use of this feature to a group of subscribers (you can do so by assigning owners to the SMPP providers that you create on the System > SMPP Provider page), or you may want to ask subscribers to limit the number of message notifications that they receive by message type or urgency. For example, subscribers can specify in the Cisco Unity Assistant that Cisco Unity will send message notifications only when new voice messages arrive, or only when a new voice or urgent e-mail message arrives, and so on.
Tasks for Setting Up SMS (SMPP) Message Notification
To enable SMS (SMPP) message notifications for subscribers with SMS-compatible devices, do the following tasks:
1.
2.
For example, you will need to know the SMPP server name, TCP port, account name and password, and other similar information, as indicated in the documentation that your service provider gave you on setting up a messaging server to communicate with an SMSC. See the "SMPP Provider Settings" section on page 29-17 for additional details and procedures.
3.
4.
When you are ready to enable SMS (SMPP) message notifications for subscribers, see the "Subscriber Template Message Notification Settings" section on page 13-25 or the "Subscriber Message Notification Settings" section on page 17-26, as applicable. Subscribers can also set it up for themselves in the Cisco Unity Assistant.
Note that while neither the Cisco Unity Bulk Import wizard nor the Bulk Edit utility (available in Tools Depot) allow you to enable SMS (SMPP) message notifications, you can use the Bulk Edit utility to disable SMS (SMPP) notifications at any time for multiple subscribers at once. For logging and troubleshooting information, refer to the "SMS Notifications Are Not Working at All" section in the "Message Notification" chapter of the Cisco Unity Troubleshooting Guide. The Cisco Unity Troubleshooting Guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/tsg/tsg404/ex/index.htm.
Cisco Unity Inbox Message Notifications
You can also set up a text message notification so that subscribers receive an e-mail notification in their respective e-mail Inboxes when a new voice message arrives in their Cisco Unity Inbox. With Cisco Unity Inbox notifications, you can also enter the URL for the Cisco PCA on the System > Configuration page so that it is automatically included as a link in the body of the e-mail message that is sent to the subscriber. See the "Configuration Settings" section on page 29-2 for details.
Consider setting up Cisco Unity Inbox notifications for Voice Messaging subscribers who work remotely and have e-mail access. These subscribers rely on MWIs on their desk phones to tell them when a new message arrives when they are in the office. When they work remotely, they may appreciate the convenience of Cisco Unity Inbox notifications so that they do not need to call Cisco Unity periodically to check for new messages.
In order for subscribers to receive Cisco Unity Inbox message notifications, your site must have an SMTP gateway. When the gateway is set up, you can use the Text for VMI option on the Subscribers > Subscribers > Message Notification page to enable Cisco Unity Inbox message notifications for subscribers. Alternatively, subscribers can enable it on the Notification Devices page in the Cisco Unity Assistant.
Note that when a site without an SMTP gateway attempts to deliver text message notifications, the notification attempt fails and a nondelivery receipt (NDR) is sent to the Cisco Unity Messaging System and then routed, by default, to the Unaddressed Messages distribution list. (For more information, see the "How Cisco Unity Handles Messages Without a Specific Recipient" section.)
