Webex Calling in India: What DoT Licensing and TRAI Rules Actually Mean for Your Deployment

Cloud Calling India Compliance

By Kunal Gill, Head, Proactive's Collaboration Practice · Updated June 2026 

 
Up Front 

Deploying Webex Calling in India requires more than a Cisco subscription and a QoS policy. The Department of Telecommunications has specific licensing expectations for OTT communication services, TRAI's interconnection framework governs how cloud calling platforms connect to the PSTN, and data localisation obligations are still evolving in ways that affect call record storage. Most UCaaS vendors mention none of this in their sales cycle. Most IT teams discover all of it three months after go-live. 
 
A finance director in Hyderabad once told me that her company's Webex Calling deployment had gone "perfectly", right up until the day a DoT notice arrived asking why they had activated voice services over the internet without OTT registration. The migration had taken six weeks. The retroactive compliance exercise took four months and cost more than the platform itself. The vendor was nowhere to be found. 
 
That story is not unusual. It is, in my experience, close to the norm. 
 
India is not a hostile market for cloud calling. It is a complex one. Webex Calling is an excellent platform, proven at enterprise scale, deeply integrated with Cisco's Collaboration portfolio, and genuinely suited to the hybrid work patterns that now define the Indian IT/ITeS sector. The regulatory layer around it, though, is one that Cisco's global documentation does not fully address and that most system integrators are not equipped to navigate. If you are a CIO or Telecom Manager evaluating Webex Calling in India, this is the briefing you should have received before the shortlisting began. 

The DoT OTT Framework Is Not Optional; It Is Just Poorly Communicated 

The Department of Telecommunications classifies Webex Calling as an OTT Communication Service. Under the Telecom Regulatory Authority of India Act and subsequent DoT directives, entities providing voice communication services over the internet to subscribers in India are required to register as OTT Communication Service Providers. This is distinct from a Unified Licence, it is a registration obligation, and it carries its own compliance conditions. 
 
The confusion arises because Cisco, as the platform provider, holds its own licensing arrangements. Many IT teams assume, reasonably but incorrectly, that purchasing Webex Calling through a Cisco partner transfers all regulatory obligations to Cisco. It does not. The enterprise deploying the service, your organisation, bears primary compliance responsibility for how that service is used within India's telecommunications jurisdiction. 
 
What this means practically: before you port a single DID number to Webex Calling and instruct your employees to make external PSTN calls through it, your legal and IT teams need to confirm the OTT registration status of the deployment and document the compliance position. If your deployment is internal-only, no PSTN breakout, no calls to external numbers, the obligation is narrower. The moment you introduce PSTN connectivity, which is the point of a cloud calling platform, you are in regulated territory.

TRAI Interconnection Rules Govern More Than You Think 

The Telecom Interconnection Regulations govern how any voice service connects to India's public switched telephone network. For Webex Calling deployments, the relevant question is how PSTN breakout is being achieved. 
 
There are three common configurations in India: 

 
The second configuration, Local Gateway with a third-party SIP trunk, is the most common in Indian enterprise deployments. It is also where most compliance failures originate. The IT team procures a SIP trunk from a provider that holds a National Long Distance licence but lacks the Access Services licence required for local PSTN termination in specific circles. Calls work. The compliance gap is invisible until it is not.

Data Localisation: The Obligation That Is Still Being Written

India's Digital Personal Data Protection Act (DPDP Act), enacted in 2023, does not prescribe blanket data localisation for all categories of personal data. The specific localisation obligations will be defined through subordinate rules that were, as of mid-2025, still under finalisation. This does not mean the question is irrelevant; it means your compliance position needs to be actively maintained as the rules are published. 
 
For Webex Calling, the data categories that attract scrutiny are call detail records (CDRs), voicemail content, call recordings (if enabled), and directory information. Cisco's Webex infrastructure has a data centre presence in India, and it is possible to configure tenants with data residency preferences. The critical point is that this configuration is not the default. It must be explicitly specified during deployment and verified against Cisco's compliance documentation at the time of go-live. 
 
If you operate in BFSI, healthcare, or any sector with additional data protection obligations — RBI's IT governance guidelines, IRDAI's cloud policy, DISHA for health data — the data residency question carries regulatory weight beyond the DPDP Act. Your Webex Calling deployment configuration must be aligned with your sectoral compliance framework, not just your UCaaS vendor's standard offering.

What RingCentral, Microsoft Teams Calling, and Zoom Phone Do (and Don't) Address

In the interest of completeness: Webex Calling is not the only platform facing these questions in India. RingCentral, Microsoft Teams Calling, and Zoom Phone all operate in similar regulatory territory. RingCentral has faced its own India-specific licensing questions around PSTN access and tends to rely heavily on local carrier partners for termination. Microsoft Teams Calling, when deployed with Operator Connect or Direct Routing, places significant compliance responsibility on the chosen operator and on the enterprise's IT governance framework. Zoom Phone's India data residency options are more limited than Webex's at enterprise scale. 
 
The point is not that Webex Calling regulations in India are uniquely complex; it is that this compliance layer exists across all UCaaS platforms and is, across the board, systematically underserved by global vendor documentation. 
 
The platform that suits your organisation is the one your team can deploy compliantly, at your scale, with your existing PSTN and PBX infrastructure. That evaluation cannot happen without the regulatory groundwork. 

The Compliance Conversation Should Happen Before the PO

Here is what a pre-deployment regulatory checklist for Webex Calling in India looks like in practice: 
 

 
Proactive Data Systems has been deploying Webex Calling for enterprise clients across India since the platform's introduction in this market. Since our founding in 1991, the pattern holds for all IT Infra portfolios: the compliance conversation that happens before the purchase order costs an afternoon. The compliance conversation that happens after a regulatory notice costs months and, frequently, considerably more than the platform itself. 
 
The Hyderabad company I mentioned at the outset was not negligent. They were not unsophisticated. They were served by a vendor and an integrator who treated India as a global template deployment rather than a distinct regulatory environment. That is a choice you can make differently.

Webex Calling is a capable, enterprise-grade platform. India's regulatory environment is navigable. The combination requires preparation that most vendors will not provide and that most IT teams cannot reasonably be expected to know without it. 
 
If your organisation is evaluating or currently deploying Webex Calling in India, Proactive Data Systems will walk through the regulatory and technical groundwork with you before the porting and before the go-live date, which becomes a compliance problem. We have been doing this since 1991. The call you make before deployment is always cheaper than the one you make after. 
 
Write to [email protected] to speak with a Proactive infrastructure advisor about your Webex Calling deployment.