16 Jul India DoT Telecom Rules for Contact Centers

India DoT Telecom Rules for Contact Centers

What Is Permitted and What Is Not

A plain-language guide for contact center operators, BPOs, and enterprise IT teams

Published July 16th, 2026  |  Covers DoT OSP Guidelines 2021, TRAI Regulations, and the Telecommunications Act 2023

Running a contact center in India — or routing calls to India-based agents — sounds straightforward until you hit Indian telecom regulation. The Department of Telecommunications (DoT) has very specific rules about how calls can enter and exit India, how domestic calls must be routed, and where your voice traffic must break out to the PSTN. Breaking these rules is not a minor compliance issue: penalties include large fines, cancellation of operating rights, and even criminal liability.

The good news is that DoT has progressively liberalized its rules since 2020, making it significantly easier to operate modern, cloud-based contact centers in India. But the core restrictions around toll bypass remain firmly in place — and misunderstanding them is the most common, and most expensive, mistake operators make.

This guide explains the rules in plain language, walks through all three main call scenarios, and gives you a practical summary of what to keep on file for a DoT audit.

Who Regulates What?

Before diving into the rules, it helps to understand the two main regulators and what each one controls.

DoT — Department of Telecommunications is the government body under the Ministry of Communications. It issues telecom licenses, sets the OSP (Other Service Provider) guidelines for call centers, and enforces the rules around how voice traffic flows across India’s networks. If you operate a contact center in India, DoT’s rules govern your infrastructure and call-routing architecture.

TRAI — Telecom Regulatory Authority of India is an independent statutory body that handles tariff regulation, consumer protection, the Do-Not-Disturb (DND) registry, and rules for commercial communications. TRAI governs how you interact with customers — consent, caller ID display, calling hours, and the DND framework.

This guide focuses primarily on DoT’s rules, since they govern the technical and architectural side of call routing that most contact center operators need to get right.

Do You Need to Register as an OSP?

An OSP (Other Service Provider) is any company that uses telecom resources to provide application services — including call centers, tele-banking, tele-medicine, telemarketing, and voice-based BPO services.

Under the revised OSP Guidelines issued in June 2021, DoT made a major change: OSP registration is no longer mandatory. You no longer need to submit a registration form, pay a security deposit, or get DoT approval before operating. The catch: the rules themselves still apply in full. This is a self-governance model — DoT will not audit you routinely, but if something goes wrong, you are expected to demonstrate that you have been compliant all along.

The Central Concept: Toll Bypass

Everything in Indian telecom regulation for contact centers revolves around one idea: preventing toll bypass.

Toll bypass means routing voice calls between two points over your own private network — a VPN, an MPLS circuit, a leased line — in a way that avoids using India’s licensed telecom carriers. Doing this skips the interconnect charges that licensed carriers are entitled to, depriving them, and indirectly the government, of revenue.

In plain language: you cannot use your own private network to move a PSTN call that should be travelling through a licensed carrier’s network.

Example — not permitted A UK customer calls your toll-free number. Instead of the call transiting a licensed International Long Distance (ILD) operator when it enters India, you route it end-to-end over your own private MPLS network straight to an agent’s desk in Bangalore. No licensed gateway ever touches the call. This is illegal international toll bypass.

 

Example — permitted The same UK call transits a licensed ILD carrier at the India border. After that legal entry point, you are free to carry the call over your own internal WAN to distribute it to agents anywhere in India.

The same principle applies domestically. Receiving a Chennai customer’s call through a licensed local carrier and then distributing it over your WAN to agents in Mumbai or Delhi is fine. What is not fine is originating an outbound call to that Chennai customer from a centralized Mumbai gateway instead of a local Chennai PSTN trunk — that is national toll bypass.

Scenario 1: International Calls Coming Into India

This is the scenario most relevant to global enterprises and multinational BPOs where overseas customers are served by India-based agents.

When an international call enters India and terminates to a contact center agent, it must transit through a licensed ILD operator at the point it enters the Indian telephone network. Only companies holding a Unified License (UL) or UL-VNO International Long Distance license are authorized to carry international voice traffic into India — in practice, this means relying on carriers like Airtel, Tata Communications, BSNL, or international carriers like AT&T for that leg.

