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

2026-09-15

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

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

Source notes citing this source

• Webex Calling detailed call history records carry a Correlation ID that ties together the multiple call legs of one call session. in context
• The Webex Calling detailed call history Direction field uses ORIGINATING for outbound and TERMINATING for inbound. in context
• The Webex Calling detailed call history Duration field is the length of the call in seconds. in context
• The Webex Calling detailed call history Original reason field records why a call was redirected, with values including Unconditional, NoAnswer, Deflection, TimeOfDay, UserBusy, FollowMe, CallQueue and HuntGroup. in context
• In Webex Calling detailed call history, Calling number and Called number are defined relative to the user on the leg: on an outgoing call the calling number is the user's number, and on an incoming call the called number is the user's number. in context
• Webex Calling detailed call history produces one record per call leg, so a single call session can yield several records. in context
• The help article gives Webex Calling detailed call history report access of 400 days with Pro Pack and 89 days without it, and at most 31 days per report. in context
• In the Webex Calling detailed call history report, Start time and Answer time are given in UTC, and the answer time may be slightly after the start time. in context
• A call leg appears in the Calling Media Quality Report only if it established a media connection for at least 10 seconds. in context
• The Calling Media Quality Report gives per-call-leg details, including jitter, packet loss, latency, codec and connection type, for call legs with an established Webex Calling or Call on Webex media session. in context
• The Calling Detailed Call History Report covers all calls made using Webex Calling, with fields such as start and answer time, duration, calling and called numbers, user, location, trunk, call direction, call type, client, device and redirection reason. in context
• Pro Pack users can access 400 days of past data for the Calling Detailed Call History Report, and standard users can access 89 days. in context
• The Analytics page and the Reports page state different next-day freshness times (metrics by 1:00 PM GMT versus about 8:00 UTC), so the same day's data can appear at different times on the two surfaces. inferred in context
• For Calling reports other than Detailed Call History, the latest available data is yesterday and the available range is 13 months from the current date. in context
• The Calling Connectivity report shows Webex Calling connectivity status for the organization's users across endpoints. in context
• Control Hub reports can be generated immediately or scheduled to run daily, weekly or monthly, and are produced as ZIP or CSV files. in context
• A single Control Hub report download may cover at most 31 days under a standard license and at most 92 days under Pro Pack. in context
• The Telephone Number report gives a consolidated view of the organization's entire current inventory of Webex Calling telephone numbers and extensions. in context
• Control Hub Calling report templates include the Calling Media Quality, Calling Detailed Call History, Call Queue Stats, Call Queue Agent Stats, Auto Attendant, Hunt Group Stats, Hunt Group Agent Stats, Calling Connectivity, Telephone Number, AI Receptionist, Business Texting Usage Details and Voicemail Usage Stats reports. in context
• Report data capture is based on UTC, and the previous day's data takes about eight hours to appear, around 8:00 UTC. in context
• Generating Control Hub reports through the API requires Pro Pack. in context
• The Calling Engagement and Calling Quality reports were retired on April 28, 2026, and the Calling Media Quality report is the stated replacement for similar data. in context
• Control Hub offers Auto-attendant stats summary, business hours key details and after-hours key details report templates under Monitoring > Reports, and the key details reports show the key pressed and its destination. in context
• In the auto attendant reports, calls transferred to call services are counted as answered. in context
• The Call Queue Stats report counts size-based overflow ('Calls Overflowed', queue limit met) separately from wait-based overflow ('Calls Timed Out', wait time exceeded). in context
• The Call Queue agent stats report gives per-agent Total Presented Calls, Total Answered Calls and Bounced Calls (presented but not answered). in context
• Call queue reports list their latest available data as 'Today', unlike most other Control Hub reports, which list 'Yesterday'. in context
• The Webex Calling Detailed Call History report's Call type field includes SIP_NATIONAL, SIP_INTERNATIONAL, SIP_TOLLFREE and SIP_PREMIUM values for outgoing calls. in context
• The report's International country field gives the country of the dialed number and appears only for international calls. in context
• Pro Pack customers can report on 400 days of detailed call history and Standard customers on 89 days, with at most 31 days per report run. in context
• 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. 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. 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. 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. 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. 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. in context
• The correlation identifier takes 3 distinct values across the 4 call detail records of Cisco's call park example. in context
• Cisco describes the correlation identifier as tying together multiple call legs of the same call session. in context
• The correlation identifier is unchanged across all 4 call detail records of Cisco's blind transfer example. in context
• The Webex Calling detailed call history table publishes 87 columns. in context
• A device owner identifier field names the device owner when it differs from the line's actual user. 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. 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 report in context
• Three rows of the hunt group statistics table carry each other's descriptions in a cycle. field report in context
• The interaction identifier is mutable during a call and may fail to propagate when an agent already holds several answered calls. in context
• Cisco describes the interaction identifier shared across products as a service-interaction correlation mechanism and not a universal call-chain identifier. in context
• Call park has its own values in the related reason field, where a blind transfer collapses into deflection. in context
• A recall type field names a hunt group as the fallback recall destination. 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. 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. 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. in context
• 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 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. 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. 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. in context

Cite this source record

APA

WarmTransfer. (2026, September 15). 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-16}
}