Cisco SPA921 - - IP Phone Provisioning Manual page 43

Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
• Each element name must be unique. For fields that are duplicated on
multiple Line, User, or Extension pages, you must append [n] to indicate the
line, user, or extension number.
For example, the Dial Plan for Line 1 is represented by the following
element: <Dial_Plan[1]>
The following additional features can be used:
• Comments are delimited by a # character up to the end-of-line.
• Blank lines can be used for readability.
The following illustrates the format for each parameter-value pair:
Parameter_name [ '?' | '!' ] ["quoted_parameter_value_string"] ';'
Boolean parameter values are asserted by any one of the values {Yes | yes | Enable
| enable | 1}. They are deasserted by any one of the values {No | no | Disable | disable
| 0}.
The following are examples of plain-text file entries:
# These parameter names are for illustration only
Feature_Enable
Enable
Another_Parameter
Hidden_Parameter
Some_Entry
Multiple plain text files can be spliced together to generate the source for the final
binary CFG file. This is accomplished using the import directive at the start of a
new line followed by one or more spaces and the file name to splice into the
stream of parameter-value pairs. File splicing can be nested several files deep.
For example, the file base.txt contains the following:
Param1 "base value 1" ;
Param2 "base value 2" ;
The file spa1234.txt contains the following lines:
import base.txt
Param1 "new value overrides base" ;
Param7 "particular value 7" ;
! "Enable" ; # user read-write, but force the value to
? "3600" ; # user read-only
"abc123" ; # user not-accessible
! ; # user read-write, leaves value unchanged
2
41