Cisco SPA2102-AU Provisioning Guide - Page 14

Provisioning Overview Chapter 1 Provisioning Linksys VoIP Devices The following is a sample template for an RC unit: Restricted Access Domain "domain.com, domain1.com, domain2.com"; Primary_DNS * "x.y.w.z"; Secondary_DNS * "a.b.c.d"; Provision_Enable * "Yes"; Resync_Periodic * "30"; Resync_Error_Retry_Delay * "30"; Profile_Rule * "http://prov.domain.com/sipura/profile?id=$MA"; The Restricted Access Domain parameter is configured with the actual domain names of up to a maximum of five domains. The Primary_DNS and Secondary_DNS parameters are configured with the actual domain names or IP addresses of the DNS servers available to the RC unit. Redundant Provisioning Servers 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 SPA 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 SPA continues to process A-records until the first server responds. If no server associated with the A-records responds, the SPA logs an error to the syslog server. Retail Provisioning The SPA firmware includes an administration web server that displays SPA 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 Linksys 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 SPA 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/linksys-init/1234abcd In this example, 1234abcd is the PIN number of the new account. The remote provisioning server is configured to associate the SPA that is performing the resync request with the new account, based on the URL and the supplied PIN. Through this initial resync operation, the SPA 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/linksys For both initial and permanent access, the provisioning server relies on the SPA client certificate for authentication and supplies correct configuration parameter values based on the associated service account. Linksys SPA Provisioning Guide 1-4 Version 3.0