-
Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(5)
-
Index
-
Preface
-
Networking in Cisco Unity
-
Digital Networking
-
Cross-Server Logon, Transfers, and Live Reply
-
SMTP Networking
-
AMIS Networking
-
Bridge Networking
-
VPIM Networking
-
Using VPIM for Networking with Cisco Unity Express or Other Cisco Unity Systems
-
Primary Location Settings
-
Upgrading and Uninstalling Networking Options
-
Migrating from SMTP Networking to VPIM Networking
-
Glossary
-
Feedback
Table Of Contents
SMTP Networking Option Will Not Be Supported Beyond the Cisco Unity 4.0(x) Train
Setting Up Cisco Unity to Use SMTP Networking
Task List: Setting Up Cisco Unity to Use SMTP Networking
Procedures: Setting Up Cisco Unity to Use SMTP Networking
Making Design Decisions and Gathering Needed Information
Verifying Connectivity Between the Exchange Servers
Resolving Names with IP Addresses
Setting Up the Voice Connector for SMTP Networking
Setting Up the Voice Connector for Exchange 5.5
Setting Up the Voice Connector for Exchange 2000
Customizing the Primary Location
Creating SMTP Delivery Locations
Creating Internet Subscriber Accounts
Before Creating Internet Subscriber Accounts
Using the Cisco Unity Bulk Import Wizard to Create Multiple Internet Subscriber Accounts
Using the Cisco Unity Administrator to Create Internet Subscriber Accounts
After Creating Internet Subscriber Accounts
SMTP Networking Concepts and Definitions
Voice Connector and SMTP Networking
Blind Addressing and SMTP Networking
Subscriber Experience with Blind Addressing
Internet Subscribers That Correspond to Remote Cisco Unity Subscribers
Subscriber Experience with Internet Subscribers
Determining How Internet Subscribers Appear in the Outlook Address Book
Preventing Contacts From Appearing in the Outlook Address Book
Modifying How Contacts Appear in the Outlook Address Book
Considerations for Networked Cisco Unity Servers
SMTP Delivery Location Profile Settings
Internet Subscribers Are Not Identified
Call Transfer Settings and Internet Subscribers
Running the Voice Connector Setup Program in Another Language
SMTP Networking
SMTP Networking Option Will Not Be Supported Beyond the Cisco Unity 4.0(x) Train
Earlier announcements indicated that SMTP Networking would not be supported in Cisco Unity 4.0(5) and later. After further consideration the decision was made to continue to support the SMTP Networking option in the 4.0(x) train because its replacement, VPIM Networking, is not supported in a pure Exchange 5.5 Cisco Unity deployment. Although SMTP Networking support is continuing, it is important to note that 4.0(x) is the last train that will support the option. We recommend that customers who need to network Cisco Unity servers that access separate directories migrate to VPIM Networking instead of using SMTP Networking.
Both SMTP Networking and VPIM Networking use SMTP as the mechanism for exchanging messages, but the message format differs. SMTP Networking uses a proprietary message format, while the message format in VPIM Networking adheres to the VPIM industry standard. In addition, VPIM Networking provides functionality that is not available in SMTP Networking. Cisco Unity 4.0(5) and later include enhancements to VPIM Networking that are not available with SMTP Networking.
To migrate from SMTP Networking to VPIM Networking, see the "Migrating from SMTP Networking to VPIM Networking" chapter.
Note that VPIM Networking is a licensed feature and is currently supported only with Exchange 2000 and Exchange 2003.
In addition to VPIM Networking, customers will still be able to set up Internet subscriber accounts for messaging with individuals who do not use Cisco Unity, but who have computers connected to the Internet.
Overview: SMTP Networking
With SMTP Networking, subscribers on the local Cisco Unity server can send voice messages to individuals who do not have mailboxes on the local Exchange network. Messages are sent over the Internet or any TCP/IP network. The recipients can be:
•
Subscribers on a different Cisco Unity server that accesses a directory other than the directory on the local Cisco Unity server. For installations with multiple Cisco Unity servers, this means that the Cisco Unity servers can be in one of the following configurations:
–
–
–
Note
•
Subscriber accounts created for use with SMTP Networking are called Internet subscriber accounts. SMTP Networking can be combined with Digital Networking or any of the other networking options. For example, if the Cisco Unity servers in your organization are networked together such that they access a common directory (and thus can make use of the Digital Networking option), you can still add Internet subscriber accounts for contractors working at home, and also set up an SMTP delivery location on one of the Cisco Unity servers for messaging with a field sales office where the Cisco Unity server accesses a separate directory.
No special permissions are required for SMTP Networking beyond those required for Cisco Unity itself. For detailed information about the permissions required by Cisco Unity, refer to the Permissions wizard Help, which is available in Tools Depot on the Cisco Unity server.
In this chapter, you will find procedures for setting up SMTP Networking, followed by detailed discussions of the concepts and terminology you need to understand. See the following sections:
•
•
•
•
•
Setting Up Cisco Unity to Use SMTP Networking
Prerequisites
Before starting the setup, verify that the following prerequisites have been met.
•
•
For installations with multiple Cisco Unity servers that access that same directory, you should first set up the servers for Digital Networking as described in the "Digital Networking" chapter before setting up SMTP Networking and/or creating Internet subscribers. After the Cisco Unity servers have been set up for Digital Networking, verify the following settings:
•
•
–
–
Task List: Setting Up Cisco Unity to Use SMTP Networking
Use this task list to set up SMTP Networking. If some or all of the remote message recipients use Cisco Unity, do these tasks on the local and on the remote systems. The cross-references take you to detailed procedures for the setup.
1.
2.
3.
4.
5.
6.
If some or all of the remote message recipients use Cisco Unity, create delivery location(s) on the local server that correspond to the remote Cisco Unity server(s). See the "Creating SMTP Delivery Locations" section.
7.
Procedures: Setting Up Cisco Unity to Use SMTP Networking
This section contains all of the procedures necessary to set up Cisco Unity for SMTP Networking.
Making Design Decisions and Gathering Needed Information
Before you begin setting up SMTP Networking, be sure to plan for the following, and gather the applicable information:
•
•
•
Verifying Connectivity Between the Exchange Servers
The processing of messages between the local and remote Cisco Unity servers occurs on the Exchange servers on which the Voice Connector is installed. Use the following procedures to verify that the Exchange servers have network and SMTP connectivity.
To Verify Network Connectivity Between the Exchange Servers
Step 1
Step 2
If you receive no reply, troubleshoot the network connectivity problem until the problem is resolved. Then continue with Step 3.
Step 3
If you received a reply when pinging the IP address in Step 2, but no replies when pinging the domain name and server name, see the "Resolving Names with IP Addresses" section. When the problem(s) are resolved, continue with Step 4.
Step 4
Step 5
To Verify SMTP Connectivity Between the Exchange Servers
Step 1
Step 2
Step 3
Step 4
If any of the telnet tests fails, there is a basic SMTP connectivity problem that must be resolved before proceeding with the SMTP Networking setup.
If the telnet tests succeeded, continue with the SMTP Networking setup. See the "Setting Up the Voice Connector for SMTP Networking" section.
Resolving Names with IP Addresses
Both Exchange servers require some mechanism for name resolution. While any method or combination of methods may be used, two common ways to accomplish name resolution are through Domain Name System (DNS), and by using HOSTS files.
If the Exchange servers are in a network that uses DNS, the servers should have a host address resource (A) record and mail exchange (MX) record in DNS. If the A and MX records for the servers have not already been added, do so now before continuing. Refer to the Microsoft Windows documentation for more information about adding A and MX records in DNS.
A HOSTS file is a text file that contains the mappings of IP addresses to host and domain names. The HOSTS file is located in the C:\WINNT\System32\Drivers\Etc directory. If either Exchange server is in a network that does not use DNS, you will need to edit the HOSTS file to add host and domain entries for the other Exchange server.
Whether using DNS or HOSTS files, you will need to know the fully-qualified domain name of each Exchange server on which the Voice Connector is installed. This is the name displayed in the Windows System Control Panel on the Network Identification tab in the Full Computer Name field.
If you made changes to DNS or HOSTS files, verify the network and SMTP connectivity again before continuing with the rest of the SMTP Networking setup. To verify connectivity, do the preceding "To Verify Network Connectivity Between the Exchange Servers" and "To Verify SMTP Connectivity Between the Exchange Servers" procedures.
Setting Up the Voice Connector for SMTP Networking
There are two Voice Connector installation programs included on Cisco Unity DVD 1 and CD 1, and separate setup procedures:
•
•
As applicable, see the "Setting Up the Voice Connector for Exchange 5.5" section or the "Setting Up the Voice Connector for Exchange 2000" section.
The Voice Connector installation program does not prompt with a choice of languages for the installation; it always installs in English. To run the Voice Connector installation program by using one of the localized versions (FRA, DEU, or JPN) instead of English, see the "Running the Voice Connector Setup Program in Another Language" section.
Setting Up the Voice Connector for Exchange 5.5
Install the Voice Connector on an Exchange 5.5 server that is in the same Exchange site as the Exchange partner server. Although the Voice Connector can be installed on the Cisco Unity server (when Exchange is also on the server), this is not recommended for performance reasons. Following are additional requirements:
•
•
•
–
–
–
–
–
To Install the Voice Connector for Exchange 5.5
As a best practice, back up the Exchange server before installing the Voice Connector.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Setting Up the Voice Connector for Exchange 2000
Install the Voice Connector on any Exchange 2000 or Exchange 2003 server that is not part of an Exchange cluster (Microsoft does not support third-party connectors on an Exchange cluster server). Although the Voice Connector can be installed on the Cisco Unity server (when Exchange is also on the server), this is not recommended for performance reasons.
If the Exchange server on which the Voice Connector will be installed is in a different routing group than the Exchange servers on which Cisco Unity subscribers are homed, routing group connectors must be configured between the routing groups.
The Voice Connector service is automatically configured to log on as the LocalSystem account. The account that the service logs on as should not be changed.
To Install the Voice Connector for Exchange 2000
Uninstall any previous versions of the Voice Connector. See the "Uninstalling the Cisco Unity Voice Connector" section.
As a best practice, back up the Exchange server before installing the Voice Connector.
Step 1
Step 2
Step 3
Step 4
If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.
Step 5
Step 6
Step 7
Step 8
Step 9
Note
To Determine if the Microsoft Windows 2000 Script Host Should Be Updated
Step 1
Step 2
Step 3
Step 4
Step 5
Customizing the Primary Location
You need to customize the primary location if you are configuring Cisco Unity for networking with another Cisco Unity server in another directory. If your organization has multiple Cisco Unity servers networked together via Digital Networking, the primary location must be configured on all of the networked servers as well. In particular, the SMTP Domain Name must be entered on the primary locations of all of the other networked Cisco Unity servers. Otherwise, SMTP Networking will not work for the subscribers on the other networked Cisco Unity servers.
If you only have one Cisco Unity server and are just creating Internet subscribers and not setting up SMTP Networking between Cisco Unity servers, customizing the primary location is optional (although as a best practice, it is recommended even in this circumstance).
See the "Primary Location Profile Settings" section for details about the settings.
To Customize the Primary Location
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Creating SMTP Delivery Locations
Do the following procedure if some or all of the remote message recipients use Cisco Unity. Create an SMTP delivery location on your local Cisco Unity server for each remote Cisco Unity server to which subscribers will send messages.
When multiple Cisco Unity servers are networked together such that they access a common directory, you need to create the SMTP delivery location(s) on only one Cisco Unity server in the network. The location data is stored in the directory and will replicate to the other Cisco Unity servers.
To Create SMTP Delivery Locations
Step 1
Step 2
Step 3
Step 4
See the "Guidelines for Assigning Dial IDs and Extensions" section for detailed information about choosing a Dial ID. The Dial ID that you enter here must match the Dial ID of the corresponding primary location on the remote Cisco Unity server.
Step 5
Step 6
Step 7
Step 8
Step 9
Creating Internet Subscriber Accounts
You can create Internet subscriber accounts by using the Cisco Unity Bulk Import wizard or the Cisco Unity Administrator. See the following sections:
•
•
•
•
Before Creating Internet Subscriber Accounts
This section lists—in order—the issues that you must consider before creating Internet subscriber accounts.
1.
If you are unsure whether the account that you are using has sufficient rights and permissions to create Internet subscribers, or whether Cisco Unity is properly configured to work with your message store, use the following procedure to run the SysCheck diagnostic tool.
To Check Cisco Unity Setup and Permissions by Using the Cisco Unity SysCheck Tool
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
a.
b.
c.
Step 8
2.
A class of service (COS) defines limits and permissions for subscribers who use Cisco Unity. For example, a COS dictates the maximum length of subscriber messages and greetings. Although most COS settings are not applicable to Internet subscribers, they still must be members of a COS. In the Cisco Unity Administrator, a COS is specified in each subscriber template; thus, a subscriber is assigned to the COS that is specified in the template upon which the Internet subscriber account is based. Cisco Unity includes predefined classes of service, which you can modify. You can also create new classes of service. For details, see the "Class of Service Settings" chapter in the Cisco Unity System Administration Guide.
3.
Each COS specifies a restriction table for call transfers, one for message notification, and one for fax deliveries. Cisco Unity applies the restriction table associated with the COS of a subscriber, and displays an error message if the phone number is not allowed. Cisco Unity comes with predefined restriction tables, which you can modify.
Although most restriction table settings do not apply to Internet subscribers because they cannot log on to Cisco Unity or use the Cisco Personal Communications Assistant (PCA), administrators can enter call transfer numbers for Internet subscribers. For security purposes, you should modify the restriction table used for transfers in the COS to which Internet subscribers belong, as necessary. For details, see the "Restriction Tables" chapter in the Cisco Unity System Administration Guide.
4.
Public distribution lists are used to send voice messages to multiple subscribers at the same time. Cisco Unity assigns new subscribers to the public distribution lists that are specified in the template on which the Internet subscriber account is based. For details, see the "Public Distribution List Settings" chapter in the Cisco Unity System Administration Guide.
5.
In the Cisco Unity Administrator, you can specify settings for a group of Internet subscribers by using a subscriber template. Subscriber templates contain settings that are applicable for subscribers of a particular type, such as a department. The settings from the template you choose are applied to Internet subscriber accounts as they are created. Cisco Unity comes with a default subscriber template, which you can modify, and you can create an unlimited number of additional templates. For more details, see the "Subscriber Template Settings" chapter in the Cisco Unity System Administration Guide.
Internet subscribers correspond to contacts in Active Directory and to custom recipients in Exchange 5.5. The contacts/custom recipients are listed in the address book for Microsoft Outlook (or other e-mail client), unless they are explicitly hidden. You may prefer that the associated contacts/custom recipients do not appear in the Outlook address book at all, or you may want to alter how contacts appear in the Outlook address book. See the "Determining How Internet Subscribers Appear in the Outlook Address Book" section for details.
Note
Using the Cisco Unity Bulk Import Wizard to Create Multiple Internet Subscriber Accounts
The Cisco Unity Bulk Import wizard allows you to create multiple Internet subscriber accounts at once by importing user data directly from the Exchange 5.5 directory or Active Directory, or by importing user data from a comma-separated value (CSV) file. CSV is a common text file format for moving data from one data store to another.
As long as the user data contained in the CSV file is formatted correctly, you can use it to create new contacts or custom recipients at the same time that you create Internet subscriber accounts. (If Cisco Unity uses an Exchange 2000 server as its partner server, a contact is created in Active Directory. If Cisco Unity uses an Exchange 5.5 server as its partner server, a custom recipient is created in the Exchange 5.5 directory.) Alternatively, the Cisco Unity Bulk Import wizard allows you to use a CSV file to create Internet subscriber accounts with existing contact or custom recipient data.
To create Internet subscriber accounts by importing user data directly from Exchange, see the "To Create Internet Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard" procedure. Otherwise, use the following procedure to prepare your CSV file. Refer to Cisco Unity Bulk Import wizard Help to find additional information about using the wizard to create Internet subscriber accounts, or about the required and optional column headers for your CSV file.
To Prepare a CSV File for Creating Internet Subscriber Accounts
Step 1
As a best practice, do not include more than 7,500 records in a single CSV file, as you may encounter unexpected results when the Cisco Unity Bulk Import wizard imports the data.
Step 2
Step 3
•
•
Step 4
For example, the columns of data in this sample are sorted so that the last name of the user is followed by the first name, and then by the remote address (the example data below varies whether you use the VOICE or the SMTP format):
Abade,Alex,VOICE:123_5678
Bader,Kelly,VOICE:123_4789
Campbell,Terry,VOICE:123_8521
Cho,Li,VOICE:123_3214Or
Abade,Alex,SMTP:aabade@cisco.com
Bader,Kelly,SMTP:kbader@cisco.com
Campbell,Terry,SMTP:tcampbell@cisco.com
Cho,Li,SMTP:lcho@cisco.com
Note
Step 5
LAST_NAME,FIRST_NAME,REMOTE_ADDRESS
Step 6
•
•
Step 7
Step 8
Step 9
Step 10
Note
To Create Internet Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard
Step 1
Step 2
To learn more about the options presented in the dialog boxes that appear as the wizard proceeds, click Help.
Step 3
Step 4
•
•
Step 5
Step 6
If you had no import errors, or if all errors have now been corrected, see the "After Creating Internet Subscriber Accounts" section.
Correcting Import Errors
The error log file contains data that the Cisco Unity Bulk Import wizard could not import. The Cisco Unity Bulk Import wizard reports the first error it detects in any user mailbox or row in a CSV file. Once you correct that error, the wizard may detect additional errors in the same mailbox or row when the data is imported again. Thus, you may need to repeat the correction process—running the Cisco Unity Bulk Import wizard and correcting an error—several times to find and correct all errors.
The output log file contains all the records that were not imported. You can save it as a CSV file, and use it when you run the Cisco Unity Bulk Import wizard again. Note that each time you run the Cisco Unity Bulk Import wizard, the error and output log files are overwritten (unless you specify new names for the files).
To correct import errors, use one of the following procedures: "To Correct Errors That Occurred When Importing Data from a CSV File," or "To Correct Errors That Occurred When Importing Data from the Message Store."
To Correct Errors That Occurred When Importing Data from a CSV File
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
To Correct Errors That Occurred When Importing Data from the Message Store
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Using the Cisco Unity Administrator to Create Internet Subscriber Accounts
By using the Cisco Unity Administrator, you can create an Internet subscriber account by adding a new account, or by importing existing account data for a user from Exchange. When you add a new Internet subscriber account, Cisco Unity creates a contact or custom recipient. (If Cisco Unity uses an Exchange 2000 server as its partner server, a contact is created in Active Directory. If Cisco Unity uses an Exchange 5.5 server as its partner server, a custom recipient is created in the Exchange 5.5 directory.)
To create an Internet subscriber account, do one of the following procedures: "To Create an Internet Subscriber Account by Adding a New Contact or Custom Recipient," or "To Create an Internet Subscriber Account by Importing Existing User Data."
To Create an Internet Subscriber Account by Adding a New Contact or Custom Recipient
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
To Create an Internet Subscriber Account by Importing Existing User Data
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
After Creating Internet Subscriber Accounts
After creating Internet subscriber accounts, consider the following:
•
•
When you want to modify settings for multiple subscribers at once, you can (re)run the Cisco Unity Bulk Import wizard. To learn more, see the Cisco Unity Bulk Import wizard Help.
•
SMTP Networking Concepts and Definitions
The following sections explain SMTP Networking concepts in detail:
•
•
•
•
•
Locations and SMTP Networking
The Cisco Unity objects called locations play a key role in messaging between Cisco Unity servers that access separate directories. Each Cisco Unity server is associated with a location referred to as the default or primary location, which is created during installation and which cannot be deleted. When setting up SMTP Networking, you give the primary location a new name and a Dial ID, enter a Domain Name, and customize other properties as applicable.
As Figure 4-1 illustrates, you create an SMTP delivery location on the local Cisco Unity server to correspond to each remote Cisco Unity server. The Dial ID and Domain Name that you enter on the delivery location must match the corresponding Dial ID and Domain Name for the primary location on the remote Cisco Unity server and vice versa. With the Dial IDs and Domain Names, Cisco Unity has the information it needs to exchange messages with remote Cisco Unity servers.
Figure 4-1 Relationship Between Primary and SMTP Delivery Locations
Voice Connector and SMTP Networking
Cisco Unity makes use of the standard Exchange SMTP Connector to provide messaging among Cisco Unity servers that access separate directories, and to individuals who do not use Cisco Unity. (In Exchange 5.5, the SMTP Connector is called the Internet Mail Service.) The SMTP Connector provides the ability to send and receive messages through the Internet to computers that support SMTP, which means that messages can be sent to both Exchange and non-Exchange mail servers.
The Cisco Unity Voice Connector allows Cisco Unity systems to send and receive SMTP mail while preserving the Cisco Unity-specific attributes in the voice messages. These attributes allow Cisco Unity to handle messages as voice messages. The Voice Connector is registered with Exchange to handle messages with the VOICE address type, so all messages to remote recipients must have VOICE in the address.
When a subscriber sends a voice message to someone at another location, the Voice Connector converts the voice message to MIME. The Exchange SMTP Connector can then send the message with all associated information.
On the receiving Cisco Unity server, because the message address type is VOICE, Exchange gives the message to the Voice Connector to handle. The Voice Connector converts the MIME message back to a voice message. When the message is delivered to the recipient Exchange mailbox, it is identified as a voice message, and Cisco Unity lights the MWI lamp on the recipient phone. The recipient can access the message just like any other voice message, by using the phone, Cisco Unity ViewMail for Microsoft Outlook, or the Cisco Unity Inbox.
There are two versions of the Voice Connector. The version that you use depends on your Exchange network:
•
•
Note
Caution
For more information about the SMTP Connector, refer to your Exchange documentation.
See the "Setting Up the Voice Connector for SMTP Networking" section for information about setting up the Voice Connector.
Message Addressing Options
Cisco Unity provides two methods for addressing messages to subscribers and to others who do not have mailboxes on the local Exchange network:
•
•
Blind Addressing and SMTP Networking
Blind addressing allows subscribers on the local Cisco Unity to send voice messages to subscribers on a remote Cisco Unity server even though the recipient extension, name, and recorded name are not in the directory. One of the steps to setting up blind addressing is to adjust the Blind Addressing setting on the Primary Location > Addressing Options page. You also create an SMTP delivery location that corresponds to each remote Cisco Unity server with which the local Cisco Unity server communicates.
When addressing a message with blind addressing, subscribers dial a number that consists of the Dial ID of the SMTP delivery location and the extension of the recipient on the remote Cisco Unity server. Note that the extension must be the primary extension for the recipient; alternate extensions do not work with blind addressing. Before addressing the message, Cisco Unity parses the number that the subscriber entered and searches for a matching delivery location. If Cisco Unity does not find a matching location, it reports the error to the sender and does not address the message. If a matching delivery location is found, Cisco Unity addresses the message without verifying that the remote extension exists. However, Cisco Unity does provide voice name confirmation that the delivery location exists before addressing the message (assuming a voice name was recorded for the delivery location).
For example, assume the primary and SMTP delivery locations have been set up as illustrated in Figure 4-1. A subscriber on the New York Cisco Unity server presses 3335067 on the phone to address a message to Chris Durand in Paris, whose extension is 5067. Cisco Unity searches the directory and finds that there is a delivery location with the Dial ID 333.
The 333 delivery location contains the domain name paris.cisco.com, so the Voice Connector constructs the To address SMTP:IMCEAVOICE-333_5067@paris.cisco.com. In order for Chris Durand to receive the message, the primary location on the Paris Cisco Unity server must have 333 as the Dial ID and paris.cisco.com as the Domain Name. Additionally, the primary extension for Chris must be 5067 (alternate extensions are not supported with blind addressing).
Note
Subscriber Experience with Blind Addressing
Because blind-addressed messages are sent and received as voice messages:
•
[VOICE:<Location Dial ID>_<Extension>]•
•
•
•
•
•
Because your Cisco Unity server does not have access to the names, extensions, recorded voice names and e-mail addresses of the subscribers at other locations, subscribers will encounter some limitations with blind addressing, as follows:
•
•
•
•
Internet Subscribers
Internet subscribers are a representation in Cisco Unity of users who do not have mailboxes on the local Exchange network. Instead, messages for Internet subscribers are sent to an e-mail address that you specify when you create the Internet subscriber account. Internet subscribers are created in Cisco Unity to enable Cisco Unity subscribers to find them in the directory and send messages as they would to any other subscriber. If the remote message recipients do not use Cisco Unity, they receive voice messages as e-mails with attached WAV files. If they use Cisco Unity, and the Voice Connector has been installed, they receive voice messages.
Internet subscribers are represented as custom recipients in Exchange 5.5 and as mail-enabled contacts in Active Directory. You create and manage Internet subscriber accounts in much the same way that you do regular subscriber accounts. For example, you can set call transfer settings for Internet subscribers.
Internet subscribers do not require additional Exchange client access licenses (CALs), and they do not consume Cisco Unity subscriber licenses. The Cisco Unity subscriber license count does not change when you create Internet subscribers.
Other than receiving messages (and possibly calls), Internet subscribers do not have access to other Cisco Unity features, and some sections of the Cisco Unity Administrator are disabled for Internet subscribers. Internet subscribers:
•
•
•
•
•
•
Internet Subscribers That Correspond to Remote Cisco Unity Subscribers
If your organization uses multiple Cisco Unity servers that access separate directories, you can create Internet subscriber accounts on the local server that correspond to subscribers on the remote Cisco Unity server(s). Similarly, the remote Cisco Unity server(s) can create Internet subscriber accounts that correspond to the subscribers on your local server.
In effect, you manually duplicate the subscriber directory of the remote Cisco Unity server on the local server, and vice versa. Such a setup provides the benefits listed in the "Subscriber Experience with Internet Subscribers" section. Additionally, because the messages are sent and received as voice messages:
•
•
•
•
•
Creating Internet subscriber accounts on both the local and remote servers avoids the limitations of blind addressing. You may decide to do this in the following circumstances:
•
•
•
Because of the administrative overhead of setting up and maintaining many Internet subscriber accounts, you may prefer a combination of blind addressing for most employees, and Internet subscriber accounts only for a few select subscribers. For example, you might want to set up Internet subscriber accounts for the senior sales staff of each location, but have other employees use blind addressing.
In order to set up Internet subscriber accounts that correspond to remote Cisco Unity subscribers, you need to create the applicable SMTP delivery locations (see Figure 4-2). When you create the Internet subscriber accounts, give them SMTP addresses in the following format:
VOICE:<Delivery Location Dial ID>_<Primary Extension>For example, if the SMTP address is VOICE:123_5678:
•
•
•
Note
Carefully consider the Dial IDs that you assign to primary and delivery locations. At any time after the Internet subscriber accounts have been created, if the Dial ID of a primary location is changed:
•
•
See Figure 4-2. In this example, on the New York Cisco Unity server, Kelly Bader addresses a message to Avery Hughes by dialing 1234. Cisco Unity does a directory lookup to obtain the address, and determines this is an Internet subscriber. The message is addressed to VOICE:333_1234 and is handed off to Exchange. Because of the VOICE address type, Exchange gives the message to the Voice Connector. The Voice Connector converts the message to MIME, and then searches for a delivery location 333. It finds the SMTP delivery location, and changes the To address to SMTP:IMCEAVOICE-333_1234@paris.cisco.com. It also changes the From address to SMTP:IMCEAVOICE-444_5678@ny.cisco.com. Then the Voice Connector sends the message back to Exchange, which sends it through the SMTP gateway.
On the receiving side, Exchange gives the message to the Voice Connector for processing. The Voice Connector converts the MIME message back to a voice message, and then searches for a subscriber with the primary extension 1234 associated with the primary location 333. It finds Avery Hughes, and changes the To address appropriately so that Exchange can deliver the message. The Voice Connector uses the From address and searches for a matching Internet subscriber. It finds the Internet subscriber Kelly Bader, and changes the From address appropriately so that Cisco Unity can play the recorded voice name when Avery listens to the message. The Voice Connector hands the message back to Exchange, and the voice message is delivered to Avery.
Figure 4-2 Internet Subscribers That Correspond to Remote Cisco Unity Subscribers
Deleting Internet Subscribers
Each Internet subscriber is associated with a directory object, which is either an Active Directory contact or an Exchange 5.5 custom recipient. When you delete Internet subscribers in the Cisco Unity Administrator, you are offered the option to delete the associated directory objects.
Subscriber Experience with Internet Subscribers
Provided that Internet subscribers have extensions, are listed in the phone directory, and have had voice names and greetings recorded for them:
•
•
•
•
•
•
Extensions are optional for Internet subscribers whereas they are mandatory for regular subscribers. If an extension has not been assigned to an Internet subscriber:
•
•
•
Determining How Internet Subscribers Appear in the Outlook Address Book
Note
To discourage people from inadvertently sending e-mail messages to Internet subscribers, you can prevent the associated contact (or custom recipient) from appearing in the Outlook address book. Alternatively, you can change how the display name for the contact appears in the Outlook address book so that subscribers can distinguish the contact from a user account. In this way, you can reduce the number of e-mail messages inadvertently sent to contacts and simplify addressing for those who send voice messages to Internet subscribers at the same time.
If you prefer that the associated contacts for subscribers do not appear in the Outlook address book at all, see the "Preventing Contacts From Appearing in the Outlook Address Book" section.
Alternatively, if you want to alter how contacts appear in the Outlook address book, see the "Modifying How Contacts Appear in the Outlook Address Book" section.
Preventing Contacts From Appearing in the Outlook Address Book
Either before or after you create Internet subscriber accounts, you can prevent the associated contact (or custom recipient) from appearing in the Outlook address book by hiding the contacts from Exchange address lists. When you do so, Exchange will still deliver e-mail messages addressed to an existing user account (if one exists) and to the contact. However, the number of e-mail messages sent to the contact may be reduced because subscribers cannot inadvertently pick the contact from the Outlook address book when addressing messages to them.
The method by which you prevent subscribers from appearing in Outlook address books varies depending on your version of Exchange:
Cisco Unity with Exchange 5.5
To prevent subscribers from appearing in Outlook address books, you can use either the Cisco Unity Administrator, Bulk Edit, or Microsoft Exchange 5.5 Administrator:
•
•
•
Cisco Unity with Exchange 2003 or Exchange 2000
To prevent subscribers from appearing in Outlook address books, you can use the Cisco Unity Administrator, the Cisco Unity Bulk Import wizard, Bulk Edit, or Windows Active Directory for Users and Computers:
•
•
•
Modifying How Contacts Appear in the Outlook Address Book
As an alternative to preventing a contact (or custom recipient) from appearing in the Outlook address book altogether, you may want to alter the display name for the contact so that subscribers can distinguish the contact from the user account. For example, you could append " - Voice mail" to the display name of each Internet subscriber, and the names would appear in the Outlook address book as follows:
Abade, Alex
Abade, Alex - Voice mail
Bader, Kelly
Bader, Kelly - Voice mail
Campbell, Terry
Campbell, Terry - Voice mail
Cho, Li
Cho, Li - Voice mailIn this way, subscribers can easily determine which address is appropriate to use when they send voice messages to Internet subscribers. Additionally, when subscribers use the Outlook address book to address a message to a contact, they can be confident that the address is formatted correctly.
Considerations for Networked Cisco Unity Servers
A small subset of subscriber and distribution list data is stored in the directory, as is all location data. In organizations with multiple Cisco Unity servers networked together such that they access a common directory, the Cisco Unity-specific data replicates to all Cisco Unity servers in the network. Therefore, all Cisco Unity servers on the network have the information that subscribers need to address messages to a remote Cisco Unity server that is not on the network.
Because of directory replication, SMTP delivery locations and Internet subscriber accounts need to be created on only one Cisco Unity server in the network. If allowed by the primary location addressing options on each server, all subscribers, no matter which Cisco Unity server they are associated with, can send messages to an SMTP delivery location or to an Internet subscriber created on another server. The Cisco Unity server configured for SMTP Networking acts as the "bridgehead" server for the other Cisco Unity servers in the network.
SMTP Networking Reference
This section contains tables that define the fields in the Cisco Unity Administrator related to SMTP Networking setup, and briefly explains the options for correctly entering information in the fields.
SMTP Delivery Location Profile Settings
SMTP delivery locations are Cisco Unity objects that contain the addressing information that Cisco Unity needs to send messages to a remote Cisco Unity server that is on a separate network. You create an SMTP delivery location that corresponds to each remote Cisco Unity server with which the local Cisco Unity server will communicate.
Use the following tables to learn more about the delivery location profile settings for an SMTP location.
Notable Behavior
This section describes notable behavior of SMTP Networking and Internet subscribers.
•
•
•
Internet Subscribers Are Not Identified
When a person who has a corresponding Internet subscriber account calls a Cisco Unity subscriber and leaves a message, Cisco Unity does not identify the message as being from the Internet subscriber. In this case, when the phone system forwards the call to Cisco Unity, the message is handled as though it came from an unidentified caller. This means that:
•
•
•
Call Transfer Settings and Internet Subscribers
In installations with multiple Cisco Unity servers networked via Digital Networking, the number that Cisco Unity uses for call transfers to a subscriber is the only number replicated among the Cisco Unity servers; none of the other settings on the Subscriber > Call Transfer page in the Cisco Unity Administrator are replicated. For example, in Figure 4-3, call transfers are set to ring the subscriber at the number 9,5551212. The only call transfer setting that is replicated to other Cisco Unity servers is the call transfer number 9,5551212. If the setting was "Yes, ring subscriber's extension" instead, the number 3047 would be replicated.
Figure 4-3 Only the Call Transfer Number Is Replicated
When the call transfer setting is set to "No (send directly to subscriber's greeting)," the call transfer number is automatically set to the subscriber extension (3047 in the example above), which is replicated to the other networked Cisco Unity servers.
Call transfers to Internet subscribers created on other Cisco Unity servers are always handled by the phone system (release to switch)—rather than by Cisco Unity (supervised transfer)—even if the subscribers are set up for supervised transfers (as in the above example). The release to switch call transfers happen when:
•
•
On a release to switch transfer, Cisco Unity dials the call transfer number configured for the Internet subscriber and hangs up, leaving the phone system to handle the call. Note the following limitations with release to switch transfers:
•
•
Running the Voice Connector Setup Program in Another Language
The Voice Connector installation program does not prompt with a choice of languages for the installation; it always installs in English. To run the Voice Connector installation program by using one of the localized versions (FRA, DEU, or JPN) instead of English, do the following procedure.
To Run the Voice Connector Setup Program in Another Language
Step 1
Step 2
Step 3
Step 4
Step 5
Note
