When Cloud Softphone apps (both generic Cloud Softphone and white-label apps based on Cloud Softphone) are started for the first time after installation, they need to be provisioned with graphics theme, configuration data, account credentials and other parameters.
The provisioning process begins when the user enters Input Parameters for Provisioning and submits them. There are several ways how the input parameters may be provided and they are discussed in a separate article about Initial Screens.
When submitted, the app does a sequence of actions to collect provisioning information from various sources:
Steps 1) and 2) download provisioning from Cloud Softphone portal which is common for all users of the same Cloud Softphone app. It only uses the cloud ID as input parameter.
Step 3) allows the provider to add or modify some of the provisioned information from step 1) by calling a web service which receives all input parameters, including the username and password. and returns a response which is merged with provisioning from the Cloud Softphone portal. The global exernal provisioning can, for example, set quick dial items or define new dial actions for the app.
Step 4) is another web service implemented by provider. This web service receives all input parameters, including the username and password and the response must be Account XML which is merged with common defaults received from Cloud Softphone portal in step 1). This allows the provider to set user-specific parameters to the account, like SIP credentials, codec settings, messaging feature etc.
The first two steps run in parallel and they must be executed first, because web service definitions for steps 3 and 4 are returned in the response of Step 1 - they are part of app configuration at Cloud Softphone portal.
When all steps succeed, all the received provisioning information is merged together and saved within the app. The app is then launched with provisioned settings.
The app keeps the provisioning information up-to-date by periodically checking for changes on Cloud Softphone portal and optionally also at the web services given by provider. In case the provider changes configuration of the app on the portal, or via the web service, all the existing apps should get the update within 24 hours by default.
Some providers may request that the app does not contact any 3rd party servers after it has been provisioned, for security reasons. In this case, automatic reprovisioning may be disabled completely. It is possible to add a button to the app which triggers reprovisioning explicitly.