3631 Firmware Upgrade 1

[MasterRacker]

We have a pair of 3631's we are trying to upgrade the firmware on. I tried to connect to them a few months ago with a couple of different USB cables with no luck whatsoever, so that option is out for now.

We normally run the phones completely manually programmed (no http server or 46xxsettings.txt file.)

I've gotten the new firmware on a http server in a "down" directory with a copy of the 3631upgrade.txt file in the web root as outlined in the 3631 Administrator Guide. I've also programmed the file server address into one of the phones.

The problem I'm having is that the phone boots, finds the file server and tries to start downloading 46xxsettings.txt. When it can't find that file it reports "Bad File Server Address", aborts any further downloads and simply finishes booting the phone.

I have a copy of the generic 46xxsettings.txt from the Avaya site. This file is completely comments in it's generic form. My thought is to put this file in the webroot as a placeholder hoping the phone downloads it, ignores it since it's all comments then starts downloading the upgrade.

Is this worth trying?



Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[rocketlauncher]

Hi Master,

I'm not an Avaya expert. But I've dealt with this phones due to a project that required them.

First of all, make sure you can browse the download directory and the 46xxsettings file thru IE, from the subnet where the phone is located. Make sure all required ports are open.

Follow the the admin guide. It describes what ports need to be open, the startup process for the phone, the configuraion parameters and some troubleshooting tips. The link is below.

http://support.avaya.com/japple/css...tID=291674&temp.bucketID=159898&PAGE=Document

Also, if needed setup a syslog server in the phone (This is done manually through the phone interface. go into Advanced -> IP Addresses, RemoteLog Server), this gives a lot of informaiton and might give you an idea on what's going on and why it might be failing.

I was able to get our phones working, but let me tell you it wasn't easy and we had to got through a lot of research in order to get them going. Not even Avaya was able to help us out with our issue.

Hope this helps.

Regards,

Rocket

 

[MasterRacker]

You link points to the same Admin guide I have. AFAIK I have everything setup as requested except the 46xxsettings file.

From your comment, it appears that I must have a 46xxsettings file in place for the upgrade, even if we normally do not use one.

In another post I also saw mention that IIS may not be able to transfer one of the files correctly. Has anyone else seen this issue? (My Web server is IIS.)

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[mojoputter]

MasterRacker,

Do you have the IP address of the HTTP server in your DHCP string..? in the DHCP string there should be a HTTPSRVR(ip address) setting.

 

[MasterRacker]

We're not using DHCP.

I got this to work finally. It turns out you do need to have a 46xxsettings file even if you're not actually using it. The boot process needs to see one.

I also saw the issue of a file not downloading. By default IIS will not server files without an extension unless you create a custom MIME type for them.



Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[rocketlauncher]

I'm glad you got it going Master.