Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleProvisioning flow

The N870 auto provisioning flow is described below.

Step

1

Provisioning URL = URL to a server.

N870 tries to download the file provisioning.xml

If the file "provisioning.xml" is not on the server, the N870

will try to download the file "<MAC>.xml>"

2
3
4
5
6
7
8





Section

   

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


Warning
titleImportant note!

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
Code Block
languagexml
titleprovisioning.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
Code Block
languagexml
titleupdates.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.


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

 

...