Feedback
Table Of Contents
SMTP Networking (Cisco Unity 3.1(5) and Later)
Task List: Setting Up Cisco Unity to Use SMTP Networking
Procedures for 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
Setting the Addressing, Directory Handler, and Automated Attendant Search Scopes
Setting the Addressing Search Scope
Setting the Directory Handler Search Scope
Setting the Automated Attendant Search Scope
Creating SMTP Delivery Locations
Creating Internet Subscriber Accounts
Before Creating Subscriber Accounts
Using the Cisco Unity Import Utility to Create Multiple Subscriber Accounts
Using the Cisco Unity Administrator to Create Internet Subscriber Accounts
After Creating 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
Unidentified Callers and Internet Subscribers
Path of Voice Messages to a Remote Cisco Unity Server
Considerations for Networked Cisco Unity Servers
SMTP Delivery Location Profile Settings
Leaving a Message Versus Sending a Message
Extension Address Utility (Cisco Unity 2.4(6) - 3.0(4) Only)
Version Requirements for SMTP Networking
SMTP Networking (Cisco Unity 3.1(5) and Later)
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.
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:
•
•
•
•
•
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.
7.
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.
8.
Procedures for 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 procedures "To Verify Network Connectivity Between the Exchange Servers" and "To Verify SMTP Connectivity Between the Exchange Servers."
Setting Up the Voice Connector for SMTP Networking
There are two Voice Connector installation programs included on Cisco Unity Disc 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.
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 Cisco Unity. Although the Voice Connector can be installed on the Cisco Unity server (if Exchange 5.5 is also on the server), this is not recommended for performance reasons. Following are additional requirements:
•
•
•
–
–
–
–
–
For installations running Cisco Unity 3.1(6), skip to the "To Install the Voice Connector for Exchange 5.5" section.
Caution
To Download the Voice Connector for Exchange 5.5 (Cisco Unity 3.1(5) Only)
Step 1
Step 2
Step 3
Step 4
Step 5
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 an Exchange 2000 server. If the Exchange 2000 and Cisco Unity servers are in different routing groups, a routing group connector must be installed. Although the Voice Connector can be installed on the Cisco Unity server (if Exchange 2000 is also on the server), this is not recommended for performance reasons.
Do not install the Voice Connector on a server in an Exchange cluster. Microsoft does not support third-party connectors on an Exchange cluster server.
For installations running Cisco Unity 3.1(6), skip to the "To Install the Voice Connector for Exchange 2000" section.
Caution
To Download the Voice Connector for Exchange 2000 (Cisco Unity 3.1(5) Only)
Step 1
Step 2
Step 3
Step 4
Step 5
To Install the Voice Connector for Exchange 2000
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
Step 10
Note
To Determine if the Microsoft Windows 2000 Script Host Should Be Updated
Step 1
Step 2
Step 3
Step 4
Step 5
To update the Windows Script Host, go to the downloads page on the Microsoft website, and do a keyword search for Windows Script Host. Follow the installation instructions.
Customizing the Primary Location
Carefully consider the Dial ID that you will assign to the primary location, particularly if your organization has multiple Cisco Unity servers networked together. See the "Guidelines for Assigning Dial IDs and Extensions" section on page 6-2 for detailed information about choosing a Dial ID. If some or all of the remote message recipients use Cisco Unity, the Dial ID entered here must match the Dial ID for the corresponding SMTP delivery location on the remote Cisco Unity server.
If none of the Internet subscribers use Cisco Unity, customizing the primary location is optional (although as a best practice, it is recommended even in this circumstance).
To Customize the Primary Location
Step 1
Step 2
Step 3
Step 4
Step 5
•
•
Note
The time that it takes for the primary location data from other Cisco Unity servers to be reflected on the local server depends on your network configuration and replication schedule.
Step 6
Step 7
Note
Setting the Addressing, Directory Handler, and Automated Attendant Search Scopes
In installations with multiple Cisco Unity servers networked together such that they access a common directory, set the addressing and directory handler search options on all Cisco Unity servers, not just those that you are setting up for SMTP Networking.
Do the following procedures to set up the addressing, directory handler, and automated attendant search scopes.
•
•
•
Setting the Addressing Search Scope
For detailed information about the addressing search options, see the "Primary Location Addressing Option Settings" section on page 6-6.
To Set the Addressing Search Scope
Step 1
•
•
Step 2
Step 3
Setting the Directory Handler Search Scope
For detailed information refer to the "Directory Handler Search Options Settings" section in the "Directory Handler Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)
To Set the Directory Handler Search Scope
Step 1
Step 2
Step 3
Setting the Automated Attendant Search Scope
By default, outside callers who reach the opening greeting for your organization can be transferred only to subscribers associated with the local Cisco Unity server. If you want to set up the automated attendant so that callers can be transferred to subscribers associated with other Cisco Unity servers in the same dialing domain, change a registry setting as described in the following procedure.
Note
To Set the Automated Attendant Search Scope
Step 1
Step 2
Step 3
Step 4
Step 5
You do not need to restart Cisco Unity to enable the change.
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 on page 6-2 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 Import utility or the Cisco Unity Administrator. See the following sections:
•
•
•
•
Before Creating Subscriber Accounts
This section lists—in order—the issues that you must consider before creating subscriber accounts.
1.
If you are unsure whether the account that you are using has sufficient rights and permissions to create 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 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, refer to 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 ActiveAssistant, 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, refer to 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 subscriber account is based. For details, refer to 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 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 subscriber accounts as the accounts 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, refer to the "Subscriber Template Settings" chapter in the Cisco Unity System Administration Guide.
Note
Using the Cisco Unity Import Utility to Create Multiple Subscriber Accounts
The Cisco Unity Import utility allows you to create multiple Internet subscriber accounts at once 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, new contacts or custom recipients are created when Cisco Unity creates the 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.)
To Prepare a CSV File for Creating Internet Subscriber Accounts
Step 1
As a best practice, do not include more than 2,500 records in a single CSV file.
Step 2
•
•
Step 3
Step 4
LAST_NAME, FIRST_NAME, DTMF_ACCESS_ID, SUBSCRIBER_TYPE, REMOTE_ADDRESS
Note the following:
•
•
•
Step 5
•
•
Step 6
Extensions are optional for Internet subscribers, so this column does not have to contain any data even though the column header is required in the CSV file. If the Internet subscriber does not have an extension, enter a comma in the column.
Step 7
When importing information for regular and Internet subscribers, use a separate CSV file for each type of subscriber. Mixing the subscriber types in one CSV file produces erroneous results such as regular subscribers being imported as Internet subscribers.
Step 8
•
•
VOICE:<Delivery Location Dial ID>_<Remote Primary Extension>
For example:
LAST_NAME, FIRST_NAME, DTMF_ACCESS_ID, SUBSCRIBER_TYPE, REMOTE_ADDRESS
Abade, Alex, 3401, 2, VOICE:123_5678
Bader, Kelly, 3403, 2, VOICE:123_4789
Campbell, Terry, 3404, 2, VOICE:123_8521
Cho, Li, 3405,2, VOICE:123_3214Or
Abade, Alex, 3401, 2, SMTP:aabade@cisco.com
Bader, Kelly, 3402, 2, SMTP:kbader@cisco.com
Campbell, Terry, 3403, 2, SMTP:tcampbell@cisco.com
Cho, Li, 3404, 2, SMTP:lcho@cisco.comStep 9
Step 10
Step 11
Step 12
To Create Internet Subscriber Accounts by Using the Cisco Unity Import Utility
Step 1
Step 2
To learn more about the options presented in the dialog boxes that appear as the utility proceeds, click Help.
Step 3
If you had no import errors, or if all errors have now been corrected, see the "After Creating Subscriber Accounts" section.
Correcting CSV Import Errors
The error log file contains data that the Import utility could not import because of CSV file errors. The Import utility reports the first error it detects in any row in a CSV file. Once you correct that error, the Import utility may detect additional errors in the same row when the data is imported again. You may need to repeat the process—running the Import utility and correcting an error—several times to find and correct all errors.
The first column of the error log file, titled NOTES, provides an error code that describes the error found in a record. The second column of the error log file (also titled NOTES) lists the column number in which the error can be found. Data columns are numbered sequentially beginning with one. You will also see the word ERROR next to the data item that contains the error.
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 Import utility again. Note that each time you run the Import utility, the error and output log files are overwritten (unless you specify new names for the files).
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
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, depending on the type of subscriber accounts that you want to create.
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
•
•
VOICE:<Delivery Location Dial ID>_<Remote Primary Extension>
For example: VOICE:123_5678
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 Subscriber Accounts
After creating Internet subscriber accounts, consider the following:
•
•
•
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 3-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 for 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 3-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, ViewMail for Microsoft Outlook, or the Cisco Unity Visual Messaging Interface.
There are two versions of the Voice Connector. The version that you use depends on your Exchange network:
•
•
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 3-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>]–
[VOICE:<Location Dial ID>_<Extension>]@<Domain name>.com•
•
•
•
•
•
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.
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 3-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 3-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 3-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, the underlying directory objects are not removed; you must delete them manually by using Microsoft Active Directory Users and Computers or Microsoft Exchange 5.5 System Administrator.
Caution
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:
•
•
•
•
•
•
Note
Extensions are optional for Internet subscribers whereas they are mandatory for regular subscribers. If an extension has not been assigned to an Internet subscriber:
•
•
•
Unidentified Callers and Internet Subscribers
Internet subscribers can be listed in the phone directory, and they have recorded voice names and greetings just like regular Cisco Unity subscribers. If you have used Cisco Unity to set up an automated attendant, callers who reach the opening greeting can enter the extension of an Internet subscriber, and callers who reach the phone directory can look up the extension of an Internet subscriber.
You configure call transfer settings for Internet subscribers in the Cisco Unity Administrator just as you do for regular Cisco Unity subscribers, and the behavior is the same. If you allow calls to Internet subscribers to be transferred to the phone system, note the following:
•
•
Path of Voice Messages to a Remote Cisco Unity Server
Whether a subscriber uses blind addressing, or addresses a message to an Internet subscriber on the local server that corresponds to a subscriber on a remote Cisco Unity server, the path of the message is similar:
1.
2.
–
–
In both cases, Cisco Unity forms an address in the following format and gives the message to Exchange:
VOICE:<Delivery Location Dial ID>_<Extension>3.
4.
SMTP:IMCEAVOICE-<Delivery Location Dial ID>_<Extension>@<Domain Name>5.
SMTP:IMCEAVOICE-<Primary Location Dial ID>_<Extension>@<Domain Name>If the message was from an unidentified caller to an Internet subscriber, the From message is constructed in the following format:
SMTP:IMCEAVOICE-<Primary Location Dial ID>_unknown@<Domain Name>6.
7.
8.
9.
10.
11.
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. See the following sections for more information:
•
•
Leaving a Message Versus Sending a Message
When a person who has a corresponding Internet subscriber account on the local Cisco Unity server calls a local 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:
•
•
•
However, when the person with the Internet subscriber account records and sends a message to a local Cisco Unity subscriber, Cisco Unity can identify the message as being from the Internet subscriber. In this case, the phone system is not involved and the recipient phone does not ring. Instead, the message is sent via SMTP to Exchange in the local site, which delivers the message to the recipient. Thus, when the recipient listens to the message, Cisco Unity plays the recorded name of the Internet subscriber, and allows the recipient to record a reply.
Extension Address Utility (Cisco Unity 2.4(6) - 3.0(4) Only)
To set up blind addressing in Cisco Unity 2.4(6) through 3.0(4), you must generate extension addresses for the Cisco Unity subscribers. An extension address is an address formed by combining the delivery location Dial ID, extension, and domain name. Cisco Unity provides the Extension Address utility to generate extension addresses. When you run the Extension Address utility, it forms addresses for each subscriber in the following format:
SMTP:<Dial ID>_<Extension>@<Domain Name>.
VOICE:<Dial ID>_<Extension>@<Domain Name>.
The Extension Address utility creates extension addresses of type VOICE and of type SMTP, both of which are required for SMTP blind addressing to work. Note that the utility uses the Dial ID and Domain Name from the primary location, so before you use the Extension Address utility, you must customize the primary location.
After the Voice Connector is installed, Cisco Unity automatically generates extension addresses when you add new subscribers. Therefore, you only need to use the Extension Address utility to generate extension addresses for subscriber accounts that existed before the Voice Connector was installed. However, if you modify the primary location Dial ID or domain name after generating extension addresses, you need to run the Extension Address utility again to generate new extension addresses. (You may also need to run the Extension Address utility if you change subscriber extensions. You can view the extension addresses for Cisco Unity subscribers in the Exchange 5.5 Administrator to determine if you need to run the Extension Address utility after changing a subscriber extension.)
Beginning with Cisco Unity 3.1(5), with Voice Connector 10.0(1), extension addresses are no longer needed for blind addressing. Therefore, Cisco Unity 3.1(5) no longer automatically generates extension addresses for Cisco Unity subscribers, and you do not need to run the Extension Address utility.
Version Requirements for SMTP Networking
To set up SMTP Networking on a Cisco Unity 3.1(5) system, you will need the Voice Connector version 10.0(1) or later (which is not the Voice Connector version that ships with Cisco Unity 3.1(5)). The Voice Connector is available on the Cisco Unity Voice Connector for Exchange Software Download page at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-voice-connector.
Note that Voice Connector version 10.0(1) is available with Cisco Unity 4.0(1). Voice Connector version 10.0(2) is available with Cisco Unity 4.0(2) and 3.1(6). In Cisco Unity 2.4(6) through 3.1(5), the Voice Connector version matched the version of Cisco Unity that the Voice Connector shipped with.
In a network consisting of Cisco Unity servers running version 3.1(2) or later, the Cisco Unity bridgehead server set up for SMTP Networking must be version 3.1(5) or later.
Support for SMTP Networking prior to 3.1(5) depends on the version. Table 3 lists the version combinations of the Cisco Unity bridgehead server and the Voice Connector that are supported for SMTP Networking.
Table 3 Version Requirements for SMTP Networking
Bridgehead Server
for Exchange 2000
for Exchange 5.53.1(6)
10.0(2), 10.0(1)
10.0(2), 10.0(1)
3.1(5)1
10.0(2), 10.0(1)
10.0(2), 10.0(1)
3.1(4)
Not supported
Not supported
3.1(3)
Not supported
Not supported
3.1(2)
Not supported
Not supported
3.1(1)
Not supported
Not supported
3.0(4)
Not supported
3.0(4)
3.0(3)
Not supported
3.0(3)
3.0(2)
Not supported
3.0(2)
3.0(1)
Not supported
3.0(1)
2.4(6)
Not supported
2.4(6)
1 Cisco Unity 3.1(5) does not ship with the needed Voice Connector version. For SMTP Networking with Cisco Unity 3.1(5), you must download the Voice Connector version 10.0(1) or later from http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-voice-connector.
