Skip to main content
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: See 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).

​
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.
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, 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.

​
Platform Support for 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 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)
  2. Number: India number rented and KYC-verified (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