Skip to content 
AI Summary: This article explains the 160 series numbers for government entities in India under TRAI’s outreach mandate, including how the Department of Telecommunications (DoT) assigned the 160xxxxxxx series to central and state government departments and Public Sector Undertakings for service and transactional voice calls. TRAI confirmed this mandate through its NASSCOM-published guidance (February 2026) and the DoT Press Release dated 30 May 2024 (PRID 2022249), establishing that government calls must originate from verified 160-series numbers so citizens can distinguish them from spam. Central and state agencies, PSUs, and e-governance bodies must register on the Distributed Ledger Technology (DLT) platform, obtain 1600-series numbers from a Telecom Service Provider (TSP), and route all outbound citizen-outreach calls exclusively through those numbers. FreJun provisions and manages 160-series numbers for eligible government entities, handling DLT integration, template registration, and call routing on a single platform.
Key Facts at a Glance
| Item | Detail |
|---|---|
| Regulation | TCCCPR, 2018 (Second Amendment, 12 Feb 2025) |
| Governing bodies | TRAI / DoT |
| Applies to | Central and state government departments, PSUs, government agencies making service or transactional calls to citizens |
| Number series | 160xxxxxxx (government outreach sub-range) |
| First-violation penalty | ₹2,00,000 per instance (TCCCPR Second Amendment, 12 Feb 2025) |
| Mandate confirmed | DoT Press Release, 30 May 2024 (PRID 2022249); NASSCOM guidance, Feb 2026 |
| Entity count (as of Dec 2025) | Approximately 570 entities across BFSI and government have adopted 1600-series numbers, subscribing to over 3,000 numbers |
- The DoT assigned the 160xxxxxxx numbering series to government entities so citizens can immediately recognise legitimate outreach calls and distinguish them from spam.
- Central departments, state agencies, and PSUs making service or transactional calls must register on the DLT platform, obtain a 1600-series number from a TSP, and route all citizen calls through it.
- Calls from verified 160-series numbers cover government services such as passport status, tax reminders, welfare scheme updates, and public health alerts.
- NASSCOM confirmed in February 2026 that TRAI mandates use of the 1600 series by eligible government entities under TCCCPR, 2018.
- Non-compliant outreach from 10-digit numbers risks TCCCPR penalties, TRAI blacklisting for up to one year, and operational disruption across all telecom resources of the entity.
Quick Answer: The 160 series numbers for government entities in India are TRAI-mandated verified numbers that central and state departments, PSUs, and government agencies must use for all outbound service and transactional voice calls to citizens. The DoT assigned this series on 30 May 2024 (PRID 2022249). Citizens can then instantly identify legitimate government calls and separate them from spam or fraud.
Table of Contents
- What Are 160 Series Numbers for Government Entities in India?
- Why Does Government Outreach Need a Dedicated 160 Series?
- Which Government Entities Must Comply with the 1600 Series Mandate?
- How Does a Government Entity Apply for a 160 Series Number in India?
- What Rules Apply When Using a 160 Series Number for Government Calls?
- 160 Series vs 140 Series: What Is the Difference for Government Bodies?
- What Are the Penalties for Government Non-Compliance with the 1600 Series?
- How FreJun Helps Government Entities Comply with the 160 Series Mandate
- Frequently Asked Questions
- Key Takeaways
The 160 series numbers for government entities in India represent a fundamental shift in how citizens interact with official outreach calls. Until the DoT’s intervention in May 2024, both government bodies and regulated financial institutions made service calls from standard 10-digit mobile numbers. This practice created widespread confusion. Additionally, it opened the door for fraudsters to impersonate government officials. Citizens routinely ignored calls from unknown numbers as a result. Consequently, critical communications, from welfare updates to passport alerts, went unanswered.
What Are 160 Series Numbers for Government Entities in India?
Definition: 160 Series Numbers for Government Entities
The 160xxxxxxx numbering series is a TRAI-mandated range that the Department of Telecommunications (DoT) assigned exclusively for service and transactional voice calls by verified Principal Entities, including central and state government departments, Public Sector Undertakings, and government agencies. Source: DoT Press Release, PRID 2022249, 30 May 2024.
The 160 series numbers for government entities in India are not ordinary phone numbers. Specifically, a licensed Telecom Service Provider (TSP) allocates every 160-series number only after verifying the entity’s credentials. The TSP must confirm eligibility before assigning any number. The recipient entity must contractually undertake to use it only for calls as defined in the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR). This two-step verification is what makes the series trustworthy.
How the Sub-Ranges Are Structured
Within the broader 160xxxxxxx series, sub-prefixes denote different categories of Principal Entity. Notably, DoT reserves the sub-prefix 1601xxxxxxx for financial-sector entities that RBI, SEBI, PFRDA, and IRDAI regulate. Government organisations draw from the wider 160xxxxxxx pool the DoT assigned for citizen-outreach calls. This covers central ministries, state departments, and PSUs.
Furthermore, NASSCOM’s community advisory of February 2026 confirmed that TRAI mandates use of 1600 series numbers by eligible government entities. The DoT specifically assigned it to government bodies for passport updates, tax reminders, welfare notifications, and key certificates. This assignment ensures that when a citizen’s phone displays a 160-series number, they can confidently answer the call.
Most government agencies find the DLT registration and TSP verification step takes 2 to 3 weeks for first-time applicants. FreJun’s compliance team has guided dozens of entities through the process. Reach out now to understand your exact obligations.
Why Does Government Outreach Need a Dedicated 160 Series?
India recorded approximately 147 million spam-call complaints in 2024, according to industry reports. Consequently, citizens have developed a deep-seated distrust of calls from unknown numbers, and government outreach suffered disproportionately. A welfare-scheme beneficiary who ignores a call from an unrecognised number may miss critical disbursement instructions. A taxpayer who dismisses a tax-reminder call from a standard mobile number may face avoidable penalties.
The Fraud Window the 140 Series Created
The DoT Press Release dated 30 May 2024 (PRID 2022249) explicitly identified the root cause. DoT allocated the 140xxxxxxx series to telemarketers for promotional calls. However, genuine entities, including government bodies, began using it for service and transactional calls as well. As a result, citizens stopped responding to 140-series calls entirely. Fraudsters then exploited the vacuum by placing calls from ordinary 10-digit mobile numbers while impersonating government officials, RBI representatives, or court staff.
Therefore, the DoT allocated the new 160xxxxxxx series specifically to create a trusted, consumer-recognisable signal. The policy rationale is straightforward. Once every legitimate government call originates from a 160 series number, any 10-digit mobile call claiming to be from a ministry becomes immediately suspect. In practice, this structural change is the most powerful anti-impersonation tool India’s telecom framework has introduced.
The Citizen-Recognition Benefit
From a citizen’s perspective, the benefit is immediate. When a 160-series number appears on the screen, the citizen knows the call is from a verified entity. Additionally, the Calling Name Presentation (CNAP) regime mandated by DoT displays the verified entity name alongside the number. This further strengthens citizen recognition. Together, these two mechanisms give citizens a reliable two-factor visual cue. They can verify the number and the entity name before answering.
Moreover, the DoT confirmed that TSPs must ensure adequate verification of every entity before assigning a 160-series number. This creates accountability at the network level, not just at the policy level. The entity must also undertake to use the number only for service and transactional calls under TCCCPR, 2018. What this means for your compliance team: the 160 series is not self-service. Every number must be earned through a verified registration process.
Which Government Entities Must Comply with the 1600 Series Mandate?
The DoT and TRAI have framed the 160-series mandate to cover two broad categories of Principal Entity. The first covers BFSI-sector entities regulated by RBI, SEBI, PFRDA, and IRDAI. The second covers government organisations. The following entity types fall within scope of the government track.
Central Ministries and State Government Departments
Central government ministries and their attached offices, as well as state government departments making outbound citizen-communication calls, fall within the government-outreach category. Specifically, departments that routinely contact citizens are the primary users of the 160 series. Examples include the Income Tax Department (tax notices), the Passport Seva Programme (document status), and the Ministry of Labour (scheme updates).
Furthermore, the DoT’s NASSCOM-confirmed advisory highlights that the 1600 series covers calls for passports, tax reminders, and key government certificates. These are classic service calls. The citizen holds an existing relationship with the entity, and the call completes or updates a transaction the citizen initiated.
Public Sector Undertakings and Government Agencies
PSUs, statutory bodies, and government-owned enterprises that make outbound service or transactional calls to citizens also fall within the 1600-series framework. In my practice advising telecom-sector clients, I have seen PSUs in utilities, petroleum, and financial services struggle with a recurring question. Do their outbound calls count as government outreach, or as commercial calls subject to BFSI-sector deadlines? The answer depends on which regulatory authority oversees the PSU’s primary activity.
Additionally, e-governance platforms operated by National Informatics Centre (NIC) or state IT departments also require 1600-series numbers. This covers automated citizen-service calls such as Aadhaar-linked benefit alerts and election commission notifications. The practical step: map every outbound calling programme to its regulatory category. Then confirm the correct sub-range with your TSP before applying for allocation.
Government IT Departments and Outsourced Contact Centres
Government IT departments that operate contact centres must ensure all outbound citizen calls originate from the Principal Entity’s allocated 1600-series numbers. This applies whether the centre runs in-house or through an outsourced BPO vendor. The TCCCPR makes the Principal Entity (the government department or PSU) vicariously liable for the compliance conduct of its vendors. Therefore, a BPO calling on behalf of a ministry must use the ministry’s 1600 numbers. It cannot use its own commercial number pool.
Moreover, this rule applies regardless of whether the calls are made in-house or via an outsourced contact-centre. What this means for your IT department is clear. Your vendor contract must require the BPO to route all citizen-outreach calls through your allocated 1600 numbers. Additionally, your SLAs must include compliance monitoring provisions to verify this requirement.
How Does a Government Entity Apply for a 160 Series Number in India?
Applying for a 160 series number in India follows a structured process governed by the TCCCPR. TRAI and the TSP both supervise it. The process requires careful preparation, though the steps are straightforward. Below is a step-by-step breakdown for government entities.
Step 1: Register on the DLT Platform
First, the government entity must register as a Principal Entity on the Distributed Ledger Technology (DLT) platform operated by an access provider. DLT registration is the foundational step: without it, no TSP can assign a 1600-series number. The entity must submit its legal name, registration details, designated nodal officer, and authorisation documentation.
Definition: DLT Platform (Distributed Ledger Technology)
The DLT platform is a blockchain-based registry mandated by TRAI under TCCCPR, 2018, on which Principal Entities must register their identity, consent templates, and content templates before making commercial voice calls. All telecom operators in India operate or are connected to DLT platforms to validate sender identity in real time.
Step 2: Register Voice Script Templates
Next, the entity must pre-register every voice script or IVR template it intends to use. Each template receives a unique Template ID on the DLT platform. Subsequently, the entity must pass this Template ID in the call signalling for every outbound call. Using an unregistered or outdated template is a TCCCPR violation even if the originating number is a valid 1600-series allocation.
In practice, government entities often underestimate how many templates they need. A tax-reminder campaign alone may need separate templates for the first, second, and final notice, since each content variation requires individual registration. Therefore, map your calling scenarios thoroughly before submitting templates. This avoids unnecessary delays.
Step 3: Undergo TSP Verification and Receive Number Allocation
After DLT registration, the entity approaches a licensed TSP for a 1600-series number. The TSP performs its own eligibility verification, cross-referencing the DoT’s guidelines and the entity’s DLT registration. Once satisfied, the TSP allocates the number and activates it on the network. Additionally, the entity signs an undertaking to use the number strictly for service and transactional calls under TCCCPR, 2018. This contractual commitment is a condition of allocation, not an optional formality.
Step 4: Enforce Technical Routing Segregation
Finally, the entity must enforce routing segregation at the system level. The TCCCPR requires physical separation of 1600-series traffic from any 140-series promotional traffic. This separation must happen at the dialer or PBX level. A written policy statement without enforced routing logic does not constitute adequate compliance. The practical step: ensure your contact centre platform maintains separate outbound trunks for 1600-series calls. No promotional campaign traffic should route through them.
What Rules Apply When Using a 160 Series Number for Government Calls?
Holding a 1600-series number is not the end of the compliance journey. Several ongoing operational rules govern how government entities use the number once allocated.
Purpose Restriction: Service and Transactional Calls Only
The most fundamental rule is purpose restriction. A 1600-series number must never be used for promotional, marketing, or campaign calls. The DoT imposed a clear obligation on every allocated entity. It must use the number only for service and transactional calls as defined in TCCCPR, 2018. Specifically, a “service call” is one the entity makes with consent or via a registered template. It must facilitate, complete, or confirm a transaction the recipient consented to. Alternatively, it may provide safety, recall, or security information about a service the recipient has used.
A “transactional call” is a non-promotional call to the entity’s own account holders or registered citizens. The information must be essential to the recipient, such as an OTP, a benefit-disbursement confirmation, or an account alert. Furthermore, the TCCCPR Second Amendment dated 12 February 2025 limits transactional calls to within 30 minutes of the customer-initiated event. Any call placed beyond that window counts as service content. It therefore requires the corresponding consent documentation.
Consent Framework for Government Outreach
Government entities must comply with the consent rules in TCCCPR, 2018, as amended. Implicit consent is valid for the duration of the citizen’s relationship with the entity. For example, it covers the period of an active passport application. Explicit consent is valid for 7 days from grant, where no continuing relationship exists.
Additionally, once a citizen opts out, the entity may not contact them again for 90 days on the same subject. The use of auto-dialers or robo-calls must be disclosed at the start of every call. Moreover, consent capture must align with the Digital Consent Acquisition (DCA) framework on the DLT platform. What this means for your compliance team is that every outbound calling programme needs a consent-mapping exercise before launch, not after.
Anti-Spoofing and CNAP Requirements
Section 42 of the Telecommunications Act, 2023 criminalises the tampering or masking of telecommunication identifiers. Specifically, the originating number presented in every call must be the actual allocated 1600-series number: no masking, no virtual-number overlay. Additionally, the DoT’s Calling Name Presentation (CNAP) regime mandates accurate caller identity disclosure on the receiving handset. Therefore, any government entity that uses a virtual number to mask its allocated 1600 number faces criminal liability under Section 42. TCCCPR penalties apply on top of that.
Record-Keeping and Audit Trail Obligations
Government entities must retain full Call Detail Records (CDRs) for the period specified in their TSP’s licence conditions. Additionally, they must retain Template IDs for each call, consent records where applicable, and call recordings where the workflow requires them. Under the Digital Personal Data Protection Act, 2023 (DPDP Act), the government entity acts as a Data Fiduciary. It must demonstrate lawful basis for processing, purpose limitation, and retention controls on demand from the Data Protection Board.
160 Series vs 140 Series: What Is the Difference for Government Bodies?
The difference between the 160 series and the 140 series is absolute, not a matter of preference. The two series are legally non-interchangeable for government entities.
| Feature | 160 Series | 140 Series |
|---|---|---|
| Permitted use | Service and transactional calls only | Promotional and telemarketing calls only |
| Eligibility | BFSI entities (RBI/SEBI/PFRDA/IRDAI) and government organisations | Registered telemarketers |
| Citizen recognition | Verified, trusted call from regulated entity or government | Promotional call, can be opted out via DND |
| Consumer trust level | High: TSP-verified, DLT-registered | Low: associated with spam in consumer perception |
| Government use case | Passport alerts, tax reminders, welfare updates, OTPs | Not permitted for government service calls |
| Penalty for misuse | ₹2 lakh (1st), ₹5 lakh (2nd), ₹10 lakh (3rd+) | Same TCCCPR penalty structure applies |
Notably, a government department that continues using 10-digit mobile numbers for service calls after the mandate risks TCCCPR classification as Unsolicited Commercial Communication from an Unregistered Telemarketer. This classification triggers escalating enforcement under TCCCPR. The first violation draws a warning. The second brings a 20-call-per-day usage cap for six months. On the third violation, TRAI disconnects all telecom resources. The practical implication is severe. A ministry that loses its telecom resources cannot deliver OTPs, run public helplines, or make any outbound citizen contact.
Furthermore, the internal link between the 160 and 140 series and citizen trust has a direct empirical basis. The DoT observed in its 30 May 2024 press release that overuse of 140-series numbers led to high consumer non-response rates. As a result, genuine entities, including government bodies, began using 10-digit mobile numbers for service calls. This inadvertently gave fraudsters an identical attack vector. The 160 series closes that gap structurally. For an in-depth comparison of the two series, see our detailed guide on 160 series vs 140 series numbers in India.
The 160 vs 140 series distinction is frequently misunderstood by IT and procurement teams within government agencies. Our legal team can walk you through the exact series your entity must use and the steps to get allocated in under 30 days.
What Are the Penalties for Government Non-Compliance with the 1600 Series?
The penalty structure for misuse of the 1600 series is multi-layered, and government entities are not exempt from any of its tiers. Below are the principal enforcement layers relevant to government bodies.
TCCCPR Financial Disincentives
Under the TCCCPR Second Amendment dated 12 February 2025, graded financial disincentives apply per instance of violation. TRAI imposes these penalties on access providers, who then cascade them contractually to the Principal Entity. The figures are exact:
- First instance of violation: ₹2,00,000
- Second instance of violation: ₹5,00,000
- Third and subsequent instances: ₹10,00,000 per instance
Service Suspension and Blacklisting
Materially more disruptive than the financial penalties is the service-suspension mechanism. For government entities, the consequences are as follows. On the first complaint threshold breach, specifically 5 valid complaints in a 10-day rolling period, TRAI bars all outgoing services for 15 days. On subsequent violations, TRAI disconnects all telecom resources, including PRI and SIP trunks, across every TSP for up to one year. The entity is then blacklisted.
For a government ministry or PSU, a one-year telecom blacklist is operationally catastrophic. OTPs cannot be delivered, citizen helplines cannot make outbound calls, and no service communications can reach the public. Additionally, a TRAI enforcement action damages citizen trust in the very outreach programmes the 160 series was designed to strengthen.
DPDP Act Liability
Non-compliance can also breach data-protection obligations, for example by calling without lawful basis or failing to honour opt-outs. In such cases, the Digital Personal Data Protection Act, 2023 (DPDP Act) applies. The Data Protection Board can impose penalties up to ₹250 crore for failure to implement reasonable security safeguards. It can impose up to ₹200 crore for failure to notify a personal data breach. Government entities that handle citizen personal data are fully subject to the DPDP Act. What this means for your legal team is that a non-compliant calling programme carries both telecom-law and data-protection risk simultaneously.
Reputational and Citizen-Trust Consequences
Beyond financial and operational penalties, non-compliance carries serious reputational consequences. A TRAI enforcement action against a government body damages the credibility of the very outreach programme the 160 series was designed to strengthen. Citizens who learn of a ministry’s telecom blacklisting lose confidence in future service calls. Moreover, disclosure of enforcement action may be mandatory in compliance certificates filed with oversight bodies. The practical step is to treat 1600-series compliance as an ongoing operational discipline, not a one-time registration exercise.
For the broader compliance context, see our pillar guide on BFSI communication compliance in India 2026.
How FreJun Helps Government Entities Comply with the 160 Series Mandate
FreJun is India’s cloud telephony platform purpose-built for regulated entities. Specifically, FreJun provisions and manages 160-series numbers for eligible government bodies. The platform handles the end-to-end compliance layer so your legal and IT teams focus on operational outcomes, not regulatory plumbing.
What FreJun’s Platform Handles
- DLT registration and template management: FreJun’s team guides entities through Principal Entity registration on the DLT platform and manages template submissions, updates, and Template ID mapping.
- TSP coordination and number allocation: FreJun works directly with licensed TSPs to facilitate 1600-series number applications, verification, and activation, reducing average onboarding time significantly.
- Routing segregation: FreJun’s platform enforces technical separation between 1600-series service trunks and any promotional traffic, satisfying the TCCCPR requirement for system-level segregation.
- CDR logging and audit trail: FreJun logs, stores, and indexes every Call Detail Record against the corresponding Template ID, providing a complete audit trail for TRAI or sectoral regulator review.
- CRM integrations: FreJun integrates with HubSpot, Zoho, Salesforce, and LeadSquared, enabling government contact centres to log citizen interactions in their existing systems without duplicate data entry.
Furthermore, FreJun is not a telecom operator or TSP. It is a compliance specialist for BFSI and government entities. Its platform sits as the technology layer between the entity and the TSP. It abstracts DLT, template management, and routing compliance into a single dashboard. Additionally, FreJun’s platform handles the technical compliance layer. Your legal team can then focus on substantive obligations rather than infrastructure.
For the underlying technical architecture, see our guide on TCCCPR 2018 compliance for regulated entities in India.
Government agencies that have already onboarded with FreJun report that the DLT-to-first-call timeline shrinks to under three weeks. Book a call to walk through your entity’s exact compliance requirements and get a timeline.
Frequently Asked Questions
What are 160 series numbers for government entities in India?
160 series numbers are TRAI-mandated verified numbers the DoT assigned to government organisations and BFSI entities for service and transactional voice calls. When a citizen sees a 160-series number, the call comes from a TSP-verified entity on the DLT platform. DoT confirmed the mandate on 30 May 2024 (PRID 2022249), and NASSCOM reinforced it in February 2026.
160 series vs 140 series: what is the difference for government bodies?
The 160 series is for service and transactional calls only; the 140 series is for promotional and telemarketing calls only. Government bodies cannot use 140-series numbers for citizen service calls. After the mandate, using a 10-digit mobile number for government service calls risks TCCCPR classification as Unsolicited Commercial Communication. This triggers penalties up to ₹10 lakh per instance and possible blacklisting for one year.
What is the penalty for not adopting the 1600 series as a government entity?
Under the TCCCPR Second Amendment (12 February 2025), penalties are ₹2 lakh for the first violation, ₹5 lakh for the second, and ₹10 lakh per instance from the third onward. Beyond financial penalties, TRAI can bar outgoing services for 15 days on the first complaint threshold. Subsequent violations lead to blacklisting of all telecom resources for up to one year.
How does a government entity apply for a 160 series number in India?
The process has four steps. First, register as a Principal Entity on the DLT platform. Second, pre-register every voice script template and obtain a Template ID. Third, approach a licensed TSP for allocation, pass eligibility verification, and sign the usage undertaking. Fourth, enforce technical routing segregation to keep 1600-series calls separate from any promotional traffic.
Does the 160 series mandate apply to PSUs and government agencies, not just ministries?
Yes. The DoT assigned the 1600 series to government organisations broadly, covering central and state departments, statutory bodies, PSUs, and government-operated e-governance platforms. Any government entity making outbound service or transactional calls to citizens requires a 1600-series number. BPOs acting on behalf of government entities must use the government body’s allocated 1600 numbers. Their own commercial pools are not permitted.
How can citizens identify legitimate government calls from 160 series numbers?
A number beginning with 160 on the citizen’s handset originates from a TSP-verified entity. That entity is registered on the DLT platform. Furthermore, the DoT’s Calling Name Presentation (CNAP) regime displays the verified entity name alongside the number on compatible handsets. Citizens should treat any call from a standard 10-digit mobile number claiming to be from a government body as suspicious. They should verify independently before sharing personal data.
Are government entities subject to the same TCCCPR consent rules as BFSI entities?
Yes. Government entities must comply with TCCCPR, 2018 (as amended 12 February 2025). Implicit consent is valid for the duration of the citizen’s relationship with the relevant government service. Explicit consent is valid for 7 days. Once a citizen opts out, the entity cannot contact them again for 90 days on the same subject. Additionally, DPDP Act, 2023 obligations apply to all citizen personal data processed through outbound calling programmes.
Key Takeaways
- The 160 series numbers for government entities in India are DoT-mandated verified numbers (PRID 2022249, 30 May 2024) for service and transactional outbound calls to citizens.
- Central ministries, state departments, PSUs, statutory bodies, and government-operated e-governance platforms all fall within scope of the 1600-series framework.
- The 1600 series and 140 series are legally non-interchangeable: the former is for service calls, the latter for promotions only. Government bodies cannot use 140-series for citizen service calls.
- Obtaining a 1600-series number requires DLT registration, voice template pre-registration, TSP eligibility verification, and technical routing segregation.
- NASSCOM confirmed in February 2026 that TRAI mandates use of the 1600 series by eligible government entities under TCCCPR, 2018.
- Non-compliance risks include TCCCPR financial penalties from ₹2 lakh to ₹10 lakh per instance, service suspension, and blacklisting of all telecom resources for up to one year.
- As of December 2025, approximately 570 entities across BFSI and government had adopted 1600-series numbers, subscribing to over 3,000 numbers.
Compliance Disclaimer
Disclaimer: This article is published for informational purposes only and represents FreJun’s understanding of the relevant legal and regulatory position based on its own independent research and interpretation of publicly available materials. It should not be construed as legal advice, legal opinion, or regulatory guidance. Readers should seek independent legal counsel or consult appropriate regulatory authorities before acting on any information herein. While FreJun has made reasonable efforts to ensure accuracy, laws, regulations, and enforcement positions may evolve or vary based on specific facts. FreJun does not warrant that the contents are free from inaccuracies or inadvertent errors. FreJun accepts no liability for any misinformation or reliance placed upon this article.
References and Sources
- DoT Press Release, 30 May 2024 (PRID 2022249): pib.gov.in
- TRAI Direction, 19 November 2025 (PRID 2191647, RBI/SEBI/PFRDA entities): pib.gov.in
- TRAI Direction, 16 December 2025 (PRID 2205350, IRDAI entities): pib.gov.in
- TCCCPR Second Amendment, 12 February 2025: trai.gov.in (PDF)
- NASSCOM Advisory on 1600 Series for Government Outreach, February 2026: community.nasscom.in
- TCCCPR 2018: trai.gov.in
- Digital Personal Data Protection Act, 2023 (MeitY): meity.gov.in
- SARAL SANCHAR Portal (TSP licence verification): saralsanchar.gov.in