# 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 &gt; 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/complete-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/simple-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>

## 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/admin-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

Statsboards status and operational review.

# Overview

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.

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