What the Webex Calling detailed call history records

Verified 2026-09-15 · 30 claims · sources tier 2

Also known as Correlation ID, Original called party ID, WxCC consult merge status, device owner identifier, recall type.

The Webex Calling detailed call history table publishes 87 columns across its records 10. Cisco describes the correlation identifier within these records as tying together multiple call legs of the same call session 8.

Reporting surfaces and delivery

Documentation describes 5 routes to call history: the downloadable report, an administrative page, a webhook, a reports interface it names without describing, and a device call log it counts access to without describing 12. The administrative detailed call history page is not the downloadable report's field set: it publishes a mandatory minimum of 14 columns and a separate list of 6 filters 2.

The detailed call records webhook article names 2 field names in the whole article and uses the words consult, transfer, and correlation 0 times 22. This webhook delivers on a 5-minute cadence over a window of 10 to 5 minutes, warns of duplicates, and offers 2 mutually exclusive feeds with 1 webhook per partner organisation 21. The webhook's access model attributes a record to a single owner in a fixed order, which makes the billing feed incomplete by design 3.

Identifiers and session continuity

• Correlation identifier: The correlation identifier is unchanged across all 4 call detail records of Cisco's blind transfer example 9. However, it breaks during parking: the correlation identifier takes 3 distinct values across the 4 call detail records of Cisco's call park example 7.
• Transfer related call identifier: This field points at the other leg's local call identifier and is populated on only 2 of the 4 call detail records in Cisco's blind transfer example 20.
• Interaction identifier: The interaction identifier is mutable during a call and may fail to propagate when an agent already holds several answered calls 15.

Feature tracking and call redirection

Webex Calling call records name every feature traced across the corpus: a queue type field, a recall type field naming a hunt group, an auto attendant key pressed field, a voicemail usage report with a mailbox entity field, and call park values in the related reason field 18. A recall type field specifically names a hunt group as the fallback recall destination 17. When handling lines, a device owner identifier field names the device owner when it differs from the line's actual user 11.

• Transfers: A consultative transfer is carried in the related reason field by its own value, while a blind transfer surfaces only as deflection, a value it shares with auto-attendant transfer and call centre exit 4. Unlike blind transfers, call park has its own values in the related reason field, where a blind transfer collapses into deflection 16.
• Consult legs: The consult merge status field distinguishes a value of No, meaning a consult leg that was never merged into the customer call, from a value of not applicable 6.
• Redirection chains: The redirecting number and redirecting party identifier give the last redirector and the original called party identifier gives the first; no field gives an intermediate one 19. Furthermore, the caller identifier number re-points at the redirected party on a redirected call, and the external caller identifier number is not set at all for redirected calls 5.

Hunt group documentation anomalies

In the field, 3 rows of the hunt group statistics table carry each other's descriptions in a cycle 14. In the field, both hunt group tables publish a formula referencing a total hold minutes field that does not occur anywhere in the document outside that formula 13.

See also

See also Webex Calling CDR schema and access. See also Webex Calling call park. See also What a consult produces in Webex Calling. See also What a transferred call leaves behind across Cisco products. See also What a Webex webhook guarantees. See also Webex Calling hunt groups. See also Webex Calling shared lines. See also Webex Calling voicemail.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Calling, verified as of 2026-09-15. The deployment model is not covered by any claim in this article.

What remains uncertain

What the detailed call records webhook payload contains beyond the 2 field names its article gives is not covered by any claim in this article. What else breaks the correlation identifier besides call park is not covered by any claim in this article. When the interaction identifier changes during a call is not covered by any claim in this article. Whether consult merge status appears on Webex Contact Center records too is not covered by any claim in this article. What the reports interface and device call log carry is not covered by any claim in this article. Which of the 3 cyclically mislabelled hunt group rows is correct is not covered by any claim in this article. The definition of the total hold minutes field used in a published formula is not covered by any claim in this article.

WarmTransfer. (2026, September 15). What the Webex Calling detailed call history records. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-cdr-reference

@misc{warmtransfer-webex-calling-cdr-reference,
  title  = {What the Webex Calling detailed call history records},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-cdr-reference},
  note   = {Verified 2026-09-15}
}