Networking Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
VPIM Networking in Cisco Unity 8.x
Downloads: This chapterpdf (PDF - 724.0KB) The complete bookPDF (PDF - 5.33MB) | Feedback

VPIM Networking in Cisco Unity 8.x

Table Of Contents

VPIM Networking in Cisco Unity 8.x

Setting Up Cisco Unity 8.x to Use VPIM Networking

Prerequisites

Task List: Setting Up Cisco Unity to Use VPIM Networking

Procedures for Setting Up Cisco Unity 8.x to Use VPIM Networking

Making Design Decisions and Gathering Needed Information

Determining the Interoperability Domain Name

Domain Name Requirements

Resolving Names with IP Addresses

Verifying Connectivity with the Remote Voice Messaging System

Extending the Active Directory Schema

Verifying the Recipient Policies or Creating a New One (Voice Connector Installations Only)

Setting Up the Voice Connector for VPIM Networking

Controlling What Happens to Messages That Cannot Be Delivered (Voice Connector Installations Only)

Creating the UVPIM Account by Using ConfigMgr.exe (Optional)

Customizing the Primary Location

Creating VPIM Delivery Locations

Using the Cisco Unity Administrator to Create VPIM Delivery Locations

Using the Cisco Unity Bulk Import Wizard to Create VPIM Delivery Locations

Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard

Creating VPIM Subscribers

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 VPIM Subscriber Accounts

After Creating Subscriber Accounts

Customizing VPIM Subscriber Directory Update Settings

Before Configuring VPIM Subscriber Creation Settings

Using the Cisco Unity Administrator to Configure VPIM Subscriber Creation Settings

Using the Cisco Unity Bulk Import Wizard to Configure VPIM Subscriber Creation Settings

Changing the AD Location in Which Automatically Created VPIM Subscribers Are Created (Optional)

Extending Identified Subscriber Messaging to Include VPIM Subscribers

Installation with Multiple Cisco Unity Servers Networked via Digital Networking

Single-Server Installations

Setting Permissions on Active Directory Containers Used for Importing Subscribers

Enabling Identified Subscriber Messaging

Extending Identified Subscriber Messaging

Gathering Information About Cisco Unity to Configure Another Voice Messaging System for VPIM

VPIM Concepts and Definitions in Cisco Unity 8.x

Introduction to VPIM

VPIM Messages

VPIM Addresses

VPIM Networking and Locations

The Interoperability Gateway for Microsoft Exchange and Cisco Unity Voice Connector for Microsoft Exchange Components

About the VPIM Transport Event Sink

How the Messaging Gateway Component Processes Incoming VPIM Messages

How the Messaging Gateway Component Processes Outgoing VPIM Messages

Message Addressing Options

Messaging Similarities and Limitations

VPIM Networking and Blind Addressing

Subscriber Experience with Blind Addressing

VPIM Subscribers

Subscriber Experience with VPIM Subscribers

Automatic VPIM Subscriber Directory Updates

Directory Update Processing That Occurs at the Messaging Gateway Component

Directory Update Processing That Occurs on the Cisco Unity VPIM Bridgehead Server

Population of VPIM Subscriber Information

Subscriber Addressing Considerations with Automatic Updates

CsVPIMConnector Logging

Identified Subscriber Messaging

Live Reply to VPIM Subscribers

Deleting VPIM Subscribers

Extension Addresses

Determining How VPIM Subscribers Appear in the Outlook Address Book

Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant

Migrating Subscribers from Another Voice Messaging System to Cisco Unity

Migrating Subscribers in Bulk

Migrating Subscribers One at a Time

Private List Considerations for Migrating Subscribers

Considerations for Digitally Networked Cisco Unity Servers

Phone Prefixes

Audio Format Considerations

VPIM Networking Maintenance in Cisco Unity 8.x

Changing the IP Address of a Microsoft Exchange Server

Moving the UVPIM Mailbox

Notable Behavior of VPIM Networking in Cisco Unity 8.x

Call Transfer Settings and VPIM Subscribers

Inbound Messages Are Delivered Only to Primary Extensions

Inbound Search Scope

Running the Voice Connector Setup Program in Another Language


VPIM Networking in Cisco Unity 8.x


Cisco Unity supports the Voice Profile for Internet Mail (VPIM) protocol, which is an industry standard that allows different voice messaging systems to exchange voice, fax, and text messages over the Internet or any TCP/IP network. VPIM is based on the Simple Mail Transfer Protocol (SMTP) and the Multi-Purpose Internet Mail Extension (MIME) protocol.

For information about the VPIM-compliant voice messaging systems that Cisco Unity supports, see Supported Hardware and Software, and Support Policies for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. Note that VPIM Networking can be used for messaging between Cisco Unity servers that are in different directories, including messaging between Cisco Unity with Microsoft Exchange and Cisco Unity with IBM Lotus Domino systems.

VPIM Networking is a licensed feature. If your organization has multiple Cisco Unity servers networked together using Cisco Unity Digital Networking (and, therefore, accessing subscriber data in the same directory), only one server in the Digital Network needs to be licensed and configured for VPIM Networking. The Cisco Unity server configured for VPIM Networking is referred to as the bridgehead server. For more information on obtaining licenses for Cisco Unity features, see the applicable Licensing for Cisco Unity white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

To use VPIM Networking, you must choose the applicable options when you run the Cisco Unity Permissions wizard. For detailed information, see Permissions wizard Help, which is available in Tools Depot on the Cisco Unity server.

See the following sections:

Setting Up Cisco Unity 8.x to Use VPIM Networking—This section describes the prerequisites for setting up VPIM Networking, and provides a task list containing a high-level view of all of the tasks you need to complete for the setup, and the order in which they should be completed.

Procedures for Setting Up Cisco Unity 8.x to Use VPIM Networking—This section contains all of the step-by-step procedures necessary to set up Cisco Unity for VPIM Networking.

VPIM Concepts and Definitions in Cisco Unity 8.x—This section explains VPIM Networking concepts in detail. If you are unfamiliar with VPIM Networking, read this section prior to doing the setup procedures.

VPIM Networking Maintenance in Cisco Unity 8.x—This section provides information about monitoring system activity.

Notable Behavior of VPIM Networking in Cisco Unity 8.x—This section documents notable behavior related to VPIM Networking.

Related Documentation

"Using VPIM for Networking Cisco Unity 8.x with Cisco Unity Express or Other Cisco Unity Systems"

"Troubleshooting VPIM Transport," at http://www.ciscounitytools.com/Documents.htm.

Setting Up Cisco Unity 8.x to Use VPIM Networking

This section describes the prerequisites for setting up VPIM Networking, and provides a task list containing a high-level view of all of the tasks you need to complete for the setup, and the order in which they should be completed. If you are unfamiliar with VPIM Networking, you should first read the "VPIM Concepts and Definitions in Cisco Unity 8.x" section and then review the task list and procedures before beginning the setup. Planning is essential to a successful setup.

Prerequisites

Before starting the setup, verify that the following prerequisites have been met:

Cisco Unity is already installed on the servers, and they are connected to the network as applicable for your installation.

The remote voice messaging system with which Cisco Unity will be networked meets the requirements as described in the "Support Policy for VPIM Voice Messaging Systems" section of the Supported Hardware and Software, and Support Policies for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

A license file with a VPIM license has been obtained and installed on the Cisco Unity Bridgehead server.

Cisco Unity and Exchange meet the requirements as described in the "VPIM Networking Requirements" section in Networking Options Requirements for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

For installations with multiple Cisco Unity servers that access that same directory, you should first set up the servers for Digital Networking as described in the "Digital Networking in Cisco Unity 8.x" chapter before setting up VPIM Networking. After the Cisco Unity servers have been set up for Digital Networking, verify the following settings:

Verify that the addressing search scope is set to either the dialing domain or the global directory on all of the networked servers so that Cisco Unity subscribers, no matter which server they are associated with, can address messages to VPIM delivery locations and/or VPIM subscribers. See the "Setting the Addressing Search Scope" section on page 2-7 for details.

If you want outside callers to be able to reach VPIM subscribers from the automated attendant (for example, from the opening greeting) or directory assistance:

Verify that the Cisco Unity servers on which the VPIM subscribers will be created are in the same dialing domain as the Cisco Unity server that outside callers call into. See the "Customizing the Primary Location" section for details on creating the dialing domain, and the "Dialing Domains" section on page 2-15 for background information.

Verify that the automated attendant and directory handlers search scopes are set to the dialing domain scope. See the "Setting the Directory Handler Search Scope" section on page 2-7 and the "Setting the Automated Attendant Search Scope" section on page 2-7.

Task List: Setting Up Cisco Unity to Use VPIM Networking

Use the task list that follows to set up VPIM Networking in Cisco Unity. The cross-references take you to detailed procedures for the setup. If you are setting up VPIM Networking for messaging between Cisco Unity servers in different directories, do these tasks in both Cisco Unity locations.

1. Make decisions about your numbering plan and gather information needed to configure VPIM Networking. See the "Making Design Decisions and Gathering Needed Information" section.

2. Determine the interoperability domain name that will be used for messaging between the remote voice messaging system and Cisco Unity. See the "Determining the Interoperability Domain Name" section.

3. As applicable, configure DNS or HOSTS files. See the "Resolving Names with IP Addresses" section.

4. Verify network and SMTP connectivity with the remote voice messaging system. See the "Verifying Connectivity with the Remote Voice Messaging System" section.

5. Extend the Active Directory schema to enable VPIM Networking. See the "Extending the Active Directory Schema" section.

6. If you are installing the Interoperability Gateway for Microsoft Exchange: Install and configure the Interoperability Gateway on an Exchange 2007 or Exchange 2003 server. See the "Setting Up the Interoperability Gateway for Microsoft Exchange in Cisco Unity 8.x" section on page 9-1.

7. If you are installing the Cisco Unity Voice Connector for Microsoft Exchange: Determine whether the default recipient policy can be used for the Voice Connector Exchange mailbox, or create a new recipient policy. See the "Verifying the Recipient Policies or Creating a New One (Voice Connector Installations Only)" section.

8. If you are installing the Cisco Unity Voice Connector for Microsoft Exchange: Install the Cisco Unity Voice Connector on an Exchange 2000 or Exchange 2003 server. See the "Setting Up the Voice Connector for VPIM Networking" section.


Caution Installing the Voice Connector on an Exchange 2007 server is not supported.

Do the Following Tasks on the Cisco Unity Server That Is Licensed for VPIM (the Bridgehead Server)

9. During Cisco Unity installation, when you ran the Cisco Unity Permissions wizard to grant the necessary permissions to the installation and service accounts, if you did not check the Set Permissions Required by AMIS, Cisco Unity Bridge, VPIM, and Connection Networking check box on the Choose Whether to Enable Voice Messaging Interoperability page, do the following steps:

a. Log on to the bridgehead server by using an account that:

Is a member of the Domain Admins group in the domain that the Cisco Unity server belongs to, or that has permissions equivalent to the default permissions for the Domain Admins group.

Is either an Exchange Full Administrator or a member of the Domain Admins group in the domain that contains all of the domains from which you want to import Cisco Unity subscribers.

b. Re-run the Permissions wizard, and follow the on-screen prompts until the Choose Whether to Enable Voice Messaging Interoperability page appears.

c. Check the Set Permissions Required by AMIS, Cisco Unity Bridge, VPIM, and Connection Networking check box.

d. Follow the on-screen prompts to complete the Permissions wizard.

For more information on running the Permissions wizard, see the Permissions wizard Help file, PWHelp_<language>.htm, in the directory where the Permissions wizard is installed.

If you do not know whether you checked the check box, run the Permissions wizard in report mode. For more information, see the Report Mode Help file, PWReportHelp_<language>.htm, in the directory where the Permissions wizard is installed.

10. If you plan to configure Cisco Unity to automatically update the VPIM subscriber directory, run ConfigMgr.exe in order to create the UVPIM account. See the "Creating the UVPIM Account by Using ConfigMgr.exe (Optional)" section.

11. Customize the primary location profile settings. See the "Customizing the Primary Location" section.

12. Create delivery locations for each remote voice messaging system. See the "Creating VPIM Delivery Locations" section.

13. Optionally, create VPIM subscribers. See the "Creating VPIM Subscribers" section.

14. Optionally, customize the delivery location settings that control automatic VPIM directory updates. See the "Customizing VPIM Subscriber Directory Update Settings" section.

15. Optionally, extend identified subscriber messaging to include VPIM subscribers. See the "Extending Identified Subscriber Messaging to Include VPIM Subscribers" section.

Finish the Setup

16. Set up the remote voice messaging system for VPIM. Precisely how this is done depends on the voice messaging system. However, you will need to provide the remote system with information about Cisco Unity. See the "Gathering Information About Cisco Unity to Configure Another Voice Messaging System for VPIM" section.

17. Test the setup to verify that Cisco Unity can exchange messages with the other voice messaging system.

Procedures for Setting Up Cisco Unity 8.x to Use VPIM Networking

This section contains all of the procedures necessary to set up Cisco Unity for VPIM Networking. If you are unfamiliar with VPIM Networking, you should first read the "VPIM Concepts and Definitions in Cisco Unity 8.x" section. Consult the "Task List: Setting Up Cisco Unity to Use VPIM Networking" section for information on the order in which the procedures must be done.

Making Design Decisions and Gathering Needed Information

Before you begin setting up Cisco Unity for VPIM Networking, be sure to plan for the following, and gather the applicable information:

Review your numbering plan strategy to determine whether you will need to enter prefixes on the VPIM delivery location and to determine which numbers to assign as Dial IDs for the primary and VPIM delivery locations.

Decide whether you want Cisco Unity subscribers to use blind addressing or to address messages to VPIM subscribers. If you choose to use VPIM subscribers, determine for each remote VPIM system whether you will allow Cisco Unity to automatically create, modify, and delete VPIM subscriber entries for users on that system, based on information received in incoming VPIM messages. For each delivery location that will allow automatic updates, find out if the remote system will send a vCard with each message, or if the message headers should be used as the source of VPIM subscriber information instead. Also decide how you will map the source information to VPIM subscriber display names and extensions. For more information on automatic directory update considerations, see the "Automatic VPIM Subscriber Directory Updates" section.

Make note of the following information about the remote voice messaging system: the mailbox range, the server name, the domain name, and the IP address.

Decide whether you will use the Interoperability Gateway for Microsoft Exchange or the Voice Connector as the messaging gateway. Note the following considerations:

If your Exchange organization includes only Exchange 2007 servers, you must use the Interoperability Gateway. The Voice Connector cannot be installed on an Exchange 2007 server.

If you are using or plan to use Cisco Unity Connection Networking, you must use the Interoperability Gateway for VPIM Networking. Connection Networking requires the Interoperability Gateway, and the Interoperability Gateway is not compatible with the VPIM Transport Event Sink required by the Voice Connector.

If you are using or plan to use AMIS or Bridge Networking, these protocols require the Voice Connector. You can choose either gateway for VPIM in this case (as long as you do not also use Connection Networking, which requires you to use the Interoperability Gateway for VPIM); either way, you will have to retain the Voice Connector for AMIS or the Bridge.

The Interoperability Gateway cannot be installed on Exchange 2000. If you must use an Exchange 2000 server for the messaging gateway, choose the Voice Connector. Note, however, that Connection Networking is not supported in this configuration, and if you call Cisco TAC with a problem related to using the Voice Connector that is tracked to an Exchange 2000 issue, the Cisco TAC engineer may require that you migrate the Voice Connector to an Exchange 2003 server.

If none of these considerations apply to your situation and you are unsure which to choose, we recommend that you choose the Interoperability Gateway.


Note For additional requirements and version compatibility information for both the Interoperability Gateway and the Voice Connector, see the "VPIM Networking Requirements" section in Networking Options Requirements for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.


Choose the Exchange (or relay) server that will handle outgoing messages to the remote voice messaging system.

Choose the Exchange servers on which to install the Interoperability Gateway or the Voice Connector and the VPIM Transport Event Sink. (Note that the Transport Event Sink is not used when you install the Interoperability Gateway on an Exchange 2007 server; if you install the Interoperability Gateway on an Exchange 2003 server, it automatically installs an event sink on the same server.) Write down the FQDN and IP address of the Exchange server(s).

Write down the FQDN and IP address of the Exchange (or relay) servers that handle incoming SMTP messages.

Determining the Interoperability Domain Name

VPIM messages are addressed in the format <Mailbox Number>@<Domain Name>. In order for messages to be exchanged between the remote voice messaging system and Cisco Unity, you will need to decide on the interoperability domain name that the remote voice messaging system will use when addressing messages to Cisco Unity subscribers. The interoperability domain name will be configured as follows:

On the remote voice messaging system on the location or node profile that corresponds to Cisco Unity. (Refer to the documentation for the remote voice messaging system for additional information.)

On the SMTP Domain field, during the installation of the Voice Connector VPIM Transport Event Sink.

On the SMTP Domain Name field on the Network > Primary Location page in the Cisco Unity Administrator.

As the foreign domain name in the Interoperability Gateway Administrator, if you install the Interoperability Gateway on an Exchange 2007 server.

In the recipient policy for the Interoperability Gateway, if you install the Interoperability Gateway on an Exchange 2003 server.

In the recipient policy for the Voice Connector Exchange mailbox, if you install the Voice Connector.

If the remote voice messaging system location or node profile that corresponds to Cisco Unity has already been configured with a domain name, use that domain name in the procedures that follow. Otherwise, consult with the Exchange administrator for your organization to determine an appropriate interoperability domain name to use.

Domain Name Requirements

The domain name uniquely identifies the messaging system. When choosing domain names used by Cisco Unity and the remote voice messaging system, keep the following in mind:

Cisco Unity and the remote voice messaging system cannot use the same domain name; each system must use a unique domain name.

The complete interoperability domain name used by Cisco Unity cannot be a subset of the domain name used by the remote voice messaging system. For example, if Cisco Unity is using the domain name cisco.com, the remote voice messaging system cannot use names like london.cisco.com, paris-cisco.com, or romecisco.com. However, you could use europe.cisco.com for Cisco Unity, and then use the names london.cisco.com, paris-cisco.com, and romecisco.com.

