Find the 96xxupgrade. txt, open it in any text editor and you should see something similar to this (if youre using the sample file from Avaya # # Check backup application version # # IF MODEL goto BACKUPAPP 96XX. It will just jump to GETSET. Within the PHONEAPP 96XX section, my file says # PHONEAPP 96XX SET APPNAME ha96xxua1_1_03_n goto GETSET Maybe yours does too. This just sets the application file to the right name. I am looking to convert these phones to the SIP firmware from Avaya, from my understanding I need have the phones pull the config files from a. If you have an Avaya telephone system, you probably have a web server to manage firmware. If not, its pretty easy to set up so let me know if I should post the procedures. What is not easy is testing firmware before deploying it to. N ENHANCED CALL FORWARDING Forwarded Destination Active Unconditional For Internal Calls To: n External Calls To: n Busy For Internal Calls To: n External Calls To: n No Reply For Internal Calls To: n External Calls To: n SAC/CF Override: n This method will follow. But thats a different post. For now, I hope this helps and I look forward to hearing from you. This method will follow the phone so if you log a new extension into the phone, it will retain the phones setting. However, it gets over-ridden by the stations group if there is one. Interaction gets complicated. My 96xxupgrade file now has this line in the BACKUPAPP 96XX section: # BACKUPAPP 96XX IF GROUP SEQ 30 goto BACKUPAPP 30. IF BOOTNAME SEQ hb96xxua3_1_03_n goto PHONEAPP 96XX. SET APPNAME hb96xxua3_1_03_n goto GETSET When the phone gets to that line in red, it will check against. Note how theres a check against a MODEL 4 variable? This allows the phone to jump to a new section after a very basic check. Unfortunately, there are only a few variables available. Ive never been able to find a definitive list of all available variables.