> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sentivue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloudonix

> Configure Cloudonix for voice communication in SentiVue Talk

## Overview

Cloudonix is a cloud communications platform that enables SentiVue Talk workflows 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](https://cockpit.cloudonix.io/onboarding?affiliate=SENTIVUE)
* 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 SentiVue Talk and we'll auto-create one for you on save, with the application `url` pre-set)
* A Cloudonix outbound voice trunk service provider connection

## Configuration

### Step 1: Get Cloudonix Credentials

1. Log in to your [Cloudonix Console](https://cockpit.cloudonix.io/onboarding?affiliate=SENTIVUE)
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 SentiVue Talk, then copy its **Application Name**. Skip this if you want SentiVue Talk to auto-create the Voice Application for you on save.

### Step 2: Configure in SentiVue Talk

1. Navigate to **/telephony-configurations** and click **Add configuration**
2. Select **Cloudonix** as your provider
3. Enter your credentials:
   * Bearer Token
   * Domain ID
   * Application Name — *optional*. Leave blank and SentiVue Talk will auto-create a Voice Application on save (with the application `url` and CXML runtime already configured) and store its name on this configuration.
4. Click **Save Configuration**
5. 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.

   <Note>
     If SentiVue Talk 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](#step-2-create-the-voice-application-and-link-dnids)). The auto-created application is named `sentivue-<random>` — its name is shown on the saved configuration.
   </Note>

### 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, SentiVue Talk 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 SentiVue Talk 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](https://cockpit.cloudonix.io)
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 SentiVue Talk) with these settings:
   * **Application Resource Type**: `Remote Application Resource`
   * **Application Runtime**: `Cloudonix (CXML)`
   * **Application URL**: `https://app.sentivue.com/talk/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

   <Note>
     The Application URL is what SentiVue Talk'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.
   </Note>

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

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 SentiVue Talk
3. Confirm:

   * **URL** is set to: `https://app.sentivue.com/talk/api/v1/telephony/inbound/run`
   * **Method** is `POST`

   SentiVue Talk sets this automatically when you save the inbound workflow.

   Every DNID bound to the application shares this one URL. Calls still reach the right agent, matched on the number they came in on.

   If the field is empty or shows something else, the auto-push failed — usually a wrong Bearer Token, Domain ID, or Application Name. Paste the URL in yourself, set the method to `POST`, and save.

### Step 5: Verify Setup

* Confirm the DNID is bound to the same Voice Application whose name you configured in SentiVue Talk
* Confirm the number exists in your SentiVue Talk telephony configuration with an **Inbound workflow** assigned
* Confirm your inbound trunk is active and receiving calls

### Test Inbound Calling

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

## Call handling setup

Cloudonix numbers use the **Standard** setup: calls reach your agent through your Cloudonix domain's webhook. This supports inbound calls, outbound calls, and cold transfer.

Warm transfer and live translation need the **Advanced** setup, which is currently available on Twilio only. Support for Cloudonix is in progress.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Invalid phone number error">
    Ensure phone numbers include country code in E.164 format: `+1234567890`
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="No audio on calls">
    * Confirm your inbound trunk is active in the Cloudonix cockpit
    * Review the call in your SentiVue Talk call logs for errors
  </Accordion>

  <Accordion title="Inbound calls not reaching workflow">
    * Verify the DNID is bound to the same Voice Application whose name you
      configured in SentiVue Talk - Confirm the called number exists in your SentiVue Talk telephony configuration and has an **Inbound workflow** assigned - After assigning the inbound workflow, confirm SentiVue Talk successfully updated the application's `url` (no warning shown on save) - Verify your inbound trunk is active and receiving calls - Check the application's session logs in your Cloudonix cockpit: they show the response to each webhook attempt, which tells you whether the call reached SentiVue Talk at all
  </Accordion>

  <Accordion title="Voice agent doesn't respond to inbound calls">
    * Confirm the phone number has an **Inbound workflow** assigned in
      /telephony-configurations - Verify the Bearer Token in SentiVue Talk matches the one in your Cloudonix Console - Confirm the application **URL** is exactly `https://app.sentivue.com/talk/api/v1/telephony/inbound/run` and the method is `POST` - Review call logs for error messages
  </Accordion>
</AccordionGroup>

## Best Practices

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