The complete interoperability domain name used by Cisco Unity should not match any SMTP domain used in the Exchange organization to which Cisco Unity belongs for any purpose other than for routing messages through the messaging gateway component (Interoperability Gateway for Microsoft Exchange or Voice Connector).

If Bridge Networking is already configured, choose a domain name that is different from the domain name in use for Bridge Networking, and that is not a subset of the domain name used for Bridge Networking. For example, if the domain configured for Bridge Networking is cisco.com, do not use a name like vpim.cisco.com or vpim-cisco.com for VPIM Networking. However, if you are using bridge.cisco.com for Bridge Networking, you could use the name vpim.cisco.com or vpim-cisco.com for VPIM Networking.


Caution Choosing a domain name that does not meet these requirements will result in message delivery failure.

Resolving Names with IP Addresses

VPIM messages are sent over the Internet or any TCP/IP network via SMTP. Therefore, some mechanism for name resolution is required for the remote voice messaging server and the Exchange (or relay) servers that handle incoming and outgoing SMTP messages. (Depending on your network, this may or may not be the same Exchange server on which the Interoperability Gateway or the Voice Connector and the VPIM Transport Event Sink will be installed.) While any method or combination of methods can be used, two common ways to accomplish name resolution are through Domain Name System (DNS), and by using HOSTS files.

Whether you use DNS or HOSTS files, you will need to know the fully qualified domain name (FQDN) and IP address of the remote voice messaging server and the Exchange (or relay) server that handles incoming SMTP messages. The FQDN is displayed in the Windows System Control Panel on the Network Identification tab in the Full Computer Name field.

If your organization uses DNS:

Add a host address resource (A) record and a mail exchange (MX) record in DNS for the remote voice messaging server, if they do not already exist.

Verify that an A and MX record exist in DNS for the Exchange server (or relay server) that handles incoming SMTP messages. If the records are not in DNS, add them before continuing with the setup.

Refer to the Microsoft Windows or applicable operating system documentation for more information about adding A and MX records in DNS.

If your organization does not use DNS, you can use HOSTS files for name resolution. A HOSTS file is a text file that contains the mappings of IP addresses to host and domain names. On Microsoft Windows systems, the HOSTS file is located in the %windir%\System32\Drivers\Etc directory. Edit the HOSTS files as follows:

On the Exchange (or relay) server that handles outgoing SMTP messages, add an entry to the HOSTS file with the FQDN and IP address of the remote voice messaging server.

Refer to the remote voice messaging server documentation for information on name resolution. You may need to add an entry to the HOSTS file on the remote voice messaging server with the FQDN and IP address of the Exchange (or relay) server that handles incoming SMTP messages.

Verifying Connectivity with the Remote Voice Messaging System

Verify that the Exchange (or relay) servers that handle outgoing and incoming SMTP messages have network and SMTP connectivity with the remote voice messaging server, and vice versa.

For networking with another voice messaging server, you may need to install and configure an SMTP service or gateway on that server. Refer to the documentation of the other voice messaging system for information on installing the SMTP service or gateway. Before proceeding, verify that the SMTP service or gateway has been installed on the other voice messaging server.

To Verify Network Connectivity with the Remote Voice Messaging Server


Step 1 On the Exchange (or relay) server that handles outgoing SMTP messages, open a command prompt window.

Step 2 Enter ping <IP address>, where <IP address> is the IP address of the remote voice messaging server.

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 that will be used to address messages to the remote voice messaging server. The domain name in this step is the domain name that will be entered on the VPIM delivery location page in the Cisco Unity Administrator when setting up VPIM Networking.

Step 4 If you received a reply when pinging the IP address in Step 2, but no replies when pinging the domain name in Step 3, see the "Resolving Names with IP Addresses" section. When the problem is resolved, continue with Step 5.

Step 5 Test network connectivity in the opposite direction. For systems other than Cisco Unity, consult the documentation for information on how to conduct the test, and continue with Step 6. Note that the remaining steps in this procedure may not exactly match the steps necessary for your system, so you may need to make adjustments.

Step 6 On the remote server, ping the IP address of the local Exchange (or relay) server that handles incoming SMTP messages.

If you receive no reply, troubleshoot the network connectivity problem until the problem is resolved. Then continue with Step 7.

Step 7 On the remote server, ping the interoperability domain name, where the interoperability domain name is the one that you decided on in the "Determining the Interoperability Domain Name" section.

Step 8 If pinging by the interoperability domain name fails, see the "Resolving Names with IP Addresses" section. When you verify that you have basic network connectivity, continue with the following "To Verify SMTP Connectivity with the Remote Voice Messaging Server" procedure.


To Verify SMTP Connectivity with the Remote Voice Messaging Server


Step 1 In a command prompt window on the Exchange (or relay) server that handles outgoing SMTP messages, enter telnet <RemoteDomainName> 25, where <RemoteDomainName> is the domain name that will be used to address messages to the remote voice messaging server.

Step 2 If there is a response, enter ehlo <DomainName>, where <DomainName> is the interoperability domain name that you decided on in the "Determining the Interoperability Domain Name" section.

Step 3 If the telnet test was successful, enter quit to end the telnet session.

Step 4 Test SMTP connectivity in the opposite direction. For systems other than Cisco Unity, consult the documentation for information on how to conduct the SMTP connectivity test, and continue with Step 5. Note that the remaining steps in this procedure may not exactly match the steps necessary for your system, so you may need to make adjustments based on your voice messaging system documentation.

Step 5 On the remote server, attempt to start a telnet session. Enter telnet <DomainName> 25, where <DomainName> is the interoperability domain name that you decided on in the "Determining the Interoperability Domain Name" section.

Step 6 If there is a response, on the remote server, enter ehlo <RemoteDomainName>, where <RemoteDomainName> is the domain name of the remote voice messaging server.

If either of the telnet tests in Step 5 or Step 6 fails, there is a basic SMTP connectivity problem that must be resolved before proceeding with the VPIM Networking setup.

Step 7 If you are using the Interoperability Gateway for Microsoft Exchange, the processing of VPIM messages will occur on the Exchange server on which the Interoperability Gateway is installed. If the Interoperability Gateway will not be installed on the server that handles incoming and outgoing SMTP messages, review your Exchange settings to verify:

That the server that handles incoming SMTP messages is able to route messages to the Exchange server on which the Interoperability Gateway will be installed.

That the server on which the Interoperability Gateway will be installed is able to route messages to the server that handles outgoing SMTP messages.

That the Exchange servers where Cisco Unity subscriber mailboxes are located can route messages to the Exchange server on which the Interoperability Gateway is installed.

That the Exchange server on which the Interoperability Gateway is installed can route messages to the Exchange servers where Cisco Unity subscriber mailboxes are located.

Step 8 If you are using the Cisco Unity Voice Connector for Microsoft Exchange, the processing of VPIM messages will occur on the Exchange servers on which the Voice Connector and the VPIM Transport Event Sink will be installed. If the Transport Event Sink will not be installed on the server that handles incoming and outgoing SMTP messages, and/or if the Voice Connector and the Transport Event Sink will be installed on separate Exchange servers, review your Exchange settings to verify:

That the server that handles incoming SMTP messages is able to route messages to the Exchange server on which the Transport Event Sink will be installed.

That the server on which the Transport Event Sink will be installed is able to route messages to the server on which the Voice Connector will be installed, if they will be installed on separate servers.

That the server on which the Voice Connector will be installed is able to route messages to the server that handles outgoing SMTP messages.

That the Exchange servers where Cisco Unity subscriber mailboxes are located can route messages to the Exchange server on which the Voice Connector is installed.

That the Exchange server on which the Voice Connector is installed can route messages to the Exchange servers where Cisco Unity subscriber mailboxes are located.

Refer to your Exchange documentation for more information.


Extending the Active Directory Schema

Before Cisco Unity is installed, the Active Directory schema is extended to store Cisco Unity-specific information. To support VPIM Networking, the schema must be further extended. To see the schema changes that need to be made to support VPIM Networking, browse to the directory Schema\LdifScripts on Cisco Unity Disc 1, and view the file vpimgateway.ldf.

To Extend the Active Directory Schema for VPIM Networking

Do this procedure only if you did not already modify the Active Directory schema to support VPIM Networking during the Cisco Unity installation. You can verify whether the schema has already been modified by examining the log file that is generated each time the schema is updated. A shortcut to the directory where the log file is located is placed on the Windows desktop.


Step 1 Confirm that all domain controllers are on line before making the schema updates. Schema replication will occur only when all domain controllers are on line.

Step 2 On the domain controller that is the schema master, log on by using an account that is a member of the Schema Administrators group.

Step 3 On Cisco Unity DVD 1 or CD 1, or from the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the directory ADSchemaSetup, and double-click ADSchemaSetup.exe.

Step 4 In the dialog box, double-click a row to choose the language in which you will view ADSchemaSetup.

Step 5 Check Exchange VPIM and Connection Networking Connector, uncheck the other check boxes, and then click OK.

Step 6 When the LDAP Data Interchange Format (LDIF) scripts have finished running, click OK.

Step 7 When the schema extension has finished, Ldif.log and LDif.err files are saved to the desktop. View the contents of the files to confirm that the extension completed successfully.

Step 8 Wait for the changes to the schema to replicate throughout the forest before adding information to the primary location and to delivery locations. Changes to the schema may take 15 minutes or more to replicate.


Note To determine whether changes have replicated and to force replication if necessary, use the Replication Monitor, which is available when you install Support Tools from the Windows 2000 compact disc.



Verifying the Recipient Policies or Creating a New One (Voice Connector Installations Only)

Depending on your Exchange organization, you may be able to use the default recipient policy for the Voice Connector Exchange mailbox, or you may need to create a new recipient policy.

To Check the Recipient Policies (Voice Connector Installations Only)


Step 1 On the Exchange server on which the Voice Connector will be installed, open the Exchange System Manager.

Step 2 Expand the Recipients tree in the left pane.

Step 3 Click Recipient Policies.

Step 4 In the right pane, right-click a recipient policy, and click Properties.

Step 5 Click the Email Addresses tab.

If the SMTP address is the same as the interoperability domain name that you previously chose in the "Determining the Interoperability Domain Name" section, close the Properties page, exit Exchange System Manager, and skip to the "Setting Up the Voice Connector for VPIM Networking" section.

Step 6 Close the Properties page, and repeat Step 4 and Step 5 for each recipient policy (including the default recipient policy).

If your chosen interoperability domain name does not match the SMTP address configured in any of the recipient polices, create a new recipient policy for the Voice Connector Exchange mailbox as described in the following "To Create a Recipient Policy for the Voice Connector Exchange Mailbox" procedure.


To Create a Recipient Policy for the Voice Connector Exchange Mailbox


Caution Consult the Exchange administrator for your organization before doing the following procedure. Misconfiguration of the Recipient Policies could result in problems routing other SMTP mail for the organization.

Step 1 In Exchange System Manager, right-click Recipient Policies and click New > Recipient Policy.

Step 2 In the New Policy window, confirm that Email Addresses is the only selection, and click OK.

Step 3 On the General tab, enter a meaningful name. Do not configure any Filter rules.

Step 4 On the Email Addresses (Policy) tab, click New.

Step 5 Select SMTP Address and click OK.

Step 6 In the Address field, enter the interoperability domain name that you previously chose in the "Determining the Interoperability Domain Name" section.

Step 7 Verify that the check box This Exchange Organization Is Responsible for All Mail Delivery to This Address is checked.

Step 8 Click OK.

Step 9 Check the check box next to the address that you added in Step 6, and verify that the row is highlighted.

Step 10 Click Set as Primary.

When you click Set as Primary, the new address should change to bold text.

Step 11 Click OK, and then click Yes to the warning about updating the corresponding recipient email addresses.


Setting Up the Voice Connector for VPIM Networking

Install the Voice Connector on any Exchange 2000 or Exchange 2003 server that is not part of an Exchange cluster (Microsoft does not support third-party connectors on an Exchange cluster server). Although the Voice Connector can be installed on the Cisco Unity server (when Exchange is also on the server), this is not recommended for performance reasons.


Caution Installing the Voice Connector on an Exchange 2007 server is not supported.


Caution Installing the Transport Event Sink on an Exchange 2007 server is not supported.

If the Exchange server on which the Voice Connector will be installed is in a different routing group than the Exchange servers on which Cisco Unity subscribers are homed, routing group connectors must be configured between the routing groups.

The Voice Connector service is automatically configured to log on as the account that is associated with the Exchange server on which the Voice Connector is installed (sometimes referred to as the "Local System" account). The account that the service logs on as should not be changed.


Caution Do not change the default permissions for the Local System account. In addition, do not change the permissions granted to Exchange administrative groups during Exchange installation. The Voice Connector logs on using that account, and if you change permissions, the Voice Connector may not function properly.

To set up VPIM Networking, the Voice Connector and the Transport Event Sink must be installed. Although you use the same Voice Connector installation program to install these components, where you install them depends on the network configuration.

In most cases, you install the Voice Connector on only one Exchange server, even if the system includes multiple Exchange servers. You install the Transport Event Sink on each Exchange server that will receive incoming VPIM messages.

The Voice Connector installation program does not prompt with a choice of languages for the installation; it always installs in English. To run the Voice Connector installation program by using one of the localized versions (FRA, DEU, or JPN) instead of English, see the "Running the Voice Connector Setup Program in Another Language" section.


Note The following procedure is for installing Voice Connector version 15.0(1), which ships with Cisco Unity 8.0(3). We recommend that you first check for a later version of the Voice Connector, and that you install that version instead. Follow the installation instructions in the release notes for the applicable version. To check for a later version, go to the Cisco Unity Voice Connector for Microsoft Exchange Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-voice-connector.


To Install the Voice Connector for Exchange 2000

First uninstall any previous versions of the Voice Connector. See the "Uninstalling the Cisco Unity Voice Connector" section on page 11-5.

As a best practice, back up the Exchange server before installing the Voice Connector.


Step 1 Log on to the Exchange server on which you are installing the Voice Connector.

Step 2 Disable any virus-scanning services on the Exchange server.

Step 3 If Cisco Unity is also on the server on which you are installing the Voice Connector, disable the Cisco Security Agent service, if applicable.

Step 4 If you are installing the Voice Connector from Cisco Unity DVD 1, insert the disc in the computer, and browse to the VoiceConnector-Ex2000 directory.

If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.

Step 5 Double-click Install.exe and then click Next.

Step 6 On the Voice Connector Setup Wizard Select Components dialog box, check the Voice Connector for Exchange check box.

Step 7 If you are setting up secure messaging and if Cisco Unity is not on the Exchange server, check the Cisco Secure Messaging Service check box.

Step 8 If you are installing the Transport Event Sink on the same server, check the Transport Event Sink for VPIM Networking check box.


Caution Installing the Transport Event Sink on an Exchange 2007 server is not supported.

Step 9 Click Next.

Step 10 If you did not check the Transport Event Sink for VPIM Networking check box in Step 8, skip to Step 11. Otherwise, do the following sub-steps:

a. On Transport Event Sink wizard welcome screen, click Next.

b. On the Choose Destination Folder dialog box, specify the destination, and click Next.

c. On the Enter Domain Name dialog box, enter the interoperability domain name that you previously decided on in the "Determining the Interoperability Domain Name" section.

d. Click Next.

e. On the Ready to Install the Program screen, click Install.

f. When the installation is complete, click Finish.

Step 11 On the Voice Connector for Exchange Welcome screen, click Next.

Step 12 On the Confirm SMTP Pickup Directory screen, click Next.

Step 13 In the Address Types dialog box, check the VPIM check box.

Step 14 If you are setting up the system to use other networking options, check the check boxes of the applicable address types.

Step 15 Click Next.

Step 16 On the Confirm Directory dialog box, click Next to launch the setup.

Step 17 If you did not check the Secure Messaging Service check box in Step 7, skip to Step 18. Otherwise, do the following sub-steps in the Cisco Unity Secure Messaging Service Setup wizard:

a. On the Welcome screen, click Next.

b. On the Choose Destination Folder dialog, specify the destination, and click Next.

c. Optionally, on the Message Security Settings screen, check the Enable Message Aging check box, and enter the number of days that encrypted messages should be available. (If the check box is unchecked, Cisco Unity will not limit the number of days for which encrypted messages will be available.)

d. Click Next.

e. On the Ready to Install Software screen, click Install.

Step 18 When the setup is complete, click Finish to exit Setup and restart the server.

Step 19 Enable virus-scanning and the Cisco Security Agent services, if applicable.


To view Voice Connector properties in Exchange System Manager, Windows Script Host version 5.6 or later must be installed on the Exchange server. (Note that if the Exchange server uses an earlier version of Windows Script Host, the Voice Connector functions properly, but you will not be able to view Voice Connector properties in Exchange System Manager.)

To Determine Whether 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 click Properties.

Step 3 Click the Version tab.

Step 4 In the Item Name list, click Product Version to view the version in the Value box.

Step 5 If the version is earlier than 5.6, update Windows Script Host so that the Voice Connector properties can be displayed in Exchange System Manager. (Go to the downloads page of the Microsoft website, and do a keyword search for Windows Script Host. Follow the installation instructions.)


To Verify the Voice Connector Installation

To verify that the Voice Connector for Exchange 2000 installed properly, verify that the Voice Connector service is running, and that the Voice Connector mailbox has been created.


Step 1 Open the Services applet on the Exchange server on which the Voice Connector is installed. (On the Windows Start menu, click Programs > Administrative Tools > Services.)

Step 2 Verify that the Status for the Exchange 2000 Voice Connector (<Server name>) service is Started, and that the Startup Type is set to Automatic.

Step 3 Exit the Services applet.

Step 4 Open Exchange System Manager on the Exchange server on which the Voice Connector is installed. (On the Windows Start menu, click Programs > Microsoft Exchange > Exchange System Manager.)

Step 5 In the tree in the left pane, expand the Servers container. If the organization properties at the top of the tree have been set such that administrative groups are displayed in the tree, the Servers container is nested within the administrative group container.

