Cloud Softphone provisioning process needs some Input Parameters for Provisioning from the user to complete successfully. These parameters are collected from some initial screen. There are several types and variants; all are described below.
This is the default initial screen used by generic Cloud Softphone app (not white-label apps). It is a screen with two input fields and a button which starts QR code reader.
The first of the input fields is titled “Cloud ID”, the other one “Password”.
The text from first input field is processed by finding the last ‘@’ character from the end of the string and splitting the string in two from this position. The first part is treated as username, the second part as cloud ID.
The contents of the “Password” field is taken as password.
The values of username and password are url-decoded before use. Searching for the ‘@’ character from the end of the string helps in some cases when the username has ‘@’ sign in it and is is not url-encoded and the app will gracefully accept this input.
Classic initial screen behaves slightly different in white label case. For white label apps, the cloud ID of the app is known and is hard-coded into the app binary during the white label build process. It is also possible to customize the initial screen, like change the textation, colors and it is also possible to hide the input fields and keep only the QR code reader, or hide the QR code part and keep just the input fields.
Since the cloud ID is hard-coded and known, the content of the first input field is treated differently. Let’s assume the cloud ID of our app is WLAPP. See the table below for examples:
input username cloud ID note
user WLAPP hard-coded cloud ID is used
user WLAPP the part after @ matches hard-coded cloud ID
user WLAPP* specifies test version of the app
user WLAPP* different cloud ID is ignored, but * for test version is used
email@example.com WLAPP gracefully accepted
firstname.lastname@example.org WLAPP correct form
The main difference between the generic app case is that since cloud ID is known, single word is treated as username instead of cloud ID. When cloud id is explicitly entered, it is ignored and the hard-coded one is always used instead. In case the explicitly entered cloud id is appended by *, this * will be used to provision editable settings from the portal.
To avoid typing, the input parameters may be passed via QR code. There is an embedded QR code reader in the app which is used to scan the code.
The code should contain text in the following format:
- URI scheme prefix - required as-is
- this part will be used as username parameter
- this part will be used as password parameter
- this part will be used as cloud ID parameter
Like above, the values of username and password should be url-encoded. Valid Cloud IDs contain only letters and digits, so url-encoding should have no effect on it.
input username password cloud ID
(empty) (empty) CODE
user 12345 CODE
email@example.com @AB CODE
Provisioning the editable version from classic initial screen is done by appending
* character to cloud ID
input parameter. For generic app, cloud ID needs to be always explicitly provided, so it’s all about appending
For white label apps, the cloud ID is embedded inside the app binary and it is normally not needed to enter it
explicitly. It is embedded without the
* character though, so to provision Editable version, the full form
user*CODE* has to be entered into the first input field.
Registration Wizard is only available in Cloud Softphone White Label apps. In case of white label apps, the cloud ID input parameter is embedded into the app binary and we only need to get the username and password from the user.
Registration wizard is typically used to verify the user’s phone number. It consists of two pages:
On this page, the user is asked to fill in his phone number, including country code. When done, the user clicks “Next” button.
The app then uses Phone Number Verifier web service to send user input to your server. The web service is supposed to send an activation code to the phone number the user has entered. When the web service response is successful, the registration wizard switches to Page 2
On the second page, the user is expected to enter the activation or PIN code sent to him in Step 1. For Android devices it is possible to fill in the PIN code automatically from the incoming SMS if the SMS is in proper format.
When Step 2 is submitted, the app uses the hard-coded cloud ID as cloud ID input parameter, contents of the text field in Wizard Step 1 as username and contents of the text field in Wizard Step 2 as password.
White Label apps which use Registration Wizard initial screen typically support External Provisioning web service, which receives the username and password input parameters and verifies that the PIN code matches the one generated by Phone Number Verifier. If it doesn’t match, the web service can return an error and user is returned back to the wizard, where he can correct the input.
Cloud ID is not entered anywhere in Registration Wizard, the hard-coded cloud ID embedded in the app binary is
always used. The trick to provision the editable version is to put the
* character to the end of the input field in
Wizard Step 1. When the app detects trailing
* character in username input param, it removes it and puts it to
the end of cloud ID input param.
For example, if you register with phone number
+15551231234, you’d enter
+15551231234*. Note that the trailing
* is stripped before the value is sent to your scripts, so you don’t need to add any special handling there.
The Registration Wizard offers an elegant way how to handle both new users and existing ones. When the external provisioning web service receives the phone number entered by the user, it can check whether the phone number is known and it is an existing user, or if it is a new one. In the second case, it can create a new account and return SIP credentials and other settings in the external provisioning response.
Web Registration Wizard is the most generic and flexible way of all Initial Screens. When this option is selected, the app shows a full-screen embedded browser and it opens an URL which you can configure.
It is then up to you to create anything you want on this web page, the app will serve only as a browser which displays the content you provide. You can ask for username/password, do a 2-factor authentication, add a CAPTCHA check etc. and generally do whatever is needed to collect the two input parameters which are needed to provision the app - username and password. Cloud-ID is always known because it is hard-coded in the app binary.
When the process on the web is complete and the input parameters are known, they are passed to the app by navigating the
browser to the provisioning link, as described higher on this page. For example, the final page of the reg wizard may
contain a link
<a href="csc:username:password@CODE">Start the app</a>, or the similar link may be openeded via
The app will detect links whih use the
csc provisioning scheme and will extract the input parameters from this link.
Then it will start the provisioning process.
WebRTC app has some additional setup required to enable Web Registration Wizard. You can read the details in the Web Registration Wizard documentation of the WebRTC app.
The URL you choose to show as the initial screen of the Web Registration Wizard is shared among all versions of your app including iOS, Android and WebRTC. You can however use the Client API parameters in your URL to differentiate between platforms.
For example, the
%platform% parameter resolves to either
Chrome depending on
whether the app is the iOS, Android or WebRTC version.
You can use this parameter in a URL like
https://your-service.com/csp/%platform%/register, and then if you
run the WebRTC app, it will load the page at the following URL:
In case of Web Registration Wizard on iOS and Android, the provider itself must find a way how to pass the
character in the cloud ID part of the provisioning link. One possible way is to do it like the native
Registration Wizard - in case
* is entered as part of username, this character is moved to cloud ID.
For the WebRTC app, you cannot enable the Editable version by using the
* character in the
csc: URI. The
WebRTC app will simply ignore the presense of the character in either the username or the CloudID. You can
enable Testing Mode in the WebRTC app to test the Editable version. Refer to the Testing Mode documenation for more information.