PBXtech.info - View Single Post

gkludt · June 6th, 2005, 09:14 AM

Hello all - A cautionary tale:

Our company has an IP Office 403 that until recently had firmware version 1.3 and voicemail lite. I have completed many of these upgrades from 1.3 to 1.99 to 2.x in the past.

I also had no problems getting to 2.1.15 firmware using a factory CD in this case. I also know that 2.1.15 is buggy, so I did not want to stay on that version long.

Here is where it get's sticky - and :D thank goodness :D I had backed up the old config to TWO locations...

I downloaded 2.1.31 admin CD from avaya's website, uninstalled the admin software and voicemail. I then installed 2.1.31 and ran the upgrade. It all went quite well until the final reboot. The system began to "christmas tree" repeatedly, essentially running through continuous reboots.

I got out my console cable (essentially a 25 to 9 pin serial cable - not sure if the pinouts are standard RS232?) and launched hyperterminal, powered down and up the system, and found an error message referring to "magic number not found". While I found no evidence of this error on the avaya site, on pbxtech, or even on google searches, I knew I would have to try to factory default it through the console port.

I may be missing a few steps here, and I do encourage you to download Avaya's pdf with the specific instructions for using the AT commands on the console.

Fortunately, Avaya's instructions using hyperterminal and the escape key on boot, and typing the commands AT [enter] and AT-X [enter] did allow me to get back into the system with the factory default IP of 192.168.42.1. I changed my static IP on the Manager computer I was using to 192.168.42.2, and the system's tftp requests were answered. I then opened the old config offline, sent it to the system, and rebooted again. I changed my IP back to our existing network setting static ip.

Long story, but the bottom line is this - I can NOT believe I'm the first person to experience this magic number error during an IP Office upgrade. Would stepping from 1.3 to 1.4 to 1.99 to 2.0 to 2.1.15 to 2.1.31 have avoided this problem?

You may be wondering why I did not go to 3.x firmware, and it is simply because I know that the later versions of 2.1.x are reasonably stable - I'd rather have the rest of the world work the bugs out before I go 3.0. But I am

I hope this post helps!

June 6th, 2005, 09:14 AM	#1 (permalink)
gkludt Join Date: Jul 2004 Posts: 23	IP403 Magic number not found Hello all - A cautionary tale: Our company has an IP Office 403 that until recently had firmware version 1.3 and voicemail lite. I have completed many of these upgrades from 1.3 to 1.99 to 2.x in the past. I also had no problems getting to 2.1.15 firmware using a factory CD in this case. I also know that 2.1.15 is buggy, so I did not want to stay on that version long. Here is where it get's sticky - and :D thank goodness :D I had backed up the old config to TWO locations... I downloaded 2.1.31 admin CD from avaya's website, uninstalled the admin software and voicemail. I then installed 2.1.31 and ran the upgrade. It all went quite well until the final reboot. The system began to "christmas tree" repeatedly, essentially running through continuous reboots. I got out my console cable (essentially a 25 to 9 pin serial cable - not sure if the pinouts are standard RS232?) and launched hyperterminal, powered down and up the system, and found an error message referring to "magic number not found". While I found no evidence of this error on the avaya site, on pbxtech, or even on google searches, I knew I would have to try to factory default it through the console port. I may be missing a few steps here, and I do encourage you to download Avaya's pdf with the specific instructions for using the AT commands on the console. Fortunately, Avaya's instructions using hyperterminal and the escape key on boot, and typing the commands AT [enter] and AT-X [enter] did allow me to get back into the system with the factory default IP of 192.168.42.1. I changed my static IP on the Manager computer I was using to 192.168.42.2, and the system's tftp requests were answered. I then opened the old config offline, sent it to the system, and rebooted again. I changed my IP back to our existing network setting static ip. Long story, but the bottom line is this - I can NOT believe I'm the first person to experience this magic number error during an IP Office upgrade. Would stepping from 1.3 to 1.4 to 1.99 to 2.0 to 2.1.15 to 2.1.31 have avoided this problem? You may be wondering why I did not go to 3.x firmware, and it is simply because I know that the later versions of 2.1.x are reasonably stable - I'd rather have the rest of the world work the bugs out before I go 3.0. But I am I hope this post helps!