WarmTransfer
cdr analytics · published

What the Webex Calling detailed call history records

Verified 2026-09-16 · 48 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 10. Cisco describes the correlation identifier as tying together multiple call legs of the same call session 8.

Call history surfaces and field sets

The 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. In the field, the Control Hub Calling Detailed Call History Report publishes a Transfer type context column whose description explains that it provides additional context for the transfer type, while the report publishes no Transfer type column 37.

Session identifiers and transfer tracking

The correlation identifier is unchanged across all 4 call detail records of Cisco's blind transfer example 9. In contrast, the correlation identifier takes 3 distinct values across the 4 call detail records of Cisco's call park example 7. The transfer related call identifier 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. Additionally, the interaction identifier is mutable during a call and may fail to propagate when an agent already holds several answered calls 15.

A consultative transfer is carried in the related reason field by its own value, whereas a blind transfer surfaces only as deflection, a value it shares with auto-attendant transfer and call centre exit 4. Call park has its own values in the related reason field, where a blind transfer collapses into deflection 16. For consults, 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 and feature representations

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. On a redirected call, the caller identifier number re-points at the redirected party, and the external caller identifier number is not set at all for redirected calls 5.

The Webex Calling call records name every feature the corpus has traced a call into: 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 names a hunt group as the fallback recall destination 17. A device owner identifier field names the device owner when it differs from the line's actual user 11.

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.

Webhook delivery mechanisms

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. The 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.

See also

See also Records and fields that represent a consult or a transfer. See also What a Webex webhook guarantees. See also What a transferred call leaves behind across Cisco products. See also What a consult produces in Webex Calling. See also Webex Calling call park. See also Webex Calling hunt groups. See also Webex Calling shared lines. See also Webex Calling voicemail. See also CUCM CDR and CMR field reference. See also The Webex Calling Detailed Call History API. See also Webex Calling call quality troubleshooting in Control Hub. See also Webex Contact Center Analyzer and reporting model. See also Teams call quality dashboard and analytics. See also Cross-platform CDR normalization model. See also Contact center KPI definitions and calculation. See also Call quality metrics and MOS estimation. See also SIP trace capture and ladder analysis. See also Carrier escalation evidence packages. See also UC observability and synthetic monitoring.

Applicability

Applies to: Cisco Webex Calling. Sources checked 2026-09-15.

What remains uncertain

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

See also

Documents models for

Part of

Related to

Referenced by

