UC Analytics Dashboards and Wallboards

UC Analytics turns Call Telemetry reports into dashboards your UC team can monitor, arrange, and share. Put dropped calls beside voice quality, compare queue performance with call volume, or keep phone registration and CUBE health on a full-screen wallboard. Each dashboard is a saved 12-column layout built from report charts, tables, KPI cards, and multi-panel widgets.

Loading product walkthrough…

What You Can Build

The same dashboard can serve three different jobs:

Use	What it is	Typical audience
Dashboard	An editable, saved page of related reports and live gauges	UC administrators and voice engineers
Wallboard	A dashboard shown in a full-screen browser with automatic refresh	NOC, service desk, or queue supervisor
Shared view	A token-scoped, read-only copy of one dashboard that opens without a login	Team monitors and approved viewers

A wallboard is not a separate report type. Build a dashboard, set the time range and refresh interval, then show the full grid in a full-screen browser. You can also expand one widget when a single chart or table needs the screen.

Start With the Question

Useful dashboards keep related evidence together. Common examples include:

• Calling health: call attempts, failed or dropped calls, route activity, and recent failure detail
• Voice quality: average MOS, poor-call rate, jitter, packet loss, and the devices or locations with the weakest results
• Phone and infrastructure health: registration state, CUBE health, trunk utilization, media resources, and location bandwidth
• Queue performance: offered, answered, abandoned, wait time, and agent or hunt-pilot results
• Cross-platform quality: Cisco CMR and Microsoft Teams quality panels on the same dashboard when both sources are configured

The dashboard should help a viewer compare facts or choose the next report to open. A page filled with unrelated charts is harder to use than a smaller, purpose-built board.

How Dashboard Data Works

Report widgets use the same report templates and QuerySpec engine as Report Builder. When the report, filters, date range, and timezone match, the dashboard and Report Builder are two presentations of the same query result.

You can create a widget from:

• a supported report template from the generated report catalog
• a saved report
• a composite preset or a custom group of report and live-gauge panels

Linking a widget to a saved report keeps its dimensions, metrics, and non-date filters connected to that saved definition. The dashboard's date range and timezone still control the view. An anonymous shared view uses the widget configuration stored on the dashboard because it cannot open the owner's saved report.

Refresh is not the same as source freshness

Automatic refresh reruns a widget. The age of the result still depends on the source: CDR and CMR file ingestion, Microsoft Graph snapshots, report rollups, or a live CUCM gauge. Check the source and its last update before describing a wallboard as real time.

Widget Types

Widget	Best for
Chart	Trends, comparisons, distributions, and report-provided chart views
Table	Exact values, ranked lists, and recent call or device rows
KPI card	One important count, average, rate, or threshold value
Composite	Several related panels inside one tile, such as MOS, poor-call rate, a trend, and a worst-device list

Composite widgets can contain stat, sparkline, list, chart, table, gauge, progress, and threshold-driven panels. Available presets on the 0.8.7 stable release include:

• Dropped / 911 Calls
• Live Operations
• CUBE / XCC Health
• Voice Quality / CMR Fleet
• Teams Call Quality
• Teams Call Queue Live
• Teams Queue SLA & Staffing
• Teams Agent Performance
• Teams Auto Attendant
• Cross-Platform Call Quality

Presets are starting points. They still require the named data source, license, and recent data. If a panel does not apply to your environment, remove it or replace it with a report your team uses.

Requirements

• Call Telemetry Server Appliance 0.8.7 or later for the composite widgets and presets described on this page
• Advanced license for one custom dashboard, or Premium for unlimited dashboards and public share links; Demo and Beta licenses also enable the feature
• cdr_reports or full_admin role when organization RBAC is enabled
• CDR integration for call-history reports
• CMR collection for MOS, jitter, latency, and packet-loss reports
• Optional CUCM, CUBE/XCC, or Microsoft Teams connections for their respective panels

Create a Dashboard

1. Go to Reporting and Analytics > UC Analytics Dashboard.
2. Select New.
3. Enter a name that describes the job, such as Voice Quality Review or NOC Calling Health.
4. Select Create.
5. Choose Set Default if this dashboard should open first for the organization.

Use the page menu to rename, duplicate, export, share, or delete the selected dashboard.

Add a Report Widget

