Updating Firmware On The snom m3
This afternoon I finally took some time to update the firmware in the snom m3 phone system. The phones arrived early in January loaded with v1.01, but in the eight weeks since then snom has released v1.07.
Performing the upgrade was extremely simple and took about 20 minutes. The default settings access snom’s provisioning server to fetch the firmware so nothing about the phones settings required adjustment.
The installation process went as follows:
1. Press the [select] button in the center of the 4 way navigation dial to access the phones menu.
2. Move up one to the [settings] menu and [select]
3. Move down 5 to the System Setting option and [select]
4. Enter the 4 digit pin code (default = 0000) and [select]
5. Move down 4 to Firmware upgrade and [select]
6. Wait while the phone connects to the provisioning server and retrieves the list of software releases.
7. Moved to the desired release and [select]
8. Confirm your selection using the [yes] or [no] soft keys when prompted
9. Wait.
The LCD backlight will go out for a while as the upgrade is downloaded and installed. Don’t worry. This is normal. The backlight will come one again when the process moves to its next step.
The base unit is upgraded first, then each handset. Early in the process you see a text mode screen indicating progress as a per centage.
This indicates the download, writing and verifying of the firmware to the base unit. This is followed by a progress display in four parts.
When the upgrade is complete the handset announces this fact as follows:
Each stage in the process take just a little longer than you might think. Be patient. Just when you suspect that it’s hung the LCD lights up and the next step proceeds.
The snom support wiki has very good information about the upgrade process and potential error codes that the phone might display. For the very organized there’s also detaisl on how to setup routine scheduled firmware updates. In my case manual updates suffice. Thankfully I didn’t need those diagnostic resources today.
Comments are closed.
[…] February from the initial shipment. These have now been through three firmware upgrades (described here, here and here) and are working […]