# Status

Operational status guide for call history, queues, peers, conferences, faxes, reports, voicemail, balances, statistics, and realtime monitoring.

# Call History

Call History status and operational review.

# Overview

The **Call History** chapter documents the tenant call-history screens used to review completed and attempted calls. The screenshots below were captured from the live interface with fictional call data in the Canistracci Oil tenant.

Open **Status > Call History** and confirm that the tenant selector at the top of the screen points to the tenant you want to inspect. Call History is a diagnostic area: use it to search, export, listen to recordings, and open related log pages. Change configuration objects from their configuration pages instead of editing status data.

## Complete Call History

**Complete Call History** shows the detailed call-detail view. It is the best view for troubleshooting because it exposes individual call legs, linked IDs, destination context, final landing information, provider account, cost fields when billing is enabled, and optional transcript, summary, and sentiment columns.

<figure id="bkmrk-complete-call-histor-2">![Complete Call History with fictional call data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/yeAcomplete-call-history.png)<figcaption>Complete Call History with fictional call data.</figcaption></figure><table id="bkmrk-areahow-to-use-it-fi"><thead><tr><th>Area</th><th>How to use it</th></tr></thead><tbody><tr><td>Filters</td><td>Use the date range, source, destination, and additional filters before reviewing or exporting. Narrow filters keep the grid responsive and make exports easier to audit.</td></tr><tr><td>Columns</td><td>Select **Columns** to hide, show, and reorder fields. The browser stores the column selection locally, so each administrator can keep a personal troubleshooting layout.</td></tr><tr><td>Rows</td><td>Each row represents a call-detail entry or relevant call leg. Use linked ID, unique ID, destination, disposition, duration, and where-landed fields to follow how the call moved through the PBX.</td></tr><tr><td>Recordings</td><td>Recording icons open the recording player when recordings are available. The player can expose main, transmit, and receive recordings, plus copy, download, or delete controls depending on permissions.</td></tr><tr><td>View switch</td><td>Select **Simple View** to move from detailed call legs to the summarized call-history view.</td></tr></tbody></table>

## Simple Call History

**Simple Call History** groups call data into an easier operational view. It is useful for help-desk work, quick call searches, and user-facing explanations because it focuses on date, direction, caller ID, dialed number, disposition, duration, and talk time.

<figure id="bkmrk-simple-call-history--1">![Simple Call History with fictional call data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/4qbsimple-call-history.png)<figcaption>Simple Call History with fictional call data.</figcaption></figure><table id="bkmrk-areahow-to-use-it-su"><thead><tr><th>Area</th><th>How to use it</th></tr></thead><tbody><tr><td>Summary rows</td><td>Each row is a simplified call record. Expand a row to inspect the underlying detailed call legs without leaving the simple view.</td></tr><tr><td>Direction and disposition</td><td>Use direction to distinguish inbound, outbound, local, and active calls. Use disposition to quickly find answered, missed, failed, busy, or abandoned calls.</td></tr><tr><td>Columns</td><td>Use **Columns** to keep the grid compact for operational staff while still allowing hidden troubleshooting fields when needed.</td></tr><tr><td>Multi-select</td><td>Enable multi-select when you need to run actions such as blacklist or transcription scheduling on more than one selected call.</td></tr><tr><td>View switch</td><td>Select **Complete View** when you need call-leg detail, linked IDs, provider data, where-landed data, or billing-related columns.</td></tr></tbody></table>

## Sentiment Analysis

When transcription and sentimental analysis are enabled, recorded calls can expose AI-generated sentiment details from the transcript view. The detailed Call History grid can show the sentiment score and brief analysis, while the transcript page shows the sentiment and tone timeline, speaker-role detection, and evidence rows.

