Firmware/Update/Update Description

From Snom User Wiki

Jump to: navigation, search

Date: Mar-24-2004 Author: Sven Fischer


Software Components

Snom phones come with two software components: a bootloader and a firmware. Both are stored in a flash memory on the phone. The flash also stores non-volatile settings like the network identity, the phone type or call lists.

The bootloader is required to load the initial firmware image on the phone and to start up the firmware. Even though the phone´s firmware became unusable by any means the bootloader still permits loading a firmware image from a TFTP server.

The firmware contains the software that makes up the VoIP phone. It includes the user interface, the stack and other components. The firmware also contains a software update mechanism that allows to load a new firmware into the flash memory of the phone.

Update using the bootloader via TFTP (via Phone GUI)

Please read the correspondend description in english or german.

Update via Web Interface (HTTP)

1. Go to Webinterface -> Status -> System Information


2. Check the currently running firmware and rootfs version

  • Application Version: snom3XX-SIP X.X.X
  • Rootfs version: snom3XX (ramdisk or jffs2) X.XX

3. Go to Webinterface -> Setup -> Software Update


4. Fill in the appropriate HTTP URL of the firmware image and click LOAD:


Note: For snom190 and snom3xx series only the firmware field is used. Don't use the bootloader field and if it is set, remove its content before clicking onto the LOAD button.

5. The phone displays "SW" and reboots automatically.

6. After rebooting you will be asked if you want to perform the update.

  • Confirm this by pressing the "OK" key.
  • While the update process continues Loading, Erasing and Writing will be displayed

Note: Do NOT ever interrupt this process by unpowering the phone. In such case the phone can only be recovered via TFTP Update.

7. The update process finishes by rebooting the freshly updated phone.

Update via Mass Deployment


Using Mass_deployment new firmware images can be downloaded automatically. The following settings are involved:

The complete boot- up procedure is explained in the mass deployment download section.

Remote phone reboot

The automatic update can be performed remotely. There are three options to trigger the update procedure and reboot the phone:

  1. To reboot the phone using the web interface
  2. To send a special SIP NOTIFY to the phone that will ask the phone to reboot
  3. Use update_policy setting set to auto_update

The SIP NOTIFY method waits until all calls on the phone have ended and then starts to reboot. This avoids service disruptions in networks where it is not clear whether or not the phone is idle.

An example notify could look like this:

NOTIFY sip:123@;line=3242msd SIP/2.0
From: ...
To: ...
Call-ID: ...
CSeq: 2342 NOTIFY
Event: reboot
Content-Length: 0

Defining Firmware Realms

An operator sometimes wants to control which firmware must be run in its network. By controlling the files that are downloaded during the start-up process, this can be done on a mac address based addressing mechanism. When a phone boots up for the first time, it always contacts the snom web page for downloading its settings. If the mac address of the phone has been set up for settings redirection, it will download the file for this mac address. This file contains a new value for the “setting_server” setting and the phone will automatically start downloading its setting from the URL in this variable. The phone is now in a different setting realm. This realm may define its own value for firmware and bootloader. It is then up to the operator to define the links for the software. To get your settings redirection account set up by snom, please contact and provide your company’s name and password. You will then receive an email with a username and password, which you can use to register your desired phones by MAC address for this redirection to your own setting server.

Personal tools