Page tree
Skip to end of metadata
Go to start of metadata
Introduction

It is possible to insert a link to a second xml config file that is automatically loaded after the first config file.

This can be used to first download the basic settings in clear text and then the other settings encrypted .



N510 IP PRO

The DX800 version 173 has the same functionality like the N510.

XML parameters:

Tag nameValueMeaning
EXTENDED_PROFILEstring

URL to xml file. Example: http://<provider/server URL>/<Directory (optional)>/<filename.xml>

From software 210 and higher also %MACD placeholder is allowed. When used, the device will replace this with own MAC address.

Example: http://<provider/server URL>/<Directory (optional)>/%MACD_2.xml>

Example to http file:

<EXTENDED_PROFILE class="string" value="http://192.168.178.200/device/xml/%MACD_2.xml"/>

Example to https file:

<EXTENDED_PROFILE class="string" value="https://192.168.178.200/device/xml/%MACD_2.xml"/>


In this example we will first load the default xml file and here we link to a second xml file.

 N510 first xml file

<?xml version="1.0" encoding="ISO-8859-1"?>
<ProviderFrame xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="profile.xsd">
<Provider>
<MAC_ADDRESS value="7C2F8030D21E"/>
<PROFILE_NAME class="string" value="n510_test"/>

<SYMB_ITEM ID="BS_IP_Data1.aucS_SIP_DOMAIN" class="symb_item" value='"192.168.178.120"'/>
<SYMB_ITEM ID="BS_IP_Data1.ucB_SIP_ACCOUNT_IS_ACTIVE_1" class="symb_item" value="1"/>
<SYMB_ITEM ID="BS_IP_Data3.aucS_SIP_LOGIN_ID" class="symb_item" value='"test3"'/>
<SYMB_ITEM ID="BS_IP_Data1.aucS_SIP_REGISTRAR" class="symb_item" value='"192.168.178.120"'/>
<SYMB_ITEM ID="BS_IP_Data1.aucS_SIP_USER_ID" class="symb_item" value='"test3"'/>
<SYMB_ITEM ID="BS_IP_Data1.aucS_SIP_PASSWORD" class="symb_item" value='"test3"'/>
<SYMB_ITEM ID="BS_Accounts.astAccounts[0].aucAccountName[0]" class="symb_item" value='"Timer_4"'/>
<SYMB_ITEM ID="BS_IP_Data1.aucS_SIP_SERVER" class="symb_item" value='"192.168.178.120"'/>
<SYMB_ITEM ID="BS_IP_Data1.aucS_SIP_DISPLAYNAME" class="symb_item" value='"test"'/>

<!-- Needed to enable Provisioning, After Reboot -->
<SYMB_ITEM ID="BS_IP_Data.ucB_AUTO_UPDATE_PROFILE" class="symb_item" value="0x1"/>
<SYMB_ITEM ID="BS_IP_Data3.ucI_ONESHOT_PROVISIONING_MODE_1" class="symb_item" value="0x1"/>

<!-- Link to second user specific configuration file -->
<EXTENDED_PROFILE class="string" value="http://<Provider URL>/device/xml/7c2f8030d21e_2.xml"/>


</Provider>
</ProviderFrame>

From N510 software 210 (and DX800 software 173) we also support the usage of the placeholder %MACD

Example: <EXTENDED_PROFILE class="string" value="http://<Provider URL>/device/xml/%MACD_2.xml"/>

%MACD will be replaced with the device own MAC address.

The xml file name should be with capital letters, else the device can not find the xml file.

In the second file we just inserted some settings.

 N510 second xml file

<?xml version="1.0" encoding="ISO-8859-1"?>
<ProviderFrame xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="profile.xsd">
<Provider>
<MAC_ADDRESS value="7C2F8030D21E"/>
<PROFILE_NAME class="string" value="n510_test"/>

<SYMB_ITEM ID="BS_Accounts.astAccounts[0].aucAccountName[0]" class="symb_item" value='"SecondXML"'/>

</Provider>
</ProviderFrame>



Maxwell Basic, 2 and 3

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.

Example:

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.

provisioning.xml

This file can be used for:

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

provisioning.xml

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

<category type="firmware" url="http://providerurl.com/device/firmware.xml"/>

<category type="nvm" url="http://providerurl.com/device/config.xml"/>

</provisioning>


config.xml

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

config.xml

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

<file url="http://providerurl.com/device/httpdigest.xml"/>

<file url="http://providerurl.com/devicesettings/%MACD.xml"/>

</nvm>


httpdigest.xml

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

httpdigest.xml

<?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"/>

</settings>



%MACD.xml

%MACD is replaced with the real MAC address.

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

  • HTTPS
  • 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