Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange) - Migrating from SMTP Networking to VPIM Networking [Cisco Unity]

Table Of Contents

Migrating from SMTP Networking to VPIM Networking

Overview

Prerequisites

Task List for Migrating from SMTP Networking to VPIM Networking

Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers

Manually Converting VPIM Delivery Locations and Subscribers

Migrating from SMTP Networking to VPIM Networking

Overview

This chapter provides information on migrating from SMTP Networking to VPIM Networking for messaging between Cisco Unity servers that access different directories. Because Cisco Unity 4.x was the last train that supported the SMTP Networking option, customers who need to network Cisco Unity servers that access separate directories must migrate to VPIM Networking instead of using SMTP Networking after upgrading to Cisco Unity 5.0 or later.

Both SMTP Networking and VPIM Networking use SMTP as the mechanism for exchanging messages, but the message format differs. SMTP Networking uses a proprietary message format, while the message format in VPIM Networking adheres to the VPIM industry standard. In addition, VPIM Networking provides functionality that is not available in SMTP Networking. See the "VPIM Networking" chapter for more information.

Prerequisites

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

•The servers have already been upgraded to Cisco Unity 5.x as described in the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange), which is available 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.

Task List for Migrating from SMTP Networking to VPIM Networking

Use the task list that follows to migrate from SMTP Networking to VPIM Networking for messaging between Cisco Unity servers that access different directories. The cross-references take you to detailed procedures, most of which are in other chapters of the Networking Guide. After finishing a procedure, return to this task list and continue with the next item. Do these tasks in both Cisco Unity locations.

1. Uninstall the older version of the Voice Connector that was used for SMTP Networking. See the "Uninstalling the Cisco Unity Voice Connector" section on page 10-4.

2. Make decisions about your numbering plan and gather information needed to configure VPIM Networking. See the "Making Design Decisions and Gathering Needed Information" section on page 7-4.

3. Determine the domain name that will be used for messaging between the remote voice messaging system and Cisco Unity. See the "Determining the Domain Name" section on page 7-5.

4. As applicable, configure DNS or HOSTS files. See the "Resolving Names with IP Addresses" section on page 7-5.

5. Verify network and SMTP connectivity with the remote voice messaging system. See the "Verifying Connectivity with the Remote Voice Messaging System" section on page 7-6.

6. If you have not already done so, extend the Active Directory schema to enable VPIM Networking. See the "Extending the Active Directory Schema" section on page 7-8.

7. 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" section on page 7-9.

8. 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 on page 7-10.

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

9. During the Cisco Unity 5.x upgrade, 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, and VPIM 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, and VPIM 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 on page 7-16.

11. Customize the primary location profile settings. See the "Customizing the Primary Location" section on page 7-18.

12. Convert SMTP delivery locations to VPIM delivery locations, and Internet subscribers to VPIM subscribers, either by running the stored procedure, or by doing the conversion manually:

–To run the stored procedure, see the "Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers" section.

–To convert the VPIM delivery locations and subscribers manually, see the "Manually Converting VPIM Delivery Locations and Subscribers" section.

13. Optionally, customize the delivery location settings that control automatic VPIM directory updates. See the "Customizing VPIM Subscriber Directory Update Settings" section on page 7-28.

14. Optionally, extend identified subscriber messaging to include VPIM subscribers. See the "Extending Identified Subscriber Messaging to Include VPIM Subscribers" section on page 7-34.

Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers

If there are a large number of Internet subscribers to be converted to VPIM subscribers, we recommend that you run the stored procedure during off hours when the Cisco Unity server is not processing very many calls or messages.

To Run the VpimMigrateSMTP Stored Procedure

As a best practice, you should back up the Cisco Unity server before running the stored procedure.

Step 1 Log on to the Cisco Unity Bridgehead server by using the administration account that was selected when Cisco Unity was installed.

Step 2 Open a command prompt window.

Step 3 At the command prompt, enter the following:

osql /d UnityDB /E /Q csp_VpimMigrateSMTP

Note For more information about any of the osql options, enter osql /?

Step 4 After the stored procedure has finished running, close the command prompt window.

