Remote Customization (Rc) Distribution - Cisco 8800 Series Manual

Hide thumbs Also See for 8800 Series:
Table of Contents

Advertisement

Cisco IP Phone Provisioning

Remote Customization (RC) Distribution

Remote Customization (RC) Distribution
All phones contact the Cisco EDOS RC server until they are provisioned initially.
In an RC distribution model, a customer purchases a phone that has already been associated with a specific
Service Provider in the Cisco EDOS RC Server. The Internet Telephony Service Provider (ITSP) sets up and
maintains a provisioning server, and registers their provisioning server information with the Cisco EDOS RC
Server.
When the phone is powered on with an internet connection, the customization state for the unprovisioned
phone is Open. The phone first queries the local DHCP server for provisioning server information and sets
the customization state of the phone. If DHCP query is successful, Customization State is set to Aborted and
RC is not attempted due to DHCP providing the needed provisioning server information.
When a phone connects to a network for the first time or after a factory reset, if there are no DHCP options
setup, it contacts a device activation server for zero touch provisioning. New phones will use
"activate.cisco.com" instead of "webapps.cisco.com" for provisioning. Phones with firmware release prior
to 11.2(1), will continue to use webapps.cisco.com. Cisco recommends that you allow both the domain names
through your firewall.
If DHCP server does not provide provisioning server information, the phone queries the Cisco EDOS RC
Server and provides its MAC address and model and the Customization State is set to Pending. The Cisco
EDOS server responds with the associated service provider's provisioning server information including
provisioning server URL and the phone's Customization State is set to Custom Pending. The phone then
performs a resync URL command to retrieve the Service Provider's configuration and, if successful, the
Customization State is set to Acquired.
If the Cisco EDOS RC Server does not have a service provider associated with the phone, the customization
state of the phone is set to Unavailable. The phone can be manually configured or an association added for
the service provider of the phone to the Cisco EDOS Server.
If a phone is provisioned via either the LCD or Web Configuration Utility, prior to the Customization State
becoming Acquired, the Customization State is set to Aborted and the Cisco EDOS Server will not be queried
unless the phone is factory reset.
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
33

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

885188618865

Table of Contents