Table of Contents
Advertisement
Creating Provisioning Scripts
Using Provisioning Parameters
Cisco Small Business IP Telephony Devices Provisioning Guide
The following example condition triggers a resync if Line 1 failed to register for
more than 5 minutes (300 seconds), and at least 10 minutes (600 seconds) have
elapsed since the last resync attempt.
$REGTMR1 gt 300 and $PRVTMR ge 600
Resyncing at a Specific Time
The Resync_At parameter allows you to resync at a specific time. This parameter
uses the 24-hour format (hhmm) to specify the time.
To avoid simultaneously flooding the server with resync requests from multiple
phones set to resync at the same time, the phone triggers the resync up to ten
minutes after the specified time.
For example, if you set the resync time to 1000 (10 a.m.), the phone triggers the
resync anytime between 10:00 a.m. and 10:10 a.m.
By default, this feature is disabled. If the Resync_At parameter is provisioned, the
Resync_Periodic parameter is ignored.
Configurable Schedules
Profile resyncs and upgrades provide for automatic retries in case of failure, in
addition to periodic configuration updates. Time intervals are specified by using
three parameters, which are usually specified as a specific interval duration, in
seconds. Starting with firmware version 3, these parameters allow the application-
level (macro time scale) retry schedule to be configured. These provisioning
parameters are:
•
Resync_Periodic
•
Resync_Error_Retry_Delay
•
Upgrade_Error_Retry_Delay
These parameters accept a single delay value (seconds). The new extended
syntax allows for a comma-separated list of consecutive delay elements. Each
delay element consists of a deterministic delay value, optionally followed by a plus
sign and an additional numeric value that bounds a random extra delay. The last
element in the sequence is implicitly repeated forever. For example,
Resync_Periodic
Resync_Error_Retry_Delay
=
7200
=
1800,3600,7200,14400
2
50
Advertisement
Table of Contents
