Avaya 96XX downloads SIP file, not H323

[moose4me]

Hello all,

I have a situation where my 96XX IP phones, when they are rebooted, whether manually or a power glitch, come back up as a SIP phone, not to its original H323 set. I have to go in and clear the settings and enter them manually in which case, the phone come up ok, as H323.
Has anyone experienced this issue before? It just started all its own. In the past, when disconnected or relocated to another network jack, they would come up ok, H323, but now, they come up as a SIP phone. Not sure at this point what is causing that. Any input is greatly appreciated.

 

[kyle555]

Default in the firmware is H323... What's DHCP 242 look like? What do your 96x1Hupgrade.txt and 96x1Supgrade.txt look like?

 

[jimbojimbo]

First, to be clear you are talking about a 96xx (9620, 9630, 9640, etc) and not a 96x1 (9608, 9611, 9621).

You most likely have a setting for SIP configured somewhere. For example with 96x1 if you SET SIG 2 in the 46xxsettings.txt file you will download SIP firmware.

Are you using the utility server or another HTTP server (I prefer Apache httpd on Linux)? I use a stand alone Linux system because I'm not locked out of root and can view any of the HTTP/HTTPS access logs.

 

[gwebster]

96x0 models use a common 96xxupgrade.txt file. 96x1 models use 96x1Hupgrade.txt for H.323 and 96x1Supgrade.txt for SIP. As mentioned above, check for a "SET SIG" in your 46xxsettings.txt file (or whatever it is called).

 

[moose4me]

Thanks for the responses guys:
Kyle555- this is what the files look like, tried looking for the DHCP 242 but could not find it.
96x1Hupgrade.txt:
********************************************
* Common Kernel/RFS File for all 96x1 models
********************************************
IF $MODEL4 SEQ 9641 GOTO 9641SW
IF $MODEL4 SEQ 9608 GOTO 9608SW
IF $MODEL4 SEQ 9611 GOTO 9611SW
IF $MODEL4 SEQ 9621 GOTO 9621SW
*********************************************
* Application and Kernel file for 9641
*********************************************
# 9641SW
SET RFSNAME S96x1_UKR_V9_V9.tar
SET APPNAME S9621_41HALBR6_0_20S_V452.tar
GOTO GETSET
*********************************************
* Application and Kernel file for 9608
*********************************************
# 9608SW
SET RFSNAME S96x1_UKR_V9_V9.tar
SET APPNAME S9608_11HALBR6_0_20S_V452.tar
GOTO GETSET
*********************************************
* Application and Kernel file for 9611
*********************************************
# 9611SW
SET RFSNAME S96x1_UKR_V9_V9.tar
SET APPNAME S9608_11HALBR6_0_20S_V452.tar
GOTO GETSET
*********************************************
* Application and Kernel file for 9621
*********************************************
# 9621SW
SET RFSNAME S96x1_UKR_V9_V9.tar
SET APPNAME S9621_41HALBR6_0_20S_V452.tar
GOTO GETSET
********************************************
* Get the settings file
********************************************
# GETSET
GET 46xxsettings.txt
96x1Supgrade.txt:
IF $MODEL4 SEQ 9601 GOTO 9601sp0
# 9601sp0
SET APPNAME S9601aSALB_R6_1_0r26418_V11r1271.tar
SET APPSIGNAME S9601aSALB_R6_1_0r26418_V11r1271.tar.sig
## if the phone has earlier load than SP0 then download SP0 and then SP3, else download SP3
IF $APPNAME_IN_USE SEQ S9601aSALB_R6_1_0r26418_V11r1271.tar GOTO 9601sp3
IF $APPNAME_IN_USE SEQ S9601aSALB_R6_1_2r26428_V11r1271.tar GOTO 9601sp3
IF $APPNAME_IN_USE SEQ S9601_SALB_R6_1_3r27949_V11r1448.tar GOTO 9601sp3
GOTO GETSET
# 9601sp3
SET APPNAME S9601_SALB_R6_1_3r27949_V11r1448.tar
SET RFSNAME S9601_UKR_V11r1448_V11r1448.tar
SET APPSIGNAME S9601_SALB_R6_1_3r27949_V11r1448.tar.sig
SET RFSSIGNAME S9601_UKR_V11r1448_V11r1448.tar.sig
GOTO GETSET
# GETSET
GET 46xxsettings.txt

Jimbojimbo: yes, they are all 96XX models. I did find a SET SIPSIGNAL 2 parameter on my 46xxsettings.txt file but its here:
############################################################
## ##
## SIP SETTINGS ##
## Settings applicable only to 46xx telephone models ##
## or 96xx telephone models in non-Avaya environments ##
## ##
############################################################
## SIP Signaling Transport Type
## Specifies the type of transport to use for SIP signaling.
## 0 for UDP
## 1 for TCP
## 2 for TLS (default)
## SET SIPSIGNAL 2
it specifies for non-Avaya environments. Although we are using Cisco routers and switches for connectivity, would that be an issue? We are using Avaya utility servers, there are seven in our network but only one is in the "Running" mode, the others are "stopped"

gwebster: since I am the only one who manages the Avaya network, I am sure that no changes were made to any of the servers. All our 96XX phones when plugged in would always come up H.323, no matter which location they were plugged in. But now, when a new phone, or a phone that has been factory reset by using the "clear" option, you can see that it downloads ha96xxual_50.bin, and hb96xxual_50bin. It's only when I manually input the values that it downloads the proper H323 files.

I am still at it, please feel free to suggest more input as every little clue may point me in the right direction.

 

[gwebster]

You are using ancient software. If you are buying new 9698G/9611G, they will not even downgrade to those releases. Start by upgrading your server to use more recent software.

 

[gwebster]

Your 96x1Hugrade.txt file is for 6.020S which is circa 2011. Your 96x1Supgrade.txt file is for 6.1.3.2 whish is from the same timeframe and should only apply to the 9601. If you are using software that old, then you probably have much bigger issues happening as there has been significant bug-fix since that time.

 

[moose4me]

Thanks guys for the responses. I had hoped that the software releases was not an issue since this problem appeared our of nowhere ...one day all is good, the next, well, issues. However, one good thing came out of all of this, and that is that instead of setting the IP phones to factory using the "clear" option, all I have to do is simply change the SIG option on the phone from SIP to H.323. Then use the 'Restart Phone" option on the phone screen and in a few minutes, the phone is back to working order as H.323. I don't have to enter IP addresses.

I'll see what I can do for upgrading, but if something comes to mind, please let me (us) know.

 

[ken07734]

Are you using the Avaya utility server? if so are do you have the firmware set for SIP instead of H323?