Note that the stored procedure adds the VPIM subscribers to the SQL Server database on the Cisco Unity server and then finishes running. However, Cisco Unity still must synchronize the subscriber data with Active Directory. If there are a large number of VPIM subscribers, this synchronization could take up to several hours.

Step 5 Finish the migration by continuing with the procedures in the "Setting Up the Voice Connector for VPIM Networking" section on page 7-10.

Manually Converting VPIM Delivery Locations and Subscribers

If you prefer not to use the VpimMigrateSMTP stored procedure to convert SMTP delivery locations to VPIM delivery locations and Internet subscribers to VPIM subscribers, use the following task list and procedures to do the conversion manually. You do these tasks on the Cisco Unity Bridgehead server.

1. Write down the data on each SMTP delivery location, and then delete the delivery location. See the "To Record SMTP Delivery Location Data and Then Delete the Delivery Location" procedure.

2. Create VPIM delivery locations by using the SMTP delivery location data. See the "To Create VPIM Delivery Locations" procedure.

3. Export Internet subscriber data to a CSV file by using the Subscriber Information Dump tool, available in Tools Depot. See the "To Export Internet Subscriber Data to a CSV File" procedure.

4. Modify the CSV file so that it can be used as the input CSV file for the Cisco Unity Bulk Import wizard. See the "To Modify the CSV File for Use with the Cisco Unity Bulk Import Wizard" procedure.

5. Delete the Internet subscribers and the associated contacts. See the "To Delete the Internet Subscribers and Associated Contacts" procedure.

6. Create VPIM subscribers by using the Cisco Unity Bulk Import wizard with the modified CSV file. See the "To Create VPIM Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard" procedure.

To Record SMTP Delivery Location Data and Then Delete the Delivery Location

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

Step 2 Click the Find icon to search for and display an SMTP delivery location.

Step 3 Make note of the Display Name, Dial ID, and Domain Name on the Delivery Location Profile page.

Step 4 Click the Delete icon to delete the SMTP delivery location.

Step 5 Repeat Step 2 through Step 4 for each SMTP delivery location.

To Create VPIM Delivery Locations

Add the VPIM delivery locations by using the Display Names, Dial IDs, and Domain Names that you had made note of in Step 3 of the previous "To Record SMTP Delivery Location Data and Then Delete the Delivery Location" procedure.

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

Step 2 Click the Add icon.

Step 3 Enter the Display Name and Dial ID for the location.

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

Step 5 Click Add.

Step 6 Record a voice name for the location.

Step 7 Enter the SMTP domain name of the remote Cisco Unity server.

Step 8 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.

Subscribers do not enter this prefix when addressing messages. However, on outgoing messages, the Voice Connector adds the prefix to the beginning of the recipient mailbox number to form the To address. On incoming messages, the Voice Connector 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 9 If needed to accommodate your numbering plan, enter a number in the Cisco Unity Phone Prefix field.

On outgoing messages, the Voice Connector adds this prefix to the beginning of the sender mailbox number to form the From address. On incoming messages, the Voice Connector 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 10 Indicate whether incoming messages from this VPIM location should be converted to another audio format.

Step 11 Indicate whether outbound messages to this VPIM location should be converted to another audio format. Typically, you choose Do Convert Outgoing Messages.

Step 12 Optionally, check the Sender's Recorded Name and/or Sender's vCard check box(es). The data may be used for creating or updating directory entries, if the remote system is configured to allow automatic creation, modification, and deletion of VPIM subscribers for the delivery location corresponding to this system.

Step 13 Click the Save icon.

Step 14 Repeat Step 2 through Step 13 for each delivery location.

To Export Internet Subscriber Data to a CSV File

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 Subscriber Information Dump. The Subscriber Information Dump dialog box opens.

Step 3 In the Subscribers to Dump list, click SMTP Subscribers Only.

Step 4 Indicate the output file name and location.

Step 5 Use the default settings for the Separate Data With and Use Quotes Around fields.

By default, these fields are set respectively to "Commas" and "When the Data Includes a Comma."

