NoojeeProvision.xml
The following describes each of the settings in NoojeeProvision.xml and what they mean.
Database
<NoojeeProvision.Database>
...
Password
The password used to connect to the database.
Services
Specifies what protocols are available for the handsets to download settings files. Currently HTTP and TFTP are supported. You can enable one or both, but at least one must be enabled.
...
TemplateRoot
The root of the directory where the settings file templates will be stored. This is normally set to 'filesystem/handsets' which maps to /opt/njprovision/filesystem/handsets
FileService
The FileService describes the set of files which can be served by either the HTTP or TFTP service on request.
...
| Code Block | ||
|---|---|---|
| ||
<FileService preprocessor="Null">
<RootDirectory>config/fileservice</RootDirectory>
</FileService>
<!-- files in the fileservice-vm directory are pre-processed by velocity -->
<FileService preprocessor="Velocity">
<RootDirectory>config/fileservice-vm</RootDirectory>
</FileService> |
HTTP
Controls how the Noojee Provision HTTP service operates.
...
Port
The port number the HTTP services listens for requests on. This should normally be set to the default value of 80. Note: make certain that you don't have another HTTP services running from the same IP address.
TFTP
Controls how the Noojee Provision TFTP services operates. Note TFTP is a UDP based protocol.
...
Port
The port number the TFTP services listens for requests on. This should normally be set to the default value of 69. Note: make certain that you don't have another TFTP services running from the same IP address.
Modules
Modules can be added to Noojee Provision to extend the functionality of the system as well as defining a set of core functions.. This section provides settings for each module to be loaded into the system.
Module
Specifies the configuration details for a specific module.
...
The following control specific settings on the handset (sip_buddies).
OperatingContext - the context to place the handset into when provisioning the handset.
DTMFMode
Allow
Disallow
PickupGroup
CallGroup
Permit - semi-colon separated list of ip/subnet masks.
e.g.10.0.0.0/255.0.0.0;172.16.0.0/255.255.0.0;192.168.0.0/255.255.0.0</Permit>
Deny- semi-colon separated list of ip/subnet masks.
Range02. NoojeeProvision.xml settings
...
<Exclusion>00:21:5c:95:93:f8</Exclusion>
<Exclusions>
Manufacturers
Provides settings for each manufacturer supported by Noojee Provision . Additional manufacturers can be added by adding another Manufacturer section with the appropriate settings. Noojee Provision has no specialized code for a manufacturer, all operations are controlled from the Noojee Provision .xml configuration file.
Manufacturer
...
Name
The name of the manufacturer. There is no real significance in this entry, it is only used as convenience to identify actions and problems associated with a specific manufactures settings and handsets.
MACPrefix
Allows the definition of one ore more MacPrefix elements. The prefix used by all handsets manufactured by this manufacturer. This is generally the first 6 digits from the mac address found on the back of a handsets.
...
The path, relative to the TemplateRoot where the settings files for this manufacturer can be found. This should normally be something like:
/snom/templates
Where name is the same name you used in the Name element above.
TemplateFiles
...
Specifying a pattern can be important in networks were ARP doesn't work. Many phones request a filename which includes the Mac address. By specifying a pattern which matches the requested filename Noojee Provision can then extract the MAC address from the filename.
SIP
Controls how the Asterisk realtime SIP details are configured for each handset added to the Asterisk server.
...