Sources

  1. 1
    The auto attendant article does not mention call recording, a call detail record or reporting.
    Manage auto attendants · Manage auto attendants, counted against the rendered article · Checked 2026-09-05
  2. 2
    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.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, detailed call history page and its template customisation · Checked 2026-09-15
  3. 3
    The webhook's access model attributes a record to a single owner in a fixed order, which makes the billing feed incomplete by design.
    Detailed call records webhook for Webex Calling in Partner Hub · Detailed call records webhook, access model · Checked 2026-09-05
  4. 4
    A consultative transfer is carried in the related reason field by its own value, and a blind transfer surfaces only as deflection, a value it shares with auto-attendant transfer and call centre exit.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, related reason · Checked 2026-09-05
  5. 5
    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.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, caller identifier fields · Checked 2026-09-05
  6. 6
    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.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, consult merge status · Checked 2026-09-05
  7. 7
    The correlation identifier takes 3 distinct values across the 4 call detail records of Cisco's call park example.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, call park worked example · Checked 2026-09-05
  8. 8
    Cisco describes the correlation identifier as tying together multiple call legs of the same call session.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, correlation identifier · Checked 2026-09-05
  9. 9
    The correlation identifier is unchanged across all 4 call detail records of Cisco's blind transfer example.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, blind transfer worked example · Checked 2026-09-05
  10. 10
    The Webex Calling detailed call history table publishes 87 columns.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference · Checked 2026-09-05
  11. 11
    A device owner identifier field names the device owner when it differs from the line's actual user.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, device owner identifier field · Checked 2026-09-15
  12. 12
    The document 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.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, whole document · Checked 2026-09-15
  13. 13
    Both hunt group tables publish a formula referencing a total hold minutes field that does not occur anywhere in the document outside that formula.field report
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, hunt group statistics tables · Checked 2026-09-15
  14. 14
    Three rows of the hunt group statistics table carry each other's descriptions in a cycle.field report
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, hunt group statistics table · Checked 2026-09-15
  15. 15
    The interaction identifier is mutable during a call and may fail to propagate when an agent already holds several answered calls.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, interaction identifier · Checked 2026-09-05
  16. 16
    Call park has its own values in the related reason field, where a blind transfer collapses into deflection.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, related reason values · Checked 2026-09-15
  17. 17
    A recall type field names a hunt group as the fallback recall destination.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, recall type field · Checked 2026-09-15
  18. 18
    The Webex Calling call records name every feature the corpus has traced a call into: 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.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, detailed call history field reference and the voicemail usage report · Checked 2026-09-15
  19. 19
    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.
    Reports for Your Cloud Collaboration Portfolio · Detailed call history field reference, redirection fields · Checked 2026-09-05
  20. 21
    The 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.
    Detailed call records webhook for Webex Calling in Partner Hub · Detailed call records webhook, delivery behaviour · Checked 2026-09-05
  21. 22
    The detailed call records webhook article names 2 field names in the whole article and uses the words consult, transfer and correlation zero times.
    Detailed call records webhook for Webex Calling in Partner Hub · Whole article, counted against the rendered text · Checked 2026-09-05
  22. 23
    Detailed Call History Answer reason displays Auto Answer when the Auto-Answer feature handled the call and N/A for a manually answered call, so the field distinguishes only 1 named answering mechanism from everything else.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Answer reason description · Checked 2026-09-15
  23. 24
    The Detailed Call History API returns 86 fields while the Control Hub Calling Detailed Call History Report publishes 87 columns, and the difference is 3 names: External customer ID and AI Agent ID appear only in the report, and Transfer type appears only in the API.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema property names, compared against the 87-row Calling Detailed Call History Report column table on cisco-help-nmug598-cloud-collaboration-reports · Checked 2026-09-15
  24. 25
    Both Detailed Call History endpoints return 86 fields per record, and the 2 field sets are identical in membership and in order.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 application/json schema, items.items.properties, compared property by property against the same path on cisco-dev-cdr-stream-detailed-call-history · Checked 2026-09-15
  25. 26
    Detailed Call History Call outcome reason documents 26 values under the 3 outcomes on the cdr_feed endpoint: 3 under Success, 15 under Refusal and 8 under Failure.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Call outcome reason description, counted over the 3 grouped value lists · Checked 2026-09-15
  26. 27
    Detailed Call History Call outcome carries 3 values, and Success is defined as a call routed and disconnected successfully including the Normal, UserBusy and NoAnswer scenarios, so a busy or unanswered call is recorded as a successful outcome; Failure means an internal or external error and Refusal means the call was rejected because of call block or timeout.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Call outcome description · Checked 2026-09-15
  27. 28
    The Detailed Call History Direction field is described as recording whether the call was inbound or outbound, and the 2 values it publishes are ORIGINATING and TERMINATING.field report
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Direction description · Checked 2026-09-15
  28. 29
    The Detailed Call History API documentation directs a reader to the Control Hub report article for the fields it returns and their possible values, and that article does not publish 1 of the API's fields, Transfer type.inferred
    Reports: Detailed Call History — Get Detailed Call History · meta.info.description, field reference sentence, read against the Calling Detailed Call History Report column table on cisco-help-nmug598-cloud-collaboration-reports · Checked 2026-09-15
  29. 30
    A Detailed Call History record carries 4 session UUIDs, Local SessionID, Remote SessionID, Final local SessionID and Final remote SessionID, described as usable for end-to-end tracking of a SIP session in compliance with RFC 7206 and draft-ietf-insipid-session-id-15; the Local value is generated by the originating user agent, the Remote value by the terminating user agent, and the 2 Final values are those values as they stood at the end of the call.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, the identical description shared by Local SessionID, Remote SessionID, Final local SessionID and Final remote SessionID · Checked 2026-09-15
  30. 31
    Detailed Call History Interaction ID ties together multiple call patterns linked by a service interaction, and Cisco's worked example is a consult and transfer: when a user holds an active call, places another call from the same app or device and then transfers the original call, both calls share the same Interaction ID.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Interaction ID description · Checked 2026-09-15
  31. 32
    Detailed Call History Local call ID is used with 2 other fields for 2 different purposes: with Remote call ID it identifies the remote record of the same call leg, and with Transfer related call ID it identifies the transferred leg.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Local call ID description · Checked 2026-09-15
  32. 33
    Detailed Call History Network call ID shows whether 2 records belong to the same call leg: 2 records belong to the same leg if and only if they carry the same Network call ID, and Report ID is described as a unique identifier for the individual record that can be used to deduplicate while processing.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Network call ID and Report ID descriptions · Checked 2026-09-15
  33. 34
    Detailed Call History Redirect reason and Original reason publish the same 13 values, Redirect reason carrying the reason for the redirecting number and Original reason the reason for the original called number, and their value descriptions differ in 4 places, of which only 1 is substantive: Original reason adds Group night forwarding to the Unconditional value and Redirect reason does not.
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema, Redirect reason and Original reason descriptions compared line by line · Checked 2026-09-15
  34. 37
    The Control Hub Calling Detailed Call History Report publishes a Transfer type context column whose description explains that it provides additional context for the transfer type, while the report publishes no Transfer type column.field report
    Reports for Your Cloud Collaboration Portfolio · Report templates tab, Webex Calling reports, Calling Detailed Call History Report column table, Transfer type context row · Checked 2026-09-15
  35. 38
    Exactly 1 field description differs between the 2 Detailed Call History endpoints: the stream endpoint lists RouteListCalls as a Failure value of Call outcome reason, describing an off-net route list call blocked for exceeding the organisation's Route List Calls licence overage limit, and the feed endpoint does not list it.
    Reports: Live Stream Detailed Call History — Get Live Stream Detailed Call History · spec.responses.200 schema, Call outcome reason description, Failure list, compared against the same field on cisco-dev-cdr-feed-detailed-call-history · Checked 2026-09-15
  36. 39
    6 Detailed Call History field names are spelled differently by the API and by the Control Hub report while naming the same field: Client version against Client Version, Device MAC against Device Mac, Call transfer Time against Call transfer time, Final local SessionID against Final Local Session ID, Final remote SessionID against Final Remote Session ID, and PSTN Vendor Name against PSTN vendor name.field report
    Reports: Detailed Call History — Get Detailed Call History · spec.responses.200 schema property names against the Calling Detailed Call History Report column table on cisco-help-nmug598-cloud-collaboration-reports, the API spelling given first in each pair · Checked 2026-09-15
  37. 40
    The Webex Calling reconciliation and records APIs make call records available for 30 days and enforce that window in their own parameters: startTime must not be older than 30 days from the current UTC time and endTime must be at least 5 minutes before the current UTC time and no older than 30 days.
    Detailed call records webhook for Webex Calling in Partner Hub · Data reconciliation, Reconciliation API and Records API parameter lists · Checked 2026-09-16
  38. 41
    The 30-day availability figure belongs to the reconciliation and records interfaces, which exist to catch up on records a webhook listener may not have received, and no article gives the webhook itself a retention window.
    Detailed call records webhook for Webex Calling in Partner Hub · Detailed call records webhook, Partner API endpoints and API Parameters · Checked 2026-09-05
  39. 42
    Neither hunt group article mentions call recording, and neither says anything about what a hunt group leaves in a call detail record or a report.
    Manage hunt groups in Control Hub · Both hunt group articles, counted against the rendered article · Checked 2026-09-05
  40. 43
    Neither call park article mentions call detail records, reporting, call history or a correlation identifier; those terms occur 0 times in both.
    Manage call park in Control Hub · Manage call park in Control Hub and Park and unpark calls, counted against the rendered article · Checked 2026-09-05
  41. 44
    The shared line article does not mention call detail records, call history or logs.
    Work with a shared line on your phone · Work with a shared line on your phone, counted against the rendered article · Checked 2026-09-05
  42. 46
    A call handled by voicemail is recorded as answered in the detailed call history with the user type field set to voicemail retrieval.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, detailed call history, Answered and User type fields · Checked 2026-09-15
  43. 47
    None of the 3 voicemail articles mentions a call detail record, reporting or call history.
    Configure and manage voicemail settings for a Webex Calling user · The user voicemail, shared voicemail and voice portal articles, counted against the rendered article · Checked 2026-09-05
  44. 48
    The voicemail usage report publishes 31 fields describing the state of a mailbox rather than events and Cisco states it is intended for operational monitoring and troubleshooting and not for billing.
    Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, Voicemail Usage Stats report · Checked 2026-09-15

