Phone Firmware with multiple models

[trilogy8]

I use IIS for our phones to get firmware and settings. We have had 96xx, 961x and B189 models deployed on the same floor and have been able to combine all the relevant firmware into 1 specific folder where the web server points. Recently, we have also started deploying the J169 models. Since adding these files into the mix the 96xx,961x models lose the visiting user field for whatever reason. The only way to get this back is to repoint the webserver at the old folder, without the J169 files. Has anyone come across this?

 

[Wanebo]

We experienced something similar but it was with a different setting. Our solution was to put the J series phoes into their own seperate group and tweak their settings there.

 

[trilogy8]

How do you put them separate if they are on the same user switch/vlan as the other models using the same DHCP scope options and pointing to the same webserver?

 

[BIS]

Look in to SSON - here is a start

https://documentation.avaya.com/bun...page/Setting_Site-Specific_Option_Number.html

 

[phoneguy55]

##############################################################
##
# GROUP_SETTINGS
##
##############################################################
##
## Parameter values can be set for specifically-designated groups of
## telephones by using IF statements based on the GROUP parameter.
##
## The value of GROUP can be set manually in a telephone by using the
## GROUP local craft procedure or, for H.323 telephones, it can be set
## remotely by CM based on the telephone's extension number.
## The default value of GROUP in each telephone is 0,
## and the maximum value is 999.
##
## To create a group of settings, use one of the templates below,
## or create others just like them.
##
##############################################################

IF $GROUP SEQ 1 GOTO GROUP_1
IF $GROUP SEQ 2 GOTO GROUP_2

######################################################################################
## COMMON_CATCH-ALL_SETTINGS
######################################################################################
SET ...
GOTO END

##############################################################
# GROUP_1
SET...
GOTO END

##############################################################
# GROUP_2
SET...
GOTO END


##############################################################
# END
############## END OF CONFIGURATION FILE #####################

 

[wpetilli]

I'm also seeing this issue with these models. I use IIS and have the webserver pointed at a folder that has the combined firmware files of the 96xx and j169 h.323 phones. We use one common 46xx.settings file. In this state my 96xx phones lose the 3rd field that allows to select visiting user. It isn't until I repoint the webserver at a folder with only the 96xx files and then reboot. Has anyone experienced this? This is becoming a major issue for us.

 

[wpetilli]

After several hours of tinkering with this, I finally got to the bottom of it.

my issue: when combining firmware of 96xx, 961x, b189 and J169 phones my 9630's specifically would lose the visiting user option. Even with a successful onboarding of a 9630, which I assumed everything remains cached in the phone, the minute I pointed our web server at the combined folder I would lose the feature. Because of the amount of visitors from other regions we had multiple tickets / week from our help desk.

my fix: the newer 96xx upgrade.txt file had no mention of 9630. I copied in the original file into this directory and that solved the issue. I was able to leave both old and new in the directory as the names are slightly different. I did not try adding a line to the newer file with 9630, but I have it working normally nonetheless.

 

[gwebster]

The 96xxupgrade.txt file for the 96x0 as provided by Avaya contains the 3.3.2A firmware for the 9630. The 96x1Hupgrade.txt file for the 96x1/J169/J179 contains the correct firmware files for those models.