IP406 V2 Upgrade 1

[rm81]

Hi Everyone I'm new to the tech tips forum.

I have an IP 406 v2(DS)pcs 7 running version 3.0(59)IP400 ds module v2 2 off, the customer wishes to upgrade from 3.0(59) to 4.2(14). using a mixture of 5402,5410,5420 handsets.

The customer is using soft console v 3.1.12 along with vmpro client 3.0(19) Vmpro appears just to be used as a basic answer service no modules configured.Current licencing is 1 pmp 1 softconsole and a 4 port voicemail pro licence.

I have checked that the 406 has enough memory to upgrade to 4.0 my plan is to upgrade from 3.0(59)>3.0(99)>3.1(99)>4.0>4.2(14)(armed with a serial rs232 connector lead & AT commands just incase)

Reinstall both VMPRO and softconsole software

I'll be upgrading the the 406 from 6.2(14) manager with the relevant bin files, my questions are as i have not upgrade an Avaya on as old a version as this,

Does the above upgrade path seem correct( i just have a slight concern with the software being so old? And can anyone see any potential issues given the information above (is it safe to upgrade from 3.0(59) using 6.2(14) manager.

Many thanks in advance

 

[amriddle01]

You only need to go to the 3.1.999(this is within the Manager folder)loader and then to 4.2 on the 406

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[teletechman]

be aware that there will be some operating changes such as call park no longer having an answer button etc..
Mike

 

[amriddle01]

I base that upon this document

CODE
Platform Current Release Upgrade Step 1 Upgrade Step 2
SOE 2,1 3.2(999) Loader Load 4.2
SOE 3 3.2(999) Loader Load 4.2
SOE 3,1 3.2(999) Loader Load 4.2
SOE 3,2 3.2(999) Loader Load 4.2
SOE 4 Load 4.2
IP406v2 2.1(27) Load 2.1(35) and higher Load 4.2
IP406v2 2.1(35) and higher Load 4.2
IP406v2 3 Load 4.2
IP406v2** 3.1(62) and lower 3.1.999 Loader ** Load 4.2
IP406v2 3.1(63) and higher Load 4.2
IP406v2 3,2 Load 4.2
IP406v2 4 Load 4.2
IP412 2,1 Load 4.2
IP412 3 Load 4.2
IP412 3,1 Load 4.2
IP412 3,2 Load 4.2
IP412 4 Load 4.2
IP500*** 4.0.0*** Load 4.2
IP500 4 Load 4.2
DSv2 module* 2,1 3.2(999) Loader* Load 4.2
DSv2 module* 3 3.2(999) Loader* Load 4.2
DSv2 module* 3,1 3.2(999) Loader* Load 4.2
DSv2 module* 3,2 3.2(999) Loader* Load 4.2
DSv2 module* 4 Load 4.2
All other modules 2.1/3.0/3.1/3.2/4.0 Load 4.2

* Note: When upgrading DSv2 modules to the 3.2(999) release an additional step may be needed. If the modules are attached to an IP406v2 system the Upgrade Wizard will report an error if there is not an IP406u.bin file in the V3_2_999 directory. Please copy the IP406u.bin file from the Manager directory to the V3_2_999 directory before attempting to upgrade the DSv2 expansion modules.
** Note: The 3.1.999 loader can be found in the bin\IP406v2\V3_1_999 directory of the admin CD or in the Manager\V3_1_999
*** Note: The IP Office 500 system is shipped from the factory with software version 4.0.0 installed. This is not a fully functioning version of software and MUST be upgraded to the IP Office 4.2 software.


ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[amriddle01]

Look out for LCR now being ARS and working differently amongst other things

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[rm81]

Guys,

Thankyou for the responses really appreciate the replys.

Shouldnt be an issue with LCR changing to ARS as they dont appear to be using it.

Would i be ok just doing a clean install of vmpro as they dont use it for anything other than basic voicemail i imagine this would be easier than backing up the reg settings and doing it that way? (will be configuring modules for use going forward)

Looking at the licences i wouldn't have thought that they need any additionals to use a new version of vm pro or soft console am i correct in thinking this?

Thanks very much for the upgrade paths

Sorry if these sound like daft questions just want be certain (and avoid a late night if possible)

 

[TomMills]

No the licenses should be fine.

Clean voicemail install will be fine, depends if they want to keep their old prompts/greetings or not. but you could just copy those, do a clean install, drop them in and restart the services.

"There's a dog in the New Zealand section

 

[rm81]

Thanks guys,

You rip our distributor's response time to pieces

So fingers crossed things shouldnt be too tough.
One thing that does interest me slightly is that our distributors tech support guy said use 3.0(59)>3.0(99)>3.1(99)>4.0>4.2(14)are there any benefits in using one method or the other or does this just boil down to individual choice.

Mucho thanks again

 

[TomMills]

the avaya docs say to use 3.1999 then straight to 4.2

ive done it this way a couple of times. not had any issues.

good luck.

"There's a dog in the New Zealand section

 

[amriddle01]

Rick, that's because he just quoted the first document he found to you, experianced users know that the full path is not required as stated in the latest documentation

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[tlpeter]

The only problem you can have is that the LCR part screws your ARS when you upgrade

Not a big problem but annoying

Sometimes the ARS entry does not work well
If it happens then export everything except ARS (to a bin file)

Then default the system and import everything and you have a good system

ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[rm81]

Guys thanks very much for all of your help will let you know how it goes much appreciated amriddle thanks for taking the time to post the upgrade doc's

 

[amriddle01]

Anytime

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[Escorthosis]

Can't be bothered to read the whole thread.
But check with the monitor if system memory is > 16MB.
Have a tftpserver or manager running as the 5410/20
will have to upgrade from 2.0/4.0 to 5.0.
User 4.2.17 instead of 4.2.14 it's the latest release.