Table of Contents
Advertisement
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
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:
<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):
[--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_.
2
46
Advertisement
Table of Contents
