CounterPath Bria 4 Provisioning Guide - Enterprise Deployments - Manual (Page 20)

CounterPath Corporation
16
3.2 Remote Update
3.2.1 Setting Up
• Set up Bria as described on page 15.
• Set up the update server to handle the procedure described below.
3.2.2 Timing of Update Checks
Bria contacts the update server as follows:
1. Bria starts and the update timer starts using the value in config_check_initial_t_s.
2. When the update timer expires, Bria checks for and (if appropriate) performs an update.
3. The update timer is then restarted, but this time with the value in update_check_t1_s. Each time the update
timer expires, a check is performed again and the timer is restarted.
Note that the update timer and upgrade timer have separate initial values (separate settings) but share the
same value after that: the value in update_check_t1_s.
3.2.3 How Remote Update Is Performed
Assuming that the timers are not all set to zero, this procedure runs “in the background” for as long as Bria is
running.
1. When triggered by the timer, Bria checks for remote updates by sending a GET to the update server.
For example, the value of feature:auto_update:config_server_url might be:
This URL could result in a GET to your web server of:
2. The update server must response with the following:
or
where:
• success: 1=true (there are updates) or 0=false (there are no updates).
• The [ SETTINGS ] section contains the changed settings. See “Data Format” on page 7 for details.
• The response must end with a CRLF.
https://myupdatesettingsserver.com?language=$language$&build=$build$&name=$loginame$
myupdatesettingsserver.com?language=en-US&build=16835&name=kperera
[DATA]
Success=0
<CRLF>
[DATA]
Success=1
[SETTINGS]
feature:auto_update:
update_check_t1_s =“3600”
<CRLF>