Normal Provisioning Server; Phone Provisioning Practices; Onboard Your Phone With The Activation Code - Cisco 8800 Series Manual

Cisco IP Phone Provisioning
By default, a profile resync is only attempted when the phone is idle. This practice prevents an upgrade that
would trigger a software reboot and interrupt a call. If intermediate upgrades are required to reach a current
upgrade state from an older release, the upgrade logic can automate multistage upgrades.

Normal Provisioning Server

The Normal Provisioning Server (NPS) can be a TFTP, HTTP, or HTTPS server. A remote firmware upgrade
is achieved by using TFTP or HTTP, or HTTPS, because the firmware does not contain sensitive information.
Although HTTPS is recommended, communication with the NPS does not require the use of a secure protocol
because the updated profile can be encrypted by a shared secret key. For more information about utilizing
HTTPS, see
mechanism that uses SSL functionality. An unprovisioned phone can receive a 256-bit symmetric key encrypted
profile that is targeted for that device.

Phone Provisioning Practices

Typically, the Cisco IP Phone is configured for provisioning when it first connects to the network. The phone
is also provisioned at the scheduled intervals that are set when the service provider or the VAR preprovisions
(configures) the phone. Service providers can authorize VARs or advanced users to manually provision the
phone by using the phone keypad. You can also configure provisioning using the Phone Web UI.
Check the Status > Phone Status > Provisioning from the Phone LCD UI, or Provisioning Status in the
Status tab of the web-based Configuration Utility.

Onboard Your Phone with the Activation Code

This feature is available in firmware release 11-2-3MSR1, BroadWorks Application Server Release 22.0
(patch AP.as.22.0.1123.ap368163 and its dependencies). However, you can change phones with older firmware
to use this feature. You instruct the phone to upgrade to the new firmware and to use the
to trigger the activation code screen. A user enters a 16-digit code in the provided field to onboard the phone
automatically.
Before you begin
Ensure that you allow the activation.webex.com service through your firewall to support onboarding via
activation code.
Procedure
Step 1
Edit the phone config.xml file in a text or XML editor.
Step 2 Follow the example below in your config.xml file to set the profile rule for Activation Code Onboarding.
<?xml version="1.0" encoding="UTF-8"?>
<device>
<flat-profile>
<!-- System Configuration -->
<Profile_Rule ua="na">gds://</Profile_Rule>
<!--
<Upgrade_Enable ua="na">Yes</Upgrade_Enable>
<Upgrade_Error_Retry_Delay ua="na">3600</Upgrade_Error_Retry_Delay>
<Upgrade_Rule ua="na">http://<server ip address>/sip88xx.11-2-3MSR1-1.loads</Upgrade_Rule>
Communication Encryption, on page
Firmware Upgrade -->
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
31. Secure first-time provisioning is provided through a
Normal Provisioning Server
profile rule
gds://
25