Linksys SPA922 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 43

import, Multiple plain text files can be spliced together to generate the source for the final

Get Linksys SPA922 - IP Phone With Switch PDF manuals and user guides
UPC - 745883570836
View all Linksys SPA922 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 • 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: 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 ! "Enable" ; ? "3600" ; "abc123" ; # user read-write, but force the value to # user read-only # user not-accessible Some_Entry ! ; # 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 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" ; Cisco Small Business IP Telephony Devices Provisioning Guide 41

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
41
2
•
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” ;
# user read-write, but force the value to
Enable
Another_Parameter
? “3600”
;
# user read-only
Hidden_Parameter
“abc123” ;
# user not-accessible
Some_Entry
!
;
# 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 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” ;