Page 1: Meridian Mail To Callpilot Migration Utility Guide
Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502...
Page 2 The process of transmitting data and call messaging between the CallPilot server and the switch or system is proprietary to Nortel Networks. Any other use of the data and the transmission process is a violation of the user license unless speciﬁcally authorized in writing by Nortel Networks prior to such use. Violations of the license by alternative usage of any portion of this process or the related hardware constitutes grounds for an immediate termination of the license and Nortel Networks reserves the right to seek all allowable remedies for such breach.
Page 3 QUICKTIME is a trademark of Apple Computer, Inc. RADISYS is a trademark of Radisys Corporation. ROLM is a trademark of Siemens ROLM Communications Inc. SLR4, SLR5, and TANDBERG are trademarks of Tandberg Data ASA. SONY is a trademark of Sony Corporation. SYBASE is a trademark of Sybase, Inc.
Page 5: Publication History
CallPilot 5.0, Standard 01.00 of the Meridian Mail to CallPilot Migration Utility Guide is issued for general release. July 2005 CallPilot 4.0, Standard 1.03 of the Meridian Mail to CallPilot Migration Utility Guide is issued for general release. July 2005 CallPilot 4.0, Standard 1.02 of the Meridian Mail to CallPilot Migration Utility...
Page 6 6 Publication History November 2004 Standard 1.0 of the Meridian Mail to CallPilot Migration Utility Guide for CallPilot 3.0 is released for general availability. Minor changes, resulted from addressing CRs, have been made to the document May 2003 Standard 1.0 is released for CallPilot 2.02 (2.01.27.05) to introduce new procedures to migrate Symposium Voice Services (Appendix C) and to introduce the new migrate.exe utility (CallPilot 2.x migrations only) which...
Page 7: Table Of Contents
Migration limitations 16 Reference documents 18 Chapter 3 Planning a Meridian Mail data collection Meridian Mail releases and platforms that can be migrated 19 Data that can or cannot be migrated 20 Meridian Mail system size 22 Types of data collection 24...
Page 8 Disconnecting the tape drive 85 Verifying CallPilot system conﬁguration 85 Verifying CallPilot network database 88 Replacing Meridian Mail with CallPilot 93 Running Meridian Mail and CallPilot at the same time 94 Chapter 7 Troubleshooting Migration problems 107 Correcting precheck inconsistencies 108...
Page 9: Chapter 1 How To Get Help
Getting help over the phone from a Nortel Solutions Center If you don’t ﬁnd the information you require on the Nortel Technical Support Web site, and have a Nortel support contract, you can also get help over the phone from a Nortel Solutions Center.
Page 10 To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to: http://www.nortel.com/erc...
Page 11: Chapter 2 Understanding The Migration Process
About this guide This guide provides guidelines and detailed information for the migration of a Meridian Mail* system to a CallPilot system. You must have a good knowledge of the Meridian Mail and CallPilot systems to be able to perform a migration.
Page 12 If you are migrating to a T1/SMDI system, DNs presented over the SMDI must be 10 digits in length. Unlike Meridian Mail, CallPilot does not support the left pad feature which allows for shorter DN lengths. For further information, see the T1/SMDI and CallPilot Server Conﬁguration guide (NN44200-303).
Page 13: Migration Task Flow
— After the switchover, Meridian Mail no longer answers calls and takes new messages. — The messages stored on the Meridian Mail system are available only after the completion of the migration to CallPilot. — Users can retrieve messages from Meridian Mail if you run both systems in parallel for a limited time.
Page 14 Collect Meridian Mail voice messages, as well as Contact Center voice prompts and voice segments, on one or more tapes. Review the Meridian Mail data collection log to find any data collection errors. Install an external tape drive and the tape drive driver on the CallPilot server (if necessary).
Page 15 If the logs indicate that data was not migrated: • add the missing information to CallPilot manually • fix the problem on Meridian Mail and perform the migration again Use the method that is easiest for you. If you create test messages on Meridian Mail, verify that they successfully migrate.
Page 16: Migration Limitations
• You can perform a selective migration only for the following reasons: — The Meridian Mail system to be migrated has more than 7000 users. — The Meridian Mail system is an MSM. — The customer requested a selective migration.
Page 17 If the prompt ﬁle name and mailbox combinations result in ﬁle names that are not unique, the Meridian Mail data collection utility does not collect the prompts in the ﬁles with duplicate names. Segment titles and descriptions The CallPilot Application Builder segment titles and descriptions are shorter than the Meridian Mail segment titles and descriptions.
Page 18: Reference Documents
18 Chapter 2 Understanding the migration process Reference documents Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Copyright © 2007, Nortel Networks...
Page 19: Chapter 3 Planning A Meridian Mail Data Collection
You can migrate data from Meridian Mail systems running Release 11 and later to CallPilot. To migrate data from Meridian Mail systems running releases 8, 9, and 10, you must upgrade the systems to Meridian Mail Release 11 or later before performing the migration to CallPilot.
Page 20: Data That Can Or Cannot Be Migrated
20 Chapter 3 Planning a Meridian Mail data collection The following table summarizes the Meridian Mail platforms and releases that can be migrated to CallPilot. Meridian Mail platform Card Option Enhanced card option Option EC 11 Compact Option Modular Option...
Page 21 • user core and mailbox properties • multiple MWI settings of mailboxes on Meridian Mail • duplicate DNs — Meridian Mail users with duplicate primary and secondary DN entries • user voice messages • networking sites and locations (local and...
Page 22: Meridian Mail System Size
22 Chapter 3 Planning a Meridian Mail data collection Can be migrated • system distribution lists (SDL) • remote voice users • directory entry users • personal verification recording • voice segments in menus • announcements • fax segments Note 1: CallPilot currently supports only one customer. Mailboxes with the same numbers that exist in different customer groups are not migrated.
Page 23 Systems with many voice segments or fax items Voice segments and Application Builder applications If a Meridian Mail system has many voice or fax segments, you can perform the migration in multiple sessions. Meridian Mail to CallPilot Migration Utility Guide Copyright ©...
Page 24: Types Of Data Collection
24 Chapter 3 Planning a Meridian Mail data collection The voice segments or fax items of a Meridian Mail system must be converted to CallPilot Application Builder applications. The migration utility migrates the Meridian Mail voice segments and fax items to CallPilot, but it does not create CallPilot applications.
Page 25: Time Estimates
You must select and collect the data groups in the sequence indicated in the preceding list. Use selective data collection if one of the following conditions applies: • The Meridian Mail system has more than 3000 users and more than 200 hours of messages stored. • The Meridian Mail platform is an MSM.
Page 26: Collecting Data In A Single Session
Data collection Message and Contact Center prompt collection Schedule the migration for one ore more maintenance periods. A maintenance period is the time during which the Meridian Mail system can be taken out of service. the total migration time is...
Page 27: Collecting Data In Multiple Sessions
To minimize the migration impact, carefully plan and schedule the migration over several sessions. A Meridian Mail system with more than 96 ports and 2400 hours of storage is too large to be migrated to a single CallPilot system. Contact your distributor or Nortel for information on the appropriate migration strategy.
Page 28 28 Chapter 3 Planning a Meridian Mail data collection Add new users carefully to the Meridian Mail system so that their mailboxes and voice messages are captured at some stage during the data collection. The total message capacity can exceed 2.5 Gbytes if all the messages on the system are collected in one session.
Page 29 The number of users (DNs) that you can assign to a COS depends on the length of the available maintenance period. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Collecting data in multiple sessions 29 Data •...
Page 30 30 Chapter 3 Planning a Meridian Mail data collection To calculate the number of users that you can assign to a COS (x), use the following formula: where • "users" is the total number of users on the system •...
Page 31: Meridian Mail Data Collection Check List
• one tape for the corresponding voice messages and Contact Center prompts Meridian Mail data collection check list Complete the following tasks before you begin the Meridian Mail data collection. Item Review the system event and error reports (SEER) to •...
Page 32 SDL names do not contain punctuation. • each SDL name is unique. Ensure that last names are defined in the Meridian Mail Directory Entry Users. The last name field is mandatory in CallPilot. A migrated user whose last name field was empty in Meridian Mail cannot be selected in CallPilot Manager.
Page 33 If the prompt file name and mailbox number combination results in file names that are not unique, the prompts in the duplicate files are not collected by the Meridian Mail data collection utility. Ensure that the network site names and switch location names are unique.
Page 34 Meridian Mail system. Ensure that the tape drive is installed and operational on the Meridian Mail system. Ensure that you have the most recent Meridian Mail to CallPilot migration tape. The Nortel migration package contains the most recent migration tape.
Page 35: Chapter 4 Collecting Meridian Mail Data
"Reviewing the Meridian Mail migration log" (page 53) Installing the data collection utility Tape drive requirements Depending on the software release and type of hardware platform, the Meridian Mail system uses one of the following tape drives and tapes: Tape drive Archive Viper Tandberg SLR4 tape drive...
Page 36 36 Chapter 4 Collecting Meridian Mail data If the Meridian Mail system to be migrated uses an Archive Viper tape drive or 250 Mbyte tapes, ensure that you take to the customer site a Tandberg SLR4 (TDC4220) tape drive and a supply of 2.5 Gbyte tapes.
Page 37 Wait ten seconds and then power up the Meridian Mail system. If your Meridian Mail system is a Card Option systems, re-enable the AML after turning on the power. Result: Meridian Mail displays diagnostic routines and then pauses for approximately ﬁve minutes while the tape is automatically...
Page 38: Soft Keys
Soft keys During the collection of Meridian Mail data, you are instructed to select soft keys. The soft keys are the black buttons at the bottom of the screens of the migration utility. The functions of the soft keys that appear on a speciﬁc screen depend on the information displayed on that screen.
Page 39: Launching The Data Collection Utility
Launching the data collection utility The screens on your Meridian Mail system can differ from those shown in this guide, depending on the Meridian Mail release number and the type and number of features installed. To launch the data collection utility...
Page 40 40 Chapter 4 Collecting Meridian Mail data Select the Other menu option as follows: enter the option number (13) at the Select an item prompt and then press Enter. Result: The Other menu appears. Select the Collect CallPilot Data option as follows: enter the option number (6) at the Select an item prompt and then press Enter.
Page 41: Collecting Meridian Mail Data
Continue with one of the following tasks, as required: "Collecting Meridian Mail data" (page 41) "Collecting Symposium Call Center Server data" (page 48) "Reviewing the Meridian Mail migration log" (page 53) Collecting Meridian Mail data Preliminary The procedure provided in this section starts after the data collection utility...
Page 42 42 Chapter 4 Collecting Meridian Mail data To collect Meridian Mail data Step Action Select the Create Data Migration Tape option on the Collect CallPilot Data screen as follows: enter the option number (1) at the Select an item prompt and then press Enter.
Page 43 VS Voice Segments / Fax Item Data If you perform a selective data collection, collect the data in the sequence shown on the screen, from top to bottom. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Data •...
Page 44 44 Chapter 4 Collecting Meridian Mail data Select the Write All Data soft key by pressing the F3 key. Result: The Selected Users or the Enter Tape Label screen appears. Depending on the screen that appeared, proceed as follows. IF the screen is...
Page 45 Tip: The maximum length of the tape name is 27 characters. Insert a blank tape in the tape drive. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks The plus sign (+) matches 0 or more characters or digits. For example, if you type 776+, mailboxes 776, 7761, 7762, 776123, and so on are selected.
Page 46 Result: The data collection starts. The data collection progress is displayed on the screen. Tip: The data tapes for a Meridian Mail system with 700 mailboxes are created in approximately 30 minutes. The following illustration is an example of screen that appears when the data collection is complete.
Page 47: Collecting Meridian Mail Voice Messages
All option. This option collects message and prompt data for the mailbox. Press Enter. Result: The Enter Tape Label screen appears. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Collecting Meridian Mail voice messages 47 Nortel CallPilot NN44200-502 01.02 Standard...
Page 48: Collecting Contact Center Data
Type the following name for the blank tape that you are using: CallPilot Voice Messages. Insert a blank tape into the Meridian Mail tape drive. Select the OK to Start Writing Tape soft key by pressing F1. Result: The system receives tape descriptor data, then rewinds the tape and writes the prompt data to the tape.
Page 49 ACCESS • Contact Center prompts Note: If Meridian Mail is also used as a front-end IVR subsystem, the migration must be treated as a whole voice processing engine migration. Outline of the Symposium Voice Service Center data collection The procedure of collecting Symposium Voice Service Center data consists of the following main tasks: •...
Page 50 Result: The System/Feature Dependent Tools menu appears. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Note: On a Meridian Mail 13 system, use the Tools user ID and the Tools level password. Nortel CallPilot NN44200-502 01.02 Standard...
Page 51 Data screen as follows: enter the option number (1) at the Select an item prompt and then press Enter. Result: The following screen appears: Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Collecting Contact Center data 51 Nortel CallPilot NN44200-502 01.02 Standard...
Page 52 52 Chapter 4 Collecting Meridian Mail data Select the VS Voice Segments / Fax Item Data option as follows: press the down arrow key to move the cursor to the option line, and then press spacebar to highlight the option.
Page 53: Reviewing The Meridian Mail Migration Log
Reviewing the Meridian Mail migration log Introduction This section describes the methods of reviewing the Meridian Mail migration log: • displaying the migration log on the screen • printing the migration log to a printer The procedures provided in this section start after that the data collection...
Page 54 54 Chapter 4 Collecting Meridian Mail data To print the migration log ﬁle to the printer Step Action Ensure that an operational printer is connected to your system. Select the Write Migration Log File to printer option as follows: •...
Page 55: Chapter 5 Migrating Meridian Mail Data To Callpilot
Hardware, software, media, and networking requirements Introduction Ensure that all the required hardware and software are installed on the CallPilot system before migrating the Meridian Mail data from tape. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Nortel CallPilot NN44200-502 01.02 Standard...
Page 56: Safety Warnings
The IPE server supports the Tandberg SLR5 (NTRH9038) tape drive. This tape drive can read the 2.5 Gbyte tapes that are created on a Meridian Mail system using the Tandberg SLR4 (TDC4220) tape drive.
Page 57: Networking Requirements
Introduction The CallPilot migration utility offers you the option to copy the collected Meridian Mail ﬁles to the CallPilot server before starting the migration. The folder to which the ﬁles are copied is referred to as the staging area. The \nortel\MPCX\Migration\MigrationFiles folder is the staging area.
Page 58: Stopping The Migration
The migration utility offers you the option to delete the ﬁles from the CallPilot staging area when the migration is ﬁnished. Nortel recommends that you do not select the option to delete the staging ﬁles until you are certain that the migration completes successfully. This saves time if you must rerun the migration.
Page 59: Callpilot Migration Check List
Ensure that no users have been added to the CallPilot system. Ensure that all CallPilot restriction/permission list (RPL) names are unique and different than the Meridian Mail RPL names. Ensure that all existing CallPilot mailbox classes are renamed. If a duplicate class of service (COS) is found during the migration, the Meridian Mail COS is renamed to <COS name>_MMail<COS...
Page 60: Migration Sequence
60 Chapter 5 Migrating Meridian Mail data to CallPilot Migration sequence Transfer to CallPilot the system data and the voice messages from tapes in the sequence in which you created the tapes on the Meridian Mail system. Always transfer the system data ﬁrst. IF you are performing...
Page 61: Migrating A System With Many Voice Segments Or Fax Items
Migration utility location The migration utility is located on the CallPilot server hard drive in the \nortel\MPCX\Migration folder. You must run the CallPilot migration utility from this folder only. Do not start the migration utility from another folder. Do not remove the tape from the tape drive during the migration.
Page 62 62 Chapter 5 Migrating Meridian Mail data to CallPilot Insert the appropriate data tape into the tape drive. Ensure that you use the tapes in the order in which they were created. Type readtapelabel at the CI> prompt and then press Enter.
Page 63 MMail tapes to Windows NT format staging area on the CallPilot server. Do you wish to copy the Meridian Mail data files now? Select the ﬁle transfer option (Yes or No) as follows:...
Page 64 Press Enter. Result: The following message appears: Please insert the Meridian Mail data tape in the tape drive and press Enter. Press Enter (you already inserted the data tape into the tape drive). Result: The migration utility performs the following tasks: •...
Page 65: Meridian Mail To Callpilot Migration Utility Guide
Migrating Contact Center data General Perform the tasks associated to the migration of Contact Center data as indicated in the following outline. Step Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks ATTENTION —End— Task Migrate the voice segments.
Page 66: Nortel Callpilot
Handling data that cannot be migrated For GIVE IVR voice services, the information stored in the Meridian Mail VSDN table and the voice menu structure is critical. As this data cannot be automatically migrated, you must use Application Builder to: •...
Page 67: Meridian Mail To Callpilot Migration Utility Guide
To migrate Contact Center voice segments and voice prompts to CallPilot If you perform a selective data collection from Meridian Mail, you must perform a selective data migration to CallPilot. Do not remove the tape from the tape drive during the migration.
Page 68: Meridian Mail To Callpilot Migration Utility Guide
If you are executing the utility for the first time, you must copy the data from the MMail tapes to Windows NT format staging area on the CallPilot server. Do you wish to copy the Meridian Mail data files now? proceed to "Correcting precheck inconsistencies" (page 108) Analyzing System...
Page 69: Meridian Mail To Callpilot Migration Utility Guide
If you close the MS-DOS window without typing quit, the migration transaction log is not created. Check the MigTransaction.log ﬁle. If you create any test messages on Meridian Mail, verify that they successfully migrate. Log in to the CallPilot mailbox and review the messages.
Page 70: Meridian Mail To Callpilot Migration Utility Guide
70 Chapter 5 Migrating Meridian Mail data to CallPilot Reviewing the migration log and summary Migration transaction log The log ﬁle name uses the following convention to deﬁne its structure: MigTransaction<yymmddhhmmss>.log, where yymmdd represents the date and hhmmss represents the time in the 24-hour format. The date and time in the ﬁle name allow you to:...
Page 71: Meridian Mail To Callpilot Migration Utility Guide
The service ID file name [_F1\cust\cust1\nm_abd\nm_mig\MS1760001] The service ID file name [_F1\cust\cust1\nm_abd\nm_mig\AS1540401] The service ID file name Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Reviewing the migration log and summary 71 THEN COS #[11] User #[700]...
Page 72: Meridian Mail To Callpilot Migration Utility Guide
72 Chapter 5 Migrating Meridian Mail data to CallPilot [_F1\cust\cust1\nm_abd\nm_mig\AS1540402] ** Monday, February 18, 2002 [05:12:21 PM] ** ************| Summary of Data Migration |************ System and Customer Profile Data Migration: ------------------------------------------- System Record: Customer Record: Tenant Record: Messaging Parameters: Security Parameters:...
Page 73: Meridian Mail To Callpilot Migration Utility Guide
------------------------------- Total Number of Services attempted: Total Number of Services created/updated successfully: Total Number of Services in Error: Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Reviewing the migration log and summary 73 <12> <12> <0>...
Page 74: Meridian Mail To Callpilot Migration Utility Guide
Please check the log file (MigTransaction.log) for details. Reviewing the CallPilot event log Nortel recommends that you review the CallPilot event log for errors after a migration. You can view the event log by using one of the following methods: •...
Page 75: Meridian Mail To Callpilot Migration Utility Guide
CallPilot system. If a COS or RPL on the CallPilot system has the same name, the migration utility does not overwrite it with the collected Meridian Mail data. The following events occur when the migration utility ﬁnds duplicate names during the migration to CallPilot: •...
Page 76: Meridian Mail To Callpilot Migration Utility Guide
If a network site or switch location is already deﬁned on CallPilot with the same name as in Meridian Mail, the migration utility does not overwrite it with Meridian Mail data. This ensures that any changes that you make to the network database on CallPilot after the ﬁrst migration attempt are not lost.
Page 77: Meridian Mail To Callpilot Migration Utility Guide
Fax services A migrated fax service has the preﬁx FS1, followed by the service ID from the Meridian Mail VSDN table. For example, a fax service with an ID of 30000 appears as FS130000 in Application Builder. The description of the application is as follows: "Migrated from Fax Service FS130000."...
Page 78: Meridian Mail To Callpilot Migration Utility Guide
Click a migrated voice service and then click Open. For illustration purposes, a menu (MS123000) is selected. The service ID of this menu is 23000 in the Meridian Mail VSDN table. Based on your knowledge of the Meridian Mail system, determine the VSDN IDs of the services that this application includes.
Page 79: Meridian Mail To Callpilot Migration Utility Guide
Tip: The block must match the type of voice service that you open (in this example, a menu). Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Nortel CallPilot NN44200-502 01.02 Standard...
Page 80: Meridian Mail To Callpilot Migration Utility Guide
Conﬁgure the block according to the requirements of your application, as the voice service was conﬁgured in Meridian Mail. Click OK to close the Properties dialog box. Perform the following tasks for each service that must be included in...
Page 81: Meridian Mail To Callpilot Migration Utility Guide
Connect the menu keys to the imported application according to your conﬁguration requirements and to the structure of the service migrated from Meridian Mail; for example, connect key 1 to the MS123100 block. Meridian Mail to CallPilot Migration Utility Guide Copyright ©...
Page 82: Meridian Mail To Callpilot Migration Utility Guide
82 Chapter 5 Migrating Meridian Mail data to CallPilot Save the completed application. To publish the application in the CallPilot SDN table Step Action Open CallPilot Manager. Click System > Service Directory Number. Result: The following page appears on the screen.
Page 83: Meridian Mail To Callpilot Migration Utility Guide
Select the name of the application that you want to put into service from the Application Name drop-down list box. Click Save. Result: The migrated Meridian Mail application can now be used in CallPilot. Test the application before use, and ensure that each key is associated with the correct menu option.
Page 84: Meridian Mail To Callpilot Migration Utility Guide
Format of migrated voice items Announcements and prompts are considered to be different in Meridian Mail voice services. You can use announcements in multiple services, but you can use a voice prompt only in one service. However, both announcements and voice prompts are classiﬁed as voice items in Application Builder.
Page 85: Nortel Callpilot
During the migration to CallPilot, some ﬁelds are converted to default values, because the information cannot be migrated from Meridian Mail to CallPilot, or the information did not exist in Meridian Mail. Refer to that can or cannot be migrated" (page Meridian Mail to CallPilot Migration Utility Guide Copyright ©...
Page 86: Meridian Mail To Callpilot Migration Utility Guide
Verifying mailboxes and mailbox owners CallPilot mailboxes must be three or more digits in length. If a Meridian Mail user’s mailbox number is less than three digits in length, the mailbox is not migrated. Warning messages are generated in the transaction log ﬁle and displayed on screen.
Page 87: Meridian Mail To Callpilot Migration Utility Guide
If a data migration is not completed because of an error, then resolve the error before rerunning the migration. Verifying system distribution lists The Meridian Mail system distribution lists are known in CallPilot as shared distribution lists (SDL). A Meridian Mail system distribution list, whose number is less than three digits in length, is not migrated to CallPilot.
Page 88: Meridian Mail To Callpilot Migration Utility Guide
This ensures that any changes you make after the ﬁrst migration attempt are not lost. If you intend to run both Meridian Mail and CallPilot at the same time, then review "Running Meridian Mail and CallPilot at the same time" (page 94) before verifying the network database conﬁguration.
Page 89: Nortel Callpilot
Note: The transaction log ﬁles capture the protocol changes. Network sites Ensure that all the sites present in the Meridian Mail network database are migrated. If any sites or switch locations are missing, you must add them manually in CallPilot.
Page 90: Meridian Mail To Callpilot Migration Utility Guide
90 Chapter 6 Performing post-migration tasks If there were any duplicated site names on Meridian Mail, only the site or location associated with the ﬁrst occurrence of the name is migrated to CallPilot. Subsequent occurrences are not migrated. The same rule applies to switch location names that are duplicated within a particular site.
Page 91: Meridian Mail To Callpilot Migration Utility Guide
Nortel recommends that you verify the items listed in the following table after you completed the migration to CallPilot. Item Server type CallPilot server name Site ID Protocol Connections DN1, DN2, and DN3 Enterprise networking initiating password Enterprise networking responding...
Page 92: Meridian Mail To Callpilot Migration Utility Guide
Open AMIS delivery schedules • economy delivery schedules • stale times Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Value after migration to CallPilot These options can be disabled if the networking protocol was changed during the migration.
Page 93: Meridian Mail To Callpilot Migration Utility Guide
CallPilot. Using MAT when upgrading from Meridian Mail If Meridian Mail is still present on the Meridian 1 switch, and VMBA data is programmed in the Meridian Administration Tools (MAT) for a set that is to be migrated to CallPilot, delete the VMBA information through MAT on a per set basis.
Page 94: Nortel Callpilot
Sample network setup If you plan to migrate all your Meridian Mail users to CallPilot, ensure ﬁrst that CallPilot works as expected and implement the CallPilot system with a limited number of users. The CallPilot system is set up to reside together with the Meridian Mail system, as illustrated below.
Page 95: Nortel Callpilot
Site conﬁguration You must allow users on the Meridian Mail and CallPilot systems to address messages to each other. Therefore, you must deﬁne each system as a remote site in the other system network database so that: •...
Page 96: Nortel Callpilot
96 Chapter 6 Performing post-migration tasks Dialing plans To accommodate both Meridian Mail and CallPilot systems, as well as to minimize the switch conﬁguration effort, Nortel recommends that you use one of the following options: • "Option 1: To change the current dialing plan to use digit overlap" (page 96).
Page 97: Meridian Mail To Callpilot Migration Utility Guide
Modify the existing dialing plan for the local site conﬁguration in the Meridian Mail network database as follows: Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Running Meridian Mail and CallPilot at the same time 97 Nortel CallPilot NN44200-502 01.02 Standard 5.0 17 April 2007...
Page 98: Meridian Mail To Callpilot Migration Utility Guide
CDP steering codes with a one-digit overlap for 1, 2 and 3. The bold digits represent the 1-digit overlap with the mailbox numbers. Migrate users from Meridian Mail to CallPilot on the basis of the user extensions. Example:Collect and migrate users with extensions 1000–1999.
Page 99: Meridian Mail To Callpilot Migration Utility Guide
Modify the dialing plan for the Meridian Mail remote site in the b. Add the CallPilot system as a new remote site to the network Repeat steps to CallPilot.
Page 100: Meridian Mail To Callpilot Migration Utility Guide
Meridian Mail and CallPilot systems. For example, if most of the mailbox owners reside on the Meridian Mail system, conﬁgure the Meridian Mail remote site to use the existing dialing plan and the CallPilot remote site to use the "none" dialing plan (as shown in the diagram "Option 2: To use the existing dialing plan on one system and create a...
Page 101: Meridian Mail To Callpilot Migration Utility Guide
Conﬁgure the local site using the current dialing plan in the CallPilot network database. Conﬁgure the Meridian Mail system as a remote site using a "none" dialing plan (that is, do not conﬁgure the ESN preﬁx or the CDP code).
Page 102: Meridian Mail To Callpilot Migration Utility Guide
Users Call Answering and message waiting indicator Users can have mailboxes on CallPilot, Meridian Mail, or both. However, only one system can accept Call Answering messages for each user. Conﬁgure the user’s telephone set to forward messages in busy or no answer situations to the system designated as the Call Answering system (for example, CallPilot) for that user.
Page 103: Meridian Mail To Callpilot Migration Utility Guide
Calls routed between the Meridian Mail and CallPilot systems appear to both systems as local extension numbers. When a message is composed and sent between the Meridian Mail and CallPilot systems, a user hears a message envelope prompt indicating that the message was received from a telephone number instead of a mailbox number.
Page 104: Nortel Callpilot
CallPilot and Meridian Mail systems must use the appropriate preﬁxes. For example, Meridian Mail users must dial 81 1234 to address a message to mailbox 1234 on CallPilot. Messages cannot be addressed between the Meridian Mail and CallPilot systems using only extension numbers.
Page 105: Meridian Mail To Callpilot Migration Utility Guide
The Contact Center supports only one link for each system. If you integrate CallPilot with the Contact Center, you must move any channels that are dedicated to the link from Meridian Mail to CallPilot. You cannot run simultaneously Contact Center with Meridian Mail and Contact Center with CallPilot;...
Page 106: Meridian Mail To Callpilot Migration Utility Guide
106 Chapter 6 Performing post-migration tasks Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Copyright © 2007, Nortel Networks...
Page 107: Meridian Mail To Callpilot Migration Utility Guide
Differences between Meridian Mail and CallPilot occur. For example, CallPilot requires three or more digits for mailbox numbers. • The data on the Meridian Mail system is inconsistent or corrupted. • The data collected on the tape is corrupted. •...
Page 108: Nortel Callpilot
Support representative. To revert to the Meridian Mail system It can be necessary to revert to the Meridian Mail system if you cannot resolve a migration failure. Before you retry the migration, you must execute the following on the CallPilot system:...
Page 109: Meridian Mail To Callpilot Migration Utility Guide
Nortel Technical Support group for assistance. To perform a ﬁrst-level manual recovery procedure Step Action Open the ServerDataRepairLog.txt log ﬁle in the \nortel\temp\ folder. Search for inconsistent applications, which are identiﬁed in the ServerDataRepairLog ﬁle as follows: ***Found Inconsistent Application!*** Application ID = <nnnn>...
Page 110: Meridian Mail To Callpilot Migration Utility Guide
Note: If the precheck application ﬁnds inconsistencies in the same ﬁles, perform a second level manual recovery procedure. —End— "To Perform a third-level manual recovery procedure" or refer the trouble to Nortel Technical Support for corrective Nortel CallPilot NN44200-502 01.02 Standard 5.0 17 April 2007 67).
Page 111: Meridian Mail To Callpilot Migration Utility Guide
Application <nnnn> is either imported or exported. Are you sure you want to delete it without investigating further? YES/NO Unknown exception - Manual intervention required Note: Refer the trouble to Nortel Technical Support for corrective action. Perform a second level recovery procedure as follows: Step Action Open the ServerDataRepairLog.txt log ﬁle in the \nortel\temp\...
Page 112: Meridian Mail To Callpilot Migration Utility Guide
Return to the Application Builder Data Integrity Check and Deletion Tool, and delete the inconsistent application as indicated in perform a second-level manual recovery procedure" (page Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks "To migrate Meridian Mail data to CallPilot"...
Page 113: Meridian Mail To Callpilot Migration Utility Guide
Results: The nmvutl utility repopulates the applications. Repeat the procedure (page segments and voice prompts to CallPilot" (page Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Correcting precheck inconsistencies 113 "To migrate Meridian Mail data to CallPilot"...
Page 114: Meridian Mail To Callpilot Migration Utility Guide
The debug tool creates the MigrationTrace.txt ﬁle found in the D:\nortel\MPCX\Migration folder. The MigrationTrace.txt can be so large that you cannot open it. Use the debug tool only as needed; do not use it when performing a migration for the ﬁrst time.
Page 115: Meridian Mail To Callpilot Migration Utility Guide
CallPilot. When the migration is completed, open the log ﬁle generated by the LDAP trace tool. You can ﬁnd the log in the D:\nortel\logs folder. This is an example of ldap trace ﬁle name: migrate_142_20040115.txt, where 142 is the process ID that you enter at the prompt and 20040115 is the ﬁle creation...
Page 116: Meridian Mail To Callpilot Migration Utility Guide
= 36 cMMer037 = 37 CallPilot migration error messages Error code GENERAL error messages 000–099 Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Message Message not migrated. RC gives message type as defined in mt_types...
Page 117: Meridian Mail To Callpilot Migration Utility Guide
Error code MAPFILE error messages 100–199 (MAPFILE errors refer to problems related to the mapping of the Meridian Mail data to CallPilot data. When you receive a MAPFILE error, call your support organization.) Meridian Mail to CallPilot Migration Utility Guide Copyright ©...
Page 118: Nn44200-502 01.02 Standard
(MMINPUT errors refer to problems related to accessing the tape drive or files.) Debug messages: 200–209 Debug messages: 200–209 (continued) Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Message The Data Type must not be left blank MM Data Type must be specified...
Page 119: Meridian Mail To Callpilot Migration Utility Guide
230–239 SYSMOD error messages 300–399 (SYSMOD errors refer to problems related to either the migrating system or customer profiles.) Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks CallPilot migration error messages 119 Message 210 — TapeOpen Function 211 —...
Page 120: Meridian Mail To Callpilot Migration Utility Guide
USERMOD error messages 400–499 (USERMOD errors refer to problems related to migrating user profiles, greetings, and mailbox classes.) Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Message The MM RPLID value obtained from staging file is zero; using default value.
Page 121: Meridian Mail To Callpilot Migration Utility Guide
Error code Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks CallPilot migration error messages 121 Message Invalid FID; Can not migrate the greetings data Invalid recID provided for the greetings FID, skipping greetings migration MMFS file open error; skipping the Greetings data migration for...
Page 122: Meridian Mail To Callpilot Migration Utility Guide
(MSGMOD errors refer to problems related to migrating user messages.) NETMOD error messages 600–699 (NETMOD errors refer to problems related to migrating network data.) Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Message The user Type field value could not be obtained...
Page 123: Meridian Mail To Callpilot Migration Utility Guide
Error code Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks CallPilot migration error messages 123 Message The location Overlap code array could not be obtained from MM data files Invalid code type obtained from MM data...
Page 124: Meridian Mail To Callpilot Migration Utility Guide
APPBMOD error messages 700–799 (APPBMOD errors refer to problems related to migrating Application Builder data, such as voice menus, announcements, and fax data.) Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Message Invalid value obtained for the MM dialing CLID field...
Page 125: Nortel Callpilot
The most important difference is that CallPilot uses the Controlled Directory Number (CDN) queue, which is similar to the Automatic Call Distribution (ACD) queue in Meridian Mail. Calls in the CDN queue are managed by the CallPilot system, while calls in the ACD queue are managed by the Meridian 1 switch.
Page 126: Meridian Mail To Callpilot Migration Utility Guide
126 Appendix A Meridian Mail and CallPilot comparison Setup and call routing comparison The following table compares the setup and call routing elements for CallPilot and Meridian Mail. Comparison issue Customer Application Module Link (AML) connection Call routing from switch...
Page 127: Meridian Mail To Callpilot Migration Utility Guide
Comparison issue CallPilot system setup Introduction The CallPilot setup is different from the Meridian Mail setup. A CallPilot system has three layers: • server hardware/software layer • Windows Server 2003 layer • CallPilot application layer All three layers are required for CallPilot to take calls. You must set up and conﬁgure each layer individually.
Page 128: Meridian Mail To Callpilot Migration Utility Guide
128 Appendix A Meridian Mail and CallPilot comparison Sample network setup: tower or rackmount server with Meridian The following diagram shows a network setup with a tower server and a Meridian 1 switch. The same network setup applies when the CallPilot server is a rackmount server.
Page 129: Meridian Mail To Callpilot Migration Utility Guide
Sample network setup: 201i server with Communications Server 1000 The following diagram shows a network setup with a 201i server and a Communications Server 1000 system. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Nortel CallPilot NN44200-502 01.02 Standard 5.0 17 April 2007...
Page 130: Meridian Mail To Callpilot Migration Utility Guide
Comparing switch and server conﬁguration Overview This section deﬁnes key concepts for CallPilot conﬁguration, and then highlights switch and server conﬁgurations in CallPilot and Meridian Mail. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Nortel CallPilot NN44200-502 01.02 Standard...
Page 131: Meridian Mail To Callpilot Migration Utility Guide
The directory number (DN) associated with one of these virtual telephone sets is called a phantom DN. Services that must use phantom DNs Nortel recommends that you use a phantom DN for each service that callers dial directly, such as the following: •...
Page 132: Meridian Mail To Callpilot Migration Utility Guide
132 Appendix A Meridian Mail and CallPilot comparison • Express Voice Messaging • Express Fax Messaging Creating a phantom DN To create a phantom DN, ﬁrst create a phantom loop, then deﬁne a terminal number (TN) within that loop. Each phantom TN is assigned a DN (the phantom DN).
Page 133: Meridian Mail To Callpilot Migration Utility Guide
MPB16-4 board (NTRH20BA) on the tower and rackmount servers. Additional MPUs reside on the MPC-8 cards, which are optionally installed. Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Comparing switch and server conﬁguration 133 Nortel CallPilot NN44200-502 01.02 Standard...
Page 134: Meridian Mail To Callpilot Migration Utility Guide
134 Appendix A Meridian Mail and CallPilot comparison Multimedia channels A multimedia channel comprises a DS0 channel plus one or more MPUs. The DS0 channel provides the connection between the switch and the server, and the MPUs provide the processing power.
Page 135: Meridian Mail To Callpilot Migration Utility Guide
Create a dummy ACD DN for each Meridian Mail service that callers must dial directly. In Meridian Mail Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Comparing switch and server conﬁguration 135 CallPilot CallPilot reference On Meridian 1 •...
Page 136: Meridian Mail To Callpilot Migration Utility Guide
CallPilot. Call routing overview In Meridian Mail, the switch handles call routing. The switch accepts the incoming call and places it in an ACD queue to await the ﬁrst available ACD virtual agent (the ﬁrst free Meridian Mail port).
Page 137: Meridian Mail To Callpilot Migration Utility Guide
Voice Messaging (6030) • Multimedia Messaging (6050) Two phantom DNs are conﬁgured: • 6090 is the DN for a menu service (without fax items) Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks CallPilot page "CallPilot setup" (page 137) Page "What...
Page 138: Meridian Mail To Callpilot Migration Utility Guide
138 Appendix A Meridian Mail and CallPilot comparison • 6095 is the DN for Fax Call Answering What happens when a caller dials a CallPilot service Refer to the CallPilot setup diagram on page 1. A caller dials 6090 to access a menu service. This phantom DN forwards the call to CDN 6030, because the menu contains no fax or speech recognition capability.
Page 139: Meridian Mail To Callpilot Migration Utility Guide
Sample call ﬂow in Meridian Mail Meridian Mail setup In this example, one ACD queue (3000) is conﬁgured: Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Nortel CallPilot NN44200-502 01.02 Standard 5.0 17 April 2007 Comparing call routing 139...
Page 140: Meridian Mail To Callpilot Migration Utility Guide
3. The call is directed to the ﬁrst available ACD agent and is connected to a Meridian Mail channel (port). 4. Meridian Mail looks up the DN that was dialed (3100) in the VSDN Table to determine which service is associated with it. Meridian Mail then starts Express Voice Messaging, answers the call, and plays the appropriate prompts.
Page 141: Meridian Mail To Callpilot Migration Utility Guide
Introduction The CallPilot migration utility supports the migration of Contact Center prompts from Meridian Mail to CallPilot. After migration, you can integrate CallPilot into the Contact Center environment. This section identiﬁes the differences between Meridian Mail and CallPilot voice services in a Contact Center environment.
Page 142: Meridian Mail To Callpilot Migration Utility Guide
142 Appendix A Meridian Mail and CallPilot comparison Feature Managing voice prompts Voice segment update Voice segment deletion Voice prompt migration Front-end IVR robustness Maximum capacity Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Meridian Mail...
Page 143: Meridian Mail To Callpilot Migration Utility Guide
Comparing Meridian Mail and CallPilot terminology Overview The following table compares the Meridian Mail and CallPilot feature names. Meridian Mail feature name Interface Meridian Mail Voice Messaging Fax Messaging Fax Call Answering Meridian Mail User Interface (MMUIF) not applicable Service name...
Page 144: Meridian Mail To Callpilot Migration Utility Guide
144 Appendix A Meridian Mail and CallPilot comparison Meridian Mail feature name Meridian Mail Remote Notification Delivery to Non User (DNU) Fax Call Back Desktop messaging clients Nortel Messenger Client Not applicable Not applicable Not applicable Not applicable Mailbox management...
Page 145: Meridian Mail To Callpilot Migration Utility Guide
Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Comparing Meridian Mail and CallPilot terminology 145 CallPilot feature name • Fax Select •...
Page 146: Meridian Mail To Callpilot Migration Utility Guide
146 Appendix A Meridian Mail and CallPilot comparison Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Copyright © 2007, Nortel Networks...
Page 147: Meridian Mail To Callpilot Migration Utility Guide
Result:The following information appears: Commands available: *CLI ListMap Summary For more help type "HELP <command>" or "HELP all". Note: The following commands are reserved for Nortel use only: • ListMap • Debug This command generates more output to the console window. It also generates a migrationtrace.txt ﬁle, which contains the input data.
Page 148: Meridian Mail To Callpilot Migration Utility Guide
Type delete, and then press Enter. Result:The following prompt appears: Are you sure you want to delete the staging files at this time? Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks (y/n): Nortel CallPilot NN44200-502 01.02 Standard...
Page 149: Meridian Mail To Callpilot Migration Utility Guide
Total Number of Locations Code updates in Error: Total Server Connection Lists attempted: Total Server Connection Lists created/updated Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Using the CallPilot migration utility 149 —End— <Update not required>...
Page 150: Meridian Mail To Callpilot Migration Utility Guide
Total Number of Directory Entry Users created/updated successfully: Total Number of Directory Entry Users in Error: ----------------------------------------------------- System Distribution Lists: -------------------------- Total Number of SDLs attempted: Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks <0> <Update not <0> <0> <0>...
Page 151: Meridian Mail To Callpilot Migration Utility Guide
Other Errors encountered during the migration: ****************| End of Summary |***************** Please check the log file (MigTransaction.log) for details. CI> Meridian Mail to CallPilot Migration Utility Guide Copyright © 2007, Nortel Networks Using the CallPilot migration utility 151 <0> <0> Total Number of PDLs in Error: <0>...
Page 152: Meridian Mail To Callpilot Migration Utility Guide
CDP dialing plan, verifying after migration 90, 92 channel allocation table 21 channels checklists Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Meridian Mail and CallPilot comparison 126, 126, 127, 136 conﬁguration, verifying after...
Page 153: Meridian Mail To Callpilot Migration Utility Guide
43 migrating from Meridian Mail Voice Services 77 fax segments 22 features, Meridian Mail and CallPilot comparison 143 format Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Index 153...
Page 154: Meridian Mail To Callpilot Migration Utility Guide
Meridian Mail Voice Services 77 migrated menus format 77 from Meridian Mail Voice Services 76 migration CallPilot migration checklist 59 checklist 13 conversion issues 76 Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007...
Page 155: Meridian Mail To Callpilot Migration Utility Guide
92 VPIM network shortcuts 92 network delivery proﬁles, collecting for migration 43 network dialing defaults 21 network locations 88 Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Index 155...
Page 156: Meridian Mail To Callpilot Migration Utility Guide
ID, verifying 91 site protocols, verifying 91 SL-100 130 small system migration 26 SMDI link information 21 soft keys 38 staging ﬁles, copying to CallPilot 57 Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007...
Page 157: Meridian Mail To Callpilot Migration Utility Guide
141 IVR robustness 142 maximum capacity 142 prompt management 142 prompt migration 142 segment deletion 142 segment length 141 segment update 142 Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007 Index 157...
Page 158: Meridian Mail To Callpilot Migration Utility Guide
VPIM Networking Names across the Network 103 shortcuts, verifying 92 Copyright © 2007, Nortel Networks VSDN Table 21 wild cards, using for data collection 45 Nortel CallPilot Meridian Mail to CallPilot Migration Utility Guide NN44200-502 01.02 Standard 5.0 17 April 2007...
Page 160: Meridian Mail To Callpilot Migration Utility Guide
Users must take full responsibility for their applications of any products speciﬁed in this document. The information in this document is proprietary to Nortel Networks. *Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. *Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

This manual is also suitable for:

Callpilot

Nortel Meridian Mail Utility Manual

Chapter 1 How to Get Help

Chapter 2 Understanding the Migration Process

Chapter 3 Planning a Meridian Mail Data Collection

Chapter 4 Collecting Meridian Mail Data

Chapter 5 Migrating Meridian Mail Data to Callpilot

Chapter 6 Performing Post-Migration Tasks

Chapter 7 Troubleshooting

Appendix A Meridian Mail and Callpilot Comparison

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for Nortel Meridian Mail

Summary of Contents for Nortel Meridian Mail

This manual is also suitable for:

Table of Contents