96x1Hupgrade.txt for multiple releases?

[bostong3]

Hi, I know that Avaya would probably not approve of this, but....

Is there a way to write an if/then statement into the 96x1Hupgrade.txt file? Something like this or maybe in another area?

********************************************* Application and Kernel file for 9611*********************************************

# 9611SW

IF APPNAME S9608_11HALBR6_2_3_13_V452.tar GOTO GETSET
IF APPNAME S9608_11HALBR6_3_0_37_V452.tar GOTO GETSET
SET RFSNAME S96x1_UKR_V13r94_V13r94.tar
SET APPNAME S9608_11HALBR6_3_1_16_V452.tar
GOTO GETSET

We have a CM upgrade coming up and have a mix of releases on our 9611Gs. In a perfect world, I'd love to get them all on the same release prior to the upgrade, but it's not going to happen. A good # of them are at 6.2313 and 6.3037 which are both acceptable for CM 6.3.x. I'd like to be able to update the phones that are pre 6.2313 to 6.3116, but not the 6.2313 and 6.3037.

I hope this makes sense!

 

[lopes1211]

What is the reasoning for not wanting the 6.2313 to upgrade as well?

-CL

 

[bostong3]

I'd love to, but.... Too many phones, not enough time. Most of them are at remote locations where there is no dedicated IT staff and management prefers that someone is on-site when upgrades occur to ensure there are no issues. And we've had issues in the past, such as the phones look good, but don't get dialtone, etc after a successful upgrade.