Callpilot Meridian Mail to Callpilot Migration Utility Guide
Total Page:16
File Type:pdf, Size:1020Kb
555-7101-801 555-7101-801 CallPilot Meridian Mail to CallPilot Migration Utility Guide Product release 2.x Standard 2.0 May 2004 CallPilot Meridian Mail to CallPilot Migration Utility Guide Publication number: 555-7101-801 Product release: 2.x Document release: Standard 2.0 Date: May 2004 Copyright © 2004 Nortel Networks, All Rights Reserved Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. 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 specifically 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. This page and the following page are considered the title page, and contain Nortel Networks and third-party trademarks. Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks, BNR, CallPilot, DMS, DMS-100, DMS-250, DMS-MTX, DMS-SCP, DPN, Dualmode, Helmsman, IVR, MAP, Meridian, Meridian 1, Meridian Link, Meridian Mail, Norstar, SL-1, SL-100, Succession, Supernode, Symposium, Telesis, and Unity are trademarks of Nortel Networks. 3COM is a trademark of 3Com Corporation. ACCENT is a trademark of Accent Software International Ltd. ADOBE is a trademark of Adobe Systems Incorporated. AMDEK is a trademark of Amdek Corporation. AT&T is a trademark of American Telephone and Telegraph Corporation. ATLAS is a trademark of Quantum Corporation. ATRIA is a trademark of Pure Atria Corporation. CASEWARE is a trademark of Caseware International, Inc. CONTINUUS is a trademark of Continuus Software Corporation. CRYSTAL REPORTS is a trademark of Seagate Software Inc. DEFINITY is a trademark of Avaya Inc. DIALOGIC, INTEL and VOICEBRIDGE are trademarks of Intel Corporation. DIVX is a trademark of DivXNetworks, Inc. EUDORA and QUALCOMM are trademarks of Qualcomm, Inc. eTrust and InoculateIT are trademarks of Computer Associates Think Inc. DIRECTX, EXCHANGE.NET, FRONTPAGE, INTERNET EXPLORER, LINKEXCHANGE, MICROSOFT, MICROSOFT EXCHANGE SERVER, MS-DOS, NETMEETING, OUTLOOK, POWERPOINT, VISUAL STUDIO, WINDOWS, WINDOWS MEDIA, and WINDOWS NT are trademarks of Microsoft Corporation. GROUPWISE and NOVELL are trademarks of Novell Inc. HITACHI is a trademark of Hitachi Limited. LOGITECH is a trademark of Logitech, Inc. LUCENT is a trademark of Lucent Technologies, Inc. MATRA is a trademark of Matra Hachette. MCAFFEE and NETSHIELD are trademarks of McAfee Associates, Inc. MYLEX is a trademark of Mylex Corporation. NET2PHONE is a trademark of Net2Phone, Inc. NETOPIA is a trademark of Netopia, Inc. NETSCAPE COMMUNICATOR is a trademark of Netscape Communications Corporation. NOTES is a trademark of Lotus Development Corporation. NORTON ANTIVIRUS and PCANYWHERE are trademarks of Symantec Corporation. POWERQUEST is a trademark of PowerQuest Corporation. PROMARK and RHOBOT are trademarks of DMI Promark, Inc. QUICKTIME is a trademark of Apple Computer, In. 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. TEAC is a trademark of TEAC Corporation. UNIX is a trademark of X/Open Company Limited. U.S. ROBOTICS, the U.S. ROBOTICS logo, and SPORTSTER are trademarks of U.S. Robotics. WINAMP is a trademark of Nullsoft, Inc. WINRUNNER is a trademark of Mercury Interactive Corporation. WINZIP is a trademark of Nico Mark Computing, Inc. Meridian Mail to CallPilot Migration Utility Guide v Publication history Standard 2.0 Publication history May 2004 Standard 2.0 of the Meridian Mail to CallPilot Migration Utility Guide for CallPilot 2.x is released for general availability. vi CallPilot Contents 1 Understanding the migration process 9 Overview. 10 Migration task flow. 13 Migration limitations . 16 Reference documents . 18 2 Planning a Meridian Mail data collection 23 Meridian Mail releases and platforms that can be migrated. 24 Data that can or cannot be migrated . 25 Meridian Mail system size . 28 Types of data collection . 30 Time estimates . 32 Collecting data in a single session . 33 Collecting data in multiple sessions . 35 Meridian Mail data collection check list. 41 3 Collecting Meridian Mail data 45 Installing the data collection utility . 46 Soft keys . 50 Launching the data collection utility . 51 Collecting Meridian Mail data . 54 Collecting Symposium Call Center Server data . 61 Reviewing the Meridian Mail migration log . 68 4 Migrating Meridian Mail data to CallPilot 71 Hardware, software, and media requirements . 72 Staging area. 74 Stopping the migration . 76 CallPilot migration check list . 77 Migration sequence. 79 Migrating a system with many voice segments or fax items . 81 Meridian Mail to CallPilot Migration Utility Guide vii Contents Standard 2.0 Migrating Meridian Mail data. 82 Migrating Symposium Call Center Server data . 87 Reviewing the migration log and summary . 93 Rerunning the migration . 102 Using Application Builder to complete the migration of voice services . 104 5 Performing postmigration tasks 115 Disconnecting the tape drive. 116 Verifying CallPilot system configuration. 117 Verifying CallPilot network database. 121 Replacing Meridian Mail with CallPilot. 127 Running Meridian Mail and CallPilot at the same time . 129 6 Troubleshooting 143 Migration problems. 144 Correcting pre-check inconsistencies . 146 Troubleshooting tools . 153 Meridian Mail data collection error messages . 155 CallPilot migration error messages. 158 A Meridian Mail and CallPilot comparison 175 Overview. 176 CallPilot system setup. 179 Comparing switch and server configuration. 186 Comparing call routing . 194 Comparing networking solutions . 200 Comparing Symposium Call Center Server voice services . 201 Comparing Meridian Mail and CallPilot terminology . 204 Index 209 viii CallPilot Chapter 1 Understanding the migration process In this chapter Overview 10 Migration task flow 13 Migration limitations 16 Reference documents 18 Meridian Mail to CallPilot Migration Utility Guide 9 Understanding the migration process Standard 2.0 Overview 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. For a comparison of Meridian Mail and CallPilot, refer to Appendix A. Introduction to the migration process A migration from Meridian Mail to CallPilot consists of two major steps: ! collection of Meridian Mail data on tape ! transfer of the collected data from tape to CallPilot The number of tapes necessary for a migration depends on the size of the Meridian Mail system. During a migration from Meridian Mail to CallPilot, both systems must be out of service for a variable period of time. The length of this period depends on the system size, data volume and number of users that must be migrated. The Meridian Mail system still accepts calls and messages after the data collection. 10 CallPilot May 2004 Understanding the migration process Meridian Mail data Two types of Meridian Mail data can be migrated to CallPilot: ! system data ! user data (including voice greetings) ! system profiles ! networking data ! voice services—voice menus, voice services, and announcements ! message data—voice messages (the Symposium Call Center Server prompts are also considered to be message data) The CallPilot migration utility allows you to migrate all the Meridian Mail information to CallPilot or to perform a selective migration. In a selective migration, you can migrate each of the following data sets individually: ! messages ! messages and Symposium Call Center Server prompts ! Symposium Call Center Server prompts only ! system data ! system and customer profiles ! networking data ! restriction/permission lists (RPL) ! classes of service (COS) ! users ! voice services (Application Builder applications on CallPilot) ! voice menus ! voice services ! announcements ! system distribution lists (SDL) ! personal distribution lists (PDL) Meridian Mail to CallPilot Migration Utility Guide 11 Understanding the migration process Standard 2.0 Migration rules Follow these general migration rules to minimize system down time: ! Perform the data collection during one or more off-hour periods. ! Do the following after collecting Meridian Mail data on tape: ! freeze Meridian Mail configuration changes ! freeze changes to users, RPLs, COSs, networking data, voice menus, voice announcements, and any data that has to be migrated ! warn users to stop making changes to mailboxes Note: Changes made after collecting the Meridian Mail data are not migrated to CallPilot. ! Verify that the data has been migrated to CallPilot. ! Perform the switchover to CallPilot so that CallPilot accepts calls and new messages, and inform users that they must check the CallPilot mailboxes for messages. Before switching the service to CallPilot, take into consideration the following issues: ! After the switchover, Meridian Mail no longer answers calls and takes new messages.