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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrade to 4.2.xx

Status
Not open for further replies.

SJCA53

Technical User
Jan 18, 2008
37
US
We are getting ready to do the upgrade to IPO 4.2.xx, and we have some trepidation about it because of lots of prior issues. How did that upgrade go for any of you that went through it? I am particularly interested in people with multiple sites, using ASCN and VoIP internally.

Any helpful hints would be appreciated!
 
what release are you migrating from

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
What processor and firmware version are you upgrading from?

For the most part the 4.2 firmware has been very solid with all the customers we've got on it. On migrations to 4.2 it's usually very smooth, but any differences on the end-user side might depend on what version you're coming off of. There's a few "gotchas" if you're upgrading from 3.2 or below, such as re-doing park buttons, using a shortcode for Dial Direct as opposed to a button (button requires a confirmation press after dialing extension), etc.. just a few minor things that always get complaints if they aren't caught.

So get us a bit more info and I'm sure I can expand.. also make sure you check out the newest 4.2.14 release. Just came out a couple of days ago.
 
VMPro - 4.1.40
IPO Mgr 6.1(12)
Firmware - 4.1(159603 - custom build)
PMP 4.1.1707

I've checked, and none of the 8 406 controllers has the potential memory issue.
Avaya Tier 4 assures me that any custom patches we had are included in the fixes in 4.2.14, so they want us to upgrade to that version.
 
Upgrading to 4.1.40 to 4.2.14 should go real smoothly. With 9 sites linked over ASCN it'll take some time, but realistically there are no real big differences between the two releases.

The one thing to make note of is since 4.2.14 has a new firmware release for 56xx series phones (I'm assuming you're using them according to your local VoIP comment), I'd recommend running Manager as each location locally to send out the BIN files for the TFTP requests. Doing it over a VPN will take a long time. If possible I would install Manager on a local PC with remote access into it at each location and run the upgrade from there. Not only will it go quicker, but it will help prevent any possible issues with sending the BIN files to either the 406 processors or the phones themselves.

That would be my advice. Totally not necessary, however. I ran a 15-site upgrade from 3.1 to 4.2 recently, most of them over a VPN. They had 3 Voicemail servers (technically not supported) so I was upgrading about 4-6 sites per server. Took a while for all the updates to go through.. the entire process probably took a good 5-6 hours for all locations. But I guarantee if I had local machines at each location to run to the upgrades off of, it would've taken half that time.
 
We do have local monitoring workstations that we use for doing any upgrades, as well as monitoring our WAN. We are using the 54XX digital sets and not IP phones because they were really problematic when we started the system implementation back in 2007. I've done other upgrades through the local workstations and it went just fine, so I think that will work just fine.

TheTaker - we've had several PBs; as I recall,that particular one resolved some one-way audio issues we had that were impacting caller's ability to leave voicemails.
 
the upgrade will be fine. the 54XX phones will have already taken the 5.0 firmware at some point so they wont upgrade. shouldtnt take long at all. system and modules take around 5-10 minutes.

make sure you have config backups, and backups of the voicemail folders and database etc. normal sort of stuff.

avaya do make a point of incorporatinng PB's into each subsequent release so in theory you are always best off on the latest firmware. but we have a client that is still reluctant to upgrade because of similar issues. problems in the past etc etc. they are a single site on a private build but its flakey at best.

im sure im telling you stuff you already know, good luck with the upgrade. just be methodical and dont rush it.

arsene knows......

everything. apart from the importance of depth in a squad. and what a chequebook looks like......
 
Thanks all - I will definitely be doing my backups before and testing after!
[no evil]
and keeping all appropriate appendages crossed...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top