India DOT & TRAI VoIP Regulations: What Every Teams Admin Must Know Before Deploying Voice in India

India's telecommunications regulatory landscape is among the most complex in the world for VoIP deployments. Having deployed Microsoft Teams voice across multiple Indian enterprises — from Mumbai financial institutions to Bangalore IT parks to Delhi government offices — I've learned that the technical deployment is often the easy part. The regulatory compliance is where projects succeed or fail.

This guide covers everything you need to know about DOT/TRAI regulations for Microsoft Teams telephony in India — toll bypass, Location-Based Routing, CDR storage, OSP licensing, and practical compliance strategies.

The Two Regulatory Bodies You Must Understand

DOT (Department of Telecommunications)

DOT operates under the Ministry of Communications and is the licensing authority. Every telecom operator in India needs a license from DOT before providing service. DOT issues the Unified License (UL), UL-VNO (Virtual Network Operator), and International Long Distance Operator (ILDO) licenses. DOT sets the rules — and the penalties for breaking them.

TRAI (Telecom Regulatory Authority of India)

TRAI is the regulatory authority responsible for fixing tariffs, ensuring quality of service, and protecting consumer interests. While DOT makes the licensing rules, TRAI sets the pricing framework and service quality standards that all operators must follow.

Key takeaway: For Microsoft Teams deployments, you answer to both. DOT governs your licensing and interconnect compliance. TRAI governs your call routing and tariff compliance.

The Cardinal Rule: Toll Bypass is Illegal in India

This is the single most important regulation for any VoIP deployment in India, and it's where most international UC architects get caught off guard.

What is toll bypass? When a call that should traverse the PSTN (and generate toll revenue for licensed carriers) is instead routed over an IP network to avoid those charges, that's toll bypass. In most countries, this is a business optimization. In India, it's a criminal offense under the Indian Telegraph Act.

How This Affects Microsoft Teams

Consider this scenario: Your company has offices in Mumbai and Delhi. A user in Mumbai needs to call a PSTN number in Delhi.

Compliant routing: Mumbai Teams user → Mumbai SBC → Mumbai PSTN gateway → Long-distance carrier → Delhi PSTN → Destination

Non-compliant routing (toll bypass): Mumbai Teams user → WAN/Internet → Delhi SBC → Delhi local PSTN → Destination

The second scenario is illegal because it bypasses the long-distance carrier toll charges by routing the call over your private network to terminate as a local call in Delhi.

The Practical Impact

This means you cannot simply deploy a single SBC in one city and route all India PSTN traffic through it. Each location needs its own PSTN breakout through a locally licensed carrier, or you must use a carrier that handles the inter-circle routing compliantly.

Location-Based Routing: Microsoft's Compliance Solution

Microsoft developed Location-Based Routing (LBR) specifically to address India's toll bypass regulations. LBR is a mandatory configuration for any Teams Direct Routing or Operator Connect deployment in India.

How LBR Works

LBR uses the user's physical location (determined by their network subnet) to decide which PSTN gateway handles their calls. The system ensures that:

Outbound calls are routed through the PSTN gateway local to the user's current location

Inbound calls are delivered only when the user is at the location matching the called number

Call transfers to PSTN are only allowed through local gateways

Roaming users cannot make or receive PSTN calls through a gateway in a different telecom circle

LBR Configuration Requirements

To implement LBR for India, you need:

Network sites defined for each office location

Network subnets mapped to each site

Trusted IP addresses for each site's external IP

PSTN gateways tagged with their geographic location

Voice routing policies that enforce location-based decisions

Users enabled for Location-Based Routing

LBR for Operator Connect India

Microsoft also supports LBR for Operator Connect deployments in India. The configuration differs slightly from Direct Routing LBR — the operator handles the gateway-side compliance, but tenant administrators still need to configure network sites, subnets, and enable LBR for users.

CDR Storage Requirements: The Compliance You Can't Ignore

Telecom Licensees (2-Year Retention)

As of the DOT amendment dated December 21, 2021, all telecom licensees operating under a Unified License must maintain:

This was increased from the previous 1-year requirement, citing national security interests. The amendment explicitly covers internet telephony services including VoIP calls.

OSP (Other Service Provider) Requirements

If your organization operates as an OSP (BPO, call center, ITES), the requirements are slightly different:

After the 1-year period, OSPs must securely delete records and provide deletion certification.

CERT-In Requirements

For organizations classified as internet infrastructure operators, CERT-In mandates:

What This Means for Teams Deployments

Your SBC must be configured to generate and store CDRs locally. Microsoft's CQD (Call Quality Dashboard) retains call metadata, but this does not satisfy DOT's CDR requirements. You need:

SBC-level CDR logging enabled and archived

