* <span style="color:#ff0000">'''IMPORTANT NOTE 1: Direct upgrading from version 324BXX to 400BXX is not possible, you have to update first to the version 355B25 and then to the version 400'''</span> to facilitate customers in this task we prepared an auto-update script at this address: [http://dect.snom.com/324-to-400/auto-update.php http://dect.snom.com/324-to-400/auto-update.php] , please follow the reported instructions.

+

* <span style="color:#ff0000">'''IMPORTANT NOTE 2: Rollback to version 355BXX or 380BXX is possible from version 400BXX</span>

+

====Upgrading base or handsets from version 324 or earlier:====

* <span style="color:#ff0000">'''IMPORTANT NOTE 1: After upgrading to the version 355BXX you WILL NOT ABLE TO DOWNGRADE TO THE VERSION 324BXX. Please take this upgrade carefully'''</span>

* <span style="color:#ff0000">'''IMPORTANT NOTE 1: After upgrading to the version 355BXX you WILL NOT ABLE TO DOWNGRADE TO THE VERSION 324BXX. Please take this upgrade carefully'''</span>

* <span style="color:#ff0000">'''IMPORTANT NOTE 2: The upgrade will remove all the manually uploaded contacts from the global addressbook. Please make sure to re-upload the addressbook after the update.'''</span>

* <span style="color:#ff0000">'''IMPORTANT NOTE 2: The upgrade will remove all the manually uploaded contacts from the global addressbook. Please make sure to re-upload the addressbook after the update.'''</span>

Download links

Latest version

Upgrading to version 400BXX from version 324BXX or earlier:

IMPORTANT NOTE 1: Direct upgrading from version 324BXX to 400BXX is not possible, you have to update first to the version 355B25 and then to the version 400 to facilitate customers in this task we prepared an auto-update script at this address: http://dect.snom.com/324-to-400/auto-update.php , please follow the reported instructions.

IMPORTANT NOTE 2: Rollback to version 355BXX or 380BXX is possible from version 400BXX

Upgrading base or handsets from version 324 or earlier:

IMPORTANT NOTE 1: After upgrading to the version 355BXX you WILL NOT ABLE TO DOWNGRADE TO THE VERSION 324BXX. Please take this upgrade carefully

IMPORTANT NOTE 2: The upgrade will remove all the manually uploaded contacts from the global addressbook. Please make sure to re-upload the addressbook after the update.

IMPORTANT NOTE 3: In case you are doing the update from a 323 version you need to update to the version 324B12 before applying the version 355

Firmware binaries

If you have read and understood the Release Notes and all the reported information, click here to show the download links

Update Instructions

Downloading locally the firmware files

Before starting the update, you must download all required files and save them in folders using the exact structure described below.

Do not rename the update files as the base station will look for file names that adhere to the M-series naming scheme.

All M-series product names start with a capital M, followed by one to three numerals.

The names of the firmware files also start with the capital M and are followed by one to three numerals, i.e., M700, M300, M65, M25, etc.

The product name is followed by the underscore _ which, in turn, is followed by a small v and the three-digit firmware version preceded by a zero, i.e., 0323, 0324, 355 etc.

Starting from version 355 you must also define the branch number using 4 digits preceded by a small b.

The repeater firmware file is without a branch number (Eg. M5_v0039.fwu)

The file name has the .fwu extension

Examples:

The update file for updating the M700 to version 324 must be named M700_v0324.fwu

The update file for updating the M65 to version 324 must be named M65_v0324.fwu

The update file for updating the M300 to version 355 branch 16 must be named M300_v0355_b0016.fwu

Note: Linux/Unix based HTTP servers are case sensitive. Since all M-series product names start with a capital M, the names of the folders must also start with a capital M, i.e., M700, M300, M65, M25, etc. Naming the folders m700, m300, etc. will cause the downloads to fail.

Set up a folder for each M-series product on your http server and download the firmware file for each product into the respective folder.