16xx phones not upgrading to 1.3 FW

[avayastrongman79]

All...

I recently upgraded a customer to 5.0.24, back in early April to be exact. Upgraded from 4.2.14, but the 16xx IP sets did not upgrade to the new fw.

When we reboot or re-address a 16xx set in an attempt for it to pull the upgrade files, it comes back stating a bad file server address. Weve checked manager working directory, and network to a degree, but does anyone have any ideas as to why 1608/1616 will not upgrade?

Thanks in advance.

 

[tlpeter]

What DHCP server do you use? The IPO or a different one?
When it is the IPO then is the httpserver IP address set as the IP address of lan1?
When a Windows DHCP server is used then is there an option 242?
It needs to have:

MCIPADDR=xxx.xxx.xxx.xxx, MCPORT=1719, HTTPSRVR=xxx.xxx.xxx.xxx

Put the IP addresses in place of the xxx.xxx.xxx.xxx

BAZINGA!

I'm not insane, my mother had me tested!

 

[hairlessupportmonkey]

your post implies you are using TFTP

1600 / 9600 phones require an HTTP server

just use the IPO as the HTTP server.

ACSS - SME

 

[avayastrongman79]

Thanks for the replies, sorry for leaving some info out in initial post. DHCP is windows based and used on customer's LAN, not on IPO. NO known option 242 in DHCP scope.

I have the http ip address pointed to LAN1 or IPOffice. We've tried rebooting the ip sets a couple times, it still says no file serv address.

 

[amriddle01]

Did you know you can run the IPO dhcp server alongside the windows one? You can set it to only issue to Avaya phones and the phones look for this first before looking for an alternative server, so as long as you exclude the addresses the IPO Is issuing from the server and vice versa all will be good

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

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