Reports for Your Cloud Collaboration Portfolio

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/nmug598/Reports-for-Your-Cloud-Collaboration-Portfolio

Published

unknown

Updated

unknown

Accessed

2026-09-05

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• 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. fact in context
• 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. fact in context
• 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. fact in context
• The reporting table with a conference time column and no consult column is the Customer Assist Queue Call Details report of 41 columns; the Webex Calling Call Queue Stats report has 24 columns and no conference column at all. fact in context
• 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. fact in context
• Webex Calling call detail records carry a field named WxCC consult merge status, which specifies whether Webex Contact Center performed a transfer or conference on a consultative call; a value of No means the leg was started as an agent's consult and was never merged into the customer call. fact in context
• The correlation identifier takes 3 distinct values across the 4 call detail records of Cisco's call park example. fact in context
• Cisco describes the correlation identifier as tying together multiple call legs of the same call session. fact in context
• The correlation identifier is unchanged across all 4 call detail records of Cisco's blind transfer example. fact in context
• The Webex Calling detailed call history table publishes 87 columns. fact in context
• A device owner identifier field names the device owner when it differs from the line's actual user. fact in context
• 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. fact in context
• 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-pattern in context
• Three rows of the hunt group statistics table carry each other's descriptions in a cycle. field-pattern in context
• The interaction identifier is mutable during a call and may fail to propagate when an agent already holds several answered calls. fact in context
• Cisco describes the interaction identifier shared across products as a service-interaction correlation mechanism and not a universal call-chain identifier. fact in context
• Call park has its own values in the related reason field, where a blind transfer collapses into deflection. fact in context
• A recall type field names a hunt group as the fallback recall destination. fact in context
• 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. fact in context
• 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. fact in context
• 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. fact in context
• A call handled by voicemail is recorded as answered in the detailed call history with the user type field set to voicemail retrieval. fact in context
• No held document states what happens when a consult leg reaches voicemail: the reports document never uses consult and voicemail in one sentence and neither voicemail article uses consult at all. fact in context
• 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. fact in context

Cite this source record

APA

WarmTransfer. (2026, September 5). Reports for Your Cloud Collaboration Portfolio. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-nmug598-cloud-collaboration-reports

BibTeX

@misc{warmtransfer-cisco-help-nmug598-cloud-collaboration-reports,
  title  = {Reports for Your Cloud Collaboration Portfolio},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-nmug598-cloud-collaboration-reports},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-05}
}