Cisco WRP400-G1 Administration Guide - Page 22

XML Format, Binary Format, Product Overview and Deployment Guidelines, Appendix C

Get Cisco WRP400-G1 - Wireless Router PDF manuals and user guides
UPC - 745883580958
View all Cisco WRP400-G1 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

Product Overview and Deployment Guidelines Remote Provisioning 1 XML Format Use the XML format for data (router) parameters. The XML file consists of a series of elements (one per configuration parameter), encapsulated within the element tags ... . The encapsulated elements specify values for individual parameters. Here is an example of a valid XML profile: some secret Yes The names of parameters in XML profiles can generally be inferred from the WRP400 Configuration Utility, by substituting underscores (_) for spaces and other control characters. To distinguish between Lines 1, 2, 3, and 4, corresponding parameter names are augmented by the strings _1_, _2_, _3_, and _4_. For example, Line 1 Proxy is named Proxy_1_ in XML profiles. For more information, see Appendix C, "WRP400 Provisioning Reference." Binary Format Binary format profiles contain voice parameter values and user access permissions for the parameters. By convention, the profile uses the extension .cfg (for example, spa2102.cfg). The Profile Compiler (SPC) tool compiles a plain-text file containing parameter-value pairs into a properly formatted and encrypted .cfg file. The syntax of the plain-text file accepted by the profile compiler is a series of parameter-value pairs, with the value in double quotes. Each parameter-value pair is followed by a semicolon. Here is an example of a valid text source profile for input to the SPC tool: Admin_Passwd "some secret"; Upgrade_Enable "Yes"; The names of parameters in the source text files for the SPC tool can generally be inferred from the WRP400 Configuration Utility, by substituting underscores (_) for spaces and other control characters. To distinguish between Line 1, 2, 3, and 4, corresponding parameter names are augmented by adding [1], [2], [3], or [4]. For example, the Line 1 Proxy is named Proxy[1] in source text profiles for input to the SPC. Cisco Small Business WRP400 Administration Guide 20

  • 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
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
Product Overview and Deployment Guidelines
Remote Provisioning
Cisco Small Business WRP400 Administration Guide
20
1
XML Format
Use the XML format for data (router) parameters. The XML file consists of a series
of elements (one per configuration parameter), encapsulated within the element
tags <flat-profile> … </flat-profile>. The encapsulated elements specify values for
individual parameters. Here is an example of a valid XML profile:
<flat-profile>
<Admin_Passwd>some secret</Admin_Passwd>
<Upgrade_Enable>Yes</Upgrade_Enable>
</flat-profile>
The names of parameters in XML profiles can generally be inferred from the
WRP400 Configuration Utility, by substituting underscores (_) for spaces and other
control characters. To distinguish between Lines 1, 2, 3, and 4, corresponding
parameter names are augmented by the strings _1_, _2_, _3_, and _4_. For
example, Line 1 Proxy is named Proxy_1_ in XML profiles. For more information,
see
Appendix C, “WRP400 Provisioning Reference.”
Binary Format
Binary format profiles contain voice parameter values and user access
permissions for the parameters. By convention, the profile uses the extension .cfg
(for example, spa2102.cfg). The Profile Compiler (SPC) tool compiles a plain-text
file containing parameter-value pairs into a properly formatted and encrypted .cfg
file.
The syntax of the plain-text file accepted by the profile compiler is a series of
parameter-value pairs, with the value in double quotes. Each parameter-value pair
is followed by a semicolon. Here is an example of a valid text source profile for
input to the SPC tool:
Admin_Passwd
“some secret”;
Upgrade_Enable “Yes”;
The names of parameters in the source text files for the SPC tool can generally be
inferred from the WRP400 Configuration Utility, by substituting underscores (_) for
spaces and other control characters. To distinguish between Line 1, 2, 3, and 4,
corresponding parameter names are augmented by adding [1], [2], [3], or [4]. For
example, the Line 1 Proxy is named Proxy[1] in source text profiles for input to the
SPC.