Linksys SPA922 Cisco SPA9000 Voice System Administration Guide - Page 185

Remote Provisioning Features, Using Configuration Profiles - resync

Page 185 highlights

Advanced Topics in SPA9000 Administration Remote Provisioning Features A Remote Provisioning Features The SPA9000 provides for secure provisioning and remote upgrade. Provisioning is achieved through configuration profiles that are transferred to the device via TFTP, HTTP, or HTTPS. Using Configuration Profiles The SPA9000 accepts configuration profiles in XML format, or alternatively in a proprietary binary format, which is generated by a profile compiler tool available from Linksys. The SPA9000 supports up to 256-bit symmetric key encryption of profiles. For the initial transfer of the profile encryption key (initial provisioning stage), the SPA9000 can receive a profile from an encrypted channel (HTTPS with client authentication), or it can resync to a binary profile generated by the Linksyssupplied profile compiler. In the latter case, the profile compiler can encrypt the profile specifically for the target SPA9000, without requiring an explicit key exchange. The XML file consists of a series of elements (one per configuration parameter), encapsulated within the element tags ... . The encapsulated elements specify values for individual parameters. Refer to the following example of a valid XML profile: some secret Yes Binary format profiles contain SPA9000 parameter values and user access permissions for the parameters. By convention, the profile uses the extension .cfg (for example, spa2000.cfg). The Linksys Profile Compiler (SPC) tool compiles a plain-text file containing parameter-value pairs into a properly formatted and encrypted .cfg file. The SPC tool is available from Linksys for the Win32 environment and Linux-i386-elf environment. Requests for SPC tools compiled on other platforms are evaluated on a case-by-case basis. Please contact your Linksys sales representative for further information about obtaining the SPC tool. 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. Here is an example of a valid text source profile for input to the SPC tool: Admin_Passwd "some secret"; Upgrade_Enable "Yes"; SPA9000 Voice System Administration Guide 183

  • 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
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286

Advanced Topics in SPA9000 Administration
Remote Provisioning Features
SPA9000 Voice System Administration Guide
183
A
Remote Provisioning Features
The
SPA9000
provides for secure provisioning and remote upgrade. Provisioning is
achieved through configuration profiles that are transferred to the device via TFTP,
HTTP, or HTTPS.
Using Configuration Profiles
The
SPA9000
accepts configuration profiles in XML format, or alternatively in a
proprietary binary format, which is generated by a profile compiler tool available
from Linksys. The
SPA9000
supports up to 256-bit symmetric key encryption of
profiles. For the initial transfer of the profile encryption key (initial provisioning
stage), the
SPA9000
can receive a profile from an encrypted channel (HTTPS with
client authentication), or it can resync to a binary profile generated by the Linksys-
supplied profile compiler. In the latter case, the profile compiler can encrypt the
profile specifically for the target
SPA9000
, without requiring an explicit key
exchange.
The XML file consists of a series of elements (one per configuration parameter),
encapsulated within the element tags <flat-profile> … </flat-profile>. The
encapsulated elements specify values for individual parameters.
Refer to the following example of a valid XML profile:
<flat-profile>
<Admin_Passwd>some secret</Admin_Passwd>
<Upgrade_Enable>Yes</Upgrade_Enable>
</flat-profile>
Binary format profiles contain
SPA9000
parameter values and user access
permissions for the parameters. By convention, the profile uses the extension .cfg
(for example, spa2000.cfg). The Linksys Profile Compiler (SPC) tool compiles a
plain-text file containing parameter-value pairs into a properly formatted and
encrypted .cfg file. The SPC tool is available from Linksys for the Win32
environment and Linux-i386-elf environment. Requests for SPC tools compiled on
other platforms are evaluated on a case-by-case basis. Please contact your
Linksys sales representative for further information about obtaining the SPC tool.
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. Here is an example of a valid text source profile for
input to the SPC tool:
Admin_Passwd
“some secret”;
Upgrade_Enable “Yes”;