<figure id="bkmrk-sentiment-and-tone-t">![Sentiment and tone timeline with fictional call data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/sentiment-analysis-graph.png)<figcaption>Sentiment and tone timeline with fictional call data.</figcaption></figure><table id="bkmrk-elementmeaning-overa"><thead><tr><th>Element</th><th>Meaning</th></tr></thead><tbody><tr><td>Overall score</td><td>A single sentiment score returned by the configured AI prompt. The default prompt uses a negative-to-positive scale so supervisors can quickly find calls that need review.</td></tr><tr><td>Customer sentiment arc</td><td>Plots how the customer sentiment changes across the call. This is useful when the call starts negatively but recovers, or when a positive call degrades over time.</td></tr><tr><td>Agent sentiment and tone</td><td>Plots the agent tone across the same timeline. Tone labels such as calm, informative, empathetic, confident, or tense help explain why the call moved in a given direction.</td></tr><tr><td>Speaker roles</td><td>Shows which speaker was identified as customer or agent, the party role, confidence, and the evidence used for the decision.</td></tr><tr><td>Evidence rows</td><td>Shows time range, party, speaker, sentiment score, tone or emotion, and the transcript evidence supporting each point. Selecting a row in the application highlights the closest transcript segment.</td></tr></tbody></table>

<figure id="bkmrk-sentiment-evidence-a">![Sentiment evidence and speaker-role tables with fictional call data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/sentiment-analysis-details.png)<figcaption>Sentiment evidence and speaker-role tables with fictional call data.</figcaption></figure>## Changing the View

You can change views directly from the Call History page by selecting **Simple View** or **Complete View**. The administrator can also choose the default view from **Admin &gt; Settings**, in the **Call History Theming** section.

<figure id="bkmrk-admin-settings-call-">![Admin Settings Call History Theming section showing the default Call History view controls.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/kYDadmin-settings-call-history-theming.png)<figcaption>Admin Settings Call History Theming section showing the default Call History view controls.</figcaption></figure><table id="bkmrk-settingmeaning-call-"><thead><tr><th>Setting</th><th>Meaning</th></tr></thead><tbody><tr><td>Call History view</td><td>Controls the default Call History view. **Show all legs** opens the full detailed view, **Show only relevant entries** keeps a compact detailed view, and **Simple view** opens the summary view by default.</td></tr><tr><td>Call History easy filters</td><td>Shows or hides the top filter form with date, source, destination, and related quick filters.</td></tr><tr><td>Call History mobile view</td><td>Allows MiRTA PBX to open the mobile-optimized call-history view automatically on smartphones.</td></tr><tr><td>Call History destination view</td><td>Controls whether the destination column shows dialed digits, expanded digits, or both.</td></tr><tr><td>Call History row count</td><td>Controls how aggressively the system counts matching rows. Approximate or skipped counts can improve performance on large call-history tables.</td></tr><tr><td>Call History number of rows preloaded</td><td>Sets how many rows are loaded initially when the page opens.</td></tr><tr><td>Call History wherelanded preprocessing</td><td>Schedules preprocessing of where-landed data so the Call History page can open faster when that calculation is expensive.</td></tr></tbody></table>

## Linked Pages and Actions

The following controls can appear in Complete Call History and Simple Call History depending on tenant settings, installed modules, and the permissions of the logged-in administrator.

