Cisco SPA525G Administration Guide - Page 139

General Purpose Parameters - config file

Page 139 highlights

Provisioning Basics IP Phone Configuration Profiles 7 The names of parameters in XML profiles can generally be inferred from the SPA9000 configuration web pages, by substituting underscores (_) for spaces and other control characters. Further, to distinguish between Lines 1, 2, 3, and 4, corresponding parameter names are augmented by the strings _1_, _2_, _3_, and _4_. For example, Line 1 Proxy is named Proxy_1_ in XML profiles. The plain-text configuration file uses a proprietary format, which can be encrypted to prevent unauthorized use of confidential information. By convention, the profile is named with the extension .cfg (for example, spa942.cfg). The Cisco SIP Profile Compiler (SPC) tool is provided for compiling the plain-text file containing parameter-value pairs into an encrypted CFG file. The SPC tool is available from Cisco for the Win32 environment (spc.exe) and Linux-i386-elf environment (spclinux-i386-static). Availability of the SPC tool for the OpenBSD environment is available on a case-by-case basis. The syntax of the plain-text file accepted by the profile compiler is a series of parameter-value pairs, with the value in double quotes. Each parameter-value pair is followed by a semicolon. The following is an example of a valid text source profile for input to the SPC tool: Admin_Passwd "some secret"; Upgrade_Enable "Yes"; Parameters in the case of source text files for the SPC tool are similarly named, except that to differentiate Line 1, 2, 3, and 4, the appended strings ([1], [2], [3], or [4]) are used. For example, the Line 1 Proxy is named Proxy[1] in source text profiles for input to the SPC. General Purpose Parameters These are configured in the General Purpose Parameters section of the Provisioning tab. These parameters can be used as variables in provisioning and upgrade rules. They are referenced by prepending the variable name with a '$' character, such as $GPP_A. You can optionally Require Admin Password to Reset Unit to Factory Defaults (see last line of sample config file). Cisco SPA and Wireless IP Phone Administration Guide 137

  • 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
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280

Provisioning Basics
IP Phone Configuration Profiles
Cisco SPA and Wireless IP Phone Administration Guide
137
7
The names of parameters in XML profiles can generally be inferred from the
SPA9000 configuration web pages, by substituting underscores (_) for spaces and
other control characters. Further, to distinguish between Lines 1, 2, 3, and 4,
corresponding parameter names are augmented by the strings _1_, _2_, _3_, and
_4_. For example, Line 1 Proxy is named Proxy_1_ in XML profiles.
The plain-text configuration file uses a proprietary format, which can be encrypted
to prevent unauthorized use of confidential information. By convention, the profile
is named with the extension .cfg (for example, spa942.cfg). The Cisco SIP Profile
Compiler (SPC) tool is provided for compiling the plain-text file containing
parameter-value pairs into an encrypted CFG file. The SPC tool is available from
Cisco for the Win32 environment (spc.exe) and Linux-i386-elf environment (spc-
linux-i386-static). Availability of the SPC tool for the OpenBSD environment is
available on a case-by-case basis.
The syntax of the plain-text file accepted by the profile compiler is a series of
parameter-value pairs, with the value in double quotes. Each parameter-value pair
is followed by a semicolon. The following is an example of a valid text source
profile for input to the SPC tool:
Admin_Passwd “some secret”;
Upgrade_Enable “Yes”;
Parameters in the case of source text files for the SPC tool are similarly named,
except that to differentiate Line 1, 2, 3, and 4, the appended strings ([1], [2], [3], or
[4]) are used. For example, the Line 1 Proxy is named Proxy[1] in source text
profiles for input to the SPC.
General Purpose Parameters
These are configured in the
General Purpose Parameters
section of the
Provisioning
tab. These parameters can be used as variables in provisioning and
upgrade rules. They are referenced by prepending the variable name with a ‘$’
character, such as $GPP_A.
You can optionally Require Admin Password to Reset Unit to Factory Defaults (see
last line of sample config file).