Step 6 Within the Servers container, expand the <Server name>\<Storage group>\Mailbox Store (<Server name>) container for the server on which the Voice Connector is installed.

Step 7 In the expanded tree, click Mailboxes.

In the right pane, you should see the mailbox for "Exchange 2000 Voice Connector (<Server name>)" or "AvExchangeIVC_<Server name>." (The name changes from "AvExchangeIVC_<Server name>" to "Exchange 2000 Voice Connector (<Server name>)" after you run Cleanup Agent.)

Step 8 Exit Exchange System Manager.


To Verify or Set the Recipient Policy for the Voice Connector Exchange Mailbox


Step 1 On the Exchange server on which the Voice Connector is installed, open the Exchange System Manager.

Step 2 Expand the Connectors container in the left-hand pane.

Step 3 Right-click Exchange 2000 Voice Connector (<Server name>), and select Properties.

Step 4 If you are using the default recipient policy for the Voice Connector Exchange mailbox:

a. Verify that "Recipient Policy to Calculate Enterprise GDI for MTS-IDs" on the bottom of the Options tab is set to Default Policy.

b. Close the properties page, exit Exchange System Manager, and go to the "Customizing the Primary Location" section.

If you created a new recipient policy for the Voice Connector Exchange mailbox:

a. Choose the new recipient policy from the "Recipient Policy to Calculate Enterprise GDI for MTS-IDs" list on the bottom of the Options tab.

b. Click OK and exit Exchange System Manager.


The following procedure is for installing the Transport Event Sink on a separate Exchange server from the server on which the Voice Connector is installed. The procedure is for running the setup program for Voice Connector version 15.0(1), which ships with Cisco Unity 8.0(3). We recommend that you first check for a later version of the Voice Connector, and that you install the Transport Event Sink from that version instead. Follow the installation instructions in the release notes for the applicable version. To check for a later version, go to the Cisco Unity Voice Connector for Exchange Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-voice-connector.

First uninstall any previous versions of the Transport Event Sink. See the "Uninstalling the Cisco Unity Voice Connector" section on page 11-5.


Caution Installing the Transport Event Sink on an Exchange 2007 server is not supported.

To Install the Transport Event Sink on a Separate Exchange Server


Step 1 Log on to the Exchange server on which you are installing the Transport Event Sink.

Step 2 Disable any virus-scanning services on the Exchange server.

Step 3 If Cisco Unity is also on the server on which you are installing the Transport Event Sink, disable the Cisco Security Agent service, if applicable.

Step 4 If you are installing the Transport Event Sink by running the Voice Connector installation program from a Cisco Unity DVD or CD, insert the disc in the computer, and browse to the VoiceConnector-Ex2000 directory.

If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.

Step 5 Double-click Install.exe, and click Next.

Step 6 On the Voice Connector Setup Wizard Select Components dialog box, check the Transport Event Sink for VPIM Networking check box, and click Next.

Step 7 On the Transport Event Sink wizard welcome screen, click Next.

Step 8 On the Choose Destination Folder dialog box, specify the destination, and click Next.

Step 9 On the Enter Domain Name dialog box, follow the instructions to specify the domain. (Typically, the domain entered is the same as the interoperability domain that will be entered on the Primary Location page. Note that the domain does not have to be the same domain as that of the server on which the Transport Event Sink is being installed.)

Step 10 Click Next.

Step 11 On the Ready to Install the Program screen, click Install.

Step 12 When the installation is complete, click Finish to exit Setup and restart the server.

Step 13 Enable virus-scanning and the Cisco Security Agent services, if applicable.


Controlling What Happens to Messages That Cannot Be Delivered (Voice Connector Installations Only)

When the Voice Connector encounters a message that cannot be delivered, and the sender information is incomplete or incorrect such that a nondelivery receipt (NDR) cannot be sent to the message sender, the Voice Connector saves the message in the Archive folder in the Voice Connector mailbox. The Archive folder is accessible only when using tools available from Microsoft. If you want more control over archived messages, you can add to the registry either the AliasToForwardBadMailsTo value or the DeleteArchiveFolderMessages value (but not both).

When you add the AliasToForwardBadMailsTo registry value and set it to the SMTP address of a user or distribution list, when the Voice Connector encounters a problematic message, information about the message is sent to the specified address instead of being saved in the Archive folder. When a problematic VPIM message is encountered, the informational message that the Voice Connector sends to the specified user (or distribution list) includes the MIME header of the problematic message as a text attachment. The MIME header contains the "To" and "From" addresses, which may help in troubleshooting the problem.

When you add the DeleteArchiveFolderMessages registry value and set it to 1, the Voice Connector continues to save problematic messages in the Archive folder, but periodically, the Voice Connector automatically deletes the messages in the Archive folder.

When a message is saved to the Archive folder or sent to the address specified in the AliasToForwardBadMailsTo registry value, an entry is made in the Voice Connector log file. (The information is logged when the Voice Connector properties are set to the default logging level or a higher logging level.) The Voice Connector logs are located on the Exchange server on which the Voice Connector is installed in the directory <ExchangeServerPath>\VoiceGateway\LogFiles. The files are named in the format GwIvc_<YyMmDd >.log, where Yy in the year, Mm is the month, and Dd is the day.

To add the registry values, do the following procedure.

To Control What Happens to Messages That Cannot Be Delivered (Voice Connector Installations Only)


Step 1 On the Exchange server on which the Voice Connector is installed, start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (See the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 3 Expand the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvIvc

Step 4 If you want information about the messages to be sent to a user or distribution list instead of being saved to the Archive folder, do the following sub-steps. Otherwise, skip to Step 5.

a. On the Edit menu, click New > String Value.

b. Enter AliasToForwardBadMailsTo as the value name.

c. Double-click AliasToForwardBadMailsTo.

d. In the Edit String dialog box, enter the SMTP address of the recipient (for example unityadministrator@company.com). This must be the SMTP address of a user, contact, or distribution list object in Exchange. An email with the failed message and information about the message will be sent to this address.

e. Click OK.

f. Exit Regedit.

g. Skip to Step 6.

Step 5 If you want messages that are saved in the Archive folder to be automatically deleted, do the following sub-steps:

a. On the Edit menu, click New > DWORD Value.

b. Enter DeleteArchiveFolderMessages as the value name.

c. Double-click DeleteArchiveFolderMessages.

d. In the Edit DWORD dialog box, enter 1.

e. Click OK.

f. Exit Regedit.

Step 6 Open the Services MMC on the Exchange server on which the Voice Connector is installed. (On the Windows Start menu, click Programs > Administrative Tools > Services.)

Step 7 Right-click Exchange 2000 Voice Connector (<Server name>), and click Restart.

Step 8 Exit the Services MMC.


Creating the UVPIM Account by Using ConfigMgr.exe (Optional)

If you plan to configure Cisco Unity to automatically update the VPIM subscriber directory based on the information received in incoming VPIM messages, you must first configure the bridgehead server by running ConfigMgr.exe with the Create VPIM Account option. (Note that the use of automatic directory updates is optional, and that this procedure and the steps for configuring automatic updates can be done at any time after VPIM Networking has been set up, if you later decide to use this functionality.) To enable the processing of directory update information, ConfigMgr.exe does the following:

Configures the server to automatically start and stop the CsVPIMConnector service.

Configures the Cisco Unity Administrator to enable the link to the Delivery Locations > Subscriber Creation pages.

Creates the UVPIM mailbox to which the messaging gateway component (Interoperability Gateway or Voice Connector) will deliver directory messages for the CsVPIMConnector service to process. Note that the UVPIM mailbox is actually homed on the Exchange server that the Cisco Unity Bridgehead server is connected to. This server is also known as the partner Exchange server; it was selected in the Cisco Unity Server Message Store Configuration wizard during setup.

Do one of the following two procedures, depending on the version of Exchange that the partner Exchange server is running.

To Create the UVPIM Account When the Partner Exchange Server Is Running Exchange 2000 or Exchange 2003


Step 1 On the VPIM bridgehead Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location is CommServer).

Step 2 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 3 Click Create VPIM Dir Account.

Step 4 Click OK in the dialog box that displays after the configuration has completed.

Step 5 Close the ConfigMgr dialog box.

Step 6 On the Cisco Unity server, start the Services tool. (On the Windows Start menu, click Programs > Administrative Tools > Services.)

Step 7 Right-click AvNotifierMgr, and select Restart.


Note The CPU usage on the Cisco Unity server will spike for a few minutes while the AvNotifierMgr reinitializes connections with subscriber mailboxes.


Step 8 Close the Services tool.


To Create the UVPIM Account When the Partner Exchange Server Is Running Exchange 2007


Step 1 On the VPIM bridgehead Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location is CommServer).

Step 2 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 3 Click Create and Configure VPIM Account and Mailbox.

Step 4 In the Create the PowerShell Script That Creates the VPIM Account and Mailbox dialog box, choose the path and file name for the script that will create the VPIM account.

You must run the script on the partner server or another server on which Exchange Management Shell is installed, so choose one of the following locations to save the script:

The server that you will run the script on.

A network location that is accessible to that server.

A removeable disk.

Step 5 Click Create Script.

Step 6 Click OK.

Step 7 Click Exit to close ConfigMgr.

Step 8 Log on to the Exchange 2007 server on which you want to run the script by using an account that has the right to run a PowerShell script.

Step 9 If necessary, copy the script locally to the Exchange server.

Step 10 Run Exchange Management Shell. (From the Start menu, click All Program > Microsoft Exchange Server 2007 > Exchange Management Shell.)

Step 11 Run the script. In the Exchange Management Shell window, enter the full pathname of script. For example:

d:\scripts\UVpim_<ServerName>.PS1

Alternatively, you can change to the directory where the script is located by using the "cd" command, and then run the script by entering:

.\UVpim_<ServerName>.PS1

For more information, refer to Microsoft documentation.

Step 12 On the VPIM bridgehead Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location is CommServer).

Step 13 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 14 Click Create and Configure VPIM Account and Mailbox.

Step 15 Click OK.

Step 16 Click Exit to close ConfigMgr.

Step 17 On the Cisco Unity server, start the Services tool. (On the Windows Start menu, click Programs > Administrative Tools > Services.)

Step 18 Right-click AvNotifierMgr, and select Restart.


Note The CPU usage on the Cisco Unity server will spike for a few minutes while the AvNotifierMgr reinitializes connections with subscriber mailboxes.


Step 19 Close the Services tool.


Be sure to let anyone who administers Active Directory and Exchange know about the UVPIM mailbox so that it is not moved or deleted by mistake. To avoid inadvertently moving or deleting the UVPIM mailbox, consider changing the Exchange display name so that the account is more clearly identified to you or the Exchange administrator as requiring "special" treatment. Note also that when it is created, the UVPIM account is hidden from the Outlook address book.

Customizing the Primary Location

If your installation consists of multiple Cisco Unity servers networked via Digital Networking, you may have already customized the primary location. In this case, verify that the SMTP Domain Name has been entered on the primary locations of all Cisco Unity servers networked via Digital Networking. Otherwise, VPIM Networking will not work for the subscribers on the other Cisco Unity servers.

For detailed information about the settings, see the "Primary Location Profile Settings in Cisco Unity 8.x" section on page 10-1.

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 For the Dialing Domain name:

If your installation consists of only one Cisco Unity server, and if you plan to enable identified subscriber messaging to include VPIM subscribers, enter a dialing domain name.

If your installation consists of multiple Cisco Unity servers networked via Digital Networking, and if this server is integrated with the same phone system as other networked Cisco Unity servers, you may have already added this server to a dialing domain. If not, enter the dialing domain name, or select it from the available list. The list contains names of dialing domain names already configured on at least one other Cisco Unity server in the network.

Note that the dialing domain name is case sensitive and must be entered exactly the same on all of the servers. To ensure that all servers are correctly added to the same dialing domain, enter the dialing domain name on one Cisco Unity server and wait for the name to replicate to the other Cisco Unity servers. By doing so, you also confirm that replication is working correctly among the servers. 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 In the SMTP Domain Name field, enter the interoperability domain name that you previously chose in the "Determining the Interoperability Domain Name" section.

Step 7 Click the Save icon.


Creating VPIM Delivery Locations

Create a VPIM delivery location on the bridgehead Cisco Unity server for each remote voice messaging system to which subscribers will send messages. If Cisco Unity will be messaging with a large number of voice messaging systems, you may prefer to configure only a few delivery locations at this time and proceed with the rest of the setup. After verifying that messaging works correctly between Cisco Unity and the voice messaging systems for which delivery locations have been configured, you can create the rest of the delivery locations.

Carefully consider the Dial ID that you will assign to the delivery location. See the "Guidelines for Assigning Dial IDs and Extensions" section on page 10-2 for detailed information about choosing a Dial ID.

You can create VPIM delivery locations by using the Cisco Unity Administrator or the Cisco Unity Bulk Location Import wizard. See the following sections:

Using the Cisco Unity Administrator to Create VPIM Delivery Locations

Using the Cisco Unity Bulk Import Wizard to Create VPIM Delivery Locations

Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard

Using the Cisco Unity Administrator to Create VPIM Delivery Locations

You can create VPIM delivery locations one at a time by using the Cisco Unity Administrator.

To Create VPIM Delivery Locations by Using the Cisco Unity Administrator


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 to blind address messages to recipients at this location.

Step 5 Select VPIM as the Destination Type for the location.

Step 6 Click Add.

Step 7 Record a voice name for the location.

Step 8 Enter the Internet-addressable SMTP domain name of the system on the TCP/IP network that handles messages for the remote voice messaging system.

Step 9 If needed to accommodate your numbering plan, or if there is more than one VPIM delivery location with the same domain name, enter a number in the Remote Phone Prefix field.


Note Subscribers do not enter this prefix when addressing messages. However, on outgoing messages, the messaging gateway component (Interoperability Gateway or Voice Connector) adds the prefix to the beginning of the recipient mailbox number to form the To address. On incoming messages, the messaging gateway component expects this same prefix to be the leading digits of the From mailbox number and removes these digits before determining the sending mailbox number.


Step 10 If needed to accommodate your numbering plan, enter a number in the Cisco Unity Phone Prefix field.


Note On outgoing messages, the messaging gateway component adds this prefix to the beginning of the sender mailbox number to form the From address. On incoming messages, the messaging gateway component expects this same prefix to be the leading digits of the To mailbox number and removes these digits prior to determining the matching Cisco Unity recipient ID.


Step 11 Indicate whether incoming messages from this VPIM location should be converted to another audio format.

Step 12 Indicate whether outbound messages to this VPIM location should be converted to another audio format. If the remote system is Cisco Unity, typically you choose Do Convert Outgoing Messages. For systems other than Cisco Unity, typically you choose G.726.

Step 13 Optionally, check the Sender's Recorded Name and/or Sender's vCard check boxes. Some systems have the capability of using this information to create directory entries.

Step 14 Optionally, check any or all of the Remove Message Subject, Remove All Text Attachments, and Remove All Fax Attachments check boxes to further configure messages when they are sent from Cisco Unity to this delivery location.

Step 15 If you are using Secure Messaging, indicate whether to have incoming messages encrypted and outgoing messages decrypted.

Step 16 Click the Save icon.


Using the Cisco Unity Bulk Import Wizard to Create VPIM Delivery Locations

The Cisco Unity Bulk Import wizard allows you to create or modify multiple delivery locations at once by importing data in a CSV file. If you have already created delivery locations, you can run Cisco Unity Bulk Import to export the data about the delivery locations to a CSV file.

Use the following procedure to prepare your CSV file. To learn more about preparing a CSV file for use with the Cisco Unity Bulk Import wizard—including information on the required and optional column headers for your CSV file—see the Cisco Unity Bulk Import wizard Help.

To Prepare a CSV File for Creating VPIM Delivery Locations


Step 1 Create a CSV file in a spreadsheet application (or another applicable application) on the Cisco Unity server, or in a directory that you can browse to from the server.

Step 2 Enter the required column headers in the first row. Column headers must be in uppercase, separated by commas, and spelled as indicated below:

DTMF_ACCESS_ID, DISPLAY_NAME, SMTP_DOMAIN_NAME

Step 3 If desired, add optional column headers to the first row. Be sure to separate the column headers with commas.

Step 4 Add the data for the delivery locations in the subsequent rows. When finished:

Confirm that each row contains the applicable data corresponding to each column header.

Confirm that the data is separated by commas, and that no tabs, spaces, or semicolons separate the data in the file.

If any data includes a space, quotes, or commas, contain it within quotes.

Note that every row does not have to contain data in the optional columns.

Step 5 Save the file as a CSV file.

Step 6 Continue with the following "To Create VPIM Delivery Locations by Using the Cisco Unity Bulk Import Wizard" procedure.


To Create VPIM Delivery Locations by Using the Cisco Unity Bulk Import Wizard


Step 1 Before you run the Cisco Unity Bulk Import wizard, disable virus-scanning services and intrusion-detection software on the Cisco Unity server, if applicable. Otherwise, the Cisco Unity Bulk Import wizard may run slowly.

Step 2 On the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Bulk Import.

Step 3 On the Welcome page, click Next.

Step 4 On the Select Import Operation, in the Locations section, click CSV File, and then click Next.

Step 5 On the Select Location Operation page, click Create New Locations, and then click Next.

Step 6 On the Type of Locations page, click VPIM, and then click Next.

Step 7 On the Files page, specify the name and location of the input file.

Step 8 Specify the name and location of the output file, or use the default location and file name, which is based on the input file. For example, if the input file is C:\Temp\VPIM_Locations.csv, the default output file will be C:\Temp\VPIM_Locations.out.csv.

Step 9 Click Next to proceed to the Valid Location Data page, which displays a table with validated rows of data from the input CSV file. If you do not want to import a row of data, uncheck the check box in the first column of the row.

If errors were found in any of the rows, you can click the Errors link at the bottom of the page to open the output CSV file to correct the errors, or you can ignore the errors for now and proceed with the import.

Step 10 Click Next to start the import process and display the Creating Locations page, which provides status information about the import.

Step 11 When the delivery locations are created, click Next to display the Cisco Unity Bulk Import Wizard Finished page, which displays summary information.

