04. Creating Manufacturer (Phone)Template files

Overview 

The primary purpose of Noojee Provision is to automate the generate of configuration files for handsets.
Each manufacturer has their own proprietary configuration file, however they all have certain common requirements.
Using the NoojeeProvision.xml file you can control how each manufacturers configuration file is generated.
You need to start be creating a configuration file which contains all of the handset features that you want to configure.
The easiest way to start this process is by downloading a sample configuration file from the manufacturers website or some handsets will let you export their current settings from their web interface. This can be an easy way of getting the configuration file correct. Simply set the phone up as you would want it to operate using the handsets web interface. Export the configuration and save it to the manufactureres directory under filesystem/handsets.
Once you have a configuration file you need to modify it so that Noojee Provision can manipulate the file at runtime.
The resulting file is referred to as the Template file. You will need one for each brand of phone that you plan on deploying into your network.
Each time a phone requests a configuration file Noojee Provision will take your Template and search for any replaceable properties.
A replaceable properties takes the following form:
$<Name>
Where <Name> is the name of a built-in property or a property that you have defined in the NoojeeProvision.xml file.

Noojee Provision has a number of built-in properties which you don't need to define in the Properties section of NoojeeProvision.xml.

The following is an example extracted from a Snom Template file:

user_pname1$: $AsteriskUsername
user_pass1$: $AsteriskPassword
user_name1$: $Extension
user_realname1$: CLID
user_host1$: $AsteriskServer
user_srtp1$: off

New templates should be checked into svn

[http://repos.noojeeit.com.au/svn/Ast...rovision/trunk]