HTTP Server to phone firmware file updates

[Stewaro1]

I have a HTTP server set up in companies QA development lab.
Server type: Virtual Windows Server 2008 R2
OS version: 6.1.7601 Service Pack 1 Build 7601
It has iis setup with files in inetpub/

http://wwwroot

directory. I changed/updated the firmware files to newest 6.6 46xxsetting and downloads for 96x1 & B189 conference phones. Phones are updating to new firmware once registered to QA network. We have a production network where I want to eventually load the new settings files. However, once I install an uploaded phone with 6.6 firmware to production network it reverts to 6.4 firmware.
Question:
I thought phones booting up with higher firmware than version in http server would remain at current level. Is there a setting string that needs to be in 46xxsetting file or xxxxHupGrade file to make the phoen stay at higher release?

The phone boots up properly with correct settings file from http server. I need phone to NOT update the firmware if it currently has a greater version than resides on http server.

 

[rejackson]

The only way to avoid that is configure the ip address in the phone and skip DHCP. The architecture uses the xxupgrade.scr file to tell the phones what version they should be running. They get pointed to that by the 46xx file. That enables you to downgrade phones when necessary. It could be done scope by scope in DHCP if the dhcp option the different scopes pointed to different servers.

 

[gwebster]

Phones will follow whatever they are told to in the 96x1Hupgrade.txt file. The only exception is if they are told to downgrade to a release which is not supported on that hardware version.

 

[jimbojimbo]

You might want to use the GROUP parameter to allow the phones to run at different software releases. See the 96xx admin guide. Nice way to introduce new firmware into your production environment without upgrading all the phones. Newer CM releases allow you to assign group numbers in the station form.

Different parameters you can key on include GROUP, MACADDR, MODEL, MODEL4, VPNACTIVE, and SIG_IN_USE.

 

[Stewaro1]

Great suggestions all. Thanks very much. jimojimbo I am now working on GROUP parameters in 96xxupgrade file. Thanks for all the suggestions.