We currently have a customer running IPO 500 v1 with 4.2 software. We are looking to move them in to a v2 Control Unit with 9.1 software. Outside of getting the licenses moved over to the new SD Card and an Essential Edition License, what is the best practice for going from 4.2 to 9.1. I know we should be able to take a config and load it to the new V2 Unit. They currently have 2 DS30 Digital and 1 Phone 30 Analog Module. Can we just power on the v2 with the new SD card with 9.1 and old config and the Expansion modules will upgrade from 4.2 to 9.1? Or do we have to get the old v1 upgraded from 4.2 to 8.0 to 9.0 first and then move the config over to the v2 and then upgrade the expansion modules from 9.0 to 9.1?
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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Upgrade IP Office 500v1 to 500v2
- Thread starter tmcd123
- Start date
As far as the config is concerned, no, don't just copy the config over.
Export your users, groups, incoming call routes, user rights, ARS (if anything), shortcodes.
Make a new config using the wizard, delete the above info from it, import your other items. Don't import the whole thing, it just causes issues. If you have to re-create parts manually like the lines, system, extensions, it's fine, just do it. It takes a little time, but better to do it that way then end up with issues with a broken config.
-Austin
I used to be an ACE. Now I'm just an Arse.
Export your users, groups, incoming call routes, user rights, ARS (if anything), shortcodes.
Make a new config using the wizard, delete the above info from it, import your other items. Don't import the whole thing, it just causes issues. If you have to re-create parts manually like the lines, system, extensions, it's fine, just do it. It takes a little time, but better to do it that way then end up with issues with a broken config.
-Austin
I used to be an ACE. Now I'm just an Arse.
- Thread starter
- #3
As long as still supported, the expansion modules will be automatically upgraded as part of upgrading when after attaching them, the V2 chassis is restarted.
The "as long as still supported" is the big caveat. Release 9.1 dropped support for a lot of older IP400 branded expansion modules so make sure you don't have any of those.
Stuck in a never ending cycle of file copying.
The "as long as still supported" is the big caveat. Release 9.1 dropped support for a lot of older IP400 branded expansion modules so make sure you don't have any of those.
Stuck in a never ending cycle of file copying.
TouchToneTommy
Vendor
The Expansion modules need to be brought up to 8.1(73) or 9.0 before going to 9.1. Load Manger 9.1 and get the 9.0 Bins. Point the bin directory to the 9.0's, run the upgrade wizard on only the expansion modules while they are connected to the V1 just before changing out the hardware. When the expansion modules are connected to the V2 they will automatically upgrade to 9.1
- Thread starter
- #6
- Status
Similar threads