Step 12 If you had import errors, continue with the following "To Correct Errors That Occurred When Importing Delivery Location Data from a CSV File" procedure.


To Correct Errors That Occurred When Importing Delivery Location Data from a CSV File


Step 1 Browse to the directory location of the output file that you specified during the import. (The default location and file name is based on the input file. For example, if the input file is C:\Temp\VPIM_Locations.csv, the default output file will be C:\Temp\VPIM_Locations.out.csv.)

This file contains all of the records that were not imported.

Step 2 Use a text editor to open the output file.

Step 3 Correct any records in the output file by using the error information listed in the Results column of the file.

Step 4 When you have finished editing the output file, save it as a CSV file with a new name.

Step 5 Run the Cisco Unity Bulk Import wizard again with the new CSV file.

Step 6 Repeat this procedure until all delivery locations are created without error.


Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard

If you want to use the Cisco Unity Bulk Import wizard to make modifications to existing delivery locations, you will need to create a CSV file for the modifications. We recommend that you run the Cisco Unity Bulk Import wizard to export your existing delivery location data to a CSV file, and then edit the CSV file to use for the modification.

Note that the DTMF_ACCESS_ID column is used as the primary key to find the existing delivery location, and therefore it cannot be modified by the Cisco Unity Bulk Import wizard.

Creating VPIM Subscribers

You may prefer to create only a few VPIM subscribers at this point, for testing purposes, until you verify that Cisco Unity and the remote system can successfully exchange messages. After you have confirmed that messaging between Cisco Unity and the remote system is working correctly, you can finish creating the VPIM subscribers. Note that you must first create VPIM delivery locations before creating VPIM subscribers, and the VPIM subscribers must be created on the same Cisco Unity server as the VPIM delivery locations.

If you choose not to create VPIM subscribers at this point, you can still configure Cisco Unity to automatically create, update, and delete VPIM subscriber records as VPIM messages are received from users on remote systems. With this approach, subscribers may initially need to use blind addressing to address messages to users on remote systems, but as incoming messages and replies to outgoing messages are received from those users, the directory of VPIM subscribers will be populated based on the vCard or header information in those messages. Alternatively, you can use a combination of pre-populated VPIM subscribers and automatic updates to avoid the need to use blind addressing and to keep the VPIM subscriber directory updated when changes occur to active users on the remote system.

You can create VPIM 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 VPIM Subscriber Accounts

After Creating Subscriber Accounts

Before Creating Subscriber Accounts

This section lists—in order—the issues that you must consider before creating VPIM subscribers. VPIM subscribers can be created only on a Cisco Unity Bridgehead server. Do the following tasks on the Cisco Unity Bridgehead server where you will be adding the VPIM subscribers.

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 "To Check Cisco Unity Setup and Permissions by Using the Cisco Unity SysCheck Tool" procedure.

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 VPIM 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 that you can modify. You can also create new classes of service. For details, see the "Managing Classes of Service in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

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 that you can modify.

Although most restriction table settings do not apply to VPIM subscribers because they cannot log on to Cisco Unity or use the Cisco Personal Communications Assistant (PCA), administrators can enter call transfer numbers for VPIM subscribers. For security purposes, you should modify the restriction table used for transfers in the COS to which VPIM subscribers belong, as necessary. For details, see the "Managing Restriction Tables in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

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, see the "Managing Distribution Lists in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

Public distribution lists correspond to distribution groups in Active Directory. The distribution lists are listed in the address book for Microsoft Outlook (or other email client), unless they are explicitly hidden. To help prevent email from being sent to VPIM subscribers, you may want to create lists that contain only VPIM subscribers, and hide these distribution lists from the Outlook address book. The option to hide distribution lists is available on the Subscribers > Public Distribution Lists > Profile page in the Cisco Unity Administrator.

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 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 that you can modify, and you can create an unlimited number of additional templates. For more details, see the "Managing Subscriber Templates in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

VPIM subscribers correspond to contacts in Active Directory. The contacts are listed in the address book for Microsoft Outlook (or other email client), unless they are explicitly hidden. You may prefer that the associated contacts do not appear in the Outlook address book at all, or you may want to alter how contacts appear in the Outlook address book. See the "Determining How VPIM Subscribers Appear in the Outlook Address Book" section for details.

You can also specify the template that Cisco Unity uses when creating VPIM subscribers based on information from incoming VPIM messages, if automatic directory updates are enabled for a particular delivery location. You can use an existing template, or you may wish to create a template specifically for this purpose. For more information, see the "Customizing VPIM Subscriber Directory Update Settings" section.


Note The System Administration Guide for Cisco Unity Release 8.x is available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.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 the same time by importing user data from a comma-separated value (CSV) file. CSV is a common text file format for moving data from one data store to another. As long as the user data contained in the CSV file is formatted correctly, you can use it to create new Active Directory contacts at the same time that you create VPIM subscriber accounts, or you can use it to create VPIM subscriber accounts with existing Active Directory contact data.

If you choose to create VPIM subscriber accounts with existing Active Directory contact data, note that the email addresses for the imported contacts are overwritten with extension addresses that are used for addressing voice messages to the remote voice messaging systems. Thus, the imported objects can no longer be used for outbound message addressing to remote email addresses.

Use the following procedure to prepare your CSV file. To learn more about preparing a CSV file for use with the Cisco Unity Bulk Import wizard—including information on the required and optional column headers for your CSV file—see Cisco Unity Bulk Import wizard Help.

To Prepare a CSV File for Creating VPIM Subscriber Accounts


Step 1 Save the data that 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 Bridgehead server or to a directory 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 the characters 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, the extension (DTMF_ACCESS_ID), and then by the remote mailbox number (REMOTE_USER_ID):

Abade,Alex,2001,3000
Bader,Kelly,2002,3100
Campbell,Terry,2003,3200
Cho,Li,2004,3300

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,DTMF_ACCESS_ID,REMOTE_USER_ID


Note The examples in this procedure illustrate how to set up a CSV file so that the Cisco Unity Bulk Import wizard creates subscriber accounts and new contacts at the same time. If you choose to create new subscriber accounts with existing contact data, you must also include the ALIAS column header and data in your CSV file.


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 every row does not have to contain data for any optional column headers.

Any data that includes a space, quotes, or commas is contained within quotes.

Step 7 To associate the VPIM subscribers in the CSV file with a delivery location, you can either choose from the list of defined delivery locations presented by the Cisco Unity Bulk Import wizard during the import, or you can add the DELIVERY_LOCATION_ID column to the CSV file.

The DELIVERY_LOCATION_ID column contains the dial ID of a delivery location with which the external subscriber will be associated. This value corresponds to the Dial ID field on the Network > Delivery Locations > Profile Page in the Cisco Unity Administrator. If this column header is omitted, or if a row does not contain a value, the delivery location that the Cisco Unity Bulk Import wizard prompts for is used as a default. You can import external subscribers for multiple delivery locations by using one CSV file.

Step 8 To help prevent others from sending email to VPIM subscribers, you may want to include the HIDE_IN_ADDRESS_BOOK column header, and enter a 1 (one) in each row of subscriber data.

A value of 1 indicates that subscribers will be hidden from the email address book; a value of 0 indicates that subscribers will be displayed.

Step 9 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 10 Confirm that each row contains the appropriate data corresponding to each column header.

Step 11 Save the file as a CSV file.

Step 12 Continue with the following "To Create VPIM Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard" procedure.


To Create VPIM Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard


Step 1 Disable virus-scanning services and intrusion-detection software on the bridgehead Cisco Unity server, if applicable. Otherwise, the Cisco Unity Bulk Import wizard may run slowly. See the Cisco Unity Bulk Import wizard Help for procedures.

Step 2 On the bridgehead Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Bulk Import.

Step 3 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 4 When prompted to choose the type of subscriber that you want to create, click VPIM.

Step 5 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 6 When the subscriber accounts are created, click Finish.

Step 7 If you had import errors, but in Step 5 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 a row in a CSV file. When you have corrected that error, the wizard may detect additional errors in the same 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, do the following "To Correct Errors That Occurred When Importing Data from a CSV File" procedure.

To Correct Errors That Occurred When Importing Data from a CSV File


Step 1 Browse to the directory that contains 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 Browse 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 VPIM Subscriber Accounts

By using the Cisco Unity Administrator, you can create VPIM subscriber accounts one at a time. When you add a new VPIM subscriber account, Cisco Unity creates a contact in Active Directory.

To create an VPIM subscriber account, do the following "To Add a New VPIM Subscriber by Using the Cisco Unity Administrator" procedure.

To Add a New VPIM Subscriber by Using the Cisco Unity Administrator


Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.

Step 2 Click the Add icon.

Step 3 Click New and select VPIM from the list.

Step 4 Enter the First Name and Last Name.

Step 5 Enter the Extension of the VPIM subscriber on Cisco Unity. This is the number that Cisco Unity subscribers use when addressing a message to this VPIM subscriber.

Step 6 Select the Subscriber Template to use.

Step 7 Enter the Remote Mailbox Number, which is the number that the remote voice messaging system uses to route messages to this VPIM subscriber.

Step 8 Select the Delivery Location with which the subscriber is associated.

Step 9 Click Add.

Step 10 On the subscriber record, customize settings as applicable, and then click the Save icon.


After Creating Subscriber Accounts

After creating VPIM subscriber accounts, consider the following:

It takes a few minutes for the newly-created subscriber account to be available to receive messages.

You can make changes to subscriber settings for individual accounts in the Cisco Unity Administrator.

When you want to modify unique subscriber settings—such as primary or alternate extensions—for multiple subscribers at once, you can (re)run the Cisco Unity Bulk Import wizard. To learn more, see the Cisco Unity Bulk Import wizard Help.

When a subscriber leaves the organization or otherwise no longer needs a Cisco Unity account, you can delete the subscriber account. See the "Deleting VPIM Subscribers" section for details.

Customizing VPIM Subscriber Directory Update Settings

In addition to manually creating, modifying, and deleting VPIM subscribers, you can configure Cisco Unity to automatically update records in the VPIM subscriber directory based on information contained in incoming VPIM messages. The settings that control whether or not the creation, modification, and deletion actions occur automatically, and how the incoming information is used to create or modify a record, can be individually configured for each delivery location. By default, no automatic directory updates will occur for any VPIM delivery locations.

Depending on the Subscriber Creation settings you choose for each delivery location, Cisco Unity will use information either from the header of an incoming VPIM message, or from a vCard attachment included with the message (if more than one vCard attachment is included, only the vCard in the most recent portion of the message will be used). If a VPIM message is received from a sender on a delivery location that is configured to allow automatic VPIM subscriber creation, and no existing VPIM subscriber matches the information of the sender, a new VPIM subscriber record will be created, provided that the VPIM message contains:

a phone number

a text name

a domain name

a recorded voice name (when required, based on the delivery location configuration)

Additional Subscriber Creation settings on the Delivery Location page allow you to specify which template to use when creating VPIM subscribers, how to map the parsed text name of the VPIM subscriber to a first name, last name, and display name, and how to map the phone number to an extension.

If a VPIM message is received from a sender on a delivery location that is configured to allow automatic VPIM subscriber modification, and an existing VPIM subscriber matches the sender information, the VPIM subscriber may be updated. You can choose whether VPIM subscriber information is updated each time a message is received from a VPIM subscriber, or only when a message is received from a VPIM subscriber whose text name has changed since the directory entry was created. You can also decide whether or not to allow an update to the display name when a modification is made.

If a message from a Cisco Unity subscriber to a VPIM subscriber results in a non-delivery receipt (NDR), indicating that the message was undeliverable because the intended recipient does not exist (SMTP 5.1.1), and if the delivery location is configured to allow automatic VPIM subscriber deletion, the VPIM subscriber will be deleted.

For additional information on how Cisco Unity uses the information from incoming VPIM messages and NDRs to create, modify, and delete VPIM subscribers, see the "Automatic VPIM Subscriber Directory Updates" section.

You can update the VPIM delivery location subscriber creation settings by using the Cisco Unity Administrator or the Cisco Unity Bulk Location Import wizard. See the following sections:

Before Configuring VPIM Subscriber Creation Settings

Using the Cisco Unity Administrator to Configure VPIM Subscriber Creation Settings

Using the Cisco Unity Bulk Import Wizard to Configure VPIM Subscriber Creation Settings

Changing the AD Location in Which Automatically Created VPIM Subscribers Are Created (Optional)

Before Configuring VPIM Subscriber Creation Settings

Before configuring the VPIM delivery location subscriber creation settings, consider the following:

If an incoming VPIM message or NDR does not contain a vCard, and the delivery location is configured to use the vCard as the source of directory update information, no update will be made.

If you have pre-populated VPIM subscribers with specific display names that should not be changed, but want to allow automatic modification of other fields in the subscriber record, you may choose to keep the Allow VPIM Subscriber Display Name Updates check box unchecked. In this case, the first name, last name, and spoken name of a subscriber may be modified during an automatic update. This may result in a mismatch if the spoken name is updated and the display name is not.

When the Allow VPIM Subscribers Without Recorded Voice Names check box is unchecked, new VPIM subscribers will not be created for incoming messages that do not contain an Originator-Spoken-Name attachment. In addition, if automatic modification of VPIM subscribers is enabled, and if the sender of an incoming message matches an existing VPIM subscriber, the VPIM subscriber will be deleted if the attachment is not present in the message.

When the Allow VPIM Subscribers Without Recorded Voice Names check box is checked, and automatic modification of VPIM subscribers is enabled, if the sender of an incoming message that does not include an Originator-Spoken-Name attachment matches an existing VPIM subscriber, the existing recorded voice name will be deleted.

If the phone number in an incoming message can not be successfully mapped to an extension by using the option selected for the Map VPIM Subscriber Extensions To setting, a VPIM subscriber will not be created for the sender.

When determining whether to use vCards or message headers as the source from which to obtain the VPIM subscriber information, consider the following:

Not all VPIM-compliant voice messaging systems send vCards with every message; for such systems, use message headers as the source.

Every VPIM message includes a message header, but it is possible that the header may not include the text name of the sender, in which case it would be necessary to use vCards for obtaining sender information.

vCards can provide information about the sender in a more detailed format. For example, the vCard can include names already parsed into first name and last name, so that Cisco Unity does not need to make a determination as to how to parse a single name field from the message header. The vCard may also include a phone number that could be mapped directly to the extension of the VPIM subscriber, so that Cisco Unity does not need to parse the header information to create an extension in the format desired. Or, it may contain a distinct number that it would not be possible for Cisco Unity to generate from the message header based on the set of rules available.

If the remote voice messaging system is also a Cisco Unity server, it is possible to turn on or off the transmission of vCards, so the configuration of the locations should be coordinated between systems.

Using the Cisco Unity Administrator to Configure VPIM Subscriber Creation Settings

After you create a delivery location, you can configure the settings that control automatic directory updates for that specific delivery location by using the Cisco Unity Administrator.

To Configure VPIM Subscriber Creation Settings by Using the Cisco Unity Administrator


Step 1 In the Cisco Unity Administrator, go to the Network > Delivery Locations > Subscriber Creation page.

Step 2 Check the check box for each type of update—creation, modification, or deletion—that you would like to allow for this location. If you choose to enable automatic modification of VPIM subscribers for this location, indicate whether modifications should occur:

Only When the Text Name Changes—The VPIM subscriber record will be updated only when the text name received in the VPIM message does not match the name of the VPIM subscriber.

With Each VPIM Message—Every incoming VPIM message from a remote sender at this delivery location will result in an update to the corresponding VPIM subscriber.

Step 3 Select an option for the source from which to obtain the VPIM subscriber information—either the vCard or the message headers.

Step 4 Select the template on which to base newly created VPIM subscriber accounts.

Step 5 Indicate whether VPIM subscriber display name updates should be allowed.

Step 6 Indicate whether VPIM subscribers without recorded voice names should be allowed.

Step 7 Indicate how text names that do not contain commas should be parsed into first and last names for auto-created VPIM subscribers, if the remote messaging system transmits the text name as one single field. Select one of the following:

Treat as FirstName LastName

Treat as LastName FirstName

Step 8 Indicate how text names on incoming messages should be mapped to the display names for auto-created VPIM subscriber entries. Select one of the following:

Directly to VPIM Subscriber Display Names—Click this option to have the display names for VPIM subscribers match their corresponding text names.

Custom Mapping—Click this option and enter a rule that defines how text names will be mapped to VPIM subscriber display names. Enter the tokens <FirstName>, <LastName>, or <TextName> in any combination, along with any additional text. Always precede <FirstName>, <LastName>, or <TextName> with a space, comma, or semicolon unless it appears at the beginning of the rule. In addition, always follow one of these tokens with a space, comma or semicolon unless it appears at the end of the rule. No additional characters are required at the beginning or end of a rule.

Step 9 Indicate how the phone number on incoming messages should be mapped to the extension for auto-created VPIM subscribers. Select one of the following:

Phone Number—Click this option for extensions to be the same as the phone numbers that are parsed from incoming VPIM messages.

Phone Number - Remote Phone Prefix—Click this option for extensions to be formed by removing the remote phone prefix from the beginning of the phone number.

Location Dial ID + Phone Number—Click this option for extensions to be formed by adding the location Dial ID in front of the phone number.

Phone Number + Location Dial ID - Remote Phone Prefix—Click this option for extensions to be formed by removing the remote phone prefix from the beginning of the phone number, and then adding the location Dial ID in front of the resulting number.

This mapping is applied only to create the extension for the VPIM subscriber; it is not applied to the remote mailbox number.

Step 10 Click the Save icon.


Using the Cisco Unity Bulk Import Wizard to Configure VPIM Subscriber Creation Settings

After you have created delivery locations and reviewed the considerations for creating subscriber accounts, you can customize the subscriber creation settings that control automatic VPIM subscriber directory updates for multiple existing delivery locations by using the Cisco Unity Bulk Import wizard. Or, you can create new delivery locations and customize the subscriber creation settings for the new locations at the same time. In either case, you configure each of the subscriber creation settings by including an optional column in the CSV file that you create for use in the wizard (the columns are not required when creating or modifying a delivery location, but if you include any one of the subscriber creation columns, you must include them all).

