Documentation

Cloudonix Integration

Configure Cloudonix for voice communication in Paladin AI

Overview#

Cloudonix is a cloud communications platform that enables Paladin voice agents to connect to SIP communications platform, either on-premise or in the cloud. In addition, Cloudonix exposes a full set of voice APIs, that provide a full suite of call-control capabilities and more.

Prerequisites#

Before setting up Cloudonix integration, you'll need:

  • 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 Paladin and we'll auto-create one for you on save, with the application url pre-set)
  • A Cloudonix outbound voice trunk service provider connection
  • Access to your Paladin workspace

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 Paladin, then copy its Application Name. Skip this if you want Paladin to auto-create the Voice Application for you on save.

Step 2: Configure in Paladin AI#

  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 Paladin will auto-create a Voice Application on save (with the application url and CXML runtime already configured) and store its name on this configuration.
  1. Click Save Configuration
  2. 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.

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#

Cloudonix routes inbound calls per Voice Application — the webhook URL is set once on the application, and applies to every DNID bound to it. When you save an inbound workflow on a phone number, Paladin automatically pushes the webhook URL to your Voice Application's url (provided the credentials are correct), so you don't need to set the webhook by hand. If Paladin auto-created the application during configuration save, the url is already set and this push is a no-op — you only need to bind your DNIDs to the auto-created application.

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
Cloudonix console showing domain selection
Cloudonix console showing domain selection
Cloudonix console showing domain selection
Cloudonix console showing domain selection
  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 Paladin) with these settings:
  • Application Resource Type: Remote Application Resource
  • Application Runtime: Cloudonix (CXML)
  • Application URL: https://app.paladin.northmanngrp.com/api/v1/telephony/inbound/run
  • HTTP Method: POST
  1. Under DNID Numbers, add each phone number (DNID) you want to route through this application
  2. Save

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

  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 Paladin
  3. Confirm:
  • URL is set to: https://app.paladin.northmanngrp.com/api/v1/telephony/inbound/run
  • Method is POST

Step 5: Verify Setup#

  • Ensure your Paladin AI 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 Paladin AI voice agent answers and responds
  3. Check call logs in both Paladin AI dashboard and Cloudonix Console
  4. Confirm clear two-way audio communication

Troubleshooting#

Invalid phone number error

Ensure phone numbers include country code in E.164 format: +1234567890

Authentication failed
  • Verify Domain ID, Bearer Token, and Application Name are correct
  • Check for extra spaces in credentials
  • Ensure credentials haven't been disabled or deleted in Cloudonix Console
No audio on calls
  • Verify WebSocket connection is established
  • Check firewall rules for WebSocket traffic
  • Ensure audio pipeline is configured correctly
Inbound calls not reaching voice agent
  • Verify the DNID is bound to the same Voice Application whose name you

configured in Paladin - Confirm the called number exists in your Paladin telephony configuration and has an Inbound workflow assigned - After assigning the inbound workflow, confirm Paladin successfully updated the application's url (no warning shown on save) - Verify your inbound trunk is active and receiving calls

Voice agent doesn
  • Confirm the phone number has an Inbound workflow assigned in

/telephony-configurations - Verify the Bearer Token in Paladin matches the one in your Cloudonix Console - Verify WebSocket connection establishes successfully - Review call logs for error messages

Best Practices#

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