Cisco SPA2102-AU Provisioning Guide - Page 42

Triggers, Configurable Schedules - update firmware

Page 42 highlights

Using Provisioning Parameters Chapter 2 Creating Provisioning Scripts Triggers The SPA is designed to resync with the provisioning server periodically. The resync interval is configured in Resync_Periodic (seconds). If this value is left empty, the SPA does not resync periodically. The resync typically takes place when the voice lines are idle. In case a SPA voice line is active when a resync is due, the SPA delays the resync procedure until the line becomes idle again. However, it waits no longer than Forced_Resync_Delay (seconds). A resync may cause configuration parameter values to change. This, in turn, causes a firmware reboot, which terminates any voice connection active at the time of the resync. If a resync operation fails because the SPA was unable to retrieve a profile from the server, if the downloaded file is corrupt, or an internal error occurs, the SPA tries to resync again after a time specified in Resync_Error_Retry_Delay (seconds). If Resync_Error_Retry_Delay is set to 0, the SPA does not try to resync again following a failed resync attempt. When upgrading, if an upgrade fails, a retry is performed after Upgrade_Error_Retry_Delay seconds. Two configurable parameters are available to conditionally trigger a resync: Resync_Trigger_1 and Resync_Trigger_2. Each of these parameters can be programmed with a conditional expression (which undergoes macro expansion). If the condition in any of these parameters evaluates to true, a resync operation is triggered, as though the periodic resync timer had expired. 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 Configurable Schedules Profile resyncs and upgrades provide for automatic retries in case of failure, in addition to periodic configuration updates. Time intervals are specified via 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, which bounds a random extra delay. The last element in the sequence is implicitly repeated forever. For example, Resync_Periodic = 7200 Resync_Error_Retry_Delay = 1800,3600,7200,14400 In this example, the SPA periodically resyncs every two hours. In case of resync failure, the SPA retries in 30 minutes, then again in 1 more hour, then after two more hours, and then after four more hours, continuing at four-hour intervals until it successfully resyncs. The following is another example: Resync_Periodic = 3600+600 Resync_Error_Retry_Delay = 1800+300,3600+600,7200+900 2-16 Linksys SPA Provisioning Guide Version 3.0

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94

2-16
Linksys SPA Provisioning Guide
Version 3.0
Chapter 2
Creating Provisioning Scripts
Using Provisioning Parameters
Triggers
The SPA is designed to resync with the provisioning server periodically. The resync interval is
configured in Resync_Periodic (seconds). If this value is left empty, the SPA does not resync
periodically.
The resync typically takes place when the voice lines are idle. In case a SPA voice line is active when a
resync is due, the SPA delays the resync procedure until the line becomes idle again. However, it waits
no longer than Forced_Resync_Delay (seconds). A resync may cause configuration parameter values to
change. This, in turn, causes a firmware reboot, which terminates any voice connection active at the time
of the resync.
If a resync operation fails because the SPA was unable to retrieve a profile from the server, if the
downloaded file is corrupt, or an internal error occurs, the SPA tries to resync again after a time specified
in Resync_Error_Retry_Delay (seconds). If Resync_Error_Retry_Delay is set to 0, the SPA does not try
to resync again following a failed resync attempt.
When upgrading, if an upgrade fails, a retry is performed after Upgrade_Error_Retry_Delay seconds.
Two configurable parameters are available to conditionally trigger a resync: Resync_Trigger_1 and
Resync_Trigger_2. Each of these parameters can be programmed with a conditional expression (which
undergoes macro expansion). If the condition in any of these parameters evaluates to true, a resync
operation is triggered, as though the periodic resync timer had expired.
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
Configurable Schedules
Profile resyncs and upgrades provide for automatic retries in case of failure, in addition to periodic
configuration updates. Time intervals are specified via 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, which bounds a random
extra delay. The last element in the sequence is implicitly repeated forever. For example,
Resync_Periodic
=
7200
Resync_Error_Retry_Delay
=
1800,3600,7200,14400
In this example, the SPA periodically resyncs every two hours. In case of resync failure, the SPA retries
in 30 minutes, then again in 1 more hour, then after two more hours, and then after four more hours,
continuing at four-hour intervals until it successfully resyncs.
The following is another example:
Resync_Periodic
=
3600+600
Resync_Error_Retry_Delay
=
1800+300,3600+600,7200+900