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

Bria 3.0 Provisioning Guide – Retail Deployments
19
where:
• Success : 1=true (there is an upgrade) or 0=false (there is no upgrade).
• Mandatory : 1=true. This response is optional; the default is “0”. Bria handles the upgrade
differently depending on this response; see below.
• version : identifies a build stamp set by Bria during build time. Bria uses this version to
determine whether to prompt the user to install the upgrade; see step .
• url : the absolute path to the installer software for the new version.
• The response must end with a CRLF.
The response cannot include a [SETTINGS] secti on. In other words, none of the user’s current settings can
be changed via this response.
If no upgrades are found, Bria will recheck periodically for available upgrades. See “Timer Settings” on
page 16 for details.
Handling of the Upgrade
If an upgrade is available, Bria compares the build number of the application on the user’s computer to the build
number specified in the response (60000 in the above example).
• If the response has the same number, Bria does not prompt the user to download
• If the response has a different number, Bria prompts the user to download the upgrade.
• If the user initiates the download, Bria will download the installer and save it to the local Bria program
folder. Bria will also prompt the user to exit in order to install the new version. The user can install
immediately or postpone installation.
• If the user declines the upgrade and the upgrade is optional, Bria will enter its timing cycle and display
the download prompt again at the appropriate time. See “Timer Settings” on page 16.
• If the user declines a mandatory upgrade, Bria shuts down
• If the user declines with “do not ask me again” (possible only with an optional upgrade), Bria will not
check again for upgrades during the session.
“Install Later” Handling
If the user declines to install the downloaded version, then the next time Bria is started the user will be prompted
to install the newer version.One of the following will occur:
• If the user initiates the installation, Bria will install the new (local) version.
• If the user declines, Bria will start the original version and will enter its timing cycle, displaying the
download prompt again at the appropriate time. See “Timer Settings” on page 16.
• If the user declines with “do not ask me again”, Bria will start the original version and will not prompt to
install again during the session.
Bria starts the version installed most recently. The automatic check scenario will be initiated as described in the
previous section. The downloaded installer will not be deleted, to enable manual rollback, if required.
[DATA]
Success=1
Mandatory=1
version=60000
url=https://executableupgradeserver.com/newversion.exe
<CRLF>