Redundant Provisioning Servers; Retail Provisioning - Cisco Small Business SPA509G Administration Manual

Provisioning Basics

Redundant Provisioning Servers

Redundant Provisioning Servers

Retail Provisioning

Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide
The provisioning server may be specified as an IP address or as a fully qualified
domain name (FQDN). The use of a FQDN facilitates the deployment of redundant
provisioning servers. When the provisioning server is identified through a FQDN,
the Cisco IP phone attempts to resolve the FQDN to an IP address through DNS.
Only DNS A-records are supported for provisioning; DNS SRV address resolution
is not available for provisioning. The Cisco IP phone continues to process A-
records until the first server responds. If no server associated with the A-records
responds, the Cisco IP phone logs an error to the syslog server.
The Cisco IP phone includes the web-based configuration utility 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. 1 68. 1 . 1 02
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
6
175