Linksys SPA2102-AU Provisioning Manual page 30

Open Format Configuration File
</flat-profile>
The element names that are recognized by the SPA can be derived from the SPA administration web
server field names as follows:
•
Append [n] to each of the numbered parameters, where n is the line, user, or extension number (for
example Dial_Plan[1] and Dial_Plan[2]).
•
Replace spaces plus any of the following special characters with underscores:
–
This is illustrated by
attribute.
Example 2-4
<flat-profile>
<!-- This sets the SIP TOS/DiffServ Value[1] parameter to be user not-accessible -->
<SIP_TOS_DiffServ_Value_1_
<!-- This sets the Dial Plan[1] parameter to be user read-only -->
<Dial_Plan_1_
<!-- This sets Dial Plan[2] parameter to be user read-write -->
<Dial_Plan_2_
</flat-profile>
The SPA processes empty elements and elements with empty values differently. If an element tag is
specified within an empty element form, than the current value of the corresponding parameter is left
unchanged. On the other hand, if the element tag is used within an opening and a closing element, with
no value between them, then the corresponding parameter is set to an empty string. This is illustrated in
Example
Example 2-5
<flat-profile>
<!-- GPP_A will be set to an empty string -->
<GPP_A>
</GPP_A>
<!-- GPP_B will remain unchanged -->
<GPP_B/>
</flat-profile>
Using the empty element form is useful when specifying a read/write parameter (ua=rw). This allows
the end user to set and maintain specific values (such as User 1 and User 2 settings), while preventing
the profile from overwriting the user-supplied values during a resync operation.
Example 2-6
<flat-profile>
<!-- End-user manages these parameters, values are not changed by this profile -->
Linksys SPA Provisioning Guide
2-4
[ ] ( ) /
Example 2-4, which also illustrates setting user access privileges, using the ua
Using Numbers and Spaces in an XML Profile
ua="ro"/>
ua="rw"/>
2-5.
Empty Elements vs. Empty Strings
Empty Elements Preserve User-Configured Values
ua="na"/>
Chapter 2 Creating Provisioning Scripts
Version 3.0