Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MerMail Migration: Rebuild Menus??

Status
Not open for further replies.

Wanker04

Technical User
Feb 25, 2006
4
US
Cheers Gang - Q: Do I have to manually rebuild auto attendant menus and services from Mermail to CallPilot 5.0.

Prepping for a Mermail 13 to CallPilot 5.0 migration and colleagues are telling me that all the menu services will need to be manually reconfigured in Callpilot. I will be using the CallPilot 4.0 Migration Utility Tape NTUB25AC.

So after 5 hours of manually copying and pasting from the terminal, I read the NTP for Mermail to Callpilot 5.0 and it describes that the only thing that does not migrate are Thrudials.

Thanks
 
You don't want to hear this, but based on a migration i just did, my biggest concern now are the techs i work with in the future, not the actual migration.

There is a migration utility that can do most of that work for you, but you have to have competent techs. if your guys are good, then no sweat.

If you have any doubts, do it manually as i did. it took me the same exact time, 5 hours, to build everything from scratch in CP, but i had to because i lost faith in the PM and my Tech. so i had to add almost 200 mailboxes, build every App and every SDN, but i knew that it was right.

a little more info than you asked for, but this one is very fresh in my mind.
 
i always rebuild the aa menus but all the rest should be Ok. you may find it builds 99% of everything ok but you know Nortel.

Remember if it doesn't work hit it harder

Scott UK
 
Here are a few tips that I do on every migration.

1. rename the RPLs so On Switch besomes MM On Switch and so forth. The rpl will migrate but the callpilot will rename the rpl because the RPL On Switch already exists. That is not the problem. the problem comes in when you migrate the mailboxes and they are still assigned the name On Switch and now they are all restricted by default...Ooops

2. I put MM infront of all of the class of service names just in case.

The only thing that migrates on the voice services side is the recordings so all applications will have to be rebuilt from scratch. The menu structure does not migrate.

I did one migration that had 48 menus and 12 announcements and had to rebuild them all.

Here is what I did.....

1. Gathered all the call flow data from the Meridian Mail
2. Created the applications in CallPilot and I named the menu and announcement blocks the same as the voice service id in meridian mail
3. migrated the data
4. exported all the recordings from the migrated applications to my laptop. I used the voice services id as a file name.
5. Imported the recordings into the proper application block
6. deleted all the migrated menus and announcements

When I was done I had 3 applications from 48 menus and 12 announcements.

When they migrate the application name will look like MS1001 in callpilot for menu service 1001 in meridian mail

I migrated the system data and built the applications before the actual migrating of the users. Just migrate all the system data.

Signature===========================================

Aastra Authorized Reseller
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top