Table of Contents
Advertisement
Provisioning Tutorial
Basic Resync
STEP 4 Verify that your syslog server received messages such as the following:
Cisco Small Business IP Telephony Devices Provisioning Guide
The device generates two syslog messages during the resync. The first indicates
that a request is in progress. The second marks success or failure of the resync.
SPA-962 00:0e:08:ab:cd:ef –- Requesting resync tftp://192.168.1.200/basic.txt
SPA-962 00:0e:08:ab:cd:ef –- Successful resync tftp://192.168.1.200/basic.txt
More detailed messages are available by programming the Debug_Server
parameter (instead of the Syslog_Server parameter) with the IP address of the
syslog server, and setting the Debug_Level to a value between 0 and 3 (3 being
the most verbose).
The contents of these messages can be configured using the following
parameters:
•
Log_Resync_Request_Msg
•
Log_Resync_Success_Msg
•
Log_Resync_Failure_Msg.
If any of these parameters are cleared, the corresponding syslog message is not
generated.
Occasionally, it may also be informative to capture an Ethernet packet trace of the
interaction between the IP Telephony Device and the provisioning server. You can
run the Ethernet packet analyzer (such as Ethereal/Wireshark) on a PC that is
connected, through a hub or through a switch with port mirroring enabled, to the
same subnet as the IP Telephony Device.
Automatic Resync
When a IP Telephony Device is deployed remotely or as part of an internal
company deployment, it may need to resync periodically to the provisioning
server, to ensure that any customer profile configuration changes made on the
server are propagated to the endpoint, without requiring an explicit resync request
to the endpoint.
To cause the IP Telephony Device to automatically and periodically resync to a
server, a configuration profile URL is defined using the Profile_Rule parameter, and
a resync period is defined using the Resync_Periodic parameter.
3
65
Advertisement
Table of Contents
