Cisco SPA2102-AU Provisioning Guide - Page 40

Combining Options, Using Provisioning Parameters

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 40 highlights

Using Provisioning Parameters Chapter 2 Creating Provisioning Scripts To map these three parameters directly to the SPA Display_Name_1_, User_ID_1_, and Password_1_ parameters (Line 1), enter this mapping in a general purpose parameter (for example, GPP_M): /CPE/SIP-Credentials/name = /flat-profile/Display_Name_1_ ; /CPE/SIP-Credentials/number = /flat-profile/User_ID_1_ ; /CPE/SIP-Credentials/auth-secret = /flat-profile/Password_1_ ; Then, request the customer credentials profile with the following URL option (showing an example URL for completeness): [--alias m ] http://acct.voipservice.net/credentials/spa$MA.xml Upon receiving the profile, the SPA would apply the indicated translations, assigning J. Smith to Display_Name_1_, 14085551234 to User_ID_1_, and 732091751563sfd to Password_1_. The alias option matches only the left-hand-side of an alias as much as specified by the configured alias map. The element itself can be nested further. In the example above, GPP_M could have contained the following instead: /SIP-Credentials/name = /flat-profile/Display_Name_1_ ; /SIP-Credentials/number = /flat-profile/User_ID_1_ ; /auth-secret = /flat-profile/Password_1_ ; In general, it is best to specify enough enclosing elements to ensure an unambiguous translation. The alias option is designed to recognize a limited number of critical parameters. Up to 30 parameters can be remapped this way. Combining Options Multiple URL options can be combined, by enclosing them within the same set of square brackets. The following are examples of valid URL option strings: [--post j --alias k] [--key "SymmetricSecret" --alias a] [--key "$SB" --post g] [--alias a --key abracadabra321 --post c] Using Provisioning Parameters This section describes the provisioning parameters broadly organized according to function. It includes the following topics: • General Purpose Parameters, page 2-15 • Enables, page 2-15 • Triggers, page 2-16 • Configurable Schedules, page 2-16 • Profile Rules, page 2-17 • Report Rule, page 2-19 • Upgrade Rule, page 2-19 2-14 Linksys SPA Provisioning Guide 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-14
Linksys SPA Provisioning Guide
Version 3.0
Chapter 2
Creating Provisioning Scripts
Using Provisioning Parameters
To map these three parameters directly to the SPA Display_Name_1_, User_ID_1_, and Password_1_
parameters (Line 1), enter this mapping in a general purpose parameter (for example, GPP_M):
/CPE/SIP-Credentials/name = /flat-profile/Display_Name_1_ ;
/CPE/SIP-Credentials/number = /flat-profile/User_ID_1_ ;
/CPE/SIP-Credentials/auth-secret = /flat-profile/Password_1_ ;
Then, request the customer credentials profile with the following URL option (showing an example URL
for completeness):
Upon receiving the profile, the SPA would apply the indicated translations, assigning J. Smith to
Display_Name_1_, 14085551234 to User_ID_1_, and 732091751563sfd to Password_1_.
The
alias
option matches only the left-hand-side of an alias as much as specified by the configured alias
map. The element itself can be nested further. In the example above, GPP_M could have contained the
following instead:
/SIP-Credentials/name = /flat-profile/Display_Name_1_ ;
/SIP-Credentials/number = /flat-profile/User_ID_1_ ;
/auth-secret = /flat-profile/Password_1_ ;
In general, it is best to specify enough enclosing elements to ensure an unambiguous translation.
The
alias
option is designed to recognize a limited number of critical parameters. Up to 30 parameters
can be remapped this way.
Combining Options
Multiple URL options can be combined, by enclosing them within the same set of square brackets. The
following are examples of valid URL option strings:
[--post j --alias k]
[--key “SymmetricSecret” --alias a]
[--key “$SB” --post g]
[--alias a --key abracadabra321 --post c]
Using Provisioning Parameters
This section describes the provisioning parameters broadly organized according to function. It includes
the following topics:
•
General Purpose Parameters, page 2-15
•
Enables, page 2-15
•
Triggers, page 2-16
•
Configurable Schedules, page 2-16
•
Profile Rules, page 2-17
•
Report Rule, page 2-19
•
Upgrade Rule, page 2-19