Linksys SPA921 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 16

Redundant Provisioning Servers, Retail Provisioning

Get Linksys SPA921 - Cisco - IP Phone PDF manuals and user guides
UPC - 745883570799
View all Linksys SPA921 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 16 highlights

Provisioning Cisco Small Business VoIP Devices Provisioning Overview 1 The following is a sample template for an RC unit: Restricted Access Domains "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 IP Telephony Device 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 IP Telephony Device continues to process A-records until the first server responds. If no server associated with the A-records responds, the IP Telephony Device logs an error to the syslog server. Retail Provisioning The firmware for each IP Telephony Device includes an administration web server that displays the 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 Small Business 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 with an Internet Telephony Service Provider (ITSP). Subsequently, the customer binds the particular device to the assigned service account. Cisco Small Business IP Telephony Devices Provisioning Guide 14

  • 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
Provisioning Cisco Small Business VoIP Devices
Provisioning Overview
Cisco Small Business IP Telephony Devices Provisioning Guide
14
1
The following is a sample template for an RC unit:
Restricted Access Domains "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
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 IP Telephony Device 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 IP Telephony Device continues to
process A-records until the first server responds. If no server associated with the
A-records responds, the IP Telephony Device logs an error to the syslog server.
Retail Provisioning
The firmware for each IP Telephony Device includes an administration web server
that displays the 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 Small Business 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 with an Internet Telephony Service Provider (ITSP).
Subsequently, the customer binds the particular device to the assigned service
account.