Cisco Ip Phone 8800 Series Multiplatform Phones Administration Guide - Cisco 8851 Administration Manual

Parameter
Forced Resync Delay
Resync From SIP
Resync After Upgrade Attempt
Resync Trigger 1
Resync Trigger 2
Resync Fails On FNF
Profile Rule
Profile Rule B
Profile Rule C
Profile Rule D
DHCP Option To Use
DHCPv6 Option To Use
Description
Forced resync delay typically takes place when it is time to a resync
and you are in an active call. For example, if you set 5 minute for
Periodic Resync and you place a call right after the resync, the resync
happens while you are 6 minutes into the call (normal time of Resync
+ Forced Resync Delay).
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
Enables or disables the resync operation after any upgrade occurs. If
Yes is selected, sync is triggered.
Default: Yes
If the logical equation in these parameters evaluates to FALSE, Resync
is not triggered even when Resync On Reset is set to TRUE. Only
Resync via direct action URL and SIP notify ignores these Resync
Trigger.
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: 66,160,159,150,60,43,125
DHCP options, delimited by commas, used to retrieve firmware and
profiles.
Default: 17,160,159

Cisco IP Phone 8800 Series Multiplatform Phones Administration Guide

Cisco IP Phone Web Page
response from the server
file-not-found
231