Overview
Testing outbound calls involves two main steps:- Getting the list of evaluators with phone numbers
- Running the selected evaluators for outbound testing
Phone number regional coverage: Cekura provides testing phone numbers in a limited set of regions. If you need a receiving number in a region Cekura doesn’t cover (for example, an Indian +91 number), you can import your own number from Plivo or Twilio. Imported numbers work identically to Cekura-provisioned numbers for inbound and outbound testing — your system calls the imported number and Cekura’s testing agent answers.
Prerequisites
- Outbound mode enabled: Agent’s
inboundmust be set tofalse - Agent
contact_numberset to your outbound caller ID: Cekura validates the caller ID (ANI) of every incoming outbound-test call against the agent’scontact_numberfield. If your agent dials from+15551234567, the agent’scontact_numbermust be exactly+15551234567in E.164 format. Set this in Agent settings or via the Update Agent API. - Evaluators ready: Created evaluators with valid phone numbers
Getting Evaluators and Phone Numbers
To retrieve the available evaluators and their associated phone numbers:- Use the List Evaluators API endpoint
- The response will include both evaluators and their corresponding phone numbers for testing
API Reference
Check out the List Evaluators API documentation
Example Code Running Outbound Call
Example Response Structure
Running Outbound Call Tests
Once you have your list of evaluators and phone numbers:- Select which evaluators you want to run
- Execute the evaluators using the Running Evaluators API
- The system will automatically make outbound calls to the phone numbers associated with the selected evaluators
- Monitor the test results through the dashboard
API Reference
Learn more about the Running Evaluators API
Troubleshooting
Calls show Busy / NoAnswer on your telephony provider but never reach Cekura
Calls show Busy / NoAnswer on your telephony provider but never reach Cekura
Cekura rejects incoming outbound-test calls whose caller ID doesn’t match a configured
contact_number on any agent in your project. Open the agent under test and confirm its contact_number is set to the exact E.164 number your agent dials from. An empty or mismatched contact_number causes every outbound attempt to be silently dropped — the symptom on your provider side is Busy / NoAnswer / no-pickup, with no audio and no SIP error explaining why. After setting the correct contact_number, trigger a new run; existing runs that hit this state will remain in timeout and cannot be recovered.Run status stays `timeout` with no transcript
Run status stays `timeout` with no transcript
A
timeout with duration: 0 and an empty transcript means the call never connected to Cekura. Work through these in order:- Caller-ID match — see the entry above; this is the most common cause.
- Dial actually happened — check your telephony provider’s logs to confirm the outbound call was placed.
- Destination number — confirm the number your agent dialed matches the
outbound_numberreturned for that run in the bulk runs API response.