> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voice.wixzel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Exotel vSIP trunk: console steps for Wixzel Voice

> Connect Exotel Virtual SIP Trunking (vSIP) to Wixzel Voice for AI calls on Indian numbers: TCP transport, the IP whitelist and the Destination URI.

Agents you build on Wixzel Voice place and answer phone calls over a SIP trunk
you bring, and Exotel Virtual SIP Trunking is one of the carriers that works
with it. Exotel bills you for the trunk and the minutes at your own rates; the
voice engine is billed per second of actual usage from your Wixzel Voice
balance. This page covers where Exotel keeps each setting. The steps that are
the same for every carrier, and the troubleshooting list, are on
[SIP trunks](/sip-trunks).

<Info>
  Allowlist **`95.216.218.102`** for outbound calls. Exotel delivers over TCP, so
  send inbound calls to **`95.216.218.102:5091`**, the TCP port, rather than the
  `5090` in `origination_uri`, which is the UDP port. Every trunk returns the
  address as `platform_ip` and `origination_uri`, so read it from
  `GET /v1/sip-trunks` rather than trusting this page to stay current.
</Info>

<Warning>
  Inbound calls over Exotel have not been verified end to end yet.
</Warning>

## How do I connect an Exotel SIP trunk to Wixzel Voice?

Exotel's trunking product is **Virtual SIP Trunking (vSIP)**, aimed at Indian
numbering. It does not take UDP: use TCP with Wixzel Voice.

<Steps>
  <Step title="Set the transport on your Wixzel Voice trunk">
    Exotel publishes `pstn.in4.exotel.com:5070` for TCP. Set `host` to
    `pstn.in4.exotel.com`, `port` to `5070` and `transport` to `tcp` on your
    Wixzel Voice trunk; leaving it on UDP will not connect.
  </Step>

  <Step title="Whitelist the platform IP">
    Exotel whitelists through a **Map ACL to Trunk** API call rather than only
    through the dashboard, and the dashboard is limited to one IP range. For
    more, their documentation directs you to contact them.
  </Step>

  <Step title="Set the Destination URI for inbound">
    Exotel's name for the origination side is the **Destination URI**. Point it
    at **`95.216.218.102:5091`** over TCP. `origination_uri` reports `5090`,
    the UDP port, which Exotel does not use.
  </Step>
</Steps>

## What else stops an Exotel call in India?

Some markets gate outbound calling behind identity checks. In India in
particular, an account that has not finished KYC (and, for many providers, DLT
registration) can hold a positive balance and still have every outbound call
cleared immediately. The portal shows the calls; it does not always show the
reason.

If an Exotel call fails some other way, work through
[When a call does not connect](/sip-trunks#when-a-call-does-not-connect).

## Related

* [SIP trunks](/sip-trunks): the allowlist, the inbound address and the
  troubleshooting list that apply to every carrier.
* [Quickstart](/quickstart): connect the trunk, register a number, create an
  agent and place a first call.
* [Exotel SIP trunk setup](https://voice.wixzel.com/integrations/exotel):
  the short version on the Wixzel Voice site, with what a minute costs on each
  voice engine.