Direct 2.1(27) to 3.1(x) 1

[onsetcomp]

Can an IPO 412 be upgraded directly from version 2.1(27) to the latest 3.1(x) version or do I have to install 3.0(x) first? The tech support docs refer me back to the 3.0 upgrade procedure but do not state that I need to install 3.0 first.

Thanks

 

[derry163]

I was wondering the same thing myself...Or for that matter 1.4 to 3.1....

 

[Leemondcomm]

May I point you to this.

Is a do and dont guide to upgrading sw.

http://support.avaya.com/elmodocs2/ip_office/tech/Global_IP_Office_Technical_Bulletin_Number_54.pdf

 

[mattKnight]

Don't forget though that tech bulletin 54 realtes to version 3.0.xx
This link suggest that only the IP406v2 (and early 406v1) need the 2 stage upgrade

The 2 stage upgrade process between 2.1.xx and 3.0.xx only applies to IP403 units.

If you are using an IP412, you should therefore be able to go straight from 2.1.27 to 3.1.29

That being said, ensure you are happy with defaulting units using the DTE port!


Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[onsetcomp]

Can you please elaborate on this comment: That being said, ensure you are happy with defaulting units using the DTE port!

Does that mean?

We have the IPO 412 with almost all 4406D and 4412D phones.

 

[Telecomboy]

If anything fails to upgrade properly, or if the proper upgrade steps are not followed, the IP Office can lock-up and can only be restored via the DTE port on the back of the unit.

 

[mattKnight]

Onsetcomp - the firmware can be deleted & the unit returned to a default state using the serial port on the rear of the unit

There is an excellent FAQ on this ( faq940-5354) which you should read! It also gives some useful tips on preventing upgrade failures

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[intrigrant]

You MUST always go through all the last maintenance releases of a major build in order to preserve a valid database.
So if you want to go from 1.4 to 3.1 then in all cases and with all kind of units you must :
upgrade from 1.1 -> 1.2
upgrade from 1.2 -> 1.3
upgrade from 1.3 -> 1.4
upgrade from 1.4 -> 2.0
upgrade from 2.0 -> 2.1
upgrade from 2.1 -> 3.0
upgrade from 3.0 -> 3.1

If the database is of no concern then the above do not apply but the following is always important.
You must always use intermediate builds for the 403, 406V1 and 406V2 in some cases. Read the upgrade manuals provided with the software.

 

[derry163]

Thanks Intrigrant !! That's exactly the info I was looking for that the tech bulletins don't offer. Does the same hold true for voicemail upgrades ?

 

[intrigrant]

Not that i am aware of, i have always copied the .mdb file and the custom .wav files to a secure place, uninstalled the VM Pro completely, reinstalled the new version, set the vmpro server service to log on with a system account, copied all files back and reboot the PC.
Done! Has always worked and still does.

 

[onsetcomp]

Okay I did the upgrade from 2.1 to 3.0 then 3.1 with no problems.

I have noticed that now when the system is put into Night Service mode there is no "O" displayed on the phone displays. The night service lights are on and the system behaves like it should in night service.

Is that normal in 3.1?

I missed the VMPro 3.1 upgrade step that had me export the registry info prior to the upgrade. The VM seems to be working but what would be messed up by not performing the registry export/import?

 

[mbjst]

I don't mean to beat a dead horse, but I want to be sure.

I have a IP412 ver 2.0.16 that I need to upgrade. I have downloaded 3.1.29, but in the bin directory there are no previous versions for the 412. Do I need to download past versions to get the proper .bin files? Is doing the "step upgrade" necessary for the 412? Or is it not necessary, but RECOMMENDED. If so what are the final versions for 2.0 and 2.1.

Also what about VM Pro? Do the step thing or go whole hog.

Thanks
Mark

 

[IPGuru]

It Is recomended to go through the interim steps when upgradind however the IPO is fairly rubust with its CFG format & usualy inserts sensible defaults for new parameters when upgrading firmware.

you would borbably be O.K going straight from V2.0 to V3.1 but make sure you have a backup copy of your CFG just incase

also expect to have to make chages to the CFG that relate to V3.0 Specifics

 

[mbjst]

Thanks. I've found that one retains their sanity longer when you back up EVERYTHIBG before an upgrade.

Thanks again.

MBJ

 

[jdovejr]

i took a new 406V2 from 2.1.27 to 3.0.99 to 3.1.29 without a problem.

 

[CarGoSki]

One small rub that I have run into twice recently is when the IPO refused to accept the firmware upgrade. Instead returning an error message. The systems neither crashed nor accepted 2.99 on the way to 3.1.48.

One unit was a 406V1 at 2.0 and the other was a 403 at 2.1.15. I had to go to 2.1.24 in both cases before moving to 2.99.