With the new parameter settings, the phone resyncs twice a minute to the configuration file that the URL
specifies.
Step 5
Observe the resulting messages in the syslog trace (as described in the Use Syslog to Log Messages, on page
46 section).
Step 6
Ensure that the Resync On Reset field is set to Yes.
<Resync_On_Reset>Yes</Resync_On_Reset>
Step 7
Power cycle the phone to force it to resync to the provisioning server.
If the resync operation fails for any reason, such as if the server is not responding, the unit waits (for the
number of seconds configured in Resync Error Retry Delay) before it attempts to resync again. If Resync
Error Retry Delay is zero, the phone does not try to resync after a failed resync attempt.
Step 8
(Optional) Set the value of Resync Error Retry Delay field to a small number, such as 30.
<Resync_Error_Retry_Delay>30</Resync_Error_Retry_Delay>
Step 9
Disable the TFTP server, and observe the results in the syslog output.
Unique Profiles, Macro Expansion, and HTTP
In a deployment where each phone must be configured with distinct values for some parameters, such as
User_ID or Display_Name, the service provider can create a unique profile for each deployed device and host
those profiles on a provisioning server. Each phone, in turn, must be configured to resync to its own profile
according to a predetermined profile naming convention.
The profile URL syntax can include identifying information that is specific to each phone, such as MAC
address or serial number, by using the macro expansion of built-in variables. Macro expansion eliminates the
need to specify these values in multiple locations within each profile.
A profile rule undergoes macro expansion before the rule is applied to the phone. The macro expansion controls
a number of values, for example:
•
$MA expands to the unit 12-digit MAC address (using lower case hex digits). For example, 000e08abcdef.
•
$SN expands to the unit serial number. For example, 88012BA01234.
Other values can be macro expanded in this way, including all the general purpose parameters, GPP_A through
GPP_P. An example of this process can be seen in TFTP Resync, on page 45. Macro expansion is not limited
to the URL file name, but can also be applied to any portion of the profile rule parameter. These parameters
are referenced as $A through $P. For a complete list of variables that are available for macro expansion, see
Macro Expansion Variables, on page 67.
In this exercise, a profile specific to a phone is provisioned on a TFTP server.
Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide
48
Provisioning Examples
Unique Profiles, Macro Expansion, and HTTP
To Next Page
Loading...
Need help?
General
