Source note · Cross-platform CDR normalization model
Unified CM logs calls to busy or bad destinations as normal calls whose calling or called party cause field explains why the call did not connect, with Date/Time Connect left blank.
Checked 2026-09-24
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- CDR generation
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Release 15 and SUs
- Checked
- 2026-09-24
Sources
- Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - CDR Examples — Cisco Systems · tier 2 current vendor documentation · CDR Examples chapter, section Calls with Busy or Bad Destinations
Cite this note
APA
WarmTransfer. (2026, September 24). Cross-platform CDR normalization model: source note cdr-normalization-cucm-busy-bad-destination. WarmTransfer. https://warmtransfer.net/knowledge/claims/cdr-normalization-cucm-busy-bad-destination
BibTeX
@misc{warmtransfer-claim-cdr-normalization-cucm-busy-bad-destination,
title = {Cross-platform CDR normalization model: source note cdr-normalization-cucm-busy-bad-destination},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cdr-normalization-cucm-busy-bad-destination},
note = {Source note cdr-normalization-cucm-busy-bad-destination, checked 2026-09-24}
}