Compatibility Notes
- The minimum recommended firmware is 4.0.4
- J100 series support only one line registration
- J129 does not have programmable linekeys and is only supported for legacy, not Builder provisioning
Provisioning URL
The following methods can be used to point the devices to the Endpoints Module.
- Log in to the device's admin interface and navigate to Management. Set the HTTP(s) Server Address to portal.connecting-britain.com and set HTTP(s) Server Directory Path to cfg. If this is missing you're running an older firmware and the option will be under Management.
- Use DHCP options 242, setting like HTTPSRVR=10.138.251.67,HTTPDIR=cfg
- Use Avaya DES - contact your partner manager to sign up for Avaya DES.
Firmware Updating
Download the latest files from Avaya, upload the entire set of files with names unchanged. Because of the number of files, it may be preferable to upload via SFTP and move the files to /var/www/html/frm.
Advanced Firmware Management (Optional)
If you need to have select phones get different firmware versions, that can be managed from the J100Supgrade.txt file.
- Upload the firmware bin files
- Edit the J100Supgrade.txt and specify a special group to get different firmware. This can be set by MAC address or GROUP
- The group cannot currently be set from the config file
- On the phone screen set the MAC/GROUP by navigating to Menu > Administration > Group
- From the phone web GUI set the MAC/GROUP by navigating to Settings > Other
- The example below is NOT meant to be used verbatim, adjust the file/model names as needed to the firmware and devices available
IF $GROUP SEQ 42 GOTO J100_SPECIAL
IF $MACADDR SEQ "c8:1f:ea:ce:d3:7a" GOTO J100_SPECIAL
GOTO J100_NORMAL
# J100_SPECIAL
IF $MODEL4 SEQ J129 GOTO J129_SW_SPECIAL
IF $MODEL4 SEQ J139 GOTO J139_SW_SPECIAL
IF $MODEL4 SEQ J159 GOTO J159_SW_SPECIAL
IF $MODEL4 SEQ J169 GOTO J169_SW_SPECIAL
IF $MODEL4 SEQ J179 GOTO J179_SW_SPECIAL
IF $MODEL4 SEQ J189 GOTO J189_SW_SPECIAL
GOTO GETSET
# J129_SW_SPECIAL
SET APPNAME FW_S_J129_R4_0_7_0_5b284.bin
GOTO GETSET
# J139_SW_SPECIAL
SET APPNAME FW_S_J139_R4_0_7_0_5b284.bin
GOTO GETSET
# J159_SW_SPECIAL
SET APPNAME FW_S_J159_R4_0_7_0_5b284.bin
GOTO GETSET
# J169_SW_SPECIAL
SET APPNAME FW_S_J169_R4_0_7_0_5b284.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_15.bin
GOTO GETSET
# J179_SW_SPECIAL
SET APPNAME FW_S_J179_R4_0_7_0_5b284.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_15.bin
GOTO GETSET
# J189_SW_SPECIAL
GET J189Special.txt
SET APPNAME FW_S_J189_R4_0_7_0_5b284.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_15.bin
GOTO GETSET
# J100_NORMAL
IF $MODEL4 SEQ J129 GOTO J129_SW
IF $MODEL4 SEQ J139 GOTO J139_SW
IF $MODEL4 SEQ J159 GOTO J159_SW
IF $MODEL4 SEQ J169 GOTO J169_SW
IF $MODEL4 SEQ J179 GOTO J179_SW
IF $MODEL4 SEQ J189 GOTO J189_SW
GOTO GETSET
# J129_SW
SET APPNAME FW_S_J129_R4_0_7_0_5b275.bin
GOTO GETSET
# J139_SW
SET APPNAME FW_S_J139_R4_0_7_0_5b275.bin
GOTO GETSET
# J159_SW
SET APPNAME FW_S_J159_R4_0_7_0_5b275.bin
GOTO GETSET
# J169_SW
SET APPNAME FW_S_J169_R4_0_7_0_5b275.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_15.bin
GOTO GETSET
# J179_SW
SET APPNAME FW_S_J179_R4_0_7_0_5b275.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_15.bin
GOTO GETSET
# J189_SW
GET J189Normal.txt
SET APPNAME FW_S_J189_R4_0_7_0_5b275.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_15.bin
GOTO GETSET
# GETSET
GET 46xxsettings.txt
Transport
Avaya J Series format supports UDP, TCP, and TLS transports. If you are using TLS/SRTP the following overrides are needed.
If your certificate authority is not one Avaya builds into their firmware you will need to add the parameter TRUSTCERTS. The value of TRUSTCERTS will be the filename of your SSL chain file in pem format, it should be loaded to Files and Firmwares on your Endpoints Module.
TLSSRVRID="0" // this is only required if wildcards certs are used
ENABLE_PUBLIC_CA_CERTS="1"
MEDIAENCRYPTION="1,9"
ENFORCE_SIPS_URI="0"
Special Overrides
- Setting a value as NULL will blank out a setting; for example; PHNOL="NULL"