Claim record · CUCM CDR and CMR field reference
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.
fact · verified 2026-09-15
When the originating party releases the call, the OrigCause gets populated. When the terminating party releases the call, or the call is rejected, the DestCause gets populated. When unpopulated, the cause code value shows zero.
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- Call detail records
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Release 12.5(1)
- Status
- fact
- Confidence
- 0.90
- Verified
- 2026-09-15
Sources
- Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23 — Cisco Systems, Inc., served by the Internet Archive · tier 2 current vendor documentation · Call Detail Records chapter, Call Clearing Causes
Cite this claim
APA
WarmTransfer. (2026, September 15). CUCM CDR and CMR field reference: claim cucmcdr-cause-is-set-by-whichever-party-released. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucmcdr-cause-is-set-by-whichever-party-released
BibTeX
@misc{warmtransfer-claim-cucmcdr-cause-is-set-by-whichever-party-released,
title = {CUCM CDR and CMR field reference: claim cucmcdr-cause-is-set-by-whichever-party-released},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucmcdr-cause-is-set-by-whichever-party-released},
note = {Claim cucmcdr-cause-is-set-by-whichever-party-released, verified 2026-09-15}
}