报告连同分析故障排除是 Control Hub 中监控部分下的一部分,可以用于帮助跟踪使用情况或解决组织中 Webex 服务的问题。

Report templates in Control Hub

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

要通过 API 生成这些报告,请参阅报告 API报告模板 API 开发者页面。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.

下表将显示 Control Hub 可使用的报告类型、可查看每个报告数据的最早日期范围以及可为所运行的每个报告选择的最大日期范围。

报告

标准许可证

Pro Pack 许可证

Latest Data Available to Generate on Current Date

可用数据日期范围

标准—每次下载的日期范围限制

Pro Pack—每次下载的日期范围限制

加入用户激活和许可证详细信息报告

昨天

自当前日期起 13 个月

3 个月

13 个月

Meetings Embedded Apps Report

昨天

自当前日期起 13 个月

3 个月

13 个月

Meetings In-Meeting Feature Usage Report

昨天

自当前日期起 13 个月

31 天

会议使用摘要报告

昨天

自当前日期起 13 个月

3 个月

13 个月

会议高 CPU 报告

昨天

自当前日期起 13 个月

3 个月

13 个月

会议当前主持人报告

昨天

自当前日期起 13 个月

3 个月

13 个月

会议非活跃用户报告

昨天

自当前日期起 13 个月

3 个月

13 个月

Meetings Active User Rolling Average Report**

昨天

自当前日期起 13 个月

3 个月

13 个月

Enterprise Agreement Report**

昨天

自当前日期起 13 个月

3 个月

13 个月

会议详细信息报告

昨天

自当前日期起 13 个月

31 天

会议与会者报告

昨天

自当前日期起 13 个月

31 天

会议音频使用报告

昨天

自当前日期起 13 个月

31 天

Meetings 电话报告

昨天

自当前日期起 13 个月

31 天

Meetings License Consumption Report**

昨天

不适用

不适用

网络研讨会报告*

昨天

2021 年 5 月 1 日

3 个月

13 个月

Messaging External Domain Report

昨天

自当前日期起 13 个月

31 天

Bot 消息传递活动报告

昨天

自当前日期起 13 个月

31 天

消息传递用户活动报告

昨天

自当前日期起 13 个月

31 天

Bot 消息传递活动摘要报告

昨天

自当前日期起 13 个月

31 天

消息传递用户活动摘要报告

昨天

自当前日期起 13 个月

31 天

消息传递应用程序版本报告

昨天

自当前日期起 13 个月

不适用

会议未来计划报告

NA (future 90 days)

不适用

90 天

Calling Media Quality Report

昨天

自当前日期起 13 个月

31 天

31 天

呼叫参与度报告

昨天

自当前日期起 13 个月

31 天

31 天

呼叫质量报告

昨天

自当前日期起 13 个月

31 天

31 天

呼叫详细呼叫历史记录

昨天

自当前日期起 13 个月

自 2022 年 4 月 12 日起提供的数据

31 天

31 天

呼叫详细呼叫历史记录报告

昨天

自当前日期起 13 个月

31 天

31 天

Call Queue Stats Report

今天

自当前日期起 13 个月

3 个月

13 个月

Call Queue Agent Stats Report

今天

自当前日期起 13 个月

3 个月

13 个月

Auto Attendant Reports - Stats Summary, Business Hours Key Details, After-Hours Key Details

今天

自当前日期起 13 个月

Data available from July 29, 2022

3 个月

13 个月

会议室和桌面详细信息报告*

昨天

自当前日期起 13 个月

3 个月

13 个月

VIMT 许可证报告*

昨天

自当前日期起 13 个月

3 个月

13 个月

VIMT 使用情况报告*

昨天

自当前日期起 13 个月

3 个月

13 个月

Devices Power Consumption Report*

昨天

自当前日期起 13 个月

3 个月

13 个月


 

* 这些报告不可用于政府版 Webex 组织。

** These reports are only available for subscriptions that bill based on the number of license usage.

报告列表

该选项卡显示可供下载的报告列表。如果您在计划报告时选择订阅报告,那么系统还会收到一封电子邮件,通知您报告已就绪可供下载。

生成报告时,状态列将变为“正在进行”。当报告准备就绪可供下载时,状态列将变为“完成”。您的报告最多可能需要 24 小时才能生成,具体取决于报告的大小以及排队的报告数。生成的报告会显示在报告列表标签页中。


 

该列表最多只能包含 50 份报告。达到限制后,请删除一些报告以再次生成新报告。

Reports list UI in Control Hub

已安排的报告

该选项卡显示了设置为周期性运行的报告列表。您可查看每个报告的重复详情以及最后生成时间。

Scheduled Reports UI in Control Hub

该选项卡显示可用于计划报告的固定模板列表,以及每个报告的简要描述。


 
These reports are for your general use and shouldn't be used for billing purposes.

要查看有关这些报告的更多信息,您可以展开以下部分:

数据可用性

数据是根据 UTC 时区捕捉的。最后一天的数据需要大约 8 小时才能显示在后一天(大约 8:00 UTC)中。当某些报告更新为新数据时,可能会影响不同的时区。

例如,如果您在同一天生成报告,报告可能只包含部分数据。如果您在该时间范围内包含前一天和同一天,报告可能也包含部分数据,具体取决于您的时区。

如果发现报告没有包含前一天的所有数据,我们建议您在下午生成同一天的报告,并包括前一天的报告。

Meetings Embedded Apps

Provides details about the different types of Webex embedded apps that a participant uses in a meeting

列名称

描述

Conference_ID

会议的唯一标识。

Meeting_Name

会议主题。

Meeting_Type

Type of meeting that took place. 可能的值为:

  • MC — Webex Meetings
  • EC - Webex Events(经典)
  • TC — Webex Training
  • SC — Webex Support
  • 网络研讨会 - Webex网络研讨会
  • 网络广播 - Webex网络研讨会视图

电子邮件地址

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

列名称

描述

MEETING_NUMBER

用于加入会议的 9 位会议访问码。

MEETING_NAME

会议的主题。

CONFID

会议的唯一标识。

USER_NAME

The name of the user who attended the meeting.

EMAIL

The email address of the user who attended the meeting.

JOIN_DATE

会议日期 (GMT)。

START_TIME

会议开始时间 (GMT)。

END_TIME

