> 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/performance-long-handoff.md).

# Long Handoff Summary

**Long Handoff Summary** is the second tab of the [Performance](/amie-advanced/using-the-platform/performance.md) screen. A handoff is a handset moving its connection from one access point to another during a call. This tab counts the slow ones — those that took more than 50 milliseconds (ms) — over time, and shows which access points and handsets are involved. To reach it, select **Performance** in the sidebar, then the **Long Handoff Summary** tab.

## Why this screen matters

A handset on a call that walks out of one access point's range must hand off to the next. A slow handoff is heard as a gap or a click in the audio, and a handset that hands off slowly at the same place every time marks an access point boundary where coverage overlaps badly. This tab says how often handoffs are slow, on which access points, and for which handsets, so that a site survey can be aimed at the right corridor rather than the whole building.

## Before you start

The tab follows the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector), the [time range](/amie-advanced/using-the-platform/performance.md#time-range) and the [filters](/amie-advanced/using-the-platform/performance.md#filters) described on [Performance](/amie-advanced/using-the-platform/performance.md). An hour or day with no handoffs over 50 ms is plotted as **0**, whether it had calls or not. Networks your organization has asked to exclude are left out as described under [Before you start](/amie-advanced/using-the-platform/performance.md#before-you-start) on Performance.

## Screen layout

![Long Handoff Summary over 90 days with no handoffs recorded: a flat line and empty tables.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-cdd625db121bd78afb8888e15dd0282083c67888%2Fperformance-long-handoff.png?alt=media)

### The chart

One line, on the left axis only:

| Series                         | Axis                                                             | What each point is                                                            |
| ------------------------------ | ---------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| **Total Long Handoffs** (blue) | Left, from **0** to a round number at or above the highest point | The number of handoffs recorded in that hour or day that took more than 50 ms |

There is no right-hand axis and no legend.

### The tables

**Long Handoffs by AP** on the left (the by AP table) and **Long Handoffs by Device** on the right (the by Device table). Each by AP row gathers the handoffs attributed to one access point. Unlike the other three tabs, this by AP table keeps records with an [all-zeros address](/amie-advanced/using-the-platform/performance.md#the-two-tables), as a row whose **AP BSSID** reads **00:00:00:00:00:00**. With no handoffs in the range, each table reads **No data for the selected period**.

{% hint style="warning" %}
TODO: is a handoff attributed to the access point the call moved to, or the one it moved from? The console does not say, and the answer decides which access point a red dot points at.
{% endhint %}

## Controls

The shared controls are described on [Performance](/amie-advanced/using-the-platform/performance.md#controls). Exports from this tab are named `long-handoff-ap.csv` and `long-handoff-device.csv`.

## Columns

Every column is sortable; each table opens sorted by its first column.

### Long Handoffs by AP

| Column                    | What it shows                                                                                                                                                                                                                                                     |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AP BSSID**              | The access point's hardware address                                                                                                                                                                                                                               |
| **AVG Handoff Time (ms)** | The average time, in milliseconds, of the handoffs attributed to this access point, shown as a whole number                                                                                                                                                       |
| **Total Long Handoffs**   | How many handoffs attributed to this access point took more than 50 ms                                                                                                                                                                                            |
| **Total Handoffs**        | How many handoffs with a recorded time were attributed to this access point                                                                                                                                                                                       |
| **Long Handoff Rate**     | **Total Long Handoffs** as a percentage of **Total Handoffs**, to two decimal places                                                                                                                                                                              |
| (dot)                     | Green when **AVG Handoff Time (ms)** is under 45, orange from 45 up to 50, red at 50 or more. The dot is judged on the unrounded average, so a row reading **45** can carry either a green or an orange dot. The count uses more than 50; the dot uses 50 or more |

### Long Handoffs by Device

The same columns for each handset, with **Device Serial** in place of **AP BSSID**, counting the handoffs that handset made. No dot.

## Icons and indicators

| Icon or indicator                       | Meaning                                                         | When it appears                       |
| --------------------------------------- | --------------------------------------------------------------- | ------------------------------------- |
| Blue line                               | **Total Long Handoffs**                                         | When there is data                    |
| Green / orange / red dot on a by AP row | Average handoff under 45 ms / 45 to under 50 ms / 50 ms or more | Every by AP row with a value to judge |

The shared icons are described on [Performance](/amie-advanced/using-the-platform/performance.md#icons-and-indicators).

## What to look for

* A red dot on an access point with a large **Total Handoffs**. Handoffs at that access point are slow on average and there are many of them: a coverage boundary worth surveying. Open [Access Points](/amie-advanced/using-the-platform/access-points.md) to find where it is.
* A high **Long Handoff Rate** with a **Total Handoffs** of 1 or 2. One slow handoff, not a pattern. Read **Total Handoffs** before acting on the rate.
* A green dot beside a **Total Long Handoffs** above zero. "Long" means over 50 ms for the count and the chart, but the dot judges the average against 45 ms and 50 ms, so an access point can average well while still having some long handoffs.
* A handset near the top of the by Device table across many access points. The handset roams slowly wherever it is. Open its [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md) and hover over the **Network Connected** bars to see where it moved between access points.
* **Total Long Handoffs** on the chart rising over the daily ranges. More slow handoffs than before. The by Device table for the same range shows whether one handset or many are behind it, and the by AP table whether one access point or many.
* A by AP row whose **AP BSSID** reads **00:00:00:00:00:00**, and totals that include it. This by AP table keeps records with an [all-zeros address](/amie-advanced/using-the-platform/performance.md#the-two-tables); the others leave them out.
* Different figures from a colleague. Points are placed by when the handoff was recorded, within the range cut in each person's browser time zone — see [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md).

## Metrics on this screen

* [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md)

## Related

* [Performance](/amie-advanced/using-the-platform/performance.md) — ranges, filters, tables and export
* [Low RSSI Events Summary](/amie-advanced/using-the-platform/performance/performance-low-rssi.md) — weak signal on the same access points
* [Access Points](/amie-advanced/using-the-platform/access-points.md) — where the access points in the by AP table are


---

# 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/performance-long-handoff.md?ask=<question>&goal=<user_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.