You can customize your users' phones remotely. You don't need to physically touch the phone and your users don't need to configure their phones. You can work with a sales engineer at order time to set up remote customization.
If you purchase your phones from a distributor, you need to contact Cisco Small Business Support Center to upload the phone MAC addresses to the Cisco Cloud server. For cloud provisioning feature, you need to selected a correct RC SKU before you place an order and also you need to have a profile setup in Cisco Cloud server that contains the provisioning server information. When a user connects a new phone to the network for the first time, the phone tries the DHCP options (160,159,66,150) to get the provisioning and configuration information. If this information is not set up or available, the phone attempts to connect to the Cisco Cloud server to retrieve its profile and find its provisioning server. If the profile is set up correctly when the phones are ordered, the phone is able to register without any manual user intervention.
In the System Status
tab, you find the current remote customization status. If the System Status
tab shows Pending or Custom-Pending states and provisioning resynchronization is failing, the Download Status
tab contains the status in the Provisioning Status
section. The following is a brief description about the various remote customization states that are displayed on the web interface:
Open—The phone has booted for the first time and is not configured.
Aborted—Remote customization using DHCP options has aborted.
Pending—The profile has been downloaded from the EDOS server.
Custom-Pending—The phone has downloaded a redirect URL from the EDOS server.
Acquired—In the profile downloaded from the EDOS server, there is a redirect URL for provision configuration. If the redirect URL download from the provisioning server is successful, this state is displayed.
Unavailable—Remote customization has stopped because the EDOS server responded with an empty provisioning file and the HTTP response was 200 OK.