Connect ElevenLabs to Bitcall (Outbound SIP Trunk)
Connect ElevenLabs to Bitcall (Outbound SIP Trunk)
Use Bitcall as the outbound SIP trunk for your ElevenLabs Conversational AI agent. Import a SIP trunk, set the address and digest auth, and place a test outbound call.
Before you begin
💡 Heads-up: Bitcall is outbound-only today. ElevenLabs Conversational AI supports native SIP trunking (no Twilio middleman required), so you can point it straight at Bitcall for outbound calls. Inbound numbers (DIDs) are coming soon.
"ElevenLabs gives your agent its voice. Bitcall puts that voice on the phone — outbound, worldwide." 🗣️📞
🧰 What You'll Need
- An ElevenLabs account with a Conversational AI agent built and tested
- A Bitcall SIP account (username + password) — see Set Up Your First SIP Account
- An outbound Caller ID (CLI) you're allowed to present
- A little Bitcall balance (prepaid)
🔑 Step 1: Get Your Bitcall SIP Details
| Setting | Value |
|---|---|
| SIP address (host) | gateway.bitcall.io (enter without the sip: prefix) |
| Port / transport | 5060 UDP by default; TLS/TCP via the domain (recommended for ElevenLabs) |
| Auth | SIP username/password (digest) — recommended |
ElevenLabs uses wideband audio (PCM 16 kHz) where the trunk supports it, and can fall back to G.711. Encrypt the media (SRTP) if you enable a TLS transport.
➕ Step 2: Import the SIP Trunk in ElevenLabs
- In ElevenLabs, go to Conversational AI → Phone Numbers → Import Number from SIP Trunk.
- Configure the connection:
- Address:
gateway.bitcall.io(hostname only — nosip:prefix) - Transport: TLS (or TCP) — ElevenLabs recommends an encrypted transport
- Authentication: Digest — enter your Bitcall SIP username and password (digest is recommended over IP ACL, which is harder to manage)
- Address:
- Click Import.
Prefer IP allowlisting instead? You can use ACL auth and whitelist ElevenLabs' signalling IPs in Bitcall (Trusted IP) — but digest auth is simpler and the recommended path. See Trusted IP vs. SIP Credentials.
🎭 Step 3: Set Your Caller ID + Assign the Agent
- The number you import is your outbound caller ID (not a Bitcall DID — Bitcall is outbound-only). Manage CLI rules here: Change or Manage Your Caller ID.
- Assign your Conversational AI agent to the imported number.
🚀 Step 4: Place a Test Outbound Call
Trigger an outbound call from the ElevenLabs dashboard or API (the SIP-trunk outbound-call endpoint). 📞 The agent dials out through Bitcall. 🎉
🛠️ Troubleshooting Table
| Problem | Likely cause & fix |
|---|---|
| Trunk import fails / no registration | Wrong Address (drop the sip: prefix) or wrong digest credentials. Double-check username/password. |
| Connected but no / one-way audio | Media path issue or codec mismatch. If you enabled TLS, make sure SRTP is on; allow the negotiated codec (ulaw works as a fallback). See AI voice calls dropping after 30 seconds. |
401 / 403 rejected |
If using ACL auth, ElevenLabs' IPs aren't whitelisted in Bitcall; switch to digest auth or add the IPs. |
| Call drops after ~30–60 seconds | RTP inactivity during the agent's thinking gaps → RTP keepalives + raise the timeout. See AI voice calls dropping after 30 seconds. |
| Caller ID wrong / missing | CLI rules vary by destination. See Change or Manage Your Caller ID. |
🧠 TL;DR Recap
✅ Import a SIP trunk in ElevenLabs → Address = gateway.bitcall.io (no sip:)
✅ Transport TLS/TCP, Digest auth with your Bitcall username/password
✅ Set your Caller ID, assign your agent, place a test call ☕
Related: SIP trunking for AI voice agents (full explainer) · AI voice calls dropping after 30 seconds · Trusted IP vs. SIP Credentials
Connect Bland AI to Bitcall (Outbound SIP Trunk)
Connect LiveKit to Bitcall (Outbound SIP Trunk)
On This Page
Before you begin
🧰 What You'll Need
🔑 Step 1: Get Your Bitcall SIP Details
➕ Step 2: Import the SIP Trunk in ElevenLabs
🎭 Step 3: Set Your Caller ID + Assign the Agent
🚀 Step 4: Place a Test Outbound Call
🛠️ Troubleshooting Table
🧠 TL;DR Recap