Cloudonix Integration

Documentation Index

Fetch the complete documentation index at: https://asisso-cd509912.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

​

Prerequisites

• A Cloudonix account
• A Cloudonix domain UUID (or the domain name)
• A Cloudonix domain API Key (Bearer Token)
• A Cloudonix Voice Application on that domain (optional — leave the field blank in Asisso and we’ll auto-create one for you on save, with the application url pre-set)
• A Cloudonix outbound voice trunk service provider connection
• Asisso instance running and accessible

​

Video Tutorial

​

Configuration

​

Step 1: Get Cloudonix Credentials

1. Log in to your Cloudonix Console
2. Find your Domain ID (UUID or domain name) and Bearer Token (Domain API Key) on the dashboard
3. (Optional) Navigate to your domain’s Applications and create (or open) the application you’ll use with Asisso, then copy its Application Name. Skip this if you want Asisso to auto-create the Voice Application for you on save.

​

Step 2: Configure in Asisso

1. Navigate to /telephony-configurations and click Add configuration
2. Watch the Cloudonix setup video tutorial above for detailed guidance
3. Select Cloudonix as your provider
4. Enter your credentials:
   • Bearer Token
   • Domain ID
   • Application Name — optional. Leave blank and Asisso will auto-create a Voice Application on save (with the application url and CXML runtime already configured) and store its name on this configuration.
5. Click Save Configuration
6. Open the configuration you just created and add at least one phone number (with country code in E.164 format, e.g. +1234567890). The default caller ID is used for outbound calls.
   If Asisso auto-created the Voice Application for you, you still need to bind your DNIDs to that application in the Cloudonix cockpit (see Step 2 of Inbound Calling Setup). The auto-created application is named asisso-<random> — its name is shown on the saved configuration.

​

Step 3: Test Your Configuration

1. Create a test workflow
2. Click “Call” to verify connection
3. Check call logs for successful connection

​

Inbound Calling Setup

​

Step 1: Set Up the Inbound Trunk

1. Log in to your Cloudonix Console
2. Navigate to Trunks → Create Inbound Trunk and configure your inbound trunk with your voice service provider

​

Step 2: Create the Voice Application and Link DNIDs

1. In the Cloudonix cockpit, select your domain and navigate to Applications
2. Create a new application (or open the existing one whose name you configured in Asisso) with these settings:
   • Application Resource Type: Remote Application Resource
   • Application Runtime: Cloudonix (CXML)
   • Application URL: https://api.asisso.com/api/v1/telephony/inbound/run
   • HTTP Method: POST
3. Under DNID Numbers, add each phone number (DNID) you want to route through this application
4. Save
   The Application URL is what Asisso’s auto-push updates in Step 3 — you can leave it blank during creation and let the auto-push fill it in, or paste the URL above so the application is usable immediately. Either works.
   

​

Step 3: Assign an Inbound Workflow to the Phone Number in Asisso

1. Go to /telephony-configurations and open your Cloudonix configuration
2. In the Phone numbers section, edit the number that should receive inbound calls
3. Set its Inbound workflow to the agent that should answer
4. Save

​

Step 4: Verify the URL on the Voice Application

1. Open your Cloudonix cockpit and navigate to your domain’s Applications
2. Open the application whose name you configured in Asisso
3. Confirm:
   • URL is set to: https://api.asisso.com/api/v1/telephony/inbound/run
   • Method is POST
   Asisso pushed this URL automatically when you saved the inbound workflow in Step 3. The same URL is shared across every DNID bound to that application — Asisso routes each inbound call to the right agent based on the called number’s inbound workflow assignment. If the field is empty, shows a different URL, or Asisso surfaced a sync warning on save, the auto-push failed — most often because the Bearer Token, Domain ID, or Application Name in Asisso is incorrect. Paste the URL into the field yourself, set the method to POST, and save.
   

​

Step 5: Verify Setup

• Ensure your Asisso instance is publicly accessible
• Verify any firewalls allow Cloudonix’s IP ranges
• Confirm your inbound trunk is active and receiving calls

​

Test Inbound Calling

1. Call your configured phone number from another phone
2. Verify your Asisso voice agent answers and responds
3. Check call logs in both Asisso dashboard and Cloudonix Console
4. Confirm clear two-way audio communication

​

Troubleshooting

​

Best Practices

• Test your configuration with a single call before running campaigns
• Monitor Cloudonix Sessions for usage
• Use a dedicated Voice Application for Asisso so the shared url doesn’t conflict with other systems