Avaya J100 Expansion Module upgrade

Last Updated : Jan 12, 2023 |

Upgrade the Avaya J100 Expansion Module firmware to a new version using Avaya J100 Series IP Phones software distribution package. The combined package contains the .bin files for the button module upgrade, for example: FW_JEM24_R1_0_1_0_9.bin.

In the J100Supgrade.txt file, the following parameter points at the Avaya J100 Expansion Module upgrade file:
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_9.bin

During the boot-up, the phone downloads the new firmware for the Avaya J100 Expansion Module. The phone screen displays Updating software notification.

After the phone downloads the expansion module firmware, the upgrade process continues in the background. On the phone screen navigate to Main Menu > Administration > View > Button modules, to see the Upgrading status.

During the upgrade procedure, the Avaya J100 Expansion Module is functional. You can access phone features such as make and receive calls. Each module attached to the phone takes up to four hours to upgrade from an older software version to 1.0.1, and it takes up to an hour and a half to upgrade from software version 1.0.1 to a new one.

When the upgrade is complete, the Avaya J100 Expansion Module displays the following: “This device will be out of service for 3 minutes to apply the update. It will be applied automatically between 12am and 3am.”. Press the corresponding line button for Apply now or Apply tonight option to select the suitable upgrade time.

Note:

When the phone screen displays the Upgrade notification, the phone disables the expansion module screen saver and does not turn off the backlight.

Configuring JEM24_APPNAME parameter

From the software version 4.1.0, you can upgrade Avaya J100 Expansion Module to a newer firmware version by obtaining the upgrade files from another file server that is not the same as the initial provisioning server.

To obtain upgrade files from another file server, configure the JEM24_APPNAME parameter as one of the following:

  • An absolute URL: Prefix the URL with an https:// or http://. A valid URL supports a combination of IPv4, IPv6, or FQDN. a directory path can contain macros such as $MACADDRESS, $SERIALNO, and $MODEL4, and the URL can have optional values such as ports, sub-directories, and credentials.

    Few examples:

    http://10.1.1.2/FW_JEM24_R4_1_0_0_9.bin
    http://10.1.1.2/prov/firmware/FW_JEM24_R4_1_0_0_9.bin
    http://10.1.1.2:8080/FW_JEM24_R4_1_0_0_9.bin
    http://prov.example.com/FW_JEM24_R4_1_0_0_9.bin
    http://username:password@prov.example.com/prov/firmware/FW_JEM24_R4_1_0_0_9.bin
    https://upgrade.acme.com/J100/$MODEL4/FW_JEM24_R4_1_0_0_9.bin
    https://10.1.1.2/prov/firmware/FW_JEM24_R4_1_0_0_9.bin
    https://prov.example.com/prov/firmware/FW_JEM24_R4_1_0_0_9.bin
    https://prov.example.com:8080/prov/firmware/FW_JEM24_R4_1_0_0_9.bin
    https://username:password@prov.example.com/prov/firmware/FW_JEM24_R4_1_0_0_9.bin
  • A relative path that appends to the TLSDIR or HTTPDIR parameter value. For example:

    firmware/FW_JEM24_R4_1_0_0_9.bin
    J100/$MODEL4/FW_JEM24_R4_1_0_0_9.bin
  • An absolute path that temporarily ignores TLSDIR or HTTPDIR. For example:

    /firmware/FW_JEM24_R4_1_0_0_9.bin
    /FW_JEM24_R4_1_0_0_9.bin
  • A file name. For example:

    FW_JEM24_R4_1_0_0_9.bin
Note:

If the server that is hosting the .bin file requires authentication, configure the credentials in the URL. The phone ignores HTTP_AUTH_USERNAME and HTTP_AUTH_PASSWORD parameter values.