Connect ElevenLabs to Indian Telephony via AgentStream

If you are planning an elevenlabs sip integration for India, design the telephony layer before you configure the bot. Indian phone numbers, caller ID rules, SIP routing, and PSTN handoff all affect whether calls connect cleanly, show the right number, and reach the right flow. The safer approach is to set up Exotel and AgentStream around Indian routing requirements first, then connect ElevenLabs into that path.

This guide covers the full setup for inbound, outbound, and mixed call flows. It includes prerequisites, Exotel number and routing setup, how to connect ElevenLabs over SIP, where AgentStream sits in the call path, what to test before launch, and the issues teams most often hit during rollout.

Plan ElevenLabs SIP integration around Indian number and routing requirements

A generic SIP setup guide usually starts with credentials. In India, that comes too late. The first decision is how calls enter and leave the network.

Indian telephony has practical constraints that shape the design:

• Your Phone Number Strategy Matters. You need to know whether you are attaching a virtual number, DID, toll-free number, or an existing business line strategy to the flow.
• Caller ID Must Be Planned Early. Outbound calls need the right presentation number and routing logic from day one, especially if you want a consistent customer callback path.
• Inbound And Outbound Often Need Different Logic. The number a customer dials for support is usually not the same as the path you use for outbound reminders, verification, or service calls.
• Regional And Language Routing Can Affect The Bot Flow. If your business handles English, Hindi, Hinglish, or segment-based call paths, the telephony design should support that split before the ElevenLabs side goes live.
• Compliance And Audit Needs Should Be Baked In. If the call type touches regulated workflows, recording, consent language, and script control should be considered up front.

This is where Exotel helps as the India-facing telephony layer. Instead of forcing a direct one-size-fits-all setup between ElevenLabs and the public phone network, use Exotel to handle the Indian telephony side and AgentStream to route calls into the right voice experience.

For most teams, the architecture looks like this:

• A Customer Call Reaches An Exotel Number Or Exotel Places The Outbound Call.
• Exotel Routes The Live Call Through AgentStream.
• AgentStream Connects The Session To The ElevenLabs SIP Endpoint Or Bot Flow.
• The Bot Handles The Conversation, While Exotel Continues To Manage PSTN Connectivity.
• The Call Can Be Transferred, Escalated, Or Logged Based On Your Business Logic.

That split matters. Exotel handles the Indian numbering and network layer. ElevenLabs handles the conversation. AgentStream sits in the middle as the real-time bridge and routing layer that makes the end-to-end call flow workable.

Choose the right call flow for inbound, outbound, or both

Before you enter any SIP trunk details, decide what kind of call journey you need.

Inbound call flow

An inbound setup fits best when customers call a published Indian number and expect an automated voice experience first. In that model, Exotel receives the call on your number, applies routing logic, and passes the session through AgentStream into ElevenLabs.

This flow works well for:

• Customer Support Front Door.
• Lead Qualification Lines.
• Service Appointment Or Status Queries.
• After-Hours Call Handling.

Inbound routing often needs one or more pre-bot decisions. You may want to identify the dialed number, map it to a business unit, insert a greeting, or separate premium customers from general traffic before handing the call to the bot.

Outbound call flow

Outbound flows start from your application or campaign orchestration layer. Exotel places the call using the configured Indian caller ID path, and when the customer answers, AgentStream routes the live session to ElevenLabs.

This flow is common for:

• Payment Reminder Calls.
• Verification Calls.
• Appointment Reminders.
• Delivery Updates.
• Lead Re-Engagement.

Outbound design needs more attention on caller ID, answer detection, retry logic, and fallback actions. If the bot cannot continue, the call should either transfer to a live team, schedule a callback, or end cleanly with the right status logged. For collections or other regulated outreach, pair automation with consent, audit-ready recording, script adherence, and regulatory alignment.

Mixed inbound and outbound flow

Some teams need both. That is normal. It should not be treated as one universal route. Inbound and outbound usually need separate routing rules, separate numbers, and sometimes separate ElevenLabs agents.

A mixed design is easier to run when you define:

