11-7
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 11 Migrating from SMTP Networking to VPIM Networking
Task List for Migrating from SMTP Networking to VPIM Networking
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 on page 11-6.
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 on page 11-7.
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 on page 11-7.
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.