What’s permitted

• Using a licensed carrier for the international leg, with the call entering India through the ILD operator’s gateway before reaching your agents.
• Carrying the call over your own private WAN, MPLS, or VPN for internal distribution once it has already legally entered India through a licensed ILD entry point.
• Collecting incoming PSTN traffic at one TSP location, then distributing it across Indian OSP centers over any WAN technology.
• Hosting your PBX, IVR, and ACD systems outside India — one of the biggest changes from the 2021 guidelines, now available to all OSPs, not just international ones.
• Work-from-home agents connecting to a centralized hosted PBX over any technology, including broadband internet.

What’s not permitted

• Routing an international PSTN call end-to-end over your own WAN without ever transiting a licensed ILD gateway.
• Using plain internet VoIP to terminate international calls to Indian phone numbers.
• Terminating international calls directly to an agent’s personal mobile number over VoIP, without an ILD gateway in between.

Real-world example — how HPE does it correctly In HPE’s India contact center setup (via its Vonage implementation), a US customer’s call enters through AT&T’s licensed carrier network to a US-hosted PBX. The call is then distributed to India-based agents over a managed, licensed network path — not raw internet. This is compliant because the call transits a licensed carrier at every leg, the PBX being in the US is permitted under the 2021 guidelines, and India agents receive calls over a managed network rather than a PSTN-to-VoIP bridge that bypasses licensed carriers.

Scenario 2: Domestic Customer Calls Terminating Locally

This covers Indian customers calling your contact center from their own phones — the most common scenario for domestic BPOs and enterprise contact centers serving Indian markets.

The call must be received via a licensed Telecom Service Provider (TSP) holding a Unified License with Access Services. The TSP delivers the call to your contact center infrastructure, which can then distribute it to agents.

What’s permitted

• Receiving inbound calls through a licensed TSP on your toll-free or DID numbers.
• Distributing calls across multiple India locations via private WAN, once the PSTN call has been received at the TSP’s point of delivery — you don’t need a separate PSTN connection in every city.
• Hosting your ACD/PBX outside India, with the TSP delivering the call to a local Point of Presence (POP) that connects to your external PBX.
• Procuring hosted contact center infrastructure from a TSP holding a valid DoT license.

What’s not permitted

• Receiving a domestic PSTN call and bridging it to an agent over internet VoIP in a way that creates a PSTN-to-VoIP-to-PSTN path bypassing licensed interconnects.
• Taking a call that entered the PSTN in one city (say, Chennai) and routing it out of a PSTN gateway in another city (say, Mumbai) to reach a local agent — that’s national toll bypass.
• Placing a domestic VoIP-to-PSTN call-back to a customer’s mobile or landline over the public internet. The Telecommunications Act 2023 has not lifted this ban.

Scenario 3: Outbound Calls — Domestic and International

Outbound to domestic customers

Local PSTN breakout is mandatory for outbound calling. If you have agents in Mumbai, Delhi, and Chennai making outbound calls, each city must use its own local PSTN gateway. A centralized media gateway in one city cannot originate outbound PSTN calls on behalf of agents in other cities — this is the most common national toll bypass violation found during audits.

• All commercial outbound calls must display a TRAI-designated 160-series caller ID — mandatory, not a best practice.
• Outbound lists must be scrubbed against the TRAI DND registry before every campaign.
• Calls are restricted to between 9:00 AM and 9:00 PM in the recipient’s local time zone.
• Telemarketers must register through a licensed operator’s DLT (Distributed Ledger Technology) platform to get a Telemarketer ID.
• Abandoned calls in predictive dialing must ring at least 15 seconds before disconnecting; repeat calls within 72 hours of an abandoned call require a live agent guaranteed available.

Outbound to international customers

Outbound international calls must exit India through a licensed ILD operator — you cannot route them out of India directly over your own private WAN. VoIP is fine for the internal leg (agent headset to PBX); it’s the exit point at India’s border that must go through a licensed carrier. CLI presentation must be valid; benign CLI masking (a centralized trunk number) is permitted, but deliberately false or misleading CLI is not.

