Upgrade Questions On Avaya IPO 1

[FreightTrain]

I have have a customer that has a V1 500 chassis at 5.0 software. They will be upgrading to the latest release. I'm replacing the V1 chassis for the V2 chassis with a new R9 SD card that will have the Essential license. Do I need the Large upgrade License and upgrade the new chassis to R7 then to R8 then to R9 with uploading the old CFG? Or should I just reprogram the whole system? My problem is that I don't want to do the upgrade license and then something happens, and at the same time I don't want to spend all day reprogramming a 150 station system either. Any thoughts?

"When all else fails call for backup

 

[intrigrant]

Going through the different software versions also takes a lot time.
This is how I do it:
I create a offline config with the used hardware in the exsisting system.
Then from the old config I perform a binary export of the users, groups, shortcodes, incoming call routes, IP routes, user rights and ARS.

Then I import the binary data into the just created offline config and manually program those items not importer, e.g. system, lines. licenses etc.
Once done I send the offline config into the IP 500v2 and when done all is left is a checkup and renumber the extension numbers and a functional test.
For me that is the quickest & safe way to upgrade.

I used to do the upgrade as suggested by Avaya but with every upgrade I ran into vague issues like no number presentation on analog stations, failing DTMF and other strange issues which could only be solved by a full manual reprogram.
With the above method I never ran into any issue and last year I did about fifty upgrades from IP400 & IP500v1 systems.

 

[FreightTrain]

Nice. Thanks for the idea, I like your way better.

"When all else fails call for backup

 

[smokinjoe2938]

I think that deserves some pink!

 

[Pepp77]

I just take a copy of the old config, then create a new 500v2 on release 9 with default config and then import the old config. Not yet had an issue and have done a load of these this way.

| ACSS SME |