Table Of Contents
Migrating from SMTP Networking to VPIM Networking
Overview
Prerequisites
Task List for Migrating from SMTP Networking to VPIM Networking
Procedures: Migrating from SMTP Networking to VPIM Networking
Extending the Active Directory Schema
Uninstalling the Cisco Unity Voice Connector
Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers
Manually Converting VPIM Delivery Locations and Subscribers
Setting Up the Voice Connector for VPIM Networking
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 4.0(x) is the last train that will support the SMTP Networking option, we recommend that customers who need to network Cisco Unity servers that access separate directories migrate to VPIM Networking instead of using SMTP Networking.
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.
See the following sections in this chapter for more information:
•
Prerequisites
•Task List for Migrating from SMTP Networking to VPIM Networking
Prerequisites
Before starting the migration, verify that the following prerequisites have been met.
•Cisco Unity is already installed on the servers, and they are connected to the network.
•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 Cisco Unity Networking Options Requirements, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_table09186a0080531ba9.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. Do these tasks in both Cisco Unity locations.
1. Extend the Active Directory schema to enable VPIM Networking. See the "Extending the Active Directory Schema" section.
2. Uninstall the older version of the Voice Connector that was used for SMTP Networking. See the "Uninstalling the Cisco Unity Voice Connector" section.
3. 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.
4. Install the new version of the Voice Connector, and select VPIM as the address type that the Voice Connector will handle. See the "Setting Up the Voice Connector for VPIM Networking" section.
Procedures: Migrating from SMTP Networking to VPIM Networking
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 2000 VPIM 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.
Uninstalling the Cisco Unity Voice Connector
The uninstall procedure that you use depends on the Cisco Unity Voice Connector version that is installed, and whether it is installed on an Exchange 2000 (or Exchange 2003) server or on an Exchange 5.5 server. Beginning with Cisco Unity version 4.0(1), the Voice Connector was assigned a version number separate from the Cisco Unity version number.
To determine the version of an already installed Voice Connector, see the following procedures:
•To Determine the Voice Connector Version in Use: Cisco Unity 4.0 and Later, Voice Connector 10.0 and Later
•To Determine the Voice Connector Version in Use: Cisco Unity 3.0 through 3.1
To uninstall the Voice Connector, see the following procedures:
•To Uninstall the Voice Connector for Exchange 2000: Cisco Unity 3.1 and Later, Voice Connector 10.0 and Later
•To Uninstall the Voice Connector for Exchange 5.5: Cisco Unity 3.1(2) or Later, Voice Connector 10.0 and Later
•To Uninstall the Voice Connector for Exchange 5.5: Cisco Unity 2.4(6.x), 3.0(x), or 3.1(1)
To Determine the Voice Connector Version in Use: Cisco Unity 4.0 and Later, Voice Connector 10.0 and Later
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 In Windows Explorer or My Computer, browse to the applicable directory:
Exchange 2000
or Exchange 2003
|
<ExchangeServerPath>\VoiceGateway\Bin
|
Exchange 5.5
|
<ExchangeServerPath>\Connect\Voice\Bin
|
Step 3 Right-click GwIvc.exe, and click Properties.
Step 4 Click the Version tab in the Properties window.
Step 5 In the Item Name box, click Product Version to view the product version in the Value box.
To Determine the Voice Connector Version in Use: Cisco Unity 3.0 through 3.1
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 In Windows Explorer or My Computer, browse to the applicable directory:
Exchange 2000
|
<ExchangeServerPath>\VoiceGateway\Bin\LocalizedFiles\ENU
|
Exchange 5.5
|
<ExchangeServerPath>\Voice\Bin\LocalizedFiles\ENU
|
Step 3 Right-click SetupRes.dll, and click Properties.
Step 4 In the Properties window, click the Version tab to view the File Version.
To Uninstall the Voice Connector for Exchange 2000: Cisco Unity 3.1 and Later, Voice Connector 10.0 and Later
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 3 Click Exchange 2000 Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
Step 5 On the Windows Start menu, click Programs > Microsoft Exchange > System Manager.
Step 6 Expand Servers\<Server name>\<Storage group>\Mailbox Store\Mailboxes for the server on which the Voice Connector was installed.
The mailbox for the Voice Connector is named "AvExchangeIVC_<Servername>" or "Exchange 2000 Voice Connector (<Servername>)."
Step 7 Right-click Mailboxes in the left pane, and select Run Cleanup Agent.
Step 8 After the Cleanup Agent has run, right-click each Voice Connector mailbox marked with the red X icon and select Purge. Click Yes in the warning dialog box.
Step 9 Close the Exchange System Manager.
To Uninstall the Voice Connector for Exchange 5.5: Cisco Unity 3.1(2) or Later, Voice Connector 10.0 and Later
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
To Uninstall the Voice Connector for Exchange 5.5: Cisco Unity 2.4(6.x), 3.0(x), or 3.1(1)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 In the CD-ROM drive, insert Cisco Unity Disc 1 for the version of the Voice Connector that is installed, and browse to the VoiceGateway directory.
Step 3 Double-click Setup.exe, and click Next.
The Setup program detects that the Voice Connector is already installed, and the Uninstall dialog box appears.
Step 4 Click Next, and click Yes in the warning dialog box.
Step 5 When the uninstall is complete, click Finish to exit the program and restart the server.
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 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 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.
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" section.
2. Create VPIM delivery locations by using the SMTP delivery location data. See the "To Create VPIM Delivery Locations" section.
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" section.
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" section.
5. Delete the Internet subscribers and the associated contacts. See the "To Delete the Internet Subscribers and Associated Contacts" section.
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" section.
To Record SMTP Delivery Location Data
Step 1 In the Cisco Unity Administrator, go to 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 had been entered on the SMTP delivery location pages.
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.
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 strips 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 strips 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. Refer to 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 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. Refer to 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.
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.
Setting Up the Voice Connector for VPIM Networking
Although there are two Voice Connector installation programs included on Cisco Unity Disc 1, the Voice Connector for Exchange 2000 is the only one supported 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.
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 LocalSystem account. The account that the service logs on as should not be changed.
If you plan to allow Cisco Unity to perform automatic VPIM subscriber directory updates, version 11.0(3) or later of the Voice Connector is required on any system(s) that will receive incoming VPIM messages.
To Install the Voice Connector for Exchange 2000
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 you are installing the Voice Connector from Cisco Unity DVD 1 or CD 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 4 Double-click Install.exe and then click Next.
Step 5 In the Address Types dialog box, check VPIM.
Step 6 Click Next. The VPIM Transport Sink dialog box is displayed.
Step 7 Optionally, check Install SMTP Transport Event Sink.
If you are installing the Voice Connector on multiple Exchange servers, in most cases you need to install the VPIM Transport Event Sink only once. The Exchange server on which the VPIM Transport Event Sink is installed should be the Exchange server that will receive incoming VPIM messages. Only one instance of the VPIM Transport Event Sink is necessary if all VPIM messages will be routed through a single Exchange server. If incoming VPIM messages will be routed through multiple Exchange servers, the Voice Connector and VPIM Transport Event Sink should be installed on each of these servers.
Step 8 If you checked Install SMTP Transport Event Sink in Step 7, enter the SMTP Domain. This is the domain name used in your e-mail addresses/recipient policy, which does not have to be the same domain as that of the server on which the SMTP Transport Event Sink is being installed. Typically, the domain entered here is the same as the one that will be entered on the Primary Location page.
Step 9 Click Next twice.
Step 10 When setup is complete, click Finish to exit Setup and restart the server.
Step 11 Enable virus-scanning services on the server.
Step 12 In order to view Voice Connector properties in Exchange System Manager, Microsoft Windows Script Host version 5.6 or later must be installed on the Exchange server. Continue with the "To Determine Whether the Microsoft Windows 2000 Script Host Should Be Updated" procedure.
Note 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 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>\First 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.
Feedback
