Provisioning Server Setup; Tftp Provisioning; Remote Endpoint Control And Nat - Cisco 6800 Series Provisioning Manual

Provisioning Server Setup

The phone automatically resyncs to the local TFTP server and initializes its internal state in preparation for
deployment. This preprovisioning profile typically includes the URL of a remote provisioning server. The
provisioning server keeps the device updated after the device is deployed and connected to the customer
network.
The preprovisioned device bar code can be scanned to record its MAC address or serial number before the
phone is shipped to the customer. This information can be used to create the profile to which the phone
resynchronizes.
Upon receiving the phone, the customer connects it to the broadband link. On power-up, the phone contacts
the provisioning server through the URL that is configured through preprovisioning. The phone can thus
resync and update the profile and firmware, as necessary.
Related Topics
Retail Distribution, on page 6
TFTP Provisioning, on page 38
Provisioning Server Setup
This section describes setup requirements for provisioning a phone by using various servers and different
scenarios. For the purposes of this document and for testing, provisioning servers are installed and run on a
local PC. Also, generally available software tools are useful for provisioning the phones.

TFTP Provisioning

The phones support TFTP for both provisioning resync and firmware upgrade operations. When devices are
deployed remotely, HTTPS is recommended, but HTTP and TFTP can also be used. This then requires
provisioning file encryption to add security, as it offers greater reliability, given NAT and router protection
mechanisms. TFTP is useful for the in-house preprovisioning of a large number of unprovisioned devices.
The phone is able to obtain a TFTP server IP address directly from the DHCP server through DHCP option
66. If a Profile_Rule is configured with the filepath of that TFTP server, the device downloads its profile from
the TFTP server. The download occurs when the device is connected to a LAN and powered up.
The Profile_Rule provided with the factory default configuration is $PN.cfg, where $PN represents the phone
model name.
For example, for a CP-6841-3PCC, the filename is CP-6841-3PCC.cfg.
For a device with the factory default profile, upon powering up, the device resyncs to this file on the local
TFTP server that DHCP option 66 specifies. The filepath is relative to the TFTP server virtual root directory.
Related Topics
In-House Device Preprovisioning, on page 37

Remote Endpoint Control and NAT

The phone is compatible with network address translation (NAT) to access the Internet through a router. For
enhanced security, the router might attempt to block unauthorized incoming packets by implementing symmetric
NAT, a packet-filtering strategy that severely restricts the packets that are allowed to enter the protected
network from the Internet. For this reason, remote provisioning by using TFTP is not recommended.
Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide
38
In-House Preprovisioning and Provisioning Servers