Cisco 7800 Series Administration Manual page 159

Parameter
Forced Resync Delay
Resync From SIP
Resync Trigger 1
Resync Trigger 2
Resync Fails On FNF
Profile Rule Profile Rule B Profile
Rule C Profile Rule D
Resync Option To Use
Log Request Msg
Log Success Msg
Description
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.
Default: 14400
Controls requests for resync operations via a SIP NOTIFY event sent
from the service provider proxy server to the IP Telephony device. If
enabled, the proxy can request a resync by sending a SIP NOTIFY
message containing the Event: resync header to the device.
Default: Yes
Configurable resync trigger conditions. A resync is triggered when the
logic equation in these parameters evaluates to TRUE.
Default: Blank
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
as a successful resync.
Default: Yes
Remote configuration profile rules evaluated in sequence. Each resync
operation can retrieve multiple files, potentially managed by different
servers.
Default: /$PSN.xml
DHCP options, delimited by commas, used to retrieve firmware and
profiles.
Default: 160,159,66,150
The message sent to the syslog server at the start of a resync attempt.
Default:
$PN $MAC –Requesting % $SCHEME://$SERVIP:$PORT$PATH
The syslog message issued upon successful completion of a resync
attempt.
Default:
$PN $MAC –Successful % $SCHEME://$SERVIP:$PORT$PATH -- $ERR
Cisco IP Phone 7800 Series for Third-Party Call Control Administration Guide
Cisco IP Phone Web Page
response from the server
file-not-found
145