Can't get Avaya 9610 IP phones to convert H.323 to SIP prior to registering with FreePBX

I’m not sure if this is the proper place to post this, but as somebody once claimed, it’s better to plead for forgiveness than to ask for permission, so here goes… I’m hoping there’s some Avaya geeks or others out there that can help me out.

The preamble to my issue:
Firstly, I’m running FreePBX / Asterisk 13.29.2 with all patches up to date. I have three models of Avaya IP phones. The first two, an Avaya 9650 and an Avaya 9620L were originally running H.323. It was a relatively easy process to convert them from H.323 to SIP R2.6.17, which is, as I understand, the latest release of SIP firmware that will work on these two phone. On the website, enter the product “9650”, and download the file.

These Avaya phones are provisioned using http using DHCP server option 242 with the following string (I’m using pfSense 2.4.4 as my router firewall):


HTTPDIR=/ indicates that the root directory to look for files is the Server Root, in my case /var/www/html
HTTPSRVR is the IP address where the web server is running
SIP_CONTROLLER_LIST is a list of addresses of SIP Proxies (i.e., the FreePBX server)
The SIG=2 option indicates that H.323 software, if it exists on the IP, should be converted to SIP.
Since port 80 is in use by Let’s Encrypt certificate management (FreePBX menu under System Admin–>Port Management), I needed to add the following line (i.e., Listen 8080) to /etc/httpd/conf/http.conf:

#Listen 80 # Removed by FreePBX Sysadmin Module
Listen 8080

Note: you can, if you wish, have httpd listen on multiple ports, as follows:

Listen 8080
Listen 8118

altho’ I didn’t have reason do this.

The zip file is then unzipped into the /var/www/html directory on FreePBX, permissions and ownership are changed appropriately. The /var/www/html directory looks as follows (I’ve removed some .xml files to minimize clutter):

$ ls -l
total 25100
-rw-rw-r-- 1 asterisk asterisk 714851 Mar 15 23:06 46xxsettings.txt
-rwxrwxrwx 1 asterisk asterisk 118549 Oct 1 2015 96xxmibDRAFT.txt
-rwxrwxrwx 1 asterisk asterisk 4608 Mar 13 14:22 96xxupgrade.txt
drwxrwxr-x. 10 asterisk asterisk 4096 Mar 13 15:55 admin
-rwxrwxrwx 1 asterisk asterisk 8921 Mar 17 07:40 Alternate_96xxupgradeSIP_R2_6_17.txt
drwxrwxr-x. 2 asterisk asterisk 59 Feb 15 16:58 digium_phones
drwxrwxr-x 11 asterisk asterisk 4096 Mar 10 10:10 fop2
-rwxrwxrwx 1 asterisk asterisk 4418058 Mar 2 2009 hb96xxua3_00.bin
-rwxrwxrwx 1 asterisk asterisk 4422067 Oct 8 2015 hb96xxua3_00_SHA256.bin
-rw-rw-r–. 1 asterisk asterisk 453 Feb 22 23:00 index.php
lrwxrwxrwx 1 asterisk asterisk 52 Jan 12 23:17 provisioning -> /var/www/html/admin/modules/endpointman/provisioning
-rwxrwxrwx 1 asterisk asterisk 17528 Mar 23 2017 release.xml
drwxrwxr-x. 2 asterisk asterisk 22 Feb 15 2018 restapi
drwxrwxr-x. 2 asterisk asterisk 4096 Feb 15 16:50 restapps
-rw-rw-r–. 1 asterisk asterisk 361 Feb 22 23:00 robots.txt
drwxrwxrwx 2 asterisk asterisk 4096 Mar 24 2017 signatures
-rwxrwxrwx 1 asterisk asterisk 4730256 Apr 25 2014 SIP96xx_2_6_12_1.bin
-rwxrwxrwx 1 asterisk asterisk 4747120 Mar 24 2017 SIP96xx_2_6_17_0.bin
-rwxrwxrwx 1 asterisk asterisk 4751145 Mar 24 2017 SIP96xx_2_6_17_0_SHA256.bin
lrwxrwxrwx. 1 asterisk asterisk 38 Feb 15 2018 ucp -> /var/www/html/admin/modules/ucp/htdocs
lrwxrwxrwx. 1 root root 47 Feb 15 2018 wcb.php -> /var/www/html/admin/modules/webcallback/wcb.php

Two important files are the 96xxupgrade.txt file and the massive 46xxsettings.txt file. The latter file contains a vast number of parameters that can be changed. I changed only the following:

SET DNSSRVR,,,9,9,9,9
SET TIMEZONE America/Vancouver

