Table of Contents
Advertisement
Provisioning Tutorial
Basic Resync
Cisco Small Business IP Telephony Devices Provisioning Guide
Several other values can be macro expanded in this way, including all the general
purpose parameters, (GPP_A through GPP_P) These can be referenced as $A
through $P. Macro expansion is not limited to the URL file name, but can also be
applied to any portion of the profile rule parameter.
For a complete list of variables available for macro expansion, see the
Expansion Variables" section on page
URL Resolution
The profile URL can contain a provisioning server name instead of an explicit IP
address. In this case, the IP Telephony Device performs a DNS lookup to resolve
the name.
A non-standard server port can be specified in the URL, using the standard syntax
:port following the server name.
Also, the configuration profile can be stored in a subdirectory of the server virtual
root directory. Again, this is specified using standard URL notation.
For example, the following is a valid Profile_Rule that requests the file spa962.cfg,
in the server subdirectory /cisco/config, for the TFTP server running on host
prov.telco.com, which listens for connection on port 6900.
tftp://prov.telco.com:6900/cisco/config/spa962.cfg
Again, macro expansion can be used anywhere in the URL. This can be convenient
in organizing a directory of profiles on the server for the deployed devices. For
example, a profile subdirectory name might be supplied for each IP Telephony
Device in a dedicated general purpose parameter, with its value referred within a
common profile rule via macro expansion.
For example, GPP_B has the following definition:
Dj6Lmp23Q
The Profile_Rule has this value:
tftp://prov.telco.com/cisco/$B/$MA.cfg
Then, when resyncing, this IP Telephony Device (assuming a MAC address of
000e08012345) requests the profile at the following URL:
tftp://prov.telco.com/cisco/Dj6Lmp23Q/000e08012345.cfg
89.
3
"Macro
68
Advertisement
Table of Contents
