Changing 46xxsettings file with Group ID

[Stewaro1]

I am upgrading my 96xx series phone firmware. Presently have agents using different features than back-office users. That is controlled by Group ID in 46xxsettings file. While I am doing a controlled firmware update I have introduced group ID's into 96x1Hupgrade file. I have renamed the original files as 96x1HQA & 96x1Prod to distinguish between those getting new firmware and staying same....until roll-out is complete. Here is my issue...I have been unable to make the settings file recognize the Group IDs unless I make two separate files (one for back office and 1 for agents).

Here is dilemma: I have come across new site deploy that wants certain group of agents phones to its have feature PHNSCRALL set to 1. This enables consolidated display screen that includes call appearances and features.

Barring putting another settings file and splitting the upgrade file commands again I cannot get this to work off one settings file by GROUP ID setting features as I need them to. I know the phone is following the proper files as I can see it working correctly when booting. However, the features do not change as placed in file. Any suggestions what I may be doing incorrectly. See attached and capture of files as I have them loaded on TFTP server.

 

[kyle555]

why not use the group id in the station form and let the phone grab the stock upgrade and settings file and go to the right part of the file based on the group?

 

[Stewaro1]

This is a controlled roll-out. We NOT WANT anyone (on incidental reboot) to get update until we are prepared to push to specific site. Are you suggesting that because GROUP ID is being used in 96x1H.. file it does not recognize it once it goes to the settings file?

 

[kyle555]

phone retains it on reboot as defined by CM in the station form for h323 sets.

Try it out. Make a set group 3 in the settings file but group 4 in the station form, reboot it and see what it grabs in 96x1Hupgrade

 

[Stewaro1]

Thanks. So I did not state my problem correctly.
Once I split the firmware upgrade file to designate which phones should update, I am not getting the phones to recognize the group settings in the 46xxsettings file. I have checked spelling syntax of the GOTO GETSET commands to the settings file.

Once the phone reboots, it correctly steps through the DHCP scope and points to appropriate files, and firmware updates....It will not set itself with features outlined in group settings at bottom of settings file. It will only accept settings enabled/not # out in the file feature statements itself.

 

[kyle555]

post your settings and upgrade file? Phone does the upgrade before settings file.

 

[Stewaro1]

You can see the names of files in previous attachment.
Portion of 96x1Hupgrade file:
# 9611SW
IF $GROUP SEQ 30 GOTO TEST
IF $GROUP SEQ 31 GOTO TESTAgt
## Production
GET 96x1HProd.txt
GOTO END
# TEST
GET 96x1HQA.txt
# END
# TESTAgt
GET 96x1HQAAgt.txt
# END
GOTO GETSET
# GETSET
GET 46xxsettings_96x1.txt

My groups are just site designations. The '0' differentiates an agent phone which has different feature sets.
'96x1HProd' is the current firmware level file for phones. It is pointing to same settings file.
'96x1HQA' & '96x1HQAAgt' is the new firmware level file being rolled out.
The two settings files are attached. The only way I can get the features to be enabled is to remove ## out from designated feature. Thus the reason for two different settings' files. See 1 settings files attached for agent. Same for other I just enable different features in file statements itself

 

[Stewaro1]

CORRECTION...... My '96x1Hupgrade' has these statements. They match the group ID in the settings file previous attached.
# 9611SW
IF $GROUP SEQ 11 GOTO TEST
IF $GROUP SEQ 12 GOTO TEST
IF $GROUP SEQ 13 GOTO TEST
IF $GROUP SEQ 14 GOTO TEST
IF $GROUP SEQ 15 GOTO TEST
IF $GROUP SEQ 16 GOTO TEST
IF $GROUP SEQ 17 GOTO TEST
IF $GROUP SEQ 110 GOTO TESTAgt
IF $GROUP SEQ 120 GOTO TESTAgt
IF $GROUP SEQ 130 GOTO TESTAgt
IF $GROUP SEQ 140 GOTO TESTAgt
IF $GROUP SEQ 150 GOTO TESTAgt
IF $GROUP SEQ 160 GOTO TESTAgt
IF $GROUP SEQ 170 GOTO TESTAgt
## Production
GET 96x1HProd.txt
GOTO END
# TEST
GET 96x1HQA.txt
GOTO END
# TESTAgt
GET 96x1HQAAgt.txt
# END
GOTO GETSET

 

[kyle555]

Maybe the "getset" at the end is messing you up? You can syslog a phone and see what/why it's doing things. They all follow their "group" thing and then go to end which says go to getset which might be making the phone ignore getting 96x1HProd/QA/etc.

 

[DAVIDPAYNE]

The only way I have been able to get this to work in the upgrade file, to load FW1 on only phones with a specific Group ID was to build the the file for each Group ID.
Everything needs to happen in the one file, until you are ready to get the settings files.

 

[john8lee]

looks like you are missing a goto end
GET 96x1HProd.txt
GOTO END
# TEST
GET 96x1HQA.txt
GOTO END
# TESTAgt
GET 96x1HQAAgt.txt
GOTO END
# END
GOTO GETSET

 

[Stewaro1]

I checked that GOTO END in the file. Thanks John8lee. However, that was not the issue. After testing, thanks to Kyle555, and turning on syslog; I uncovered that the phone jumping multiply firmware files (96x1Hupgrade ---> 96x1Prod.txt, etc..) before hitting the settings file it drops the Group ID tag and thus is being ignored by the settings file. A controlled roll out of firmware using group ID to determine what/when firmware is to downloaded; I had to designate which settings file from 96x1HProd.txt, 96x1HQA.txt, 96x1HQAAgt.txt) the phone should get with its intended firmware. Then on each settings file I had to enable the corresponding features. Thanks for all the suggestions. Hope that makes sense. After the firmware roll out I can/will remove the hierarchical tiered firmware files and have one settings file with the Group ID---then the phones will recognize the Group ID in the settings file and its corresponding feature selections.

 

[john8lee]

Thanks Stewaro1, I am looking to do a rollout of SIP to my 9608 phones but only want to roll to a limited selection and keep the rest on H.323.
I will try the same approach