Support data sovereignty in India

India's telecom rules require both SIP signaling and RTP media for PSTN calls to stay inside the country. Use these guardrails to keep LiveKit workloads compliant while still giving customers local reach.

Can you use {project_id_without_p_prefix}.{region}.sip.livekit.cloud?

Yes—there is no plan restriction on pointing your SIP trunks at a region-specific hostname such as voiceapp-delhi.in.sip.livekit.cloud. Keep in mind:

• Redundancy trade-off. That hostname keeps traffic in the India region; if the India data center is down, calls cannot fail over elsewhere.
• Outbound trunk config. Set the destination_country field to IN so LiveKit can apply the right carrier routing rules.
• Region pinning. Pinning is only available on Scale+ plans, but most teams do not need it once they use the region-specific hostname plus destination_country.

Media anchoring requirements

For any call touching the Indian PSTN, regulators expect the entire call to stay in-country:

• Outbound calls. Your server that originates SIP to LiveKit (or Plivo) must reside in India.
• Inbound calls. The webhook or application that answers the SIP INVITE must also run on Indian infrastructure.
• No mixed conferences. Plivo forbids mixing PSTN and WebRTC legs inside one conference; doing so triggers “Violates Media Anchoring” (Hangup Code 2070).

If either signaling or media exits India, carriers may drop the call outright.

Acquire and operate Indian numbers

When renting local numbers in India through Plivo, expect a documentation review. Provide business registration, proof of address, and a clearly described use case. Regulators only approve numbers for legitimate, pre-declared workflows, so plan provisioning lead time into rollouts.

Messaging, DLT, and consent controls

• DLT registration. Every entity sending SMS into India must register the business, sender headers, and message templates on a TRAI-approved Distributed Ledger Technology portal before traffic will pass.
• Consent for marketing. Obtain explicit opt-in before firing promotional SMS or voice campaigns; keep auditable records so you can prove consent if carriers challenge a complaint.

These steps sit outside LiveKit, but skipping them is the fastest route to traffic blocks or fines.

Static egress IPs

Use static IP allow lists when Indian partners demand them. LiveKit currently advertises the same blocks per region (see the LiveKit Cloud firewall reference):

Confirm the list with Support before handing it to carriers, as allocations can change.