Basics [DokuWiki extern]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Basics ======

**Scope of this document**

This document is describing the xml Templates for IP relays with http command set in the following PBX systems:\\ 
  * COMpact 4000\\ 
  * COMpact 5000/5000R\\ 
  * COMpact 5200/5200R\\ 
  * COMpact 5500R\\ 
  * COMmander 6000/6000R/6000RX\\

Minimum firmware requirement: Version 7.4 or later.\\ 
The document is meant for developers wanting to create or alter provisioning files for non supported devices.\\ 

A device to be provisioned is identified by its unique MAC-address. During the subscriber configuration, this MAC-address is either entered or selected from a list of unused but known MAC-addresses while entering the subscriber extension number.

If you would like to use provisioning you than have to specify a file which is sent to the subscriber if the subscriber requests provisioning data. The PBX will notify the subscriber if subscriber relevant data is changed in the PBX. The subscriber will then request new provisioning data.
Auerswald / FONtevo devices will use the new configuration immediately, devices from various other manufacturers will have to reboot to use the new configuration.

Zero Touch Provisioning:
This is a method where a device does not have to be configured, bevor it is connected by the PBX.
The only device identifier required in the PBX is the MAC-Address of the device. You only have to configure subscriber in the PBX and assign the subscriber number to the MAC-address of the device.
If zero-touch provisioning is possible, the device will use a multicast-based mechanism to find its provisioning server (the PBX) and if found, the device will request its configuration data. In this case, you can simply put the device on the user's desk, configure the PBX and all necessary steps for the device provisioning are done automatically.

The provisioning mechanism implemented in the Auerswald/FONtevo PBX is capable of supporting template files from a wide range of telephone manufactures.
The mechanism supports only text-based formats. Binary formats of any kind are NOT supported.

For some manufacturers, we have included basic template files which can be altered to better suit the needs of you or your customers.
If you encounter omissions or bugs, please send an email to the following address:
mailto:support@auerswald.de 
mailto:support@fontevo.com

__Principle:__\\
The mechanism used is a simple text replacement.
A value which should be provided by the PBX like an account name or an account password is represented in the configuration file by placeholder using a specially formatted string. If the configuration is sent to the device, a temporary duplicate instance of the configuration file is generated. Only in the duplicate file, the variables (placeholders) are substituted with the actual device data.
After transmitting this temporary file, it is automatically deleted.

Continue to [[.:variables|Next Chapter]] ->