<table id="bkmrk-linked-page-or-actio"><thead><tr><th>Linked page or action</th><th>Explanation</th></tr></thead><tbody><tr><td>Complete View / Simple View</td><td>Switches between the detailed call-leg grid and the summarized call-history grid. This changes the current view only; the default view is configured in Admin Settings.</td></tr><tr><td>Call Steps</td><td>Opens the chronological call-step view for the selected call. Use it to understand transfers, bridges, queue handling, dial attempts, hangups, and other call events.</td></tr><tr><td>Recording Player</td><td>Opens from recording icons in the grid. It plays available recordings and may offer copy-link, download, delete, or alternate-channel recording controls according to permissions.</td></tr><tr><td>CSV Export and XLS Export</td><td>Exports the current prepared dataset. Filter first, then export, so the downloaded file contains only the calls you intend to review.</td></tr><tr><td>Blacklist callerid</td><td>Adds the selected caller ID to the tenant blacklist with a reason based on the call date. Use it only after confirming the number should be blocked.</td></tr><tr><td>Call Hold Logs</td><td>Opens hold-event history, including extension, start, end, duration, party held, unique ID, and linked ID. Use it to investigate long holds and caller experience.</td></tr><tr><td>Parked Call Logs</td><td>Opens parking history, including extension, parking space, parking lot, duration, party, and unique ID. Use it to verify parking-lot workflows.</td></tr><tr><td>Scheduled Call Logs</td><td>Opens scheduled-call history, including the target number, not-before time, attempts, confirmation, DTMF received, status, and sender.</td></tr><tr><td>AI Logs</td><td>Opens generative AI call logs with caller ID, start and end time, duration, talk time, token counts, and unique ID. Use it to audit AI-assisted call handling.</td></tr><tr><td>Voice Service Logs</td><td>Opens voice-service usage logs for text-to-speech, speech-to-text, and similar services. It shows provider, unique ID, words, duration, characters, tokens, and language.</td></tr><tr><td>Call Privacy/Screening</td><td>Opens the privacy and screening status page for caller IDs. Administrators with permission can review or adjust the action assigned to screened callers.</td></tr><tr><td>AI Processing</td><td>Opens the queue of transcript, summary, and sentiment processing jobs, including action, unique ID, first check, last check, note, and notification email.</td></tr><tr><td>Transcribe call</td><td>Schedules transcription, summarization, or sentiment analysis for selected recorded calls. The dialog can also send a notification email when processing is complete.</td></tr><tr><td>Alarms Received</td><td>Appears when alarm controls are enabled. It opens the received-alarm history related to alarm receiver handling.</td></tr></tbody></table>

## Operational Notes

- Use Complete Call History for troubleshooting and Simple Call History for quick operational lookup.
- Filter by date and tenant before exporting or scheduling actions on calls.
- Recording, export, deletion, billing, transcription, and AI actions depend on permissions and enabled features.
- When the grid feels slow on large deployments, review the Call History row count, preloaded rows, easy filters, and where-landed preprocessing settings.

# SMS History

SMS History status and operational review.

# Overview

The **SMS History** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; SMS History**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Queue History

Queue History status and operational review.

# Overview

The **Queue History** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Queue History**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# IVR Logs

IVR Logs status and operational review.

# Overview

The **IVR Logs** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; IVR Logs**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Response Path Logs

Response Path Logs status and operational review.

# Overview

The **Response Path Logs** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Response Path Logs**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Peers

Peers status and operational review.

# Overview

The **Peers** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Peers**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Conferences

Conferences status and operational review.

# Overview

The **Conferences** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Conferences**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Queues

Queues status and operational review.

# Overview

The **Queues** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Queues**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Faxes

Faxes status and operational review.

# Overview

The **Faxes** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Faxes**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Reports

Reports status and operational review.

# Overview

The **Reports** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Reports**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Voicemail Messages

Voicemail Messages status and operational review.

# Overview

The **Voicemail Messages** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Voicemail Messages**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Mail Messages

Mail Messages status and operational review.

# Overview

The **Mail Messages** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Mail Messages**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Balance

Balance status and operational review.

# Overview

The **Balance** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Balance**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Stats

Stats status and operational review.

# Overview

The **Stats** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Stats**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Statsboards

The **Statsboards** status page is used to inspect operational state and historical records without changing normal tenant configuration.

How to Use

1. Open **Status &gt; Statsboards**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.

# Total Inbound Duration

The **Total Inbound Duration** statsboard report adds a reusable card for **Total inbound duration**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-total-inbound-durati">![Total Inbound Duration example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/6Putotal-inbound-duration.png)<figcaption>Total Inbound Duration example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Total inbound duration</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Sum sc\_duration for Simple CDR rows where sc\_direction is IN.

## When To Use

Useful for seeing how much inbound traffic the tenant handled.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Total Outbound Duration

The **Total Outbound Duration** statsboard report adds a reusable card for **Total outbound duration**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-total-outbound-durat">![Total Outbound Duration example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/bP7total-outbound-duration.png)<figcaption>Total Outbound Duration example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Total outbound duration</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Sum sc\_duration for Simple CDR rows where sc\_direction is OUT.

## When To Use

