Cisco SPA901-UK Provisioning Guide - Page 66

Automatic Resync, Log_Resync_Request_Msg

Get Cisco SPA901-UK - Small Business Pro PDF manuals and user guides
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals

Page 66 highlights

Provisioning Tutorial Basic Resync 3 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. STEP 4 Verify that your syslog server received messages such as the following: 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. Cisco Small Business IP Telephony Devices Provisioning Guide 65

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
Provisioning Tutorial
Basic Resync
Cisco Small Business IP Telephony Devices Provisioning Guide
65
3
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.
STEP 4
Verify that your syslog server received messages such as the following:
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.