Secure storage meeting DOT standards (encrypted, access-controlled)

Retention automation — automatic archival at 6 months, retention for 2 years

Audit trail for CDR access (who accessed what records, when)

OSP Licensing: The June 2021 Reforms

The June 23, 2021 revision of OSP guidelines was a watershed moment for cloud telephony in India. Before this revision, OSP regulations were extremely restrictive — requiring dedicated leased lines, EPABX registration, and bank guarantees.

Post-Reform OSP Landscape

The 2021 reforms introduced several relaxations:

No registration requirement for OSPs (previously mandatory)

Work from home/anywhere explicitly permitted for OSP employees

VPN/Private circuits allowed for carrying voice traffic

Bank guarantee requirement eliminated

EPABX sharing between multiple OSP centers permitted

Interconnect between OSP centers within India allowed

How This Helps Teams Deployments

These reforms are what made Microsoft Teams with Operator Connect viable for Indian BPO/ITES companies. Previously, running a cloud-based phone system for a call center in India was a regulatory nightmare. Now, as long as you:

Use a DOT-licensed operator for PSTN termination

Maintain CDRs as required

Don't bypass toll regulations

Ensure agents' locations are properly tracked for LBR

...you can deploy Teams voice for OSP operations.

International Calling: ILD Requirements

For calls between India and other countries, the regulations are clear:

All international calls must be routed through a licensed International Long Distance Operator (ILDO)

Direct SIP trunking to foreign carriers is not permitted without ILD licensing

Microsoft Teams calls to international PSTN numbers from India must go through an ILDO-licensed carrier

Practical Options

Media Optimization and Toll Bypass Concerns

Media Bypass in India

Media Bypass (where RTP flows directly between the Teams client and SBC) is technically supported but creates compliance risks in India. If a user in Mumbai has Media Bypass enabled and travels to Delhi, the media stream would flow from Delhi to the Mumbai SBC — potentially constituting toll bypass.

Recommendation: Disable Media Bypass for India deployments unless you have sophisticated network controls that can dynamically adjust media paths based on user location. Use Location-Based Routing to handle this correctly.

Local Media Optimization (LMO)

LMO is a better fit for India because it routes media through the local SBC based on the user's network location. Combined with LBR, LMO ensures both signaling and media comply with toll bypass regulations.

Practical Deployment Architecture for India

Based on my deployments across Indian enterprises, here's the architecture that works:

Multi-City Deployment

For organizations with offices across multiple telecom circles:

Deploy SBCs in each major circle (or use a carrier that provides local breakout in each circle)

Configure LBR with network sites mapped to each office

Use a carrier with national coverage — Tata Communications, Airtel Business, or Reliance Jio Business

Enable CDR logging on every SBC with centralized archival

Configure separate voice routes per circle for local, national, and international calling

Single-City Deployment

For organizations in one city:

Deploy SBC pair (HA) connected to local carrier

Enable LBR even for single-site (future-proofing)

Configure CDR logging with 2-year retention

Use carrier's ILD service for international calling

Recommended Carriers for Teams in India

Common Compliance Mistakes

Using a single SBC for all India — Violates toll bypass if users are in different circles

Skipping LBR configuration — Non-compliant from day one

Not storing CDRs at the SBC — CQD data doesn't satisfy DOT requirements

Using foreign SIP trunks — Illegal without ILD licensing

Enabling Media Bypass without LBR controls — Risk of toll bypass

Ignoring OSP requirements — BPO/call centers have additional obligations

Checklist: India Compliance for Teams Voice

Before going live with Teams voice in India, verify:

Licensed carrier selected (UL or UL-VNO)

ILD operator engaged (for international calls)

LBR configured and tested

CDR logging enabled on SBC(s)

CDR retention automation set (2-year minimum)

Network sites and subnets defined

Voice routes configured per circle

Media Bypass disabled (or LMO configured with LBR)

OSP compliance verified (if applicable)

Emergency calling configured (112 is India's unified emergency number)

Final Thoughts

India's regulatory landscape for VoIP is evolving. The 2021 OSP reforms were a massive step forward, and Microsoft's investment in LBR and Operator Connect for India shows the market's importance. But compliance is not optional — the penalties for toll bypass and regulatory violations include license revocation and criminal prosecution.

Work with a regulatory-savvy carrier, configure LBR properly, maintain your CDRs, and you can run a world-class Teams voice deployment in India that's fully compliant.

If you're deploying Teams voice in India and need help with dial plans for Indian cities and area codes, SwiftM365 supports all major Indian cities with proper normalization rules — Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Pune, Kolkata, and 20+ more.

---

Have questions about India telecom compliance for Teams? Reach out via our feedback page or contact me directly at +91 9011070193.