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

15
3 Updates and Upgrades
Remote Updates
You can configure Bria to check with the update server at specified intervals for changes to the user’s settings.
Remote Upgrades
There are two ways to support upgrades to Bria.
Use CounterPath Upgrade Server
The default behavior is to obtain upgrades from the CounterPath upgrade server. Whenever CounterPath puts a
new executable on its upgrade server, each user’s Bria will automatically download the upgrade and an install
prompt will appear.
No work on your part is required for this option. Bria is already configured to do this. You do not have to set up
any servers.
Set up your Own Upgrade Server
You can set up an upgrade server and deploy upgrades yourself. One of the advantages of this option is that you
can test the new executable on a few deployments before rolling it out to all your users. See page 17.
3.1 General Setup
Remote update and remote upgrade are controlled by Bria settings. To change the default values to values
suitable for your deployment, change them through remote provisioning, the first time the user logs in. After
that, change them as necessary through remote provisioning or remote update.
Domain:Section Setting Comment
feature:auto_update code_server_url The web server for remote upgrades of the executable. Default is
empty.
feature:auto_update config_server_url The web server for remote update. Default is empty.
feature:auto_update config_check_initial_t_s Sets the initial value for the update timer (page 16). Default is 60
seconds.
feature:auto_update code_check_initial_t_s Sets the initial value for the upgrade timer (page 17). Default is 60
seconds.
feature:auto_update update_check_t1_s Sets the post-initial value for both the update timer and upgrade
timer. Default is 86400 seconds (24 hours). Typically, leave the
default.