16xxupgrade.txt broken 9.0.5

[daken]

The auto generated 16xxupgrade.txt file is fault.

It will not upgrade the 16xx phones

you will need to take a copy and change the definitions at the top of the file then upload it to the primary directory on the SD card.

[pre]
IF $MODEL4 SEQ 1616 goto BACKUPAPP1616-I
IF $MODEL4 SEQ 1608 goto BACKUPAPP1608-I
IF $MODEL4 SEQ 1603 goto BACKUPAPP1603-I
[/pre]

Should be

[pre]
IF $MODEL4 SEQ 1616 goto BACKUPAPP1616
IF $MODEL4 SEQ 1608 goto BACKUPAPP1608
IF $MODEL4 SEQ 1603 goto BACKUPAPP1603
[/pre]

 

[daken]

On second look what the *&^ are they trying to do is there now 2 different firmware versions for the phones.

 

[intrigrant]

Has been announced in a tech bulletin for the 1600 series IP Phones as the "old" 1600 series are no longer updated.

 

[daken]

I cant see anything other than a split of firmware for the 16xx and 16xx-I
I can see any mention in the tech bulletining 173

Still looks like the 16xxupgrade.txt is incorrect should it not have the lines highlighted in yellow added.

[pre]## IPOFFICE/9.0.5.0 build 972 X.X.X.X AUTOGENERATED
IF $PHONECC SEQ 700415565 goto BACKUPAPP1616
IF $PHONECC SEQ 700450190 goto BACKUPAPP1616
IF $PHONECC SEQ 700415557 goto BACKUPAPP1608
IF $PHONECC SEQ 700415540 goto BACKUPAPP1603
IF $PHONECC SEQ 700458508 goto BACKUPAPP1603
IF $MODEL4 SEQ 1616 goto BACKUPAPP1616-I
IF $MODEL4 SEQ 1608 goto BACKUPAPP1608-I
IF $MODEL4 SEQ 1603 goto BACKUPAPP1603-I
goto END
[highlight #FCE94F]#BACKUPAPP1616-I[/highlight]
IF $BOOTNAME SEQ hb1616ua1_360A.bin goto PHONEAPP1616-I
SET APPNAME hb1616ua1_360A.bin
goto GETSET
[highlight #FCE94F]#BACKUPAPP1608-I[/highlight]
IF $BOOTNAME SEQ hb1608ua1_360A.bin goto PHONEAPP1608-I
SET APPNAME hb1608ua1_360A.bin
goto GETSET
#BACKUPAPP1603-I
IF $BOOTNAME SEQ hb1603ua1_360A.bin goto PHONEAPP1603-I
SET APPNAME hb1603ua1_360A.bin
goto GETSET
# BACKUPAPP1616
IF $BOOTNAME SEQ hb1616ua1_350B.bin goto PHONEAPP1616
SET APPNAME hb1616ua1_350B.bin
goto GETSET
# BACKUPAPP1608
IF $BOOTNAME SEQ hb1608ua1_350B.bin goto PHONEAPP1608
SET APPNAME hb1608ua1_350B.bin
goto GETSET
# BACKUPAPP1603
IF $BOOTNAME SEQ hb1603ua1_350B.bin goto PHONEAPP1603
SET APPNAME hb1603ua1_350B.bin
goto GETSET
[highlight #FCE94F]# PHONEAPP1616-I[/highlight]
SET APPNAME ha1616ua1_360A.bin
SET BMAPPNAME GBM32_B_1_1_0.hex
goto GETSET
[highlight #FCE94F]# PHONEAPP1608-I[/highlight]
SET APPNAME ha1608ua1_360A.bin
goto GETSET
[highlight #FCE94F]# PHONEAPP1603-I[/highlight]
SET APPNAME ha1603ua1_360A.bin
goto GETSET
# PHONEAPP1616
SET APPNAME ha1616ua1_350B.bin
SET BMAPPNAME GBM32_B_1_1_0.hex
goto GETSET
# PHONEAPP1608
SET APPNAME ha1608ua1_350B.bin
goto GETSET
# PHONEAPP1603
SET APPNAME ha1603ua1_350B.bin
goto GETSET
# GETSET
GET 46xxsettings.txt
[/pre]

 

[daken]

Mistake in last post.
Now my 1616I is updating.


[pre]## IPOFFICE/9.0.5.0 build 972 X.X.X.X AUTOGENERATED
IF $PHONECC SEQ 700415565 goto BACKUPAPP1616
IF $PHONECC SEQ 700450190 goto BACKUPAPP1616
IF $PHONECC SEQ 700415557 goto BACKUPAPP1608
IF $PHONECC SEQ 700415540 goto BACKUPAPP1603
IF $PHONECC SEQ 700458508 goto BACKUPAPP1603
IF $MODEL4 SEQ 1616 goto BACKUPAPP1616-I
IF $MODEL4 SEQ 1608 goto BACKUPAPP1608-I
IF $MODEL4 SEQ 1603 goto BACKUPAPP1603-I
goto END
[highlight #FCE94F]# BACKUPAPP1616-I[/highlight]
IF $BOOTNAME SEQ hb1616ua1_360A.bin goto PHONEAPP1616-I
SET APPNAME hb1616ua1_360A.bin
goto GETSET
[highlight #FCE94F]# BACKUPAPP1608-I[/highlight]
IF $BOOTNAME SEQ hb1608ua1_360A.bin goto PHONEAPP1608-I
SET APPNAME hb1608ua1_360A.bin
goto GETSET
[highlight #FCE94F]# BACKUPAPP1603-I[/highlight]
IF $BOOTNAME SEQ hb1603ua1_360A.bin goto PHONEAPP1603-I
SET APPNAME hb1603ua1_360A.bin
goto GETSET
# BACKUPAPP1616
IF $BOOTNAME SEQ hb1616ua1_350B.bin goto PHONEAPP1616
SET APPNAME hb1616ua1_350B.bin
goto GETSET
# BACKUPAPP1608
IF $BOOTNAME SEQ hb1608ua1_350B.bin goto PHONEAPP1608
SET APPNAME hb1608ua1_350B.bin
goto GETSET
# BACKUPAPP1603
IF $BOOTNAME SEQ hb1603ua1_350B.bin goto PHONEAPP1603
SET APPNAME hb1603ua1_350B.bin
goto GETSET
[highlight #FCE94F]# PHONEAPP1616-I[/highlight]
SET APPNAME ha1616ua1_360A.bin
SET BMAPPNAME GBM32_B_1_1_0.hex
goto GETSET
[highlight #FCE94F]# PHONEAPP1608-I[/highlight]
SET APPNAME ha1608ua1_360A.bin
goto GETSET
[highlight #FCE94F]# PHONEAPP1603-I[/highlight]
SET APPNAME ha1603ua1_360A.bin
goto GETSET
# PHONEAPP1616
SET APPNAME ha1616ua1_350B.bin
SET BMAPPNAME GBM32_B_1_1_0.hex
goto GETSET
# PHONEAPP1608
SET APPNAME ha1608ua1_350B.bin
goto GETSET
# PHONEAPP1603
SET APPNAME ha1603ua1_350B.bin
goto GETSET
# GETSET
GET 46xxsettings.txt
[/pre]

 

[Bas1234]

Have a look here;

https://support.avaya.com/css/P8/documents/101004150

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[daken]

Thanks
Bas1234


Its always nice when Avaya hide new info would have been nice if they included it in the tech bulletin.

I have just completed the install.
The 1608-I phones out of the box came with 350B.
they failed to upgrade as the auto generated 16xxupgrade.txt file on the IP500v2 running 9.0.5 is missing the 6 lines highlighted in the above post.

Without these any 16XX-I phones will not upgrade.
Any 16XX would have upgraded to 350B which looks like the last release for these phones.

With the 6 lines highlighted above added the 16xx-I phones successfully updated to 360A


I cannot believe that Avaya has not tested plugging in a new phone will the firmware update?

No 16XX-I phones running any version of software will not update on a auto generated 16xxupgrade.txt file on this firmware release 9.0.5
I would guess the same problem will exist on 8.1.95

 

[derfloh]

I would never use autogenerated upgrade files. I didn't check if there is a file on SD card once but told the customer IPO upgrade will result in a loss of functionality for about 10 min. The upgrad delivered a new upgrade file and all phones (9611) had to upgrade. But... IPO file server didn't deliver firmware files during file upload from manager... So all phones were waiting for manager to finish file transfer until they got their new firmware files.

It took about 90min until the first users could use their phones again instead of 10min...