Cisco SPA525G Administration Guide - Page 145

Retail Provisioning, Automatic In-House Preprovisioning

Page 145 highlights

Provisioning Basics Retail Provisioning 7 Retail Provisioning The Cisco IP phone includes an web UI that displays internal configuration and accepts new configuration parameter values. The server also accepts a special URL command syntax for performing remote profile resync and firmware upgrade operations. In a retail distribution model, a customer purchases a Cisco voice endpoint device, and subsequently subscribes to a particular service. The customer first signs on to the service and establishes a VoIP account, possibly through an online portal. Subsequently, the customer binds the particular device to the assigned service account. To do so, the unprovisioned Cisco IP phone is instructed to resync with a specific provisioning server through a resync URL command. The URL command typically includes an account PIN number or alphanumeric code to associate the device with the new account. In the following example, a device at the DHCP-assigned IP address 192.168.1.102 is instructed to provision itself to the SuperVoIP service: http://192.168.1.102/admin/resync?https://prov.supervoip.com/cisco-init/ 1234abcd In this example, 1234abcd is the PIN number of the new account. The remote provisioning server is configured to associate the Cisco IP phone that is performing the resync request with the new account, based on the URL and the supplied PIN. Through this initial resync operation, the Cisco IP phone is configured in a single step, and is automatically directed to resync thereafter to a permanent URL on the server. For example: https://prov.supervoip.com/cisco-init For both initial and permanent access, the provisioning server relies on the Cisco IP phone client certificate for authentication and supplies correct configuration parameter values based on the associated service account.1-5 Automatic In-House Preprovisioning Using the web UI and issuing a resync URL is convenient for a customer in the retail deployment model, but it is not as convenient for preprovisioning a large number of units. Cisco SPA and Wireless IP Phone Administration Guide 143

  • 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
Retail Provisioning
Cisco SPA and Wireless IP Phone Administration Guide
143
7
Retail Provisioning
The Cisco IP phone includes an web UI that displays internal configuration and
accepts new configuration parameter values. The server also accepts a special
URL command syntax for performing remote profile resync and firmware upgrade
operations.
In a retail distribution model, a customer purchases a Cisco voice endpoint device,
and subsequently subscribes to a particular service. The customer first signs on to
the service and establishes a VoIP account, possibly through an online portal.
Subsequently, the customer binds the particular device to the assigned service
account.
To do so, the unprovisioned Cisco IP phone is instructed to resync with a specific
provisioning server through a resync URL command. The URL command typically
includes an account PIN number or alphanumeric code to associate the device
with the new account.
In the following example, a device at the DHCP-assigned IP address 192.168.1.102
is instructed to provision itself to the SuperVoIP service:
1234abcd
In this example, 1234abcd is the PIN number of the new account. The remote
provisioning server is configured to associate the Cisco IP phone that is
performing the resync request with the new account, based on the URL and the
supplied PIN. Through this initial resync operation, the Cisco IP phone is
configured in a single step, and is automatically directed to resync thereafter to a
permanent URL on the server. For example:
For both initial and permanent access, the provisioning server relies on the Cisco
IP phone client certificate for authentication and supplies correct configuration
parameter values based on the associated service account.
1-5
Automatic In-House Preprovisioning
Using the web UI and issuing a resync URL is convenient for a customer in the
retail deployment model, but it is not as convenient for preprovisioning a large
number of units.