Cisco SPA901-UK Provisioning Guide - Page 39
Source Text Syntax, <Resync_On_Reset>, <Dial_Plan[1]>
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 39 highlights
Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 Source Text Syntax The syntax of the plain-text file accepted by SPC is a series of parameter-value pairs, with the value enclosed in double quotes. Each parameter-value pair is followed by a semicolon (for example, parameter_name "parameter_value";). If no quoted value is specified for a parameter (or if a parameter specification is missing entirely from the plain-text file) the value of the parameter remains unchanged in the IP Telephony device. The syntax also controls the User account access to the parameter in the administration web server. An optional exclamation point or question mark, immediately following the parameter name, indicates the parameter should be read-write (!) or user read-only (?) for the User account. If neither mark is present, the parameter is made inaccessible to the user from the web server pages. Note that this syntax has no effect on the Admin account access to the parameter. If the parameter specification is missing entirely from the plain-text file, the User account access to the parameter remains unchanged in the IP Telephony device. If the plain-text file contains multiple occurrences of the same parameter-value specification, the last occurrence overrides any earlier ones. To avoid accidentally overwriting configuration values, it is recommended that a profile includes no more than one specification for each parameter. The element names derive from the field names in the administration web pages for the device, with the following modifications: • Element names may not include spaces or special characters. To derive the element name from the field name, substitute an underscore for spaces or the following special characters: [ ] ( ) / For example, the Resync On Reset field is represented by the following element: • Each element name must be unique. For fields that are duplicated on multiple Line, User, or Extension pages, you must append [n] to indicate the line, user, or extension number. For example, the Dial Plan for Line 1 is represented by the following element: Cisco Small Business IP Telephony Devices Provisioning Guide 38