Avaya Utility Server 6.3 - Firmware & 46xxsettings File

[AuraPS]

Hi

On the Utility server (6.3 VMware OVA - no root PW), does anyone know how to get IP phones to pickup the 46xsetting.txt files whilst the FW is deactivated ....it’s the 96xxupgrade.txt in the FW pack that tells the phone to check the FW then ‘goto GETSET’ to get the 46xxsettings.
I don’t want to install new FW....but when I deactivate, the phone does not see the 96xxupgrade.txt file (404) and is therefore not told to ‘goto GETSET’ so the new settings are not picked up. It just boots up without trying to get the 46xxsettings.txt

I have tried to put a 96xxupgrade.txt file manually on the server (with just to command – ‘GET 46xxsettings.txt’) but the /var/

http://www/html

folder on the utility server is root owned and Avaya have tied down the root/sroot passwords. (Does anyone know this????)

Any ideas? – I’m testing a 9650...so the 96xx-IPT-H323...FW & 96xxupgarde.txt is relevant here.

Many thanks

 

[montyzummer]

if that is the case why not install the firmware the phones are on and unpack activate and utilize the settings file from there

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[AuraPS]

monty, I understand your point but we have a situation whereby we only want to apply new 46xxsettings and not invoke a FW upgrade. we have hundreds of IP phones.

thanks

 

[kyle555]

Why not download and activate the release of firmware your phones are using right now?
Or, if you can edit 96xxupgrade.txt or 96x1upgrade.txt (depending on model) you could also just make them say to do nothing.
The way 96xxupgrade.txt works is it says "if you're not running _______, then download this bootloader and image and upgrade yourself"

So, the right tweak to that file would make the phone ignore firmware and just go to 46xxsettings. That, or activate the older firmware you're already using in production on it.

 

[montyzummer]

Thats exactly what i meant ^

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[AuraPS]

Kyle / Monty

I have considered these options but we have hundreds of IP phones (all on varying versions), therfore i would have to upload the relevant version and reset each IP phone version in turn / then repeat for each version...not an option from an admin point of view.

I cannot edit the 96xxupgrade file nor can I upload my own to the /var/

http://www/html

folder on the utility server because the file/folder is 'root' owned and Avaya have not given us the option to set the root PW, not do we know what it is

On IIS or the MV_IPTel server i used to just insert the command 'GET 46xxsettings.txt' at the top of the 96xxupgarde file to bypass the FW upgrade

thanks

tom

 

[sekitori]

Place the firmware/settings files on your own http/ftp server and do whatever you want ?

regards,
Sekitori

 

[AuraPS]

Yes Sekitori ...that what i would love to do but our customer's (i'm business partner) telephony design and proposition includes the utility server -- i do not want to tell them that Avaya have restricted it so that we have less flexibilty

 

[sekitori]

Wouldn't it be better to be honest ?

Personally, I wouldn't do business with a 'partner' that doesn't tell me the (whole) truth....

Sekitori

 

[kyle555]

I know you can specify different firmware for different models, but can you not get more granular than that on a per site/vlan basis?

Even at that, I would phrase it somewhat positively and say "Avaya does it this way to avoid dealing with a gaggle of phones doing the same thing all at different firmware loads that make everyone's life more complicated to diagnose afterwards."

Unless you've got a very good reason to run different loads of firmware - then that's probably you're biggest problem!

But, hacking up the 96xxupgrade to just say "GOTO 46xxsettings.txt" might fix it all up for ya.

 

[AuraPS]

We intend to get everything in line as it should be eventually, but we are dealing with around a 1000 handsets so i need a workaround in the interim to apply some 46xxsettings only. It is an upgrade to a system that hasn't been well managed over the years. It's our job to straighten things out.

I'm just a mere engineer trying to find a workaround and keep a large customer happy, the fact that the utility server has had the root access tied down makes life that little bit more difficult.

Anyway, it's back to IIS for now....thanks all for your input

 

[sekitori]

cdtd,

You could temporarily set up your own FTP/HTTP server - the IP-address for it can be specified in the Vlan's DHCP option string 176/242 on the DHCP server.

That way you could even test only a small amount of sets when they are in their separate vlan (with it's own dhcp range)

You can set it back later the the utility server's....

regards,
sekitori