Step 6 In the Data to Include in Output File list, check the First Name, Last Name, Primary Extension, and RemoteAddress check boxes. You can also check other check boxes in the list, as applicable.

Step 7 Click Start.

Step 8 When the output is complete, a message box opens with the number of errors encountered in the process. Click OK to view the error log, or Cancel if no errors were encountered.

Step 9 Exit the Subscriber Information Dump and Tools Depot.

To Modify the CSV File for Use with the Cisco Unity Bulk Import Wizard

Step 1 Open the output CSV file in a text editor or spreadsheet application.

Step 2 Modify the column headers in the first row of the CSV file by changing the following headers:

First Name,Last Name,Primary Extension,RemoteAddress

to:

FIRST_NAME,LAST_NAME,DTMF_ACCESS_ID,REMOTE_ADDRESS

Step 3 If all VPIM subscribers will be associated with the same VPIM delivery location, skip to Step 4. (You do not need to include the DELIVERY_LOCATION column header because you will be prompted to specify a default delivery location when running Cisco Unity Bulk Import wizard.)

Otherwise, add the DELIVERY_LOCATION column header to the first row and enter the applicable delivery location Dial ID in each data row. If a row does not contain a value for DELIVERY_LOCATION, the default delivery location that the Cisco Unity Bulk Import wizard prompts for will be used.

Step 4 Change any other column headers as applicable. See the Cisco Unity Bulk Import wizard Help for details.

Step 5 In the CSV file, do a search and replace to change VOICE: to VPIM: in each remote address.

Step 6 If the Dial IDs of the VPIM delivery locations are different from the Dial IDs that were in the SMTP delivery locations, change the Dial ID in each remote address. Remote addresses are in the format:

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

Step 7 Save and close the CSV file.

To Delete the Internet Subscribers and Associated Contacts

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

Step 2 In the tree in the left pane, expand the container in which users are created.

Step 3 In the right pane, click the Type column header so that all of the contacts are listed together.

Step 4 Select the contacts that are associated with the Internet subscribers.

Step 5 Right-click the highlighted selection and click Delete.

The Cisco Unity directory monitor service will detect the change the next time it synchronizes with the directory, and the associated Internet subscribers will be deleted from Cisco Unity.

Step 6 Exit Active Directory Users and Computers.

Step 7 Verify that the Internet subscribers have been deleted from Cisco Unity by doing the following sub-steps:

a. In the Cisco Unity Administrator, go to any page in the Subscribers > Subscribers section.

b. Click the Find icon and search for an Internet subscriber whose associated contact was deleted in Active Directory Users and Computers. You may need to wait for the deletion of the contacts to be propagated to Cisco Unity.

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

Step 1 Prepare a subscriber template that will be used for creating the VPIM subscribers.

Step 2 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 instructions.

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

Step 4 Accept the default, CSV File, and click Next.

Step 5 Specify where the log files should be saved, and click Next.

Step 6 On the Choose Subscriber Type dialog box, click VPIM, and click Next.

Step 7 Click Next, and proceed through the wizard. When you get to the Select the CSV File dialog box, use the CSV file that you modified in the "To Modify the CSV File for Use with the Cisco Unity Bulk Import Wizard" procedure.

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 "To Correct Errors That Occurred When Importing Data from a CSV File" procedure.

Step 8 When the VPIM subscriber accounts are created, click Finish.

Step 9 If you had import errors, but in Step 7 you chose to correct them later, see the "To Correct Errors That Occurred When Importing Data from a CSV File" procedure.

