Cloud Softphone Provisioning Methods

Acrobits Cloud Softphone portal is the default provisioning tool that generates a single configuration for all desired Softphone endpoints (devices). The external provisioning method is also available for Cloud Softphone project owners.

Our tutorial video summarizes the provisioning methods available for Cloud Softphone:

Acrobits offers two provisioning methods for Cloud Softphone projects:

The Cloud Softphone portal at providers.cloudsoftphone.com
- Besides being the platform for the softphone project owners to create their applications, the Cloud Softphone portal also acts as the primary provisioning method for distributing and managing the application on various devices.
- This portal is user-friendly and intuitive, even for non-technical users who have a limited understanding of the SIP.
External provisioning

Tips

Refer to Acrobits documentation at doc.acrobits.net/provisioning/index.html for more information.

- For project owners who are looking for more granular and targeted provisioning methods, this method works similarly to provisioning methods used for hardware phone endpoints.
- It involves the use of an XML file to configure settings.

Global external provisioning (optional)

An optional provider-hosted service the app calls after portal provisioning to fetch items not in Account XML, such as Quick Dials and Custom Dial Actions, using the same input parameters.

Note: Configure in the portal with keys prefixed initialGlobalProvisioning* (for example, initialGlobalProvisioningUrl). The app substitutes %username%, %password%, and %fullcode% before calling your endpoint.

See the developer reference: Global external provisioning.

When to use

Deliver organization-wide or per-user Quick Dial entries.
Define Custom Dial Actions that adjust or enrich call behavior.
Vary content per user with the same provisioning input parameters.

How it works

The app downloads base configuration and theme from the portal for the Cloud ID.
The app calls your initialGlobalProvisioningUrl with resolved placeholders.
Your service returns XML with a free root node that may include <quickDial> and/or <dialActions>.
The app applies these items to the user’s configuration.
If configured, the app refreshes these items on an interval (see Re-provisioning).

Response format

Return 2xx OK with Content-Type: application/xml and a root node containing your data. To show a custom error in the app, return a non-2xx response with <error><message>...</message></error>.

Re-provisioning

Enable periodic refresh with keys prefixed globalExtProv* and set globalExtProvRefresh in seconds (default 3600). Refresh is automated and transparent to end users.