Five steps, no guesswork — you always know exactly what comes next. Tap a step to see what it involves.
12345
You pay securely. Payment is confirmed instantly, and your receipt with the written fee breakup lands in your inbox.
Overview
For two decades, starting a call centre in India meant a pilgrimage to the Department of Telecommunications: register every OSP centre, deposit bank guarantees, declare static IPs, publish network diagrams, file periodic reports, and seek written permission before moving or transferring anything. The compliance cost of running the phones often rivalled the cost of the phones themselves.
Then, in the space of eight months, the government deleted almost all of it. The OSP guidelines of 5 November 2020 abolished registration outright. The revised guidelines of 23 June 2021 swept away what remained — the domestic/international split, the EPABX location restrictions, the interconnectivity bans, the reporting. What is left is one of the lightest telecom regulatory regimes in the world: no licence, no filings, self-regulation.
And yet the old questions keep coming. "Where do I apply for the OSP licence?" "How much is the bank guarantee now?" "My consultant says I need DoT approval for work-from-home agents." The answers are all the same — you do not, there is not one, and you do not — but the confusion is understandable. An entire advisory industry was built on the old regime, and not all of it has updated its scripts.
This page sets out the current position as it stands in 2026: what an OSP is, exactly what was abolished and when, what obligations genuinely remain, who sits inside the regime and who sits outside it, and how to set up a compliant voice operation today.
What an OSP actually is
OSP stands for Other Service Provider. In DoT terminology, it means a company or firm providing voice-based secondary or tertiary services using telecom resources — the classic examples being call centres, telemarketing operations, telebanking and telesupport desks, and telemedicine facilitation. The "other" in the name distinguishes these providers from licensed telecom service providers (the Airtels and Jios of the world): OSPs *use* telecom networks to deliver services; they do not *operate* public networks.
The single most important boundary in the current regime is voice versus non-voice. The liberalised guidelines apply to — and only to — entities providing voice-based BPO services. A software company, a data-annotation firm, a SaaS business, or any pure data/internet operation is entirely outside the OSP framework. It was never meaningfully inside it, and the 2020 guidelines made the exclusion explicit. If your agents never touch voice calls, stop reading about OSPs — this regime is not yours.
The liberalisation — what was abolished, and when
The old regime died in two instalments:
5 November 2020 — the first guidelines. The DoT issued new OSP guidelines that, at a stroke: abolished the registration requirement for OSP centres (TRAI had recommended retaining a mere "intimation" — even that was dropped); removed bank guarantee requirements; removed the static-IP requirement; removed frequent reporting obligations and the network-diagram publication requirement; removed penal provisions from the guidelines; and permitted work-from-home, including call traffic over VPN. Data-based services were taken out of the OSP ambit altogether.
23 June 2021 — "OSP Reforms 2.0". The revised guidelines finished the job: the distinction between domestic and international OSPs was removed, so one BPO centre with common telecom resources can serve customers worldwide including in India; EPABX systems may be located anywhere in the world, or at third-party data centres in India; interconnectivity between all types of OSP centres — same company, group companies, even unrelated companies — was permitted; remote agents were allowed to connect directly to the centralised EPABX (or the customer's EPABX) over any technology including broadband, without routing through an OSP centre; centralised internet connectivity via MPLS/SD-WAN was clarified as permitted; and it was expressly confirmed that non-voice entities are not governed by the OSP regime.
An analogy helps. The old regime was like requiring a driving licence to ride a bicycle — a heavy permissioned system for an activity that never justified it. The government did not merely simplify the licence test; it closed the licensing counter. But closing the counter did not repeal the traffic rules. What follows is what still applies.
What remains regulated in 2026 — the self-regulation framework
"Self-regulation" does not mean "no rules." It means the DoT trusts you to follow them without filing anything. The obligations that survive are:
Maintain the records. OSPs must maintain call detail records (CDR), usage detail records (UDR), and system logs for voice traffic, and furnish them to DoT or security agencies as and when required. Logs of activities carried out by extended/remote agents must be maintained for one year, and the guidelines expect system logs to be tamper-proof.
No toll bypass. The historic core of OSP regulation was preventing arbitrage of telecom tariffs — routing calls to dodge interconnection charges. That prohibition survives. Your architecture must not bypass the licensed telecom service providers' networks or charges.
Respect TSP jurisdiction. OSP operations must not infringe on the jurisdiction of authorised telecom service providers. You are a user of telecom resources, not a provider of telecom services to the public.
Data security norms. OSPs must abide by the data security norms prescribed by the Centre — relevant for BPOs handling customer data across borders.
Enforcement still exists. The DoT has stated that on complaints of violations, its field units in the Licensed Service Areas act under the telecom legislation in force (the PIB release cited the Indian Telegraph Act; the Telecommunications Act, 2023 has since replaced it — the enforcement machinery continues under the current law).
Telemarketing is a separate regime. If your voice operation does telemarketing, TRAI's Telecom Commercial Communications Customer Preference Regulations (TCCCPR), 2018 apply independently: registration as a telemarketer, the 140 number series for promotional calls, the 160 series for service/transactional calls, scrubbing against do-not-disturb preferences, and the associated penalties. The DoT's OSP relaxation changed nothing about TRAI's UCC framework.
Who is inside the regime — and who is outside it
Activity
OSP regime?
Notes
Voice call centre (inbound/outbound customer support)
Yes — self-regulation applies
No registration; maintain CDR/UDR/logs
Telemarketing / telesales
Yes, plus TRAI TCCCPR
DoT layer is light; TRAI layer is the real compliance
Telebanking / tele-support desks
Yes — voice-based
Same self-regulation duties
Work-from-home voice agents
Yes — expressly permitted
Direct EPABX connection allowed; 1-year logs
Pure data entry / annotation (no voice)
No — outside purview
Never needed OSP compliance
SaaS / software development
No — outside purview
Ordinary company law + tax apply
IT consulting without voice ops
No — outside purview
—
The practical test: do your people make or receive voice calls as the service itself? If yes, you are an OSP in the definitional sense, with the (light) duties above. If no, the OSP guidelines are not your problem.
Setting up a compliant voice operation — the practical checklist
There is no licence to apply for, so "getting an OSP licence" is not a step. What follows is what a well-run setup actually involves:
Step 1 — Incorporate the business entity
Register a private limited company or LLP for the BPO — the DoT layer needs no entity approval, but clients, payment gateways, and GST registration all need a proper legal entity. This is company incorporation, not telecom licensing; do not let anyone sell you the two as a bundle.
Step 2 — Decide the voice architecture
Choose how calls will flow: a cloud telephony/EPABX solution (which may sit anywhere in the world or at an Indian data centre), direct PSTN connectivity through a licensed provider, or a hybrid. The only regulatory constraint is no toll bypass — route through authorised telecom service providers.
Step 3 — Arrange telecom resources
Procure PRI/SIP trunks, toll-free numbers, or cloud telephony seats from a licensed telecom service provider or authorised reseller. Keep the service agreements — they are your evidence of legitimate telecom sourcing if questions ever arise.
Step 4 — Set up the EPABX and logging
Deploy the EPABX (on-premise, cloud, or at a third-party data centre) with CDR/UDR capture and tamper-proof system logging switched on from day one. Retrofitting logging after operations begin is where most companies fail the "produce on demand" test.
Step 5 — Define the work-from-home policy
Document which roles are remote, how remote agents connect (direct to centralised EPABX over broadband is permitted), and how their activity logs are captured and retained for one year. A written WFH/WFA policy is both an HR document and a compliance artefact.
Step 6 — Separate telemarketing compliance if applicable
If any team does promotional outreach, handle TRAI compliance separately: telemarketer registration, correct number series (140 for promotional, 160 for service/transactional), DND scrubbing, and consent records. This is the part of "call centre compliance" that still has teeth.
Step 7 — Implement data security basics
Access controls on call recordings and customer data, defined retention periods, and incident response contacts. The guidelines reference the Centre's data security norms; for BPOs serving foreign clients, map these against the client's contractual requirements too.
Step 8 — Keep the evidence file current
Maintain a single compliance file: entity documents, telecom service agreements, EPABX/network description, log-retention confirmations, WFH policy, and (if applicable) TRAI registrations. No filing is due anywhere — but if DoT or a security agency ever asks, "we maintain everything and can produce it" is the entire game.
Old regime vs new regime — the before and after
Requirement
Before November 2020
Now (2026)
OSP registration with DoT
Mandatory per centre
Abolished — no registration at all
Bank guarantee
Required
Removed
Periodic/annual reports to DoT
Required
None required
Static IP
Required
Removed
Network diagram publication
Required
Removed
Penal provisions in guidelines
Existed
Removed
Domestic vs international OSP
Separate categories, separate rules
Distinction removed
EPABX location
Restricted
Anywhere in the world, or third-party Indian data centres
Interconnectivity between OSP centres
Restricted
Permitted — even between unrelated companies
Work from home
Restricted, needed dispensations
Expressly permitted (WFH and WFA within India)
Remote agent connection
Via OSP centre
Direct to centralised EPABX over any technology
Centralised internet (MPLS/SD-WAN)
Unclear
Clarified as permitted
Data-only businesses
Grey area
Expressly outside OSP purview
Record-keeping (CDR/UDR/logs)
Required
Still required — self-regulation
No toll bypass
Required
Still required
Telemarketing (TRAI)
Separate regime
Still separate — TCCCPR 2018 applies
Common misconceptions — corrected
"I need to apply for an OSP licence before starting." No. There is no application, no portal, no certificate. Anyone telling you otherwise is selling the old regime.
"Work-from-home agents need DoT permission." No. WFH and work-from-anywhere within India are expressly permitted, and remote agents may connect directly to the centralised EPABX. What you need is logging, not permission.
"My data-entry BPO needs OSP compliance." No. Non-voice, data/internet businesses are outside the OSP purview entirely. If no voice calls are involved, the guidelines do not apply to you.
"No registration means no compliance at all." Wrong, and this is the dangerous one. The record-keeping duties (CDR, UDR, system logs), the toll-bypass prohibition, and TRAI's telemarketing rules all survive. "Nobody checks" is not a compliance strategy — DoT field units act on complaints.
"International and domestic operations need separate setups." Not anymore. The distinction was removed in June 2021. One centre, common telecom resources, global plus Indian customers.
"Cloud telephony counts as bypass." Not inherently. Using authorised cloud telephony providers and proper SIP/PSTN termination is legitimate sourcing. Bypass means engineering call flows to dodge interconnection charges — a design choice, not a technology.
Fees and timelines — the honest picture
There is no government fee because there is no licence to buy. Your setup costs are commercial, not regulatory:
Company incorporation: standard MCA fees plus professional fees for a private limited company or LLP
Telecom resources: PRI/SIP trunks, toll-free numbers, or cloud telephony seats — priced by providers, not by the government
EPABX/cloud telephony: one-time setup plus per-seat monthly costs
TRAI telemarketer registration (if doing promotional outreach): the applicable TRAI fees — separate from DoT entirely
Timelines: a voice BPO can be operationally ready in 2–4 weeks from a standing start — entity incorporation plus telecom provisioning run in parallel. There is no DoT approval clock because there is no DoT approval.
Buying telecom resources the right way
With no licence to obtain, the most consequential decision in a voice BPO setup is commercial: where your call capacity comes from. Get this right and the regulatory layer takes care of itself; get it wrong and you inherit someone else's compliance problems.
Source from licensed providers. PRI lines, SIP trunks, toll-free (1800) numbers, and cloud telephony seats should come from licensed telecom service providers or their authorised channel partners. Keep the service agreements on file — they are your proof of legitimate sourcing and the first document you would produce if questions ever arose about your call flows.
Match the technology to the operation. A 20-seat domestic support desk and a 500-seat international outbound operation are different engineering problems. Cloud telephony (per-seat, no hardware) suits variable or distributed teams, including work-from-home agents. On-premise or hosted EPABX with SIP trunks suits large fixed centres. Toll-free numbers remain the standard for inbound customer service in India. There is no regulatory preference among these — only cost, reliability, and scale.
Read the agreements for bypass risk. The contract should describe standard termination through the provider's licensed network. Be wary of arrangements promising dramatically below-market international termination rates through opaque routing — legitimate arbitrage exists in telecom, but structures designed to disguise call origin or dodge interconnection charges are exactly what the toll-bypass prohibition targets. If you cannot explain your call flow to a regulator in one paragraph, redesign it.
Plan number strategy early. Toll-free, local presence numbers, and (for telemarketing) the correct TRAI series — 140 for promotional, 160 for service and transactional calls — should be decided before agents start dialling. Renumbering mid-operation confuses customers and breaks callback workflows.
Separate voice from data budgets. Because data/internet operations sit outside the OSP regime entirely, mixed businesses should keep voice infrastructure and its logging distinct from data operations. Clean separation simplifies everything: the evidence file, the log-retention policy, and any future regulatory conversation.
Sector snapshots — how the rules land in practice
Domestic BPO (Indian customers). The archetypal call centre: customer support, collections, helpdesks. Fully within the OSP definition, fully covered by the liberalisation. One centre, no registration, WFH permitted, CDR/UDR/logs maintained. TRAI telemarketing rules apply only if the work includes promotional outreach.
International BPO (foreign customers). Serving US, UK, or other foreign clients from India. The old regime's international-OSP category no longer exists as a separate thing — the same centre, the same rules, the same absence of registration. The June 2021 removal of the domestic/international distinction was aimed squarely at this segment: no more parallel compliance tracks for serving two markets.
KPO and blended operations. Knowledge process outsourcing with voice components (analyst calls, client servicing) sits inside the OSP definition for its voice part. Pure research and analytics without voice sits outside. Most KPOs are blended — apply the voice test team by team, not company by company.
How ComplyKart helps
The OSP space is full of consultants selling obsolete licences. Our value is telling you what you do *not* need — and building what you actually do.
What we do:
Entity setup: private limited company or LLP incorporation for the BPO, with GST and Shops & Establishment registrations
Compliance architecture: WFH/WFA policy drafting, log-retention framework (CDR/UDR/system logs, one-year remote-agent logs), and the evidence file
Telemarketing layer: TRAI compliance mapping where your operation does promotional outreach — number series, DND scrubbing, registration
Contract review: telecom service agreements checked for legitimate sourcing and toll-bypass risk
Ongoing: annual compliance for the entity (ROC filings, tax filings) so the business layer stays clean
What we do not do:
We do not "obtain" OSP licences — there is nothing to obtain, and anyone offering to is misrepresenting the law
We do not file anything with DoT on your behalf — there is nothing to file
We do not advise on evading interconnection charges or designing toll-bypass architectures
We do not replace your telecom vendor's technical implementation — we handle the legal and compliance layer
Sources
Department of Telecommunications — OSP Guidelines, 5 November 2020 (registration abolished; bank guarantees, static IPs, periodic reports, network diagrams, penal provisions removed; WFH permitted; data services out of ambit)
Department of Telecommunications — Revised OSP Guidelines, 23 June 2021 ("OSP Reforms 2.0": domestic/international distinction removed; EPABX anywhere; interconnectivity permitted; remote agents direct EPABX connection; SD-WAN clarified; non-voice entities expressly excluded)
Press Information Bureau Release ID 1812280 (1 April 2022) — Rajya Sabha reply summarising the OSP reforms; self-regulation basis; CDR/UDR/system-log maintenance; DoT field-unit enforcement
NASSCOM community summary of OSP Reforms 2.0 (June 2021) — remote-agent direct connection; OSP–non-OSP interconnectivity; centralised internet; non-voice exclusion
Telecommunications Act, 2023 — replaced the Indian Telegraph Act, 1885
FAQ
Frequently asked questions
28 answers from our consultants.
You pay for our expert's time — document checking, filing, follow-ups — not the government. The government fee goes to the government; our fee is for the work we do so you don't have to figure it out yourself.
Tell us your situation in plain words — what you're trying to do, not which form you think you need. Half our job is stopping clients from buying the wrong service. The first consultation is free and honest.
Yes. We quote professional fee + government charges + taxes separately, in writing, before you pay. The number doesn't change midway. If the government fee changes, we show you the notification.
Every engagement gets a tracker — you see what's filed, what's pending and what's next. No chasing on WhatsApp for status updates.
Both. Startups get incorporation + early compliance bundles; established companies get annual retainers. About half our clients started with us at incorporation.
Yes — MCA, GST and income tax are central systems, so location doesn't matter for most filings. We're Delhi-based but serve clients across India. State-specific licences (Shops & Establishment, Professional Tax) we handle through our network.
That's most of our cleanup work. We assess the backlog, calculate exact late fees, file everything in the right order and get you current. No judgment — it happens more than you'd think.
Working hours: you can reach us on phone and WhatsApp, and a real person from the team replies to every message. Filings are done on the committed timeline, not 'whenever'. If we need more time, we tell you before the deadline, not after.
No. Everything — documents, signatures, payments — works digitally. DSC-based filings don't need physical presence. Some clients never visit and that's fine.
No. OSP registration was abolished on 5 November 2020 and the June 2021 revised guidelines confirmed it. There is no licence to apply for, no portal to file on, and no certificate to hold. Incorporate your company, arrange telecom resources from licensed providers, and operate under the self-regulation framework.
No. Non-voice, data/internet businesses are expressly outside the OSP purview. The 2020 guidelines made this explicit. Your compliance universe is company law, tax, labour, and data protection — not DoT.
Yes — work from home and work from anywhere within India are expressly permitted. Remote agents may connect directly to the centralised EPABX (or the customer's EPABX) over any technology, including broadband. Maintain their activity logs for one year.
No periodic or annual filings exist anymore. The regime is self-regulatory: maintain CDR, UDR, and system logs, and produce them if DoT or a security agency asks. "No filing" is not "no records."
Engineering your call flows to avoid paying the interconnection charges that licensed telecom operators are entitled to — for example, disguising international calls as domestic ones. It was the original sin the OSP regime policed, and the prohibition survives the liberalisation. Route through authorised providers and the question never arises.
Yes. The June 2021 guidelines removed the domestic/international distinction entirely. A single centre with common telecom resources can serve customers worldwide, including in India.
Anywhere in the world, or at a third-party data centre in India. You may also use your telecom service provider's EPABX services. The old location restrictions are gone.
Call detail records and usage detail records for voice traffic, tamper-proof system logs, and one-year activity logs for remote/home agents. Keep them organised and retrievable — "produce on demand" is the operational standard.
Yes, to the extent they are voice-based operations — they fall within the OSP definition. The same light-touch duties apply: records, no toll bypass, data security norms.
Separate track, still fully in force. TRAI's TCCCPR (2018) requires telemarketer registration, the 140 series for promotional calls, the 160 series for service/transactional calls, DND scrubbing, and consent management. The DoT relaxation did not touch any of this — budget for TRAI compliance independently.
Yes. Interconnectivity between OSP centres of the same company, group companies, or completely unrelated companies is permitted for voice and data. This was one of the June 2021 clarifications.
Yes. The 2020 guidelines expressly permitted call traffic over VPN, which lets OSPs integrate international locations with Indian operations. Bypassing international long-distance providers remains prohibited — VPN for connectivity is fine; VPN for tariff arbitrage is not.
DoT field units in the Licensed Service Areas can act on complaints under the telecom legislation in force. In practice, complaints arise around toll bypass, unsolicited calls (which route to TRAI), or security concerns. A clean evidence file — agreements, logs, policies — is your defence.
No. Bank guarantees were removed in the 2020 guidelines and never reinstated. If a consultant quotes you a "DoT bank guarantee," you are being sold history.
Yes. The June 2021 guidelines clarified that centralised internet connectivity using MPLS/SD-WAN is permitted, and OSP centres may share internet from a centralised location.
The regime covers voice-based BPO services; pure data/internet (non-voice) entities are outside it. Internet calling as the *service* in a voice BPO sits in the voice camp; a business whose agents never handle voice calls sits outside. When in doubt, the test is whether voice is the service, not the transport.
Two to four weeks from a standing start is realistic — company incorporation and telecom provisioning run in parallel. There is no DoT approval stage, so nothing waits on the government beyond standard incorporation timelines.
The guidelines' own penal provisions were removed in 2020. That does not mean violations are consequence-free — general telecom law, TRAI regulations, and contractual liability with your telecom providers all still bite.
There is nothing to surrender — the registration requirement was abolished, not converted. Your old registration certificate is a historical document. Operate under the current self-regulation framework; no closure filing exists for a regime that no longer requires entry.
What clients say about working with us
Real stories from businesses we've worked with.
Trademark Registration“
Our Trademark was applied in all the classes with a short span of time by Complykart Trademark Experts and I can say the level of expertise and commitment they carry is remarkable. It's an A+ from my side. We are now sticking to ComplyKart only.
Company Registration“
I found the professionalism of the staff at complykart.com, a pleasure to work with. As a foreigner to India, they took the time to explain the documentation and assisted in every question I raised. I was pleased that complykart.com made it easy for my Business.
Merger & Acquisition“
Trust, Commitment, Dedication and responsiveness are the best things with ComplyKart. Thanks for handling our Merger assignment with so much care. After my business disputes, complykart handles all things with own sense of understanding.
Company Law Specialist · Company Law & ROC Compliance · 10+ years experience
Naman Agarwal specialises in company law and ROC compliance. He manages incorporations, annual filings (AOC-4, MGT-7, ADT-1), board processes and statutory registers for private limited companies, LLPs and Section 8 companies.
Last reviewed: 16 November 2026
Get a free consultation
Talk to a ComplyKart professional about OSP/DOT Liscence. The first consultation is free.