Redundant Provisioning Servers; Retail Provisioning - Cisco 521SG - Unified IP Phone VoIP Administration Manual

Provisioning

Redundant Provisioning Servers

Redundant Provisioning Servers

Retail Provisioning

Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide
Additional information is available in:
• Cisco SPA3xx, SPA50xG, and SPA525G SPC Templates for
Configuration Files, available on the Cisco Support Community at:
https://supportforums.cisco.com/docs/DOC-10008
• Cisco SPA9000 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 phone web user interface 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:
6
155