See the Cisco Unity Bulk Import wizard Help for a description of each of the optional columns that control subscriber creation. For more information on using the wizard to create or modify delivery locations, see the "Using the Cisco Unity Bulk Import Wizard to Create VPIM Delivery Locations" section or the "Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard" section.

Changing the AD Location in Which Automatically Created VPIM Subscribers Are Created (Optional)

By default, all automatically created VPIM subscribers are placed in the Active Directory container that was specified in the Message Store Configuration wizard during Setup. If you want to have auto-created VPIM subscribers created in a different location, you can configure Cisco Unity to use any properly configured container or organizational unit. Separating the auto-created contacts from other AD objects allows you to more easily monitor and control these objects. However, we do not recommend that you attempt to change the container used for subscriber creation unless you are familiar with Active Directory objects and permissions.

If you choose to change the container for auto-created contacts, note the following:

New VPIM subscribers that are created manually by using the Cisco Unity Administrator will still be created in the default AD container that was selected in the Message Store Configuration wizard.

Existing VPIM subscribers that have been manually created will not be relocated to the container selected for auto-created contacts. However, if an automatic modification or deletion is initiated for one of these accounts, Cisco Unity will update the account properly in the default container.

If auto-created VPIM subscribers have already been created in the current container, or you wish to move existing manually created VPIM subscribers, you can move the existing contacts to the new container by using Active Directory Users and Computers.

Use the following task list to set up the container or organizational unit and to configure Cisco Unity to use it when automatically creating VPIM subscribers:

1. Identify the Active Directory location in which the auto-created contacts will be created. This can be an object of the class Container or Organizational Unit (OU). To create a new container, use a tool such as ADSI Edit. Or, to create a new OU, see the "To Create a New Organizational Unit" procedure.

2. Set applicable permissions for the Cisco Unity service account on the Active Directory container or OU that you selected in Task 1. To set up permissions by using the Permissions wizard, see the "To Set Permissions on the AD Location by Using the Permissions Wizard" procedure. Or, to manually set the specific permissions required on the container, see the "To Set Permissions on the AD Location by Using Active Directory Users and Computers" procedure.

3. Obtain the distinguished name of the container or OU. See the "To Obtain the Distinguished Name of the Container or Organizational Unit" procedure.

4. Use the Advanced Settings tool to change the container in which auto-created VPIM subscribers will be created. See the "To Change the AD Location in Which Automatically Created VPIM Subscribers Are Created" procedure.

To Create a New Organizational Unit


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Active Directory Users and Computers.

Step 2 In the console tree, right-click any node or folder, and click New > Organizational Unit.

Step 3 Enter a name for the organizational unit, and click OK.


To Set Permissions on the AD Location by Using the Permissions Wizard


Step 1 On the Cisco Unity server, double-click the Cisco Unity Tools Depot icon on the desktop.

Step 2 In the left pane of the Tools Depot window, expand Administration Tools.

Step 3 Double-click Permissions Wizard.

Step 4 Click Next without changing any options until you arrive at the Set Active Directory Containers for New Objects page.

Step 5 Select the domain and the applicable container or organizational unit in which Cisco Unity will create new users (in this case, VPIM subscribers).


Note The Permissions wizard only has the ability to grant permissions—it does not remove any permissions. Following this procedure will add the necessary permissions on the container or OU that you select, but will not remove permissions that are already granted on other containers for Cisco Unity.


Step 6 Click Next and follow the prompts to complete the Permissions wizard.


To Set Permissions on the AD Location by Using Active Directory Users and Computers


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Active Directory Users and Computers.

Step 2 Click View > Advanced Features (if it is not already selected).

Step 3 Right-click the container or OU in which the auto-created contacts are to be created, and click Properties.

Step 4 Click the Security tab.

Step 5 Click Add.

Step 6 Select from the list the account that Cisco Unity directory services log on as (typically this is UnityDirSvc).

Step 7 Click Add, then click OK.

Step 8 Click Advanced.

Step 9 Select the permission entry for the account that you selected in Step 6, and then click View/Edit.

Step 10 In the Apply Onto list, select This Object Only (if it is not already selected).

Step 11 In the Allow column of the Permissions list, check the Create Contact Objects check box, and click OK.

Step 12 Click View/Edit.

Step 13 In the Allow column of the Permissions list, check the Read All Properties, Write All Properties check box, and click List Contents.

Step 14 Click OK twice, and exit Active Directory Users and Computers.


To Obtain the Distinguished Name of the Container or Organizational Unit


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Active Directory Users and Computers.

Step 2 Right-click the container or OU in which the auto-created contacts are to be created, and click Properties.

Step 3 Click the Object tab. The fully qualified domain name of the object is displayed in the dialog box. For example, if the fully qualified domain name is ecsbu-paris.cisco.com/Unity-VPIM:

If the object is a Container, the distinguishedName is CN=Unity-VPIM,DC=ecsbu-paris,DC=cisco,DC=com

If the object is an Organizational Unit, the distinguishedName is OU=Unity-VPIM,DC=ecsbu-paris,DC=cisco,DC=com


To Change the AD Location in Which Automatically Created VPIM Subscribers Are Created


Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Networking - Change AD Location Where VPIM Contacts Are Created.

Step 4 In the New Value box, enter the distinguished name of the container to use.

Step 5 Click Set.

Step 6 Click Exit.

Step 7 Stop and restart the CsVPIMConnector service on the VPIM bridgehead servers. You do not need to restart Cisco Unity to enable the change.


Extending Identified Subscriber Messaging to Include VPIM Subscribers

When a person on a remote voice messaging system who has a corresponding VPIM subscriber account calls a Cisco Unity subscriber and leaves a message, by default Cisco Unity will not identify the message as being from the VPIM subscriber. For Cisco Unity to identify callers whose calling number matches the extension or alternate extension of a VPIM subscriber, identified subscriber messaging (ISM) must be extended to include VPIM subscribers. See the following sections as applicable to your installation.

Installation with Multiple Cisco Unity Servers Networked via Digital Networking

Single-Server Installations

Setting Permissions on Active Directory Containers Used for Importing Subscribers

Enabling Identified Subscriber Messaging

Extending Identified Subscriber Messaging

Installation with Multiple Cisco Unity Servers Networked via Digital Networking

In installations with multiple Cisco Unity servers networked via Digital Networking, enabling ISM to include VPIM subscribers requires the following:

1. The Cisco Unity servers must be connected to the same phone system or phone system network as described in the "Dialing Domains" section on page 2-15.

2. The servers must be configured to be in the same dialing domain, as described in the "Customizing the Primary Location" section.

3. The automated attendant search scope on each server must be set to the dialing domain as described in the "Setting the Automated Attendant Search Scope" section on page 2-7.

4. The applicable permissions on each server must be set, as described in the "Setting Permissions on Active Directory Containers Used for Importing Subscribers" section.

5. Identified subscriber messaging on each server must be enabled as described in the "Enabling Identified Subscriber Messaging" section.

6. Identified subscriber messaging on each server must be enabled for VPIM subscribers as described in the "Extending Identified Subscriber Messaging" section.

Single-Server Installations

In installations with only one Cisco Unity server, enabling ISM to include VPIM subscribers requires the following:

1. The server must be configured with a dialing domain name, as described in the "Customizing the Primary Location" section.

2. The applicable permissions must be set, as described in the "Setting Permissions on Active Directory Containers Used for Importing Subscribers" section.

3. Identified subscriber messaging must be enabled as described in the "Enabling Identified Subscriber Messaging" section.

4. Identified subscriber messaging must be enabled for VPIM subscribers as described in the "Extending Identified Subscriber Messaging" section.

Setting Permissions on Active Directory Containers Used for Importing Subscribers

If you will be importing contacts from two or more containers (for all of the Cisco Unity servers combined), the Cisco Unity message store services account on each Cisco Unity server must be granted SendAs permission on every container from which contacts will be imported on every Cisco Unity server in the forest. Otherwise, identified subscriber messaging may not work between Cisco Unity servers. For example, if CiscoUnityServer1 will import contacts from Container1 and Container2, and if CiscoUnityServer2 will import contacts from Container3 and Container4, Cisco Unity message store services account on each Cisco Unity server must have SendAs permission for all four containers.

To Set the Applicable Permissions


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, expand Administration Tools.

Step 3 Double-click Permissions Wizard.

Step 4 Do the following:

Choose the same Active Directory account for the Cisco Unity message store services account:

Click Next without changing any options until you arrive at the Choose the Cisco Unity Message Store Services Account page.

Choose the same Active Directory account for the Cisco Unity message store services account on every Cisco Unity server.

Choose the applicable containers:

Click Next without changing any options until you arrive at the Choose Active Directory Containers for Import page.

Choose all of the containers from which users will be imported for every Cisco Unity server in the forest.

Step 5 Click Next without changing any options until you complete the wizard.

Step 6 Repeat Step 1 through Step 5 on each Cisco Unity in the forest.


Enabling Identified Subscriber Messaging

If the system is using failover, you must make this change on both the primary and secondary servers because the setting is stored in the registry.

To Enable Identified Subscriber Messaging


Step 1 In the Cisco Unity Administrator, go to the System > Configuration Settings page.

Step 2 In the Identified Subscriber Messaging section, uncheck the Disable Identified Subscriber Messaging check box.

Identified subscriber messaging for subscribers on the same Cisco Unity server is enabled when the check box is unchecked. By default, the box is unchecked.

Step 3 Click the Save icon.


Extending Identified Subscriber Messaging

After identified subscriber messaging has been enabled, you must extend it to include VPIM subscribers.

To Extend Identified Messaging


Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Networking - Enable Identified Subscriber Messaging (ISM) for AMIS, Bridge, and VPIM Subscribers.

Step 4 In the New Value list, click 1, then click Set.

Step 5 When prompted, click OK.

Step 6 Click Exit.

Step 7 Restart Cisco Unity for the registry setting to take effect.


Gathering Information About Cisco Unity to Configure Another Voice Messaging System for VPIM

Configuring another voice messaging system to exchange VPIM messages with Cisco Unity may require the following information:

The server name and domain name of the Exchange (or relay) server that handles incoming SMTP messages. Depending on your network, this may or may not be the same server on which the Interoperability Gateway or Voice Connector and VPIM Transport Event Sink are installed.

The Cisco Unity phone prefix (if any) and Remote phone prefix (if any) entered on the corresponding delivery location page.

Mailbox number range for Cisco Unity subscribers.

If you are using the Interoperability Gateway on Exchange 2007, incoming VPIM messages are routed to a designated directory for pick-up by the gateway based on Foreign Connector routing. When defining a location for Cisco Unity on the remote voice messaging system, use the domain name that you entered for the Interop Domain FQDN in the Interoperability Gateway Administrator. The Interoperability Gateway Administrator assists you in setting up Foreign Connector routing.

If you are using the Interoperability Gateway on Exchange 2003, incoming VPIM messages must be routed to the VPIM Transport Event Sink for the Interoperability Gateway, which is installed on the same server as the Interoperability Gateway. When defining a location for Cisco Unity on the remote voice messaging system, use the domain name that you entered for the Interop Domain FQDN in the Interoperability Gateway Administrator.

If you are using the Voice Connector, incoming VPIM messages must be routed to the Exchange server on which the Voice Connector and VPIM Transport Event Sink is installed. When defining a location for Cisco Unity on the remote voice messaging system, use the domain name that you entered for the SMTP Transport Event Sink during the Voice Connector setup program.

Cisco Unity expects incoming VPIM messages to be formatted as follows: <UnityPhonePrefix+UnitySubscriberExtension@PrimaryLocationSMTPDomainName>. These specific properties are configured in Cisco Unity, but similar information will need to be configured in the other voice messaging system.

VPIM Concepts and Definitions in Cisco Unity 8.x

The following sections explain VPIM concepts in detail:

Introduction to VPIM

VPIM Networking and Locations

The Interoperability Gateway for Microsoft Exchange and Cisco Unity Voice Connector for Microsoft Exchange Components

Message Addressing Options

VPIM Networking and Blind Addressing

VPIM Subscribers

Automatic VPIM Subscriber Directory Updates

Identified Subscriber Messaging

Live Reply to VPIM Subscribers

Deleting VPIM Subscribers

Extension Addresses

Determining How VPIM Subscribers Appear in the Outlook Address Book

Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant

Migrating Subscribers from Another Voice Messaging System to Cisco Unity

Considerations for Digitally Networked Cisco Unity Servers

Phone Prefixes

Audio Format Considerations

Introduction to VPIM

VPIM Networking allows the exchange of voice, fax, and text messages between different voice messaging systems over the Internet or any TCP/IP network. VPIM is an industry-standard protocol based on the Simple Mail Transfer Protocol (SMTP) and the Multi-Purpose Internet Mail Extension (MIME) protocol.

VPIM enables organizations to link different voice messaging systems and to provide seamless voice message sending, receiving, forwarding, and replying between these systems. An organization can exchange messages over a TCP/IP-based intranet, or over the Internet, or a combination of the two. In simplified terms, voice messages are exchanged between the systems like regular email.

Figure 7-1 VPIM Networking Enables Messaging Between Different Systems Over a TCP/IP Network

VPIM Networking also enables messaging between Cisco Unity servers that access different directories, specifically when the Cisco Unity servers are in different Active Directory forests. (When the Cisco Unity servers are in the same Active Directory forest, Digital Networking is the solution to use rather than VPIM Networking.)

Figure 7-2 EXVPIM Networking Enables Messaging Between Cisco Unity Servers in Different Directories

The VPIM specification defines the format of messages and message addresses, and how messages are exchanged between mail servers. VPIM does not specify how the mail servers interact with client applications, or how they interface with end users. This allows many different kinds of existing systems to support VPIM. For more information about VPIM, refer to the Open Group VPIM website.

VPIM Messages

VPIM messages are made up of one or more MIME-encoded parts. The VPIM specification allows for optional MIME parts for spoken name and for forwarded, fax, and text messages. VPIM messages can also include a vCard, an electronic business card that includes phone number, text name, and email address. Cisco Unity allows you to specify whether the voice name and vCard of the sender will be sent with outgoing messages. If incoming messages include a voice name, it is played as part of the message. If a vCard is attached to an incoming message, the recipient can look at the vCard data in Cisco Unity ViewMail for Microsoft Outlook. Cisco Unity can also be configured to update the directory with information from the header or vCard data from incoming messages. For more information, see the "Automatic VPIM Subscriber Directory Updates" section.

VPIM fax encoding is based on the TIFF-F specification, and the vCard format is based on the Internet adaptation of the Versit vCard specification.

Figure 7-3 shows a sample VPIM message. Only a portion of the MIME encoding of the spoken name and voice message parts are shown because they are very long.

Figure 7-3 Sample VPIM Message

VPIM Addresses

A VPIM address is in the same format as a typical SMTP email address: localpart@hostpart. The right-hand side of the address is the domain name of the system on the TCP/IP network that handles messages. The left-hand side of the address is a unique identifier for the user. Typically, the left-hand side is the subscriber mailbox number or the mailbox number with a prefix.

For example, an outgoing VPIM message to Terry Campbell with the remote mailbox number 2233 could be addressed:

To: 2233@remotevoicemailsystem.com

If it is necessary to accommodate the numbering plan for your organization, the address can also contain a prefix:

To: 8882233@remotevoicemailsystem.com

VPIM addresses are created by the Interoperability Gateway or the Voice Connector when sending VPIM messages; they are not entered by subscribers when addressing messages.

VPIM Networking and Locations

Central to how you set up VPIM Networking is a Cisco Unity object called a location. Each Cisco Unity server is associated with one location referred to as the default or primary location, which is created during installation and which cannot be deleted. When setting up VPIM Networking, you use the Cisco Unity Administrator to give the primary location a new name and a Dial ID (which is an identifier for the location within Cisco Unity), enter the SMTP domain name, and customize other properties as applicable. See the "Primary Location Profile Settings in Cisco Unity 8.x" section on page 10-1 for more information.

You create a delivery location in the Cisco Unity Administrator to correspond to each remote voice messaging system with which Cisco Unity communicates. Delivery locations contain the information that Cisco Unity needs to exchange messages with other VPIM-compliant voice messaging systems. A VPIM delivery location contains the SMTP domain name of the system on the TCP/IP network that handles messages for the remote voice messaging system.

Location data is stored both in the SQL Server database on the Cisco Unity server and in Active Directory. In organizations with multiple Cisco Unity servers networked together, the location data replicates to all of the Cisco Unity servers in the network. This means that delivery locations need to be created only on one Cisco Unity server in the network. The Cisco Unity server on which delivery locations are created is referred to as the bridgehead server. See the "Considerations for Digitally Networked Cisco Unity Servers" section for more information.

The Interoperability Gateway for Microsoft Exchange and Cisco Unity Voice Connector for Microsoft Exchange Components

Cisco Unity uses Exchange to provide messaging between Cisco Unity and other VPIM-compliant voice messaging systems. Exchange is VPIM-transport compliant and provides the ability to send and receive messages across the Internet or any TCP/IP network to computers that support SMTP.

Before an outgoing message to a VPIM-compliant voice messaging system can be sent, it must be encoded as a MIME message. There are two Cisco Unity components that can handle the conversion to and from the MIME format—the Interoperability Gateway for Microsoft Exchange and the Cisco Unity Voice Connector for Microsoft Exchange. Depending on the details of your deployment, you may need one or the other of these messaging gateway components, or you may choose to deploy them both.

The Interoperability Gateway can be installed on an Exchange 2007 or Exchange 2003 server to provide VPIM functionality in all Exchange environments that are supported by Cisco Unity, including pure Exchange 2007 or any mixture of Exchange 2007, Exchange 2003, and Exchange 2000. However, the gateway does not support AMIS or Bridge networking. If your deployment includes AMIS or Bridge Networking, you must use the Voice Connector for those protocols. In this case, you can either use the Voice Connector for VPIM as well, or you can deploy the Interoperability Gateway alongside the Voice Connector. If you are using or plan to use Cisco Unity Connection Networking, you must use the Interoperability Gateway for VPIM Networking. Connection Networking requires the Interoperability Gateway, and the Interoperability Gateway is not compatible with the VPIM Transport Event Sink required by the Voice Connector.

