Configuration and Setup
      Back to home
      1. Acrobits & Cloud Softphone FAQ
      2. Cloud Softphone (Business Solution) FAQ
      3. Configuration and Setup

      How does External Provisioning for Cloud Softphone and services work?

      External provisioning is an **optional** provider-hosted web service that the app calls after portal provisioning. It receives username, password, and cloud ID, returns Account XML, and the app merges it with portal defaults.

      Note: 

      Refer to Acrobits documentation on Cloud Softphone external provisioning at doc.acrobits.net/provisioning/external_provisioning.html for detailed technical information.

      What is External Provisioning?

      External Provisioning is an optional web service that your backend hosts. After the app downloads its base configuration and theme from the Cloud Softphone portal, it can call your service, which returns Account XML. The app merges your response with the portal defaults to finalize the user’s setup.

      We have a paid service option for those who need assistance. If you lack the resources, expertise, and time, we provide paid professional services for setting up the external provisioning.

      Check with your sales representative about its cost, or contact us directly by email at sales@cloudsoftphone.com

      Is External Provisioning required?

      No. Portal-only provisioning works. Use External Provisioning when you need per-user data or custom logic.

      Background on the provisioning flow: Provisioning introduction

      See also:

      When should I use it?

      • Hide SIP credentials from end users while mapping login to SIP accounts.
      • Per-user configuration (e.g., enable/disable messaging for specific users).
      • Custom account parameters (e.g., add identifiers or flags your backend needs).

      See examples and use cases: Use cases

      See also:

      Changes in the editable copy

      How does the flow work?

      1. App downloads the base configuration and theme from the portal (by Cloud ID).
      2. Optional: App calls Global External Provisioning for quick dials and dial actions.
      3. Optional: App calls your External Provisioning service with placeholders %username%, %password%, %fullcode%.
      4. Your service returns Account XML; the app merges it with portal defaults.
      5. App starts with the merged settings and follows re-provisioning rules if configured.

      Full sequence details: Initial provisioning

      Also important:

      For implementation basics, visit spec: Web service definition · Response format

      Re-provisioning

      Docs: Re-provisioning