Hierarchy of XML files for the provisioning.

Let’s assume that the structure of directory containing all the provisioning files on the provisioning server has a next hierarchy and the further .xml files are presenting the case marked with a red arrow:

Examplarery hierarchy

Usage of empty or inappropriate values in value=” ” (see configuration.xml example below) can
lead to unpredictable behavior. Please, fulfill this field carefully according to the standards.

1) provisioning.xml

<?xml version="1.0" encoding="UTF-8"?>
	<provisioning version="1.0" productID="e2">
 			<category type="nvm"url="http://172.29.17.156/specific_path/nvm/updates.xml"/>
 	</provisioning>

2) updates.xml

<?xml version="1.0" encoding="UTF-8"?>
	<nvm version="1.0" productID="e2">
		<file version="2015-10-10_10:10:10" url="http://172.29.17.156/specific_path/nvm/configuration.xml"/>
 	</nvm>

3) configuration.xml

With 2016 software, the version value in this step 3 is changed from "date and time" to "1.0"

The "macAddress" is optional, see wiki article.

<?xml version="1.0" encoding="UTF-8"?>
	<settings version="1.0" productID="e2" macAddress= "7c:2f:80:00:00:00">  
		<!-- SIP -->
		
		
	</settings>

Example1:

Provisioning is done via an own local server with IP address: 192.168.178.101
All the provisioning files are in the directory maxwell
The URL to the provisioning server is: http://192.168.178.101/maxwell

When the device comes online after reboot, it will try to search in the above directory for the file "provisioning.xml".

In this file, the information about the other files is stored. Like, where to find the file "updates.xml" that contains the link to the file containing all the settings.

<MAC>.xml, the settings of the device can be found.

When you use this provisioning, the version value (version="2017-01-18_11:37:14") in the updates.xml must be increased every-time a new file must be downloaded. If the value is the same or older, then the device will not download the <MAC.xml>