Problems with Firmware Upgrade for 1603 SW-I from H.323 to SIP

[indecided]

I've got a setup of about 80 1603SW-I phones that we are trying to upgrade from H.323 to SIP.

We're having issues with the phone taking the SIP firmware.

Upon boot (and pointed to correct HTTP server with the SIP 1.0.1 firmware and 46xxsettings.txt file, we can see the phone pull the 46xxsettings.txt file followed by the 16xxupgrade.txt file. It then tries to pull the hb1603ua1_2200.bin file, successfully. But it doesn't write/save to flash and continues to boot into H323 firmware.

The 16xx-IPT-SIP-R1_0_1-080910.zip file was downloaded directly from Avaya and the 46xxsettings.txt file is fairly benign save a couple of changes for server, etc.

We've also tried to change the protocol in the CRAFT menu from DEFAULT to SIP, with the same result.

Any pointers on how to get these phones to pick up the SIP firmware would be much appreciated.

Thanks!

 

[amriddle01]

That's not an "upgrade" that's making them into expensive paperweights, no point doing this for IP Office

 

[gwebster]

I recall that the newest 1608SW-I will not load the SIP firmware and that Avaya has actually discontinued it.

 

[multimedV1]

Only 1603 can be loaded with SIP firmware. The other 1600 phones are H.323 only.

 

[indecided]

Too early in the morning. I'm sorry - it was the 1603 SW-I, not 1608 SW-I, which clearly supports SIP.

The phones are 13XX serial so about 3 years old.

 

[multimedV1]

Do you have such settings in 16xxupgrade.txt?
############################################################
## Check backup application version ##
############################################################

IF $MODEL4 SEQ 1603 goto BACKUPAPP1603
goto END

# BACKUPAPP1603
IF $BOOTNAME SEQ hb1603ua1_2200.bin goto PHONEAPP1603
SET APPNAME hb1603ua1_2200.bin
goto GETSET


############################################################
## Check phone application version ##
############################################################

# PHONEAPP1603

SET APPNAME sa1603ua1_0100.bin
goto GETSET

 

[indecided]

Yep, that's exactly what it is.

Henceforth the phone does try to pull hb1603ua1_2200.bin. But doesn't write/save to flash.

 

[multimedV1]

I suppose you have hb1603ua1_2200.bin on HTTP server. You can check your current boot application file on the phone and put in the settings above instead of hb1603ua1_2200.bin, so that phone tries to load phone application only.