Connect LiveKit to Bitcall (Outbound SIP Trunk)

💡 Heads-up: Bitcall is outbound-only today — a clean fit for LiveKit agents that place calls. Works with self-hosted LiveKit or LiveKit Cloud. Inbound numbers (DIDs) are coming soon.

---

"LiveKit runs your real-time agent. Bitcall is the outbound trunk it dials through." 🤖📞

• A LiveKit project (self-hosted or LiveKit Cloud) with the lk CLI installed, or dashboard access
• A Bitcall SIP account (username + password) — see Set Up Your First SIP Account
• An outbound Caller ID (CLI) you're allowed to present, in E.164
• A little Bitcall balance (prepaid)

---

---

LiveKit dials out through a SIP outbound trunk that holds your provider endpoint and credentials. Create outbound-trunk.json:

{
  "trunk": {
    "name": "Bitcall Outbound Trunk",
    "address": "gateway.bitcall.io",
    "numbers": ["YOUR_OUTBOUND_CALLER_ID"],
    "auth_username": "YOUR_BITCALL_SIP_USERNAME",
    "auth_password": "YOUR_BITCALL_SIP_PASSWORD"
  }
}

Then create it with the CLI:

lk sip outbound create outbound-trunk.json

📋 Copy the returned Trunk ID — you'll need it to place calls.

• address is your Bitcall SIP host (gateway.bitcall.io).
• numbers is the outbound Caller ID you present (not a Bitcall DID — Bitcall is outbound-only).
• On LiveKit Cloud, you can do the same from Telephony → SIP trunks → Create new trunk → JSON editor → Outbound.
• Optional: set destination_country to originate from a region close to where you're calling.

---

Caller-ID behavior depends on the destination country and operator rules: Change or Manage Your Caller ID.

---

Dial a number into a room using the trunk (CLI shown; the same exists in the SDKs via create_sip_participant):

lk sip participant create \
  --room "my-room" \
  --trunk "YOUR_TRUNK_ID" \
  --call "NUMBER_YOU_ARE_CALLING" \
  --identity "outbound-caller"

For an AI agent, dispatch your LiveKit Agent into the room, then create the SIP participant to dial the user — see LiveKit's "outbound calls" agent guide. 📞🎉

---

---