In some situations you would like to have the possibility to load multiple provisioning files.

  • First file with general settings
  • Second file with device specific settings
  • If required more files then 2 can be used

Maxwell provisioning version 1.1

The device receives an provisioning URL to download the first file.

Example provisioning file with general settings.
?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="mx3b">

    <!-- <file version="2.22.4" url="" flags="FORCE_ACCEPT"/> -->
    <!-- SIP -->

    <param name="SIP.DefaultAccount" value="0" />
    <param name="SIP.Account.0.AccountName" value="1012" />
    <param name="SIP.Account.0.Active" value="1" />
    <param name="SIP.Account.0.Provider" value="PBX" />
    <param name="SIP.Account.0.AuthName" value="1012" />
    <param name="SIP.Account.0.AuthPassword" value="password" />
    <param name="SIP.Account.0.DisplayName" value="1012" />
    <param name="SIP.Account.0.Username" value="1012" />
    <param name="SIP.Account.0.Domain" value="" />
    <param name="SIP.Account.0.CallWaiting" value="1" />
    <param name="SIP.Account.0.ProxyServer.Address" value=""/>
    <param name="SIP.Account.0.ProxyServer.Port" value="5060" />
    <param name="SIP.Account.0.RegistrationServer.Address" value=""/>
    <param name="SIP.Account.0.RegistrationServer.Port" value="5060"/>
    <param name="SIP.Account.0.OutboundProxy.Mode" value="2"/>
    <param name="SIP.Account.0.OutboundProxy.Address" value=""/>
    <param name="SIP.Account.0.OutboundProxy.Port" value="5060"/>
    <param name="SIP.Account.0.FailoverServer.Enabled" value="0"/>
    <param name="SIP.Account.0.CLIPSource" value="2"/>
        <step type="Redirect" url="" />

The Parameter: <step type="Redirect" url="" />

Contains the URL to the second provisioning file.

URL can contain:

  • Name of the file (Example: test_second.xml)
  • %MACD.xml (%MACD will be replaced with own MAC address)

Example for the second provisioning file
<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="mx3b">

    <param name="SIP.Account.0.DisplayName" value="1012_3" />

Maxwell provisioning version 1.0

With the Maxwell, it works as follows:

  1. Via the Gigaset redirect server, set the redirect to the file "provisioning.xml" that is located on the own web-server.
  2. The file "provisioning.xml" contains the information about the next files to be downloaded.
    1. Firmware
    2. Settings
    3. Custom
  3. The file "firmware.xml" could contain information about the firmware update to be done yes or no, is optional.
  4. The file "settings.xml" contains information about the xml file that has the settings, these can be multiple files.


We would like to change the http digest username and password via auto provisioning before it downloads customer specific settings protected with these HTTP digest username and password.


This file can be used for:

  1. Firmware update
  2. Link to config file (that contains the URL to 2 files)


<?xml version="1.0" encoding="UTF-8"?> <provisioning version="1.0" productID="mx3b">

<category type="firmware" url=""/>

<category type="nvm" url=""/>



This file takes care that first the http digest username and password are loaded, and then the file with the config is loaded. 


<?xml version="1.0" encoding="UTF-8"?> <nvm version="1.0" productID="mx3b">

<file url=""/>

<file url=""/>



Takes care that the HTTP digest username and password are loaded.


<?xml version="1.0" encoding="UTF-8"?> <settings version="1.0" productID="mx3b" >

<param name="System.Security.HTTPAuthUsername" value="Gigaset"/>

<param name="System.Security.HTTPAuthPassword" value="Password"/>



%MACD is replaced with the real MAC address.

Contains the Settings of the device, this file is secured via:

  • HTTP Digest

Change also via this file the provisioning URL so that it always contacts the providers provisioning server loading the <MAC>.xml via HTTPS and HTTP Digest

  • No labels