Useful for tracking outbound trunk usage and customer-callback workload.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Average Inbound Duration

The **Average Inbound Duration** statsboard report adds a reusable card for **Average inbound duration**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-average-inbound-dura">![Average Inbound Duration example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/DYFaverage-inbound-duration.png)<figcaption>Average Inbound Duration example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Average inbound duration</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Average sc\_duration for inbound Simple CDR rows.

## When To Use

Helps spot days where inbound calls become longer than usual.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Average Outbound Duration

The **Average Outbound Duration** statsboard report adds a reusable card for **Average outbound duration**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-average-outbound-dur">![Average Outbound Duration example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/WhQaverage-outbound-duration.png)<figcaption>Average Outbound Duration example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Average outbound duration</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Average sc\_duration for outbound Simple CDR rows.

## When To Use

Helps compare outbound follow-up duration across periods.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Total Talk Time

The **Total Talk Time** statsboard report adds a reusable card for **Total talk time**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-total-talk-time-exam">![Total Talk Time example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/mqdtotal-talk-time.png)<figcaption>Total Talk Time example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Total talk time</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Sum sc\_billsec for Simple CDR rows in the selected period.

## When To Use

Measures real answered conversation time instead of total call setup time.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Average Talk Time

The **Average Talk Time** statsboard report adds a reusable card for **Average talk time**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-average-talk-time-ex">![Average Talk Time example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/fGFaverage-talk-time.png)<figcaption>Average Talk Time example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Average talk time</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Average sc\_billsec for answered Simple CDR rows.

## When To Use

Useful when comparing agent or tenant conversation patterns.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Answered Call Count

The **Answered Call Count** statsboard report adds a reusable card for **Answered call count**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-answered-call-count-">![Answered Call Count example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Voranswered-call-count.png)<figcaption>Answered Call Count example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Answered call count</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Count Simple CDR rows where sc\_billsec is greater than zero or disposition is ANSWERED.

## When To Use

Gives a tenant-level answered call volume trend.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Missed / Failed Inbound Calls

The **Missed / Failed Inbound Calls** statsboard report adds a reusable card for **Missed / failed inbound calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-missed-%2F-failed-inbo">![Missed / Failed Inbound Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/xVPmissed-failed-inbound-calls.png)<figcaption>Missed / Failed Inbound Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Missed / failed inbound calls</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Count inbound Simple CDR rows that were not answered.

## When To Use

Highlights inbound demand that did not reach a successful conversation.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Outbound Failed Calls

The **Outbound Failed Calls** statsboard report adds a reusable card for **Outbound failed calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-outbound-failed-call">![Outbound Failed Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/kxDoutbound-failed-calls.png)<figcaption>Outbound Failed Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Outbound failed calls</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Count outbound Simple CDR rows with failed, busy, no-answer, congestion, or unavailable disposition.

## When To Use

Useful for identifying carrier or dialing-quality problems.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Answer Rate %

The **Answer Rate %** statsboard report adds a reusable card for **Answer rate %**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-answer-rate-%25-exampl">![Answer Rate % example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/sL6answer-rate.png)<figcaption>Answer Rate % example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Answer rate %</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Answered Simple CDR rows divided by all Simple CDR rows, multiplied by 100.

## When To Use

Provides a fast tenant-level service-health indicator.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Average Time To Answer

The **Average Time To Answer** statsboard report adds a reusable card for **Average time to answer**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-average-time-to-answ">![Average Time To Answer example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/pJsaverage-time-to-answer.png)<figcaption>Average Time To Answer example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Average time to answer</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Average seconds between sc\_start and sc\_whenanswered for answered rows.

## When To Use

Shows how quickly answered calls are picked up.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Short Calls Count

The **Short Calls Count** statsboard report adds a reusable card for **Short calls count**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-short-calls-count-ex">![Short Calls Count example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/DvVshort-calls-count.png)<figcaption>Short Calls Count example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_METRIC`</td></tr><tr><td>Metric</td><td>Short calls count</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Line or bar chart by selected date bucket.</td></tr></tbody></table>

## Calculation

