#Help me setup Inbound and Outbound calls for ElevenLabs + Twilio - SIP

1 messages · Page 1 of 1 (latest)

vague sequoiaBOT
#
AI-generated Answer for looptilbreak_97434

Below are the two supported ways to run inbound and outbound calls with ElevenLabs + Twilio. Pick one path: the Native Twilio integration (simplest) or Twilio Elastic SIP Trunking (SIP).

Option A — Native Twilio integration (recommended)

  • Prereqs: Twilio account plus either a purchased Twilio number (inbound + outbound) or a Twilio Verified Caller ID (outbound only). (elevenlabs.io)
  • Import your Twilio number in ElevenLabs: Agents Platform -> Phone Numbers -> Add -> Twilio. Enter Phone Number, Twilio Account SID, and Auth Token. ElevenLabs auto-configures the number and detects whether it supports inbound+outbound (purchased number) or outbound-only (Verified Caller ID). (elevenlabs.io)
  • Inbound setup: Assign the imported (inbound-capable) number to your agent. Call the number to test—your agent answers. (elevenlabs.io)
  • Outbound setup: Use the Outbound Call action in Phone Numbers (or the API) to have your agent call a destination; Verified Caller IDs work for outbound-only use cases. (elevenlabs.io)
  • API (optional): You can import Twilio numbers programmatically via POST /v1/convai/phone-numbers/create with twilio.sid and twilio.token. (elevenlabs.io)

Option B — Twilio Elastic SIP Trunking (SIP)
Use this if you prefer to keep calls on SIP trunks. ElevenLabs supports both inbound and outbound over SIP with Twilio-specific header compatibility.

  1. Add your Twilio SIP number to ElevenLabs
  • Agents Platform -> Phone Numbers -> Import a phone number from SIP trunk.
  • Enter:
    • Label and E.164 Phone Number (e.g., +15551234567).
    • Transport: TCP or TLS (recommended).
    • Media encryption: Disabled/Allowed/Required (recommend TLS + Required).
    • Outbound “Address”: the hostname/IP where ElevenLabs should send outbound SIP INVITEs (use your Twilio SIP Termination hostname; enter only the host, no sip: prefix). (elevenlabs.io)
  • Authentication: Provide SIP digest auth (username/password) if your trunk requires it; otherwise use ACL (IP allowlist). Digest auth is recommended. (elevenlabs.io)
  • Assign the imported phone number to your agent for inbound handling. (elevenlabs.io)
  1. Point Twilio SIP origination to ElevenLabs
  • Send SIP INVITEs for your number(s) from Twilio to your ElevenLabs SIP endpoint. If you require static IP allowlisting, use the Enterprise static endpoint sip-static.rtc.elevenlabs.io (region-specific options available); otherwise traffic is served via sip.rtc.elevenlabs.io behind ElevenLabs’ load balancer. Contact Support for static IP access. (elevenlabs.io)
  • Codec/transport: Use G.711 or G.722; SIP over TCP/TLS (UDP not available). SIP signaling ports: 5060 (TCP) or 5061 (TLS). Configure SRTP to match your “Media encryption” choice. (elevenlabs.io)
  1. Twilio-specific headers and metadata
  • ElevenLabs will accept standard custom headers X-CALL-ID and X-CALLER-ID for metadata.
  • If those aren’t present, ElevenLabs automatically falls back to Twilio’s sip.twilio.callSid header—no extra configuration needed. Metadata is exposed in pre-call webhooks and system variables. (elevenlabs.io)

Testing and

sly mural
#

Provide the SIP configuration details for Twilio