Cisco 8800 Series, Manual

Page: 72 / 544

Description Parameter
Controls requests for resync operations via a SIP NOTIFY event sent from the service
provider proxy server to the phone. If enabled, the proxy can request a resync by
sending a SIP NOTIFY message containing the Event: resync header to the device.
• In the phone configuration file (cfg.xml) with XML , enter a string in this format:
<Resync_From_SIP ua="na">Yes</Resync_From_SIP>
• On the phone web page , select Yes to enable this feature, or No to disalbe it.
Default: Yes
Resync From SIP
Enables or disables the resync operation after any upgrade occurs. If Yes is selected,
sync is triggered after a firmware upgrade.
• In the phone configuration file (cfg.xml) with XML , enter a string in this format:
<Resync_After_Upgrade_Attempt
ua="na">Yes</Resync_After_Upgrade_Attempt>
•
On the phone web page
, select
Yes
to trigger resync after a firmware upgrade,
or
No
to not resync.
Default: Yes
Resync After
Upgrade Attempt
If the logical equation in these parameters evaluates to FALSE, resync is not triggered
even when
Resync On Reset is set to TRUE . Only the resync via direct action URL
and SIP notify ignores these resync triggers.
The parameters can be programmed with a conditional expression that undergoes macro
expansion. For the valid macro expansions, see
Macro Expansion Variables, on page
73 .
• In the phone configuration file (cfg.xml) with XML , enter a string in this format:
<Resync_Trigger_1 ua="na">$UPGTMR gt 300 and $PRVTMR ge
600</Resync_Trigger_1>
<Resync_Trigger_2 ua="na"/>
• On the phone web page , specify the triggers.
Default: Blank
Resync Trigger 1
Resync Trigger 2
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
52
Cisco IP Phone Provisioning
Profile Resync Parameters