CounterPath Bria 3.0 Provisioning Guide – Retail Deployments - Manual (Page 20)

CounterPath Corporation
16
Timer Settings
Remote upgrades and remote updates rely on four timers in the user’s settings. The timers control how
frequently Bria contacts the update and upgrade executable servers.
All values are in seconds. You can use the timer_factor setting to convert the values on your side into seconds.
• update_check_initial_t1_s.
• update_check_t1_s.
• deffer_timer_t2_s.
• block_timer_t3_s.
Automatic checks for remote upgrades and automatic checks for remote updates are performed at the same
point: when the user starts Bria. The interaction of the timers occurs as follows:
1. Bria starts.
2. The timer update_check_initial_t1_s starts.
3. When update_check_initial_t1_s expires, Bria checks its state of business (whether or not the user is busy
with a call or instant message session).
• If Bria is busy, deffer_timer_t2_s starts. When this timer expires, Bria checks its business again.
deffer_timer_t2_s continues restarting and expiring until Bria is no longer busy (when the user hangs
up from an active call).
• If Bria is not busy, it contacts the servers.
4. The timer block_timer_t3_s is set when a check is initiated at Bria. Another check is not allowed as long as
block_timer_t3_s is still active. This timer ensures that provisioning checks are not performed too often,
and is especially useful for protecting against potential hacker requests (which may arrive with frequency).
The timer block_timer_t3_s is typically shorter in duration than update_check_t1_s.
5. After the first check, the cycle starts over at step 1 using the timer update_check_t1_s (not
update_check_initial_t1_s).
Changing Timer Settings
New timer settings will take effect as follows:
• If the timer is not running when the server sends new settings (and they are saved on the Bria computer),
then the setting take effect immediately. The next time the timer is loaded, the new setting will be used.
• If the timer is running, the new setting takes effect after the timer expires and is reloaded. This means if
update_check_t1_s still has 23 hours to go, it will be changed only after 23 hours. However, if the session is
restarted, the new setting will take effect.
feature:auto_update update_check_t1_s See below for a description.
Default is 86400 seconds (24 hours).
Typically, leave the default.
feature:auto_update timer_factor See below for a description.
Default is 1.00