会议结束时间 (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

The user accessed annotation features during the meeting.

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.


 
This field only applies to users who join meetings on the Webex Suite meeting platform. The value for users who aren't on this platform show as N even if they 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.

会议详细信息

提供有关在所选日期范围内开始的会议的详细信息。您可查看会议主持人、会议开始与结束时间、参加会议的人数、会议是否被录制等。

列名称

描述

MEETING_NUMBER

用于加入会议的 9 位会议访问码。

MEETING_NAME

会议的主题。

CONFERENCE_ID

会议的唯一标识。

MEETING_TYPE

所举行的会议类型。可能的值为:

  • MC — Webex Meetings
  • EC - Webex Events(经典)
  • TC — Webex Training
  • SC — Webex Support
  • 网络研讨会 - Webex网络研讨会
  • 网络广播 - Webex网络研讨会视图

HOST_NAME

创建或安排会议的用户的姓名。

HOST_USERID

主持人的唯一标识。

HOSTEMAIL

主持人的电子邮件地址。

START_TIME

会议开始时间 (GMT)。

END_TIME

会议结束时间 (GMT)。

DURATION

会议的时长(分钟)。

TOTAL_ATTENDEE

会议中的参加者人数。

PEOPLE_MINS

所有参加者在会议中已经待过的总分钟数。

例如,如果一个会议有 3 位参加者,每个参加者加入了 10 分钟,那么总数等于 3 个参加者 x 10 分钟 = 30 分钟。

IS_VOIP

至少有一位参加者通过计算机使用音频连接来呼入会议。

IS_SHARING

至少有一位参加者在会议中共享了屏幕。

IS_RECORD

会议是否已录制。

VIDEO_USERS

通过 Webex Meetings 客户端加入并在会议期间开启视频的参加者人数。

VIDEO_MINS

参加者发送视频的总分钟数。

AUDIO_ONLY (PCN)

使用 PSTN 呼叫所有会议参加者。

TRACKING_CODE_1-10

与用户关联的跟踪代码。


 

报告只显示默认的跟踪代码名称。

INTEGRATION_USED

该字段可显示是否通过与 Cisco Webex Meetings 应用程序集成的 Microsoft TeamsMicrosoft OutlookSlackGoogle Calender 安排会议。

WEBEX_ASSISTANT

此字段可显示会议中是否已使用 Webex Assistant for Meetings。可能的值为:

  • Y—会话期间已使用 Webex Assistant。

  • N—完全未使用 Webex Assistant。

BREAKOUT_USED

该字段显示会议期间是否启动分组讨论。可能的值为:

  • Y—已创建分组讨论。

  • N—没有使用分组讨论。

IS_E2EE

此字段显示是否使用端到端加密 (E2EE) 安排了会议。可能的值为:

  • Y—会议已进行端到端加密。

  • N—会议未进行端到端加密。

SI_USED

此字段显示主持人是否启用了会议的同声传译功能。可能的值为:

  • Y - 主持人为会议启用了同声传译。

  • N - 主持人没有为会议启用同声传译。

会议与会者

提供每个在所选日期范围内出席会议的参加者的详细信息。您可以了解在会议期间参加者的媒体质量数据及其加入会议方式的信息。


 

参加者的媒体质量数据和硬件信息仅在会议持续时间超过两分钟时可用。

列名称

描述

MEETING_NUMBER

用于加入会议的 9 位会议访问码。

MEETING_NAME

会议的主题。

CONFERENCE_ID

会议的唯一标识。

USER_NAME

出席会议的参加者的姓名。

EMAIL

出席会议的参加者的电子邮件地址。

LOCATION

参加者加入会议时所在的国家/地区。

JOIN_DATE

会议日期 (GMT)。

START_TIME

参加者加入会议的时间 (GMT)。

END_TIME

参加者离开会议的时间 (GMT)。

DURATION

参加者加入会议的时间长度(分钟)。

OS

参加者用于加入会议的设备的操作系统。

BROWSER

参加者用于 Web 版 Webex Meetings 以加入会议的 Web 浏览器。

LOCAL_IP

用于加入会议的客户端的 IP 地址。如果这些 IP 地址位于防火墙后,它们可能不是外部可路由地址。

PUBLIC_IP

外部可路由的客户端的 IP 地址。This can be the same as LOCAL_IP if the client is connected directly to the internet without using a VPN.

VOIP_RECEIVING_AVERAGE_PACKET_LOSS

会议持续时间内从 Webex 云到客户端方向的平均音频丢包率(以百分比表示)。


 

接收丢包在 Webex 丢包恢复后计算。

VOIP_AVERAGE_LATENCY

会议持续时间内的平均音频延迟(以毫秒为单位)。

JOIN_MEETING_TIME

JMT = (从单击会议链接到加载预览窗口的时间) + (从单击预览窗口中的“加入”按钮到连接进入会议的时间)。

JMT 不计算用户浏览菜单、在预览窗口中进行选择或在等候区中等待所花费的时间。

TCP_PERCENTAGE

参加者已针对网络语音呼叫使用 TCP 连接的持续时间百分比。

UDP_PERCENTAGE

参加者已针对网络语音呼叫使用 UDP 连接的持续时间百分比。

IS_CMR

与会者是否使用 Webex Room 或桌面设备加入会议。

IS_SHARING

参加者是否在会议期间共享了屏幕。

IS_RECORD

参加者是否单击了“录制”按钮。

VIDEO_MINUTES

参加者在会议中启用视频的总分钟数。

CLIENT

用于加入会议的软客户端的类型。

CLIENT_VERSION

用于加入会议的软客户端的版本。

MEDIA_NODE

客户端连接到的媒体节点的数据中心或区域。对于基于云的媒体节点,这是通用区域名称,例如“美国圣何塞”。

对于基于视频网的媒体节点,这将具有与客户设置的视频网集群名称相匹配且更为具体的名称。

CONNECTION

客户端用于交换媒体的网络连接类型。可能的值为“wifi”、“以太网”、“蜂窝”或“未知”。


 

此项并非对每种媒体类型都会跟踪。在会议期间,此项可能发生变化(并相对常见)。此处仅录制初始连接。

HARDWARE

用于加入会议的设备的硬件品牌和型号。对于计算机,这可能是“Lenovo Thinkpad p60”。对于电话,这可能是“Samsung Galaxy S7”。对于协作室设备,这可能是“Cisco Webex Room Kit”。

CAMERA

会议期间使用的摄像头的品牌名称和型号信息。


 

此项在会议期间可能发生改变,但只会报告使用的初始摄像机。

MICROPHONE

会议期间使用的麦克风的品牌名称和型号信息。


 

此项在会议期间可能发生改变,但只会报告使用的初始麦克风。

SPEAKER

会议期间使用的扬声器的品牌名称和型号信息。


 

此项在会议期间可能发生改变,但只会报告使用的初始扬声器。

AUDIO_AVERAGE_LATENCY

会议持续时间内的平均音频延迟(以毫秒为单位)。

AUDIO_MAX_LATENCY

会议持续时间内的音频延迟的最高值(以毫秒为单位)。

AUDIO_RECEIVING_AVERAGE_PACKET_LOSS

会议持续时间内的平均端到端音频丢包率(以百分比表示)。

AUDIO_RECEIVING_MAX_PACKET_LOSS

会议持续时间内的端到端音频丢包率的最高值(以百分比表示)。

AUDIO_SENDING_AVERAGE_PACKET_LOSS

会议持续时间内的平均音频丢包率(以百分比表示)。

AUDIO_SENDING_MAX_PACKET_LOSS

会议持续时间内的音频丢包率的最高值(以百分比表示)。

AUDIO_RECEIVING_AVERAGE_JITTER

会议持续时间内的平均音频抖动时间(以毫秒为单位)。

AUDIO_RECEIVING_MAX_JITTER

会议持续时间内的音频抖动时间的最高值(以毫秒为单位)。

AUDIO_SENDING_AVERAGE_JITTER

会议持续时间内的平均音频抖动时间(以毫秒为单位)。

AUDIO_SENDING_MAX_JITTER

会议持续时间内的音频抖动时间的最高值(以毫秒为单位)。

VIDEO_AVERAGE_LATENCY

会议持续时间内的平均视频延迟(以毫秒为单位)。

VIDEO_MAX_LATENCY

会议持续时间内的视频延迟的最高值(以毫秒为单位)。

VIDEO_RECEIVING_AVERAGE_PACKET_LOSS

会议持续时间内的平均视频丢包率(以百分比表示)。

VIDEO_RECEIVING_MAX_PACKET_LOSS

会议持续时间内的视频丢包率的最高值(以百分比表示)。

VIDEO_SENDING_AVERAGE_PACKET_LOSS

会议持续时间内的平均视频丢包率(以百分比表示)。

VIDEO_SENDING_MAX_PACKET_LOSS

会议持续时间内的视频丢包率的最高值(以百分比表示)。

VIDEO_RECEIVING_AVERAGE_JITTER

会议持续时间内的平均视频抖动时间(以毫秒为单位)。

VIDEO_RECEIVING_MAX_JITTER

会议持续时间内的视频抖动时间的最高值(以毫秒为单位)。

VIDEO_SENDING_AVERAGE_JITTER

呼叫持续时间内的平均视频抖动时间(以毫秒为单位)。

VIDEO_SENDING_MAX_JITTER

会议持续时间内的视频抖动时间的最高值(以毫秒为单位)。

CPU_APPLICATION_AVERAGE

会议持续时间内 Webex 应用程序的平均 CPU 使用率(以百分比表示)。

CPU_APPLICATION_MAX

会议持续时间内 Webex 应用程序的 CPU 使用率最高值(以百分比表示)。

CPU_SYSTEM_AVERAGE

会议持续时间内的平均系统 CPU 使用率(以百分比表示)。

CPU_SYSTEM_MAX

会议持续时间内的系统 CPU 使用率最高值(以百分比表示)。

VIRTUAL_BACKGROUND_USED

该字段显示参加者是否在会议期间启用虚拟背景。可能的值为:

  • Y—在会议期间启用过一次虚拟背景。

  • N—没有使用虚拟背景。

主持人_指示器

该字段会显示参加者是主持人还是与会者。可能的值为:

  • TRUE - 参加者是主持人。

  • FALSE - 参加者是与会者。

IS_COHOST

This field shows if the participant was a cohost for the meeting. 可能的值为:

  • Y—The participant was a cohost.

  • N—The participant was not a cohost.

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.

可能的值为:

  • Good—If the average video packet loss was less than or equal to 5% and the average video latency was less than or equal to 400ms, then video quality is counted as good.
  • Bad—If the average video packet loss was more than 5% and the average video latency was more than 400ms, then video quality is counted as bad.
  • Unknown—If video or audio data isn't available for at least a minute, then video quality is counted as unknown.

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.

可能的值为:

  • Good—If the average audio packet loss was less than or equal to 5% and the average audio latency was less than or equal to 400ms, then VoIP quality is counted as good.
  • Bad—If the average audio packet loss was more than 5% and the average audio latency was more than 400ms, then VoIP quality is counted as bad.
  • Unknown—If video or audio data isn't available for at least a minute, then VoIP quality is counted as unknown.

会议使用摘要

提供所选日期范围内主持的会议总数的详细信息。

列名称

描述

会议数

在所选时间段内召开的会议总数。

会议总分钟数

选定时间段内所有会议持续时间的总分钟数。例如,如果三个会议各自持续 30 分钟,那么会议总分钟数为 90。

参加者人数

选定时间段内所有 Webex 会议参加者或设备加入的总数。例如,如果参加者或设备从会议断开连接然后重新加入,计数为 2。

参与总时长

所有参加者在一个会议中的总分钟数。例如,如果会议有 3 名参加者并持续 10 分钟,则计数为 30 分钟(3 x 10 分钟)。

参加者发送视频分钟数

参加者启用视频的总分钟数。例如,一项会议有五名参加者,会议时长 30 分钟,但只有两名参加者全程启用视频,则视频分钟数数为 60。

参加者网络语音分钟数

加入会议的参加者使用网络语音通话的总分钟数。

参加者音频分钟数

加入会议的参加者使用 PSTN 通话的总时长。

会议活动主持人

提供主持人在所选日期范围内安排和开始的会议数的详细信息。

列名称

说明

UserID

主持人的电子邮件地址。

主持的会议数

The number of meetings scheduled and hosted by this user within the reported time period.

主持

The name of the user who hosted the meeting, or the name of the device if the meeting was hosted on a device.

会议非活动用户

提供有关未在所选日期范围内主持或出席会议的用户的详细信息。

列名称

描述

FIRST_NAME

用户的名字。

LAST_NAME

用户的姓氏。

USERNAME

用户的电子邮件地址。

USER_ID

用户的唯一标识。

EMAIL

用户的电子邮件地址。

IS_HOST

用户是否具有 Webex Meetings 主持人许可证。

IS_SITEADMIN

用户是否具有 Webex 站点的管理员角色。

DAYS_SINCE_LAST_ACTIVE

自用户上次通过 Webex 应用程序或 Webex Meetings 主持或出席会议以来的天数。

LAST_ACTIVE_DATE

用户上次通过 Webex 应用程序或 Webex Meetings 主持或出席会议的日期。PSTN 呼入用户不会算作活跃用户。

会议音频使用情况

提供参加者在会议期间使用的不同类型音频的详细信息。

列名称

描述

CONF ID

会议的唯一标识。

会议号

用于加入会议的 9 位会议访问码。

音频类型

参加者用于加入会议的音频类型。音频类型为:

  • CCA 拨入 - 通过云连接音频拨入加入会议。

  • CCA 呼出 - 通过云连接音频回呼加入会议。

  • PSTN 拨入 - 通过 PSTN 拨入加入会议。

  • PSTN 拨出 - 通过 PSTN 回呼加入会议。

  • VoIP - 使用网络语音加入会议。

  • Edge 音频 - 通过 Edge 音频使用拨入或使用回呼加入会议。

  • 回退 - 如果参加者尝试通过 Edge 音频加入会议时失败,Webex 会通过 PSTN 重试呼叫。

用户名

出席会议的参加者的姓名。

EMAIL

出席会议的参加者的电子邮件地址。

电话号码

通过 CCA、PSTN、VolP、Edge 音频或回退加入会议的参加者的电话号码。


 

通过网络语音加入会议的参加者电话号码将显示为“NA”。

会议结束日

会议结束日期。

开始时间

会议开始时间 (GMT)。

结束时间

会议结束时间 (GMT)。

音频分钟数

每位参加者使用的总音频分钟数。

会议名称

会议的主题。

Meetings 电话报告

提供参加者在会议期间使用的不同类型音频的详细信息。您可以使用此图表来了解参加者希望连接的会议和呼叫的呼叫服务。

列名称

描述

MEETING_NUMBER

用于加入会议的 9 位或 10 位会议访问码。

CONFERENCE_ID

会议的唯一标识。

会话_类型

参加者用于加入会议的音频类型(数值)。音频类型可能为:

  • PSTN (5-9999)- 通过个人会议室加入PSTN。

  • CCA(10000 到 20000)- 通过个人会议室加入云连接音频。

  • Edge 音频(超过 20000 个)- 通过 Edge 音频加入会议的参与者。

COUNTRY_CODE

Alphabetic or numeric geographical code that the participants used to dial in to the meeting.

MEETING_NAME

会议主题。

会议_开始日期__时间

会议开始的日期和时间(GMT)。

会议_结束日期__时间

会议结束的日期和时间(GMT)。

会议_持续时间

会议持续时长(GMT)。

USER_NAME

显示参加会议的参加者的姓名。

EMAIL

参加会议的参加者的电子邮件地址。

呼叫_服务_类型

呼叫服务类型用于加入会议的会议的参加者。可能的呼叫服务类型有:

  • 国内回呼
  • 国际回呼
  • 收费呼出
  • 免费呼出
  • 国际付费呼出电话
  • 国际免费呼出
  • 网络语音
  • 高级收费

拨_入__电话号码

参加者用于拨入会议的电话号码。

回_呼_电话号码

参加者通过回呼请求加入会议的电话号码。

ANI

参加者用于呼出会议的电话号码的自动号码标识。

参加者_开始日期__时间

参加者在会议中连接音频的日期和时间(GMT)。

参加者_持续时间

参加者音频在会议中的连接时长(GMT)。

TRACKING_CODE_1-10

与用户关联的跟踪代码。


 

报告只显示默认的跟踪代码名称。

会议未来安排

此报告没有选择日期范围。自运行报告之日起 90 天内 Webex 站点上即将开始的会议。您还可以查看之前 30 天内安排的会议。

此报告显示所选 Webex 站点即将召开的会议。使用此报告可以深入了解在 Webex 站点上安排会议的用户数并了解即将召开之会议的数量和时间。这些详细信息可帮助您管理可能会影响用户的站点迁移或站点升级的时间。您还可以确定关键会议或活动,以相应地规划支持。


 

该报告中包含通过 Webex 安排的会议。如果主持人使用个人会议室邀请 URL 安排会议,则不会包含在此报告中。

列名称

描述

会议号

用于加入会议的 9 位会议访问码。

服务类型

If the meeting was scheduled as a Webex Meeting, Webex Event, Webex Training session, or Webex Webinar (WB).

主机名称

安排会议的用户的姓名。

电子邮件

安排会议的用户的电子邮件地址。

会议名称

会议的主题。

开始时间

会议开始的日期与时间 (GMT)。

结束时间

会议结束的日期与时间 (GMT)。

创建时间

安排会议的日期与时间 (GMT)。

受邀者人数

受邀加入会议的用户数。

密码设置

加入会议是否需要密码。

系列类型

会议是否为单次会议或多次会议。

有效期

会议系列结束的日期与时间 (GMT)。

上次修改日期

会议邀请最近一次更新的日期与时间 (GMT)。

例外会议

系列会议中是否有其中一个会议被重新安排在不同的时间。

Meetings 高 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. 为优化资源,Webex 在用户连续五秒达到平均系统 CPU 使用率 95% 时降低所有视频的比特率及分辨率。

您可以使用此报告帮助用户了解如何减少系统 CPU 使用率,以便获得更好的会议体验。

列名称

描述

用户电子邮件

系统 CPU 使用率较高的用户的电子邮件地址。

视频总分钟数

所选日期范围内,各用户电子邮件地址的录制视频分钟数。

CPU 使用率较高的视频分钟数

平均系统 CPU 使用率达 90% 或以上的录制视频分钟数。

CPU 使用率较高时的视频分钟数百分比

平均系统 CPU 使用率达 90% 或以上的视频分钟数百分比。

会议活动用户平均滚动

提供关于订阅中使用的许可证数量以及有多少用户在报告的日期内主持Webex许可证的详细信息。此报告仅在您的组织拥有活动 true forward 订阅时可用。

列名称

描述

日期

该时间段内的日历日期。


 

时间段定义为 30 天周期,从订阅激活当天开始,并对应您的计费周期。例如,如果您的订阅始于 2020 年 7 月 5 日,那么下一个时间段将于 30 天后(2020 年 8 月 4 日)开始。

订阅标识

订阅的唯一标识。

产品

所报告许可证的产品名称。

预分配许可证数量

为订阅和产品提供的许可证总数。

已分配许可证数量

在所报告日期分配给用户的许可证数量。

每天的唯一活动主持人

每日历日期的唯一活动主持人数。

唯一活动主持人是于报告日期内至少主持过一次 Webex 会议的人。

过去 30 天内的唯一当前会议主持人

过去 30 天内(包括当天)的唯一当前主持人的累计数量。

唯一活动主持人是于报告日期内至少主持过一次 Webex 会议的人。

90 天滚动平均唯一活动会议主持人

截至报告日期前 90 天内的唯一当前主持人的平均数量,四舍五入为最接近的整数。

如果您订阅的时间少于 90 天,则平均时间取决于订阅的激活天数。

消耗量

此数字表示用于标识 True Forward 的对齐值。IT 管理员可以在整个合同期限(订阅要发生潜在更改的时间段之前)跟踪该值。


 

该数字与 90 天滚动平均唯一活动会议主持人数相符。

会议许可证消耗报告

提供关于订阅中使用的许可证数量的详细信息。此报告仅在您的组织拥有基于活跃实用程序的计费订阅时可用。


 

*该报告不适用于政府版 Webex 组织。

列名称

描述

日期

订阅所处的时间段。时间段定义为 30 天周期,从订阅激活当天开始,并对应您的计费周期。

例如,如果您的订阅始于 2020 年 7 月 5 日,那么下一个时间段将于 30 天后(2020 年 8 月 4 日)开始。

订阅标识

订阅的唯一标识。

产品

所报告许可证的产品名称。

预分配许可证数量

为订阅和产品提供的许可证总数。

已分配许可证数量

在所报告日期分配给用户的许可证数量。

网络研讨会报告

提供在所选日期范围内主持的 Webex 网络研讨会的信息。您可以使用此报告了解网络研讨会的主持人,已安排的网络研讨会类型,以及已注册或已参加的用户数。

列名称

描述

会议标识

网络研讨会的唯一标识。

主持人标识

主持人的唯一标识。

网络研讨会主题

网络研讨会的主题。

网络研讨会类型

是安排为网络研讨会还是网络广播。

主持人电子邮件

主持人的电子邮件地址。

主持人的名

主持人的名字。

主持人的姓

主持人的姓氏。

活动日期

网络研讨会开始日期。

开始时间

网络研讨会开始的时间 (GMT)。

结束时间

网络研讨会结束的时间 (GMT)。

持续时间

网络研讨会持续的时间(分钟)。

注册者总数

网络研讨会开始前注册的用户数。

与会者总数

加入网络研讨会的用户数。

Messaging External Domain

提供关于在组织中协作的外部域和外部用户的信息。您还可以查看组织内部用户如何在外部空间中与外部域进行协作。

列名称

描述

外部域

外部域的名称。

外部用户数

组织空间中外部域中的用户数。

具有外部用户的空间数

组织中至少有一个用户(来自外部域)的空间数。例如,如果 Bob@external.com 位于您组织的 3 个不同的空间中,则此列将显示 3 作为值。

最近的阅读消息日期

来自外部域的用户在您组织的空间阅读消息的最后已知日期。

最近发送的消息日期

来自外部域的用户在您组织的空间发送消息的最后一个已知日期。

最近共享的文件日期

来自外部域的用户在您组织的空间中共享文件的上次已知日期。

最近加入的空间日期

来自外部域的用户加入组织空间的最后已知日期。

外部空间中来自组织的用户数

组织外部空间中的用户数。

与组织用户一起的外部空间数

组织用户的外部空间数。例如,如果 Alice@example.com 位于外部域的 3 个不同的外部空间中,则此列将显示 3 作为值。

消息传递 Bot 活动

此报告显示选定日期范围内每个 bot 每天进行的每项活动的数据。您选择的每个日期都有各自的一组数据。例如,如果您运行 2020 年 6 月 1 日至 2020 年 6 月 5 日的报告,则报告会显示 bot 针对报告每个日期的每项活动。

如果 bot 在特定日期内没有任何活动,则报告中不会显示该日期。


 
此报告的数据仅适用于来自您的组织的 bot。如果您的组织使用不属于您的组织的 bot,那么将不会显示这些 bot 的数据。

列名称

描述

Bot 名称

Bot 的名称。

Bot 标识

Bot 的唯一标识。

日期

Bot 活动的日期。

活动空间计数

Bot 已在其中发送消息或共享文件的空间数。

消息计数

Bot 发送的消息数。

已共享的文件

Bot 共享的文件数。

已加入的新空间

Bot 加入的空间数。

已退出的空间

Bot 离开的空间数。

Bot 用户计数

提到 Bot 的唯一用户数。

Bot 提到计数

用户提到 Bot 的次数。

消息传递用户活动

此报告显示选定日期范围内每个用户每天进行的每项活动的数据。您选择的每个日期都有各自的一组数据。例如,如果您运行 2020 年 6 月 1 日至 2020 年 6 月 5 日的报告,则报告会显示用户针对报告每个报告日期的每项活动。

如果用户在特定日期内没有任何活动,则报告中不会显示该日期。

列名称

描述

用户 ID

用户的唯一标识。

姓名

用户的名字和姓氏。

电子邮件

用户的电子邮件地址。

日期

用户活动的日期。

发送的消息

用户发送的消息数。

呼叫

由用户从 Webex 应用程序客户端发起的呼叫数和加入的会议数。

已共享的文件

用户在所有空间中共享的文件数。

空间计数

用户在其中发送消息、发起呼叫或共享文件的空间数。

已创建的新空间

用户创建的空间数。

已加入的新空间

用户加入的空间数。

已退出的空间

用户离开的空间数。

消息传递 Bot 活动摘要

此报告显示选定日期范围内每个 bot 每项活动的聚合数据。


 
此报告的数据仅适用于来自您的组织的 bot。如果您的组织使用不属于您的组织的 bot,那么将不会显示这些 bot 的数据。

列名称

描述

Bot 名称

Bot 的名称。

Bot 标识

Bot 的唯一标识。

Bot 所有者

创建 bot 的用户的姓名。

Bot 所有者的电子邮件

创建 bot 的用户的电子邮件地址。

开始日期

为报告日期范围选择的第一个日期。

结束日期

为报告日期范围选择的最后一个日期。

平均活动空间计数

Bot 其已发送消息或共享文件的平均空间数。

消息计数

Bot 发送的消息数。

已共享的文件

Bot 共享的文件数。

已加入的空间

Bot 加入的空间数。

已退出的空间

Bot 离开的空间数。

平均 Bot 用户计数

提到 Bot 的平均唯一用户数。

Bot 提到计数

用户提到 Bot 的次数。

消息传递用户活动摘要

此报告显示选定日期范围内每个用户每项活动的聚合数据。

列名称

描述

用户 ID

用户的唯一标识。

姓名

用户的名字和姓氏。

电子邮件

用户的电子邮件地址。

开始日期

为报告日期范围选择的第一个日期。

结束日期

为报告日期范围选择的最后一个日期。

发送的消息

用户发送的消息数。

呼叫

由用户从 Webex 应用程序客户端发起的呼叫数和加入的会议数。

已共享的文件

用户在所有空间中共享的文件数。

已创建的新空间

用户创建的空间数。

已加入的空间

用户加入的空间数。

已退出的空间

用户离开的空间数。

消息传递应用程序版本


 
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.

此报告没有日期范围或 Webex 站点选择,因为它会显示您组织中所有 Webex 站点的数据以及用户发送消息的最后一个已知日期。例如,如果某用户在 2020 年 3 月 1 日发送了一条消息,但自此之后尚未发送任何其他消息,报告会显示该日期使用的 Webex 应用程序客户端版本。

该报告显示用户用于登录 Webex 应用程序的所有平台上的数据。例如,如果用户同时登录 Windows 和 Mac 客户端上的 Webex 应用程序,该用户在报告中将有两个单独的条目。

列名称

描述

版本

Webex 应用程序客户端的最新检测到的版本。

平台

Webex 应用程序客户端的操作系统。

User_ID

用户的唯一标识。

电子邮件

已登录到 Webex 应用程序客户端的用户的电子邮件地址。

姓名

用户的名字和姓氏。

上次已知日期

在用户最后一次发送消息过程中,最后检测到 Webex 应用程序平台和版本号的日期。

例如,如果用户在 Webex 应用程序版本更新后未发送消息,则报告会显示该日期所用的 Webex 应用程序客户端版本。

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.

列名称

描述

用户名

First and last name of the user.

电子邮件

用户的电子邮件地址

开始时间

Time (GMT) of when the call was made.

端点

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.

呼叫质量

Media quality of the call. 如果视频和音频流的抖动在 150 毫秒以下,延迟在 400 毫秒以下,并且丢包率在 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.

音频数据包丢失 (%)

The highest value of audio packet loss for the duration of the call, in percentage.

音频延迟时间 (ms)

The highest value of audio latency for the duration of the call, in milliseconds.

纯音频

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.

呼叫 ID

呼叫的唯一标识。

Local Session ID

Unique local ID of the call.

Remote Session ID

Unique remote ID of the call.

位置

Location that the user is assigned to in Control Hub.

国家/地区

Country that the user is assigned to in Control Hub.

Connection Used

Type of connection used to connect to the call.

本地 IP 地址

Local IP address of the user.

音频编解码器

Audio media encoding and decoding format used during the call.

视频编解码器

Video media encoding and decoding format used during the call.

路径优化

Path optimization used during the call. 可用的路径优化类型包括:

  • Interactive Connectivity Establishment (ICE)—Used to enable devices to send media directly to one another, which reduces latency and bandwidth usage.
  • Private Network Connect (PNC)—Used to enable Webex Calling customers to extend their private network to the cloud over a dedicated VPN.
  • No Optimization—When neither ICE nor PNC path optimization is used.

呼叫类型

The type of call that the user made the call with. Possible values are Webex Calling or Call on Webex.

视频持续时间

用户开启视频的时间(秒)。

呼叫者

此字段显示该用户是否为发起呼叫的人。可能的值为:

  • Y - 该用户发起了呼叫。

  • N - 该用户未发起呼叫。

  • NA - 数据不可用。This can happen for calls made from and to Cisco devices.

UA 版本

The Webex Calling or Webex App desktop version of the user.

呼叫参与度报告

此报告显示用户在通过 Webex 应用程序使用 Webex 上呼叫和 Webex 呼叫应用程序拨打或接听呼叫段的数据。

列名称

描述

姓名

用户的名字和姓氏。

电子邮件

用户的电子邮件地址。

开始时间

呼叫时的时间点 (GMT)。

持续时间

呼叫持续时间(秒)。

视频持续时间

用户开启视频的时间(秒)。

端点

用于用户拨打或接听呼叫的设备或应用程序。

呼叫 ID

呼叫的唯一 ID。

呼叫者

此字段显示该用户是否为发起呼叫的人。可能的值为:

  • Y - 该用户发起了呼叫。

  • N - 该用户未发起呼叫。

  • NA - 数据不可用。对于与 Webex 设备之间的呼叫,可能会发生这种情况。

呼叫质量报告

此报告显示使用 Webex 呼叫和 Webex 桌面应用程序的用户拨打或接收呼叫的质量数据。


 

此报告中不会捕获从 Webex 应用程序和云注册设备拨打或接听呼叫的质量。

列名称

描述

姓名

用户的名字和姓氏。

电子邮件

用户的电子邮件地址。

开始时间

呼叫时的时间点 (GMT)。

持续时间

呼叫持续时间(分钟)。

端点

用于用户拨打或接听呼叫的设备或应用程序。

音频数据包丢失

平均接收音频丢包百分比。

音频延迟

平均音频往返延迟(毫秒)。

音频抖动

平均抖动(毫秒)。

视频包丢失

平均接收视频丢包百分比。

视频延迟

平均视频往返延迟(毫秒)。

UA 版本

用户的 Webex 呼叫或 Webex 桌面应用程序版本。

呼叫 ID

呼叫的唯一 ID。

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.

列名称描述
呼叫队列Name of the call queue.
位置Location assigned to the call queue.
电话号码Phone number assigned to the call queue.
分机号Extension number assigned to the call queue.
Total Hold MinsTotal number of minutes that calls were placed on hold by agents.
Avg Hold MinsAverage number of minutes that calls were placed on hold by agents.
Total Talk MinsTotal number of minutes that agents were actively talking on calls.
Avg Talk MinsAverage number of minutes that agents were actively talking on calls.
Total Handle MinsTotal number of minutes that agents spent handling calls. 处理分钟数计算为“交谈总分钟数 ” + 总保持分钟数 = 总计处理分钟数。
Avg Handle MinsAverage number of minutes that agents spent handling calls.
Total Wait MinsTotal number of minutes that callers spent waiting for the next available agent to answer the call.
Avg Wait MinsAverage number of minutes that callers spent waiting for the next available agent to answer the call.
Calls AnsweredNumber of calls answered by agents.
% Answered Calls由代理应答的呼叫的百分比。
Calls AbandonedNumber of calls where the caller hung up or left a message before an agent became available.
% Abandoned CallsPercentage of calls where the caller hung up or left a message before an agent became available.
Avg Abandoned MinsAverage number of minutes where callers hung up or left a message before an agent became available.
Abandoned MinsNumber of minutes where callers hung up or left a message before an agent became available.
呼叫总数Total number of incoming calls.
Overflow - BusyNumber of calls that overflowed because the queue limit was met.
Overflow - Timed outNumber of calls that overflowed because the wait time exceeded the maximum limit.
Calls TransferredNumber of calls that were transferred out of the queue.
Avg No. of Agents AssignedAverage number of agents assigned to call queues.
Avg No. of Agents Handling CallsAverage 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.

列名称描述
Agent/Workspace NameName of the agent or workspace.
呼叫队列Name of the call queue.
位置Location assigned to the call queue.
Total Answered CallsNumber of calls that were presented to the agent and answered by them.
退回的呼叫Number of calls that were presented to the agent but went unanswered.
Total Presented CallsNumber of inbound calls to the agent that were distributed by the call queue.
Total Talk MinsTotal number of minutes that the agent spent actively talking on calls.
Avg Talk MinsAverage number of minutes that the agent spent actively talking on calls.
Total Hold MinsTotal number of minutes that the agent put calls on hold.
Avg Hold MinsAverage number of minutes that the agent put calls on hold.
Total Handle MinsTotal number of minutes that an agent spent handling calls. 处理分钟数计算为“交谈总分钟数 ” + 总保持分钟数 = 总计处理分钟数。
Avg Handle MinsAverage number of minutes that agents spent handling calls.

自动自动与会者状态摘要

提供组织中路由到自动助理的呼叫的详细信息。

列名称描述
自动自动与会者自动自动与会者的名称(根据设置)。
Ph. No. / Extn.分配给自动自动助理的分机。
地点自动自动与会者的位置(根据设置)。
呼叫总数路由到自动自动呼叫的传入呼叫总数。
已回答由代理接听的呼叫数、用户通过呼叫转发或语音邮件应答的呼叫数。
未回答路由到代理、通过呼叫转发的用户或语音邮件但无人应答的呼叫数量。
忙碌呼叫者达到忙音的呼叫数量。
其他状态为未接听、无人应答或忙碌的呼叫数量。例如,呼叫者没有做出按键选择的实例。
已回答的 %由代理应答的呼叫的百分比。
总持续时间呼叫者与自动语音提示线路上的总时间。

自动呼叫的工作时间关键详细信息

提供在工作常规时间路由到自动呼叫的呼叫的详细信息。

列名称描述
自动自动与会者自动自动与会者的名称(根据设置)。
已按键呼叫者按下数字键盘上的按键选项
Ph. No. / Extn.分配给自动自动助理的分机。
地点自动自动与会者的位置(根据设置)。
呼叫总数路由到自动自动呼叫的传入呼叫总数。
已回答由代理接听的呼叫数、用户通过呼叫转发或语音邮件应答的呼叫数。
未回答路由到代理、通过呼叫转发的用户或语音邮件但无人应答的呼叫数量。
忙碌呼叫者达到忙音的呼叫数量。
其他状态为未接听、无人应答或忙碌的呼叫数量。例如,呼叫者没有做出按键选择的实例。
已回答的 %由代理应答的呼叫的百分比。
持续时间呼叫者与自动语音提示线路上的时间长度。
目标位置自动助理将呼叫路由到的分机。
密钥菜单分配给按下数字键盘上的键的按键菜单选项。
密钥描述键盘上的主叫方按下按键选项的描述。

在非工作时间自动自动呼叫按键详细信息

提供在工作常规时间之后路由到自动自动呼叫的呼叫的详细信息。

列名称描述
自动自动与会者自动自动与会者的名称(根据设置)。
已按键呼叫者按下数字键盘上的按键选项
Ph. No. / Extn.分配给自动自动助理的分机。
地点自动自动与会者的位置(根据设置)。
呼叫总数路由到自动自动呼叫的传入呼叫总数。
已回答由代理接听的呼叫数、用户通过呼叫转发或语音邮件应答的呼叫数。
未回答路由到代理、通过呼叫转发的用户或语音邮件但无人应答的呼叫数量。
忙碌呼叫者达到忙音的呼叫数量。
其他状态为未接听、无人应答或忙碌的呼叫数量。例如,呼叫者没有做出按键选择的实例。
已回答的 %由代理应答的呼叫的百分比。
持续时间呼叫者与自动语音提示线路上的时间长度。
目标位置自动助理将呼叫路由到的分机。
密钥菜单分配给按下数字键盘上的键的按键菜单选项。
密钥描述键盘上的主叫方按下按键选项的描述。

此报告显示详细的呼叫历史记录信息。Use this information to view trends at a high level or drill down to specific call types, for understanding the calling behavior.

列名称

描述

开始时间

This is the start time of the call, in UTC. The answer time may be slightly after this value.

应答时间

The time at which the call was answered in UTC.

持续时间

The length of the call, in seconds.

正在呼叫号码

对于传入呼叫,它是主叫方的电话号码。对于呼出,即用户的电话号码。

被叫号码

对于传入呼叫,它是用户的电话号码。对于呼出,即被叫方的电话号码。

用户

拨打或接收呼叫的用户。

呼叫线路标识

对于传入呼叫,它是主叫方的呼叫线路标识。对于呼出,它是用户的呼叫线路标识。

被叫线路标识

对于传入呼叫,它是用户的呼叫线路标识。对于呼出,它是被叫方的呼叫线路标识。

相关性标识

关联标识将同一呼叫会话的多个呼叫段关联在一起。

地点

Webex Calling录制文件的用户位置。

入站中继

入站中继可能显示于始发和终止记录中。

  • Originating—Identifies the trunk for inbound calls from an on-prem deployment integrated with Webex Calling (dial plan, unknown extension, or unknown number when org has “Call Routing between Webex Calling and premises” set to “Legacy behavior”).

  • 终止 - 当组织将“Webex Calling 和本地之间的 呼叫路由”设置为“传统行为”时,识别来自内建 PSTN 或与 Webex Calling 集成的内建部署(拨号方案、未知分机或未知号码)的入站呼叫的中继。

出站中继

始发和终止记录中可能会显示出站中继。

  • 始发 - 识别通过中继(而非路由组)路由到内建 PSTN 或与 Webex Calling(拨号方案 或未知分机)集成的内建部署路由的出站呼叫的中继。

  • 终止 - PSTN 识别到本地部署或与 Webex Calling(未知拨号方案)集成的内建部署上的呼叫的出站中继。

路由组

如果存在,该字段仅在始发记录中报告。路由组识别用于通过路由组路由到内建 PSTN 或与 Webex Calling(拨号方案 或未知分机)集成的内建部署路由组。

方向

呼叫是入站还是出站。可能的值为:

  • 终止 - 入站
  • 始发 - 出站

呼叫类型

呼叫类型。

例如:

  • SIP_MEETING—Integrated Audio for Webex Calling. A call in or callback to a Webex Meeting using a Webex Calling app or device.

  • SIP_NATIONAL—An outgoing domestic call within the user's region.

  • SIP_INTERNATIONAL—An outgoing call made to another region from the user's home region.

  • SIP_SHORTCODE—Shortcode feature/service call. Short numbers are premium or free, depending on region and service.

  • SIP_INBOUND—Inbound or Incoming call This type covers all inbound calls from PSTN or another external trunk.

  • SIP_EMERGENCY—Emergency calls. For example, dialing 911 in the US.

  • SIP_PREMIUM—Calls that use enhanced or extended Toll Premium Services, premium rate, or special rate number. Sometimes barred.
  • SIP_ENTERPRISE—Inter or intra location dialing within the same organization.

  • SIP_TOLLFREE—Toll-free based arriving (incoming) calls. Freephone numbers.

  • SIP_MOBILE—A mobile/cell call is when the user originated the call with their mobile number, or received the call when called on their mobile number.

  • UNKNOWN—Unable to determine the call type.


 
Whenever the PSTN calls are routed using a dial plan pattern, this causes a mis-categorization of the call type. In such cases, it’s not considered as a PSTN call.

示例:Using TEHO to route the call to the right country and then using the PSTN connection for the local cluster in that country.

客户端类型

用户用于拨打或接收呼叫的客户端类型(创建该记录)。

例如:

  • SIP—Calls that are made to or from a mobile phone using Webex Go or Calls from a non-Cisco client endpoint that joins via SIP.

  • WXC_客户端 - Webex Calling 应用程序

  • WXC_第三_方 - 第三方设备

  • TEAMS_WXC_客户端 - Webex 应用程序

  • WXC_DEVICE—MPP desk phone devices

  • WXC_SIP_GW — 本地网关

客户端版本

用户(该用户的客户端版本)CDR拨打或接收呼叫。

子客户端类型

If the call is TO or FROM a mobile phone using Webex Go, the Client type shows SIP, and the Sub client type shows MOBILE_NETWORK.

操作系统类型

应用程序运行的操作系统(如果可用)。

设备 (Mac)

设备的 MAC 地址(如果已知)。

型号

The device model type the user is using to make or receive the call.

例如:

  • 8865-3PCC—Cisco IP Phone 8865

  • IOS—Cisco's SIP Gateway

  • Cisco-Board 70—Cisco Webex Board series 70

  • ATA192-XX—Cisco ATA 192 Analog Telephone Adapter

  • DBS-210-3PC—Cisco IP DECT Base Station 210 Series, and so on.

已回答

Indicates whether the particular call leg was answered or not.

例如:

  • In a hunt group case, the agent who didn’t pick the call has Answered = FALSE. And the agent who picked the call has Answered = TRUE, UserType=HuntGroup.

  • Calls answered by voicemail hasAnswered = TRUE, but User Type = VoicemailRetrieval

国际国家/地区

被叫号码的国家/地区。This is only displayed for international calls.

原始原因

Call redirection reason for the original called number.

例如:

  • Unconditional—Call Forward Always (CFA) service, Group night forwarding

  • NoAnswer—The party wasn’t available to take the call. CF/busy or Voicemail/busy

  • Deflection—Indication that a call was redirected. Possible causes are Blind transfer, Auto attendant transfer, Transfer out of a Call center and so on.

  • TimeOfDay—Call scheduled period of automated redirection. CF/Selective, Group night forwarding

  • UserBusy—DND enabled or the user willingly declined the call. CF/busy or Voicemail/busy

  • FollowMe—Automated redirection to a personal redirecting service which could be Simultaneous Ringing, Sequential Ringing, Office Anywhere, or Remote Office

  • CallQueue—A Call center call to an agent or a user (a member of the call queue)

  • HuntGroup—A hunt-group-based call to an agent or a user (denotes a member of the hunt group).

  • ExplicitIdxxx—Enterprise voice portal redirection to the user’s home voice portal. The “xxx” part is the digits collected from the caller, identifying the target mailbox (Extension or DN).

  • ImplicitId—Indicates an enterprise voice portal redirection to the user’s home voice portal

  • Unavailable—To a Voicemail, when the user has no App or device

  • Unrecognized—Unable to determine the reason

  • Unknown—Call Forward by phone with no 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.

例如:

  • Deflection—Indication that a call was redirected. Possible causes could be Blind transfer, Auto-attendant transfer, Transfer out of a Call center, and so on.

  • ConsultativeTransfer—While on a call, the call was transferred to another user by announcing it first. This means that the person was asked if they're interested in taking the call and then transferred.

  • CallForwardSelective—Call Forward as per the defined schedule. It is based on factors like a specific time, specific callers or to a VM. It always takes precedence over Call Forwarding.

  • CallForwardAlways—Calls are unconditionally forwarded to a defined phone number or to a VM

  • CallForwardNoAnswer—The party wasn’t available to take the call

  • CallForwardBusy—The user willingly declined the call, or DND was enabled that then redirected the call to a defined phone number or voice mail.

  • CallForwardNotReachable—Hunt group redirection for an agent who is Not Reachable

  • CallRetrieve—The user triggered the call retrieve option to pick up a call that was parked

  • CallRecording—The User initiated the call recording service that triggered Start/Pause/Resume/Stop recording options

  • DirectedCallPickup—Indicates that this user belonged to a call pickup group who answered the call or answered when another member of the call pickup group in a location was busy

  • Executive—The user configured using the Executive/Executive assistant service who is allowed to handle calls on someone else's behalf. Also known as Boss-admin

  • ExecutiveAssistantInitiateCall—The user configured as an Executive assistant who placed or initiated the call on someone else’s (Boss admin's) behalf

  • ExecutiveAssistantDivert—The user configured as an Executive assistant who had call forwarding enabled to a defined phone number

  • ExecutiveForward—The Executive (Boss-admin) had a call forward setting enabled to a defined number. This call is triggered when an ExecutiveAssistant didn’t pick a call

  • ExecutiveAssistantCallPush—The user configured as an Executive assistant who received a call and pushed that call out (using #63) to the Executive’s (Boss-admin's) number

  • Remote Office—Indicates the call made to reach the remote location of the user

  • RoutePoint—Indicates an incoming and queued call to an agent. (For the incoming calls to the route point)

  • SequentialRing—Indicates that this user is in the list of phone numbers, which are alerted sequentially upon receiving an incoming call that matches a set of criteria.

  • SimultaneousRingPersonal—Indicates that this user was in the list of multiple destinations that are to ring simultaneously when any calls are received on their phone number. (The first destination to be answered is connected)

  • CCMonitoringBI—The indication that a Call Queue supervisor invoked silent monitoring

  • CallQueue—A call center call to an agent or a user (denotes a member of the call queue)

  • HuntGroup—A hunt group-based call to an agent or a user (denotes a member of the hunt group).

  • CallPickup—The user part of a pickup group or pickup attempted by this user against a ringing call for a different user or extension

  • CalllPark—An ongoing call was parked, assigned with a parked number (It's not the user’s phone number)

  • CallParkRetrieve—Callpark retrieval attempt by the user, either for a different extension or against the user’s own extension

  • Deflection—Indication that a call was redirected. Possible causes could be Auto attendant transfer, Transfer out of a call-center, user’s app/device redirection etc.

  • FaxDeposit—Indicates that a Fax was deposited to the Fax service

  • PushNotificationRetrieval—Push notification feature usage indication. Means that a push notification was sent to wake up the client and get ready to receive a call.

  • BargeIn—Indicates the user barged-in to someone else’s call.

  • VoiceXMLScriptTermination—Route Point feature usage indication

  • AnywhereLocation—Indicates call origination towards the single number reach (Office Anywhere) location

  • AnywherePortal—Indicates call origination towards the “user” identified by the single number reach (Office Anywhere) portal

  • Unrecognized—Unable to determine the reason

重定向原因

Call Redirection Reason for the redirecting number.

例如:

  • Unconditional—Call Forward Always (CFA) service

  • NoAnswer—The party was not available to take the call. CF/busy or Voicemail/busy

  • Deflection—Indication that a call was redirected. Possible causes could be Blind transfer, Auto attendant transfer, Transfer out of a Call center etc.

  • TimeOfDay—Call scheduled period of automated redirection. CF/Selective

  • UserBusy—DND enabled or user willingly declined the call. CF/busy or Voicemail/busy

  • FollowMe—Automated redirection to a personal redirecting service which could be Simultaneous Ringing, Sequential Ringing, Office Anywhere, or Remote Office

  • CallQueue—A Call center call to an agent or a user (a member of call queue)

  • HuntGroup—A hunt-group-based call to an agent or a user (denotes a member of the hunt group).

  • ExplicitIdxxx—Enterprise voice portal redirection to the user’s home voice portal. The “xxx” part are the digits collected from the caller, identifying the target mailbox (Extension or DN)

  • ImplicitId—Indicates an enterprise voice portal redirection to the user’s home voice portal

  • Unavailable—To a Voicemail, when user has no App or device

  • Unrecognized—Unable to determine the reason

  • Unknown—Call Forward by phone with no reason

站点主要号码

拨打或接收呼叫的用户站点的主号码。

站点时区

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.

用户类型

拨打或接收呼叫的用户类型(用户或工作空间)。

例如:

  • AutomatedAttendantVideo—Automated Attendant Video IVR group service

  • BroadworksAnywhere – Single number reach (Office anywhere) service

  • VoiceMailRetrieval—Voice Mail group service

  • HuntGroup—A hunt group based service

  • GroupPaging—One way call or group page made for target users

  • User—The direct user who made or received the call.

  • LocalGateway—A local gateway based user who made or received the call.

  • VoiceMailGroup—shared voicemail or inbound fax box for users

  • CallCenterStandard—A call queue based service

  • VoiceXML—Call added back to the Route Point queue after script termination

  • RoutePoint—Route Point call to an agent (for incoming call to the route point)

  • Place—A workspace based user who made or received the call

  • Anchor—Webex Calling user number made or received is integrated with Webex Contact Center. An "anchor" is created to facilitate the call routing flow for WxC <->WxCC

  • VirtuaLline—Call made or received by a virtual line user using the Multi-line option in Webex Calling

呼叫 ID

用于识别呼叫的 SIP 呼叫标识。您可以与 Cisco TAC 共享呼叫标识,以帮助他们如有必要找出呼叫。

Local SessionID

  • The Session ID comprises a Universally Unique Identifier (UUID) for each user-agent participating in a call

  • It can be used for end-to-end tracking of a SIP session in IP-based multimedia communication systems in compliance with RFC 7206 and draft-ietf-insipid-session-id-15.

Each call consists of four UUIDs known as Local Session ID, Remote Session ID, Final Local Session ID, and Final Remote Session ID.

  • The Local SessionID is generated from the Originating user agent

  • The Remote SessionID is generated from the Terminating user agent

  • The Final Local Session ID is value of the Local SessionID at the end of the call.
  • The Final Remote Session ID is the Remote Session ID at the end of the call.

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

用户 UUID

与呼叫关联的用户的唯一标识符。这是所有 Cisco 产品的唯一标识符。

组织 UUID

进行呼叫的组织的唯一标识符。这是整个 Cisco 的唯一标识符。

报告标识

该记录的唯一标识。可在处理记录以辅助进行重复数据处理时使用此功能。

部门标识

用户部门名称的唯一标识符。

站点 UUID

与呼叫关联的站点的唯一标识符。在 Cisco 产品中独一无二。

发布方

指示先发布呼叫的一方。可能的值为:

  • 本地 - 当本地用户先发布呼叫时使用。
  • 远程 - 当远端方先发布呼叫时使用。
  • 未知 - 当呼叫包含部分信息或无法收集关于发布呼叫的一方足够信息时使用。原因可能是强制锁定或会话审核失败。

正在重定向号码

当呼叫被重定向一次或多次后,此字段报告上次重定向的号码。这有助于识别呼叫上次重定向的人。它仅适用于呼叫情境,例如转接、呼叫转移呼叫、同时响铃等。

转移相关的呼叫标识

Transfer related call ID is used as a call identifier of the other call leg that's involved in the transfer. 您可以与 Cisco TAC 共享此标识,以帮助他们确定呼叫转移中涉及的各方。

拨打的号码

预翻译前由用户拨打的数字键盘。因此,此字段报告多种呼叫拨号可能性,例如:

  • Feature access codes (FACs) used for invoking features, such as Last Number Redial or a Call Return.

  • 被拨打的分机号和设备或应用程序拨打的键盘数字错误。

  • 当用户在拨打号码前必须拨打外部访问码(例如 9+),也会报告该访问码以及随后拨打的号码。


 
如果预翻译不起作用,则拨号数字字段包含与被叫号码字段相同的数据。

该字段仅用于发起(传出)呼叫,不能用于终止(传入)呼叫。

授权代码

为用户创建位置或站点以便用户使用的授权代码管理。通常通过帐户/授权代码或增强的“传出呼叫计划”服务进行收集。

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.

用户号

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.

本地呼叫 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—To identify the remote CDR of a call leg.
  • Transfer related call ID—To identify the call transferred leg.

远程呼叫 ID

A unique identifier that’s used to correlate CDRs and call legs with each other. This ID is used with Local call ID to identity the local CDR of a call leg.

网络呼叫 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 Network call ID.

相关呼叫 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 Local call ID field of the related call. You can use this field to correlate multiple call legs connected through other services.

呼叫结果

Identifies whether the call was set up or disconnected normally. 可能的值为:

  • Success—Call was routed and disconnected successfully. Includes Normal, UserBusy, and NoAnswer scenarios.
  • Failure—Call failed with an internal or external error.
  • Refusal—Call was rejected because of call block or timeout.

You can find more information in the Call outcome reason field.

呼叫结果原因

Additional information about the Call outcome is returned. Possible reasons are:

  • 成功
    • Normal—Call was completed successfully.
    • UserBusy—Call was a success, but the user was busy.
    • NoAnswer—Call was a success, but the user didn't answer.
  • Refusal
    • CallRejected—The call recipient did not want to receive the call and rejected the call
    • UnassignedNumber—The dialled number isn't assigned to any user or service
    • SIP408—Request timed out because couldn’t find the user in time
    • InternalRequestTimeout—Request timed out as the service could not fulfil the request due to an unexpected condition
    • Q850102ServerTimeout—Recovery on timer expiry/server timed out
    • NoUserResponse—No response from any end user device/client
    • NoAnswerFromUser—No answer from the user.
    • SIP480—Callee or called party is currently unavailable
    • SIP487—Request was terminated by bye or cancel
    • TemporarilyUnavailable—User was temporarily unavailable.
    • AdminCallBlock—Call attempt was rejected by an upstream intermediary machine, process or human
    • UserCallBlock—Call attempt from a client was rejected or blocked by the user
    • Unreachable—Unable to route the call to the desired destination.
  • 失败
    • DestinationOutOfOrder—Service request failed as the destination cannot be reached or the interface to the destination is not functioning correctly
    • SIP501—Invalid method and cannot identify the request method
    • SIP503—Service was temporarily unavailable so cannot process the request.
    • ProtocolError—Unknown or unimplemented release code.
    • SIP606—Some aspect of the session description wasn't acceptable.
    • NoRouteToDestination—No route available to the destination
    • Internal—Failed because of internal Webex Calling reasons.

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.

可能的值为:

  • Yes-PostRedirection

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.


 
The regulated entity name in region and across regions can be different.
PSTN Vendor Org IDDisplays 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 呼叫 Bob。
  • Bob 接听呼叫。
  • 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 SessionIDRemote SessionIDFinal localsessionIDFinal remote sessionID
Alice OriginatingXYXW
Bob TerminatingYXWX
Bob OriginatingZWXW
Carol TerminatingWZWX

Answer indicator with multiple redirections example:

  • Alice 呼叫 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:

Detailed call records example for Yes-Postredirection field.

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 呼叫 Bob。

  • Bob 接听呼叫。

  • 任一方结束呼叫。

Webex Calling generates two CDR data. The table below explains the CDR field names and data representations (CDR1, CDR2)

CDR field namesAlice ↔ Bob call leg
CDR1CDR2
指导ORIGINATINGTERMINATING
已回答TRUETRUE
正在呼叫号码+12814659802+442030577002
被叫号码+12814659802+442030577002
拨打的号码77002不适用
用户AliceBob
呼叫线路标识不适用Alice
被叫线路标识Bob不适用
Called IDSSE064225663310323-826219063@10.71.100.219BW064226180310323-1351546003@10.21.1.45
用户类型用户用户
相关性标识9d52512d-0e59-4cb6-9de6-bda7d5b1185e9d52512d-0e59-4cb6-9de6-bda7d5b1185e
Local SessionIDb6230eee00105000a000e069ba481bcdd0bcbad800105000a000e069ba481ba6
Remote SessionIDd0bcbad800105000a000e069ba481ba6b6230eee00105000a000e069ba481bcd
  • 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 呼叫 Bob。(Alice is the PSTN caller and Bob is Webex Calling user).

  • Bob 接听呼叫。

  • 任一方结束呼叫。

Webex Calling generates only one CDR record for Bob (CDR1=Terminating).

Alice = PSTN Caller (Originating) won’t have any CDR entries.

CDR field namesNo CDRs created for Alice PSTN caller CDR 1 for Bob Webex Calling registered user
指导-TERMINATING
已回答-TRUE
正在呼叫号码-+91638076xxxx
被叫号码-+1346298xxxx
拨打的号码-不适用
用户-不适用
呼叫线路标识-不适用
被叫线路标识-不适用
Called ID-BW101135692160523343591672@10.155.7.148
用户类型-用户
相关原因-不适用
重定向原因-不适用
正在重定向号码-不适用
相关性标识-e156cd56-f3c9-4455-bea6-174ac975cfec
Local SessionID-0816529e00105000a0000242be17dcaa
Remote SessionID-不适用

Blind Transfer Call:

盲人或无人照管的转接功能允许您将呼叫转接至备用分机或电话号码,无需等待应答或确认接收方是否可用。

  • Alice 呼叫 Bob。

  • Bob blind transfers the call to Carol. Alice goes on hold.

  • Carol answers the call.

  • Bob 清除了问题。

  • 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 namesAlice ↔ Bob call legAlice ↔ Carol call leg (post blind transfer)
CDR1CDR2CDR3CDR4
指导ORIGINATINGTERMINATINGORIGINATINGTERMINATING
已回答TRUETRUETRUETRUE
正在呼叫号码+12814659802+12814659802+12814659802+12814659802
被叫号码+442030577002+442030577002+35391111632+35391111632
拨打的号码77002不适用11632不适用
用户AliceBobBobCarol
呼叫线路标识不适用Alice不适用Alice
被叫线路标识Bob不适用Carol不适用
呼叫 IDSSE06265895710052371

1826737@10.21.0.147

BW062659522100523

2103886723@10.21.1.45

BW06265952210052

32103886723@10.21.1.45

BW062855359100523-

1346020832@10.21.1.45

用户类型用户用户用户用户
相关原因不适用挠度挠度不适用
重定向原因不适用不适用挠度挠度
正在重定向号码不适用不适用+442030577002+442030577002
转移相关的呼叫标识不适用417887153:0A417887153:0不适用
相关性标识3631b2a8-a7ba-

414b-8737-46dd30289cd6

3631b2a8-a7ba-414b-

8737-46dd30289cd6

3631b2a8-a7ba-414b-

8737-46dd30289cd6

3631b2a8-a7ba-414b

-8737-46dd30289cd6

Local SessionIDfb8ed91e00105000a

000e069ba481bcd

2247175900105000a

000e069ba481ba6

fb8ed91e00105000a

000e069ba481bcd

e54d9c6300105000a

000c4c603f1c9e8

Remote SessionID2247175900105000a0

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’s Remote Session ID. Bob’s Local Session ID = Alice’s Remote Session ID.
  • Post blind transfer, 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 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 namesAlice ↔ Bob call legBob parking the callCarol unpark / retrieving parked call
CDR1CDR2CDR3CDR4
指导ORIGINATINGTERMINATINGORIGINATINGORIGINATING
已回答TRUETRUEFALSETRUE
正在呼叫号码+12814659802+12814659802+442030577002+35391111632
被叫号码+442030577002+442030577002*6811632*8811632
拨号号码7702不适用*6811632*8811632
用户AliceBobBobCarol
呼叫线路标识不适用Alice不适用不适用
被叫线路标识Bob不适用不适用不适用
呼叫 IDSSE114440280110523-750048880@10.21.0.147BW114441007110523-418027819@10.21.1.45SSE114910189110523-234181851@10.23.0.4SSE114942533110523-1051117950@10.23.0.4
用户类型用户用户用户用户
相关原因不适用不适用CallParkCallParkRetrieve
重定向原因不适用不适用不适用不适用
正在重定向号码不适用不适用不适用不适用
转移相关的呼叫标识不适用不适用不适用不适用
相关性标识6a7156c8-fe9a-41bf-

8790-73cdf58c5f95

6a7156c8-fe9a-41bf-

8790-73cdf58c5f95

a6ccd315-99ad-42f7-

88d7-01a7f4a40699

1a4be593-5329-47ce-

9972-367a7c5452fd

Local Seccion ID6313d03900105000a

000e069ba481bcd

b7f18c4a00105000

a000e069ba481ba6

b7f18c4a00105000

a000e069ba481ba6

323ebde800105000

a000c4c603f1c9e8

Remote Session IDb7f18c4a00105000a

000e069ba481ba6

6313d03900105000a

000e069ba481bcd

不适用6313d03900105000a

000e069ba481bcd

  • Related reason = CallPark on CDR3 indicates that Bob did a CallPark.
  • Related reason = CallParkRetrieve on CDR4 indicates that Carol did the Unpark or CallParkretrieval.
  • 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 呼叫 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).

Call with multiple redirection flows table in Calling Detailed Call History report.
  • 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 约需 20 秒时间呼叫 Bob。
  • Bob 将 Alice 放在了呼叫保持状态,而她将呼叫转接至 Charlie,在 Charlie 应答转接的呼叫前约需 3 秒。
  • Bob 消失,Alice 结束与 Charlie 的通话,约需 23 秒。

根据上例,呼叫总时长为 46 秒。

For reference, the spreadsheet captures the Blind Transfer Call Details:

呼叫详细信息电子表格中显示“盲人转移”功能的示例

 

某些记录报告特殊功能。For example, records tagged with relatedReason=PushNotificationRetrieval indicates that a push notification was sent to wake up the client and get ready to receive a call.

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描述
呼叫队列Name of the call queue.
位置Location assigned to the call queue.
Phone NO.Phone number assigned to the call queue.
分机号Extension number assigned to the call queue.
Total Hold TimeTotal time that calls were placed on hold by agents.
Avg Hold TimeAverage time that calls were placed on hold by agents.
Total Talk TimeTotal time that agents were actively talking on calls.
Avg Talk TimeAverage time that agents were actively talking on calls.
Total Handle TimeTotal time that agents spent handling calls. Handle time is calculated as Total talk time + Total hold time = Total handle time.
Avg Handle TimeAverage time that agents spent handling calls.
Total Wait TimeTotal time that callers spent waiting for the next available agent to answer the call.
Avg Wait TimeAverage time that callers spent waiting for the next available agent to answer the call.
Answered CallsNumber of calls answered by agents.
% Answered Calls由代理应答的呼叫的百分比。
Abandoned CallsNumber of calls where the caller hung up or left a message before an agent became available.
% Abandoned CallsPercentage of calls where the caller hung up or left a message before an agent became available.
Avg Abandoned TimeAverage time where callers hung up or left a message before an agent became available.
Total Abandoned TimeTime where callers hung up or left a message before an agent became available.
呼叫总数Total number of incoming calls.
Calls OverflowedNumber of calls that overflowed because the queue limit was met.
Calls Timed OutNumber of calls that timed out because the wait time exceeded the maximum limit.
Calls TransferredNumber of calls that were transferred out of the queue.
Avg No. of Agents AssignedAverage number of agents assigned to call queues.
Avg No. of Agents Handling CallsAverage 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描述
Agent NameName of the agent.
呼叫队列Name of the call queue.
位置Location assigned to the call queue.
Total Answered CallsNumber of calls that were presented to the agent and answered by them.
退回的呼叫Number of calls that were presented to the agent but went unanswered.
Total Presented CallsNumber of inbound calls to the agent that were distributed by the call queue.
Total Talk TimeTotal time that an agent spent actively talking on calls.
Avg Talk TimeAverage time that an agent spent actively talking on calls.
Total Hold TimeTotal time that an agent put calls on hold.
Avg Hold TimeAverage time that an agent put calls on hold.
Total Handle TimeTotal time that an agent spent handling calls. Handle minutes are calculated as Total talk time + Total hold time = Total handle time.
Avg Handle TimeAverage time that an agent spent handling calls.

会议室和桌面详细信息

使用该报告以查看组织中每个设备的详细信息及其用途。Look at the Total Hours Used column to quickly pinpoint underutilized devices. 它显示选定日期范围内设备的总体使用情况。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.

列名称

描述

设备标识

供管理员使用的内部唯一标识符。

设备类型

设备型号。

分配给

该设备被分配到的地点或用户的名称。如果该字段为空,则表示该设备已从您的组织中删除。

标记

在 Control Hub 设备页面上显示分配给设备的标记。

IP 地址

设备在线时的最新已知 IP 地址。

Mac 地址

设备的媒体访问控制地址。

最新的已知状态

最近 24 小时内的设备在线状态。

已使用总小时数

选定日期范围内的总体使用情况

呼叫

The number of hours the device was used for a call over the selected date range.

有线本地显示

The number of hours the device was used for a wired local display over the selected date range.

无线本地显示

The number of hours the device was used for a wireless local display over the selected date range.

白板

The number of hours the device was used for whiteboarding over the selected date range.

数字标牌

The number of hours the device was used for digital signage over the selected date range.

USB 透传

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 许可证报告

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. 您选择的每个日期都有各自的一组数据。例如,如果您运行 2020 年 6 月 1 日至 2020 年 6 月 5 日的报告,则报告会显示报告每个日期的数据。

列名称

描述

Webex 组织标识

报告所属的 Control Hub 组织的唯一标识。

日期

录制数据的日历日期。每天有一条记录。

设备 24 小时

在该日期的过去 24 小时内使用 VIMT 的唯一设备计数。

设备过去 30 天

在该日期的过去 30 天内使用 VIMT 的唯一设备滚动计数。

唯一设备 90 天滚动平均

在该日期的过去 90 天内使用 VIMT 的唯一设备滚动平均计数。

VIMT 使用情况报告

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.

列名称

描述

Teams 会议标识

Microsoft Teams 会议的唯一标识。

设备名称

用于加入 Microsoft Teams 会议的设备名称。

设备 URL

The URL associated with the device.

设备加入时间

设备使用 VIMT 加入 Microsoft Teams 会议的时间(UTC+0)。

设备断开连接时间

设备从 Microsoft Teams 会议断开连接的时间。

设备 SIP URI

与会话发起协议关联的 sip(SIP)地址。

Teams 租户标识

Microsoft Teams 客户端中用户的唯一标识。

设备加入呼叫的日期

使用设备使用 VIMT 加入 Microsoft Teams 会议的日期。

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描述
设备名称Name of the device.
Device type设备型号。
位置Location assigned to the device.
Hours in Call modeNumber of hours (in two decimal points) the device spent in Call mode.
Power consumption in Call modeHow much energy the device consumed in watts while in Call mode.
Hours in Idle modeNumber of hours (in two decimal points) the device spent in Idle mode.
Power consumption in Idle modeHow much energy the device consumed in watts while in Idle mode.
Hours in Halfwake modeNumber of hours (in two decimal points) the device spent in Halfwake mode.

 
This data doesn't apply to Desk phones.
Power consumption in Halfwake modeHow much energy the device consumed in watts while in Halfwake mode

 
This data doesn't apply to Desk phones.
.
Hours in Display Off modeNumber of hours (in two decimal points) the device spent in Display Off mode.
Power consumption in Display Off modeHow much energy the device consumed in watts while in Display Off mode.
Hours in Networked Standby modeNumber of hours (in two decimal points) the device spent in Networked Standby mode.

 
This data doesn't apply to Desk phones.
Power consumption in Networked Standby modeHow much energy the device consumed in watts while in Networked Standby mode.

 
This data doesn't apply to Desk phones.
Total power consumptionHow much energy the device consumed in kilowatts while in all of the modes combined.
Hours in Deep Sleep modeNumber of hours (in two decimal points) the phone spent in Deep Sleep mode.

 
This data only applies to Desk phones.
Power consumption in Deep Sleep modeHow much energy the phone consumed in watts while in Deep Sleep mode.

 
This data only applies to Desk phones.

加入用户激活和许可证详细信息报告

此报告显示如何将用户添加到您的组织以及如何为其分配许可证的详细信息。


 

*该报告不适用于政府版 Webex 组织。

列名称

描述

姓名

已添加用户的名字和姓氏。

电子邮件

用户的电子邮件地址。

管理员姓名

添加用户的管理员的名字和姓氏,如适用。

管理员电子邮件

添加用户的管理员的电子邮件地址,如适用。

邀请已发送 (GMT)

向用户发送邀请的日期与时间,如适用。

加入方式

用于将用户添加到 Control Hub 的方法。可能的值为:

  • API—User was added with an API.
  • Manual—User was manually added in Control Hub.
  • CSV—User was added with a CSV file.
  • Dirsync—User was added with Cisco Directory Connector.
  • Convert—User was added with the claim process.
  • Sideboard—User was added from the Webex App.
  • Self_signup—User was added with the self-sign up process.
  • BWKS_prov_API—User was added with the Webex for Broadworks provisioning API.
  • People_API—User was added with the Webex People API.
  • Site_conversion—User was added with the Site admin to Control Hub update process.
  • Org_license_template—User was added with the organization license template.
  • Group_license_template—User was added with the organization group license template.
  • External_admin_invite—User was added by an external admin in the organization.
  • Other—User was added with other methods not described.

许可证分配方法

用于将许可证分配给用户的方法。这些方法包括:

  • 手动 - 管理员手动将许可证分配给用户。

  • 自动 - 自动将许可证分配给用户的许可证模板。

许可证

分配给该用户的许可证名称。

许可证分配状态

是否已成功将许可证分配给用户。

激活状态

如果用户首次登录 Webex 应用程序,用户的激活状态将显示为已激活。

尚未登录应用程序的用户Webex为待 批准

激活日期

用户状态变更为活跃的日期。

用户 ID

用户的唯一标识。

管理员 ID

添加用户的管理员的唯一 ID。

企业协议报告

提供订阅中使用的许可证数量相关信息。此报告仅在您的组织拥有活动 true forward 订阅时可用。

列名称

描述

时间段

订阅所处的时间段。时间段定义为 30 天周期,从订阅激活当天开始,并对应您的计费周期。

例如,如果您的订阅始于 2020 年 7 月 5 日,那么下一个时间段将于 30 天后(2020 年 8 月 4 日)开始。

日期

该时间段内的日历日期。

订阅标识

订阅的唯一标识。

产品

所报告许可证的产品名称。

预分配许可证数量

为订阅和产品提供的许可证总数。

已分配许可证数量

在所报告日期分配给用户的许可证数量。

消耗量

此数字表示用于标识 True Forward 的对齐值。IT 管理员可以在整个合同期限(订阅要发生潜在更改的时间段之前)跟踪该值。


 

此数量是根据订阅中具有较高预分配许可证数量或已分配许可证数量的产品计算。

例如,对于某一订阅,Calling 有 500 个已分配许可证数量,而 Meetings 有 600 个已分配许可证数量,那么该订阅的“消耗量”将为 600。

您可以通过重新排序或删除列来自定义现有模板,以查看想要关注的数据。例如,您可以创建自定义的 Meetings Attendees 报告(聚焦特定位置或特定操作系统的参加者)或自定义的呼叫质量报告(聚焦音频或视频媒体质量而非两者)。Custom templates appear in their own section,and are tagged so you can easily identify them.

Custom reports section in Control Hub

某些模板无法进行自定义,某些模板需要某些列。如果在您自定义模板时无法删除模板,您可以确定模板需要哪些列,如下图所示。


 

每个管理员可以创建多达 50 个自定义模板,而且只有您可以查看您创建的自定义模板。

您最多可创建 50 个自定义模板,且只有您可以查看自定义模板。其他管理员可自行创建一组多达 50 个自定义模板。


 
自定义模板创建后不可编辑。
1

Sign in to Control Hub and go to Reports > Templates.

2

单击 新模板

出现全屏窗口。要退出该窗口,您可以单击 取消 或完成自定义模板的创建。创建自定义模板屏幕
3

在模板 部分,选择要自定义的模板,输入自定义模板的名称,然后添加描述。

4

在数据 部分,您可以选择:

  • Filter data—Select the filters that you want the report to only show data for. For example, in the Meetings Details report, if you select IS_SHARING = YES as a filter, then the report will only show data for meetings where someone shared their screen. In the Call Queue Stats report, if you select Location = Toronto, then the report will only show data for call queues based in Toronto.
  • Customize columns—Select which columns you want to reorder to the customized template. 某些模板的列无法删除。
5

单击 保存模板

当您删除自定义模板时,该模板的任何自动安排也将被删除。您仍保留之前生成的自定义模板报告。

1

Sign in to Control Hub and go to Reports > Templates.

2

单击要 删除的自定义模板旁的更多按钮。

3

选择 删除 ,然后确认您的选择。

1

Sign in to Control Hub and go to Reports > Templates.

2

Click on a report template that you want to generate.

3

Click Generate report.

Generate report UI in Control Hub
4

选择生成报告:

  • Now—Select which date range you want to view the data for.
  • Daily—Select which days you want to generate the report automatically. 报告包含前一天选择的数据。
  • Weekly—Select the day that you want to generate the report automatically every week. 该报告包含从选择日期开始的最近 7 天的数据。
  • Monthly—Select the day that you want to generate the report automatically every month. 该报告包含从选择日期开始的最近 30 天的数据。
5

如果您希望报告已 就绪可供下载,请选中通过电子邮件通知我复选框。

6

根据报告的计划,选择生成报告计划报告

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.


 

该列表最多只能包含 50 份报告。系统将在报告少于50份时运行未来计划报告。

1

Sign in to Control Hub and go to Reports > Report list.

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.

如果您想暂停自动运行报告,可以禁用报告。

1

Sign in to Control Hub and go to Reports > Scheduled jobs.

2

操作下,单击更多更多内联图标,然后选择禁用

1

Sign in to Control Hub and go to Reports > Scheduled jobs.

2

操作下,单击更多更多内联图标,然后选择删除

3

Select Delete

您可以使用经典报告来查看组织中 Webex Meetings、Webex Events(经典版)、Webex Training 和 Webex Support 服务的综合统计信息。监控服务的使用情况、活动与课程的出席情况,并支持活动,以便您确定如何构建一个更有效的组织。

阅读此文章,了解有关这些报告的更多内容。