Provisioning
At a high level, the phone provisioning process is as follows:
1. If the phone is not configured, the provisioning server information is applied to the phone using one of
the following options:
2. The phone downloads the provisioning server information and applies the configuration XML using the
HTTPS, HTTP, or TFTP protocol.
3. The phone downloads and applies the updated firmware, if needed, using HTTPS, HTTP, or TFTP.
4. The VoIP service is established using the specified configuration and firmware.
VoIP service providers intend to deploy many phones to residential and small business customers. In business
or enterprise environments, phones can serve as terminal nodes. Providers widely distribute these devices
across the Internet, which are connected through routers and firewalls at the customer premises.
The phone can be used as a remote extension of the service provider back-end equipment. Remote management
and configuration ensure the proper operation of the phone at the customer premises.
Provisioning
A phone can be configured to resynchronize its internal configuration state to match a remote profile periodically
and on power-up. The phone contacts a normal provisioning server (NPS) or an access control server (ACS).
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
24
• A–Downloaded from the Cisco Enablement Data Orchestration System (EDOS) Remote Customization
(RC) server using HTTPS, DNS SRV, GDS (Activation code onboarding), EDOS device activation.
• B–Queried from a local DHCP server.
• C–Entered manually using the Cisco phone web-based configuration utility or Phone UI.
Cisco IP Phone Provisioning