The Voice Connector must be installed on an Exchange 2000 or Exchange 2003 server. If the Exchange 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 is also on the server), this is not recommended for performance reasons.

The Voice Connector must not be installed on a server in an Exchange cluster. Microsoft does not support third-party connectors on an Exchange cluster server. In addition, the Voice Connector cannot be installed on an Exchange 2007 server.

About the VPIM Transport Event Sink

In Exchange 2003 and Exchange 2000, a transport event sink is used to route incoming messages to the messaging gateway component (Interoperability Gateway or Voice Connector) for processing. A transport event sink is code that is activated through a defined trigger, such as the receipt of a new message.

The Interoperability Gateway and Voice Connector components each have their own transport event sink. The Interoperability Gateway transport event sink is automatically installed with the Interoperability Gateway (on the same server) when you run the Interoperability Gateway setup program on an Exchange 2003 server. The Voice Connector transport event sink is installed by using the Voice Connector setup program, but may be installed by itself on a separate server. When the Voice Connector Transport Event Sink installation program is run, a transport event sink is registered with the Windows SMTP server.

The VPIM Transport Event Sink monitors all incoming messages. Messages that have the content type Multipart/Voice-Message and are addressed to the SMTP domain specified during the transport event sink installation are readdressed to the Voice Connector by the VPIM Transport Event Sink.

Note that the Interoperability Gateway does not use a transport event sink when installed on Exchange 2007. In Exchange 2007, the Foreign Connector configuration is responsible for routing VPIM messages to a folder for pick-up by the Interoperability Gateway. VPIM messages are matched to the Foreign Connector based on the interoperability domain (defined as the Accepted Domain of the Foreign Connector) and the VPIM address space defined for the Foreign Connector.

How the Messaging Gateway Component Processes Incoming VPIM Messages

When the messaging gateway component receives the message, it first verifies that the message is from a domain specified in a VPIM delivery location. If a VPIM delivery location with a matching domain name is not found, the messaging gateway component rejects the message and sends a non-delivery receipt (NDR) to the sender.

If a VPIM delivery location with a matching location is found, the messaging gateway component does the following:

Removes the phone prefixes from the To and From addresses, if prefixes are specified on the corresponding VPIM delivery location page.

Validates the recipients of the message by looking up the extensions in Active Directory, and formats the addresses.

Converts the message from MIME to MAPI format.

Converts voice attachments to the audio format specified on the corresponding VPIM delivery location page.

Checks the delivery location configuration to see whether automatic VPIM subscriber directory updates are enabled. If so, the messaging gateway component may attempt to generate a directory update message as described in the "Automatic VPIM Subscriber Directory Updates" section.

Checks the delivery location to determine whether messages should be encrypted.

Hands the message back to Exchange for delivery to the Cisco Unity subscriber mailboxes.

How the Messaging Gateway Component Processes Outgoing VPIM Messages

When subscribers use the phone to address a message to a VPIM recipient, Cisco Unity constructs a To address for the message in the form VPIM:<Location Dial ID>_<Remote Mailbox>. As with any other message, Cisco Unity hands it off to Exchange for delivery. Because the message has a VPIM address type, it is first passed to the messaging gateway component (either the Interoperability Gateway or the Voice Connector, depending on which one you are using) for processing.

The messaging gateway component does the following tasks:

Converts the message from MAPI to MIME format.

Formats the To address by using the domain name and prefix specified on the corresponding VPIM delivery location page.

Formats the From address by using the prefix from the corresponding VPIM delivery location page and the domain name from the primary location page. (If your organization has more than one Cisco Unity server networked together, the domain name is from the primary location of the Cisco Unity server with which the sending subscriber is associated.)

Checks the delivery location for the audio format conversion setting for outbound messages to determine whether voice attachments should be converted to G.726 or remain in the format in which they were recorded.

Checks the delivery location to determine whether messages should be decrypted.

Attaches the recorded voice name and/or vCard, if specified on the corresponding VPIM delivery location page.

The newly formatted message is put in the SMTP pickup directory of the Windows server for delivery to the VPIM-compliant voice messaging system.

Message Addressing Options

Cisco Unity provides the following ways to address messages to individuals by using a VPIM-compliant voice messaging system:

Blind addressing—Blind addressing allows Cisco Unity to send messages without having specific information about the recipients on the remote voice messaging system (such as their names and mailbox numbers). To address a message to someone on another voice messaging system, subscribers enter the delivery location Dial ID and the remote mailbox number of the recipient. See the "VPIM Networking and Blind Addressing" section for more information.

VPIM subscribers—With VPIM subscribers, Cisco Unity has information about the remote users, such as their names and extensions. Subscribers address messages to VPIM subscribers the same way that they address messages to regular Cisco Unity subscribers—by extension or by spelling the name of the recipient. Note that spoken name confirmation is available when a recorded name exists for the VPIM subscriber. See the "VPIM Subscribers" section for more information.

Messaging Similarities and Limitations

For the most part, messaging between Cisco Unity subscribers and individuals on a VPIM-compliant voice messaging system is the same as messaging among Cisco Unity subscribers. For example:

Messages marked urgent when they are sent are marked urgent when they are retrieved by the recipient.

Messages marked private when they are sent are marked private when they are retrieved by the recipient.

Subscribers can send messages to Cisco Unity distribution lists that include VPIM subscribers.

Subscribers can send fax messages, if this is supported by the remote voice messaging system.

Note the following exceptions:

Email messages without a voice attachment cannot be sent to VPIM recipients even though ViewMail allows subscribers to address email messages to them. Instead of being delivered, email messages that are sent to VPIM recipients are returned to the sender as NDRs.

When replying to VPIM messages in ViewMail, if subscribers want to send text in the reply, they must enclose the text in a text file attachment. Whether the recipient receives the text attachment depends on the capabilities of the remote voice messaging system.

Messages that are marked as low importance in ViewMail are treated the same as regular messages.

Messages that are sent to Cisco Unity distribution lists from subscribers on the remote voice messaging system are not delivered, and an NDR is returned to the sender. Incoming VPIM messages to Cisco Unity are delivered to subscriber mailboxes only, and cannot be delivered to public distribution lists.

Incoming messages must be addressed to the primary extension of the subscriber; messages addressed to an alternate extension will not be delivered.

VPIM Networking and Blind Addressing

Blind addressing is one of the methods that Cisco Unity provides for addressing VPIM messages to users of another voice messaging system. Blind addressing allows Cisco Unity to address messages without having specific information about the recipients on the remote voice messaging system (such as their names and mailbox numbers). One of the steps to setting up blind addressing is to change the Blind Addressing setting on the Primary Location > Addressing Options page to something other than None. You also create a VPIM delivery location that corresponds to each voice messaging system with which Cisco Unity communicates.

You provide the following key information for each delivery location:

Dial ID—A unique number that identifies the location to Cisco Unity. This is the number that subscribers dial when blind addressing messages to individuals who use the remote voice messaging system.

SMTP Domain Name—The Internet-addressable SMTP domain name that is used to construct addresses for individuals who use the voice messaging system that corresponds to the delivery location.

When blind addressing a message, subscribers dial a number that is made up of the delivery location Dial ID and the mailbox number of the recipient. Before addressing the message, Cisco Unity parses the number that the subscriber enters 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 mailbox number exists. Cisco Unity does provide voice name confirmation that the delivery location exists before addressing the message (assuming that a voice name was recorded for the delivery location).

Subscriber Experience with Blind Addressing

Subscribers can address messages by using the phone, ViewMail for Outlook, or the Cisco Unity Inbox. To address a message by using ViewMail or the Cisco Unity Inbox, subscribers enter the address in the following format:

[VPIM:<Delivery Location Dial ID>_<Remote Mailbox Number>]


Note ViewMail requires the square brackets in the address.


Because your Cisco Unity server does not have access to the names, extensions, and recorded voice names of the people who use the other voice messaging system, subscribers will encounter some limitations with blind addressing:

When addressing a message, the sender does not hear 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 NDR if the number turns out to be an invalid extension.

When addressing a message, subscribers cannot use spelled-name mode; subscribers address the message only by using number mode, so they must know the delivery location Dial ID and the mailbox number for the recipient.

Blind addresses cannot be added to public distribution lists.

When subscribers use the phone to listen to messages from someone at the VPIM location, the conversation (also known as the telephone user interface, or TUI) cannot identify the sender.

When subscribers use ViewMail for Outlook or the Cisco Unity Inbox to listen to messages from someone at the VPIM location, the From address is in the format [VPIM:<Delivery Location Dial ID>_<Remote Mailbox Number>]. Note that the sender can be identified only if the remote system included the recorded voice name of the sender in the message.

Subscribers can use the Cisco Unity conversation to add and delete blind addresses in their private distribution lists. In contrast, subscribers cannot use the Cisco Unity Assistant to add blind addresses to their private lists, though they can use it to view list members and to delete any blind addresses that were added by phone. The Cisco Unity Administrator also does not allow you to add blind addresses to private lists, but you can use it to view and delete list members.

Note that when you delete a delivery location, blind addressees at that location are also removed from all private lists. Consider notifying subscribers of these potential changes to their private lists.

VPIM Subscribers

VPIM subscribers are a representation in Cisco Unity of individuals who use another voice messaging system. VPIM subscribers are created in Cisco Unity to enable Cisco Unity subscribers to find them in the directory and to send them messages as they would with any other subscriber. Voice messages addressed to VPIM subscribers are sent to the voice messaging system that they use.

VPIM subscribers do not require additional Exchange client access licenses (CALs), and they do not consume Cisco Unity subscriber licenses. The Cisco Unity subscriber license count does not change when you create VPIM subscribers.

To set up VPIM subscribers, you first create a VPIM delivery location that corresponds to each remote voice messaging system with which Cisco Unity communicates. After creating the delivery locations, you create a VPIM subscriber for each remote user. When creating each VPIM subscriber, you specify the user mailbox number on the other voice messaging system, and select a VPIM delivery location with which to associate the subscriber. The messaging gateway component (Interoperability Gateway or Voice Connector) uses the information on the associated delivery location when delivering a message to the VPIM subscriber. Note that VPIM subscribers can be created only on the VPIM bridgehead server on which the associated VPIM delivery location has been created.

You create and manage VPIM subscriber accounts in much the same way that you do regular subscriber accounts. You can use the Cisco Unity Administrator to create, modify, and delete VPIM subscriber accounts one at a time, and you can use the Cisco Unity Bulk Import wizard to create and modify multiple VPIM subscriber accounts.

Extensions are mandatory for VPIM subscribers. The extension is the number that subscribers dial when addressing a message to a VPIM subscriber. This number may or may not be the same as the mailbox number of the VPIM subscriber on the remote voice messaging system. Callers who reach the opening greeting of your organization can dial the extension of a VPIM subscriber or look up a VPIM subscriber in directory assistance and leave a message.

VPIM subscribers have corresponding contacts in Active Directory. When you delete VPIM subscribers, the underlying contacts are deleted automatically.

Other than receiving messages, VPIM subscribers do not have access to other Cisco Unity features, and some sections of the Cisco Unity Administrator are disabled for VPIM subscribers. VPIM 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.

Cannot use the Cisco Unity Inbox to check messages.

Cannot own private lists.

Cannot set up or receive message notifications.

Cannot receive message waiting indications.

Manually setting up VPIM subscribers requires more overhead for administrators of Cisco Unity than blind addressing does. However, you can also configure automatic directory updates so that VPIM subscribers will be automatically created, modified, and deleted based on information received in incoming VPIM messages. See the "Automatic VPIM Subscriber Directory Updates" section for more information.

Whether created manually or automatically, the VPIM subscriber option allows other subscribers to address messages to VPIM subscribers the same way that they address messages to regular subscribers. In general, creating VPIM subscriber accounts is a good solution in the following circumstances:

When there are only a few subscribers at the other voice messaging system who need to receive messages from the subscribers at your location. (Note however that there are no technical constraints associated with creating large numbers of VPIM subscribers.)

When unidentified callers need to be able to call the local Cisco Unity server to leave a message for someone on the other voice messaging system. This may provide a way for local callers to avoid long distance charges when leaving a message for a remote VPIM subscriber.

When the functionality described in the following "Subscriber Experience with VPIM Subscribers" section is required.

Because of the administrative overhead of setting up and maintaining many VPIM subscriber accounts, you may prefer a combination of blind addressing, manual creation of VPIM subscribers, and automatic directory updates. For example, you might want to set up VPIM subscriber accounts for senior sales staff, but not for other employees. Then as Cisco Unity receives incoming messages, replies, or non-delivery receipts (NDRs) for these employees, the directory of VPIM subscribers would grow and adjust automatically.

Subscriber Experience with VPIM Subscribers

Provided that VPIM subscribers are listed in the phone directory and have had voice names and greetings recorded for them:

Subscribers can address messages to VPIM subscribers by using the phone, ViewMail for Outlook, or the Cisco Unity Inbox.

Contacts that correspond to VPIM subscribers are included in Exchange address lists, which means that they are listed in the Outlook address book (unless the contact has been explicitly prevented from appearing there) and in the Cisco Unity Inbox address book. Therefore, message addressing to VPIM subscribers—either by using Outlook or the Cisco Unity Inbox—is the same as for regular subscribers.

When using the phone, subscribers can address messages to VPIM subscribers in spelled-name mode (if enabled on the system) or by extension.

Subscribers hear voice name confirmation when addressing a message to a VPIM subscriber.

When subscribers use the phone to listen to messages, the conversation announces who the message is from.

VPIM subscribers can be added to private and public distribution lists.

When Cisco Unity records a message from an unidentified caller for a VPIM subscriber, "non-mail-user@<Domain Name>" is used as the sender of the message, as required by the VPIM specification. Although VPIM subscribers are not prevented from replying to these messages, the reply messages are returned to the Unity Messaging System mailbox as NDRs.

Automatic VPIM Subscriber Directory Updates

In addition to manually creating, modifying, and deleting VPIM subscribers, you can configure Cisco Unity to automatically create, update, or delete VPIM subscriber records based on information contained in incoming VPIM messages. The settings that control whether or not the creation, modification, and deletion actions occur automatically, and how the incoming information is used to create or modify a record, can be individually configured for each delivery location. By default, no automatic directory updates will occur for any VPIM delivery locations.

See the following sections for discussions of the details:

Directory Update Processing That Occurs at the Messaging Gateway Component

Directory Update Processing That Occurs on the Cisco Unity VPIM Bridgehead Server

Population of VPIM Subscriber Information

Subscriber Addressing Considerations with Automatic Updates

CsVPIMConnector Logging

Directory Update Processing That Occurs at the Messaging Gateway Component

The directory update process begins when an incoming VPIM message is delivered from a remote voice messaging system to the messaging gateway component (either the Interoperability Gateway or Voice Connector). The messaging gateway component processes the incoming message as described in the "How the Messaging Gateway Component Processes Incoming VPIM Messages" section. In addition to the basic process, if the delivery location that is matched to the sender is configured to allow automatic creation or automatic modification of VPIM subscribers, and if the message contains sufficient information, the messaging gateway component also creates a directory update message addressed to the UVPIM_<Servername> mailbox. Depending on how the delivery location is configured, the messaging gateway component will use information either from the header of an incoming VPIM message, or from a vCard attachment included with the message.


Note If more than one vCard attachment is included with a message, only the vCard in the most recent portion of the message will be used for automatic creation or modification of a VPIM subscriber account.


The vCard or header information must contain a phone number, a text name, and a domain name; if the selected source of directory information is missing one of these fields, no directory message will be created. The messaging gateway component also uses this information to check for the existence of a matching contact, which will indicate whether the directory update pertains to creating a new VPIM subscriber, or to modifying an existing one.

If the processing of the incoming VPIM message at the messaging gateway component results in a nondelivery receipt (NDR), the messaging gateway component will not create a directory message for the sender. An NDR may instead be generated for the incoming VPIM message after it leaves the messaging gateway component (for example, if the recipient mailbox is full), but in such cases, the messaging gateway component will have already created the directory message.

Alternatively, the messaging gateway component may receive an NDR from a remote voice messaging system in response to an outgoing message addressed to a VPIM subscriber. In this case, the messaging gateway component checks the corresponding delivery location to see whether automatic deletions are enabled. For a successful deletion, the vCard or header fields in the NDR must contain a phone number and domain name, and an SMTP reason code indicating the reason for the delivery failure.

Directory Update Processing That Occurs on the Cisco Unity VPIM Bridgehead Server

The CsVPIMConnector service running on the VPIM bridgehead server monitors the UVPIM_<Servername> mailbox for directory messages. When the CsVPIMConnector service receives a directory message indicating that a new VPIM subscriber should be created, it also checks additional Subscriber Creation settings on the delivery location to determine:

Which template to use when creating VPIM subscribers

How to map the parsed text name of the VPIM subscriber to a first name, last name, and display name

How to map the phone number to an extension

Whether or not VPIM subscribers with no recorded voice names are allowed

The service uses SQL Server to create or update the VPIM subscriber on the VPIM bridgehead server. From the SQL Server database, the subscriber information is replicated to Active Directory, where a mail-enabled contact is created.

When the CsVPIMConnector service receives a directory message indicating that an existing VPIM subscriber should be modified, it checks to see whether the delivery location is configured to have the subscriber information updated with every incoming VPIM message, or only on messages where the text name has changed. The service takes the text name from the incoming message and applies the rules that have been configured to map the text name to a display name. If the option is selected that allows updates only when the text name has changed, the service compares this new display name to the display name on the VPIM subscriber record to determine whether the subscriber record should be modified. If the modification is allowed, the CsVPIMConnector service also checks to determine whether the delivery location is configured to allow display name updates. If so, the service will modify the first and last name fields and the recorded voice name, but will leave the display name unchanged. Otherwise, all of these fields will be updated.

For example, you can configure a location as follows:

Display names will be created as "Firstname Lastname - Seattle"

Updates are allowed only when the text name changes

Display name updates are allowed

