format can be sent from the provisioning server to the phone during a resync operation. The file can be sent
without compilation as a binary object.
The phone can accept configuration formats that standard tools generate. This feature eases the development
of back-end provisioning server software that generates configuration profiles from existing databases.
To protect confidential information in the configuration profile, the provisioning server delivers this type of
file to the phone over a channel secured by TLS. Optionally, the file can be compressed by using the gzip
deflate algorithm (RFC1951).
The file can be encrypted with one of these encryption methods:
• AES-256-CBC encryption
• RFC-8188 based HTTP content encryption with AES-128-GCM ciphering
Example: Open Profile Format
<flat-profile>
<Resync_On_Reset> Yes </Resync_On_Reset>
<Resync_Periodic> 7200 </Resync_Periodic>
<Profile_Rule> tftp://prov.telco.com:6900/cisco/config/CP_xxxx_MPP.cfg</Profile_Rule>
</flat-profile>
The <flat-profile> element tag encloses all parameter elements that the phone recognizes.
Configuration File Components
A configuration file can include these components:
• Element tags
• Attributes
• Parameters
• Formatting features
• XML comments
Element Tag Properties
• The XML provisioning format and the Web UI allow the configuration of the same settings. The XML
tag name and the field names in the Web UI are similar but vary due to XML element name restrictions.
For example, underscores (_) instead of " ".
• The phone recognizes elements with proper parameter names that are encapsulated in the special
<flat-profile> element.
• Element names are enclosed in angle brackets.
• Most element names are similar to the field names in the administration web pages for the device, with
the following modifications:
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
78
Cisco IP Phone Provisioning
Configuration File Components
To Next Page
Loading...
Need help?
General