Count Simple CDR rows with sc\_duration greater than zero and under the configured short-call threshold.

## When To Use

Helps detect wrong-number calls, failed conversations, or nuisance traffic.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Top Called Numbers

The **Top Called Numbers** statsboard report adds a reusable card for **Top called numbers**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-top-called-numbers-e">![Top Called Numbers example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Gz7top-called-numbers.png)<figcaption>Top Called Numbers example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_TOP`</td></tr><tr><td>Metric</td><td>Top called numbers</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Top-N bar chart or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by sc\_dialednum and count each destination.

## When To Use

Shows the destinations receiving the most calls.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Top Callers

The **Top Callers** statsboard report adds a reusable card for **Top callers**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-top-callers-example-">![Top Callers example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/r9vtop-callers.png)<figcaption>Top Callers example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_TOP`</td></tr><tr><td>Metric</td><td>Top callers</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Top-N bar chart or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by caller number and caller name, then count calls.

## When To Use

Identifies frequent callers or high-volume sources.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Disposition

The **Calls By Disposition** statsboard report adds a reusable card for **Calls by disposition**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-disposition">![Calls By Disposition example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Nv5calls-by-disposition.png)<figcaption>Calls By Disposition example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_BREAKDOWN`</td></tr><tr><td>Metric</td><td>Calls by disposition</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Pie chart, bar chart, or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by sc\_disposition.

## When To Use

Shows the result mix for the selected period.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Direction

The **Calls By Direction** statsboard report adds a reusable card for **Calls by direction**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-direction-e">![Calls By Direction example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Ttkcalls-by-direction.png)<figcaption>Calls By Direction example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_BREAKDOWN`</td></tr><tr><td>Metric</td><td>Calls by direction</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Pie chart, bar chart, or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by sc\_direction.

## When To Use

Compares inbound, outbound, and local call flow.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Answering Extension

The **Calls By Answering Extension** statsboard report adds a reusable card for **Calls by answering extension**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-answering-e">![Calls By Answering Extension example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/RrNcalls-by-answering-extension.png)<figcaption>Calls By Answering Extension example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_BREAKDOWN`</td></tr><tr><td>Metric</td><td>Calls by answering extension</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Pie chart, bar chart, or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by sc\_whoanswered, using Unanswered when empty.

## When To Use

Shows where answered calls landed.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Hour Of Day

The **Calls By Hour Of Day** statsboard report adds a reusable card for **Calls by hour of day**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-hour-of-day">![Calls By Hour Of Day example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/xsscalls-by-hour-of-day.png)<figcaption>Calls By Hour Of Day example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_BREAKDOWN`</td></tr><tr><td>Metric</td><td>Calls by hour of day</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Bar chart or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by the hour extracted from sc\_start.

## When To Use

Finds the busiest hours for staffing and routing decisions.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Weekday

The **Calls By Weekday** statsboard report adds a reusable card for **Calls by weekday**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-weekday-exa">![Calls By Weekday example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/dEBcalls-by-weekday.png)<figcaption>Calls By Weekday example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_BREAKDOWN`</td></tr><tr><td>Metric</td><td>Calls by weekday</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Bar chart or table.</td></tr></tbody></table>

## Calculation

Group Simple CDR rows by weekday extracted from sc\_start.

## When To Use

Compares traffic patterns across the week.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Longest Calls

The **Longest Calls** statsboard report adds a reusable card for **Longest calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-longest-calls-exampl">![Longest Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/T5Jlongest-calls.png)<figcaption>Longest Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`CALLS_TOP`</td></tr><tr><td>Metric</td><td>Longest calls</td></tr><tr><td>Data source</td><td>Simple CDR</td></tr><tr><td>Display</td><td>Table by default, with caller, dialed number, disposition, and duration.</td></tr></tbody></table>

## Calculation

Sort Simple CDR rows by sc\_duration descending and return the configured top-N rows.

## When To Use

Finds unusually long calls for review, billing, or quality checks.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Entered Calls

The **Queue Entered Calls** statsboard report adds a reusable card for **Queue entered calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-entered-calls-">![Queue Entered Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/uCtqueue-entered-calls.png)<figcaption>Queue Entered Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue entered calls</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Count distinct queue\_log callid values where event is ENTERQUEUE.