In this circumstance, if a VPIM subscriber exists with the display name "Jessie Smith - Seattle" and an incoming message is received from Jessie Smith, no action will be taken. If the display name for Jessie Smith on the remote system is changed to "Jess Smith," a modification will be triggered the next time Cisco Unity receives an incoming message, and the first name and display name will be updated accordingly.

In other cases, a last name may change or a given mailbox number may be reassigned to a new person, so it is not recommended that modifications be allowed while display names updates are disallowed, as this could result in a first and last name contradicting the display name. The rule for mapping display names can be configured so that most desired display name conventions can be maintained when VPIM subscribers are automatically created or modified.

When the CsVPIMConnector service receives a directory message indicating that an existing VPIM subscriber should be deleted, it checks the reason code included in the message. If the reason code indicates that the mailbox does not exist (SMTP error code 5.1.1), the CsVPIMConnector service will delete the VPIM subscriber record. All associated objects and properties, including public and private distribution list membership, will be deleted from the SQL Server database on the VPIM bridgehead server. From the SQL Server database, the change will be replicated so that the Active Directory contact is removed.

If the VPIM bridgehead server is configured for failover, automatic VPIM subscriber updates will not occur while the secondary server is active, as the CsVPIMConnector service will run only on the primary server. However, while the primary server is unavailable, the messaging gateway component continues to generate directory update messages, which will be processed as soon as the primary server becomes active again.

Population of VPIM Subscriber Information

Depending on a setting configured for each delivery location, VPIM subscribers can be created, updated, or deleted by using information either from the header of an incoming VPIM message, or from a vCard attachment included with the message (if more than one vCard attachment is included, only the vCard in the most recent portion of the message will be used). Additional delivery location options allow you to specify how certain fields from the vCard or header are mapped to VPIM subscriber fields. Table 7-1 shows the source of various fields when either the vCard or header fields are used to generate VPIM subscriber information. It also includes information on the delivery location Subscriber Creation configuration settings that can affect how the CsVPIMConnector service maps this data to the fields in a VPIM subscriber record.

Table 7-1 VPIM Subscriber Information 

Subscriber Field
Source for Field When vCard Is Used
Source for Field When Headers Are Used
Notes

First Name

N property, Given Name

or

Text name contained in the FN (formatted name) property

Text name contained in the From address

For example, if the From address contains "Terry Bader<8882233
@remotevoicemailsystem.
com>", the text name used as the source of the first name would be Terry Bader.

If the first name is derived from a single text name field (from the FN property of a vCard or the From address of the message header), the setting When the Text Name Has No Comma can be applied to determine which part of the text name field is considered the first name.

Last Name

N property, Family Name

or

Text name contained in the FN (formatted name) property

Text name contained in the From address

For example, if the From address contains "Terry Bader<8882233
@remotevoicemailsystem.
com>", the text name used as the source of the last name would be Terry Bader.

If the last name is derived from a single text name field (from the FN property of a vCard or the From address of the message header), the setting When the Text Name Has No Comma can be applied to determine which part of the text name field is considered the last name.

Display Name

N property, Given Name and Family Name

or

FN property

Text name contained in the From address

For example, if the From address contains "Terry Bader<8882233
@remotevoicemailsystem.
com>," the text name used as the source of the display name would be Terry Bader.

The display name is derived from the appropriate source field according to the rule specified in the Mapping Text Names setting.

If the N property of the vCard is used and Mapping Text Names set is set to Directly to VPIM Subscriber Display Names, the display name will be set to Family Name, Given Name (this corresponds to Last Name, First Name).

Extension

One of the following:

TEL property with no qualifier

TEL property with qualifier TYPE=voice

Mailbox number in the header From address

Mailbox number in the From address

For example, if the From address contains "Terry Bader<8882233
@remotevoicemailsystem.
com>", the mailbox number used as the source of the extension would be 8882233.

The extension is derived from the appropriate source field according to the rule specified in the Map VPIM Subscriber Extensions To setting.

Note that this field is set only when the subscriber is created, and will not be changed by an automatic modification, even if the rule for mapping extensions has changed. If you wish to change the rule, extensions for existing VPIM subscribers can be changed manually using the Cisco Unity Administrator or the Bulk Edit tool.

Recorded Voice Name

Originator-Spoken-Name attachment

Originator-Spoken-Name attachment

The messaging gateway component (Interoperability Gateway or Voice Connector) converts the audio, by using the codec specified for inbound audio conversion on the associated delivery location, before including it in the directory message.

Remote Mailbox Number

One of the following:

TEL property with no qualifier

TEL with qualifier TYPE=voice

Mailbox number in the header From address

Mailbox number in the From address

For example, if the From address contains "<8882233@remote
voicemailsystem.com>", the Remote Mailbox Number would be 8882233.

If a remote phone prefix is specified for the delivery location, the prefix is removed from the source number to create the remote mailbox number.

The rule applied to map the TEL property or mailbox number to a VPIM subscriber extension is not applied to the remote mailbox number.


Non-numeric characters in the source data for the extension field are removed when creating the VPIM subscriber extension; for example, if the TEL property is used and contains the number (555)888-2233, the subscriber extension would be formed from the digits 5558882233. If the rule that is configured for mapping the incoming phone number data cannot be successfully applied, the creation of the VPIM subscriber will fail.

When the CsVPIMConnector service automatically creates VPIM subscribers, the Active Directory contact is given an alias in the following format:

VPIM_<DeliveryLocationDialID>_Extension

The service will also apply the subscriber template that is specified in the delivery location configuration when the VPIM subscribers are created.

Subscriber Addressing Considerations with Automatic Updates

The information contained in a VPIM subscriber account can be used to aid subscribers in addressing messages to remote mailboxes (by providing spell-by-name and spoken name confirmation, for example). However, note that regardless of whether blind addressing or VPIM subscriber information is used by the sender to indicate the desired recipient of a VPIM message, ultimately the message is addressed and sent to a numerical mailbox ID on the remote system. As such, there is no mechanism for confirmation that the name information that the local subscriber uses to address an outgoing message matches the actual current owner of the remote mailbox.

Even with automatic updates in place, situations may arise where a subscriber believes he or she is sending a message to one person at a remote site, but the mailbox has changed hands since the VPIM subscriber account was created, and the new owner of the mailbox actually receives the message. Because of the usage-based nature of the updates, if no VPIM message has been received from the new owner of the remote mailbox before a local subscriber attempts to address to it, the subscriber will encounter the outdated name information belonging to the original mailbox owner (including the spoken name of the original owner), with no indication that the mailbox has changed hands.

Another situation may arise in which two VPIM subscriber accounts exist for the same person on the remote system. In the case where a subscriber on a remote VPIM system changes mailbox numbers, and a VPIM subscriber account exists for that sender on Cisco Unity, the existing account will not be updated to change the mailbox number. Instead, when a Cisco Unity subscriber addresses a message to the VPIM subscriber with the outdated mailbox number, if an NDR is received from the remote system indicating that the mailbox no longer exists, the original VPIM subscriber account will be deleted. Then, at whatever point the remote subscriber sends a message to a Cisco Unity subscriber, a new VPIM subscriber account is created for the remote subscriber. Note that these two events can happen in either order; if the remote subscriber sends a message before the local subscriber attempts to send an outgoing message to the outdated mailbox number, VPIM subscriber accounts will exist for the remote subscriber with both the old and new mailbox numbers. A local subscriber who attempts to address a message to that remote subscriber by using spell-by-name will hear both matches at this point, with different extensions. The outdated VPIM subscriber account will not be deleted unless a subscriber addresses a message to it and receives an NDR.

If the events occur in the opposite order—if a subscriber sends a message to a VPIM subscriber that results in an NDR and the deletion of the VPIM subscriber account before an incoming message is received from the new mailbox number of the remote subscriber—the sender will receive the NDR but will not have updated VPIM subscriber information to use in readdressing the message. In this case, the sender would need to use blind addressing to address further messages to the recipient, until an incoming message is received from the recipient, which will result in the creation of a new VPIM subscriber account.

CsVPIMConnector Logging

Both micro and macro traces are available for the CsVPIMConnector service. If detailed logging is required for troubleshooting purposes, these traces can be enabled and collected using the Cisco Unity Diagnostic tool (UDT). Otherwise, the CsVPIMConnector logs summary information by default for each directory message that it processes. This information is logged to a data file named data_CsVPIMConnector_<date>_<time>.txt, in the Cisco Unity trace logs directory. The default location of the trace logs is the CommServer\Logs directory.

The data is written to the file in comma-separated format. Table 7-2 describes the fields in the order that they are written to the data file.

Table 7-2 CsVPIMConnector Data Log File Columns 

Field
Contents

UTC Time Stamp

Time the directory message was processed in Coordinated Universal Time (UTC).

Logging Process Name

AvRepMgr_MC

Logging Process Number

30311

Local Time Stamp

Time the directory message was processed in the time zone of the Cisco Unity server.

Subscriber Display Name

If the VPIM subscriber display name has been successfully generated according to the rule specified in the Mapping Text Names setting, the display name is listed here; otherwise, the name as received in the VPIM message is listed.

Location Dial ID

The dial ID of the delivery location from which the original VPIM message was received.

Subscriber DTMF ID

