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

Bria 3.0 Provisioning Guide – Retail Deployments
5
1.4 The Mechanism of Remote Provisioning
Each remote provisioning service involves an exchange between the login server and an individual Bria client.
The exchange is performed over HTTP or HTTPS.
1.4.1 Servers
You must deploy servers to handle the provisioning requests:
• The “login server”: a server to handle login requests, if you decide to implement login. This server is
simply a web server that, at a minimum, can serve one plaintext or XML file.
• The “update server”: a server to handle remote update.
• The “upgrade executable server”: a server to handle remote upgrades of the Bria application.
These server roles may in fact all be deployed on the same physical server: that is your decision.
You must set these servers in Bria.
• The login server is either discovered through DHCP or manually entered by the user on the Login dialog, as
described in “Specifying the Login Server” on page 10.
• You will set the update server and upgrade executable server (if they are being used) in the provisioning
response that you set the first time the user logs in.
1.4.2 Bria-to-Server Exchange
The exchange between Bria and the appropriate server involves the following:
• When the appropriate trigger occurs, Bria sends an HTTP or HTTPS request to the server. For login, the
trigger is the user pressing OK on the Bria login dialog. For remote upgrade, the trigger is startup of the
softphone.
• The server responds.
• Bria reads the response and takes the appropriate action: starts the softphone and registers with the SIP
proxy, or finds and installs the upgrade.
Use of Scripts and Macros
You may want to run an appropriate script on the given web server, to provide the information required by Bria.
To run a script, include it in the URL for that server.
Running scripts usually requires information about the user’s deployment. The URL for the appropriate server
can include macros. When Bria contacts the server, it replaces the macros with the real data and includes this
information in the HTTPS request.
Your script must understand the names assigned to the macros.
For example a URL of:
https://mycustomloginserver.com/login.php?platform=$platform$&lic=$license$