Documents

tier 2 current vendor documentation

Cisco Webex Contact Center Analyzer User Guide

Cisco Systems, Inc. (Webex Help Center) · 2026-09-02 · accessed 2026-09-16

tier 2 current vendor documentation

Configure and manage voicemail settings for a Webex Calling user

Cisco Systems, Inc. (Webex Help Center) · 2026-05-28 · accessed 2026-09-16

tier 2 current vendor documentation

Detailed call records webhook for Webex Calling in Partner Hub

Cisco Systems, Inc. (Webex Help Center) · 2026-08-13 · accessed 2026-09-16

tier 2 current vendor documentation

Manage auto attendants

Cisco Systems, Inc. (Webex Help Center) · 2025-12-12 · accessed 2026-09-16

tier 2 current vendor documentation

Manage call park in Control Hub

Cisco Systems, Inc. (Webex Help Center) · 2026-07-23 · accessed 2026-09-16

tier 2 current vendor documentation

Manage hunt groups in Control Hub

Cisco Systems, Inc. (Webex Help Center) · 2026-07-23 · accessed 2026-09-16

tier 2 current vendor documentation

Reports for Your Cloud Collaboration Portfolio

Cisco Systems, Inc. (Webex Help Center) · 2026-09-15 · accessed 2026-09-16

tier 2 current vendor documentation

Reports: Detailed Call History — Get Detailed Call History

Cisco Systems, Inc. (developer.webex.com) · accessed 2026-09-16

tier 2 current vendor documentation

Reports: Live Stream Detailed Call History — Get Live Stream Detailed Call History

Cisco Systems, Inc. (developer.webex.com) · accessed 2026-09-16

tier 2 current vendor documentation

Work with a shared line on your phone

Cisco Systems, Inc. (Webex Help Center) · 2026-03-11 · accessed 2026-09-16

Cite this page

APA

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

BibTeX

@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-16}
}