Cisco SPA901-UK Provisioning Guide - Page 47

translations, assigning J. Smith to Display_Name_1_, 14085551234 to User_ID_1, alias

Get Cisco SPA901-UK - Small Business Pro PDF manuals and user guides
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 For example, GPP_F could contain the following POST body template: Product = "$PN"; MAC_Addr = "$MA"; Ser_Num = "$SN"; SW_Ver = "$SWVER"; Then, a URL option uses the POST method to convey the information to the server in the body of the profile request message (shown here with an accompanying URL): [--post f ] http://ps.one.com/cpe/resyncs? alias The alias option provides a flexible means of recognizing alternative parameter names in XML-based configuration profiles. This is useful in cases where part of the configuration profile is obtained from a customer database form that uses different terminology than expected by the IP Telephony device. For example, a customer XML profile specifies the SIP registration parameters: name, number, auth-secret, enclosed in an XML element hierarchy as follows: J. Smith 14085551234 732091751563sfd To map these three parameters directly to the 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 IP Telephony device would apply the indicated translations, assigning J. Smith to Display_Name_1_, 14085551234 to User_ID_1_, and 732091751563sfd to Password_1_. Cisco Small Business IP Telephony Devices Provisioning Guide 46

  • 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
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
46
2
For example, GPP_F could contain the following POST body template:
Product = “$PN”; MAC_Addr = “$MA”; Ser_Num = “$SN”; SW_Ver = “$SWVER”;
Then, a URL option uses the POST method to convey the information to the server
in the body of the profile request message (shown here with an accompanying
URL):
alias
The
alias
option provides a flexible means of recognizing alternative parameter
names in XML-based configuration profiles. This is useful in cases where part of
the configuration profile is obtained from a customer database form that uses
different terminology than expected by the IP Telephony device.
For example, a customer XML profile specifies the SIP registration parameters:
name, number, auth-secret, enclosed in an XML element hierarchy as follows:
<CPE>
<SIP-Credentials>
<name>J. Smith</name>
<number>14085551234</number>
<auth-secret>732091751563sfd</auth-secret>
<SIP-Credentials>
</CPE>
To map these three parameters directly to the 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 IP Telephony device would apply the indicated
translations, assigning J. Smith to Display_Name_1_, 14085551234 to User_ID_1_,
and 732091751563sfd to Password_1_.