If you had no import errors, or if all errors have now been corrected, finish the migration by going to the "Setting Up the Voice Connector for VPIM Networking" section on page 7-10.

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

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).

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.

	Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
	Migrating from SMTP Networking to VPIM Networking
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange) Index Preface Networking in Cisco Unity Digital Networking Cross-Server Logon, Transfers, and Live Reply Internet Subscribers AMIS Networking Bridge Networking VPIM Networking Using VPIM for Networking with Cisco Unity Express or Other Cisco Unity Systems Primary Location Settings Upgrading or Uninstalling Networking Options Migrating from SMTP Networking to VPIM Networking Glossary	Download this chapter Migrating from SMTP Networking to VPIM Networking Download the complete book PDF Version of the Entire Guide (PDF - 5 MB) Feedback Table Of Contents Migrating from SMTP Networking to VPIM Networking Overview Prerequisites Task List for Migrating from SMTP Networking to VPIM Networking Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers Manually Converting VPIM Delivery Locations and Subscribers Migrating from SMTP Networking to VPIM Networking Overview This chapter provides information on migrating from SMTP Networking to VPIM Networking for messaging between Cisco Unity servers that access different directories. Because Cisco Unity 4.x was the last train that supported the SMTP Networking option, customers who need to network Cisco Unity servers that access separate directories must migrate to VPIM Networking instead of using SMTP Networking after upgrading to Cisco Unity 5.0 or later. Both SMTP Networking and VPIM Networking use SMTP as the mechanism for exchanging messages, but the message format differs. SMTP Networking uses a proprietary message format, while the message format in VPIM Networking adheres to the VPIM industry standard. In addition, VPIM Networking provides functionality that is not available in SMTP Networking. See the "VPIM Networking" chapter for more information. Prerequisites Before starting the migration, verify that the following prerequisites have been met: •The servers have already been upgraded to Cisco Unity 5.x as described in the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange), which is available 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. Task List for Migrating from SMTP Networking to VPIM Networking Use the task list that follows to migrate from SMTP Networking to VPIM Networking for messaging between Cisco Unity servers that access different directories. The cross-references take you to detailed procedures, most of which are in other chapters of the Networking Guide. After finishing a procedure, return to this task list and continue with the next item. Do these tasks in both Cisco Unity locations. 1. Uninstall the older version of the Voice Connector that was used for SMTP Networking. See the "Uninstalling the Cisco Unity Voice Connector" section on page 10-4. 2. Make decisions about your numbering plan and gather information needed to configure VPIM Networking. See the "Making Design Decisions and Gathering Needed Information" section on page 7-4. 3. Determine the domain name that will be used for messaging between the remote voice messaging system and Cisco Unity. See the "Determining the Domain Name" section on page 7-5. 4. As applicable, configure DNS or HOSTS files. See the "Resolving Names with IP Addresses" section on page 7-5. 5. Verify network and SMTP connectivity with the remote voice messaging system. See the "Verifying Connectivity with the Remote Voice Messaging System" section on page 7-6. 6. If you have not already done so, extend the Active Directory schema to enable VPIM Networking. See the "Extending the Active Directory Schema" section on page 7-8. 7. 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" section on page 7-9. 8. 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 on page 7-10. Caution Installing the Voice Connector on an Exchange 2007 server is not supported. 9. During the Cisco Unity 5.x upgrade, 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, and VPIM 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, and VPIM 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 on page 7-16. 11. Customize the primary location profile settings. See the "Customizing the Primary Location" section on page 7-18. 12. Convert SMTP delivery locations to VPIM delivery locations, and Internet subscribers to VPIM subscribers, either by running the stored procedure, or by doing the conversion manually: –To run the stored procedure, see the "Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers" section. –To convert the VPIM delivery locations and subscribers manually, see the "Manually Converting VPIM Delivery Locations and Subscribers" section. 13. Optionally, customize the delivery location settings that control automatic VPIM directory updates. See the "Customizing VPIM Subscriber Directory Update Settings" section on page 7-28. 14. Optionally, extend identified subscriber messaging to include VPIM subscribers. See the "Extending Identified Subscriber Messaging to Include VPIM Subscribers" section on page 7-34. Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers If there are a large number of Internet subscribers to be converted to VPIM subscribers, we recommend that you run the stored procedure during off hours when the Cisco Unity server is not processing very many calls or messages. To Run the VpimMigrateSMTP Stored Procedure As a best practice, you should back up the Cisco Unity server before running the stored procedure. Step 1 Log on to the Cisco Unity Bridgehead server by using the administration account that was selected when Cisco Unity was installed. Step 2 Open a command prompt window. Step 3 At the command prompt, enter the following: osql /d UnityDB /E /Q csp_VpimMigrateSMTP Note For more information about any of the osql options, enter osql /? Step 4 After the stored procedure has finished running, close the command prompt window. Note that the stored procedure adds the VPIM subscribers to the SQL Server database on the Cisco Unity server and then finishes running. However, Cisco Unity still must synchronize the subscriber data with Active Directory. If there are a large number of VPIM subscribers, this synchronization could take up to several hours. Step 5 Finish the migration by continuing with the procedures in the "Setting Up the Voice Connector for VPIM Networking" section on page 7-10. Manually Converting VPIM Delivery Locations and Subscribers If you prefer not to use the VpimMigrateSMTP stored procedure to convert SMTP delivery locations to VPIM delivery locations and Internet subscribers to VPIM subscribers, use the following task list and procedures to do the conversion manually. You do these tasks on the Cisco Unity Bridgehead server. 1. Write down the data on each SMTP delivery location, and then delete the delivery location. See the "To Record SMTP Delivery Location Data and Then Delete the Delivery Location" procedure. 2. Create VPIM delivery locations by using the SMTP delivery location data. See the "To Create VPIM Delivery Locations" procedure. 3. Export Internet subscriber data to a CSV file by using the Subscriber Information Dump tool, available in Tools Depot. See the "To Export Internet Subscriber Data to a CSV File" procedure. 4. Modify the CSV file so that it can be used as the input CSV file for the Cisco Unity Bulk Import wizard. See the "To Modify the CSV File for Use with the Cisco Unity Bulk Import Wizard" procedure. 5. Delete the Internet subscribers and the associated contacts. See the "To Delete the Internet Subscribers and Associated Contacts" procedure. 6. Create VPIM subscribers by using the Cisco Unity Bulk Import wizard with the modified CSV file. See the "To Create VPIM Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard" procedure. To Record SMTP Delivery Location Data and Then Delete the Delivery Location Step 1 In the Cisco Unity Administrator, go to the Network > Delivery Locations > Profile page. Step 2 Click the Find icon to search for and display an SMTP delivery location. Step 3 Make note of the Display Name, Dial ID, and Domain Name on the Delivery Location Profile page. Step 4 Click the Delete icon to delete the SMTP delivery location. Step 5 Repeat Step 2 through Step 4 for each SMTP delivery location. To Create VPIM Delivery Locations Add the VPIM delivery locations by using the Display Names, Dial IDs, and Domain Names that you had made note of in Step 3 of the previous "To Record SMTP Delivery Location Data and Then Delete the Delivery Location" procedure. Step 1 In the Cisco Unity Administrator, go to the Network > Delivery Locations > Profile page. Step 2 Click the Add icon. Step 3 Enter the Display Name and Dial ID for the location. Step 4 Select VPIM as the Destination Type for the location. Step 5 Click Add. Step 6 Record a voice name for the location. Step 7 Enter the SMTP domain name of the remote Cisco Unity server. Step 8 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. Subscribers do not enter this prefix when addressing messages. However, on outgoing messages, the Voice Connector adds the prefix to the beginning of the recipient mailbox number to form the To address. On incoming messages, the Voice Connector 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 9 If needed to accommodate your numbering plan, enter a number in the Cisco Unity Phone Prefix field. On outgoing messages, the Voice Connector adds this prefix to the beginning of the sender mailbox number to form the From address. On incoming messages, the Voice Connector 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 10 Indicate whether incoming messages from this VPIM location should be converted to another audio format. Step 11 Indicate whether outbound messages to this VPIM location should be converted to another audio format. Typically, you choose Do Convert Outgoing Messages. Step 12 Optionally, check the Sender's Recorded Name and/or Sender's vCard check box(es). The data may be used for creating or updating directory entries, if the remote system is configured to allow automatic creation, modification, and deletion of VPIM subscribers for the delivery location corresponding to this system. Step 13 Click the Save icon. Step 14 Repeat Step 2 through Step 13 for each delivery location. To Export Internet Subscriber Data to a CSV File 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 Subscriber Information Dump. The Subscriber Information Dump dialog box opens. Step 3 In the Subscribers to Dump list, click SMTP Subscribers Only. Step 4 Indicate the output file name and location. Step 5 Use the default settings for the Separate Data With and Use Quotes Around fields. By default, these fields are set respectively to "Commas" and "When the Data Includes a Comma." Step 6 In the Data to Include in Output File list, check the First Name, Last Name, Primary Extension, and RemoteAddress check boxes. You can also check other check boxes in the list, as applicable. Step 7 Click Start. Step 8 When the output is complete, a message box opens with the number of errors encountered in the process. Click OK to view the error log, or Cancel if no errors were encountered. Step 9 Exit the Subscriber Information Dump and Tools Depot. To Modify the CSV File for Use with the Cisco Unity Bulk Import Wizard Step 1 Open the output CSV file in a text editor or spreadsheet application. Step 2 Modify the column headers in the first row of the CSV file by changing the following headers: First Name,Last Name,Primary Extension,RemoteAddress to: FIRST_NAME,LAST_NAME,DTMF_ACCESS_ID,REMOTE_ADDRESS Step 3 If all VPIM subscribers will be associated with the same VPIM delivery location, skip to Step 4. (You do not need to include the DELIVERY_LOCATION column header because you will be prompted to specify a default delivery location when running Cisco Unity Bulk Import wizard.) Otherwise, add the DELIVERY_LOCATION column header to the first row and enter the applicable delivery location Dial ID in each data row. If a row does not contain a value for DELIVERY_LOCATION, the default delivery location that the Cisco Unity Bulk Import wizard prompts for will be used. Step 4 Change any other column headers as applicable. See the Cisco Unity Bulk Import wizard Help for details. Step 5 In the CSV file, do a search and replace to change VOICE: to VPIM: in each remote address. Step 6 If the Dial IDs of the VPIM delivery locations are different from the Dial IDs that were in the SMTP delivery locations, change the Dial ID in each remote address. Remote addresses are in the format: VPIM:<Dial ID>_<Remote Mailbox Number> Step 7 Save and close the CSV file. To Delete the Internet Subscribers and Associated Contacts Step 1 Start Active Directory Users and Computers. (On the Windows Start menu, click Programs > Administrative Tools > Active Directory Users and Computers.) Step 2 In the tree in the left pane, expand the container in which users are created. Step 3 In the right pane, click the Type column header so that all of the contacts are listed together. Step 4 Select the contacts that are associated with the Internet subscribers. Step 5 Right-click the highlighted selection and click Delete. The Cisco Unity directory monitor service will detect the change the next time it synchronizes with the directory, and the associated Internet subscribers will be deleted from Cisco Unity. Step 6 Exit Active Directory Users and Computers. Step 7 Verify that the Internet subscribers have been deleted from Cisco Unity by doing the following sub-steps: a. In the Cisco Unity Administrator, go to any page in the Subscribers > Subscribers section. b. Click the Find icon and search for an Internet subscriber whose associated contact was deleted in Active Directory Users and Computers. You may need to wait for the deletion of the contacts to be propagated to Cisco Unity. To Create VPIM Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard Step 1 Prepare a subscriber template that will be used for creating the VPIM subscribers. Step 2 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 instructions. Step 3 On the bridgehead Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Bulk Import. Step 4 Accept the default, CSV File, and click Next. Step 5 Specify where the log files should be saved, and click Next. Step 6 On the Choose Subscriber Type dialog box, click VPIM, and click Next. Step 7 Click Next, and proceed through the wizard. When you get to the Select the CSV File dialog box, use the CSV file that you modified in the "To Modify the CSV File for Use with the Cisco Unity Bulk Import Wizard" procedure. 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 "To Correct Errors That Occurred When Importing Data from a CSV File" procedure. Step 8 When the VPIM subscriber accounts are created, click Finish. Step 9 If you had import errors, but in Step 7 you chose to correct them later, see the "To Correct Errors That Occurred When Importing Data from a CSV File" procedure. If you had no import errors, or if all errors have now been corrected, finish the migration by going to the "Setting Up the Voice Connector for VPIM Networking" section on page 7-10. To Correct Errors That Occurred When Importing Data from a CSV File 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). 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.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks