Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

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

Published

unknown

Updated

unknown

Accessed

2026-09-15

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• A cross-platform normalised leg key has to be composite (platform, tenant or cluster, native id), because Unified CM leg identifiers are unique only within a cluster and the Teams PSTN callId is not guaranteed unique. inferred in context
• Unified CM origCause_value and destCause_value carry the clearing reason as ITU-T Q.850 cause codes plus some Unified CM-defined codes. in context
• In Unified CM 15 CDRs, dateTimeConnect is zero when the call is never answered. in context
• Unified CM 15 CDR duration is the difference between connect time and disconnect time in seconds, and it remains zero if the call never connects. in context
• Unified CM assigns a globalCallID_callId value to each call, and the CDR also carries globalCallID_callManagerId (the Unified CM node identity) and globalCallId_ClusterId (the cluster identity). in context
• Unified CM lastRedirectDn holds the number of the next-to-last hop in a redirected call, and lastRedirectRedirectReason gives the last redirect reason from a separate code table. in context
• Unified CM origLegCallIdentifier and destLegCallIdentifier identify the originating and terminating legs of a call and are unique only within a cluster. in context
• Unified CM originalCalledPartyNumber is the number the call was first presented to before any forwarding, and finalCalledPartyNumber is the number the call was finally presented to. in context
• Unified CM incomingProtocolCallRef and outgoingProtocolCallRef carry a globally unique protocol call reference, alphanumeric and truncated to 32 characters. in context
• In Cisco Unified CM 15 CDR files, cdrRecordType 1 marks an end call detail record, 2 marks a CMR record, and 0 (start record) is not used. in context
• Unified CM 15 stores dateTimeOrigination, dateTimeConnect and dateTimeDisconnect as UTC. in context
• The CDR field chapter defines the unique call key as globalCallId_ClusterId plus globalCallId_CMId plus globalCallId_CallId, and the CMR also carries a globalCallId_ClusterId text field. in context
• A join across exports from more than one cluster should include globalCallId_ClusterId alongside the two Global Call ID columns, because callManagerId and callId are only described as unique within a cluster's own numbering. inferred in context
• In the CDR, origLegCallIdentifier identifies the originating leg and destLegIdentifier the terminating leg, and each value is unique within a cluster; destLegIdentifier may be 0. in context
• In Unified CM CDRs, call termination cause code 1 means Unallocated (unassigned) number. in context
• In Unified CM CDRs, cause code 125 is the Cisco-specific Out of bandwidth code. in context
• In Unified CM CDRs, cause code 3 means No route to destination. in context
• In Unified CM CDRs, cause code 34 means No circuit/channel available, and cause code 41 means Temporary failure. in context
• Unified CM's Cisco-specific cause code table includes 1107296281 (0x42000019), CCM_SIP_482_LOOP_DETECTED, for a SIP 482 Loop Detected response. in context
• The Release 15 CDR field huntPilotDN holds the hunt pilot DN through which the call was routed and huntPilotPartition holds that DN's partition; both default to an empty string. in context
• When huntPilotDN is not populated, Cisco advises checking pattern usage 7 (PATTERN_HUNT_PILOT) to identify hunt list calls. in context
• The originating and destination cause values reflect why each party cleared the call and take their values from the Q.850 specification. in context
• 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. in context
• 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. in context
• The global call identifier designates a unique call identity value assigned to each call and is allocated independently on each call server. in context
• The originating and terminating leg identifiers each identify one leg of a call and are unique within a cluster. in context
• 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 in context
• 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 in context
• The connect time field holds 0 when the call never connects and the disconnect time field is set even when the call never connects. in context

Cite this source record

APA

WarmTransfer. (2026, September 15). Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-cdr-field-descriptions-15

BibTeX

@misc{warmtransfer-cisco-cucm-cdr-field-descriptions-15,
  title  = {Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-cdr-field-descriptions-15},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-15}
}