In-House Device Preprovisioning - Cisco 6800 Series Provisioning Manual

In-House Preprovisioning and Provisioning Servers

In-House Device Preprovisioning

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.
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.
Once the phone has been provisioned, the Cisco EDOS RC Server is not utilized unless the phone is factory
reset.
In-House Device Preprovisioning
With the Cisco factory default configuration, the phone automatically tries to resync to a profile on a TFTP
server. A managed DHCP server on a LAN delivers the information about the profile and TFTP server that
is configured for preprovisioning to the device. The service provider connects each new phone to the LAN.
Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide
37