Introduction In our other devices, provisioning must handle multiple binary files (master.bin, sifs_...bin, sit_...bin, sih_...bin, siu_...bin) in order to get the final URL to config file. As provisioning is changed towards downloading xml files, we have created a new provisioning method in Maxwell 3/Basic. The Provisioning Server URL can be found in the web-interface under: Settings - System - Provisioning and Configuration How to configure the provisioning URL:The provisioning server URL can be provided via the following Methods: - DHCP option 114
- SIP Multicast
- Gigaset Redirect server
- Manually via web-interface
Provisioning files on the server:When the provisioning is started, the device will contact the server to download the provisioning files. Provisioning URL | Action: | Comment |
---|
http://<Server URL>/device | GET /device | No retry | | GET /device/provisioning.xml | Master xml file containing information about location of other files for: - Firmware update
- Settings
- Custom settings
One retry if file is not present. | Using placeholders (%MACD, %MACC, %DVID) |
---|
http://<Server URL>/device/%MACD.xml | GET /device/<MAC address>.xml | %MACD is replaced with the devices LAN MAC address Example: GET /device/7c2f12345678.xml | http://<Server URL>/device/%MACC.xml | GET /device/<MAC address with colons>.xml | %MACC is replaced with the devices LAN MAC address with colons: Example: GET /device/7c:2f:12:34:56:78.xml | http://<Server URL>/device/%DVID/%MACD.xml | GET /device/82/1/<MAC address>.xml | %DVID is replaced with the devices Device ID, composed by build variant and provisioning ID. Example: GET /device/82/1/7c2f12345678.xml |
Provisioning.xml fileThe provisioning.xml file must provide additional properties like: Version [YYYY-MM-DD_HH:MM:SS] productID [mx3b] macAddress [optional] They will be verified before taking any further actions. If the macAddress is not specified then the corresponding xml file / entry will be applied to all devices. (You need to remove the macAddress and not macAddress="") <?xml version="1.0" encoding="UTF-8"?> <provisioning version="1.0" productID="mx3b" macAddress="7c:2f:80:9c:f2:02"> <category type="firmware" url="http://192.168.178.101/device/firmware/updates.xml" /> <category type="nvm" url="/nvm/updates.xml" /> <!-- relative path - use the same server address --> <!-- You can also use the placeholders like: url="/nvm/%MACD.xml" >
<category type="custom" url="/custom/updates.xml" /> <!-- relative path - use the same server address --> </provisioning>
|
Communication with provisioning server after downloading the provisioning.xml: - GET /device/firmware/updates.xml
- GET /device/nvm/updates.xml
- GET /device/custom/updates.xml
FirmwareThe provisioning.xml file points to the Firmware file like in the above example: <category type="firmware" url="http://192.168.178.101/device/firmware/updates.xml" /> The file must provide additional properties like: Version [YYYY-MM-DD_HH:MM:SS] productID [mx3b] macAddress [optional] They will be verified before taking any further actions. If the macAddress is not specified then the corresponding xml file / entry will be applied to all devices. (You need to remove the macAddress and not macAddress="")
|