Source note · Cross-platform CDR normalization model
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 · Checked 2026-09-24
- Vendor
- multi-vendor
- Product
- CDR normalisation model
- Subsystem
- identity and keys
- Deployment
- on-premises, multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions — Cisco Systems, Inc. (Webex Help Center) · tier 2 current vendor documentation · CDR Field Descriptions, rows origLegCallIdentifier and globalCallId_ClusterId; see also ms-graph-pstncalllogrow-resource row callId
Cite this note
APA
WarmTransfer. (2026, September 24). Cross-platform CDR normalization model: source note cdr-normalization-composite-leg-key. WarmTransfer. https://warmtransfer.net/knowledge/claims/cdr-normalization-composite-leg-key
BibTeX
@misc{warmtransfer-claim-cdr-normalization-composite-leg-key,
title = {Cross-platform CDR normalization model: source note cdr-normalization-composite-leg-key},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cdr-normalization-composite-leg-key},
note = {Source note cdr-normalization-composite-leg-key, checked 2026-09-24}
}