cdr analytics · stub
CUCM CDR and CMR field reference
Verified 2026-09-15 · 30 claims · sources tier 2
Also known as call management record, globalCallID_callId, origCause_value.
Stub. This topic has 30 verified claims and no published article. The claims below are exactly what the corpus holds today.
So far, no summary has been generated for this topic. The claims below are what the corpus currently holds.
See also
Related to
- CUCM to Webex Calling migration — The record format a migration leaves behind
- ITU-T Q.850 call clearing cause valuesstub — The specification the cause column of a call detail record is defined by
- What a transferred call leaves behind across Cisco products — A complex call writes a set of records on the on-premises side too
- What the Webex Calling detailed call history records — The on-premises counterpart of the cloud call history field set
Referenced by
- ITU-T Q.850 call clearing cause valuesstub — CUCM call detail record cause values are Q.850 values plus Cisco-specific additions
- What a transferred call leaves behind across Cisco products — The Unified CM side of what a transfer leaves behind in records
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | A conference a transfer a forwarded call or a call through a gateway each produces a set of records written at the end of the call rather than a single record. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types · Call Information Record Types | fact | 0.90 | 2026-09-15 |
| 2 | A transferred call in Unified CM generates three call detail records: one for the original call, one for the consultation call, and one for the final transferred call. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, page 124 | fact | 0.90 | 2026-09-15 |
| 3 | The complete 12.5(1) call detail records guide is retrievable and hashable by this programme through the Internet Archive as a 244-page PDF of original bytes, although cisco.com itself refuses direct retrieval from this network with HTTP 403 on every documentation path. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Internet Archive capture 20250323135843 of the complete book PDF | field-pattern | 0.90 | 2026-09-15 |
| 4 | One row of the Cisco-specific cause code table is internally inconsistent: the bad extension row gives a decimal value of 83886207 against a hexadecimal value of 0x1500007F, which is 352321663, and the decimal given is instead the marker used by the not found row. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Table 13, row CCM_SIP_420_BAD_EXTENSION | disputed | 0.60 | 2026-09-15 |
| 5 | A blind transfer and a consultation transfer are distinguished in the record set by the consultation record's duration: it is 0 for a blind transfer and non-zero for a consultation transfer, while every other marker on the three records is identical. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126 | field-pattern | 0.90 | 2026-09-15 |
| 6 | The originating cause is populated when the originating party releases the call and the destination cause when the terminating party releases it or the call is rejected, and an unpopulated cause field shows zero, so which of the two fields is non-zero says which end ended the call. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Call Clearing Causes | fact | 0.90 | 2026-09-15 |
| 7 | The originating and destination cause values reflect why each party cleared the call and take their values from the Q.850 specification. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions, origCause_value and destCause_value | fact | 0.90 | 2026-09-15 |
| 8 | A call detail record stores the endpoints of a call and its control and routing while a call management record holds diagnostic information about the quality of the streamed audio and more than one management record can exist per detail record. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types · Call Information Record Types | fact | 0.90 | 2026-09-15 |
| 9 | Unified CM publishes call termination cause codes beyond the Q.850 set, marked Cisco specific in the table, including 125 out of bandwidth, 126 call split, 131 Call Control Discovery PSTN failover and a run of IME failure codes through 148. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Call Termination Cause Codes, Table 12 | fact | 0.90 | 2026-09-15 |
| 10 | The duration field is the difference between the connect time and the disconnect time in seconds and so measures connected time rather than the life of the call. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions, duration | fact | 0.90 | 2026-09-15 |
| 11 | The duration field is zero both when a call never connects and when it connects for less than one second, so a duration of zero is not evidence that a call was never answered. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions, duration | fact | 0.90 | 2026-09-15 |
| 12 | The current field reference is published for release 15 and the record type description the corpus could reach is published for release 12.5. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types · The 2 guides compared by their own release designations | field-pattern | 0.90 | 2026-09-15 |
| 13 | The final transferred record's destination leg identifier equals the consultation record's destination leg identifier in all four worked transfer examples, which is the link between the consultation and the surviving call. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126 | field-pattern | 0.90 | 2026-09-15 |
| 14 | The final transferred record's originating leg identifier is one of the original record's two leg identifiers, and which of the two it is depends on which party transferred, so a join from the original to the final record has to allow either. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126 | field-pattern | 0.90 | 2026-09-15 |
| 15 | The global call identifier designates a unique call identity value assigned to each call and is allocated independently on each call server. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions, globalCallID_callId | fact | 0.90 | 2026-09-15 |
| 16 | Grouping a transfer's records on the global call identifier collects two of the three: in all four worked examples the original and the final transferred record share one global call identifier and the consultation record carries a different one. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126 | field-pattern | 0.90 | 2026-09-15 |
| 17 | Unified CM stores IP addresses as unsigned integers and the call detail record file displays them as signed integers, and recovering the address means converting to a 32-bit hexadecimal value and reversing the byte order. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Convert Signed Decimal Value to IP Address | fact | 0.90 | 2026-09-15 |
| 18 | The final transferred record is the one whose join-on-behalf-of field is set to 10 meaning transfer, and that field is 0 on the original and consultation records. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, page 124, and the four worked examples | field-pattern | 0.90 | 2026-09-15 |
| 19 | The originating and terminating leg identifiers each identify one leg of a call and are unique within a cluster. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions, origLegCallIdentifier and destLegCallIdentifier | fact | 0.90 | 2026-09-15 |
| 20 | More than one call management record can exist per call detail record, and management records are produced by Cisco Unified IP Phones, Cisco 7960 series phones and MGCP gateways rather than by every endpoint. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types · Call Information Record Types, Cisco Call Detail Records overview | fact | 0.90 | 2026-09-15 |
| 21 | For on-net call legs Unified CM determines the cause code value and for off-net legs the far-end switch determines it, so a cause on an off-net leg is a foreign network's statement carried through rather than Unified CM's own diagnosis. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Call Clearing Causes | fact | 0.90 | 2026-09-15 |
| 22 | Only completed calls and failed calls generate call detail and call management records, and Unified CM performs no post-processing on either, so the files are the raw record set and nothing in them has been reconciled. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types · Call Information Record Types, Cisco Call Detail Records overview | fact | 0.90 | 2026-09-15 |
| 23 | The release 15 reporting and billing guide is archived only chapter by chapter and only 2 of its 13 chapters are captured, so the release comparison the corpus wants cannot be made from the archive: the chapter carrying the transfer examples is not among them. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · Internet Archive probe of the 13 chapter addresses of the release 15 guide | field-pattern | 0.90 | 2026-09-15 |
| 24 | The Cisco-specific cause code table lists SIP 503 service unavailable twice with two different codes whose Q.850 low words differ, 41 temporary failure and 63 service or option not available unspecified, so one SIP status maps to two Unified CM cause codes. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Table 13, the two service unavailable rows | fact | 0.90 | 2026-09-15 |
| 25 | Every one of the 42 SIP rows of the Cisco-specific cause code table has a Q.850 cause value in the low 16 bits of its code, and the guide states the construction for one row by writing the loop-detected code as 0x42000000 plus EXCHANGE_ROUTING_ERROR. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Table 13 Cisco-Specific Call Termination Cause Codes | field-pattern | 0.90 | 2026-09-15 |
| 26 | On both the original and the consultation record of a transfer, the originating and destination cause values are set to 393216 meaning split and the originating and destination termination-on-behalf-of fields are set to 10 meaning transfer. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Transferred Calls, page 124, and the four worked examples | field-pattern | 0.90 | 2026-09-15 |
| 27 | The Cisco-specific code 393216, hexadecimal 0x60000, is call split and the table records that it was formerly 126; it is set when a call terminates during a transfer because it was split off and was not part of the final transferred call. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Table 13 Cisco-Specific Call Termination Cause Codes | fact | 0.90 | 2026-09-15 |
| 28 | The high byte of a SIP-derived Unified CM cause code is not a fixed function of the SIP status code: across the 41 distinct status codes in the table the difference between the status code and the marker takes 6 different values, so decoding the SIP status out of a cause code needs the table rather than arithmetic. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 · Call Detail Records chapter, Table 13 Cisco-Specific Call Termination Cause Codes | field-pattern | 0.90 | 2026-09-15 |
| 29 | The date and time fields are unsigned 32-bit integers holding a time value obtained from the operating system and stored as coordinated universal time. Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types · Call Information Record Types, time formats | fact | 0.90 | 2026-09-15 |
| 30 | The connect time field holds 0 when the call never connects and the disconnect time field is set even when the call never connects. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions, dateTimeConnect and dateTimeDisconnect | fact | 0.90 | 2026-09-15 |
Sources
tier 2 current vendor documentation
Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types
tier 2 current vendor documentation
Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23
tier 2 current vendor documentation
Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions
Cite this page
APA
WarmTransfer. (2026, September 15). CUCM CDR and CMR field reference. WarmTransfer. https://warmtransfer.net/knowledge/cucm-cdr-field-reference
BibTeX
@misc{warmtransfer-cucm-cdr-field-reference,
title = {CUCM CDR and CMR field reference},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/cucm-cdr-field-reference},
note = {Verified 2026-09-15}
}