DemandFlow Support Centre

CDR: CDR

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A call detail record capturing telephony event data including parties, timing, network routing, quality, and billing.

CDR: CDR

A call detail record capturing telephony event data including parties, timing, network routing, quality, and billing.

Default definition. This article describes the default CDR definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches CDR.

Entity properties

PropertyValue
Entity codeCDR
Display nameCDR
PluralCDRs
Level320

Use cases

CDR is a telecoms-specific entity that stores individual call detail records. Each record represents a single telephony event (voice, video, SMS, data, VoLTE, etc.) with comprehensive metadata across five panels. The General panel captures call identification (call ID, session ID), type, direction, status, and the parties involved (A-number/B-number, IMSI, IMEI). The Network panel records the infrastructure path (originating/terminating switches, trunks, cell IDs, LACs, MSCs) and flags for roaming and international calls.

Fields

General: Call Information

FieldTypeRequiredNotes
nametextYesRead-only. Unique identifier for this CDR
callIdtextNetwork call identifier
sessionIdtextSIP session identifier
callTypeenumYesCall Type. Valid ids: 1 (Voice), 2 (Video), 3 (SMS), 4 (MMS), 5 (Data), 6 (VoLTE), 7 (VoWiFi), 8 (Conference), 9 (Emergency).
directionenumYesDirection. Valid ids: 1 (Inbound), 2 (Outbound), 3 (Internal), 4 (Transit), 5 (Forwarded).
callStatusenumYesCall Status. Valid ids: 1 (Answered), 2 (No Answer), 3 (Busy), 4 (Failed), 5 (Abandoned), 6 (Voicemail), 7 (Transferred), 8 (Blocked).

General: Parties

FieldTypeRequiredNotes
callingNumbertextYesCalling Number (A-Number).
calledNumbertextYesCalled Number (B-Number).
originalCalledNumbertextBefore any forwarding
finalCalledNumbertextAfter all redirections
callingNametextCalling Party Name.
calledNametextCalled Party Name.
imsitextInternational Mobile Subscriber Identity
imeitextInternational Mobile Equipment Identity

General: Timing

FieldTypeRequiredNotes
startTimedatetimeYesStart Time.
answerTimedatetimeAnswer Time.
endTimedatetimeYesEnd Time.
durationnumberRead-only. Duration (seconds).
billableDurationnumberBillable Duration (seconds).
ringDurationnumberRing Duration (seconds).
holdDurationnumberHold Duration (seconds).

Network: Network Elements

FieldTypeRequiredNotes
originatingSwitchtextOriginating Switch.
terminatingSwitchtextTerminating Switch.
transitSwitchestext (multi-line)Intermediate switches in call path
originatingTrunktextOriginating Trunk.
terminatingTrunktextTerminating Trunk.
routingNumbertextRouting Number.

Network: Location

FieldTypeRequiredNotes
originatingCelltextOriginating Cell ID.
terminatingCelltextTerminating Cell ID.
originatingLACtextLocation Area Code
terminatingLACtextTerminating LAC.
originatingMSCtextMobile Switching Center
terminatingMSCtextTerminating MSC.
roamingIndicatorbooleanRoaming.
internationalCallbooleanInternational.

Technical: Call Quality

FieldTypeRequiredNotes
codecenumCodec. Valid ids: 1 (G.711), 2 (G.729), 3 (G.722), 4 (AMR), 5 (AMR-WB), 6 (EVS), 7 (Opus), 8 (H.264), 9 (H.265).
mosnumberMean Opinion Score (1-5)
jitternumberJitter (ms).
packetLossnumberPacket Loss (%).
latencynumberLatency (ms).
rtpPacketsSentnumberRTP Packets Sent.
rtpPacketsReceivednumberRTP Packets Received.

Technical: Protocol Details

FieldTypeRequiredNotes
protocolenumSignaling Protocol. Valid ids: 1 (SIP), 2 (H.323), 3 (SS7), 4 (ISUP), 5 (MGCP), 6 (IMS).
sipResponseCodetextSIP Response Code.
releaseCodetextRelease Code.
releaseCausetextRelease Cause.
q850CausenumberQ.850 Cause Code.

Billing: Charging Information

FieldTypeRequiredNotes
chargeAmountnumberCharge Amount.
currencyreference → CURRENCYCurrency.
rateAppliednumberRate per minute/unit
rateTypeenumRate Type. Valid ids: 1 (Peak), 2 (Off-Peak), 3 (Weekend), 4 (Holiday), 5 (Special).
billingClassenumBilling Class. Valid ids: 1 (Local), 2 (National), 3 (International), 4 (Premium), 5 (Toll-Free), 6 (Mobile), 7 (Roaming).

Billing: Account Information

FieldTypeRequiredNotes
accountNumbertextAccount Number.
customerCodetextCustomer Code.
costCentertextCost Center.
projectCodetextProject Code.
taxAmountnumberTax Amount.
taxRatenumberTax Rate (%).

Analysis: Analytics & Fraud Detection

FieldTypeRequiredNotes
fraudScoregaugeRead-only. Fraud Score.
fraudIndicatorsmultiselectFraud Indicators.
qualityScoregaugeRead-only. Quality Score.
customerExperienceenumCustomer Experience. Valid ids: 1 (Excellent), 2 (Good), 3 (Fair), 4 (Poor).
tagsmultiselectTags.

Relationships

  • Lookups: currency points at a CURRENCY record.

Creating a CDR via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "CDR",
  "level":    320,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "CDR ID",
  "callType": "1",
  "direction": "1",
  "callId": "Call ID"
}

Listing CDRs records

GET /v1/entities/CDR/SUB

See also

cdrcdrs

Was this article helpful?

← Back to Knowledge Base