# CUCM CDR and CMR field reference Canonical: https://warmtransfer.net/knowledge/cucm-cdr-field-reference Last verified: 2026-09-24 A call detail record (CDR) in Cisco Unified Communications Manager (Unified CM) stores call routing, control, and endpoints, while a call management record (CMR) holds diagnostic audio quality metrics[^9]. Unified CM generates both record types only for completed and failed calls without performing any post-processing or reconciliation[^24]. ## Record generation and correlation Unified CM allocates a global call identifier independently on each call server to identify a call[^16]. Originating and terminating leg identifiers each identify a single call leg and remain unique within a cluster[^20]. More than 1 CMR can exist per CDR, and CMRs are generated by Cisco Unified IP Phones, Cisco 7960 series phones, and MGCP gateways rather than by every endpoint[^9][^21]. A complex call—including a conference, a transfer, a forwarded call, or a call through a gateway—produces a set of records written at the end of the call rather than a single record[^1]. A transferred call in Unified CM generates 3 call detail records: 1 for the original call, 1 for the consultation call, and 1 for the final transferred call[^2]. - In the field, grouping transfer records by the global call identifier captures only 2 of the 3 records, because in all 4 worked examples the original call and final transferred call share a global call identifier while the consultation call carries a different one[^17]. - In the field, both the original and consultation records show originating and destination cause values set to 393216 (call split) and originating and destination termination-on-behalf-of fields set to 10 (transfer)[^28]. - In the field, the final transferred record has its join-on-behalf-of field set to 10 (transfer), while this field is 0 on the original and consultation records[^19]. - In the field, the final transferred record's destination leg identifier matches the consultation record's destination leg identifier across all 4 worked transfer examples[^14]. - In the field, the final transferred record's originating leg identifier matches 1 of the original record's 2 leg identifiers depending on which party initiated the transfer, requiring joins between the original and final records to allow either leg identifier[^15]. - In the field, a blind transfer and a consultation transfer are distinguished by the consultation record's duration, which is 0 for a blind transfer and non-zero for a consultation transfer while other markers remain identical[^6]. ## Field formats and timing Date and time fields in Unified CM records are unsigned 32-bit integers retrieved from the operating system and stored as Coordinated Universal Time (UTC)[^31]. When a call never connects, the connect time field contains 0, whereas the disconnect time field is populated regardless of whether connection occurred[^32]. The duration field measures connected time rather than total call life, calculated as the difference between connect time and disconnect time in seconds[^11]. Because duration is 0 when a call never connects and also when a call connects for less than 1 second, a duration value of 0 does not prove that a call went unanswered[^12]. IP addresses are stored internally by Unified CM as unsigned integers but are displayed in the CDR file as signed integers[^18]. To recover an IP address, the value must be converted to a 32-bit hexadecimal value and have its byte order reversed[^18]. ## Call termination cause codes Originating and destination cause values identify why a call was cleared[^8]. The originating cause is populated when the originating party releases the call, while the destination cause is populated when the terminating party releases or rejects the call; unpopulated cause fields contain 0, indicating which end terminated the call[^7]. For on-net call legs, Unified CM determines the cause code value, whereas for off-net legs, the far-end switch determines the value and Unified CM passes it through[^23]. Cause values take their base values from the Q.850 specification[^8]. Unified CM also publishes Cisco-specific termination cause codes outside the Q.850 set, such as 125 (out of bandwidth), 126 (call split), 131 (Call Control Discovery PSTN failover), and IME failure codes spanning through 148[^10]. The Cisco-specific code 393216 (0x60000) represents call split, replacing former code 126 to indicate when a call leg was split off during a transfer and did not form part of the final transferred call[^29]. In the field, every 1 of the 42 SIP rows in the Cisco-specific cause code table carries a Q.850 cause value in the low 16 bits of its code, such as the loop-detected code defined as 0x42000000 plus EXCHANGE_ROUTING_ERROR[^27]. In the field, the high byte of a SIP-derived cause code is not an arithmetic function of the SIP status code: the difference between the status code and marker takes 6 different values across 41 distinct status codes, meaning decoding requires the reference table[^30]. Furthermore, SIP 503 (service unavailable) appears twice in the table mapped to 2 distinct Unified CM cause codes with different Q.850 low words: 41 (temporary failure) and 63 (service or option not available unspecified)[^26]. ## See also - [ITU-T Q.850 call clearing cause values](https://warmtransfer.net/knowledge/q850-cause-codes) - [What a transferred call leaves behind across Cisco products](https://warmtransfer.net/knowledge/webex-transfer-artefacts) - [CUCM to Webex Calling migration](https://warmtransfer.net/knowledge/cucm-to-webex-calling) ## Applicability Applies to: Cisco Unified Communications Manager. Deployments: on-premises. Sources checked 2026-09-15. In the field, the current field reference is published for release 15, while the record type description is published for release 12.5[^13]. In the field, the complete 12.5(1) call detail records guide is retrievable through the Internet Archive as a 244-page PDF, while direct retrieval from cisco.com returns HTTP 403 on every documentation path[^3]. In the field, the release 15 guide is archived across only 2 of its 13 chapters, and the chapter containing transfer examples is not among the archived chapters[^25]. ## What remains uncertain Whether the leg identifier join holds when a gateway or conference is involved is not covered by the sources below. Specific ITU-T Q.850 call termination cause values outside of temporary failure (41), service or option not available unspecified (63), and EXCHANGE_ROUTING_ERROR are not covered by the sources below. Whether the complete CDR field list differs by release is not covered by the sources below. What a call management record contains field by field is not covered by the sources below. Whether the release 15 guide documents the transfer record set in the same manner as release 12.5 is not covered by the sources below. What the high byte of a SIP-derived cause code encodes across all cases is not covered by the sources below. ## Sources [^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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251/cucm_b_cdr-admin-guide-1251_chapter_011.html), Call Information Record Types. Checked 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, page 124. Checked 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Internet Archive capture 20250323135843 of the complete book PDF. Checked 2026-09-15. [^4]: One row of the Cisco-specific cause code table is internally inconsistent: the BAD_EXTENSION row (CCM_SIP_420_BAD_EXTENSION) gives a decimal value of 83886207 against a hexadecimal value of 0x1500007F, which is 352321663. That decimal does not match any other row's decimal in the table, including the NOT_FOUND row's (CCM_SIP_404_NOT_FOUND), which is 83886081 and agrees with its own hex 0x5000001 (disputed). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Table 13, rows CCM_SIP_404_NOT_FOUND and CCM_SIP_420_BAD_EXTENSION. Checked 2026-09-24. [^5]: 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 (disputed). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Table 13, row CCM_SIP_420_BAD_EXTENSION. Checked 2026-09-15. [^6]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126. Checked 2026-09-15. [^7]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Call Clearing Causes. Checked 2026-09-15. [^8]: The originating and destination cause values reflect why each party cleared the call and take their values from the Q.850 specification. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions, origCause_value and destCause_value. Checked 2026-09-15. [^9]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251/cucm_b_cdr-admin-guide-1251_chapter_011.html), Call Information Record Types. Checked 2026-09-15. [^10]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Call Termination Cause Codes, Table 12. Checked 2026-09-15. [^11]: 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. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions, duration. Checked 2026-09-15. [^12]: 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. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions, duration. Checked 2026-09-15. [^13]: The current field reference is published for release 15 and the record type description the corpus could reach is published for release 12.5 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251/cucm_b_cdr-admin-guide-1251_chapter_011.html), The 2 guides compared by their own release designations. Checked 2026-09-15. [^14]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126. Checked 2026-09-15. [^15]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126. Checked 2026-09-15. [^16]: The global call identifier designates a unique call identity value assigned to each call and is allocated independently on each call server. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions, globalCallID_callId. Checked 2026-09-15. [^17]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, the four worked example tables on pages 124 to 126. Checked 2026-09-15. [^18]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Convert Signed Decimal Value to IP Address. Checked 2026-09-15. [^19]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, page 124, and the four worked examples. Checked 2026-09-15. [^20]: The originating and terminating leg identifiers each identify one leg of a call and are unique within a cluster. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions, origLegCallIdentifier and destLegCallIdentifier. Checked 2026-09-15. [^21]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251/cucm_b_cdr-admin-guide-1251_chapter_011.html), Call Information Record Types, Cisco Call Detail Records overview. Checked 2026-09-15. [^22]: No archive reachable from this programme holds the release 15 CDR examples chapter: the Internet Archive index contains exactly 3 captures under that guide's path, being the book landing page and 2 chapters, and archive.today holds none (field report). Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), Internet Archive CDX index query over the release 15 guide path. Checked 2026-09-15. [^23]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Call Clearing Causes. Checked 2026-09-15. [^24]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251/cucm_b_cdr-admin-guide-1251_chapter_011.html), Call Information Record Types, Cisco Call Detail Records overview. Checked 2026-09-15. [^25]: 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 (field report). Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), Internet Archive probe of the 13 chapter addresses of the release 15 guide. Checked 2026-09-15. [^26]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Table 13, the two service unavailable rows. Checked 2026-09-15. [^27]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Table 13 Cisco-Specific Call Termination Cause Codes. Checked 2026-09-15. [^28]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Transferred Calls, page 124, and the four worked examples. Checked 2026-09-15. [^29]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Table 13 Cisco-Specific Call Termination Cause Codes. Checked 2026-09-15. [^30]: 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 (field report). Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23](https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf), Call Detail Records chapter, Table 13 Cisco-Specific Call Termination Cause Codes. Checked 2026-09-15. [^31]: 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. Source: [Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), Call Information Record Types](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251/cucm_b_cdr-admin-guide-1251_chapter_011.html), Call Information Record Types, time formats. Checked 2026-09-15. [^32]: The connect time field holds 0 when the call never connects and the disconnect time field is set even when the call never connects. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions, dateTimeConnect and dateTimeDisconnect. Checked 2026-09-15.