Features/Auto Provisioning/Configuration Files/XML

From Snom User Wiki

Jump to: navigation, search

Contents

Introduction

With firmware version 7 snom introduces a new Mass Deployment concept based on XML formatted setting files. Additionally the new concept allows to build up more complex file structures. These structures and all supported XML tags will be described in detail below.

Supported Container Tags and Sub Tags

Setting Files Container <setting-files>

Settings Container <settings>

Firmware File <firmware-settings>

Structure

  1. One "general setting file container <setting-files>" per phone type, i.e. snom300, snom320 etc., providiong a list of setting file URLs linked to:
    1. One "settings container (<settings>)" per phone type containing general configuration parameters grouped in XML tags (<phone-settings>, <functionKeys>, <tbook>, <dialplan>) OR/AND individual XML Settings Files per phone type containing general configuration parameters:("Phone settings setting file", "Function key setting file", "Directory setting file", "Dial plan setting file")
    2. One "Phone user interface language file container" per phone type with a list of phone user interface language file URLs
    3. One "Web user interface language file container" per phone type with a list of web user user interface language file URLs
  2. One "specific setting file container <setting-files>" per phone, i.e. MAC address based, providing a list of setting file URLs linked to:
    1. One "settings container (<settings>)" per phone containing phone specific configuration parameters grouped in XML tags (<phone-settings>, <functionKeys>, <tbook>, <dialplan>) OR/AND individual XML Settings Files one per phone containing phone specific configuration parameters:("Phone settings setting file", "Function key setting file", "Directory setting file", "Dial plan setting file")
  3. Firmware setting files contains a subset of firmware related configuration parameters allowing automated firmware updates

Example Structure

You can download the following example structure and unpack it into your web server root directory. Remember you have to adapt the files according your needs.

Personal tools
Interoperability