This document defines a standard specification for the supply of wholesale billing data, for the UK telecom marketplace. The specification covers outbound, inbound and mobile call detail records (CDRs) and also recurring and fixed service charges (SDRs). The specification was developed following a consultation between the UK’s leading telecoms billing vendors.
Standard CDR Format
Version 3.0
Table of contents
1. Introduction …………………………………………………………………………………………………………………… 2
2. General Format ………………………………………………………………………………………………………………. 2
3. General Format for any Call Detail Records (CDR) ……………………………………………………………….. 4
3.1 Purpose of this format ……………………………………………………………………………………………… 4
3.2 File naming convention …………………………………………………………………………………………….. 4
3.3 CDR Format …………………………………………………………………………………………………………….. 5
3.4 Header Row …………………………………………………………………………………………………………….. 9
3.5 Call rating rules/ logic …………………………………………………………………………………………….. 10
3.6 Example CDR file ……………………………………………………………………………………………………. 10
4. Service Charge Event Output (SDRs) ………………………………………………………………………………… 11
4.1 Purpose of this format ……………………………………………………………………………………………. 11
4.2 File naming convention …………………………………………………………………………………………… 11
4.3 SDR Format …………………………………………………………………………………………………………… 11
4.4 Header Row …………………………………………………………………………………………………………… 14
4.5 Example SDR file ……………………………………………………………………………………………………. 14
1. Introduction
This document outlines a UK industry standard for the billing data files used to define the wholesale voice and data products supplied by an operator. The standard covers file formats for both call detail record (CDRs) and also service charge detail records (SDRs). The document gives resellers and CPs the information they require in order to bill their end-user customers.
This standard includes two file formats covering the following services:
Call Charges (Section 3)
– Fixed Line and VOIP CDR
– Mobile CDR
– Inbound calls (including Inbound Legs of multi-leg calls)
Service Charges (Section 4)
– Service Charge Output
The files contain the core billing data for onward billing and other common billable event records.
2. General Format
All files to be standard text files (PC ASCII encoding), each record terminated by a carriage return and line feed characters. All fields are comma delimited and field values are qualified with “double quotes”. NULL values for optional fields should still be presented with quotations, e.g.: “”.
Call Charges CDR format
The format for all types of call charges is covered in section 3. The CDR provider may choose to provide all call types mixed together in a single file(s). Alternatively, different services may be separated into different files. .
The ‘Call Type’ identifier is key to determine whether the call record is Outbound, Inbound, Mobile etc.
In many cases a ‘Call Class’ may be used to identify the charge group that should be applied when rating the call. The CDR provider should also publish a list of call classes it uses in conjunction with the standard format.
Service Charges SDR format
The service charge format is purely used for fixed and recursive charges e.g. Line rentals, License fees, set-up charges etc.
E.164 Format for Telephone Numbers
The E.164 recommendation, also called the “international public telecommunications numbering plan,” was first approved and published by the ITU-T in May 1997. The E.164 recommendation establishes a standard framework for every country to create its own international phone numbers.
[+][country code][subscriber number including area code]
Revision History
| Version | Section | Change | Date |
|---|---|---|---|
| 1.0 | First Draft of suggested standard CDR format structure | 23/05/2012 | |
| 1.1 | All | Updated following meeting of billing vendors | 29/05/2012 |
| 1.2 | All | Updated following meeting of billing vendors | 08/06/2012 |
| 1.3 | All | Merged all call formats into one | 22/08/2012 |
| 1.4 | All | Document formatting and added new field | 18/09/2012 |
| 1.5 | 3–7 | Added Account Ref to file name | 20/09/2012 |
| 2.0 | TC/SR | Changes as a result of billing group meeting | 12/11/2012 |
| 2.0 | TC | Tidy document and create final approved version following sign off by the billing group | 26/09/2013 |
| 3.0 | TC | Changes as a result of billing group meeting | 28/01/2014 |
| 3.0 | TC | Changes as a result of billing group meeting | 23/04/2015 |
Effective Date
The UK standard CDR version 3.0 is effective as of 1st July 2015. It will co-exist with version 2.0 for a
period of 12 months.
The previous UK standard CDR version 2.0 will be withdrawn on 30th June 2016, thereafter only
version 3.0 will be considered as the standard. All new CPs wishing to generate wholesale CDR/SDR
files after 1st July 2015 should only adopt version 3.0 of the standard.
3. General Format for any Call Detail Records (CDR)
3.1 Purpose of this format
To be used when producing a CDR for calls made of any type e.g. Fixed Line, VOIP services,
Mobile, Outbound etc. It is possible for all these call types to be mixed together in one file.
3.2 File naming convention
The file must be named in the following way:
RID_ Frequency_FileType_AAAAAA_DDMMYYYY_SSSSSS_CCCCCC_REF_VV.txt
Where monthly, DDMMYYYY represents the billing period date (last day of the month in which
the calls were made). Where daily, DDMMYYYY represents the day on which the calls were made.
RID = RID code of CDR provider
Frequency = The period of the file contents (either “Daily” or “Monthly”)
FileType = “Calls” this denotes that the file contains call data
AAAAAA = An account reference the CDR provider can use to denote the receiver of the CDR i.e. the reseller. (no limit on number of digits i.e. size of number).
SSSSSS = sequence number (no limit on number of digits i.e. size of number). Every file produced for a particular customer (regardless of type), should have a sequence number increasing by 1 as each subsequent file is produced.
CCCCC = record count (no limit on number of digits i.e. size of number)
REF = File content reference. Used to denote different content types when the file contains a specific call services e.g. “SIP”, “CPS”, “Mobile”, “Inbound” or “IDA” etc. If
the file may contain a mixture of different call services, then use “ALL” as a REF. Note: the REF is for information purposes and should only be used to help identity
the type of service contained in the file.
VV = The version of the standard that has been used. This should be set to “V3”
Example:
Monthly: ZZZ_Monthly_Calls_ABC001_31012012_13_189_SIP_V3.txt
Daily: ZZZ_ Daily _Calls_ABC001_29062012_394_21125_IDA_V3.txt
3.3 CDR Format
The table below shows the columns required.
| # | Field Name | Description | Example | Mandatory | Max Size |
|---|---|---|---|---|---|
| 1 | Call Type | The type of call being made. For example call types: V = outbound voice call, VOIP = Voice over IP call D = Data/ISDN Call C = Conference call N = Inbound call (billable) I = Standard Inbound call (usually not billable e.g. Raw call data) U = Unanswered call B = Busy Call X = Call failed M = Mobile call (made from mobile device) G = GPRS Data |
“V” | Yes | 4 |
| 2 | Call Cause (Definition required) |
Further defines a call from just being a certain call type.
For example call type V can be used for both fixed line and NGN outbound calls. |
“0” | No | 1 |
| 3 | Customer Identifier (CLI) | An identifier to which the call charge can be allocated. This is most commonly the customer Caller Line Identity (CLI). It must be in E.164 format if it is an actual telephone number, else can be a reference number e.g. an IP address or email address. |
“+441234567890” | Yes | 100 |
| 4 | Telephone Number Dialled (or the caller’s number for inbound calls) |
Telephone number called. All telephone numbers should be displayed in E.164 format. The convention of using 000 for international data calls should NOT be used A Telephone number must be set. The only exception to this rule is when a call class has been used to identify the charging group. |
“+441234567890” | Yes | 50 |
| 5 | Call Date | Date call is made (DD/MM/YYYY) | “31/12/2012” | Yes | 10 |
| 6 | Call Time | Time call is made (HH:MM:SS) | “09:15:30” | Yes | 10 |
| 7 | Duration | Call duration in seconds | “237” | Yes | 10 |
| 8 | Bytes Transmitted |
Only applies if Call type is G otherwise ”” if not used. Number of bytes of data transmitted. Numeric.
Note: If Used the sum of [Bytes Transmitted] + [Bytes Received] must be equal to the Total Bytes Transferred |
“12000” | No | 20 |
| 9 | Bytes Received | Only applies if Call type is G otherwise ”” if not used. Number of bytes of data received. Numeric.
Note: If Used the sum of [Bytes Transmitted] + [Bytes Received] must be equal to the Total Bytes Transferred |
“12000” | No | 20 |
| 10 | Description | Destination description | “London” | No | 100 |
| 11 | Chargecode | A destination description used on supplier’s billing system to bill the call. | “UK Local” | No | 100 |
| 12 | Time Band | The time band within which the call was made. For information purposes. Typically: Peak, OffPeak, Weekend, Special1, Special2, Special3, Special4 (optional) Note: The time band is denoted as the band that was used at the time the call was initiated, regardless of whether the call crossed into another time band. |
“Peak” | No | 10 |
| 13 | Salesprice | Sales price in the primary unit of currency e.g. pounds, euros, dollars etc. (no currency symbols to be included). This is the final sales price for the call after any bundles have been applied
Numeric (up to 4 decimal places). For example: 12.5 pence is 0.125 |
“0.125” | No | 9 |
| 14 | Salesprice (pre-bundle) | This is the sales price before any bundle has been applied. If no bundle has been used, this field should be set to be the same as the Salesprice above.
If this field is unused, set to “” Numeric (up to 4 decimal places) in the primary unit of currency e.g. pounds, euros, dollars etc. (no currency symbols to be included). |
“0.125” | No | 9 |
| 15 | Extension | User’s extension number, if known | “2142” | No | 6 |
| 16 | DDI | User’s DDI number, if known in E.164 Format | “+441234567890” | No | 50 |
| 17 | Grouping ID | Common numeric identifier to group records to represent elements of a single call. For example connections in a single conference call, or multiple legs of a single inbound call. | “1” | No | 100 |
| 18 | Call Class (Feature) |
Alpha numeric code referencing how the call should be billed. Used for when the dialling code of the dialled number cannot be used to rate the call.
For example: b) There are some kinds of calls (e.g. Operator assistance and reverse charges) that cannot be rated by number dialled. A unique call class should be allocated for each of these and used here. Typically this field could contain the feature codes that BT use to define certain call types e.g. “BT312CR” = Call Return The supplier the CDR file should also provide a list of all call classes that can be used. |
“BT313OACA” | No (but Yes if calltype is ‘M’) |
50 |
| 19 | Carrier | Origin carrier | “Gamma” | No | 150 |
| 20 | Recording | 1 = recorded, 0 = not | “0” | No | 1 |
| 21 | VAT | S = standard, Z = zero, E = exempt | “S” | No | 1 |
| 22 | Country of Origin | ISO alpha-3 code | “GBR” | No | 3 |
| 23 | Network | Mobile network (required if mobile call) | “O2” | Conditional | 10 |
| 24 | Retail Tariff Code | Represents buy tariff | “BB” | No | 8 |
| 25 | Remote Network | Roamed network | “TC” | No | 50 |
| 26 | APN | Access Point Name (GPRS) | “Blackberry” | No | 15 |
| 27 | Diverted Number | Mapped NGN number | “+441234567890” | No | 15 |
| 28 | Ring Time | Ring duration in seconds | “75” | No | 10 |
| 29 | Record ID | Unique record identifier | “2314132A23145782345” | No | 50 |
| 30 | Currency | ISO 4217 code | “GBP” | No | 3 |
| 31 | Presentation Number | CLI presented | “+441234567890” | No | 30 |
| 32 | Network Access Reference | Endpoint or access reference | “DC2N92JAZ001” | No | 50 |
| 33 | NGCS Access Charge | Access charge component | “0.125” | No | 15 |
| 34 | NGCS Service Charge | Service charge component | “1.15” | No | 15 |
| 35 | Total Bytes Transferred | Total data transferred | “12000” | No | 20 |
| 36 | User ID | User identifier | “HealthCoMainHQ2014” | No | 50 |
| 37 | Onward Billing Reference | Billing reference for customers | “21427” | No | 14 |
| 38 | Contract Name | Associated contract | “Custom Name[1067]” | No | 100 |
| 39 | Bundle Name | Name of applied bundle | “500Mb Data” | No | 100 |
| 40 | Bundle Allowance | Total bundle units | “512000” | No | 50 |
| 41 | Discount Reference | Promo reference | “628374” | No | 50 |
| 42 | Routing Code | Network routing code | “1656” | No | 10 |