Cisco 521SG - Unified IP Phone VoIP Administration Manual page 164

Provisioning
Updating Profiles and Firmware
Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide
Parameter
Resync Error Retry Delay
Forced Resync Delay
Resync From SIP
Resync After Upgrade
Attempt
Resync Trigger 1
Resync Trigger 2
Resync Fails On FNF
Description
If a resync operation fails because the IP Telephony
device was unable to retrieve a profile from the
server, if the downloaded file is corrupt, or an
internal error occurs, the device tries to resync
again after a time specified in seconds.
If the delay is set to 0, the device does not try to
resync again following a failed resync attempt.
The resync typically takes place when the voice
lines are idle. When a voice line is active and a
resync is due, the IP Telephony device delays the
resync procedure until the line becomes idle.
However, it waits no longer than the Forced Resync
Delay (seconds). A resync might cause
configuration parameter values to change. This
causes a firmware reboot and terminates any voice
connection active at the time of the resync.
Controls requests for resync operations by using a
SIP NOTIFY event sent from the service provider
proxy server to the device. When set to yes, the
proxy can request a resync by sending a SIP
NOTIFY message containing the Event: resync
header to the device.
Requests a resync of the device after a failed
upgrade attempt.
A conditional expression (that undergoes macro
expansion). If the condition in one of these triggers
evaluates to true, a resync operation is initiated as
though the periodic resync timer had expired.
A resync is considered unsuccessful if a requested
profile is not received from the server. This can be
overridden by this parameter. When it is set to no,
the device accepts a file-not-found response
from the server as a successful resync.
6
163