## When To Use

Shows queue demand over time.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Answered Calls

The **Queue Answered Calls** statsboard report adds a reusable card for **Queue answered calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-answered-calls">![Queue Answered Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/JSfqueue-answered-calls.png)<figcaption>Queue Answered Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue answered calls</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Count distinct queue\_log callid values where event is CONNECT.

## When To Use

Shows how many calls were answered by queue members.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Abandoned Calls

The **Queue Abandoned Calls** statsboard report adds a reusable card for **Queue abandoned calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-abandoned-call">![Queue Abandoned Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/F36queue-abandoned-calls.png)<figcaption>Queue Abandoned Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue abandoned calls</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Count distinct queue\_log callid values where event is ABANDON.

## When To Use

Shows caller drop-off before answer.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Transferred Calls

The **Queue Transferred Calls** statsboard report adds a reusable card for **Queue transferred calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-transferred-ca">![Queue Transferred Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/oK9queue-transferred-calls.png)<figcaption>Queue Transferred Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue transferred calls</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Count distinct queue\_log callid values for TRANSFER, BLINDTRANSFER, and ATTENDEDTRANSFER events.

## When To Use

Shows how often queue calls are transferred after handling.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Timeout Calls

The **Queue Timeout Calls** statsboard report adds a reusable card for **Queue timeout calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-timeout-calls-">![Queue Timeout Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/hyJqueue-timeout-calls.png)<figcaption>Queue Timeout Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue timeout calls</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Count distinct queue\_log callid values where event is EXITWITHTIMEOUT.

## When To Use

Shows calls leaving the queue due to timeout handling.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Answer Rate %

The **Queue Answer Rate %** statsboard report adds a reusable card for **Queue answer rate %**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-answer-rate-%25-">![Queue Answer Rate % example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/ODDqueue-answer-rate.png)<figcaption>Queue Answer Rate % example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue answer rate %</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

CONNECT calls divided by ENTERQUEUE calls, multiplied by 100.

## When To Use

Measures queue answer effectiveness.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Abandon Rate %

The **Queue Abandon Rate %** statsboard report adds a reusable card for **Queue abandon rate %**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-abandon-rate-%25">![Queue Abandon Rate % example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/tkuqueue-abandon-rate.png)<figcaption>Queue Abandon Rate % example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue abandon rate %</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

ABANDON calls divided by ENTERQUEUE calls, multiplied by 100.

## When To Use

Measures caller abandonment pressure.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Queue Timeout Rate %

The **Queue Timeout Rate %** statsboard report adds a reusable card for **Queue timeout rate %**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-queue-timeout-rate-%25">![Queue Timeout Rate % example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/nTSqueue-timeout-rate.png)<figcaption>Queue Timeout Rate % example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Queue timeout rate %</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

EXITWITHTIMEOUT calls divided by ENTERQUEUE calls, multiplied by 100.

## When To Use

Shows how often queue timeout routing is used.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Average Queue Wait Before Answer

The **Average Queue Wait Before Answer** statsboard report adds a reusable card for **Average queue wait before answer**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-average-queue-wait-b">![Average Queue Wait Before Answer example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/IbQaverage-queue-wait-before-answer.png)<figcaption>Average Queue Wait Before Answer example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Average queue wait before answer</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Average completion hold time from COMPLETECALLER and COMPLETEAGENT data1.

## When To Use

Shows how long answered callers waited before an agent took the call.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Average Queue Wait Before Abandon

The **Average Queue Wait Before Abandon** statsboard report adds a reusable card for **Average queue wait before abandon**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-average-queue-wait-b">![Average Queue Wait Before Abandon example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/0jfaverage-queue-wait-before-abandon.png)<figcaption>Average Queue Wait Before Abandon example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Average queue wait before abandon</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Average ABANDON data3 wait time.

## When To Use

Shows how long abandoned callers waited before leaving.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Max Queue Wait Time