• Which Numbers Accept Inbound Calls.
• Which Numbers Present On Outbound Calls.
• Which AgentStream Route Handles Each Journey.
• Which ElevenLabs Agent Or Prompt Is Used For Each Intent.
• Which Fallback Action Applies If The Bot Cannot Complete The Task.

That structure keeps your elevenlabs telephony india setup readable for engineering and operations teams.

Prerequisites for ElevenLabs, Exotel access, and AgentStream

You can move faster if you confirm access and ownership before opening any admin console.

ElevenLabs prerequisites

Make sure you have:

• An Active ElevenLabs Account With SIP Capability Enabled.
• The Agent Or Voice Workflow You Intend To Use For Calls.
• Access To SIP Settings, Authentication Details, And Endpoint Information.
• A Clear Prompt Or Agent Design For Phone Conversations.
• A Defined Fallback Behavior For Silence, Interruptions, And Transfer Requests.

Phone calls are less forgiving than web testing. Shorter prompts, clearer turn-taking, and direct confirmation steps work better on the PSTN.

Exotel prerequisites

On the Exotel side, confirm that you have:

• Access To The Exotel Account And The Correct Workspace Or Project.
• An Indian Number Or Number Plan Mapped To The Use Case.
• Permissions To Configure SIP Trunks, Routing, And AgentStream Flows.
• The Right Regional Telephony Setup For Your Business Operation.
• A Test Team That Can Place And Receive Real PSTN Calls In India.

If your business has separate inbound and outbound teams, align them before setup starts. Many rollout delays come from number ownership confusion, not SIP itself.

AgentStream prerequisites

For AgentStream, prepare:

• The Intended Call Routing Logic.
• The Flow Or Connector Configuration That Will Hand Calls To ElevenLabs.
• Any Metadata You Want To Pass Into The Session.
• Rules For Retry, Timeout, Escalation, And Fallback.
• Logging Access For Session-Level Troubleshooting.

If you already run other AI call paths, keep the ElevenLabs flow isolated during testing. A clean test route is easier to validate than a shared production route with many branching conditions.

Configure Indian telephony in Exotel before touching ElevenLabs

This is the part many teams rush through. It should come first.

Start by deciding which Indian numbers will be used and what each one does. If a number exists only for outbound CLI presentation, do not reuse it for general inbound support unless that is business-approved. If a number is for inbound automation, document where unanswered calls, overflow calls, and transfer requests should go.

Work through the Exotel telephony setup in this order.

Map numbers to use cases

Create a simple mapping table internally with:

• Number.
• Purpose.
• Inbound Or Outbound.
• Business Unit.
• Language Or Geography.
• Fallback Destination.

That one document prevents most routing mistakes later.

Set caller ID and presentation rules

For an elevenlabs indian phone number use case, the visible customer-facing number matters as much as the bot logic. Decide which approved number should appear on outbound calls and where callbacks should land if the customer dials back.

If you use one number for outreach and another for inbound service, design the callback experience on purpose. Customers often return missed or disconnected calls, and that callback path should not dead-end.

Define inbound entry logic

For inbound traffic, configure the first routing step in Exotel before involving ElevenLabs. Common entry logic includes:

• Time-Based Routing.
• Region Or Queue Split.
• Language Selection.
• Priority Handling.
• A Direct Branch Into AgentStream.

Keep this first layer simple. If the bot is meant to handle the initial interaction, avoid stacking too many IVR steps before the handoff.

Align recording and compliance settings

If the call flow requires recording, disclosures, or audit-ready controls, enable and review those before test traffic begins. This is especially relevant for BFSI, lending, verification, collections, and other regulated contact workflows. These controls support compliance operations but do not guarantee compliance or legal suitability for every use case.

Prepare a clean test number

Reserve at least one number or route for staging or controlled testing. Using a live production path too early can create confusion in reporting and lead to avoidable customer exposure.

Once the Indian telephony side is stable, you are ready for the ElevenLabs connection.

Connect ElevenLabs over SIP to Exotel

Now move to the SIP layer. The goal is simple: Exotel should be able to route the audio session into ElevenLabs through the approved SIP path, and ElevenLabs should accept and process that session correctly.

Exact credentials and field values can vary by account setup, so use Exotel support documentation for the live configuration values. The blog-level process is consistent.

