Configuration File Components; Element Tag Properties - Cisco 6800 Series Provisioning Manual

Configuration File Components

XML Format (XML) Profile
The open format profile is a text file with XML-like syntax in a hierarchy of elements, with element attributes
and values. This format lets you use standard tools to create the configuration file. A configuration file in this
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 256-bit AES symmetric key encryption.
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.
Related Topics
Open Profile (XML) Compression and Encryption, on page 15
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
• The phone recognizes elements with proper parameter names that are encapsulated in the special
• 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
Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide
12
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 " ".
<flat-profile> element.
the following modifications:
Provisioning Scripts