The **Max Queue Wait Time** statsboard report adds a reusable card for **Max queue wait time**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-max-queue-wait-time-">![Max Queue Wait Time example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/c9hmax-queue-wait-time.png)<figcaption>Max Queue Wait Time example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Max queue wait time</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Maximum wait time across answered, abandoned, timed-out, and transferred queue events.

## When To Use

Highlights worst-case queue waiting time.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# SLA %

The **SLA %** statsboard report adds a reusable card for **SLA %**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-sla-%25-example-with-f">![SLA % example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/7Jmsla.png)<figcaption>SLA % example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>SLA %</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Multi-queue time-series chart.</td></tr></tbody></table>

## Calculation

Answered queue calls within servicelevel seconds divided by entered calls, multiplied by 100.

## When To Use

Tracks service-level compliance using the queue service level when available.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Queue

The **Calls By Queue** statsboard report adds a reusable card for **Calls by queue**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-queue-examp">![Calls By Queue example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/QHEcalls-by-queue.png)<figcaption>Calls By Queue example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_METRIC`</td></tr><tr><td>Metric</td><td>Calls by queue</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Bar chart or table.</td></tr></tbody></table>

## Calculation

Count ENTERQUEUE events grouped by queue.

## When To Use

Compares traffic among queues in the selected period.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Calls By Agent

The **Calls By Agent** statsboard report adds a reusable card for **Calls by agent**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-calls-by-agent-examp">![Calls By Agent example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/PPjcalls-by-agent.png)<figcaption>Calls By Agent example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_AGENT_METRIC`</td></tr><tr><td>Metric</td><td>Calls by agent</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Top-N bar chart or table.</td></tr></tbody></table>

## Calculation

Count distinct queue calls with agent-handled events grouped by agent.

## When To Use

Shows the busiest queue agents.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Agent Answered Calls

The **Agent Answered Calls** statsboard report adds a reusable card for **Agent answered calls**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-agent-answered-calls">![Agent Answered Calls example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/NwLagent-answered-calls.png)<figcaption>Agent Answered Calls example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_AGENT_METRIC`</td></tr><tr><td>Metric</td><td>Agent answered calls</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Top-N bar chart or table.</td></tr></tbody></table>

## Calculation

Count distinct CONNECT events grouped by queue\_log agent.

## When To Use

Shows answered call distribution among agents.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Agent Average Talk Time

The **Agent Average Talk Time** statsboard report adds a reusable card for **Agent average talk time**. Use it inside **Status &gt; Statsboards** when the selected tenant needs this metric on a custom operations board.

<figure id="bkmrk-agent-average-talk-t">![Agent Average Talk Time example with fictional data.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/jqwagent-average-talk-time.png)<figcaption>Agent Average Talk Time example with fictional data.</figcaption></figure>## Configuration

<table id="bkmrk-fieldvaluestatsboard"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Statsboard box type</td><td>`QUEUE_AGENT_METRIC`</td></tr><tr><td>Metric</td><td>Agent average talk time</td></tr><tr><td>Data source</td><td>Queue Log</td></tr><tr><td>Display</td><td>Top-N bar chart or table.</td></tr></tbody></table>

## Calculation

Average COMPLETECALLER and COMPLETEAGENT data2 grouped by agent.

## When To Use

Compares average queue conversation duration by agent.

## Notes

- The screenshot is rendered with MiRTA PBX statsboard amCharts and fictional Docs Contact Center data.
- The report follows the date range selected when opening the statsboard.
- Queue reports can be limited to selected queues, or left empty to include all queues for the tenant.

# Realtime Status

Realtime Status status and operational review.

# Overview

The **Realtime Status** status page is used to inspect operational state and historical records without changing normal tenant configuration.

## How to Use

1. Open **Status &gt; Realtime Status**.
2. Confirm that the selected tenant is correct, or use the available global view when your account allows it.
3. Use filters to narrow the result before exporting or reviewing detailed records.
4. For live status pages, refresh the page after making configuration changes that should affect the state.

## Operational Notes

Status pages are diagnostic views. When a record points to a configuration object, open the related configuration page to make changes instead of editing the status view.