Step 1: Gather the SIP connection details

Collect the required details from ElevenLabs and Exotel before configuration starts. This usually includes:

• SIP URI Or Target Endpoint.
• Authentication Username.
• Authentication Password Or Secret.
• Any Required Domain Or Realm Value.
• Codec Expectations.
• Transport Requirements.
• Allowed Source IP Or Security Constraints, If Applicable.

Do not copy sample values from another platform integration. A small mismatch in endpoint formatting or auth fields can block registration or call setup.

Step 2: Create or configure the SIP trunk in Exotel

In Exotel, create the SIP trunk or connection object that points to ElevenLabs. Enter the connection details exactly as provisioned and label the trunk clearly so it is easy to identify in routing.

Good naming matters. A label such as “Inbound Support Bot ElevenLabs Prod” tells operations, QA, and developers what the trunk is for without opening the config.

Step 3: Match codec and media expectations

Audio issues often start here, not in the bot prompt. Confirm that both sides support the same codec path and that there is no mismatch in sample rate or media negotiation assumptions.

If you have a choice, start with the codec profile recommended in the vendor setup documentation and avoid custom changes during the first round of testing.

Step 4: Validate authentication and reachability

Before a real PSTN test, validate that the SIP trunk is reachable and that authentication succeeds. If the connection is IP-restricted, make sure the allowlist is correct on both sides.

Step 5: Place a controlled internal test

Run a limited test route through the new elevenlabs sip trunk india setup and verify the basics:

• The Call Connects.
• The Session Reaches The Correct ElevenLabs Agent.
• Audio Is Two-Way.
• The Bot Speaks At The Expected Point In The Flow.
• Timeout And Error Behavior Are Predictable.

If any of those fail, stop and fix the trunk before adding AgentStream logic around it.

Attach AgentStream so calls reach the right bot flow

Once the SIP connection is working, AgentStream becomes the traffic controller.

AgentStream should take the incoming Exotel telephony session and route it to the right ElevenLabs path based on your business rules. That may be a single flow in a simple deployment, or multiple flows split by number, language, queue, or campaign.

Build the routing logic in layers

A clean AgentStream setup usually has three layers:

• Entry Rule. Identify where the call came from and what kind of session it is.
• Bot Route. Send the call to the correct ElevenLabs agent or prompt configuration.
• Fallback Route. Decide what happens if the session drops, times out, or needs a human handoff.

This layered setup makes debugging much easier than a flat flow with many embedded conditions.

Pass useful metadata into the call

If supported in your design, pass session context such as:

• Dialed Number.
• Campaign ID.
• Customer Segment.
• Language Preference.
• CRM Identifier Or Lead ID.

That context lets the bot greet correctly, pull the right workflow, and cut unnecessary questions.

Separate bot logic from routing logic

Keep telephony routing in Exotel and AgentStream. Keep conversational behavior in ElevenLabs. Teams get into trouble when they try to hard-code telephony decisions inside bot prompts.

A clean exotel agentstream elevenlabs design makes ownership clear:

• Exotel Owns PSTN Connectivity And Number Routing.
• AgentStream Owns Real-Time Session Orchestration.
• ElevenLabs Owns The Conversational Exchange.

That separation helps when you need to change one layer without rebuilding the whole path.

Use a test-call checklist for Indian PSTN scenarios

A lab test is not enough. You need real PSTN calls placed from Indian numbers and to Indian numbers.

Use this checklist before approving the setup.

Connectivity and routing

• Call The Published Number From At Least Two Different Mobile Networks.
• Confirm The Call Reaches The Correct AgentStream Route.
• Verify That Each Number Maps To The Intended Bot Flow.
• Test Both Peak And Off-Hours Routing Rules, If Applicable.

Caller ID and callback behavior

• Check The Presented Caller ID On Outbound Calls.
• Return A Missed Call To Confirm The Callback Path.
• Verify That A Callback Lands In The Right Queue, Bot, Or Fallback Flow.

Audio quality and conversation behavior

