Provisioning Overview - Cisco SPA1112 Provisioning Manual

Deployment and Provisioning

Provisioning Overview

Provisioning Overview
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters
Resynchronization Process
The firmware for each ATA includes an administration web server that accepts
new configuration parameter values. The ATA is instructed to resync with a
specified provisioning server through a resync URL command in the device
profile. The URL command typically includes an account PIN number or
alphanumeric code to associate the device with the new account. For example:
http://192.168.1.102/admin/resync?https://prov.supervoip.com/cisco-init/
1234abcd
In this example, a device at the DHCP-assigned IP address 192.168.1.102 is
instructed to provision itself to the SuperVoIP service at prov.supervoip.com.
The PIN number for the new account is 1234abcd. The remote provisioning server
is configured to associate the ATA that is performing the resync request with the
new account, based on the URL and PIN.
Through this initial resync operation, the ATA is configured in a single step, and is
automatically directed to resync thereafter to a permanent URL on the server.
For both initial and permanent access, the provisioning server relies on the client
certificate for authentication and supplies configuration parameter values based
on the associated service account.
An IP Telephony device can be configured to resynchronize its internal
configuration state to match a remote profile periodically and on power up by
contacting a normal provisioning server (NPS) or an access control server (ACS).
By default, a profile resync is only attempted when the IP Telephony device is idle,
because the upgrade might trigger a software reboot interrupting a call. If
intermediate upgrades are required to reach a current upgrade state from an older
release, the upgrade logic is capable of automating multi-stage upgrades.
NPS
The NPS can be a TFTP, HTTP, or HTTPS server. A remote firmware upgrade is
achieved by using TFTP or HTTP, but not by using HTTPS because the firmware
does not contain sensitive information.
1
9