1. Select Edit, then Add Widget.
2. Choose a chart, table, KPI card, or composite widget.
3. Select a report template, saved report, or composite preset.
4. For a report widget, confirm the dimensions and metrics.
5. Choose the report's chart view or a table. Chart widgets use the chart views supplied by that report; they are not arbitrary chart types disconnected from the query.
6. Enter a clear title, choose an initial grid size, and set a widget refresh override only when needed.
7. Add the widget and confirm that it contains data for the dashboard's current period.

Not every report belongs on an automatic refresh loop

Dashboard refresh is designed for supported aggregate-backed reports. Detailed raw-call lists must stay bounded and are treated as drill-down panels. If the server rejects a high-volume report for dashboard refresh, choose an aggregate summary or open the detailed report on demand.

Arrange the Dashboard

1. Select Edit.
2. Drag a widget by its header.
3. Resize it from the lower-right handle.
4. Keep neighboring charts and tables visible; a wider widget should not push another report outside the grid.
5. Select Done to save the layout.

The grid has 12 columns. A half-width widget is normally six columns; a full-width trend or table uses twelve. Layout updates use optimistic locking so one editor does not silently overwrite a newer layout from another session.

Set Time, Timezone, and Refresh

Use the dashboard toolbar to choose the date range, timezone, and automatic refresh interval. The UI offers refresh intervals from 30 seconds to 30 minutes, or Off.

• The dashboard interval is the default for its widgets.
• A widget can override that interval.
• A dashboard date range replaces date filters from a linked saved report; other saved-report filters remain.
• Widgets outside the visible viewport wait to query until they are visible.

There are two refresh paths:

Path	Behavior
Report refresh	Polls an aggregate-backed report on the configured interval; freshness depends on ingestion and rollup cadence
Live gauge	Uses authenticated CUCM/CUBE gauge sources with a shared sampler and Phoenix channel; the minimum backend interval is 15 seconds

Live gauge sources include active calls, hunt-pilot queue depth, device registration, trunk utilization, CUBE health, gateway channels, media resources, and location bandwidth when the required integration is available.

Investigate From a Widget

Use a widget's menu to:

• expand the widget to a full-screen dialog
• switch between chart and table when the report supports both
• open the query in Report Builder
• use configured table-row actions to open call-path or other detail drawers

The dashboard organizes evidence; it does not claim a root cause on its own. Use the linked report or call detail to investigate the calls behind a count, trend, or threshold.

Run a Wallboard

1. Build a dashboard for one audience and purpose.
2. Set a clear time range such as Today.
3. Choose a refresh interval that matches the source. For snapshot-polled Teams queue data, one minute is a practical floor; label the board accordingly.
4. Press F11 or use the browser's full-screen command to show the entire dashboard. Use a widget's full-screen action when one panel should fill the display.

Keep the browser session authenticated if the wallboard contains live gauge panels.

Shared Wallboard Links

Dashboard sharing requires Premium, Demo, or Beta licensing.

1. Open the dashboard menu and select Share.
2. Enable public sharing.
3. Copy the generated URL.
4. Send it only to the intended viewers.

The shared page removes the main application navigation and allows no edits. Its token is scoped to one dashboard; widget results are capped at 500 rows and public requests are limited to 60 per minute per IP address.

Report-backed widgets continue to refresh in the shared view. Authenticated live-gauge panels do not: the public page has no access to the live gauge batch endpoint or Phoenix channel and shows those panels as unavailable. Build a report-backed board when anonymous viewing is required.

• Disable immediately revokes access while preserving the token for later re-enablement.
• Regenerate creates a new URL and immediately invalidates the old token.

Shared-link creation, access, disablement, and regeneration are recorded in the user activity audit trail.

Export a Dashboard

Choose Export PDF from the dashboard menu to capture the arranged widgets and their current data. Use PDF for a point-in-time record; use a wallboard or shared link when the audience needs refreshed results.

Licensing

Tier	Custom dashboards	Public share links
Premium	Unlimited by default	Yes
Advanced	1 by default	No
Demo / Beta	Enabled; token limits may override defaults	Yes
Community / Essentials / Standard	Not available	No

Related Guides

• Report Examples
• Report Builder
• Saved and Scheduled Reports
• Call Quality Reports
• CUBE XCC Analytics