• Confirm Two-Way Audio From Start To Finish.
• Check For Delayed Greetings, Clipping, Or Long Pauses.
• Test Interruption Handling During Bot Speech.
• Try Silence, Background Noise, And Short Answers.
• Confirm DTMF Expectations If Any Part Of The Flow Uses Keypresses.

Edge-case handling

• Drop The Call Mid-Conversation And Review The Session Logs.
• Test Timeouts And No-Answer Cases.
• Trigger A Human Escalation Path.
• Check What Happens If The Bot Cannot Understand The Caller.
• Verify That Duplicate Or Parallel Calls Follow The Intended Rule Set.

Reporting and traceability

• Confirm Call Records Match The Actual Customer Journey.
• Check Recording Availability, If Enabled.
• Make Sure Session IDs Can Be Traced Across Exotel, AgentStream, And ElevenLabs.

This test pass is where most issues show up in a connect elevenlabs to phone number project. Better to find them here than under live traffic.

Troubleshooting caller ID, registration, audio, and routing problems

Even a good setup can fail in predictable ways. Most issues fall into four buckets.

Caller ID problems

If the wrong number appears, or no usable callback path exists, check:

• Which Number Is Assigned For Outbound Presentation.
• Whether The Route Uses The Intended Exotel Number Pool.
• Whether The Callback Path Was Mapped For That Number.
• Whether Inbound And Outbound Flows Were Accidentally Mixed.

Caller ID problems are usually configuration errors, not SIP failures.

SIP registration or authentication failures

If the trunk refuses to connect or calls do not establish, inspect:

• Username And Password Accuracy.
• Realm, Domain, Or URI Formatting.
• Allowed IP Configuration.
• Transport Or Port Mismatch.
• Expired Or Replaced Credentials.

Keep one source of truth for credentials. Shared screenshots and copied notes cause more errors than teams expect.

One-way audio or poor audio quality

If one side cannot hear the other, or speech sounds clipped or delayed, review:

• Codec Compatibility.
• Media Negotiation.
• Network Path Stability.
• Firewall Or NAT Behavior.
• Silence Detection Or Timeout Settings.

Do not try to fix poor media by rewriting the prompt. Prompt changes do not solve transport problems.

Routing mistakes

If the wrong bot answers, the wrong prompt plays, or calls disappear into the wrong branch, inspect:

• Dialed Number Mapping.
• AgentStream Branch Conditions.
• Campaign Or Metadata Assignment.
• Default Fallback Route.
• Testing Against The Wrong Environment.

A staging number hitting a production bot is one of the most common rollout errors in an elevenlabs telephony india deployment.

Operational checks to complete before production traffic

A successful test call does not mean you are ready for launch. Production needs an operating model, not just a working trunk.

Run through these checks before go-live.

Confirm ownership across teams

Define who owns each layer:

• Telephony Configuration.
• SIP Credentials.
• AgentStream Routing.
• Bot Prompts And Behavior.
• Escalation To Human Agents.
• Monitoring And Incident Response.

If a live call fails, the team should know exactly who responds first.

Set thresholds for failure handling

Agree on what should happen if:

• The Bot Does Not Answer.
• The SIP Trunk Is Unreachable.
• Audio Quality Drops Below An Acceptable Level.
• A Customer Requests A Human.
• The Session Exceeds The Intended Duration.

Fallback paths should be configured before launch, not invented during an incident.

Review reporting and quality checks

Make sure you can answer these questions on day one:

• How Many Calls Reached The Bot Successfully?
• How Many Dropped Before Conversation Start?
• How Many Required Human Transfer?
• Which Numbers And Routes Had The Highest Failure Rate?
• Can QA Review Recordings And Session Logs Together?

Start with controlled traffic

Avoid sending full production volume immediately. Start with a narrow launch window, a limited number range, or a low-volume campaign first. That gives your operations team room to watch the call path, catch routing edge cases, and tune the experience before scale increases.

Keep the documentation current

Your internal runbook should include:

• Current Number Mappings.
• SIP Trunk Labels And Purpose.
• AgentStream Route Names.
• Fallback Rules.
• Escalation Contacts.
• Known Limitations And Recent Changes.

That discipline matters more than many teams expect. Most production confusion happens after a change, not during the first setup.

FAQs