Table of Contents
Advertisement
Provisioning Tutorial
Profile Formats
STEP 5
STEP 6
STEP 1
STEP 2
STEP 3
STEP 4
Cisco Small Business IP Telephony Devices Provisioning Guide
Click Submit All Changes.
When the IP Telephony Device resyncs, it receives the XML profile, remaps the
elements, as indicated by the alias map, and populates the User_ID_1_ and
Password_1_ parameters.
View the Line 1 tab to verify the new configuration.
The IP Telephony Device supports alias remapping of a limited
NOTE
number of parameters. It is not meant to rename all parameters in its
configuration.
Proprietary Profile Format
Firmware releases prior to 2.0.6 do not recognize the XML-based profiles
described so far in this chapter. Instead, the SIP Profiler Compiler tool (SPC)
converts a text-based profile definition into a proprietary binary format
understood by earlier versions of the firmware. The tool provides its own options
for encrypting the resulting binary profile.
The text-based profile understood by SPC uses a different syntax from the XML
profile presented earlier. It consists of a list of parameter-value pairs, with the value
in double quotes. Other minor syntax and parameter naming differences also
apply. The following example specifies values for two Line 1 parameters:.
Exercise
Obtain the SPC utility from Cisco.
Executables are available for the Windows Win32 environment, Linux ELF, and
OpenBSD.
Generate the text profile account.txt containing the two-line profile shown in the
following example:
User_ID[1] "17775551234" ;
Password[1] "512835907884" ;
Compile the text profile into a binary file, account.cfg by using the following
command:
spc account.txt account.cfg
Store account.cfg in the TFTP server virtual root directory.
3
79
Advertisement
Table of Contents
