Hii, I wanted to ask i want to know FQDN for my account to connect it to a telephony service via S

[mint wave]

AI-generated Answer for buntysaini

Short answer
Use sip.rtc.elevenlabs.io as the SIP FQDN. There isn’t a per‑account FQDN documented. (elevenlabs.io)

Steps to use it with SIP trunking

1. In your SIP provider

• Create a SIP/FQDN connection and set the destination FQDN to sip.rtc.elevenlabs.io. For example, in Telnyx: create a SIP Connection (type FQDN) and add sip.rtc.elevenlabs.io in the FQDN field. Use E.164 number format for inbound, and configure authentication per your policy. (elevenlabs.io)
• SIP signaling can use TCP or TLS (TLS recommended for production). Ensure your firewall allows 5060 for TCP and 5061 for TLS, per your chosen transport. (elevenlabs.io)

2. In ElevenLabs (Agents Platform)

• Go to Phone Numbers → Import a phone number from SIP trunk, enter the E.164 number, select transport (TCP or TLS) and media encryption, then set the outbound Address to your provider’s hostname (e.g., your SIP trunk’s termination host). Complete the import and assign the number to your agent. (elevenlabs.io)

3. Calling format (to reach ElevenLabs)

• When your provider sends calls to ElevenLabs, target a full SIP URI such as:
  sip:[e-mail]:5060;transport=tcp
  Include an identifier (e.g., the phone number) before the “@”. (elevenlabs.io)

Optional: static IP endpoints
If you require static IPs for allowlisting, Enterprise accounts can use the static-IP endpoints:

• sip-static.rtc.elevenlabs.io (default/US-International)
• sip-static.rtc.in.residency.elevenlabs.io (India)
• sip-static.rtc.eu.residency.elevenlabs.io (EU)
  Request access via support or your account rep. (elevenlabs.io)

If you share which carrier you’re using, I can point you to their specific setup guide (e.g., Telnyx) and exact UI steps. (elevenlabs.io)

Sources:
SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation

[ocean mauve]

I want to use Exotel

[mint wave]

AI-generated Answer for buntysaini

Here’s how to use Exotel with ElevenLabs via SIP trunking (and the FQDN you need):

• Provider compatibility: Exotel is supported as a standard SIP trunk provider with ElevenLabs. (elevenlabs.io)
• ElevenLabs SIP FQDN (ingress to ElevenLabs): Use sip.rtc.elevenlabs.io with a required identifier in the SIP URI, e.g. sip:[e-mail]:5060. Do not send to [e-mail] without an identifier. (elevenlabs.io)
• Transport and ports: TCP 5060 is supported; TLS is recommended for production (TLS port 5061). UDP is not available. Codecs: G.711 or G.722. (elevenlabs.io)
• ElevenLabs dashboard setup:
  1. Go to Agents Platform → Phone Numbers → “Import a phone number from SIP trunk.” Enter the E.164 number you’ll route from Exotel. (elevenlabs.io)
  2. Outbound (from ElevenLabs to Exotel): In “Outbound settings,” set Address to your Exotel SIP termination hostname (hostname only, not a full SIP URI). Select TCP or TLS and your media encryption policy. (elevenlabs.io)
  3. If Exotel requires digest auth, add SIP trunk username/password; otherwise use ACL/IP allowlisting per your provider. (elevenlabs.io)
  4. Assign the imported number to your agent. (elevenlabs.io)
• Static IP option (if Exotel needs IP allowlisting): Enterprise customers can use sip-static.rtc.elevenlabs.io (or regional static endpoints) which egress from a fixed /24. Contact support/sales to enable. (elevenlabs.io)
• Non-Twilio numbers: Using SIP trunking is the supported path to connect non-Twilio carriers. (help.elevenlabs.io)

That’s all you need from the ElevenLabs side; in Exotel, point your trunk’s origination to sip:[e-mail]:5060 and accept calls from ElevenLabs at your Exotel termination hostname you entered in the Address field. (elevenlabs.io)

If you need

[ocean mauve]

Can you confirm this is a elevenlabs Voicebot integration.

For Outbound calls in this case
Outbound Call Integration via Exotel Flow
When outbound calling is required from Exotel to a SIP bot:

Supported Pattern:

Use Exotel’s Make-a-Call API to dial the customer

Use a Connect Applet in the assigned Flow to bridge the call to a SIP bot (as Leg B)

API Call (Make-a-Call):

POST /v1/Accounts/<AccountSid>/Calls/connect.json

{

"From": "[phone]",

"To": "[phone]",

"CallerId": "[phone]",

"Url": "https://my.exotel.com/flow-control/flow/<flow-id>"

}

In Flow:

Use Connect Applet

Configure "Dial Whom":

sip:[e-mail]:5070;transport=tcp

Call Flow:

Exotel dials Leg A (customer)

On answer, Leg B is initiated to SIP bot

SIP INVITE goes from Exotel to the bot

This is the only supported outbound architecture (no direct SIP to Exotel supported)

This is exotel flow of doing call

[mint wave]

AI-generated Answer for buntysaini

Short answer: Partially.

What ElevenLabs officially supports

• ElevenLabs Agents support SIP trunking for both inbound and outbound calling with your existing carrier/PBX. This is documented in the SIP trunking guide. (elevenlabs.io)
• To receive a call from your carrier into an ElevenLabs voice agent, the carrier must send a SIP INVITE to the ElevenLabs SIP FQDN, including an identifier in the URI, for example:
  sip:[e-mail]:5060;transport=tcp
  Do not send INVITEs to [e-mail] without an identifier. (elevenlabs.io)
• ElevenLabs can originate outbound calls to your carrier when you configure the “Address” (hostname or IP only, not a full SIP URI) for your trunk in the Agents dashboard; you can choose TCP or TLS and optional digest/IP ACL auth. UDP is not currently available. (elevenlabs.io)
• Default endpoints/ports: sip.rtc.elevenlabs.io on TCP 5060 (TLS 5061 if enabled). Enterprise static-IP SIP endpoints are available on request (e.g., sip-static.rtc.elevenlabs.io and regional variants). (elevenlabs.io)
• ElevenLabs’ Help Center confirms non-Twilio carriers are supported via SIP trunking. (help.elevenlabs.io)

What I cannot confirm from ElevenLabs documentation

• ElevenLabs docs do not mention Exotel-specific flows, “Make-a-Call,” or a requirement that the only outbound architecture is “Exotel dials Leg A and bridges Leg B to a SIP bot.” I can’t verify that Exotel-specific pattern from ElevenLabs sources. (elevenlabs.io)

Implication for your proposed flow

• Your proposed Connect Applet target sip:[e-mail]:5070;transport=tcp is not the ElevenLabs SIP FQDN. To reach an ElevenLabs voice agent via SIP, Exotel (or any carrier) should INVITE the ElevenLabs SIP endpoint, e.g. sip:[e-mail]:5060 (or TLS 5061), with an identifier after sip:. (elevenlabs.io)

If you want me to validate an Exotel-specific configuration, please share Exotel’s SIP-trunk settings; however, I can only confirm compatibility where it aligns with the ElevenLabs SIP requirements above. (elevenlabs.io)

Sources:
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Can I connect a non-Twilio phone to ElevenLabs Agents (formerly Conversational AI)? – ElevenLabs
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation

[ocean mauve]

I want to do this for outbound calls