Quick Reference: Permitted vs Not Permitted

Scenario	Permitted	Not permitted
International inbound	Transit via licensed ILD carrier into India	End-to-end private WAN from abroad, bypassing ILD
International inbound	PBX/ACD hosted outside India	—
Domestic inbound	Receive via licensed TSP; distribute over WAN across India after PSTN entry	PSTN-to-VoIP-to-PSTN bridging that bypasses licensed interconnects
Domestic outbound	Local PSTN breakout at each agent city	Centralized gateway placing calls for multiple cities
Domestic outbound	160-series CLI for commercial calls; calls 9 AM–9 PM	Any other CLI; calls outside permitted hours
International outbound	Licensed ILD operator for PSTN exit from India	Private WAN routing of international PSTN calls out of India
Internal / VoIP	IP-to-IP calls within the contact center	VoIP-to-PSTN domestic dial-out

How the Call Must Route

The diagram below summarizes the core decision every architecture has to get right: a call must pass through a licensed gateway before it reaches an agent. A private WAN or VPN path that skips that gateway is toll bypass, regardless of which scenario it happens in.

The Telecommunications Act 2023: What Changed

India’s Telecommunications Act, 2023 came into force in June 2024, replacing the old Indian Telegraph Act of 1885. For contact centers, three things matter:

1. What changed: the Act introduces broader cybersecurity obligations. Under the Telecommunications (Telecom Cyber Security) Rules 2024, OSPs and VoIP providers must align security logging, incident reporting, and data retention with new standards.
2. What did not change: the ban on domestic VoIP dial-out to Indian PSTN numbers remains in place. New DoT authorization rules on this specific topic are still pending as of 2026.
3. What to watch for: DoT is expected to finalize service authorization rules under the new Act, particularly around SIP trunking liberalization and AI voice call regulations.

Best Practices for DoT Compliance

Because OSP registration is no longer mandatory, the audit burden falls entirely on you. If DoT or TRAI ever investigates — due to a complaint, a security incident, or a random inspection — you need to demonstrate compliance. Key practices:

• Document your full call architecture — every point where calls enter India, which licensed carrier handles the ILD leg, where PSTN gateways sit, and how WFH agents connect.
• Use only licensed carriers for every PSTN leg, domestic and international, and keep copies of their DoT licenses on file.
• Implement local PSTN breakout for every outbound city — never consolidate outbound calling through a centralized gateway.
• Keep domestic and international traffic logically separated at the infrastructure level so one stream can’t access the other’s PSTN resources.
• Retain Call Data Records, Usage Data Records, and system logs for at least one year, in IST, accessible from an India location even if your PBX is hosted abroad.
• Maintain an active Telemarketer DLT registration if you make any commercial outbound calls.
• Scrub every outbound list against the TRAI DND registry before each campaign, and keep a record of when the scrub was done.
• Maintain a WFH agent registry — name, home address, VPN IP address, and originating OSP center for every remote agent.

Three Rules to Remember

Rule 1 Every international PSTN call must enter and exit India through a licensed ILD operator. Your PBX can sit anywhere; the PSTN gateway cannot skip the license.

 

Rule 2 Every domestic outbound PSTN call must break out locally, at the city where your agent is located. No centralized gateway for multi-city outbound calls.

 

Rule 3 Keep your records for at least one year, in IST, and make them accessible from an India location. Self-governance means DoT won’t check on you proactively — but when they do, you need a complete paper trail.

The Bottom Line

DoT has made it dramatically easier to run a modern, cloud-based contact center in India — flexible PBX hosting, no mandatory registration, remote agents. But the toll bypass rule is a hard line, not a gray area. If a PSTN call ever crosses a national or international border without touching a licensed carrier’s network at that border, it’s a violation, regardless of how the rest of your architecture looks.

This blog post covers DoT OSP Guidelines (2021), TRAI commercial communications regulations, and the Telecommunications Act 2023. Regulations may change — verify current rules with DoT (dot.gov.in) and TRAI (trai.gov.in), or your legal counsel, before finalizing your architecture.