> ## Documentation Index
> Fetch the complete documentation index at: https://www.vobiz.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# CDR Full Form: What a Call Detail Record Contains

> CDR full form in telecom is call detail record: a per-call log of numbers, times, outcome and cost, with no audio. See its fields, uses and India rules.

*November 3, 2026 · By [Piyush Sahoo](https://www.linkedin.com/in/piyush-s713/)*

CDR stands for call detail record. It is the structured entry a telephone network or voice platform writes for a call, listing the numbers, timestamps, duration, outcome, and often cost and quality. It holds no audio. Outside telecom, CDR can also mean corporate debt restructuring or crude death rate.

This guide reads one call field by field, shows which record answers which question, and sets out India's retention and access rules, each linked to its source.

> [!NOTE]
>
> **Key takeaways**
>
> * A CDR is **metadata, not content**. It says who, when, how long, and how it ended, and never what was said.
> * **`duration` and `billsec` measure different things.** Ring time counts toward the first and not the second, so check charges against billable seconds.
> * **In India, retention depends on who holds the record.** Telecom operators keep CDRs for two years, and call centres under DoT's 2021 guidelines for one.
> * **Your business's CDRs and an operator's subscriber CDRs are different things.** You can export your own platform data, while operator records generally move only through police or court channels.
> * **Your CDRs can approximate TRAI's spam signals.** You can count call volume, recipient diversity, average duration, and the incoming-to-outgoing ratio from your own rows.

## What does CDR stand for?

In telecom and in police work, CDR means call detail record. The idea has a paper ancestor: Wikipedia describes the CDR as [the automated equivalent of the operator's toll ticket](https://en.wikipedia.org/wiki/Call_detail_record).

Search for "CDR full form" and you also find unrelated meanings, so check the context first.

| Context | CDR means | What it is |
| - | - | - |
| Telecom, call centres, police | Call detail record | The log entry for one call, and the subject of this guide |
| Mobile core networks | Charging data record | [3GPP's term](https://itecspec.com/3gpp/32.251/s/3.1) for formatted data about a chargeable event, used for billing |
| Indian banking | Corporate Debt Restructuring | A lender scheme for stressed loans. [RBI withdrew it in February 2018](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=11218\&Mode=0) |
| Demography | Crude death rate | [Deaths per 1,000 people per year](https://en.wikipedia.org/wiki/Mortality_rate) |
| Medicine | Clinical Dementia Rating | [A numeric scale for the stage of dementia](https://en.wikipedia.org/wiki/Clinical_Dementia_Rating) |
| Navy and armed forces | Commander (Cdr) | [A naval officer rank](https://en.wikipedia.org/wiki/Commander) |
| Graphic design | CorelDRAW file | [The `.cdr` file extension](https://en.wikipedia.org/wiki/CorelDRAW) for vector drawings |
| Computing | CD-R | [Compact disc-recordable](https://en.wikipedia.org/wiki/CD-R), a write-once disc |

The rest of this guide covers the telecom meaning. You may also meet some close relatives: some PBX vendors say [SMDR, for station messaging detail record](https://en.wikipedia.org/wiki/Call_detail_record), and [DoT's guidelines add UDR](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf), for usage data record.

## What does a CDR contain?

A CDR is one row per call, or per call leg on many platforms. No single global format sets its fields, so names vary by vendor, but the same six families appear almost everywhere.

![Diagram of one CDR row split into six field families: who, when, outcome, money, route and quality, with a dashed box noting that audio and transcripts are not in the row.](https://mintcdn.com/vobizai/Gqjw4qC2csbNZrm6/images/blog/what-is-a-call-detail-record/cdr-anatomy-light.svg?fit=max\&auto=format\&n=Gqjw4qC2csbNZrm6\&q=85\&s=a791c43d811ee0dca6e845681d1fe852)

If you've moved between systems, this translation table saves time. The classic terms draw on [Wikipedia](https://en.wikipedia.org/wiki/Call_detail_record) and common telecom usage, the SIP platform names are typical examples, and the last column comes from the [Vobiz CDR object](https://www.vobiz.ai/docs/cdr.md).

| What you want | Classic telecom term | Common SIP platform name | Vobiz field |
| - | - | - | - |
| Calling number | A-party, ANI | `src` | `caller_id_number` |
| Called number | B-party, DNIS | `dst` | `destination_number` |
| Total time | Call duration | `duration` | `duration` |
| Billable time | Not always present | `billsec` | `billsec` |
| How it ended | Disposition | `disposition`, `hangup_cause` | `hangup_cause`, `hangup_source` |
| Which route | Trunk or route | `trunk` | `trunk_id` |

Cause values have their own lineage. [ITU-T Q.850](https://www.itu.int/dms_pubrec/itu-t/rec/q/T-REC-Q.850-201810-I!!SUM-HTM-E.htm) defines the cause information used in ISDN and SS7 signalling, and many telephony systems report a form of it, with cause 16 meaning a normal clearing. Quality scores such as MOS use a [scale that typically runs from 1 to 5](https://en.wikipedia.org/wiki/Mean_opinion_score), with terminology defined in [ITU-T P.800.1](https://www.itu.int/rec/T-REC-P.800.1/en).

### Metadata is not harmless

CDRs are often seen as a lighter privacy burden than recordings because they hold no conversation. That's fair as a comparison, but don't treat exports as low-risk logs.

Contact patterns alone can be revealing. An operator's CDR can include [a cell ID that points to a tower sector](https://sudhirrao.com/insights/call-details-record-own-number-telecom-operator), and the Internet Freedom Foundation calls this data [sensitive](https://internetfreedom.in/the-governments-got-your-number-and-more/). Give your CDR exports the same access controls as other customer data.

## Reading one call, field by field

The fields make more sense laid over a call. In this example, the phone rang for 7 seconds and the conversation lasted 184.

![Timeline of one answered call showing ring\_time of 7 seconds, billsec of 184 seconds and duration of 191 seconds, then an unanswered call with billsec of 0 and an empty answer\_time.](https://mintcdn.com/vobizai/Gqjw4qC2csbNZrm6/images/blog/what-is-a-call-detail-record/call-timeline-light.svg?fit=max\&auto=format\&n=Gqjw4qC2csbNZrm6\&q=85\&s=0034609d41f23ededa20cb366027a6fc)

Here is the same call as a reader would interpret it. Every value is illustrative, and the numbers are masked.

| Field | Value | How to read it |
| - | - | - |
| `call_direction` | outbound | Your side placed the call |
| `caller_id_number` | +91 80XXX XX214 | The originating number |
| `destination_number` | +91 98XXX XX210 | The number dialled |
| `start_time` | 10:04:11 | The call was initiated |
| `answer_time` | 10:04:18 | The callee picked up, 7 seconds later |
| `end_time` | 10:07:22 | The call ended |
| `ring_time` | 7 | Seconds of ringing |
| `billsec` | 184 | Seconds from answer to hangup |
| `duration` | 191 | Ring plus talk |
| `hangup_cause` | NORMAL\_CLEARING | One party hung up normally |
| `hangup_source` | Callee | The person you called ended it |
| `mos` | 4.3 | Audio quality score for the call |

Two common mistakes hit reporting hardest:

* **Summing `duration` to check talk-time charges.** That sum includes ringing, so it overstates billable time. On Vobiz, `billsec` holds [talk time only](https://www.vobiz.ai/docs/cdr.md).
* **Counting one conversation as one row.** A bridged call has [more than one leg](https://www.vobiz.ai/docs/blogs/what-is-a-call-leg.md), and each can be rated separately. Link related rows with an identifier such as `bridge_uuid`, the UUID of the bridged leg, before you count conversations.

## Which call record answers your question?

Teams often query the wrong record for their question. Each one answers something different, and they work best together.

![Decision map linking five questions to records: cost and parties to the CDR, spoken content to a call recording, live events to webhooks, failures to a SIP log plus CDR quality fields, and internet use to an IPDR.](https://mintcdn.com/vobizai/Gqjw4qC2csbNZrm6/images/blog/what-is-a-call-detail-record/which-record-light.svg?fit=max\&auto=format\&n=Gqjw4qC2csbNZrm6\&q=85\&s=604f9f85fe61c94a0eb6d7af6cf8b068)

| Record | Holds | Timing | Use it for |
| - | - | - | - |
| CDR | Parties, times, outcome, cost, quality | After the call | Billing, reporting, audits |
| Call log screen | A simplified view built from CDR data | After the call | Looking up a recent call |
| [Webhooks (callbacks)](https://www.vobiz.ai/docs/concepts/callbacks.md) | Events as the call progresses | During the call | Triggering your application logic |
| [Call recording](https://www.vobiz.ai/docs/recording.md) | Audio | After the call, if enabled | QA, disputes, transcription |
| SIP log | Signalling messages | After the call | Debugging setup failures |
| IPDR | [A subscriber's internet usage](https://internetfreedom.in/the-governments-got-your-number-and-more/) | Held by the operator | Investigations, not business reporting |

Don't assume operator CDRs are instant, either. One stakeholder told TRAI that operator CDRs reach the database [only after 24 to 36 hours](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf), and TRAI's analysis accepted that same-day CDR analysis wasn't possible. Platform timing differs by provider, so confirm yours before you build alerts on it.

## What can you do with call detail records?

The headline uses are billing, reporting, and fraud detection. Here is how each works in practice.

### Reconcile the bill

Export a month of CDRs, sum billable seconds and cost by route or number, and compare the totals with your invoice. Rows that disagree point to rating questions, such as a pulse or a route you didn't expect. Your rate card decides how seconds become money, so apply its rules before you call something an error.

### Find out why calls fail

Work through a problem call in a fixed order: was it answered, did media flow, and how was the quality?

![Flow chart for a problem call. Without an answer\_time, read hangup\_cause to separate the callee, bad data and network problems. With an answer\_time, check for MEDIA\_TIMEOUT, then for low MOS, high jitter or packet loss.](https://mintcdn.com/vobizai/Gqjw4qC2csbNZrm6/images/blog/what-is-a-call-detail-record/cdr-triage-light.svg?fit=max\&auto=format\&n=Gqjw4qC2csbNZrm6\&q=85\&s=3da9a8a5a074a02d1cd7674e8d7a1038)

The causes come from Vobiz's [CDR reference](https://www.vobiz.ai/docs/cdr.md) and [hangup cause list](https://www.vobiz.ai/docs/concepts/hangup-causes.md). A single row rarely proves much. Group by destination prefix, trunk, or hour, because a failure that clusters tells you where to look.

### Spot fraud early

Unusual patterns tend to show up in the CDR before anywhere else, such as a spike in international traffic. Compare today's traffic with your usual baseline for destinations, hours, and short-call volume, and alert on large jumps. Vobiz's dashboard guidance gives one example: [a sudden cluster in a country you don't serve](https://www.vobiz.ai/docs/platform/dashboard.md) calls for a CDR cross-check.

### Check your calling against TRAI's spam signals

This use matters to Indian senders. TRAI's [February 2025 amendment](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf) tells operators to treat senders as suspected unregistered telemarketers based on signals, and your own CDRs can approximate each one.

| TRAI signal | How to measure it from your CDRs |
| - | - |
| Calls above a prescribed threshold | Count outbound rows per caller ID per day |
| High recipient diversity | Count distinct `destination_number` values per caller ID per day |
| Low average call duration | Average `billsec` per caller ID per day |
| Low incoming-to-outgoing ratio | Divide inbound rows by outbound rows per number per day |

The regulation leaves the thresholds to TRAI, and the text we read doesn't state numbers, so use these as trends and not as a pass mark. The [September 2026 Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) goes further, with AI-based flagging of high-probability spam numbers on behavioural parameters. It also gives senders a way to contest a flag, and it says numbers in dedicated commercial series aren't to be flagged as suspected spam. Its provisions start 30 to 90 days after Gazette publication, so check which ones are live. Our [India calling regulations](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md) page covers the wider rules.

CDRs also decide complaints. The Third Amendment's memorandum reports that, from January to April 2026, 1,32,137 of 12,37,707 complaints (10.68%) were [declared invalid because the CDR did not match](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf). TRAI responded by adding the power to call for CDRs when it audits complaint handling.

## How long must CDRs be kept in India?

The answer depends on who holds the record. A government direction, a dispute, or a legal hold can extend these periods. The DPDP row also requires erasure afterwards unless another law requires longer retention.

![Bar chart of retention periods in India: telecom operator CDRs 24 months, operator complaint records 24 months, OSP CDRs 12 months, enterprise communication service user records 12 months, and DPDP traffic data and logs 12 months from May 2027.](https://mintcdn.com/vobizai/Gqjw4qC2csbNZrm6/images/blog/what-is-a-call-detail-record/india-retention-light.svg?fit=max\&auto=format\&n=Gqjw4qC2csbNZrm6\&q=85\&s=f72b435ec452fd30a9d9a2652783ccdc)

| Who | What | Period | Source |
| - | - | - | - |
| Telecom operators | Commercial records, CDR, EDR, IPDR | 2 years. Raised from 1 year by the [Unified Licence amendment of 21 December 2021](https://internetfreedom.in/the-governments-got-your-number-and-more/), and matched by [Rule 45(2) of the 2026 Principal Services Rules](https://www.dot.gov.in/static/uploads/2026/06/b981573e59f32264e099912a9154dacb.pdf) | [TRAI Third Amendment explanatory memorandum, September 2026](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) |
| Telecom operators | Complaint, appeal, and report records | 2 years, aligned to the above | [Same TRAI document](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) |
| Other Service Providers (voice BPOs, call centres) | CDR, UDR, system logs, with a copy held at an Indian centre | 1 year | [DoT Revised OSP Guidelines, 23 June 2021](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf) |
| Enterprise communication services (such as cloud EPABX) | Certain records of users | 1 year | [Khaitan & Co note on the 2026 Miscellaneous Rules](https://www.khaitanco.com/sites/default/files/2026-06/Ergo_Miscellaneous%20Telecom%20Services_30062026.pdf) |
| Data Fiduciaries under the DPDP Rules | Personal data, associated traffic data, and processing logs, for the purposes in the Seventh Schedule | 1 year, then erase unless another law requires more | [Rule 8(3), DPDP Rules 2025](https://www.meity.gov.in/static/uploads/2025/11/53450e6e5dc0bfa85ebd78686cadad39.pdf) |

Four details are easy to miss:

* **The OSP rules go beyond retention.** DoT's guidelines name the content too, including calling and called number, date, start and end time, device identity, user login, and gateway and trunk IDs. Timestamps must [follow Indian Standard Time](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf). Lawyers writing about the guidelines said this content list [caused an "unanticipated stir"](https://www.hunton.com/media/publication/82702_digital-call-records-the-impact-of-indias-revised-guidelines-for.pdf).
* **The DPDP timing is staggered.** Rule 8 starts [eighteen months after publication](https://www.meity.gov.in/static/uploads/2025/11/53450e6e5dc0bfa85ebd78686cadad39.pdf) in the Gazette of 13 November 2025, which points to May 2027. Plan your retention job now.
* **Telecom network data has a location rule.** [Rule 30(3)(b) of the 2026 Principal Services Rules](https://www.dot.gov.in/static/uploads/2026/06/b981573e59f32264e099912a9154dacb.pdf) requires authorised entities to store such data in India and make no copies available abroad. Khaitan & Co describes this as [stricter than the draft rules](https://www.khaitanco.com/sites/default/files/2026-06/Ergo_Principal%20Telecom%20Authorisation%20Rules_26062026.pdf). Ask counsel how this applies to you.
* **Records seized in a case get special handling.** In 2020, the Supreme Court told cellular companies and internet providers to keep seized CDRs [in a segregated and secure manner](https://www.livelaw.in/top-stories/sc-directs-telecos-isps-to-maintain-cdr-and-other-records-seized-during-investigations-159932).

This section is a map, not legal advice. As of 3 November 2026, we found no DoT text replacing the 2021 OSP guidelines, but we couldn't confirm how the 2026 authorisation rules treat them. Ask counsel which category you fall into.

## Who can get a CDR in India?

The answer depends on which CDR you mean, because two very different records share the name.

| | Operator subscriber CDR | Your business's platform CDR |
| - | - | - |
| **Held by** | The mobile or fixed-line operator | Your voice provider, under your account |
| **Covers** | All calls on one subscriber's number | Calls your account placed or received |
| **Can include** | Cell ID, and in some records [device identifiers](https://en.wikipedia.org/wiki/Call_detail_record) | Cost, trunk, codec, MOS |
| **Who can read it** | Law enforcement and courts, through legal process | You, with your own credentials |

For operator records, the position is narrower than many people expect:

* **Police and courts.** A criminal court can summon records under [Section 94 BNSS](https://sudhirrao.com/insights/call-details-record-own-number-telecom-operator), the successor to Section 91 CrPC. The Delhi High Court [allowed a 2025 plea on the preservation of CDRs](https://www.scconline.com/blog/post/2025/10/22/dhc-on-embargo-on-call-recordsproduction-in-ndps-case/) brought under that section, and found no bar on production at an appropriate stage with privacy precautions.
* **Your own number.** A Supreme Court advocate writes that there is [no consumer route to your own CDR on request](https://sudhirrao.com/insights/call-details-record-own-number-telecom-operator). A [summary of a Delhi district-court appeal](https://advocategandhi.com/access-to-call-records-denied-legal-boundaries-clarified-by-delhi-court/) describes the same result, with the court pointing the subscriber to the criminal route.
* **Everyday billing questions.** [Regulation 8 of TRAI's consumer rules](https://trai.gov.in/sites/default/files/2025-03/CR_TCPR_28032025.pdf), consolidated to March 2025, lets prepaid users request itemised usage for the past six months, supplied within 30 days. [TRAI's prepaid FAQ](https://www.trai.gov.in/faqcategory/prepaid) caps the charge at ₹50.
* **Someone else's number.** Every route in the sources above runs through the police or a court, so a private person has no direct one. Treat any website selling another person's call records as a red flag.

If a CDR goes to court, getting the record is only half the work. [Section 63 of the Bharatiya Sakshya Adhiniyam](https://www.apnilaw.com/legal-articles/acts/section-65b-of-the-indian-evidence-act-vs-section-63-of-the-bharatiya-sakshya-adhiniyam-admissibility-electronic-evidence/) replaced Section 65B of the Evidence Act from 1 July 2024, and [a certificate must accompany the output](https://sudhirrao.com/insights/call-details-record-own-number-telecom-operator). Take advice from your lawyer on what yours should say.

## How Vobiz handles call detail records

Vobiz writes a record for each call and exposes it through the API and the Console. Reading CDRs doesn't place calls. You need your own [Auth ID and Auth Token](https://www.vobiz.ai/docs/cdr.md) for API access.

* **Query.** The [list endpoint](https://www.vobiz.ai/docs/cdr/list-cdrs.md) filters by number, date range, direction, minimum duration, `sip_call_id`, `bridge_uuid`, `hangup_cause`, `hangup_disposition`, `context`, and `campaign_id`, plus free-text search. It also returns a summary with total calls, answered calls, answer rate, billable seconds, and total cost.
* **Look up one call.** [Fetch a single CDR](https://www.vobiz.ai/docs/cdr/get-cdr.md) by call ID, for example one you got from a webhook. Use the [recent endpoint](https://www.vobiz.ai/docs/cdr/recent-cdrs.md) for the latest calls with no date range.
* **Export.** The [CSV export](https://www.vobiz.ai/docs/cdr/export-cdrs.md) returns one row per call for the filters you set, ready for reconciliation or your own data store.
* **Browse.** The Console has [voice call logs](https://www.vobiz.ai/docs/platform/voice/call-logs.md), [SIP call logs](https://www.vobiz.ai/docs/platform/sip/call-logs.md), and [campaign call logs](https://www.vobiz.ai/docs/platform/campaigns/call-logs.md), with call timing and hangup causes. Voice and SIP logs also show MOS.
* **Resell.** Partners can read [per-customer CDRs](https://www.vobiz.ai/docs/partner/api/cdrs.md) across their accounts, and CDRs for inbound calls to numbers assigned to a sub-account [belong to that child account](https://www.vobiz.ai/docs/platform/subaccounts.md).

For real-time logic, pair CDRs with the `Hangup` event from [webhooks (callbacks)](https://www.vobiz.ai/docs/concepts/callbacks.md), which is the authoritative end-of-call signal. On conference legs, read `hangup_source` alongside [`ConferenceExit` callbacks](https://www.vobiz.ai/docs/xml/conference/conference-callbacks) when you need exact attribution.

## Frequently asked questions

> [accordion] What is the full form of CDR in telecom?
>
> CDR stands for call detail record. It is the structured entry a network or voice platform writes for a call, with the numbers, times, duration, and outcome. Mobile core networks also use CDR for charging data record, a billing record defined by 3GPP.

> [accordion] What is the CDR full form in police work?
>
> It is the same term: call detail record. Investigators use an operator's CDR to see which numbers were in contact, when, and for how long. A cell ID in the record gives only an approximate location, because it identifies the tower sector and not an address.

> [accordion] Does a CDR include the call recording?
>
> No. A CDR is metadata about the call and holds no audio or transcript. A recording is a separate file that exists only if someone turned recording on. Many systems link the two through a shared call identifier, so you can move from a row to its audio.

> [accordion] How long are CDRs kept in India?
>
> Telecom operators must keep CDRs for two years, under the Unified Licence and Rule 45(2) of the 2026 Principal Services Rules. The government can direct a longer period. DoT's 2021 guidelines give call centres and other OSPs a one-year period. Check current text and take legal advice.

> [accordion] Can I get the CDR of my own mobile number?
>
> Usually not by simply asking. Indian lawyers and court summaries describe operators releasing CDRs only to law enforcement or against a court order, including a summons under Section 94 BNSS. For everyday needs, ask your operator for an itemised bill or usage statement instead.

> [accordion] What is the difference between CDR and IPDR?
>
> A CDR describes a phone call: the parties, times, and outcome. An IPDR, or IP detail record, describes a subscriber's internet use. Indian telecom operators must retain both for two years, along with exchange detail records, under the same licence condition.

## Further reading on Vobiz

* [Call detail records API](https://www.vobiz.ai/docs/cdr.md) · [Export CDRs as CSV](https://www.vobiz.ai/docs/cdr/export-cdrs.md) · [Hangup causes](https://www.vobiz.ai/docs/concepts/hangup-causes.md)
* [Voice call logs in the Console](https://www.vobiz.ai/docs/platform/voice/call-logs.md) · [Campaign call logs](https://www.vobiz.ai/docs/platform/campaigns/call-logs.md) · [Call recordings](https://www.vobiz.ai/docs/recording.md)
* [What is a call leg?](https://www.vobiz.ai/docs/blogs/what-is-a-call-leg.md) · [What is SIP trunking?](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md) · [Call recording APIs for compliant pipelines](https://www.vobiz.ai/docs/blogs/call-recording-apis-compliant-pipelines.md)
* [India calling regulations](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md) · [UCC rules on Vobiz](https://www.vobiz.ai/docs/compliance/india/ucc.md)

## Sources

**Indian regulators and government**

* TRAI, [Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, with explanatory memorandum](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf), 18 September 2026.
* TRAI, [Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf), 12 February 2025.
* DoT, [Revised Guidelines for Other Service Providers](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf), 23 June 2021.
* DoT, [Telecommunications (Authorisation for Provision of Principal Telecommunication Services) Rules, 2026](https://www.dot.gov.in/static/uploads/2026/06/b981573e59f32264e099912a9154dacb.pdf), Gazette of 23 June 2026.
* TRAI, [Consolidated Telecom Consumers Protection Regulations, updated to the 12th amendment](https://trai.gov.in/sites/default/files/2025-03/CR_TCPR_28032025.pdf), March 2025.
* TRAI, [Prepaid FAQ](https://www.trai.gov.in/faqcategory/prepaid).
* MeitY, [Digital Personal Data Protection Rules, 2025](https://www.meity.gov.in/static/uploads/2025/11/53450e6e5dc0bfa85ebd78686cadad39.pdf), Gazette of 13 November 2025.
* RBI, [Resolution of Stressed Assets: Revised Framework](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=11218\&Mode=0), 12 February 2018.

**Legal commentary and reporting**

* Khaitan & Co, [Update on the principal telecommunication services authorisation rules](https://www.khaitanco.com/sites/default/files/2026-06/Ergo_Principal%20Telecom%20Authorisation%20Rules_26062026.pdf), June 2026.
* Khaitan & Co, [Update on the miscellaneous telecommunication services authorisation rules](https://www.khaitanco.com/sites/default/files/2026-06/Ergo_Miscellaneous%20Telecom%20Services_30062026.pdf), June 2026.
* Internet Freedom Foundation, [The Government's got your number (and more)](https://internetfreedom.in/the-governments-got-your-number-and-more/), 22 February 2022.
* Hunton Andrews Kurth, [Call Detail Records: The Impact of India's Revised Guidelines for Other Service Providers](https://www.hunton.com/media/publication/82702_digital-call-records-the-impact-of-indias-revised-guidelines-for.pdf), February 2022.
* LiveLaw, [SC directs telecos and ISPs to maintain CDR and other records seized during investigations](https://www.livelaw.in/top-stories/sc-directs-telecos-isps-to-maintain-cdr-and-other-records-seized-during-investigations-159932), 15 July 2020.
* SCC Online, [Delhi High Court on CDR production in an NDPS case](https://www.scconline.com/blog/post/2025/10/22/dhc-on-embargo-on-call-recordsproduction-in-ndps-case/), October 2025.
* Sudhir Rao, Advocate, [Call Details Record of My Own Number](https://sudhirrao.com/insights/call-details-record-own-number-telecom-operator), 19 September 2026.
* Abhishek Gandhi, Advocate, [Access to Call Records Denied](https://advocategandhi.com/access-to-call-records-denied-legal-boundaries-clarified-by-delhi-court/), 3 November 2025.
* ApniLaw, [Section 65B of the Evidence Act vs Section 63 of the Bharatiya Sakshya Adhiniyam](https://www.apnilaw.com/legal-articles/acts/section-65b-of-the-indian-evidence-act-vs-section-63-of-the-bharatiya-sakshya-adhiniyam-admissibility-electronic-evidence/).

**Standards**

* 3GPP, [TS 32.251 definitions, including charging data record (iTecSpec copy)](https://itecspec.com/3gpp/32.251/s/3.1).
* ITU-T, [Recommendation Q.850 summary](https://www.itu.int/dms_pubrec/itu-t/rec/q/T-REC-Q.850-201810-I!!SUM-HTM-E.htm), October 2018.
* ITU-T, [Recommendation P.800.1: Mean opinion score terminology](https://www.itu.int/rec/T-REC-P.800.1/en).

**Reference**

* Wikipedia, ["Call detail record"](https://en.wikipedia.org/wiki/Call_detail_record).
* Wikipedia, ["Mean opinion score"](https://en.wikipedia.org/wiki/Mean_opinion_score).
* Wikipedia, ["Mortality rate"](https://en.wikipedia.org/wiki/Mortality_rate), ["Clinical Dementia Rating"](https://en.wikipedia.org/wiki/Clinical_Dementia_Rating), ["Commander"](https://en.wikipedia.org/wiki/Commander), ["CorelDRAW"](https://en.wikipedia.org/wiki/CorelDRAW), and ["CD-R"](https://en.wikipedia.org/wiki/CD-R).

> [card] [Query your call records on Vobiz](https://www.vobiz.ai/docs/cdr.md)
>
> See every CDR field and start filtering your own call data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.