- Joined
- May 2, 2018
- Messages
- 14
- Reaction score
- 1
We have provisioned several M300 and M700 across different sites. I've lost track of which device was running on which firmware. So I was wondering, why 3cx is updating the firmware of D7** automatically, but not the one of our DECT devices.
I've found, that the provisioning template for M300 and M700 found in
According to Snom, this however is placed in the wrong location.
So I replaced it with what we know from D7**
... and created the following file
Rebooting the base will then reload the configuration and upgrade both, the base and headsets' firmware. So far, we don't have any issues with this. However, I guess the template file might be replaced by a 3cx upgrade. That's why I hope 3cx is considering updating the template.
I've found, that the provisioning template for M300 and M700 found in
/var/lib/3cxpbx/Instance1/Data/Http/Templates/fxs contains the following:
XML:
<!--########################################################-->
<!--### Firmware Update ###-->
<!--########################################################-->
<firmware-settings>
<firmware>http://dect.snom.com/</firmware>
<fp_fwu_sw_version>400</fp_fwu_sw_version>
<fp_fwu_branch_version>2</fp_fwu_branch_version>
<pp_fwu_sw_version type=M65>400</pp_fwu_sw_version>
<pp_fwu_branch_version type=M65>2</pp_fwu_branch_version>
<pp_fwu_sw_version type=M85>400</pp_fwu_sw_version>
<pp_fwu_branch_version type=M85>2</pp_fwu_branch_version>
<pp_fwu_sw_version type=M25>400</pp_fwu_sw_version>
<pp_fwu_branch_version type=M25>2</pp_fwu_branch_version>
</firmware-settings>
According to Snom, this however is placed in the wrong location.
Do NOT specify neither bootloader (FW < Version 5)] nor firmware inside setting files:
In order to perform automated firmware updates specify a firmware setting file URL inside firmware status which points to the firmware setting file containing the firmware image URL.
So I replaced it with what we know from D7**
XML:
<firmware_status perm="">https://3cx.**.**/provisioning/*****/firmware/snom/snomM300.xml</firmware_status>
... and created the following file
https://3cx.**.**/provisioning/*****/firmware/snom/snomM300.xml
XML:
<?xml version="1.0" encoding="utf-8"?>
<firmware-settings>
<firmware>http://dect.snom.com/</firmware>
<fp_fwu_sw_version>410</fp_fwu_sw_version>
<fp_fwu_branch_version>14</fp_fwu_branch_version>
<pp_fwu_sw_version type=M65>410</pp_fwu_sw_version>
<pp_fwu_branch_version type=M65>11</pp_fwu_branch_version>
<pp_fwu_sw_version type=M85>410</pp_fwu_sw_version>
<pp_fwu_branch_version type=M85>11</pp_fwu_branch_version>
<pp_fwu_sw_version type=M25>410</pp_fwu_sw_version>
<pp_fwu_branch_version type=M25>11</pp_fwu_branch_version>
</firmware-settings>
Rebooting the base will then reload the configuration and upgrade both, the base and headsets' firmware. So far, we don't have any issues with this. However, I guess the template file might be replaced by a 3cx upgrade. That's why I hope 3cx is considering updating the template.