Cisco SPA1112 - Page 17

Creating XML Provisioning Scripts
File Structure
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters 17
2
User, and Extension pages. Append [n] to the element name to indicate
the number that is shown in the page tab.
For example, the Dial Plan for Line 1 is represented by the element
<Dial_Plan[1]>
• Each opening element tag must be matched by a corresponding closing
element tag. For example:
<flat-profile>
<Resync_On_Reset> Yes
</Resync_On_Reset>
<Resync_Periodic> 7200
</Resync_Periodic>
<Profile_Rule>tftp://prov.telco.com: 6900/cisco/config/
spa962.cfg
</Profile_Rule>
</flat-profile>
• Element tags are case sensitive.
• Empty element tags are allowed. Enter the opening element tag without a
corresponding element tag, and insert a space and a forward slash before
the less-than symbol. In this example, Profile Rule B is empty:
<Profile_Rule_B />
• Unrecognized element names are ignored.
• An empty element tag can be used to prevent the overwriting of any user-
supplied values during a resync operation. In the following example, the
user speed dial settings are unchanged:
<Speed_Dial_2_2_ ua=”rw”/>
<Speed_Dial_3_2_ ua=”rw”/>
<Speed_Dial_4_2_ ua=”rw”/>
<Speed_Dial_5_2_ ua=”rw”/>
<Speed_Dial_6_2_ ua=”rw”/>
<Speed_Dial_7_2_ ua=”rw”/>
<Speed_Dial_8_2_ ua=”rw”/>
<Speed_Dial_9_2_ ua=”rw”/>
</flat-profile>