3 remote upgrade, 1 setting up, 2 how remote upgrade is performed – CounterPath Bria 3.0 Provisioning Guide – Retail Deployments User Manual

Page 22

CounterPath Corporation

3.3 Remote Upgrade

3.3.1 Setting Up

•

Set up Bria as described on page 15.

•

Set up an upgrade server as follows:

•

You can use a script to include logic that determines a given deployment needs an upgrade. See below
for an example. Obtain the sample upgrade script from CounterPath and modify it to suit your needs.

Or you can skip the script and manually set up your upgrade server to simply provide a success
response when an upgrade is available and a failure response at other times.

•

If you are using scripts, set the URL for the upgrade server to include the script and any macros (for
example, the language and the build macros).

•

When you want to deploy an upgrade, place it on the “upgrade location”.

3.3.2 How Remote Upgrade 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.

Bria Sends a GET

When triggered by the timer, Bria checks for available upgrades by sending a GET to the upgrade executable
server.

•

For example, if you are using scripts, the value of feature:auto_update:code_server_url might be:

This URL could result in a GET to your webserver of:

•

Or if you are not using scripts, the value is simply the URL of the upgrade server:

Server Response

The upgrade executable server must respond with the following:

https://executablepgradeserver.com/exe_upgrade.php?build=$build$&language=$language&name=$loginame$

https://executablepgradeserver.com/exe_upgrade.php?build=38740&language=USEnglish&name=kperera

https://executablepgradeserver.com

[DATA]
Success=0