Table Of Contents
SMTP Networking
Overview: SMTP Networking
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 Search Options
Creating SMTP Delivery Locations
Creating Internet Subscriber Accounts
Before Creating Subscriber Accounts
Using the Cisco Unity Bulk Import Wizard To Create Multiple Subscriber Accounts
Correcting CSV Import Errors
Using the Cisco Unity Administrator To Create Internet Subscriber Accounts
After Creating Subscriber Accounts
SMTP Networking Concepts and Definitions
Locations and SMTP Networking
Voice Connector and SMTP Networking
Message Addressing Options
Blind Addressing and SMTP Networking
Subscriber Experience with Blind Addressing
Internet Subscribers
Subscriber Experience with Internet Subscribers
Internet Subscribers that Correspond to Remote Cisco Unity Subscribers
Path of Voice Messages to a Remote Cisco Unity Server
Considerations for Networked Cisco Unity Servers
SMTP Networking Reference
SMTP Delivery Location Profile Settings
SMTP Networking
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 Cisco Unity server that accesses a directory different from the local Cisco Unity server. For installations with multiple Cisco Unity servers, this means that the Cisco Unity servers are in one of the following configurations:
–Separate Active Directory forests.
–Separate Exchange 5.5 organizations.
–Separate Exchange 5.5 sites in the same organization, but with no installation of Exchange 5.5 message and directory replication connectors (also called site connectors). (If site connectors are installed, you can use Digital Networking instead.)
•Individuals who do not use Cisco Unity or Exchange, but who have computers connected to the Internet.
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—This task list provides a high-level view of all of the tasks you need to complete, and the order in which they should be completed.
•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.
•SMTP Networking Concepts and Definitions—This section explains SMTP Networking concepts in detail. You may want to read this section prior to completing the setup procedures.
•SMTP Networking Reference—This section contains tables that define the fields in the Cisco Unity Administrator related to SMTP Networking setup.
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. Make decisions about your dial plan and gather information needed to configure SMTP Networking. See the "Making Design Decisions and Gathering Needed Information" section.
2. If the network to which Cisco Unity is connected consists entirely of Exchange 5.5 servers, install the Exchange 5.5 Internet Mail Service (if it is not already installed). For performance reasons, you should install the Internet Mail Service on a server other than the Cisco Unity server. However, if necessary, it can be installed on the Cisco Unity server (if Exchange 5.5 is also on the Cisco Unity server). Refer to your Exchange documentation for more information.
3. Verify network and SMTP connectivity between Exchange servers in the local and remote sites. See the "Verifying Connectivity Between the Exchange Servers" section.
4. If some or all of the remote message recipients use Cisco Unity, install the Voice Connector. See the "Setting Up the Voice Connector for SMTP Networking" section.
5. Customize the primary location profile settings. See the "Customizing the Primary Location" section.
6. Set the addressing and directory handler search options. See the "Setting Search Options" section.
7. If none of the remote message recipients use Cisco Unity, skip to Step 8.
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. Create Internet Subscriber accounts on the local Cisco Unity server for every remote message recipient, as needed. See the "Creating Internet Subscriber Accounts" section.
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 appropriate information:
•Review your dial plan strategy to determine the numbers to assign to Dial IDs on the primary location and SMTP delivery location(s).
•Decide if you want subscribers to use blind addressing, or if you want to create Internet Subscribers.
•Decide on which Exchange servers (in both the local and remote location) to install the Voice Connector. Write down the server name, domain name, and the IP address of each Exchange server.
•You may want to record information on the Cisco Unity Customization Worksheets before entering the information in the Cisco Unity Administrator. The Cisco Unity Customization Worksheets are available on Cisco.com, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html. Enter information on the following worksheets:
–Primary Locations > Profile
–Primary Location > Addressing Options
–Call Management > Directory Handler > Search Options
–SMTP Delivery Location
–Subscriber Template settings, Subscriber COS settings, and Subscriber settings (if you will be creating Internet Subscriber accounts)
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 On the Exchange server on which the Voice Connector will be installed (Server 1), open a command prompt window.
Step 2 Enter ping <IP address> where <IP address> is the IP address of the remote Exchange server on which the Voice Connector will be installed (Server 2).
If you receive no reply, troubleshoot the network connectivity problem until the problem is resolved. Then continue with Step 3.
Step 3 Enter ping <domain name> where <domain name> is the domain name of Server 2. Then enter ping <server name> where <server name> is the name of Server 2.
If you receive a reply when pinging the IP address, 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 Repeat Step 2 and Step 3 on Server 2, entering the IP address, domain name, and server name of Server 1.
Step 5 When you successfully receive replies to all IP address, domain name, and server name pinging, thus verifying that you have basic network connectivity, continue with the next procedure, To verify SMTP Connectivity between the Exchange servers.
To verify SMTP Connectivity between the Exchange servers
Step 1 In a command prompt window on the Exchange server on which the Voice Connector will be installed (Server 1), enter telnet <server name> 25, where <server name> is the name of the remote Exchange server on which the Voice Connector will be installed (Server 2).
Step 2 If there is a response from the remote Exchange server, enter ehlo. The remote Exchange server should respond with a list of SMTP commands.
Step 3 If the telnet test was successful, enter quit to end the telnet session.
Step 4 Verify that SMTP connectivity works in the opposite direction by performing the above telnet tests on the remote Exchange server.
If any of the telnet tests failed, there is a basic SMTP connectivity problem that needs to be resolved before proceeding with the SMTP Networking setup.
If the telnet and ping tests succeeded, continue with the SMTP Networking setup. See the section "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 folder. 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 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.
•When Cisco Unity is connected to Exchange 5.5 (when your network consists only of Exchange 5.5 servers), set up the Voice Connector for Exchange 5.5.
•When Cisco Unity is connected to Exchange 2000 (when your network consists only of Exchange 2000 servers or a mixture of Exchange 2000 and Exchange 5.5 servers), set up the Voice Connector for Exchange 2000.
As appropriate, 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 SMTP Networking, the Voice Connector must be installed on the same Exchange server as the Exchange Internet Mail Service.
•Install only one instance of the Voice Connector in the Exchange site.
•If the Exchange server on which the Voice Connector will be installed is running Windows NT 4.0, the Microsoft Active Directory Services Client Extension (DSClient) for Windows NT 4.0 must be installed on the server prior to installing the Voice Connector. The DSClient requires Windows NT 4.0 Service Pack 6a. For information on downloading and installing the DSClient from the Microsoft website, refer to the following Microsoft Knowledge Base articles:
–Q288358—HOW TO: Install the Active Directory Client Extension
–Q295166—INFO: Advanced Installation of Directory Services Client for Windows NT 4.0
–Q295168—INFO: Files Installed by Directory Services Client Extension for Windows NT 4.0
–Q289105—INFO: Support for ADSI on Windows NT 4.0
–Q216290—INFO: Determining Which Version of ADSI Is Installed
If a prior version of the Voice Connector is installed, it will need to be uninstalled before continuing. How you uninstall the Voice Connector depends on the version that is installed. See "Upgrade and Uninstall Information" for more information. After uninstalling the existing Voice Connector, continue with the next procedure, To install the Voice Connector for Exchange 5.5.
To install the Voice Connector for Exchange 5.5
Step 1 Log on to the Exchange server on which you are installing the Voice Connector.
Step 2 As a best practice, backup the Exchange server before installing the Voice Connector.
Step 3 Disable any virus-scanning services on the Exchange server.
Step 4 Insert Cisco Unity Disc 1, and browse to the VoiceConnector-Ex55 folder.
Step 5 Double-click Setup.exe and then click Next.
Step 6 Enter the port number that Exchange uses for LDAP and then click Next.
To find the port number, open the Exchange Administrator, and under the Cisco Unity server container, browse to Configuration\Protocols\LDAP.
Step 7 In the Address Types dialog box, check Voice.
Step 8 Click Next twice.
Step 9 In the User Information dialog box, enter your Windows password and then click Next.
Step 10 When setup is complete, click Finish. The Voice Connector service starts automatically.
Step 11 Enable virus-scanning services on the server.
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.
If a prior version of the Voice Connector is installed, it will need to be uninstalled before continuing. How you uninstall the Voice Connector depends on the version that is installed. See "Upgrade and Uninstall Information" for more information. After uninstalling the existing Voice Connector, continue with the next procedure, To install the Voice Connector for Exchange 2000.
To install the Voice Connector for Exchange 2000
Step 1 Log on to the Exchange server on which you are installing the Voice Connector.
Step 2 As a best practice, backup the Exchange server before installing the Voice Connector.
Step 3 Disable any virus-scanning services on the Exchange server.
Step 4 Insert Cisco Unity Disc 1, and browse to the VoiceConnector-Ex2000 folder.
Step 5 Double-click Install.exe and then click Next.
Step 6 In the Address Types dialog box, check Voice.
Step 7 Click Next twice.
Step 8 In the User Information dialog box, enter your Windows password and then click Next.
Step 9 When setup is complete, click Finish to exit Setup and restart the server.
Step 10 Enable virus-scanning services on the server.
Note In order to view Voice Connector properties in Exchange System Manager, Microsoft Windows Script Host version 5.6 or later must be installed on the Exchange server. Continue with the next procedure, To determine if the Microsoft Windows 2000 Script Host should be updated. (Also note that if the Exchange server uses an earlier version of Windows Script Host, the Voice Connector will function properly, but you will not be able to view Voice Connector properties in the Exchange System Manager.)
To determine if the Microsoft Windows 2000 Script Host should be updated
Step 1 On the Exchange server on which the Voice Connector has been installed, browse to \winnt\system32.
Step 2 Right-click the file wshom.ocx, and select Properties.
Step 3 Click the Version tab.
Step 4 Click Product Version in the Item Name list to view the version in the Value box.
Step 5 If the version is earlier than 5.6, the Windows Script Host needs to be updated in order for the Voice Connector properties to be displayed in Exchange System Manager.
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 7-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.
To customize the primary location
Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Profile page.
Step 2 Enter a meaningful name for the location.
Step 3 Enter a Dial ID. The Dial ID identifies this location to Cisco Unity.
Step 4 Record a voice name for the location.
Step 5 Do one of the following:
•If the location does not belong to a dialing domain, click None.
•If the location does belong to a dialing domain, enter the Dialing Domain name only on one Cisco Unity server that is in the dialing domain, and wait for the name to replicate to the other Cisco Unity servers.
Note When setting up the primary location of the other Cisco Unity servers that are members of the dialing domain, select the Dialing Domain name from the list instead of entering a name.
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 Enter the SMTP Domain Name. This is the right half of an e-mail address after the @ symbol (for example, london.cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it. If some or all of the remote message recipients use Cisco Unity, the Domain Name entered here must match the Domain Name for the corresponding SMTP delivery location on the remote Cisco Unity server.
Step 7 Click the Save icon.
Note If your organization has multiple Cisco Unity servers networked together via Digital Networking, the primary location must be configured on those servers as well. In particular, the SMTP Domain Name must be entered on the primary locations of the other Cisco Unity servers. Otherwise, SMTP Networking will not work for the subscribers on the other Cisco Unity servers.
Setting Search Options
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.
To set search options
Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Addressing Options page and set the addressing options as needed.
•To allow subscribers created on the local Cisco Unity server to address messages to subscribers on other Cisco Unity servers (that access the same directory), select Dialing Domain or Global Directory, as appropriate.
•If you are using blind addressing to a Cisco Unity server in a separate directory, or to another voice messaging system, set the Blind Addressing Allowed Locations setting to something other than None, as appropriate.
Step 2 If you want locations included in address searches, check Include Locations in Searches. The location name is played only when a subscriber enters the location dial ID when addressing a message.
Step 3 Go to the Call Management > Directory Handlers > Search Options page, and modify the search options for an existing directory handler, or create a new directory handler for unidentified callers who use directory assistance.
To allow subscribers on other Cisco Unity servers to be located in directory assistance, select Dialing Domain. (The Cisco Unity servers must be in the same dialing domain as the local Cisco Unity server.)
Creating SMTP Delivery Locations
Do this 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 In the Cisco Unity Administrator, go to the Network > Delivery Locations > Profile page.
Step 2 Click the Add icon.
Step 3 Enter a meaningful name for the location.
Step 4 Enter the Dial ID, which identifies the location in Cisco Unity, and which subscribers use for blind addressing messages to recipients at this delivery location.
See the "Guidelines for Assigning Dial IDs and Extensions" section on page 7-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 Select SMTP as the Destination Type for the location.
Step 6 Click Add.
Step 7 Record a voice name for the location.
Step 8 Enter the Domain Name. This is the right half of an e-mail address after the @ symbol (for example, london.cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it. The Domain Name that you enter here must match the Domain Name of the corresponding primary location on the remote Cisco Unity server.
Step 9 Click the Save icon.
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 Subscriber Accounts
•Using the Cisco Unity Bulk Import Wizard To Create Multiple Subscriber Accounts
•Using the Cisco Unity Administrator To Create Internet Subscriber Accounts
•After Creating Subscriber Accounts
Before Creating Subscriber Accounts
This section lists—in order—the issues that you must consider before creating subscriber accounts.
1. Cisco Unity Configuration and Permissions
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 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.
Step 2 In the left pane of the Tools Depot window, in the Diagnostic Tools directory, double-click SysCheck.
Step 3 On the Welcome to the Cisco Unity Configuration Wizard page, click Select Configuration Tests, and click Next.
Step 4 Uncheck the boxes for the message stores that are not connected to Cisco Unity.
Step 5 Click Test.
Step 6 In the Test Results box, click the link provided to view the test results.
Step 7 If no errors are reported, proceed to Step 8. Otherwise, do the following sub-steps:
a. Follow the advice offered in the Resolution column to correct each configuration or permissions error.
b. Return to the Completing the Check Unity Configuration Wizard page, and click Finish.
c. Repeat Step 2 through Step 7 until no errors are reported.
Step 8 Click Finish.
2. Classes of service
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. Restriction tables
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, refer to the "Restriction Tables" chapter in the Cisco Unity System Administration Guide.
4. Public distribution lists
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. Subscriber templates
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 appropriate 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.
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.
Using the Cisco Unity Bulk Import Wizard To Create Multiple Subscriber Accounts
The Cisco Unity Bulk Import wizard allows you to create multiple 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.
For each new Internet Subscriber account, Cisco Unity creates a contact or a 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 subscribers by importing user data directly from Exchange, see the procedure, To create Internet Subscriber accounts by using the Cisco Unity Bulk Import wizard. Otherwise, use the following procedure to prepare your CSV file. Refer to the Cisco Unity Bulk Import wizard online Help to find additional information about importing user data directly from Exchange, or about the required and optional column headers for your CSV file.
To prepare a CSV file for creating Internet Subscriber accounts
Step 1 Save the data which you will use to create Cisco Unity accounts as a CSV file.
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 Copy the CSV file to the Cisco Unity server or to a folder that you can browse to from the server.
Step 3 Open the CSV file in a spreadsheet application or another application with which you can edit and reorganize the data. Do the following:
•Confirm that the data is separated by commas, and no tabs, spaces, or semicolons separate the data in the file.
•If any data includes a space, quotes, or commas, contain it within quotes.
Step 4 Rearrange the data, so that the columns are in the same order as the column headers that you will add in Step 5. The order of the column headers does not matter, though it is good practice to set up your CSV file as indicated here.
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
Or
Abade,Alex,SMTP:aabade@cisco.com
Bader,Kelly,SMTP:kbader@cisco.com
Campbell,Terry,SMTP:tcampbell@cisco.com
Cho,Li,SMTP:lcho@cisco.com
Step 5 Enter the required column headers above the first row of data. Column headers must be in uppercase, separated by commas, and spelled as indicated below:
LAST_NAME,FIRST_NAME,REMOTE_ADDRESS
For example, using the sample data from Step 4, the CSV file would look like one of the examples below, depending on which remote address format you use.
When using the VOICE format for remote address:
LAST_NAME,FIRST_NAME,REMOTE_ADDRESS
Abade,Alex,VOICE:123_5678
Bader,Kelly,VOICE:123_4789
Campbell,Terry,VOICE:123_8521
Cho,Li,VOICE:123_3214
Or, when using the SMTP format for remote address:
LAST_NAME,FIRST_NAME,REMOTE_ADDRESS
Abade,Alex,SMTP:aabade@cisco.com
Bader,Kelly,SMTP:kbader@cisco.com
Campbell,Terry,SMTP:tcampbell@cisco.com
Cho,Li,SMTP:lcho@cisco.com
Step 6 If desired, add optional column headers to the first row, and the corresponding data that you want to import in the subsequent rows below. As you do so, confirm that:
•Column headers and data are separated by commas. Note that each row does not have to contain data for each optional column header.
•Any data that includes a space, quotes, or commas is contained within quotes.
Step 7 If your CSV file contains columns of data that you do not want to import, delete the columns. Alternatively, you can title one column NOTES. The Cisco Unity Bulk Import wizard ignores data beneath any NOTES column header, but the wizard does not support more than one NOTES column in a CSV file.
Step 8 Confirm that each row contains the appropriate data corresponding to each column header.
Step 9 Save the file as a CSV file.
Step 10 Continue with the procedure, To create Internet Subscriber accounts by using the Cisco Unity Bulk Import wizard.
To create Internet Subscriber accounts by using the Cisco Unity Bulk Import wizard
Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Bulk Import.
Step 2 Follow the on-screen instructions. (To learn more about the options presented in the dialog boxes that appear as the wizard proceeds, click Help.)
Step 3 When prompted to choose the type of subscriber that you want to create, click Internet.
Step 4 Click Next, and proceed through the wizard. If the wizard reports any errors, you can:
•Click OK to continue with the import, and fix the errors later.
•Fix the errors. See the "Correcting CSV Import Errors" section for details.
Step 5 Once the subscriber accounts are created, click Finish.
Step 6 If you had import errors, but in Step 4 you chose to correct them later, see the "Correcting CSV Import Errors" section.
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 Cisco Unity Bulk Import wizard could not import. The wizard reports the first error it detects in any Exchange 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 the message store, or To correct errors that occurred when importing data from a CSV file.
To correct errors that occurred when importing data from the message store
Step 1 Go to the directory location of the error log file you specified during the import. (The default location and file name is C:\Error.log.)
Step 2 Use a text editor to open the error log file. You will use the error codes in the file to make corrections.
Step 3 When importing data from Exchange 5.5, open the Microsoft Exchange Administrator. When importing data from Exchange 2000, open Active Directory Users and Computers.
Step 4 Double-click an Exchange mailbox that contains an error to see the properties.
Step 5 Enter corrections in the appropriate boxes in the Exchange mailbox.
Step 6 Click OK.
Step 7 Repeat Step 4 through Step 6 for each Exchange mailbox listed in the error log file.
Step 8 Run the Cisco Unity Bulk Import wizard again.
Step 9 Repeat this procedure until all subscriber accounts are created without error, and then proceed to the "After Creating Subscriber Accounts" section.
To correct errors that occurred when importing data from a CSV file
Step 1 Go to the directory location of the error log file you specified during the import. (The default location and file name is C:\Error.log.)
Step 2 Use a text editor to open the error log file. You will use the error codes in the file to make corrections.
Step 3 Go to the directory location of the output log file you specified during the import. (The default location and file name is C:\Output.log.)
Step 4 Use a text editor to open the output log file.
Step 5 Correct any records in the output file that are listed as errors in the error log file.
Step 6 When you have finished editing the output log file, save it as a CSV file with a new name.
Step 7 Run the Cisco Unity Bulk Import wizard again with the CSV file that you saved in Step 6.
Step 8 Repeat this procedure until all subscriber accounts are created without error, and then proceed to the "After Creating Subscriber Accounts" section.
Using the Cisco Unity Administrator To Create Internet Subscriber Accounts
Using the Cisco Unity Administrator, you can create a 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 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.
Step 2 Click the Add icon.
Step 3 Click New Subscriber, and then select Internet from the list.
Step 4 Enter the First Name and Last Name.
Step 5 Enter the Extension of the Internet Subscriber on Cisco Unity. This is the number that Cisco Unity subscribers use when addressing a message to this Internet Subscriber.
Step 6 Select the Subscriber Template to use.
Step 7 Enter the SMTP Address in the appropriate format.
Step 8 Click Add.
Step 9 On the subscriber record, customize settings as appropriate, and then click the Save icon.
To create an Internet Subscriber account by importing existing user data
Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.
Step 2 Click the Add icon.
Step 3 Select Import Existing Exchange User.
Step 4 Click Select.
Step 5 Select Internet.
Step 6 In the Find By list, indicate whether to search by first name, last name, or Exchange alias. When Cisco Unity is connected to an Exchange 2000 server, you can also indicate the domain for the search.
Step 7 Enter the appropriate name or alias. You also can enter * to display a list of all users, or enter one or more characters followed by * to narrow your search.
Note When you perform wildcard (*) searches, Cisco Unity may take several minutes to display results in the Cisco Unity Administrator. This is particularly true if your site has a large number of users (approximately 1000 or more) and/or dozens of servers. For this reason, it is important that you narrow the scope of wildcard searches.
Step 8 Click Find.
Step 9 On the list of matches, click the name of the user to import.
Step 10 Enter the appropriate information on the Add Subscriber page.
Step 11 Click Add.
Step 12 On the subscriber record, customize settings as appropriate, and then click the Save icon.
After Creating Subscriber Accounts
After creating Internet Subscriber accounts, consider the following:
•It takes a few minutes for a newly-created subscriber to be available to receive messages.
•You can make changes to subscriber settings for individual accounts in the Cisco Unity Administrator. (Note that the Bulk Edit utility cannot be used to modify Internet Subscriber settings.) For details, refer to the "Subscriber Settings" chapter in 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.
SMTP Networking Concepts and Definitions
The following sections explain SMTP Networking concepts in detail:
•Locations and SMTP Networking
•Voice Connector and SMTP Networking
•Message Addressing Options
•Blind Addressing and SMTP Networking
•Internet Subscribers
•Considerations for Networked Cisco Unity Servers
Locations and SMTP Networking
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 that corresponds 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. Locations contain the information that Cisco Unity needs to exchange messages with remote Cisco Unity servers—their Dial IDs and Domain Names.
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—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, or through the e-mail clients Cisco Unity ViewMail for Microsoft Outlook (VMO) or the Cisco Unity Inbox.
There are two versions of the Voice Connector. The version that you use depends on your Exchange network:
•When your network consists only of Exchange 5.5 servers, you install the Voice Connector for Exchange 5.5.
•When your network consists only of Exchange 2000 servers, or a mixture of Exchange 2000 and Exchange 5.5 servers, you install the Voice Connector for Exchange 2000.
Caution If your network consists of both Exchange 5.5 and Exchange 2000 servers, do not use the Exchange 5.5 Administrator to manage the Voice Connector for Exchange 2000. Use the Exchange 2000 System Administrator to manage the Voice Connector. To avoid system errors, use the Exchange 5.5 Administrator to configure Exchange 5.5 objects, and use the appropriate MMC snap-in to configure Exchange 2000 objects.
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 others who do not have mailboxes on the local Exchange network:
•Blind addressing—Blind addressing allows subscribers on the local Cisco Unity server to send messages to subscribers on a remote Cisco Unity server that accesses a different directory. When addressing a message, subscribers dial one number that consists of the Dial ID of the SMTP delivery location and the recipient extension. Even though Cisco Unity cannot provide voice name confirmation (hence the term "blind addressing"), the message is addressed and sent. The subscribers on the remote Cisco Unity server receive voice messages. See the "Blind Addressing and SMTP Networking" section for more information.
•Internet Subscribers—Allows messaging to recipients on computers that may or may not be using Cisco Unity. Subscribers on the local Cisco Unity server address messages to Internet Subscribers the same way that they address messages to regular subscribers—by extension or spelled name. See the "Internet Subscribers" section for more information.
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, where the local and remote Cisco Unity servers access different directories. In this situation, the local Cisco Unity server does not have specific information about the recipients on the remote Cisco Unity server (such as their names, extensions, or recorded voice names).
When addressing a message with blind addressing, subscribers dial one 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. 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, who has extension 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).
Subscriber Experience with Blind Addressing
Because the messages are sent and received as voice messages:
•Subscribers can address messages by using the phone or by using Cisco Unity VMO. (Cisco Unity VMI does not support SMTP blind addressing because the blind address does not resolve to a subscriber in the address book.) To address a message by using Cisco Unity VMO, subscribers enter the address in the following format (the underscore and the brackets are required):
[VOICE:<Location Dial ID>_<Extension>]
•Cisco Unity lights the MWI lamp on the recipient phone.
•Recipients can listen to the messages by using the phone, Cisco Unity VMO, or the Cisco Unity Inbox.
•Recipients can reply to the messages by using the phone or Cisco Unity VMO. (The Cisco Unity Inbox cannot be used to reply in this case.)
•Urgent messages are received as urgent messages.
•Private messages are received as private.
•Requests for return receipts are honored.
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:
•When addressing a message, the sender does not get voice name confirmation. Cisco Unity cannot verify that the entered number is correct, so subscribers may inadvertently address a message to the wrong person or to a non-existent extension. However, subscribers will receive an non-delivery receipt (NDR) if the number turns out to be an invalid extension.
•When addressing a message, the sender cannot use spelled-name mode; the delivery location Dial ID and extension of the recipient must be entered.
•Blind addresses cannot be added to distribution lists.
•When the recipient checks messages, the message is not identified as coming from another subscriber, but from an unidentified caller. (However, if there is an Internet Subscriber on the receiving Cisco Unity server that corresponds to the sending subscriber, the message is identified as being from the Internet Subscriber. See the "Internet Subscribers that Correspond to Remote Cisco Unity Subscribers" section.)
Internet Subscribers
Internet Subscribers are Cisco Unity subscribers 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. 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:
•Cannot log on to Cisco Unity by phone to check or send messages.
•Cannot log on to Cisco Unity by phone—or use the Cisco Unity Assistant—to adjust personal settings, so their recorded names and greetings can only be recorded or changed in the Cisco Unity Administrator. (Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA)
•Cannot use Cisco Unity ViewMail for Outlook or the Cisco Unity Inbox. (Note that in version 3.1 and earlier, the Cisco Unity Inbox was known as the Visual Messaging Interface or VMI)
•Cannot own private lists.
•Cannot set up or receive message notifications.
•Cannot receive message waiting indications.
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:
•Subscribers can address messages to Internet Subscribers by using the phone, ViewMail, or the Cisco Unity Inbox.
•Unless they have been explicitly hidden, the contacts that correspond to Internet Subscribers are listed in the Exchange address book. Therefore, message addressing by using ViewMail or the Cisco Unity Inbox to Internet Subscribers is the same as for regular subscribers.
•When using the phone, subscribers can address messages to Internet Subscribers by spelled-name mode (if enabled on the system) or by extension.
•Subscribers get voice name confirmation when addressing a message to an Internet Subscriber.
•Internet Subscribers can be added to distribution lists.
•Both unidentified callers and subscribers can place a call to an Internet Subscriber and leave a message. If Cisco Unity is integrated with a networked phone system, calls from both unidentified callers and subscribers can be transferred to the Internet Subscriber extension. (With a networked phone system, subscribers dial an extension without having to dial a trunk access code or prefix when calling someone who is at another location on the phone network.)
•If the remote message recipient does not use Cisco Unity, subscribers receive replies to a message as an e-mail with a WAV attachment. If the remote message recipient uses Cisco Unity, subscribers receive replies to messages as voice messages.
Extensions are optional for Internet Subscribers whereas they are mandatory for regular subscribers. If an Internet Subscriber has not been assigned an extension:
•The Internet Subscriber cannot be listed in the phone directory.
•Unidentified callers will be unable to leave messages for the Internet Subscriber.
•When addressing messages to the Internet Subscriber, subscribers are limited to spelled-name mode, provided that the Internet Subscriber has a recorded voice name. If neither an extension nor a voice name has been set, messages cannot be addressed to the Internet Subscriber.
Internet Subscribers that Correspond to Remote Cisco Unity Subscribers
If your organization consists of 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:
•Cisco Unity lights the MWI lamp on the recipient phone.
•Recipients can listen to the messages by using the phone, Cisco Unity VMO, or the Cisco Unity Inbox.
•Recipients can reply to the messages by using the phone or Cisco Unity VMO. If the recipient subscriber and the Internet Subscriber that corresponds to the sender were created on the same Cisco Unity server, the recipient can reply by using the Cisco Unity Inbox.
•Urgent messages are received as urgent messages.
•Private messages are received as private.
•Requests for return receipts are honored.
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:
•When subscribers want voice name confirmation when addressing messages to subscribers on the remote Cisco Unity server.
•When the recipients at the remote location need to be included on public or private distribution lists that are created on the local Cisco Unity server.
•When unidentified callers need to be able to call the local Cisco Unity server to leave a message for a subscriber associated with another Cisco Unity server. You may want to do this, for example, to provide a way for customers to avoid long distance charges when leaving a message for a sales representative who is associated with a remote Cisco Unity server.
Because of the administrative overhead of setting up and maintaining many Internet Subscriber accounts, you may prefer a combination of blind addressing, 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 the 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 appropriate 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: VOICE:123_5678, where:
•VOICE indicates that the remote message recipient uses Cisco Unity. Messages with the VOICE address type are processed by the Voice Connector on both the sending and receiving systems.
•123 is the Dial ID of the SMTP delivery location on the local Cisco Unity server. A mandatory underscore (_) follows the Dial ID.
•5678 is the primary extension of the subscriber on the remote Cisco Unity server (alternate extensions are not supported).
Note The Voice Connector uses the Domain Name from the specified delivery location to form an address for the Internet Subscriber. If the address that you enter here contains a domain name, it is ignored when the message is addressed.
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 has to be changed:
•The Dial ID of the remote SMTP delivery location on the remote Cisco Unity server(s) must be updated to match the new primary location Dial ID.
•The SMTP addresses for all associated Internet Subscribers must be updated manually one at a time. There is no utility to help with the change.
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 get the address, and determines this is an Internet Subscriber. The message gets 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.
Figure 3-2 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.Internet Subscribers that Correspond to Remote Cisco Unity Subscribers
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. On the phone, a subscriber addresses a message to a subscriber on another Cisco Unity server.
2. Cisco Unity searches for a matching extension or delivery location. (See the "Subscriber Addressing Options" section on page 7-6 for details on the search that is performed.)
–If a matching extension is found, voice confirmation is provided, and Cisco Unity obtains the SMTP Address from the Internet Subscriber account and addresses the message.
–If a matching delivery location is found, the number that the subscriber entered is used for the address.
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. Because the message has the VOICE address type, Exchange hands off the message to the Voice Connector.
4. The Voice Connector obtains the domain name from the delivery location and constructs the To address in the following format:
SMTP:IMCEAVOICE-<Delivery Location Dial ID>_<Extension>@<DomainName>
5. The Voice Connector obtains information from the primary location and constructs the From address in the following format:
SMTP:IMCEAVOICE-<Primary Location Dial ID>_<Extension>@<DomainName>
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@<DomainName>
6. The Voice Connector converts the message to MIME, and then hands the message back to Exchange to be sent through the Exchange SMTP gateway.
7. On the receiving side, because of the IMCEAVOICE address type, Exchange hands the message over to the Voice Connector for processing.
8. The Voice Connector parses the To address and looks for a matching primary location and a matching subscriber extension at that location to obtain the e-mail address for the recipient. If a match is found, the Voice Connector addresses the message appropriately so that it can be delivered by Exchange. If a match is not found, an NDR is returned to the sender.
9. The Voice Connector parses the From address and looks for a matching Internet Subscriber. If a match is found, the Voice Connector changes the From address so that the sender is identified when the recipient listens to the message.
10. The Voice Connector converts the MIME message back to a voice message.
11. The Voice Connector sends the message back to Exchange to be delivered to the subscriber.
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 a SMTP delivery location or to an Internet Subscriber created on another server.
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.
Table 3-1 Settings Applicable to All Types of Delivery Locations
Field
|
Considerations
|
Name
|
This displays the name of the delivery location. To change the name, enter a new name here, and then click the Save icon.
|
Dial ID
|
Enter the ID that identifies the location to Cisco Unity. Enter numbers only, up to a maximum of ten digits. The default minimum length is three digits.
Although the minimum length for Dial IDs can be reduced by using the Advanced Settings Tool, one- and two-digit Dial IDs may conflict with private distribution list IDs during an address search. When a subscriber addresses a message by entering a one- or two-digit number, Cisco Unity first searches for a matching private distribution list. If a match is found, the search stops. Therefore, when a subscriber addresses a message by entering a location Dial ID (to narrow down the search scope to a particular location), if the number entered matches a private distribution list ID, the conversation offers only the private distribution list as a destination. If subscribers do not address messages to other locations by first entering a Dial ID, there is no conflict, and the minimum length for Dial IDs can be reduced to accommodate complex dial plans.
When addressing a message to another location by using blind addressing, subscribers dial a number that is made up of the Dial ID and the extension (or the remote mailbox number) of the recipient.
When setting up SMTP networking with a Cisco Unity server in a different directory, the ID that you enter here must match the Dial ID of the primary location at the corresponding remote Cisco Unity server.
The following policies are recommended:
•Establish a fixed length for Dial IDs and if possible, a fixed length for extensions.
•Assign unique Dial IDs. Dial IDs should not be the same as other Dial IDs or extensions.
•Assign three-digit Dial IDs.
•Use a different numbering range for Dial IDs than for extensions.
•If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs.
If you change the Dial ID after creating subscriber accounts associated with this location, run the Extension Address utility to generate new extension addresses. To run the utility, on the Windows Start menu, click Programs > Unity > Extension Address Utility, and then click Update. It may take three to five minutes for the addresses to be updated in Exchange.
|
Recorded Name
|
Record a name for the delivery location. The subscriber conversation plays this recorded name when the setting Include Locations in Searches on the Network > Primary Location > Addressing Options page is enabled. When subscribers address a message, the recorded name for this delivery location is played in the message addressing search results along with subscriber names. (For example: "There are two matches. For Chris Newton, press 1. For New York, press 2.") Additionally, the subscriber conversation plays this recorded name when subscribers address messages by using blind addressing to this delivery location.
To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
|
Destination Type
|
Display only. Indicates the type of delivery location. The Destination Type is specified when the delivery location is created, and it cannot be changed. The Destination Type is one of the following:
•SMTP—Indicates that the delivery location corresponds to a remote Cisco Unity server that accesses a directory different than the local Cisco Unity server. Messages between the local and remote Cisco Unity servers are encoded in a proprietary format and delivered over the Internet or a private TCP/IP network by using the standard Simple Mail Transfer Protocol (SMTP).
•AMIS—Indicates that the delivery location corresponds to an AMIS-compliant voice messaging system. Messages are sent by using the industry-standard Audio Messaging Interchange Specification analog (AMIS-a) protocol.
•Bridge—Indicates that the delivery location corresponds to an Octel node in an Octel analog network. Messages are exchanged between Cisco Unity and the Octel system by using the Cisco Unity Bridge. Cisco Unity sends messages to the Bridge in Voice Profile for Internet Mail (VPIM) format with proprietary extensions. The Bridge converts the message format and sends it to the appropriate Octel server by using the Octel Analog Networking protocol.
•VPIM—Indicates that the delivery location corresponds to a VPIM-compliant voice messaging system. Messages are sent by using the industry-standard VPIM protocol over the Internet or a private TCP/IP network.
|
Table 3-2 Settings Specific to SMTP Delivery Locations
Field
|
Considerations
|
Domain Name
|
Enter the Internet-addressable SMTP domain name for the Cisco Unity server that corresponds to this delivery location. This is the right half of an e-mail address after the @ symbol (for example, london.cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it.
This field must match the SMTP Domain Name in the corresponding remote primary location. When subscribers on the local Cisco Unity server address messages to subscribers on the remote Cisco Unity server, the Voice Connector obtains the Domain Name to construct the To address in the following format:
SMTP:IMCEAVOICE:<Delivery Location Dial ID>_<Extension>@<DomainName>
|
Feedback
