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

# Calling in India

> Regulatory requirements for AI voice agents handling calls to or from India over Plivo SIP trunking

India regulates voice traffic more strictly than most countries. If your agent makes or receives calls involving Indian phone numbers, both your Plivo setup and your orchestration platform must meet TRAI (Telecom Regulatory Authority of India) requirements. This page consolidates everything that applies to the SIP trunking path.

***

## The Media Anchoring Rule

TRAI regulations require voice traffic for India calls to be anchored on servers located in India. For a SIP trunking voice agent, that means **your orchestration platform must terminate SIP and media on infrastructure in India**. A platform deployment in another region cannot legally carry the call.

Calls that violate this fail rather than degrade:

| Symptom              | Meaning                                                                |
| -------------------- | ---------------------------------------------------------------------- |
| Hangup code **4590** | India media anchoring violation: the platform endpoint is not in India |

See [Hangup codes](/voice-agents/sip-trunking/troubleshooting/hangup-codes) for the full list.

Meeting the rule takes two things: your Plivo account anchored in India (below) and your platform terminating in India ([platform support](#platform-support-for-india)).

***

## Your Plivo Account Data Region

You choose a data region when you create your Plivo account. For India calls, the data region must be **India**: this is what anchors the Plivo side of your calls in-country, in Plivo's Mumbai region. Indian phone numbers are also available only to India data region accounts.

<Warning>
  The data region of an organization cannot be changed after it is created. If your organization is in another data region, create a new one under the same login: in the [Plivo Console](https://cx.plivo.com/home), open the organization switcher at the top of the left menu, select **Create New Organization**, and choose **India** as the Data Region. No new signup is needed.
</Warning>

***

## Platform Support for India

| Platform       | India support          | What you need to do                                                                                                                   |
| -------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **LiveKit**    | ✅ Via region pinning   | Enable [region pinning](https://docs.livekit.io/telephony/features/region-pinning/) for your LiveKit project                          |
| **ElevenLabs** | ✅ Via India deployment | Contact ElevenLabs sales for an India deployment, then use the India SIP URI: `sip.rtc.in.residency.elevenlabs.io:5060;transport=tcp` |
| **Vapi**       | ❌ Not supported        | Indian phone numbers are not compatible with Vapi, which does not currently offer SIP termination in India                            |

***

## India Phone Numbers

Renting an India number on Plivo requires KYC verification before purchase, with documentation requirements that depend on your business's location. See [Rent India Numbers](/numbers/rent-india-numbers) for the full process.

***

## Checklist for India Traffic

1. **Account**: Plivo account created with the **India** data region (cannot be changed after signup; see [above](#your-plivo-account-data-region))
2. **Number**: India number rented and KYC-verified ([Rent India Numbers](/numbers/rent-india-numbers))
3. **Platform region**: platform deployment or region pinning set to India (table above)
4. **Trunk URI**: inbound trunk points at the SIP endpoint that carries your platform's India traffic, whether that is a dedicated India URI or your project's standard endpoint with the India region enabled
5. **Test**: place a test call and confirm no 4590 hangups in [debug logs](https://cx.plivo.com/sip-trunking)

***

## Related

* [Hangup codes](/voice-agents/sip-trunking/troubleshooting/hangup-codes) - Including 4590 and other India-relevant codes
* [Rent India Numbers](/numbers/rent-india-numbers) - KYC process for India numbers
* [Integration guides](/voice-agents/sip-trunking/overview) - Platform-specific setup, including India URIs