Cisco SPA901-UK Provisioning Guide - Page 40
import, directive at the start of
![]() |
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 40 highlights
Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 The following additional features can be used: • Comments are delimited by a # character, from the character to the end-ofline. • Blank lines can be used for readability. The following string 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 ! "Enable" ; ? "3600" ; "abc123" ; ! ; # user read-write, but force the value to # user read-only # user not-accessible # user read-write, leaves value unchanged Multiple plain text files can be spliced together to generate the source for the final binary CFG file. This is accomplished by 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" ; When compiled, spa1234.cfg becomes: Param1 "base value 1" ; Param2 "base value 2" ; Param1 "new value overrides base" ; Param7 "particular value 7" ; Cisco Small Business IP Telephony Devices Provisioning Guide 39
![](/manual_guide/products/cisco-spa901uk-provisioning-guide-a8e818b/40.png)