Callpilot Migration Check List - Nortel Meridian Mail Utility Manual

CallPilot migration check list

Complete the following check list before you start the data migration to
CallPilot.
Item
Ensure that the CallPilot system is installed.
Ensure that the switch is configured for CallPilot operation.
Ensure that the CallPilot system is configured and operational.
All installed CallPilot services must be running properly. Dial the
Voice Messaging Service DN to ensure that calls can be placed
and received.
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
ID> and then migrated to CallPilot. As a result, migrated users can
be assigned to the wrong mailbox class.
Ensure that Application Builder is installed and operational on
CallPilot if you want to migrate voice segments (voice menus, voice
services, and announcements), Contact Center prompts, or both.
Ensure that the 201i CallPilot server is connected to an external
tape drive or that an external tape drive is available.
Ensure that the tower or rackmount server is equipped with an
internal tape drive.
Change the names of all CallPilot sites and locations to Untitled if
you already configured the CallPilot network and want to migrate
the Meridian Mail networking data.
Disable event throttling on CallPilot if throttling is enabled.
Ensure that no client applications (including CallPilot Manager and
any other software) are running on CallPilot while the migration
is in progress.
Copyright © 2007, Nortel Networks
.
Nortel CallPilot
Meridian Mail to CallPilot Migration Utility Guide
NN44200-502 01.02 Standard
5.0 17 April 2007
CallPilot migration check list 59
Check