The 9650 (IP address is rebooted (usually by pressing the “menu key” followed by “27238#”). You can see that the 9650 is reading the files if you tail /var/log/httpd/access.log - - [17/Mar/2020:21:06:07 -0700] “GET //96xxupgrade.txt HTTP/1.1” 200 4608 “-” “Mozilla/4.0 (compatible; MSIE 6.0)” - - [17/Mar/2020:21:06:07 -0700] “GET //46xxsettings.txt HTTP/1.1” 200 714851 “-” “Mozilla/4.0 (compatible; MSIE 6.0)”

This procedure will convert 9650 H.323 firmware to SIP R2.6.17, and then prompt for a username (i.e., extension) and password (i.e., secret in FreePBX lingo) and the 9650 registers with FreePBX

The identical procedure works to convert 9620L H.323 to SIP R2.6.17 and to register the 9620L with FreePBX.

That’s the end of the preamble. Now on to the issue.

The procedure above does not work for the Avaya 9610, an admittedly older phone, long discontinued. Comments at the top of the 96xxupgrade.txt that comes in the file appear to indicate that the 9610 can only be upgraded to H.323 Rel. 3.0 and make no mention of SIP firmware that will work with the 9610 (nor the 9620 or 9630), only with other phones including the 9650 and the 9620L:
9610 - Commented for Default H323 Release 3.0
9620 - Commented for Default H323 Release 3.0
9630 - Commented for Default H323 Release 3.0
9620L - Commented for Default H323 Release 3.0
- Support for SIP Release 2.6.17
9620C - Commented for Default H323 Release 3.0
- Support for SIP Release 2.6.17
9630G - Commented for Default H323 Release 3.0
- Support for SIP Release 2.6.17
9640 - Commented for Default H323 Release 3.0
- Support for SIP Release 2.6.17
9640G - Commented for Default H323 Release 3.0
- Support for SIP Release 2.6.17
9650 - Commented for Default H323 Release 3.0
- Support for SIP Release 2.6.17

I have combed through the website and I can find no SIP firmware that will support the 9610

My question is, I am quite sure that the Avaya 9610 supports SIP signaling, but which version of SIP firmware does it support? And is that firmware available anywhere?

I messed with 9608 phones trying them. I’m only posting this link as maybe that it might have something in it that will help you on your endeavour. It was what I did with that 9608 model to get it to SIP, albeit I wasn’t happy with the performance of those phones. Not sure if it will help you with 9610’s but every little bit might help.

@dickson Thanks for your reply.

My issue occurs before registration, in that I can’t convert the H.323 firmware to SIP. I think if I was able to locate a version of the SIP firmware that is (I’m speculating here) R2.6.14.5 or earlier, I might be able to convert to SIP. I’m getting the value “R2.6.14.5” from the first few lines in the most recent (Jan. 20, 2020) 46xxsettings file, as below:

# *** 19 January 2020 ***
# This file is intended to be used as a template for configuring Avaya IP telephones.
# Parameters supported by software releases up through the following are included:
# J100 SIP R4.0.4.0 (J129, J139, J159, J169, J179)
# 96x1 SIP R7.1.8.0
# Avaya IX Workplace 3.7 (running on Avaya Vantage Devices)(f.k.a Avaya Equinox)
# J169/J179 R6.8.3 H.323
# 96x1 H.323 R6.8.3
# B189 H.323 R6.8.3
# Avaya Vantage Devices SIP R2.0.1.0 (K155/K165/K175)
# Avaya Vantage Connect Application SIP R2.0.1.0
# J169/J179 R6.7.1 H.323
# 96x1 H.323 R6.7.1
# B189 H.323 R6.7.1
# 96x0 H.323 R3.2.4
# 96x0 SIP R2.6.14.5
# H1xx SIP R1.0.2
# 16xx H.323 R1.3.3
# Note: At the end of the file there is HISTORY TABLE to track changes in this file.

As I said earlier, I’m not able to locate any earlier versions of the SIP firmware on that are documented to support the 9610. If anyone knows where, or can share, it would be appreciated.

I added a link to the bottom of that URL with a firmware that might(?) help you.

Looking at the Avaya support site (I have login credentials) there are no firmware files that seem to be available prior to the ones I posted. Just this

@dickson Thanks again for your reply. The firmware that you posted in the URL above is the exact firmware that I used with the 9650 and the 9620L and it worked to convert those phones from H.323 to SIP. But it didn’t work for the 9610.

Also, the link from that you in your most recent post is already familiar. As I mentioned I have combed thru this site looking for SIP software that might work with the 9610, but haven’t been able to locate anything that might work.

Its like anything before that doesn’t exist. I’ve got a several coworkers who have contractor access to those sites and they confirmed that’s all they are seeing as available too for download. “how can we make our product more difficult and less appealing for potential customers to use.”

@dickson Too bad, I guess that’s one avenue that’s closed. I’m still hoping that maybe someone, somewhere, has an earlier version of the SIP firmware in the /var/www/html directory (or more precisely, Server Root) on their webserver. After all, as far as I can tell, those files are necessary every time an Avaya 9650 or 9620L phone reboots.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.