Reports help you track and analyze the performance of Webex services in your organization. You can use these reports to see details for each meeting, how often users are messaging each other, details for Webex Calling calls and call queues, how often Cisco devices are used, onboarding information, and more.
Reports, along with Analytics and Troubleshooting, is one part under the Monitoring section available in Control Hub that you can use to help track usage or solve issues with Webex services in your organization.
You can choose to generate a CSV-formatted report immediately or to schedule reports to run automatically in a daily, weekly, or monthly format. When you download a report, the report uses the following naming format for the file:
- Default report template—
Default Template Name_alphanumeric characters_Download Date
- Custom report template—
Custom Template Name_alphanumeric characters_Download Date
To generate these reports with an API, see the Reports API or Report Templates API developer page. You must have Pro Pack in order to generate reports with an API.
UI tooltips are shown for features that are only available with
Pro Pack. |
The table below shows you what types of reports are are available for Control Hub, the earliest date range that you can view the data for each report, and the maximum date range that you can select for each report that you run.
Report |
Standard License |
Pro Pack License |
Latest Data Available to Generate on Current Date |
Available Data Date Range |
Standard—Date Range Limit Per Download |
Pro Pack—Date Range Limit Per Download |
---|---|---|---|---|---|---|
Onboarding User Activation and License Details Report |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings Embedded Apps Report |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings In-Meeting Feature Usage Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Meetings Usage Summary Report |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings High CPU Report |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings Active Hosts Report |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings Inactive Users Report |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings Active User Rolling Average Report** |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Enterprise Agreement Report** |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Meetings Details Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Meetings Attendees Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Meetings Audio Usage Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Meetings Telephony Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Meetings License Consumption Report** |
✔ | Yesterday |
NA |
|
NA | |
Webinar Report* |
✔ |
✔ | Yesterday |
May 1, 2021 |
3 months |
13 months |
Messaging External Domain Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Messaging Bots Activity Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Messaging User Activity Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Messaging Bots Activity Summary Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Messaging User Activity Summary Report |
✔ | Yesterday |
13 months from current date |
|
31 days | |
Messaging App Version Report |
✔ | Yesterday |
13 months from current date |
|
NA | |
Meetings Future Schedules Report |
✔ | NA (future 90 days) |
NA |
|
90 days | |
Calling Media Quality Report |
✔ |
✔ | Yesterday |
13 months from current date |
31 days |
31 days |
Calling Engagement Report |
✔ |
✔ | Yesterday |
13 months from current date |
31 days |
31 days |
Calling Quality Report |
✔ |
✔ | Yesterday |
13 months from current date |
31 days |
31 days |
Calling Detailed Call History |
✔ |
✔ | Yesterday |
13 months from current date Data available from April 12, 2022 |
31 days |
31 days |
Calling Detailed Call History Report |
✔ |
✔ | Yesterday |
13 months from current date |
31 days |
31 days |
Call Queue Stats Report |
✔ |
✔ | Today |
13 months from current date |
3 months |
13 months |
Call Queue Agent Stats Report |
✔ |
✔ | Today |
13 months from current date |
3 months |
13 months |
Auto Attendant Reports - Stats Summary, Business Hours Key Details, After-Hours Key Details |
✔ |
✔ | Today |
13 months from current date Data available from July 29, 2022 |
3 months |
13 months |
Rooms and Desks Detail Report* |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
VIMT License Report* |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
VIMT Usage Report* |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
Devices Power Consumption Report* |
✔ |
✔ | Yesterday |
13 months from current date |
3 months |
13 months |
* These reports aren't available in Webex for Government organizations. ** These reports are only available for subscriptions that bill based on the number of license usage. |
Report list
This tab shows a list of reports that are ready for you to download. If you choose to subscribe to a report when scheduling one, then you'll also get an email that notifies you when the report is ready for you to download.
When the report is generating, the status column changes to “In Progress”. When the report is ready to download, the status column changes to “Complete”. Your report may take up to 24 hours to generate, depending on the size of the report and how many reports are queued. Generated reports will show up in the Report list tab.
You can only have a maximum of 50 reports in this list. Once you reach that limit, delete some reports to generate new reports again. |
Scheduled reports
This tab shows a list of reports that are set up to run recurringly. You can see the recurring details for each report and when they were last generated.
This tab shows a list of fixed templates that you can use to schedule reports, along with a brief description for each report.
These reports are for your general use and shouldn't be used for billing purposes. |
To view more information about these reports, you can expand the following sections:
Data availability
Data is captured based on the UTC time zone. It takes approximately eight hours for the last-day data to show up for the following day, which is around 8:00 UTC. Different time zones may affect when certain reports are updated with new data.
For example, if you generate a report for the same day, the report may only include partial data. If you include the previous day and the same day in the time range, then the report may also include partial data, depending on your time zone.
We recommend that you generate same-day reports in your time zone's afternoon and include the previous day along with the same day if you find that your reports don't have all of the previous day's data.
Meetings Embedded Apps
Provides details about the different types of Webex embedded apps that a participant uses in a meeting
Column Name |
Description |
---|---|
Conference_ID |
Unique ID of the meeting. |
Meeting_Name |
Subject of the meeting. |
Meeting_Type |
Type of meeting that took place. The possible values are:
|
|
Email address of the participant who attended the meeting. |
User_Name |
Name of the participant who attended the meeting. |
App_Name |
Name of the embedded app used by the participant in the meeting. |
Date |
Date on when the embedded app was used by the participant in the meeting. |
Meetings In-Meeting Feature Usage
Provides details about what collaboration features were used by which user during meetings in your organization.
We recommend that users are on the latest Webex Meetings client (WBS 42.7 or above) or at least the latest lockdown version (WBS 42.6) to accurately capture data for this report. Some data may not be captured if users are on an older client version. |
Known limitations
Data isn't captured for a user if:
- The user joined with a device that doesn't support in-meeting features.
- The user didn't leave the meeting normally, such as dropping out of the meeting due to a lost network connection or their app crashed.
Column Name |
Description | ||
---|---|---|---|
MEETING_NUMBER |
The 9-digit meeting access code used to join the meeting. | ||
MEETING_NAME |
The subject of the meeting. | ||
CONFID |
The unique ID of the meeting. | ||
USER_NAME |
The name of the user who attended the meeting. | ||
|
The email address of the user who attended the meeting. | ||
JOIN_DATE |
The date of the meeting (GMT). | ||
START_TIME |
When the meeting started (GMT). | ||
END_TIME |
When the meeting ended (GMT). | ||
NETWORK_BASED_RECORDING |
The user recorded the meeting in the cloud. | ||
APPLICATION_SHARING |
The user shared an application while sharing their screen. | ||
DOCUMENT_SHARING |
The user shared a document while sharing their screen. | ||
CHAT |
The user opened the chat panel and sent a message. | ||
QUESTION_ANSWER |
The user accessed or utilized a question and answer session. | ||
CLOSED_CAPTION |
The user turned on automated closed captions. | ||
WHITEBOARD |
The user shared a whiteboard. | ||
DESKTOP_SHARING |
The user shared their desktop. | ||
WEB_BROWSING_SHARING |
The user shared their screen when they joined the meeting through a browser. | ||
VIDEO_SETTINGS |
The user turned on their video. | ||
APPLICATION_REMOTE_CONTROL |
The user remotely controlled another participant's shared application during the meeting. | ||
WEB_BROWSER_SHARING_REMOTE_CONTROL |
The user remotely controlled another participant's shared web browser during the meeting. | ||
ANNOTATION | |||
FILE_TRANSFER |
The user transferred a file during the meeting. | ||
DESKTOP_REMOTE_CONTROL |
The user remotely controlled another participant's shared desktop during the meeting. | ||
APPLICATION_REMOTE_CONTROL |
The user remotely controlled another participant's shared desktop during the meeting. | ||
WEB_BROWSER_SHARING_REMOTE_CONTROL |
The user remotely controlled another participant's shared web browser during the meeting. | ||
BREAKOUT_SESSION |
The user started or joined a breakout session.
| ||
SIMULTANEOUS_TRANSLATIONS |
The user enabled the simultaneous translation feature. | ||
REACTIONS |
The user selected a reaction during the meeting. | ||
RAISED_HAND |
The user selected the raise hand feature during the meeting. | ||
MOVE_MEETING_TO_MOBILE |
The user moved their meeting to a mobile device during the meeting. | ||
VIRTUAL_BACKGROUND |
The user enabled a virtual background during the meeting. | ||
REAL_TIME_TRANSLATION |
The user enabled the real time translation feature during the meeting. | ||
WEBEX_ASSISTANT |
The user enabled Webex Assistant during the meeting. | ||
Meetings Details
Provides details about meetings that were started within the selected date range. You can see who hosted the meeting, when the meeting started and ended, how many participants attended the meeting, if the meeting was recorded, and more.
Column Name |
Description | ||
---|---|---|---|
MEETING_NUMBER |
The 9-digit meeting access code used to join the meeting. | ||
MEETING_NAME |
The subject of the meeting. | ||
CONFERENCE_ID |
The unique ID of the meeting. | ||
MEETING_TYPE |
The type of meeting that took place. The possible values are:
| ||
HOST_NAME |
The name of the user who created or scheduled the meeting. | ||
HOST_USERID |
The unique ID of the host. | ||
HOSTEMAIL |
The email address of the host. | ||
START_TIME |
When the meeting started (GMT). | ||
END_TIME |
When the meeting ended (GMT). | ||
DURATION |
The length of the meeting in minutes. | ||
TOTAL_ATTENDEE |
The number of participants in the meeting. | ||
PEOPLE_MINS |
The total number in minutes that all participants have been in the meeting. For example, if a meeting had 3 participants and they each joined for 10 minutes, then the total equals to 3 participants x 10 minutes each = 30 minutes. | ||
IS_VOIP |
At least one participant called into the meeting using audio connection through a computer. | ||
IS_SHARING |
At least one participant shared their screen in the meeting. | ||
IS_RECORD |
If the meeting was recorded or not. | ||
VIDEO_USERS |
The number of participants who joined with a Webex Meetings client and turned on their video during the meeting. | ||
VIDEO_MINS |
The total number in minutes that participants were sending video. | ||
AUDIO_ONLY (PCN) |
A meeting where all participants called in using PSTN. | ||
TRACKING_CODE_1-10 |
The tracking code associated with a user.
| ||
INTEGRATION_USED |
This field shows if a meeting was scheduled through the Microsoft Teams, Microsoft Outlook, Slack, or Google Calendar integration with the Cisco Webex Meetings app. | ||
WEBEX_ASSISTANT |
This field shows if the Webex Assistant for Meetings was used in the meeting. The possible values are:
| ||
BREAKOUT_USED |
This field shows if a breakout session was started during the meeting. The possible values are:
| ||
IS_E2EE |
This field shows if the meeting was scheduled using end-to-end encryption (E2EE). The possible values are:
| ||
SI_USED |
This field shows if a meeting had simultaneous interpretation enabled by the host. The possible values are:
| ||
Meetings Attendees
Provides details about every participant who attended a meeting within the selected date range. You can find out about a participant’s media quality data during the meeting and information about how they joined the meeting.
Media quality data and hardware information of participants are only available if the meeting's duration was more than two minutes. |
Column Name |
Description | ||
---|---|---|---|
MEETING_NUMBER |
The 9-digit meeting access code used to join the meeting. | ||
MEETING_NAME |
The subject of the meeting. | ||
CONFERENCE_ID |
The unique ID of the meeting. | ||
USER_NAME |
The names of the participants who attended the meeting. | ||
|
The email addresses of the participants who attended the meeting. | ||
LOCATION |
The country of where the participants joined the meeting from. | ||
JOIN_DATE |
The date of the meeting (GMT). | ||
START_TIME |
The times that the participants joined the meeting (GMT). | ||
END_TIME |
The times that the participants left the meeting (GMT). | ||
DURATION |
How long the participant joined the meeting for in minutes. | ||
OS |
The operating systems of the devices the participants used to join the meeting. | ||
BROWSER |
The web browsers that participants used for the Webex Meetings for Web to join the meeting. | ||
LOCAL_IP |
The IP addresses of the clients used to join the meeting. These IP addresses may not be externally routable addresses if they're behind a firewall. | ||
PUBLIC_IP |
The IP addresses of the client that's externally routable. This can be the same as | ||
VOIP_RECEIVING_AVERAGE_PACKET_LOSS |
The average audio packet loss for the duration of the meeting from the Webex cloud to the client direction, in percentage.
| ||
VOIP_AVERAGE_LATENCY |
The average audio latency for the duration of the meeting, in milliseconds. | ||
JOIN_MEETING_TIME |
JMT = (the time from clicking the meeting link to loading the preview window) + (the time from clicking the Join button in the preview window to connecting into the meeting). JMT doesn’t count the time the user spends browsing menus, making selections in the preview window, or waiting in the lobby. | ||
TCP_PERCENTAGE |
The percentage of the duration participants used TCP connection for a VoIP call. | ||
UDP_PERCENTAGE |
The percentage of the duration participants used UDP connection for a VoIP call. | ||
IS_CMR |
If the attendee joined the meeting using a Webex Room or Desk Device, | ||
IS_SHARING |
Whether or not the participant shared their screen during the meeting. | ||
IS_RECORD |
Whether or not the participant clicked the Record button. | ||
VIDEO_MINUTES |
The total number of minutes that video was enabled by the participant in the meeting. | ||
CLIENT |
The type of soft client used to join the meeting. | ||
CLIENT_VERSION |
The version of the soft client used to join the meeting. | ||
MEDIA_NODE |
The data center or region of the media node that the client connected to. For cloud-based media nodes, this is a general region name such as "San Jose, USA". For video mesh based media nodes, this will have a more specific name that matches the video mesh cluster name that was provisioned by the customer. | ||
CONNECTION |
The type of network connection that the client used to exchange media. Possible values could be "wifi", "ethernet", "cellular", or "unknown".
| ||
HARDWARE |
The hardware make and model of the device used to join a meeting. For computers this might be "Lenovo Thinkpad p60". For phones this might be "Samsung Galaxy S7". For room devices this might be "Cisco Webex Room Kit". | ||
CAMERA |
The brand name and model information for the camera that was used during the meeting.
| ||
MICROPHONE |
The brand name and model information for the microphone that was used during the meeting.
| ||
SPEAKER |
The brand name and model information for the speaker that was used during the meeting.
| ||
AUDIO_AVERAGE_LATENCY |
The average audio latency for the duration of the meeting, in milliseconds. | ||
AUDIO_MAX_LATENCY |
The highest value of audio latency for the duration of the meeting, in milliseconds. | ||
AUDIO_RECEIVING_AVERAGE_PACKET_LOSS |
The average end-to-end audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_RECEIVING_MAX_PACKET_LOSS |
The highest value of end-to-end audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_SENDING_AVERAGE_PACKET_LOSS |
The average audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_SENDING_MAX_PACKET_LOSS |
The highest value of audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_RECEIVING_AVERAGE_JITTER |
The average audio jitter for the duration of the meeting, in milliseconds. | ||
AUDIO_RECEIVING_MAX_JITTER |
The highest value of audio jitter for the duration of the meeting, in milliseconds. | ||
AUDIO_SENDING_AVERAGE_JITTER |
The average audio jitter for the duration of the meeting, in milliseconds. | ||
AUDIO_SENDING_MAX_JITTER |
The highest value of audio jitter for the duration of the meeting, in milliseconds. | ||
VIDEO_AVERAGE_LATENCY |
The average video latency for the duration of the meeting, in milliseconds. | ||
VIDEO_MAX_LATENCY |
The highest value of video latency for the duration of the meeting, in milliseconds. | ||
VIDEO_RECEIVING_AVERAGE_PACKET_LOSS |
The average video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_RECEIVING_MAX_PACKET_LOSS |
The highest value of video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_SENDING_AVERAGE_PACKET_LOSS |
The average video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_SENDING_MAX_PACKET_LOSS |
The highest value of video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_RECEIVING_AVERAGE_JITTER |
The average video jitter for the duration of the meeting, in milliseconds. | ||
VIDEO_RECEIVING_MAX_JITTER |
The highest value of video jitter for the duration of the meeting, in milliseconds. | ||
VIDEO_SENDING_AVERAGE_JITTER |
The average video jitter for the duration of the call, in milliseconds. | ||
VIDEO_SENDING_MAX_JITTER |
The highest value of video jitter for the duration of the meeting, in milliseconds. | ||
CPU_APPLICATION_AVERAGE |
The average CPU usage for the Webex app for the duration of the meeting, in percentage. | ||
CPU_APPLICATION_MAX |
The highest CPU usage value for the Webex app for the duration of the meeting, in percentage. | ||
CPU_SYSTEM_AVERAGE |
The average system CPU usage for the duration of the meeting, in percentage. | ||
CPU_SYSTEM_MAX |
The highest system CPU usage value for the duration of the meeting, in percentage. | ||
VIRTUAL_BACKGROUND_USED |
This field shows if participants enabled a virtual background during the meeting. The possible values are:
| ||
HOST_INDICATOR |
This field shows if the participant was a host or attendee. The possible values are:
| ||
IS_COHOST |
This field shows if the participant was a cohost for the meeting. The possible values are:
| ||
Client_Type |
Client that the participant used to join the meeting. | ||
Sub_Client_Type |
Method that the participant used to join the meeting. | ||
Client_Browser_Details |
App or browser that the participant used to join the meeting. | ||
VIDEO_QUALITY |
This field shows what the participant's video quality was during the meeting. Video quality is calculated as the participant's average value of video packet loss and latency from their total video minutes per meeting. Possible values are:
| ||
VOIP_QUALITY |
This field shows what the participant's VoIP quality was during the meeting. VoIP quality is calculated as the participant's average value of audio packet loss and latency from their total audio minutes per meeting. Possible values are:
| ||
Meetings Usage Summary
Provides details about the total number of meetings hosted within the selected date range.
Column Name |
Description |
---|---|
Number Of Meetings |
The total number of meetings hosted over the selected time period. |
Total Meeting Minutes |
The total number of minutes for all meetings over the selected time period. For example, if three meetings lasted 30 minutes each, then the count is 90 meeting minutes. |
Number Of Participants |
The total number of joins by participants or devices from all Webex meetings over the selected time period. For example, if a participant or device disconnected from a meeting and then rejoined, then the count is 2. |
Total Participant Minutes |
The total number of minutes that all participants were in a meeting for. For example, if a meeting has 3 participants and lasts for 10 minutes, then the count is 30 participant minutes (3 x 10 minutes). |
Participant Sending Video Minutes |
The total number of minutes that participants enabled video for. For example, in a meeting that lasts 30 minutes with five participants, but only two participants enabled video for the entire meeting, the count is 60 video minutes. |
Participant VOIP Minutes |
Total number of minutes for participants who joined meetings using VoIP. |
Participant Audio Minutes |
Total number of minutes for participants who called in to meetings using PSTN. |
Meetings Active Hosts
Provides details about how many meetings a host scheduled and started within the selected date range.
Column Name |
Description |
---|---|
UserID |
The host's email address. |
Count of meetings hosted |
The number of meetings scheduled and hosted by this user within the reported time period. |
Host |
The name of the user who hosted the meeting, or the name of the device if the meeting was hosted on a device. |
Meetings Inactive Users
Provides details about users who haven’t hosted or attended meetings within the selected date range.
Column Name |
Description |
---|---|
FIRST_NAME |
The first name of the user. |
LAST_NAME |
The last name of the user. |
USERNAME |
The email address of the user. |
USER_ID |
The unique ID of the user. |
|
The email address of the user. |
IS_HOST |
Whether or not the user has a Webex Meetings host license. |
IS_SITEADMIN |
Whether or not the user has an administrator role for the Webex site. |
DAYS_SINCE_LAST_ACTIVE |
The number of days since the user last hosted or attended a meeting through the Webex App app or Webex Meetings. |
LAST_ACTIVE_DATE |
The date of when the user last hosted or attended a meeting through the Webex App app or Webex Meetings. PSTN call-in users don’t count as active. |
Meetings Audio Usage
Provides details about the different types of audio that participants used during a meeting.
Column Name |
Description | ||
---|---|---|---|
CONF ID |
The unique ID of the meeting. | ||
MEETING NUMBER |
The 9-digit meeting access code used to join the meeting. | ||
AUDIO TYPE |
The audio type that participants used to join a meeting. The audio types are:
| ||
USER NAME |
The names of the participants who attended the meeting. | ||
|
The email addresses of the participants who attended the meeting. | ||
PHONE NUMBER |
The phone number for participants who joined a meeting through CCA, PSTN, VoIP, Edge Audio, or Fallback.
| ||
MEETING ENDDATE |
The date of when the meeting ended. | ||
START TIME |
When the meeting started (GMT). | ||
END TIME |
When the meeting ended (GMT). | ||
AUDIO MINUTES |
The total number of audio minutes used by each participant. | ||
MEETING NAME |
The subject of the meeting. | ||
Meetings Telephony Report
Provides details about the different types of audio that participants used during a meeting. You can use this chart to get a sense of which calling services that participants prefer to connect to for meetings and calls.
Column Name |
Description | ||
---|---|---|---|
MEETING_NUMBER |
9- or 10-digit meeting access code used to join the meeting. | ||
CONFERENCE_ID |
Unique ID of the meeting. | ||
SESSION_TYPE |
Audio type (in numerical value) that participants used to join a meeting. Possible audio types are:
| ||
COUNTRY_CODE | Alphabetic or numeric geographical code that the participants used to dial in to the meeting. | ||
MEETING_NAME |
Subject of the meeting. | ||
MEETING_START_DATE_TIME |
Date and time (in GMT) of when the meeting started. | ||
MEETING_END_DATE_TIME |
Date and time (in GMT) of when the meeting ended. | ||
MEETING_DURATION |
Duration (in GMT) of how long the meeting lasted. | ||
USER_NAME |
Display names of the participants who attended the meeting. | ||
|
Email addresses of the participants who attended the meeting. | ||
CALL_SERVICE_TYPE |
Call service type that participants used to join a meeting. Possible call service types are:
| ||
DIALED_IN_PHONE_NUMBER |
Phone number that participants used to dial in to the meeting. | ||
CALLBACK_PHONE_NUMBER |
Phone number that participants requested to join a meeting through callback. | ||
ANI | Automatic number identification of the phone number that the participant used to call in to the meeting. | ||
PARTICIPANT_START_DATE_TIME |
Date and time (in GMT) of when the participant connected their audio in the meeting. | ||
PARTICIPANTS_DURATION |
Duration (in GMT) of how long the participant's audio was connected for in the meeting. | ||
TRACKING_CODE_1-10 |
The tracking code associated with a user.
| ||
Meetings Future Schedules
This report doesn't have a date range selection. You can see the meetings that are coming up for a Webex site within the next 90 days from the date that you run the report. You can also see meetings that were scheduled within the previous 30 days.
This report shows you the upcoming meetings for the selected Webex site. Use this report to gain insights into how many users are scheduling meetings in a Webex site and understand the volume and timing of upcoming meetings. These details can help you manage the timing of a site migration or a site upgrade that might impact users. You can also identify critical meetings or events to help plan support accordingly.
Meetings scheduled from Webex are included in this report. If hosts are scheduling meetings with a Personal Room invitation URL, then those meetings won’t be included in the report. |
Column Name |
Description |
---|---|
MeetingNumber |
The 9-digit meeting access code used to join the meeting. |
ServiceType |
If the meeting was scheduled as a Webex Meeting, Webex Event, Webex Training session, or Webex Webinar (WB). |
HostName |
The name of the user who scheduled the meeting. |
|
The email address of the user who scheduled the meeting. |
MeetingName |
The subject of the meeting. |
StartTime |
The date and time of when the meeting will start (GMT). |
EndTime |
The date and time of when the meeting will end (GMT). |
CreatedOn |
The date and time of when the meeting was scheduled (GMT). |
InviteeCount |
The number of users invited to the meeting. |
PasswordSet |
If the meeting requires a password to join. |
SeriesType |
If the meeting is a one-time meeting or a recurring series. |
ExpirationDate |
The date and time of when the meeting series will end (GMT). |
LastModifiedDate |
The date and time of when the meeting invitation was last updated (GMT). |
ExceptionMeeting |
If one of the meetings in a series was rescheduled for a different time. |
Meetings High CPU
This report shows you which users had an average system CPU usage of 90% or higher for at least 25% of their video minutes during meetings. To optimize resources, Webex downgrades the bit rate and resolution of all videos when the user reaches an average system CPU usage of 95% for five consecutive seconds.
You can use this report to help users on how they can reduce their system CPU usage to have a better meeting experience.
Column Name |
Description |
---|---|
User Email |
The email address of the user who had high system CPU usage. |
Total Video Minutes |
The number of recorded video minutes for each user’s email address during the selected date range. |
Video Minutes with High CPU Utilization |
The number of recorded video minutes where the average system CPU usage was at 90% or higher. |
% Video Minutes with High CPU |
The percentage of video minutes where the average system CPU usage was at 90% or higher. |
Meetings Active User Rolling Average
Provides details about how many licenses are being used in a subscription, and how many users have hosted at least one Webex meeting within the reported date. This report is only available if your organization has an active true forward eligible subscription.
Column Name |
Description | ||
---|---|---|---|
Date |
The calendar date within the period.
| ||
Subscription ID |
The unique ID of the subscription. | ||
Product |
The name of the product for the reported licenses. | ||
Provisioned License Quantity |
The total number of licenses provisioned for the subscription and product. | ||
Allocated License Quantity |
The number of licenses allocated to users at the reported date. | ||
Unique Active Hosts Per Day |
The count of unique active hosts on the calendar date. Unique active hosts are hosts who started at least one Webex meeting on the reported date. | ||
Unique Active Meeting Hosts for Past 30 days |
The cumulative number of unique active hosts for the last 30 days, including the current day. Unique active hosts are hosts who started at least one Webex meeting on the reported date. | ||
90 Day Rolling Average Unique Active Meetings Hosts |
The average number of unique active hosts for the preceding 90 days of the reported date, rounded to the nearest whole number. If you have less than 90 days in your subscription, then the average is based on the number of days the subscription has been active for. | ||
Consumption Quantity |
This number reflects the aligned value used to identity a True Forward. IT admins can track this value throughout the contract term, well before the period in which the subscription is due for a potential change.
| ||
Meetings License Consumption Report
Provides details about how many licenses are being used in a subscription. This report is only available if your organization has an active utility-based billing subscription.
This report isn't available in Webex for Government organizations. |
Column Name |
Description |
---|---|
Date |
The period that the subscription is in. A period is defined as a 30-day cycle that starts on the day your subscription was activated, and corresponds with your billing cycle. For example, if your subscription started on July 5, 2020, then the next period would start 30 days later, on August 4, 2020. |
Subscription ID |
The unique ID of the subscription. |
Product |
The name of the product for the reported licenses. |
Provisioned License Quantity |
The total number of licenses provisioned for the subscription and product. |
Allocated License Quantity |
The number of licenses allocated to users at the reported date. |
Webinar Report
Provides information about Webex webinars that were hosted within the selected date range. You can use this report to find out who the host for an webinar was, what type of webinar was scheduled, and how many users registered or attended.
Column Name |
Description |
---|---|
Meeting ID |
The unique ID of the webinar. |
Host ID |
The unique ID of the host. |
Webinar Topic |
The subject of the webinar. |
Webinar Type |
If it was scheduled as a Webinar or Webcast. |
Host Email |
The email address of the host. |
Host First Name |
The first name of the host. |
Host Last Name |
The last name of the host. |
Event Date |
The date of when the webinar started. |
Start Time |
The time of when the webinar started (GMT). |
End Time |
The time of when the webinar ended (GMT). |
Duration |
The number of minutes that the webinar lasted for. |
Total Registrants |
The number of users that registered for the webinar before it started. |
Total Attendees |
The number of users that joined the webinar. |
Messaging External Domain
Provides information about external domains and external users collaborating in your organization. You can also see how users from your organization are collaborating with external domains in external spaces.
Column Name |
Description |
---|---|
External Domain |
Name of the external domain. |
Number of External Users |
Number of users from the external domain in your organization's spaces. |
Numbers of Spaces with External Users |
Number of spaces in your organization that has at least one user from the external domain. For example, if Bob@external.com is in 3 different spaces in your organization, then this column will show 3 as the value. |
Most Recent Read Message Date |
Last known date of when a user from the external domain read a message in a space in your organization. |
Most Recent Sent Message Date |
Last known date of when a user from the external domain sent a message in a space in your organization. |
Most Recent Shared File Date |
Last known date of when a user from the external domain shared a file in a space in your organization. |
Most Recent Joined Space Date |
Last known date of when a user from the external domain joined a space in your organization. |
Number of Users from Your Organization in External Spaces |
Number of users from your organization that are in external spaces. |
Number of External Spaces with Users from Your Organization |
Number of external spaces that users from your organization are in. For example, if Alice@example.com is in 3 different external spaces of the external domain, then this column will show 3 as the value. |
Messaging Bots Activity
This report shows data for every activity of each bot per day during the date range that you select. Each date that you select has their own set of data. For example, if you run a report for June 1, 2020 to June 5, 2020, then the report shows you every activity of the bot for each date of the report.
If a bot hasn't had any activity during a certain date, then those dates don't show up in the report.
Data for this report is only for bots from your organization. If your organization uses bots that aren't part of your organization, then data won't show for those bots. |
Column Name |
Description |
---|---|
Bot Name |
The name of the bot. |
Bot ID |
The unique ID of the bot. |
Date |
The date for the activity of the bot. |
Active Spaces Count |
The number of spaces that the bot has sent a message or shared a file in. |
Messages Count |
The number of messages sent by the bot. |
Files Shared |
The number of files shared by the bot. |
New Spaces Joined |
The number of spaces the bot joined. |
Spaces Exited |
The number of spaces the bot left. |
Bot User Count |
The number of unique users that mentioned the bot. |
Bot Mentions Count |
The number of how many times the bot was mentioned by users. |
Messaging User Activity
This report shows data for every activity of each user per day during the date range that you select. Each date that you select has their own set of data. For example, if you run a report for June 1, 2020 to June 5, 2020, then the report shows you every activity of the user for each date of the report.
If a user hasn't had any activity during a certain date, then those dates don't show up in the report.
Column Name |
Description |
---|---|
User ID |
The unique ID of the user. |
Name |
The first and last name of the user. |
|
The email address of the user. |
Date |
The date for the activity of the user. |
Messages Sent |
The number of messages sent by the user. |
Calls |
The number of calls made and meetings joined from the Webex App client by a user. |
Files Shared |
The number of files shared in all spaces by the user. |
Spaces Count |
The number of spaces that the user has sent a message, made a call, or shared a file in. |
New Spaces Created |
The number of spaces the user created. |
New Spaces Joined |
The number of spaces the user joined. |
Space Exited |
The number of spaces the user left. |
Messaging Bots Activity Summary
This report shows aggregated data for each activity of each bot during the date range that you select.
Data for this report is only for bots from your organization. If your organization uses bots that aren't part of your organization, then data won't show for those bots. |
Column Name |
Description |
---|---|
Bot Name |
The name of the bot. |
Bot ID |
The unique ID of the bot. |
Bot Owner |
The name of the user who created the bot. |
Bot Owner Email |
The email address of the user who created the bot. |
Start Date |
The first date selected for the report date range. |
End Date |
The last date selected for the report date range. |
Average Active Spaces Count |
The average number of spaces that the bot has sent a message or shared a file in. |
Messages Count |
The number of messages sent by the bot. |
Files Shared |
The number of files shared by the bot. |
Spaces Joined |
The number of spaces the bot joined. |
Spaces Exited |
The number of spaces the bot left. |
Average Bot User Count |
The average number of unique users that mentioned the bot. |
Bot Mentions Count |
The number of how many times the bot was mentioned by users. |
Messaging User Activity Summary
This report shows aggregated data for each activity of each user during the date range that you select.
Column Name |
Description |
---|---|
User ID |
The unique ID of the user. |
Name |
The first and last name of the user. |
|
The email address of the user. |
Start Date |
The first date selected for the report date range. |
End Date |
The last date selected for the report date range. |
Messages Sent |
The number of messages sent by the user. |
Calls |
The number of calls made and meetings joined from the Webex App client by a user. |
Files Shared |
The number of files shared in all spaces by the user. |
New Spaces Created |
The number of spaces the user created. |
Spaces Joined |
The number of spaces the user joined. |
Space Exited |
The number of spaces the user left. |
Messaging App Version
This report only captures the latest Webex App client version when
users send a message. If users only sign in to the Webex App, but they don't send any
messages, then the latest client version isn't captured. |
This report doesn't have a date range or Webex site selection since it shows you data from all Webex sites in your organization and the last known date of when a user sent a message. For example, if a user sent a message on March 1, 2020 and hasn't sent any other messages since then, the report shows the Webex App client version used on that date.
The report shows data on all platforms that a user signed in to Webex App on. For example, if a user signed in to Webex App on the Windows and Mac client, that user will have two separate entries in the report.
Column Name |
Description |
---|---|
Version |
The latest detected version of the Webex App client. |
Platform |
The operating system for the Webex App client. |
User_ID |
The unique ID of the user. |
|
The email address of the user that signed in to the Webex App client. |
Name |
The first and last name of the user. |
Last Known Date |
The date of when the Webex App platform and version number was last detected for a user during the last message sent. For example, if a user didn’t send a message after a Webex App version update, then the report shows the Webex App client version used on that date. |
Calling Media Quality Report
This report shows details about each call leg that had an established media session using Call on Webex or Webex Calling.
Column Name |
Description |
---|---|
User Name |
First and last name of the user. |
|
Email address of the user. |
Start Time |
Time (GMT) of when the call was made. |
Endpoint |
App that the user made or received the call with. |
Device Used |
Physical device that the user made or received the call with. For example, a Cisco IP Phone 8865. |
Call Quality |
Media quality of the call. Call legs are categorized as good if both video and audio stream had jitter below 150ms, latency below 400ms, and packet loss below 5%. |
Duration(s) |
Amount of time in seconds that the call lasted. |
Max Audio Jitter (ms) |
The highest value of audio jitter for the duration of the call, in milliseconds. |
Average Audio Jitter (ms) |
The average value of audio jitter for the duration of the call, in milliseconds. |
Audio Packet Loss (%) |
The highest value of audio packet loss for the duration of the call, in percentage. |
Audio Latency (ms) |
The highest value of audio latency for the duration of the call, in milliseconds. |
Audio Only |
This field shows if the call leg only used audio. |
Max Video Jitter |
The highest value of video jitter for the duration of the call, in milliseconds. |
Average Video Jitter |
The average value of video jitter for the duration of the call, in milliseconds. |
Video Packet Loss (%) |
The highest value of video packet loss for the duration of the call, in percentage. |
Video Latency (ms) |
The highest value of video latency for the duration of the call, in milliseconds. |
Call ID |
Unique ID of the call. |
Local Session ID |
Unique local ID of the call. |
Remote Session ID |
Unique remote ID of the call. |
Location |
Location that the user is assigned to in Control Hub. |
Country |
Country that the user is assigned to in Control Hub. |
Connection Used |
Type of connection used to connect to the call. |
Local IP Address |
Local IP address of the user. |
Audio Codec |
Audio media encoding and decoding format used during the call. |
Video Codec |
Video media encoding and decoding format used during the call. |
Path Optimization |
Path optimization used during the call. The available path optimization types are:
|
Call Type |
The type of call that the user made the call with. Possible values are Webex Calling or Call on Webex. |
Video Duration |
The amount of time in seconds that the user turned on their video. |
Caller |
This field shows if the user was the one who initiated the call. The possible values are:
|
UA Version |
The Webex Calling or Webex App desktop version of the user. |
Calling Engagement Report
This report shows data for the call legs that users made or received with the Webex app using Call on Webex and the Webex Calling app.
Column Name |
Description |
---|---|
Name |
The first and last name of the user. |
|
The email address of the user. |
Start Time |
The time (GMT) of when the call was made. |
Duration |
The amount of time in seconds that the call lasted. |
Video Duration |
The amount of time in seconds that the user turned on their video. |
Endpoint |
The device or app that the user made or received the call with. |
Call ID |
The unique ID of the call. |
Caller |
This field shows if the user was the one who initiated the call. The possible values are:
|
Calling Quality Report
This report shows data for the quality of calls made or received by users with the Webex Calling and Webex desktop apps.
The quality of calls made or received from the Webex app and cloud-registered devices aren't captured in this report. |
Column Name |
Description |
---|---|
Name |
The first and last name of the user. |
|
The email address of the user. |
Start Time |
The time (GMT) of when the call was made. |
Duration |
The amount of time in minutes that the call lasted. |
Endpoint |
The device or app that the user made or received the call with. |
Audio Packet Loss |
The average receiving audio packet loss in percentage. |
Audio Latency |
The average audio round-trip delay in milliseconds. |
Audio Jitter |
The average jitter in milliseconds. |
Video Packet Loss |
The average receiving video packet loss in percentage. |
Video Latency |
The average video round-trip delay in milliseconds. |
UA Version |
The Webex Calling or Webex desktop app version of the user. |
Call ID |
The unique ID of the call. |
Call Queue Stats Report
This report shows details of call queues that have been set up in your organization. You can use this report to see the number of incoming calls to call queues and the status of those calls.
Column Name | Description |
---|---|
Call Queue | Name of the call queue. |
Location | Location assigned to the call queue. |
Phone No. | Phone number assigned to the call queue. |
Extension | Extension number assigned to the call queue. |
Total Hold Mins | Total number of minutes that calls were placed on hold by agents. |
Avg Hold Mins | Average number of minutes that calls were placed on hold by agents. |
Total Talk Mins | Total number of minutes that agents were actively talking on calls. |
Avg Talk Mins | Average number of minutes that agents were actively talking on calls. |
Total Handle Mins | Total number of minutes that agents spent handling calls. Handle minutes are calculated as Total Talk Mins + Total Hold Mins = Total Handle Mins. |
Avg Handle Mins | Average number of minutes that agents spent handling calls. |
Total Wait Mins | Total number of minutes that callers spent waiting for the next available agent to answer the call. |
Avg Wait Mins | Average number of minutes that callers spent waiting for the next available agent to answer the call. |
Calls Answered | Number of calls answered by agents. |
% Answered Calls | Percentage of calls answered by agents. |
Calls Abandoned | Number of calls where the caller hung up or left a message before an agent became available. |
% Abandoned Calls | Percentage of calls where the caller hung up or left a message before an agent became available. |
Avg Abandoned Mins | Average number of minutes where callers hung up or left a message before an agent became available. |
Abandoned Mins | Number of minutes where callers hung up or left a message before an agent became available. |
Total Calls | Total number of incoming calls. |
Overflow - Busy | Number of calls that overflowed because the queue limit was met. |
Overflow - Timed out | Number of calls that overflowed because the wait time exceeded the maximum limit. |
Calls Transferred | Number of calls that were transferred out of the queue. |
Avg No. of Agents Assigned | Average number of agents assigned to call queues. |
Avg No. of Agents Handling Calls | Average number of agents that actively handled calls. |
Call Queue agent stats report
This report shows details of all the agents that have been assigned to call queues in your organization. You can use this report to see which agent gets the most calls and information about their calling stats.
Column Name | Description |
---|---|
Agent/Workspace Name | Name of the agent or workspace. |
Call Queue | Name of the call queue. |
Location | Location assigned to the call queue. |
Total Answered Calls | Number of calls that were presented to the agent and answered by them. |
Bounced Calls | Number of calls that were presented to the agent but went unanswered. |
Total Presented Calls | Number of inbound calls to the agent that were distributed by the call queue. |
Total Talk Mins | Total number of minutes that the agent spent actively talking on calls. |
Avg Talk Mins | Average number of minutes that the agent spent actively talking on calls. |
Total Hold Mins | Total number of minutes that the agent put calls on hold. |
Avg Hold Mins | Average number of minutes that the agent put calls on hold. |
Total Handle Mins | Total number of minutes that an agent spent handling calls. Handle minutes are calculated as Total Talk Mins + Total Hold Mins = Total Handle Mins. |
Avg Handle Mins | Average number of minutes that agents spent handling calls. |
Auto-attendant stats summary
Provides details about calls routed to auto-attendants in your organization.
Column Name | Description |
---|---|
Auto-attendant | Name of the auto-attendant, as provisioned. |
Ph. No. / Extn. | Extension assigned to the auto-attendant. |
Location | Location of the auto-attendant, as provisioned. |
Total calls | Total number of incoming calls routed to the auto-attendant. |
Answered | Number of calls answered by agents, users through call forwarding, or voicemails. |
Unanswered | Number of calls that were routed to agents, users through call forwarding, or voicemails but weren’t answered. |
Busy | Number of calls where callers reached a busy tone. |
Others | Number of calls that had a status other than answered, unanswered, or busy. For example, instances where the caller didn't make a key selection. |
% answered | Percentage of calls answered by agents. |
Total duration | Total time that callers were on the line with the auto-attendant. |
Auto-attendant business hours key details
Provides details about calls routed to auto-attendants during your business regular hours.
Column Name | Description |
---|---|
Auto-attendant | Name of the auto-attendant, as provisioned. |
Key pressed | The key option pressed by callers on the keypad |
Ph. No. / Extn. | Extension assigned to the auto-attendant. |
Location | Location of the auto-attendant, as provisioned. |
Total calls | Total number of incoming calls routed to the auto-attendant. |
Answered | Number of calls answered by agents, users through call forwarding, or voicemails. |
Unanswered | Number of calls that were routed to agents, users through call forwarding, or voicemails but weren’t answered. |
Busy | Number of calls where callers reached a busy tone. |
Others | Number of calls that had a status other than answered, unanswered, or busy. For example, instances where the caller didn't make a key selection. |
% answered | Percentage of calls answered by agents. |
Duration | Length of time that callers were on the line with the auto-attendant. |
Destination | The extension that the auto-attendant routed the call to. |
Key menu | The key menu option assigned to the key pressed on the keypad. |
Key description | The description for the key option pressed by callers on the keypad. |
Auto-attendant after hours key details
Provides details about calls routed to auto-attendants after your business regular hours.
Column Name | Description |
---|---|
Auto-attendant | Name of the auto-attendant, as provisioned. |
Key pressed | The key option pressed by callers on the keypad |
Ph. No. / Extn. | Extension assigned to the auto-attendant. |
Location | Location of the auto-attendant, as provisioned. |
Total calls | Total number of incoming calls routed to the auto-attendant. |
Answered | Number of calls answered by agents, users through call forwarding, or voicemails. |
Unanswered | Number of calls that were routed to agents, users through call forwarding, or voicemails but weren’t answered. |
Busy | Number of calls where callers reached a busy tone. |
Others | Number of calls that had a status other than answered, unanswered, or busy. For example, instances where the caller didn't make a key selection. |
% answered | Percentage of calls answered by agents. |
Duration | Length of time that callers were on the line with the auto-attendant. |
Destination | The extension that the auto-attendant routed the call to. |
Key menu | The key menu option assigned to the key pressed on the keypad. |
Key description | The description for the key option pressed by callers on the keypad. |
This report shows detailed call history data. Use this information to view trends at a high level or drill down to specific call types, for understanding the calling behavior.
Column Name |
Description | ||
---|---|---|---|
Start time |
This is the start time of the call, in UTC. The answer time may be slightly after this value. | ||
Answer time |
The time at which the call was answered in UTC. | ||
Duration |
The length of the call, in seconds. | ||
Calling number |
For incoming calls, it's the telephone number of the calling party. For outgoing calls, it's the telephone number of the user. | ||
Called number |
For incoming calls, it's the telephone number of the user. For outgoing calls, it's the telephone number of the called party. | ||
User |
The user who made or received the call. | ||
Calling line ID |
For incoming calls, it's the calling line ID of the calling party. For outgoing calls, it's the calling line ID of the user. | ||
Called line ID |
For incoming calls, it's the calling line ID of the user. For outgoing calls, it's the calling line ID of the called party. | ||
Correlation ID |
Correlation ID to tie together multiple call legs of the same call session. | ||
Location |
The Webex Calling location of the user for this record. | ||
Inbound trunk |
Inbound trunk may be presented in Originating and Terminating records.
| ||
Outbound trunk |
Outbound trunk may be presented in Originating and Terminating records.
| ||
Route group |
If present, this field's only reported in Originating records. Route group identifies the route group used for outbound calls routed via a route group to Premises-based PSTN or an on-prem deployment integrated with Webex Calling (dial plan or unknown extension). | ||
Direction |
Whether the call was inbound or outbound. The possible values are:
| ||
Call type |
Type of call. Examples:
| ||
Client type |
The type of client that the user (creating this record) is using to make or receive the call. Examples:
| ||
Client Version |
The version of the client that the user (of this CDR) is using to make or receive the call. | ||
Sub client type |
If the call is TO or FROM a mobile phone using Webex Go, the | ||
OS type |
The operating system that the app was running on, if available. | ||
Device Mac |
The MAC address of the device, if known. | ||
Model |
The device model type the user is using to make or receive the call. Examples:
| ||
Answered |
Indicates whether the particular call leg was answered or not. Examples:
| ||
International country |
The country of the dialed number. This is only displayed for international calls. | ||
Original reason |
Call redirection reason for the original called number. Examples:
| ||
Related reason |
Indicates a trigger that led to a change in the call presence. The trigger could be for this particular call or redirected via a different call. Examples:
| ||
Redirect reason |
Call Redirection Reason for the redirecting number. Examples:
| ||
Site main number |
The main number for the user's site where the call was made or received. | ||
Site timezone |
Default setting—Displays the Site/Location's time zone offset value between a particular time zone and UTC in minutes. If the calling timezone is modified from Control Hub, then it displays the particular User/Service calling timezone offset value. | ||
User type |
The type of user (user or workspace) that made or received the call. Examples:
| ||
Call ID |
SIP Call ID used to identify the call. You can share the Call ID with Cisco TAC to help them pinpoint a call if necessary. | ||
Local SessionID |
Each call consists of four UUIDs known as Local Session ID, Remote Session ID, Final Local Session ID, and Final Remote Session ID.
The existing Local and Remote Session ID fields will provide the initial Session ID values, whereas the Final Local and Remote Session IDs will bring a more complete picture of the call. These session IDs act as a global call identifier and will help with tracking even when mid-call transfer or other feature interaction occurs that involves Webex Calling and Remote call control, such as Unified CM via Local Gateway. | ||
Remote SessionID | |||
Final Local Session ID | |||
Final Remote Session ID | |||
User UUID |
A unique identifier for the user associated with the call. This is a unique identifier across Cisco products. | ||
Org UUID |
A unique identifier for the organization that made the call. This is a unique identifier across Cisco. | ||
Report ID |
A unique ID for this particular record. This can be used when processing records to aid in deduplication. | ||
Department ID |
A unique identifier for the user's department name. | ||
Site UUID |
A unique identifier for the site associated with the call. It's unique across Cisco products. | ||
Releasing party |
Indicates which party released the call first. The possible values are:
| ||
Redirecting number |
When the call has been redirected one or more times, this field reports the last redirecting number. It helps to identify who last redirected the call. It only applies to call scenarios such as transfer, call forwarded calls, simultaneous rings and so on. | ||
Transfer related call ID |
Transfer related call ID is used as a call identifier of the other call leg that's involved in the transfer. You can share this ID with Cisco TAC to help them pinpoint parties who are involved during a call transfer. | ||
Dialed digits |
The keypad digits as dialed by the user, before pre-translations. As a result, this field reports multiple call dial possibilities, such as:
This field is only used for originating (outgoing) Calls and is not available for terminating (incoming) Calls. | ||
Authorization code |
The authorization code admin created for a location or site for users to use. It's generally collected by the Account/Authorization Codes or Enhanced Outgoing Calling Plan services. | ||
Call transfer time |
Indicates the time at which the call transfer service was invoked during the call. The invocation time is shown using the UTC/GMT time zone. | ||
User number |
Represents the E.164 number of the user generating a CDR. If the user has no number assigned to them, then their extension will be displayed instead. | ||
Local call ID |
A unique identifier that’s used to correlate CDRs and call legs with each other. This ID is used in conjunction with:
| ||
Remote call ID |
A unique identifier that’s used to correlate CDRs and call legs with each other. This ID is used with | ||
Network call ID |
A unique identifier that shows if other CDRs are in the same call leg. Two CDRs belong in the same call leg if they have the same | ||
Related call ID |
Call identifier of a different call that was created by this call because of a service activation. The value is the same as the | ||
Call outcome |
Identifies whether the call was set up or disconnected normally. Possible values are:
You can find more information in the Call outcome reason field. | ||
Call outcome reason |
Additional information about the Call outcome is returned. Possible reasons are:
| ||
Answer indicator |
When a call is answered, this indicator helps identifies if the call was answered at a post redirected location (such as voicemail or a call forward destination) rather than at the called service or user's phone number. Possible values are:
| ||
Ring duration |
The length of ringing before the call was answered or timed out, in seconds. | ||
Release time |
The time the call was finished, in UTC. | ||
Report time |
The time the report was created, in UTC. | ||
PSTN vendor name |
Displays the vendor’s name from whom the PSTN service was purchased for the respective country. | ||
PSTN Legal Entity |
Displays the regulated business entity registered for providing PSTN service in that particular country. The field is exclusively for Cisco Calling Plans.
| ||
PSTN Vendor Org ID | Displays the Cisco Calling plan's org UUID. It is unique across different regions | ||
PSTN Provider ID |
Represents an immutable Cisco defined UUID attribute for a PSTN provider, which uniquely identifies the entity that has provided PSTN in that country. |
Final local and remote session ID example:
Call transfer with consultation:
- Alice calls Bob.
- Bob answers the call.
- Bob then does a consult transfer to Carol.
- Alice and Carol talk.
The table below shows how the local and final session IDs for Alice, Bob, and Carol differ (in bold) when a call transfer happens.
Detailed call history record (CDR) | Local SessionID | Remote SessionID | Final localsessionID | Final remote sessionID |
---|---|---|---|---|
Alice Originating | X | Y | X | W |
Bob Terminating | Y | X | W | X |
Bob Originating | Z | W | X | W |
Carol Terminating | W | Z | W | X |
Answer indicator with multiple redirections example:
- Alice calls Bob.
- Bob has Call Forward Always option enabled to Carol’s number.
- Carol has Call Forward Busy option enabled to Dave’s number.
- Dave finally attends the call.
- Alice and Dave talk.
The table below shows what the record looks like for the given example:
The original called party here was Bob. But, as the call was answered elsewhere as both Bob and Carol had redirections, their Terminating detailed call history records will have Answer Indicator = Yes-Postredirection
.
Point-to-Point call:
-
Alice calls Bob.
-
Bob answers the call.
-
Either party ends the call.
Webex Calling generates two CDR data. The table below explains the CDR field names and data representations (CDR1, CDR2)
CDR field names | Alice ↔ Bob call leg | |
---|---|---|
CDR1 | CDR2 | |
Direction | ORIGINATING | TERMINATING |
Answered | TRUE | TRUE |
Calling number | +12814659802 | +442030577002 |
Called number | +12814659802 | +442030577002 |
Dialed digits | 77002 | NA |
User | Alice | Bob |
Calling line ID | NA | Alice |
Called line ID | Bob | NA |
Called ID | SSE064225663310323-826219063@10.71.100.219 | BW064226180310323-1351546003@10.21.1.45 |
User type | User | User |
Correlation ID | 9d52512d-0e59-4cb6-9de6-bda7d5b1185e | 9d52512d-0e59-4cb6-9de6-bda7d5b1185e |
Local SessionID | b6230eee00105000a000e069ba481bcd | d0bcbad800105000a000e069ba481ba6 |
Remote SessionID | d0bcbad800105000a000e069ba481ba6 | b6230eee00105000a000e069ba481bcd |
-
Alice’s Originating record (CDR1) would be User = Alice, Called line ID = Bob.
-
Bob’s Terminating record (CDR2) would be User = Bob, Calling line ID = Alice.
-
Correlation ID will remain the same for both Alice and Bob.
-
Alice’s Local Session ID = Bob’s Remote Session ID AND
-
Bob’s Local Session ID = Alice’s Remote Session ID.
Webex Calling generates Originating CDR with Alice's UUID in the Local Session ID field and Bob's UUID in the Remote Session ID field. Webex Calling generates Terminating CDR with Bob's UUID in the Local Session ID field and Alice's UUID in the Remote Session ID field. |
PSTN call to a Webex Calling user:
-
Alice calls Bob. (Alice is the PSTN caller and Bob is Webex Calling user).
-
Bob answers the call.
-
Either party ends the call.
Webex Calling generates only one CDR record for Bob (CDR1=Terminating).
Alice = PSTN Caller (Originating) won’t have any CDR entries.
CDR field names | No CDRs created for Alice PSTN caller | CDR 1 for Bob Webex Calling registered user |
---|---|---|
Direction | - | TERMINATING |
Answered | - | TRUE |
Calling number | - | +91638076xxxx |
Called number | - | +1346298xxxx |
Dialed digits | - | NA |
User | - | NA |
Calling line ID | - | NA |
Called line ID | - | NA |
Called ID | - | BW101135692160523343591672@10.155.7.148 |
User type | - | User |
Related reason | - | NA |
Redirect reason | - | NA |
Redirecting number | - | NA |
Correlation ID | - | e156cd56-f3c9-4455-bea6-174ac975cfec |
Local SessionID | - | 0816529e00105000a0000242be17dcaa |
Remote SessionID | - | NA |
Blind Transfer Call:
Blind or unattended transfer allows you to transfer calls to an alternate extension or phone number without waiting for an answer or confirming the availability of the receiving party.
-
Alice calls Bob.
-
Bob blind transfers the call to Carol. Alice goes on hold.
-
Carol answers the call.
-
Bob clears down.
-
Alice and Carol talk and either party ends the call.
Webex Calling generates four CDR records. The table below explains the CDR field names and data representations (CDR1 to CDR4)
CDR field names | Alice ↔ Bob call leg | Alice ↔ Carol call leg (post blind transfer) | ||
---|---|---|---|---|
CDR1 | CDR2 | CDR3 | CDR4 | |
Direction | ORIGINATING | TERMINATING | ORIGINATING | TERMINATING |
Answered | TRUE | TRUE | TRUE | TRUE |
Calling number | +12814659802 | +12814659802 | +12814659802 | +12814659802 |
Called number | +442030577002 | +442030577002 | +35391111632 | +35391111632 |
Dialed digits | 77002 | NA | 11632 | NA |
User | Alice | Bob | Bob | Carol |
Calling line ID | NA | Alice | NA | Alice |
Called line ID | Bob | NA | Carol | NA |
Call ID | SSE06265895710052371 1826737@10.21.0.147 | BW062659522100523 2103886723@10.21.1.45 | BW06265952210052 32103886723@10.21.1.45 | BW062855359100523- 1346020832@10.21.1.45 |
User type | User | User | User | User |
Related reason | NA | Deflection | Deflection | NA |
Redirect reason | NA | NA | Deflection | Deflection |
Redirecting number | NA | NA | +442030577002 | +442030577002 |
Transfer related call ID | NA | 417887153:0A | 417887153:0 | NA |
Correlation ID | 3631b2a8-a7ba- 414b-8737-46dd30289cd6 | 3631b2a8-a7ba-414b- 8737-46dd30289cd6 | 3631b2a8-a7ba-414b- 8737-46dd30289cd6 | 3631b2a8-a7ba-414b -8737-46dd30289cd6 |
Local SessionID | fb8ed91e00105000a 000e069ba481bcd | 2247175900105000a 000e069ba481ba6 | fb8ed91e00105000a 000e069ba481bcd | e54d9c6300105000a 000c4c603f1c9e8 |
Remote SessionID | 2247175900105000a0 00e069ba481ba6 | fb8ed91e00105000a 000e069ba481bcd | e54d9c6300105000a 000c4c603f1c9e8 | fb8ed91e00105000a 000e069ba481bcd |
- Redirecting number = Bob’s number who did the blind transfer (CDR3, CDR4).
- Related reason = Deflection on CDR2. CDR3 indicates that it was a blind transfer.
- The transfer related
Call ID
provides the call identifier of the other call involved in the transfer, populated only on CDR2 and CDR3. Correlation ID
remains the same for all four CDR call legs (CDR1 through CDR4).Call ID
for CDR2 and CDR3 is unique.- For Alice ↔ Bob call leg, Alice’s
Local Session ID
= Bob’sRemote Session ID
. Bob’sLocal Session ID
= Alice’sRemote Session ID
. - Post blind transfer, Alice’s
Local Session ID
is retained and propagates to Alice ↔ Carol’s call leg. Alice’sLocal Session ID
= Carol’sRemote Session ID
.
Call Park and Retrieval:
-
Alice called Bob and talked.
-
Bob parks the call to Carol’s extension and hangs up.
-
Carol Unparks the call using the Unpark option or by dialing the FAC *88 <extension where the call got parked> and retrieves the call.
-
Alice and Carol talk and either party ends the call.
Webex Calling generates four CDR records. The table below explains the CDR field names and data representations (CDR1 to CDR4)
CDR field names | Alice ↔ Bob call leg | Bob parking the call | Carol unpark / retrieving parked call | |
---|---|---|---|---|
CDR1 | CDR2 | CDR3 | CDR4 | |
Direction | ORIGINATING | TERMINATING | ORIGINATING | ORIGINATING |
Answered | TRUE | TRUE | FALSE | TRUE |
Calling number | +12814659802 | +12814659802 | +442030577002 | +35391111632 |
Called number | +442030577002 | +442030577002 | *6811632 | *8811632 |
Dialed number | 7702 | NA | *6811632 | *8811632 |
User | Alice | Bob | Bob | Carol |
Calling line ID | NA | Alice | NA | NA |
Called line ID | Bob | NA | NA | NA |
Call ID | SSE114440280110523-750048880@10.21.0.147 | BW114441007110523-418027819@10.21.1.45 | SSE114910189110523-234181851@10.23.0.4 | SSE114942533110523-1051117950@10.23.0.4 |
User type | User | User | User | User |
Related reason | NA | NA | CallPark | CallParkRetrieve |
Redirect reason | NA | NA | NA | NA |
Redirecting number | NA | NA | NA | NA |
Transfer related call ID | NA | NA | NA | NA |
Correlation ID | 6a7156c8-fe9a-41bf- 8790-73cdf58c5f95 | 6a7156c8-fe9a-41bf- 8790-73cdf58c5f95 | a6ccd315-99ad-42f7- 88d7-01a7f4a40699 | 1a4be593-5329-47ce- 9972-367a7c5452fd |
Local Seccion ID | 6313d03900105000a 000e069ba481bcd | b7f18c4a00105000 a000e069ba481ba6 | b7f18c4a00105000 a000e069ba481ba6 | 323ebde800105000 a000c4c603f1c9e8 |
Remote Session ID | b7f18c4a00105000a 000e069ba481ba6 | 6313d03900105000a 000e069ba481bcd | NA | 6313d03900105000a 000e069ba481bcd |
- Related reason =
CallPark
on CDR3 indicates that Bob did aCallPark
. - Related reason =
CallParkRetrieve
on CDR4 indicates that Carol did theUnpark
orCallParkretrieval
. - Answered indicator =
FALSE
for CDR3 parked leg. Answered indicator =TRUE
for rest of the call legs. - The correlation ID remains the same for Alice ↔ Bob. Bob parking the call and Carol unparking would have a different correlation ID.
- For Alice ↔ Bob. Alice’s Local Session ID = Bob’s Remote Session ID. Bob’s Local Session ID = Alice’s Remote Session ID.
- When Bob parks the call to Carol’s extension, only an
ORIGINATING
CDR3 is created that retains Bob’s Local Session ID, Remote Session ID = NA. - By the time Carol Unparks the call, Alice’s Local Session ID is retained and propagates to Alice ↔ Carol's call leg. Alice’s Local Session ID = Carol’s Remote Session ID.
Call with multiple redirection flows:
-
Alice calls Bob. Bob has Call forward Busy enabled to Carol.
-
Carol has Call forward always enabled to Dave.
-
Dave picked up the call, Alice & Dave talked and either party ends the call.
Webex Calling generates six CDR records. The table below explains the CDR field names and data representations (CDR1 to CDR6).
- The calling number always conveys the actual calling party, and it is not modified by any redirections.
- CDR3, CDR4 (
CallForwardBusy
), Redirecting number = Bob’s number. Related reason=CallForwardBusy
and Redirect reason=UserBusy
. - CDR5, CDR6 (
CallForwardAlways
), Redirecting number = Carol’s number. Related reason=CallForwardAlways
and Redirect reason=Unconditional
. - For Alice ↔ Bob call leg, Alice’s Local Session ID = Bob’s Remote Session ID. Bob’s Local Session ID = Alice’s Remote Session ID.
- For Bob ↔ Carol’s (
CallForwardBusy
) and Carol ↔ Dave’s (CallForwardAlways
), Local Session ID and Remote Session ID from Alice’s call leg are retained and propagated. - For the final call leg from Alice ↔ Dave, Alice’s Local Session ID = Daves’s Remote Session ID. Dave’s Local Session ID = Alice’s Remote Session ID.
Call Timeline
- Alice takes about 20 seconds to call Bob.
- Bob places Alice on Hold and blind transfers the call to Charlie which takes about 3 seconds before Charlie answers the transferred call.
- Bob clears down and Alice ends the call with Charlie which takes about 23 seconds.
Based on the preceding case, the overall call length is about 46 seconds.
For reference, the spreadsheet captures the Blind Transfer Call Details:
Some records report special functionality. For example, records tagged with relatedReason= |
Queue stats
Provides details of call queues that have been set up in your organization. You can use this report to see the number of incoming calls to call queues and the status of those calls.
Column name | Description |
---|---|
Call Queue | Name of the call queue. |
Location | Location assigned to the call queue. |
Phone NO. | Phone number assigned to the call queue. |
Extension | Extension number assigned to the call queue. |
Total Hold Time | Total time that calls were placed on hold by agents. |
Avg Hold Time | Average time that calls were placed on hold by agents. |
Total Talk Time | Total time that agents were actively talking on calls. |
Avg Talk Time | Average time that agents were actively talking on calls. |
Total Handle Time | Total time that agents spent handling calls. Handle time is calculated as Total talk time + Total hold time = Total handle time. |
Avg Handle Time | Average time that agents spent handling calls. |
Total Wait Time | Total time that callers spent waiting for the next available agent to answer the call. |
Avg Wait Time | Average time that callers spent waiting for the next available agent to answer the call. |
Answered Calls | Number of calls answered by agents. |
% Answered Calls | Percentage of calls answered by agents. |
Abandoned Calls | Number of calls where the caller hung up or left a message before an agent became available. |
% Abandoned Calls | Percentage of calls where the caller hung up or left a message before an agent became available. |
Avg Abandoned Time | Average time where callers hung up or left a message before an agent became available. |
Total Abandoned Time | Time where callers hung up or left a message before an agent became available. |
Total Calls | Total number of incoming calls. |
Calls Overflowed | Number of calls that overflowed because the queue limit was met. |
Calls Timed Out | Number of calls that timed out because the wait time exceeded the maximum limit. |
Calls Transferred | Number of calls that were transferred out of the queue. |
Avg No. of Agents Assigned | Average number of agents assigned to call queues. |
Avg No. of Agents Handling Calls | Average number of agents that actively handled calls. |
Queue agent stats
Provides details of all agents that have been assigned to call queues in your organization. You can use this report to see which agent gets the most calls and information about their calling stats.
Column name | Description |
---|---|
Agent Name | Name of the agent. |
Call Queue | Name of the call queue. |
Location | Location assigned to the call queue. |
Total Answered Calls | Number of calls that were presented to the agent and answered by them. |
Bounced Calls | Number of calls that were presented to the agent but went unanswered. |
Total Presented Calls | Number of inbound calls to the agent that were distributed by the call queue. |
Total Talk Time | Total time that an agent spent actively talking on calls. |
Avg Talk Time | Average time that an agent spent actively talking on calls. |
Total Hold Time | Total time that an agent put calls on hold. |
Avg Hold Time | Average time that an agent put calls on hold. |
Total Handle Time | Total time that an agent spent handling calls. Handle minutes are calculated as Total talk time + Total hold time = Total handle time. |
Avg Handle Time | Average time that an agent spent handling calls. |
Rooms and Desks Detail
Use this report to see details of every device in your organization and what they're being
used for. Look at the Total Hours Used
column to quickly pinpoint
underutilized devices. It shows the total usage of the device over the selected date range.
You can also find out which devices have been offline by checking the Last Seen
Date
column.
The information in this report is the same as what you can find in the Analytics dashboard.
Column Name |
Description |
---|---|
Device ID |
Unique identifier internal for administrators. |
Device Type |
Device model. |
Assigned To |
Name of the place or user this device is assigned to. If this field is blank, then the device was deleted from your organization. |
Tags |
Shows tags assigned to the device on the Control Hub Devices page. |
IP Address |
Last known IP address of when the device was online. |
Mac Address |
Media Access Control address of the device. |
Latest Known Status |
Device online status from the last 24 hours. |
Total Hours Used |
Total usage over the selected date range |
Calls |
The number of hours the device was used for a call over the selected date range. |
Local Display Wired |
The number of hours the device was used for a wired local display over the selected date range. |
Local Display Wireless |
The number of hours the device was used for a wireless local display over the selected date range. |
Whiteboarding |
The number of hours the device was used for whiteboarding over the selected date range. |
Digital Signage |
The number of hours the device was used for digital signage over the selected date range. |
USB Passthrough |
The number of hours the device was used for USB passthrough over the selected date range. |
First Seen |
Shows when the device was added to Control Hub for the first time. |
Last Seen |
Shows when the device was last online. |
Delete Date |
Shows when the device was deleted from Webex. |
VIMT License Report
This report shows you license usage for unique active Cisco devices and third-party SIP devices that use the Video Integration for Microsoft Teams (VIMT) in your organization. Each date that you select has their own set of data. For example, if you run a report for June 1, 2020 to June 5, 2020, then the report shows you data for each date of the report.
Column Name |
Description |
---|---|
Webex Org ID |
The unique ID of the Control Hub organization that the report belongs to. |
Date |
The calendar date for the recorded data. There is one record per day. |
Device 24 hours |
The count of unique devices that used VIMT in the last 24 hours of the date. |
Device last 30 days |
The rolling count of unique devices that used VIMT in the last 30 days of the date. |
Unique Devices Rolling 90 day average |
The rolling average count of unique devices that used VIMT in the last 90 days of the date. |
VIMT Usage Report
This report provides details about calls where Cisco devices and third-party SIP devices used Video Integration for Microsoft Teams (VIMT) to join Microsoft Teams meetings.
Column Name |
Description |
---|---|
Teams Conference ID |
The unique ID of the Microsoft Teams meeting. |
Device Name |
The name of the device used to join the Microsoft Teams meeting. |
Device URL |
The URL associated with the device. |
Device Join Time |
The time (in UTC+0) when the device joined the Microsoft Teams meeting using VIMT. |
Device Disconnect Time |
The time when the device disconnected from the Microsoft Teams meeting. |
Device SIP URI |
The Session Initiation Protocol (SIP) address associated with the device. |
Teams Tenant ID |
The unique ID of the user in the Microsoft Teams client. |
Date device joined call |
The date that the device was used to join the Microsoft Teams meeting using VIMT. |
Device power consumption report
Provides details of the energy consumption of Cisco devices and phones. You can use this report to see which devices are using up a lot of energy, and with that information, change modes accordingly to save on energy costs.
This report includes data for the following measurable devices and phones:
- Desk Portfolio (excluding DX 70)
- Board Portfolio (excluding Spark Board 55 and 70)
- Room Kit and Room Kit Mini
- Room Bar and Room Bar Pro
- Quad Cam
- Codec Plus, Codec Pro, Codec EQ
- Room55S
- Desk Phone 9800
Column name | Description | ||
---|---|---|---|
Device name | Name of the device. | ||
Device type | Device model. | ||
Location | Location assigned to the device. | ||
Hours in Call mode | Number of hours (in two decimal points) the device spent in Call mode. | ||
Power consumption in Call mode | How much energy the device consumed in watts while in Call mode. | ||
Hours in Idle mode | Number of hours (in two decimal points) the device spent in Idle mode. | ||
Power consumption in Idle mode | How much energy the device consumed in watts while in Idle mode. | ||
Hours in Halfwake mode | Number of hours (in two decimal points) the device spent in Halfwake mode.
| ||
Power consumption in Halfwake mode | How much energy the device consumed in watts while in Halfwake mode
| ||
Hours in Display Off mode | Number of hours (in two decimal points) the device spent in Display Off mode. | ||
Power consumption in Display Off mode | How much energy the device consumed in watts while in Display Off mode. | ||
Hours in Networked Standby mode | Number of hours (in two decimal points) the device spent in Networked Standby
mode.
| ||
Power consumption in Networked Standby mode | How much energy the device consumed in watts while in Networked Standby
mode.
| ||
Total power consumption | How much energy the device consumed in kilowatts while in all of the modes combined. | ||
Hours in Deep Sleep mode | Number of hours (in two decimal points) the phone spent in Deep Sleep
mode.
| ||
Power consumption in Deep Sleep mode | How much energy the phone consumed in watts while in Deep Sleep mode.
|
Onboarding User Activation and License Details Report
This report shows details about how users were added to your organization and how licenses were assigned to them.
This report isn't available in Webex for Government organizations. |
Column Name |
Description |
---|---|
Name |
The first and last name of the added user. |
|
The email address of the user. |
Administrator Name |
The first and last name of the administrator who added the user, if applicable. |
Administrator Email |
The email address of the administrator who added the user, if applicable. |
Invite Sent (GMT) |
The date and time an invitation was sent to the user, if applicable. |
Onboard Method |
The method used to add the user to Control Hub. Possible values are:
|
License Assign Method |
The method used to assign the user the license. The methods are:
|
Licenses |
The names of licenses assigned to the user. |
License Assign Status |
If the licenses were assigned to the user successfully or unsuccessfully. |
Activation Status |
The user’s activation status is shown as Activated if the user signs in to the Webex App for the first time. Users that haven't signed in to the Webex App show as Pending. |
Activation Date |
The date of when the user’s status changed to Active. |
User ID |
The unique ID of the user. |
Administrator ID |
The unique ID of the administrator who added the user. |
Enterprise Agreement Report
Provides information about how many licenses are being used in a subscription. This report is only available if your organization has an active true forward eligible subscription.
Column Name |
Description | ||
---|---|---|---|
Period |
The period that the subscription is in. A period is defined as a 30-day cycle that starts on the day your subscription was activated, and corresponds with your billing cycle. For example, if your subscription started on July 5, 2020, then the next period would start 30 days later, on August 4, 2020. | ||
Date |
The calendar date within the period. | ||
Subscription ID |
The unique ID of the subscription. | ||
Product |
The name of the product for the reported licenses. | ||
Provisioned License Quantity |
The total number of licenses provisioned for the subscription and product. | ||
Allocated License Quantity |
The number of licenses allocated to users at the reported date. | ||
Consumption Quantity |
This number reflects the aligned value used to identity a True Forward. IT admins can track this value throughout the contract term, well before the period in which the subscription is due for a potential change.
| ||
You can customize existing templates by reordering or removing columns to view the data that you want to focus on. For example, you can create customized Meetings Attendees reports that focus on participants in specific locations or on specific operating systems, or customized Calling Quality reports that focus on audio or video media quality instead of both. Custom templates appear in their own section,and are tagged so you can easily identify them.
Some templates aren't available for customization, and some columns are required for certain templates. You can tell which columns are required by a template if you can't remove them when you're customizing a template, as shown in the following image.
Each administrator can create up to 50 custom templates, and only you can view the custom templates that you created. |
You can create up to 50 custom templates and only you can view your custom templates. Other administrators can create their own set of up to 50 custom templates.
Custom templates aren't editable after they're created. |
1 |
Sign in to Control Hub and go to . |
2 |
Click New template. A full-screen window appears. To exit this window, you can click Cancel or finish creating the custom template.
|
3 |
In the Template section, select which template you want to customize, enter the name for the custom template, and add a description. |
4 |
In the Data section, you can choose to:
|
5 |
Click Save template. |
When you delete a custom template, any automatic schedules for that template will also be deleted. You'll still keep any previously generated report of that custom template.
1 |
Sign in to Control Hub and go to . |
2 |
Click the More button next to the custom template you want to delete. |
3 |
Select Delete and then confirm your choice. |
1 |
Sign in to Control Hub and go to . |
2 |
Click on a report template that you want to generate. |
3 |
Click Generate report. |
4 |
Choose to generate the report:
|
5 |
Check the Notify me by email check box if you want an email of when the report is ready for you to download. |
6 |
Depending on the schedule for the report, select Generate Report or Schedule Report. |
Reports that you generate show up in the Report list tab. You can see when a report is ready to download under the Status column. Report statuses available are:
- Processing—The report is generating the data for you to download.
- Processed—The report has generated the data. You can start to prepare the report for download.
- Preparing for download—You've selected to prepare the report so you can download it.
- Ready for download—The report is ready for you to download at any time.
- Incomplete—The report wasn't processed correctly. Generate the report again to fix this status.
You can only have a maximum of 50 reports in this list. Future scheduled reports won't run until there are fewer than 50 reports. |
1 |
Sign in to Control Hub and go to . |
2 |
Under Actions, click More next to the report you want to download, and then select Prepare for download. The report's status changes to Preparing for download.
|
3 |
Once the report's status changes to Ready for download, click More, and then select Download report. |
4 |
Select Compressed file. The report starts to download.
|
You can disable a report if you want to pause the report from running automatically.
1 |
Sign in to Control Hub and go to . |
2 |
Under Actions, click More, and then select Disable. |
1 |
Sign in to Control Hub and go to . |
2 |
Under Actions, click More, and then Delete. |
3 |
Select Delete |
You can use classic reports to view comprehensive statistics for Webex Meetings, Webex Events (Classic), Webex Training, and Webex Support services in your organization. Monitor usage across services, attendance for events and sessions, and support activities so that you can determine how you can build a more efficient organization.
Learn more about these reports at this article.