> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/using-the-platform/performance.md). # Performance **Performance** is where you find out where voice quality is being lost: which access points and which handsets are behind poor calls, slow roaming, weak signal and lost audio packets. It has four tabs, one per kind of problem, and every tab has the same shape — a time-range selector, a trend chart, and two tables that break the same period down by access point and by device. To reach it, select **Performance** in the sidebar. This page covers what the four tabs share. Each tab's chart, columns and thresholds have their own page: * [Call Performance Summary](/amie-advanced/using-the-platform/performance/performance-call-performance.md) — call quality scores * [Long Handoff Summary](/amie-advanced/using-the-platform/performance/performance-long-handoff.md) — slow moves between access points * [Low RSSI Events Summary](/amie-advanced/using-the-platform/performance/performance-low-rssi.md) — weak signal during calls * [Packet Loss Summary](/amie-advanced/using-the-platform/performance/performance-packet-loss.md) — audio packets dropped or missed ## Why this screen matters When users complain about call quality, the question is whether the problem is the network or the handsets, and where. **Performance** answers it by breaking every call down two ways: the [by AP table](#the-two-tables) by access point and the [by Device table](#the-two-tables) by handset, so that sorting on a rate column ranks them; the [chart](#the-chart) shows whether the problem is getting worse. An access point with a red dot on every tab is a coverage or capacity problem at that location; a handset near the top of the by Device table on every tab, across different access points, is a handset problem. Start on [Call Performance Summary](/amie-advanced/using-the-platform/performance/performance-call-performance.md), find the worst access point or handset, then open the other three tabs to see which kind of problem — roaming, signal or packet loss — is behind it. ## Before you start The screen shows measurements from calls made by handsets in the selected group and the groups beneath it. It follows the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header. Only periods with calls have anything to measure. A group whose handsets made no calls in the selected range shows a chart of zeros and empty tables. Your organization can ask Spectralink to exclude particular Wi-Fi networks from this screen — a guest network, for example. The exclusion never affects the by AP table. Elsewhere it works in one of two ways: either every handset that has ever connected to an excluded network is left out, including its calls on other networks, or only the calls made on the excluded networks are left out. | Tab | Chart | by AP table | by Device table | | --------------------------------------------------------------------------------------------------------- | ------------------------------- | ------------ | ------------------------------- | | [Call Performance Summary](/amie-advanced/using-the-platform/performance/performance-call-performance.md) | Whole handsets left out | Not affected | Excluded-network calls left out | | [Long Handoff Summary](/amie-advanced/using-the-platform/performance/performance-long-handoff.md) | Excluded-network calls left out | Not affected | Excluded-network calls left out | | [Low RSSI Events Summary](/amie-advanced/using-the-platform/performance/performance-low-rssi.md) | Excluded-network calls left out | Not affected | Excluded-network calls left out | | [Packet Loss Summary](/amie-advanced/using-the-platform/performance/performance-packet-loss.md) | Whole handsets left out | Not affected | Whole handsets left out | {% hint style="warning" %} TODO: where an administrator sets the list of excluded networks, and whether it is visible in this console. Nothing on the Performance screen shows which networks are excluded. {% endhint %} ## Screen layout ![The Performance screen at 90d with the filters open: time ranges, four tabs, the chart, and the two tables.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-93ef1b39806d2137ae7d46069ca6d1e6cdcfa16f%2Fperformance.png?alt=media) Top to bottom: the heading **Performance** with the time-range buttons and **Show Filters** to its right; the filters when open; the four tabs; the chart; the two tables side by side. ### Time range Five buttons in a row at the top right: **Today**, **24h**, **7d**, **30d**, **90d**. The screen opens on **7d**. The selected range applies to the chart and both tables on every tab. | Range | Covers | Chart points | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | **Today** | From midnight this morning, in your browser's time zone, up to the end of the current hour | One per hour so far today — a single point just after midnight, 24 by late evening | | **24h** | The 24 whole hours ending at the end of the current hour — so it starts between 23 and 24 hours ago and includes the part of this hour that has passed | 24, one per hour | | **7d** | Seven [calendar days](/amie-advanced/metrics-reference/time-and-time-zones.md) ending at midnight tonight, in your browser's time zone: today so far and the six days before it | 7, one per day | | **30d** | Thirty calendar days ending at midnight tonight | 30, one per day | | **90d** | Ninety calendar days ending at midnight tonight | 90, one per day | **Today** and **24h** are not the same thing: **Today** starts at midnight and grows through the day; **24h** is always a full day and crosses midnight into yesterday. ### Filters **Show Filters** opens a row of three filters that apply to the chart and both tables on every tab; the button then reads **Hide Filters**. Hiding the row does not clear the filters. | Filter | What it does | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Tag** | Has no effect yet: the list offers only **All Tags**. \[GAP-performance-1] | | **Device** | Narrows the chart and both tables to one handset. Type the handset's complete serial number, matching case, and press Enter or move out of the box. A **×** inside the box clears it | | **Access Point** | Narrows both tables to calls on one access point. Type its complete hardware address (BSSID), matching case, exactly as shown in the **AP BSSID** column, and press Enter or move out of the box. A **×** clears it | The boxes read **Search devices...** and **Search APs...** until you type, but they are exact-match filters, not searches. A partial serial or address matches nothing: both tables then read **No data for the selected period**, and the chart plots **0** at every point (**Device**) or is unchanged (**Access Point**) — see below. To look for part of a serial or address, use the search box above each table instead. Two boxes on the screen read **Search devices...**: the filter sits in the filter row, the search above the by Device table. One exception to the **Device** filter, on two tabs: on **Long Handoff Summary** and **Packet Loss Summary** the by AP table keeps the access points whose most recently seen handset in the range is the one you typed, and its figures still include every handset on those access points. Three exceptions to the **Access Point** filter: the chart is narrowed to the handsets that have ever used that access point and shows all of their calls, on any access point; if the address matches no access point, the tables are empty — except the **Packet Loss Summary** by Device table, which is unchanged — and the chart is unchanged; and on **Packet Loss Summary** the by Device table lists every handset AMIE links to the same part of the Space as the access point, not only those that used it. {% hint style="warning" %} TODO: what "the same part of the Space" is, as a reader would see it in the console — a group, a site, or something else. {% endhint %} ### The tabs **Call Performance Summary**, **Long Handoff Summary**, **Low RSSI Events Summary** and **Packet Loss Summary**. Selecting a tab reloads the chart and both tables for that tab's figures with the current range and filters. It also clears any sorting and returns both tables to page 1; search text typed into the tables is kept. ### The chart A line chart of the tab's figures across the selected range, one line — a series — per figure and one point per hour or per day. Points are joined by straight lines. An hour or day with no calls is plotted as **0** on every series, not left out, so a range with calls never shows an empty chart. Three tabs plot two series on two different vertical scales; **Long Handoff Summary** plots one. Where there are two, the left-hand scale belongs to the first series and the right-hand scale to the second, and each stops at a round number at or above its own highest point, so the top of the scale changes with the data. The two lines are therefore not comparable by height; read each against its own axis. A legend beneath the chart names the series and their colors when there are two. Along the bottom, up to seven time labels: hours (**2 PM**) for **Today** and **24h**, dates (**Sep 14**) for the daily ranges. Hover anywhere over the chart and a dashed line marks the nearest point, a dot appears on each series, and a row beneath the chart shows that point's time and each series' value to two decimal places. ### The two tables Side by side beneath the chart: on the left, the tab's figures broken down by access point — for example **Call Performance Metrics by AP** — and on the right by device — **Call Performance Metrics by Device**. Both list every access point or device with a record of the tab's figures in the range — calls, handoffs or signal samples — within your selection and filters. This guide calls them the by AP table and the by Device table. Each table has its own search box, its own sort, its own page size and its own page position, so you can hold your place in one while working through the other. Every column can be sorted; each table opens sorted by its first column. The by AP table also carries a colored dot in its last column, judging each access point against the tab's thresholds, which are listed on each tab's page; the by Device table has no dot. Beneath each table a line such as **Showing 1 to 10 of** *n* **access points** (or **devices**) counts the rows that match its search and the screen's range and filters. Some call records carry an access point address of all zeros — AMIE does not know which access point the call was on. This guide calls these all-zeros addresses. Records with an all-zeros address are left out of the by AP table on every tab except **Long Handoff Summary**, and of both tables and the chart on **Packet Loss Summary**, so totals can differ slightly between tabs. On **Long Handoff Summary** they appear as a by AP row whose **AP BSSID** reads **00:00:00:00:00:00**. {% hint style="warning" %} TODO: why some call records carry an all-zeros access point address. {% endhint %} When nothing matches, each table reads **No data for the selected period** in place of its rows, with **Showing 0 to 0 of 0 access points** (or **devices**) beneath. ## Controls | Control | What it does | | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Today**, **24h**, **7d**, **30d**, **90d** | Set the period for the chart and both tables. Both tables return to page 1 | | **Show Filters** / **Hide Filters** | Show or hide the filters. Filters stay in effect while hidden | | **Device**, **Access Point** filters | Exact-match, case-sensitive filters, applied when you press Enter or leave the box. Both tables return to page 1 | | **×** in a filter or search box | Clears that box and reloads. Hovering over it shows **Clear** | | **Tag** filter | Has no effect yet. \[GAP-performance-1] | | A tab | Switches to that tab's figures. Clears sorting on both tables and returns both to page 1 | | Search box above a table (they read **Search access points...** and **Search devices...** until you type) | Narrows that table to rows containing what you typed, ignoring case, a moment after you stop typing. A **×** clears it. Returns the table to page 1 | | **Export** above a table | Downloads a spreadsheet file (CSV) of every row matching that table's search and the screen's range and filters — not only the visible page — in the current sort | | Column heading | Sorts that table. The first click sorts ascending, the second descending, the third returns to the default order — by the **AP BSSID** or **Device Serial** column, ascending. Rows with no value in the column are always listed last. Returns the table to page 1 | | **Show** | **10**, **25**, **50** or **100** rows per page; opens on **10**. Returns the table to page 1 | | **First**, **Previous**, **Next**, **Last** | Move between pages, with **Page 1 of 3** between them. Shown only when there is more than one page; each is grayed out when it would not move you | The by AP table's search matches the access point's hardware address; its name, and the floorplan it is plotted on, where AMIE has them (see [Access Points](/amie-advanced/using-the-platform/access-points.md)); the network name (SSID) on its most recent call record in the range; or the serial of the handset most recently seen on it in the range. The by Device table's search matches the serial. An export is named after the tab and table, for example `call-performance-ap.csv`; column headings match the on-screen labels and values are formatted as displayed. It stops at 10,000 rows, and there is no progress indicator, no message if the export fails, and no warning when the limit cuts the file short. Changing the group in the header reloads everything from page 1 and keeps your range, filters, search and sort. Nothing on the screen refreshes by itself; reload the page to recalculate. ## Icons and indicators | Icon or indicator | Meaning | When it appears | | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | | Highlighted range button | The selected time range | One at a time | | Three-line icon on **Show Filters** | Marks the button; the button is outlined in blue while the filters are open | Always | | **×** inside a filter or search box | Clears the box | While it has text | | Highlighted tab | The tab whose figures are shown | One at a time | | Blue and orange lines on the chart | The first and second series named in the legend, where there is one | When the tab has data | | Dashed vertical line and dots on the chart | The point nearest your pointer | While hovering | | Magnifying glass in a table's search box | Marks the search box | Always | | Down arrow on **Export** | Marks the button | Always | | Up-down arrows beside a heading | The table is not sorted by that column | Every sortable heading except the one sorted by | | Up or down arrow beside a heading | The column the table is sorted by, ascending or descending | One heading per table | | Green / orange / red dot at the end of a by AP row | **Good** / **Warning** / **Poor** against the tab's thresholds; hover to read the word. The column has no visible heading | Every by AP row with a value to judge | | Translucent overlay with the Spectralink wordmark, a moving bar and **Loading...** | That part of the screen is reloading. Search boxes stay usable | While a request is in flight | ## What to look for * A red dot on the same access point on more than one tab. That access point has a coverage or capacity problem at its location. Open [Access Points](/amie-advanced/using-the-platform/access-points.md) to find where it is. * A handset near the top of the by Device table on every tab, across different access points. The problem travels with the handset. Open it from the Devices [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) and read its [Call History](/amie-advanced/using-the-platform/device-details/device-call-history.md) and [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md). * A high count beside a low rate. Every table pairs a count with a rate — per call minute, or as a percentage. 10 events across 20 call minutes matter more than 50 across 5,000. Sort by the rate column, then read the count and, where the tab has one, the **Total Call Min** or **Total Handoffs** column to judge how much data sits behind it. * A red dot on an access point with very few call minutes. The dot applies the tab's thresholds to the row's own figure, however little data is behind it. A red dot on two call minutes deserves less weight than an orange dot on two thousand. * A chart line that looks higher than the other. On tabs with two series, each line has its own axis, and each axis stops at a round number at or above its own series. Read the values in the hover row, not the heights. * A point at **0**. It can mean no calls in that hour or day rather than a good result. Check the tables for the same period. * Totals that differ slightly between tabs. Records with an [all-zeros address](#the-two-tables) are left out of the by AP table on three tabs and of both Packet Loss tables and the Packet Loss chart, but kept on the Long Handoff by AP table and in the other three charts. * Different figures from a colleague. Check the group selector first. Then remember that the ranges are cut at midnight, and at the hour, in each person's browser time zone, and that daily ranges include today as a partial day — see [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md). ## Metrics on this screen * [Call quality (MOS)](/amie-advanced/metrics-reference/call-quality-mos.md) — the score behind the first tab * [Call Performance](/amie-advanced/metrics-reference/call-performance.md) — the Dashboard's fleet-wide version of the same score * [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — the hourly ranges end at the end of the current hour; the daily ranges are calendar days in your browser's time zone ## Related * [Call Performance Summary](/amie-advanced/using-the-platform/performance/performance-call-performance.md), [Long Handoff Summary](/amie-advanced/using-the-platform/performance/performance-long-handoff.md), [Low RSSI Events Summary](/amie-advanced/using-the-platform/performance/performance-low-rssi.md), [Packet Loss Summary](/amie-advanced/using-the-platform/performance/performance-packet-loss.md) — the four tabs * [Device details](/amie-advanced/using-the-platform/device-details.md) — one handset's calls, with a quality score for each * [Access Points](/amie-advanced/using-the-platform/access-points.md) — the access points named in the by AP tables * [Dashboard](/amie-advanced/using-the-platform/dashboard.md) — **Call Performance**, **Call Volume** and **Call Minutes** for the selected group --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spectralink.net/amie-advanced/using-the-platform/performance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.