If the VPIM subscriber extension has been successfully generated according to the rule specified in the Map VPIM Subscriber Extensions To setting, the extension is displayed here; otherwise, `Invalid' is listed.

Action Type Code

One of the following:

13001—create

13002—delete

13003—modify

Action Status Code

One of the following:

15000—error

15001—completed successfully

Error Status Code

One of the following:

100—success

101—extension conflict

102—alias conflict

103—remote address conflict

104—invalid name

105—invalid parameter

106—subscriber not local

107—subscriber not found

108—invalid extension

See Table 7-3 for a further description of each error status code.

Subscriber Status Code

One of the following:

0—global

1—local

2—not found


Table 7-3 CsVPIMConnector Error Status Code Descriptions 

Error Status Code
Description

100 (success)

Successful attempt to create, modify, or delete the subscriber.

101 (extension conflict)

Attempt to create a subscriber with an extension that already exists in the directory.

102 (alias conflict)

Attempt to create a subscriber with an alias that already exists in the directory.

103 (remote address conflict)

Attempt to create a subscriber with a remote address that already exists in the directory.

104 (invalid name)

The VPIM message was received with only a single name field (both a first and last name are required to create or modify a subscriber).

105 (invalid parameter)

Parameter used for attempted creation was invalid (for example, an invalid subscriber template or container for creation was specified, or there were insufficient permissions to create the subscriber in the specified container).

106 (subscriber not local)

Modification or deletion requested for a subscriber that is found in the global subscriber table, but not in the local subscriber table.

107 (subscriber not found)

Modification or deletion requested for a subscriber that cannot be found.

108 (invalid extension)

Extension creation rules specified for the location cannot be applied to the phone number received or the extension generated is longer than 40 digits.


Identified Subscriber Messaging

Identified subscriber messaging (ISM) affects what subscribers hear when they call other subscribers from their primary or alternate extensions and are forwarded to the greetings of the subscribers they call. If they then leave a message, ISM affects what the called subscriber hears and can do when listening to the message. When ISM is enabled, Cisco Unity recognizes that the calling extension is associated with a subscriber and accordingly plays the internal greeting of the called subscriber. Additionally, when the called subscriber later listens to the message, Cisco Unity plays the recorded voice name of the subscriber who left the message and allows the called subscriber to record a reply.

When a call to a Cisco Unity subscriber is forwarded to the subscriber greeting and ISM is enabled, Cisco Unity compares the calling number (ANI or caller ID) to the primary and alternate extensions of subscribers. If a match is found, Cisco Unity identifies the caller as a subscriber. When Cisco Unity compares the calling number to extensions, by default, only "regular" Cisco Unity subscribers on the local system are included in the comparison. ISM can be expanded to include all Cisco Unity subscribers throughout a dialing domain.

You can enable ISM for AMIS, Bridge, and VPIM subscribers (collectively referred to as external subscribers), so that Cisco Unity will include them when comparing calling numbers to extensions. Note the following:

After enabling ISM for external subscribers, Cisco Unity must be restarted.

If multiple Cisco Unity servers are networked via Digital Networking, ISM functionality can be made available only on the Cisco Unity servers that are in the same dialing domain as the bridgehead server.

You must enable ISM for external subscribers for each Cisco Unity server on which the functionality is desired.

If a single Cisco Unity server is in use, the Cisco Unity server must be a member of a dialing domain for this functionality to be used.

Note the difference between leaving a messaging and sending a message. When a person on the remote voice messaging system with a corresponding external subscriber account records and sends a message to a Cisco Unity subscriber (as opposed to calling and leaving a message), all versions of Cisco Unity identify the message as being from the corresponding external subscriber.

The phone system provides the calling number to Cisco Unity. The number of digits included in the calling number is configurable in most phone systems. For Cisco Unity to find a matching subscriber extension, the phone system must be configured to provide the applicable number of digits in the calling number. You may also need to add alternate extensions to the subscriber accounts to match the calling number. Additionally, there may be other phone system-specific issues that prevent Cisco Unity from matching the calling number to a subscriber extension. Refer to your phone system documentation and the applicable Cisco Unity integration guide for details about the call information provided by the phone system.

Live Reply to VPIM Subscribers

Live reply allows subscribers who listen to their messages by phone to respond to messages from other subscribers by calling them. When live reply is enabled, subscribers listening to messages by phone can reply to a subscriber message choosing the "call the subscriber" option to have Cisco Unity call the subscriber directly. Note that whether subscribers have access to the live reply feature depends on their class of service settings. (Live reply is enabled on the Subscribers > Class of Service > Messages page in the Cisco Unity Administrator.)

Subscribers can live reply to messages from subscribers on other voice messaging systems who have corresponding VPIM subscriber accounts in Cisco Unity. In order for the live reply call to be successfully transferred, a call transfer number must be configured for the VPIM subscribers.

Note that a live reply to a VPIM subscriber is always done via a release to phone system transfer, even when both the Cisco Unity subscriber who is replying to a message and the VPIM subscriber have accounts on the same Cisco Unity server. On a release to switch transfer, Cisco Unity dials the call transfer number configured for the VPIM subscriber and hangs up, leaving the phone system to handle the call. Note the following limitations with release to switch transfers:

The VPIM subscriber call screening, call holding, and announce features are ignored.

The call transfer setting "No (Send Directly to Subscriber's Greeting)" is ignored. Cisco Unity dials the VPIM subscriber extension and hangs up. If the subscriber extension is a valid extension on the phone system that Cisco Unity is integrated with, then the subscriber phone rings. If the subscriber extension is not a valid phone extension, what happens to the call after that depends on the phone system and how it is configured. If you do not configure the phone system to handle calls to the subscriber extensions, the caller may be disconnected.

Note the following:

Live reply to VPIM subscribers is enabled automatically, and cannot be disabled.

Live replies to VPIM subscribers with accounts on other Cisco Unity servers do not use the cross-server live reply functionality that can be used to live reply to Cisco Unity subscribers with accounts on other Cisco Unity servers. However, for live reply to be offered when a Cisco Unity subscriber replies to a message from a VPIM subscriber with a subscriber account on another Cisco Unity server, the servers must be in the same dialing domain.

Deleting VPIM Subscribers

Each VPIM subscriber is associated with an Active Directory contact. When you delete VPIM subscribers in the Cisco Unity Administrator by deleting the subscriber accounts individually, the underlying contacts are automatically deleted. To delete all of the VPIM subscribers associated with a delivery location, the underlying contacts associated with the subscribers, and the delivery location itself, use the Global Subscriber Manager, available in Tools Depot. Note that when you delete a VPIM delivery location, blind addressees are also removed from all private lists. Consider notifying subscribers of these potential changes to their private lists.

If enabled by the delivery location Subscriber Creation settings, Cisco Unity can automatically delete VPIM subscribers when non-delivery receipts are received from the delivery location in response to messages that are sent to VPIM subscribers. For further information, see the "Automatic VPIM Subscriber Directory Updates" section.

Extension Addresses

When you create a VPIM subscriber, Cisco Unity automatically generates an email address in the following format:

VPIM:<Delivery Location Dial ID>_<Remote Mailbox Number>

This special email address is called an extension address or a remote address. The extension address is a combination of the delivery location Dial ID with which the VPIM subscriber is associated, and the Remote Mailbox Number of the VPIM subscriber. Each contact in Active Directory that corresponds to a VPIM subscriber contains an extension address.

When subscribers use the phone to address messages to a VPIM subscriber, they dial an extension. Cisco Unity recognizes the recipient as a VPIM subscriber and retrieves the extension address from the SQL Server database on the Cisco Unity server.

Extension addresses are generated automatically when you create VPIM subscribers. Extension addresses are updated automatically when you change the remote mailbox number, and are automatically updated if you change the Dial ID of a delivery location.

Determining How VPIM Subscribers Appear in the Outlook Address Book

Depending on your installation, the users of the remote voice messaging system may already have Active Directory accounts and Exchange mailboxes on your local network that they use for email. Therefore, when VPIM subscriber accounts are created for them, the Exchange address lists will contain duplicate listings—the existing user account that is used for email and a new contact that is used only for voice mail. Both listings are included in the Outlook address book. This means that people may inadvertently send email messages to the contact, which should be used only for addressing voice messages.

To discourage people from inadvertently sending email messages to VPIM subscribers, you can prevent the associated contact from appearing in the Outlook address book. Alternatively, you can change how the display name for the contact appears in the Outlook address book so that subscribers can distinguish the contact from a user account. In this way, you can reduce the number of email messages inadvertently sent to contacts and simplify addressing for those who send voice messages to VPIM subscribers at the same time.

Either before or after you create VPIM subscriber accounts, you can prevent the associated contact from appearing in the Outlook address book by hiding the contacts from Exchange address lists. When you do so, Exchange will still deliver email messages addressed to an existing user account (if one exists) and to the contact. However, the number of email messages that are sent to the contact may be reduced because subscribers cannot inadvertently pick the contact from the Outlook address book when addressing messages to them.

To prevent subscribers from appearing in Outlook address books, you can use the Cisco Unity Administrator, the Cisco Unity Bulk Import wizard, Bulk Edit, or Active Directory Users and Computers:

To do so in the Cisco Unity Administrator, uncheck the Show Subscriber In Email Server Address Book check box on the Profile page for the subscriber template that you plan to use when creating VPIM subscribers, or on individual subscriber Profile pages after you have created the subscriber accounts.

To do so by using the Cisco Unity Bulk Import wizard or the Bulk Edit utility, see the Help for each tool.

To do so in Active Directory Users and Computers, click View > Advanced Features to see the Exchange Advanced property page for a user, and then check the Hide From Exchange Address Lists check box on the Exchange Advanced tab.

As an alternative to preventing a contact from appearing in the Outlook address book altogether, you may want to alter the display name for the contact so that subscribers can distinguish the contact from the user account. For example, you could append "- Voice mail" to the display name of each VPIM subscriber, and the names would appear in the Outlook address book as follows:

Abade, Alex
Abade, Alex - Voice mail
Bader, Kelly
Bader, Kelly - Voice mail
Campbell, Terry
Campbell, Terry - Voice mail

In this way, subscribers can easily determine which address is appropriate to use when they send voice messages to VPIM subscribers. Additionally, when subscribers use the Outlook address book to address a message to a contact, they can be confident that the address is formatted correctly.

You can specify rules, per delivery location, for how the display names of auto-created VPIM subscribers are generated from the text names that Cisco Unity receives in incoming messages from senders on each remote messaging system.

Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant

In the transition from a legacy voice messaging system to Cisco Unity, your organization may choose to migrate users to Cisco Unity in phases. As a result, Cisco Unity will likely support both regular subscribers and "external" subscribers—Bridge, AMIS, or VPIM contacts (as applicable)—at the same time. Regular subscribers can send messages to external subscribers, and even add them to their private distribution lists during the transition.

However, once external subscribers are converted into regular Cisco Unity subscribers, they are automatically removed from all private lists without notifying private list owners. When this occurs, subscribers may continue to send messages to their private lists without realizing that some of their intended recipients no longer receive them.

When convenient and practical, Cisco Unity Administrators should notify subscribers when external subscribers are converted to regular subscribers, notifying subscribers that they should re-add the newly migrated subscribers to existing private lists, as applicable. During the migration phase, you may also want to consider preventing subscribers from adding subscribers to their private lists in the Cisco Unity Assistant, and asking them not to use the Cisco Unity phone menus to do so—at least until the migration process is complete.

Use the following procedure to prevent all subscribers who are associated with the Cisco Unity server from adding individual subscribers to their private lists in the Cisco Unity Assistant. The procedure does not prevent subscribers from using the Cisco Unity phone menus to add regular and external subscribers to their private lists, nor does it prevent subscribers from addressing messages to regular and external subscribers.

To Prevent Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant


Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Unity Assistant—Do Not Allow Subscribers to Add Subscribers to Private Lists.

Step 4 In the New Value list, click 1, and then click Set so that when subscribers add members to their lists in the Cisco Unity Assistant, the Find Names dialog box does not display the Subscribers tab. (Subscribers can continue to add distribution lists to their lists from the Distribution Lists tab.)

Step 5 When prompted, click OK.

Step 6 Click Exit.

You do not need to restart Cisco Unity to enable the change.


Migrating Subscribers from Another Voice Messaging System to Cisco Unity

If you are using VPIM to migrate from another voice messaging system to Cisco Unity, there are several tools that you can use to create Cisco Unity subscribers from VPIM subscriber information. See the following sections for more information:

Migrating Subscribers in Bulk

Migrating Subscribers One at a Time

Private List Considerations for Migrating Subscribers

Migrating Subscribers in Bulk

Following are the general steps for migrating VPIM subscribers to Cisco Unity subscribers, in bulk. See the Help files of the applicable tools for more detailed information. (Click the Tools Depot icon on the Cisco Unity server, and click the applicable tool in the left pane to view the Help file.)

1. As a best practice, back up the Cisco Unity server (just as a precaution, because you will be deleting data).

2. Run Subscriber Information Dump from Tools Depot, and output the VPIM subscriber information to a CSV file.

3. Modify the CSV file as needed so that you can use it as the input file when you use the Cisco Unity Bulk Import wizard to create Cisco Unity subscribers.

4. Run Global Subscriber Manager from Tools Depot to delete the VPIM delivery locations and the associated VPIM subscribers and underlying contacts.

5. If the people migrating from the remote voice messaging system do not already have Active Directory accounts and Exchange mailboxes, create them. Alternatively, you can let the Cisco Unity Bulk Import wizard create the accounts.

6. Run the Cisco Unity Bulk Import wizard by using the input file that you prepared in Step 3.

Migrating Subscribers One at a Time

If you have set up VPIM subscriber accounts for the subscribers on another voice messaging system, and if they have existing Exchange mailboxes, you can use the Migrate Subscriber Data utility when the time comes to migrate them to Cisco Unity. The Migrate Subscriber Data utility creates a Cisco Unity subscriber account by combining the Cisco Unity-specific data from an existing VPIM subscriber account (such as the voice name) with an existing mail user. The utility then deletes the VPIM subscriber account and the associated Active Directory contact.

The Migrate Subscriber Data utility is available in Tools Depot (the Tools Depot icon is installed on the Cisco Unity server desktop). See the Help file that comes with the utility for more information.

Private List Considerations for Migrating Subscribers

When you migrate VPIM subscribers, consider notifying Cisco Unity subscribers of these potential effects on private distribution list membership:

When you delete a delivery location, blind addressees are removed from all private lists.

When a VPIM subscriber becomes a regular subscriber, the VPIM subscriber is removed from all private lists.

Considerations for Digitally Networked Cisco Unity Servers

A small subset of subscriber and distribution list data is stored in Active Directory, as is most 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 users at a VPIM location.

Because of directory replication, VPIM delivery locations and VPIM subscribers need to be created only on 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 VPIM delivery location or to a VPIM subscriber created on another server. The Cisco Unity server configured for VPIM acts as the VPIM "bridgehead" server for the other Cisco Unity servers in the network.

Phone Prefixes

Each VPIM delivery location provides the following prefixes, which are used to accommodate various numbering plans:

Remote Phone Prefix—This number is used to construct addresses for users at a VPIM location. On outgoing messages to the VPIM location, the messaging gateway component (Interoperability Gateway or Voice Connector) adds the prefix to the beginning of the recipient mailbox number to form the To address. On incoming messages from the VPIM location, the messaging gateway component removes the prefix from the beginning of the sender mailbox number to form the From address.

Cisco Unity Phone Prefix—This number is used to construct addresses for Cisco Unity subscribers. On outgoing messages to the VPIM location, the messaging gateway component adds the prefix to the beginning of the sender mailbox number to form the From address. On incoming messages from the VPIM location, the messaging gateway component removes the prefix from the beginning of the recipient mailbox number to form the To address.

If all VPIM delivery locations have a unique domain name, prefixes are optional. If you have multiple delivery locations with the same domain name, the Remote Phone Prefix is required. Within the set of delivery locations with the same domain name, the Remote Phone Prefix must be a unique number.

For example, assume that an organization has implemented a 10-digit numbering plan, in which the mailbox numbers for Cisco Unity subscribers begin with 206, and the mailbox numbers of subscribers on a VPIM voice messaging system begin with 425.

Assume the following has been set on the VPIM delivery location:

Dial ID = 425

Remote Phone Prefix = 425

By setting both the Remote Phone Prefix and the Dial ID to 425, the number that a subscriber enters when blind addressing a message to someone at the VPIM location is the same number that the subscriber enters when calling the person.

Because of the prefix, VPIM subscribers are assigned a 7-digit Remote Mailbox Number. In this example, for outgoing messages the messaging gateway component would add the prefix 425 to the beginning of the remote mailbox number, creating a 10-digit recipient mailbox number.

Audio Format Considerations

The Audio Format Conversion settings on the VPIM delivery location page in the Cisco Unity Administrator allow you to control the audio format of outgoing and incoming VPIM messages, as follows:

Outbound Messages—You can set whether outbound VPIM messages are converted to G.726 or sent in the format in which they were recorded (no audio format conversion).

Incoming Messages—You can set whether incoming VPIM messages are converted to G.711 (mu-law), GSM 6.10, G.729a, or stored in the format in which they were sent (no audio format conversion).

To make decisions about these settings, consider the following:

The audio format that the local Cisco Unity server (or servers, if there are multiple Cisco Unity servers networked together) uses for recording and playing voice messages.

The audio format in which the remote voice messaging system can send and receive VPIM messages. Some voice messaging systems support only the G.726 format for VPIM messages, but you will need to consult the documentation of the remote voice messaging server to be sure.

Network bandwidth.

We recommend that incoming VPIM messages be stored in the same audio format that the local Cisco Unity servers use for recording and playing messages. However, if you want incoming VPIM messages to be stored in some other audio format, you will need to verify that the applicable codec is installed on all Cisco Unity servers and on other computers that access these messages. In particular:

If your organization has multiple Cisco Unity servers networked together, all of the Cisco Unity servers must have the codec installed.

If subscribers use ViewMail for Outlook or the Cisco Unity Inbox to listen to messages, the codec may need to be installed on each subscriber workstation.

If you are using the Cisco Unity Voice Connector for Microsoft Exchange, the Voice Connector converts the audio format of incoming and outgoing VPIM messages according to the settings on the VPIM delivery location. The Voice Connector requires both the codec that the VPIM message is being converted from and the codec that the VPIM message is being converted to. Depending on the audio format conversion, you may need to install the applicable codec on the Exchange server on which the Voice Connector is installed, as follows:

G.711 and GSM 6.10—The Voice Connector uses the codecs that Windows installs. You may want to verify that the codecs are still installed on the Exchange server.

G.729a and G.726—The Voice Connector uses its own copies of the G.726 and G.729a codecs, so these codecs do not need to be installed on the Voice Connector Exchange server. (Note that the Voice Connector will add a RIFF header to an incoming message in the G.726 format if the header is missing. Without the RIFF header, Windows-based audio players will be unable to play messages.)

OKI ADPCM—To convert messages from the OKI ADPCM audio format, the OKI ADPCM codec must be installed on the Exchange server on which the Voice Connector is installed.

Other codecs—To convert messages from other audio formats, the applicable codec must be installed on the Exchange server on which the Voice Connector is installed.

Related Documentation

For general information about audio formats supported by Cisco Unity, see the Audio Codecs and Cisco Unity white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

For information specific to messaging between Cisco Unity servers in different directories, see the "Audio Format Conversion Settings" section on page 8-3.

VPIM Networking Maintenance in Cisco Unity 8.x

This section provides information on various tasks that you may need to maintain your VPIM Networking configuration. See the following sections for details:

Changing the IP Address of a Microsoft Exchange Server

Moving the UVPIM Mailbox

Changing the IP Address of a Microsoft Exchange Server

Depending on your network, after changing the IP address of a Microsoft Exchange server, you may need to update the Exchange SMTP virtual server settings on all other Microsoft Exchange servers in your network to reflect the new IP address so that VPIM messages are delivered correctly.

To Check and Update the SMTP Virtual Server Relay List on Exchange 2000 or Exchange 2003


Step 1 On the Microsoft Exchange server, on the Windows Start menu, click Programs > Microsoft Exchange > System Manager.

Step 2 In the tree on the left, expand Servers\<Server name>\Protocols\SMTP.

Step 3 Right-click Default SMTP Virtual Server and select Properties.

Step 4 Click the Access tab.

Step 5 Click Relay.

Step 6 Do one of the following:

If All Except the List Below is selected and the new server IP address does not appear in the list, skip to Step 11.

If All Except the List Below is selected and the new server IP address appears in the list, click the IP address and click Remove, then skip to Step 10.

If Only the List Below is selected, continue with Step 7.

Step 7 Click Add.

Step 8 Click Single Computer, and enter the new IP address of the server that changed addresses.

Step 9 Click OK.

Step 10 Verify that the Allow All Computers Which Successfully Authenticate to Relay, Regardless of the List Above check box is checked.

Step 11 Click OK twice to close the Properties dialog box.

Step 12 Close the Exchange System Manager.

Step 13 Repeat Step 1 through Step 12 on each Microsoft Exchange server in your network.


To Check the IP Addresses on Receive Connectors on Exchange 2007


Step 1 Open Exchange Management Console.

Step 2 For each Hub Transport and Edge Transport Receive connector:

a. Right-click the Receive connector and click Properties.

b. Click the Network tab.

c. Review the listed IP addresses to see if any changes are needed.

Step 3 Close Exchange Management Console.


Moving the UVPIM Mailbox

For information on moving the UVPIM mailbox, see the "UVPIM Mailbox" section in the "Cisco Unity Data and Log Files" chapter of the Maintenance Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Notable Behavior of VPIM Networking in Cisco Unity 8.x

This section describes notable behavior of VPIM Networking. See the following sections for more information:

Call Transfer Settings and VPIM Subscribers

Inbound Messages Are Delivered Only to Primary Extensions

Inbound Search Scope

Running the Voice Connector Setup Program in Another Language

Call Transfer Settings and VPIM Subscribers

In installations with multiple Cisco Unity servers networked via Digital Networking, the number that Cisco Unity uses for call transfers to a subscriber is the only number replicated among the Cisco Unity servers; none of the other settings on the Subscriber > Call Transfer page in the Cisco Unity Administrator are replicated. For example, in Figure 7-4, call transfers are set to ring the subscriber at the number 9,5551212. The only call transfer setting that is replicated to other Cisco Unity servers is the call transfer number 9,5551212. If the setting was "Yes, ring subscriber's extension" instead, the number 3047 would be replicated.

Figure 7-4 Only the Call Transfer Number Is Replicated

When the call transfer setting is set to "No (send directly to subscriber's greeting)," the call transfer number is automatically set to the subscriber extension (3047 in the example above), which is replicated to the other networked Cisco Unity servers.

Call transfers to VPIM subscribers created on other Cisco Unity servers are always handled by the phone system (release to switch)—rather than by Cisco Unity (supervised transfer)—even if the subscribers are set up for supervised transfers (as in the above example). The release to switch call transfers happen when:

A Cisco Unity subscriber chooses to call the sender (live reply) after listening to a message left by a VPIM subscriber. (Live replies to VPIM subscribers are always done release to switch, even when the reply is to a VPIM subscriber on the same Cisco Unity server.)

A caller enters the extension of a VPIM subscriber from the automated attendant (for example from the opening greeting), and the VPIM subscriber account is on another Cisco Unity server.

A caller spells the name of a VPIM subscriber from a directory handler, and the VPIM subscriber account is on another Cisco Unity server.

On a release to switch transfer, Cisco Unity dials the call transfer number configured for the VPIM subscriber and hangs up, leaving the phone system to handle the call. Note the following limitations with release to switch transfers:

The VPIM subscriber call screening, call holding, and announce features are ignored.

The call transfer setting "No (Send Directly to Subscriber's Greeting)" is ignored. Cisco Unity dials the VPIM subscriber extension and hangs up. If the subscriber extension is a valid extension on the phone system that Cisco Unity is integrated with, then the subscriber phone rings. If the subscriber extension is not a valid phone extension, what happens to the call after that depends on the phone system and how it is configured. If you do not configure the phone system to handle calls to the subscriber extensions, the caller may be disconnected.

Inbound Messages Are Delivered Only to Primary Extensions

When addressing a message to a Cisco Unity subscriber, users on the remote voice messaging system must use the primary extension of the Cisco Unity subscriber; alternate extensions are not supported. Senders will receive an NDR if they address a message with the alternate extension of a Cisco Unity subscriber.

Note also that Cisco Unity does not accept messages from a remote voice mail system that are sent to Cisco Unity public distribution lists, call handlers, and interview handlers. Cisco Unity accepts messages from a remote voice mail system only when they are sent to a subscriber primary extension.

When designing the numbering plan for Cisco Unity subscribers, as a best practice, configure the primary extension of all Cisco Unity subscribers with the extension that will be used for addressing from the remote voice mail system. Configure all other required extensions as alternate extensions, as all other functionality in Cisco Unity can use alternate extensions.

Inbound Search Scope

In installations with multiple Cisco Unity servers networked together, the search scope for a matching subscriber extension for inbound messages that are sent from another VPIM-compliant voice messaging system is set to the global directory. It is not possible to limit the inbound search scope to either a dialing domain or to the local Cisco Unity server.

If two (or more) Cisco Unity subscribers have identical extensions, messages from the remote voice messaging system will not be delivered by the messaging gateway component (Interoperability Gateway or Voice Connector) to any of the Cisco Unity subscribers with the duplicate extensions. When the messaging gateway component detects duplicate extensions, it NDRs the message back to the sender and logs a warning to the Windows Application Event log.If you are concerned that there might be duplicate extensions among Cisco Unity subscribers, you can check the Application Event log on the Exchange server on which the Interoperability Gateway or Voice Connector is installed for warnings from the CuIgeService or the Exchange 2000 Voice Connector, as applicable.

Running the Voice Connector Setup Program in Another Language

The Voice Connector installation program does not prompt with a choice of languages for the installation; it always installs in English. To run the Voice Connector installation program by using one of the localized versions (FRA, DEU, or JPN) instead of English, do the following procedure.


Caution Installing the Voice Connector on an Exchange 2007 server is not supported.

To Run the Voice Connector Setup Program in Another Language


Step 1 From the Cisco Unity installation DVD or CD 1, copy the entire VoiceConnector-Ex2000 to your hard disk.

Step 2 In this local directory, browse to the LocalizedFiles\ENU directory.

Step 3 Rename the CiscoUnity_VoiceConnector.dll and SetupRes.dll files. (For example, rename the files CiscoUnity_VoiceConnector_ENU.dll and SetupRes_ENU.dll.)

Step 4 Copy the files CiscoUnity_VoiceConnector.dll and SetupRes.dll from the LocalizedFiles\<XXX> directory (where <XXX> is your language of choice) to the Localized\ENU directory.

Step 5 Run Install.exe from the VoiceConnector-Ex2000 directory on your hard disk. The installation program should be presented in the language you chose.


Note Only the installation program will be in this language; currently, the Event Log messages, logging, properties, and configuration settings are not localized.