Cisco SPA2102-AU Provisioning Guide - Page 30

Using Numbers and Spaces in an XML Profile, example Dial_Plan[1] and Dial_Plan[2]. - dial plan

Get Cisco SPA2102-AU PDF manuals and user guides View all Cisco SPA2102-AU manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

Open Format Configuration File Chapter 2 Creating Provisioning Scripts 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 Example 2-4, which also illustrates setting user access privileges, using the ua attribute. Example 2-4 Using Numbers and Spaces in an XML 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 2-5. Example 2-5 Empty Elements vs. Empty Strings 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 Empty Elements Preserve User-Configured Values Linksys SPA Provisioning Guide 2-4 Version 3.0

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
2-4
Linksys SPA Provisioning Guide
Version 3.0
Chapter 2
Creating Provisioning Scripts
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
Example 2-4
, which also illustrates setting user access privileges, using the ua
attribute.
Example 2-4
Using Numbers and Spaces in an XML Profile
<flat-profile>
<!-- This sets the SIP TOS/DiffServ Value[1] parameter to be user not-accessible -->
<SIP_TOS_DiffServ_Value_1_
ua=”na”/>
<!-- This sets the Dial Plan[1] parameter to be user read-only -->
<Dial_Plan_1_
ua=”ro”/>
<!-- This sets Dial Plan[2] parameter to be user read-write -->
<Dial_Plan_2_
ua=”rw”/>
</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 2-5
.
Example 2-5
Empty Elements vs. Empty Strings
<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
Empty Elements Preserve User-Configured Values
<flat-profile>
<!-- End-user manages these parameters, values are not changed by this profile -->