Cisco SPA525G Administration Guide - Page 141

Upgrading Firmware on a Phone, Provisioning, Firmware Upgrade, Upgrade Enable: yes - firmware update

Page 141 highlights

Provisioning Basics Upgrading, Resyncing, and Rebooting Phones 7 256-bit symmetric key encryption of profiles is supported. In addition, an unprovisioned Cisco IP phone can receive an encrypted profile specifically targeted for that device without requiring an explicit key. a secure first-time provisioning mechanism using SSL functionality. 1- User intervention is not required to initiate or complete a profile update or firmware upgrade. The Cisco IP phone upgrade logic is capable of automating multi-stage upgrades, if intermediate upgrades are required to reach a future upgrade state from an older release. A profile resync is only attempted when the Cisco IP phone is idle, because this may trigger a software reboot. General purpose parameters are provided to help service providers manage the provisioning process. Each Cisco IP phone can be configured to periodically contact a normal provisioning server (NPS). Communication with the NPS does not require the use of a secure protocol because the updated profile is encrypted by a shared secret key. The NPS can be a standard TFTP, HTTP or HTTPS server. The administrator can upgrade, reboot, or resync Cisco IP phones using the web interface. Upgrading Firmware on a Phone Use the upgrade URL to upgrade firmware on the Cisco IP phone. You can upgrade from either a TFTP or HTTP server. The Upgrade Enable parameter on the Provisioning web page must be set to Yes: Cisco IP phone web UI: Provisioning > Firmware Upgrade > Upgrade Enable: yes Use the following syntax to upgrade firmware on a phone: http://phone-ip-address/admin/upgrade?protocol://servername[:port]]/firmware-path • Protocol defaults to TFTP. • Server name is the host requesting the URL. • Port is the port of the protocol being used (for example, 69 for TFTP or 80 for HTTP). • Firmware-path defaults to /spa.bin (for example, http://192.168.2.217/ admin/upgrade?tftp://192.168.2.251/spa.bin) for SPA phones and / wip310.img for the WIP310. The firmware-pathname is typically the file name of the binary located in a directory on the TFTP or HTTP server. Cisco SPA and Wireless IP Phone Administration Guide 139

  • 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
Upgrading, Resyncing, and Rebooting Phones
Cisco SPA and Wireless IP Phone Administration Guide
139
7
256-bit symmetric key encryption of profiles is supported. In addition, an
unprovisioned Cisco IP phone can receive an encrypted profile specifically
targeted for that device without requiring an explicit key. a secure first-time
provisioning mechanism using SSL functionality.
1-
User intervention is not required to initiate or complete a profile update or
firmware upgrade. The Cisco IP phone upgrade logic is capable of automating
multi-stage upgrades, if intermediate upgrades are required to reach a future
upgrade state from an older release. A profile resync is only attempted when the
Cisco IP phone is idle, because this may trigger a software reboot.
General purpose parameters are provided to help service providers manage the
provisioning process. Each Cisco IP phone can be configured to periodically
contact a normal provisioning server (NPS). Communication with the NPS does not
require the use of a secure protocol because the updated profile is encrypted by
a shared secret key. The NPS can be a standard TFTP, HTTP or HTTPS server.
The administrator can upgrade, reboot, or resync Cisco IP phones using the web
interface.
Upgrading Firmware on a Phone
Use the upgrade URL to upgrade firmware on the Cisco IP phone. You can
upgrade from either a TFTP or HTTP server.
The Upgrade Enable parameter on the Provisioning web page must be set to Yes:
Cisco IP phone web UI:
Provisioning
>
Firmware Upgrade
>
Upgrade Enable: yes
Use the following syntax to upgrade firmware on a phone:
http://
phone-ip-address
/admin/upgrade?protocol://server-
name[:port]]/firmware-path
Protocol defaults to TFTP.
Server name is the host requesting the URL.
Port is the port of the protocol being used (for example, 69 for TFTP or 80
for HTTP).
F
irmware-path
defaults to /spa.bin (for example, http://192.168.2.217/
admin/upgrade?tftp://192.168.2.251/spa.bin) for SPA phones and /
wip310.img for the WIP310. The firmware-pathname is typically the file
name of the binary located in a directory on the TFTP or HTTP server.