Firmware upgrade file 96x1Hupgrade 1

[Stewaro1]

Because I have different settings in settings file in profuction and using multiply 'IF $GROUP SEQ' statements, I have some difficulty with testing new firmware.

Testing http server upgrade of 96x1 phone to newest 6.6 firmware. Trying to test files in production before full blown upgrade of all firmware to all phones. I am using http server in QA environment. I have edited the 96x1Hupgrade with little of no success. I am using 'IF $GROUP SEQ 30' statments to designate which firware file and which settings file I need the phone to use. It works when I use one statement to designate one file. However, when I edit the file with more than one 'IF $GROUP SEQ XX' statement the phone follows the statements based upon its 'IP Phone Group ID' on page 3 of station form. But, it does not upgrade. The phone actually states in the display after reboot that it gets the correct file. Stops on 'acquiring file' but fails to load. Then the phone registers with the current firmware it has.

Does anyone know if 96x1Hupgrade file has a restriction size or whether it can be edited or not?
Any suggestions to individually upgrading a phone(s) in production environment without affecting all phones?

 

[gwebster]

The latest 96x1Hupgrade.txt forces an interim upgrade depending upon the release that the phone is coming from. Be careful when editing to not disrupt that logic.

 

[Stewaro1]

Good to know. All, the 96x1 phones in my environment are at 6.4. I understand from firmware 6.6 release notes that the 96x1 phones will not downgrade firmware below 6.4. I have tested editing the file and have been successful making the phone with 'IF $GROUP SEQ xx' statements go from 6.6 to 6.4. However, it is not always consistent. From your reply I will assumes its the phone. However if I start over with orginal file and just add one statement then the behaviour is consistent.

Does anyone know if there is another proven method to test the 96x1 phones in production individually without disturbing the other phones until ready?

 

[gwebster]

Try the following. Change the name of the 96x1Hupgrade.txt for your production load to 96x1HProd.txt. Load the 96x1Hupgrade.txt from the test version and call it 96x1HTest.txt.

Then create a 96x1Hupgrade.txt as follows:
IF $GROUP SEQ 30 GOTO TEST
## Production
GET 96x1HProd.txt
GOTO END
# TEST
GET 96x1HTest.xt
# END

Change your test phone to group 30 (either manually or via CM) and reboot it.

Side note that only specific models will not downgrade to 6.4.

 

[Stewaro1]

BRILLIANT! appreciate the suggestion. Worked like a charm. Currently we're using different feature group sets in settings file. Your suggestion even helped navigate that scenario for indivdual phone updates as needed. This cut pre-production testing time down significantly. Thanks a lot.

 

[gwebster]

Correct. You can do the same trick with settings files. Create a 46xxprod.txt for your production system and use that in 96x1HProd.txt instead of 46xxsettings.txt. Then create a 46xxtest.txt and use that in 96x1Htest.txt.