> 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/planning-and-installation/connecting-devices.md).

# Connecting handsets

A Versity handset joins your [Space](/amie-advanced/introduction/how-your-space-is-organized.md) when its AMIE Agent app is given an enrollment ID and can reach the AMIE cloud. The enrollment ID belongs to a group: every handset that enrolls with it is placed in that group. Connecting a fleet therefore has two parts — getting each group's enrollment ID from the console, and giving it to the handsets.

## Before you start

* Your network allows the handsets to reach `*.spectralink.net` on port 443 — see [Network requirements](/amie-advanced/planning-and-installation/network-requirements.md).
* The groups you want handsets in exist — see [Planning your groups](/amie-advanced/planning-and-installation/planning-your-groups.md).
* You have the **Admin** or **Owner** role. Starting enrollment and reading the enrollment ID need it; other roles see **You don't have permission to view this** in place of the ID.
* Spectralink 84 Series handsets are not supported by AMIE Advanced.

## Get a group's enrollment ID

{% stepper %}
{% step %}
In the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the console header, select the group the handsets should join.
{% endstep %}

{% step %}
Select **Settings** in the sidebar, then the [Group Details](/amie-advanced/using-the-platform/settings/settings-group-details.md) tab. **Enrollment Settings** reads **Devices can enroll into this space using the enrollment ID below.**, with the selected group named under **Current Group**. The ID is specific to that group.
{% endstep %}

{% step %}
If the **Enrollment ID** reads **No enrollment ID available**, select **Start Enrollment**. A brief message reads **Enrollment started** and the ID appears.
{% endstep %}

{% step %}
Select the copy icon beside the ID. A brief message reads **Enrollment ID copied**.
{% endstep %}
{% endstepper %}

Repeat for each group that will receive handsets. A handset enrolled with one group's ID can be seen by every user placed at or above that group.

An enrollment ID does not last forever. If **Enrollment ID** later reads **No enrollment ID available**, select **Start Enrollment** again and give the new ID to any handsets still to be enrolled; handsets already enrolled are not affected.

{% hint style="warning" %}
TODO: how long an enrollment ID remains usable, and whether the console can show when one expires.
{% endhint %}

**End Enrollment** stops new handsets joining with the current ID; handsets already enrolled are not affected. A dialog headed **End Enrollment?** asks you to confirm, because it cannot be undone: starting enrollment again creates a different ID, and any handset still configured with the old one will not join. A brief message reads **Enrollment ended**.

## Configure the AMIE Agent on the handsets

Set these AMIE Agent settings on each handset, using Spectralink Application Management (SAM), your mobile device management system, or the AMIE Agent app's own settings on the phone:

| Setting                               | Value                                                                                                        |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Enable AMIE**                       | **On**                                                                                                       |
| **Use AMIE gateway communication**    | **Off** — the gateway is not used with AMIE Advanced                                                         |
| **Cloud communication enrollment ID** | The ID you copied for the handset's group                                                                    |
| **Upload over metered networks**      | **Off**, unless the handsets must report over a carrier network                                              |
| **Metered Wi-Fi setting**             | **Allow uploads over metered Wi-Fi networks** — Android treats a VPN, including a facility's own, as metered |

When the handset has enrolled, an orange message at the top of the app reads **AMIE is connected**.

## Check that handsets are reporting

Open the [Devices inventory](/amie-advanced/using-the-platform/devices-inventory.md). A handset appears there shortly after it has enrolled, with **—** under **Last Seen** until its first report arrives, and its **Group** column names the group whose enrollment ID it used. A handset reports only once a license has been assigned to it — see [Licensing](/amie-advanced/planning-and-installation/licensing.md#how-licenses-reach-handsets). Allow 15 to 30 minutes for the first report; battery figures often arrive before the rest.

## If a handset does not connect

| Symptom                                                                          | What to check or do                                                                                                                                                                                                                                    |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| No **AMIE is connected** message in the app                                      | Check that the enrollment ID was copied whole. Check that the handsets' Wi-Fi network can reach `*.spectralink.net` on port 443; it may be filtered differently from your computer's network. Toggle **Enable AMIE** off and on. Re-enter the settings |
| **AMIE is connected** shows but the handset is not in the Devices inventory      | Check that the enrollment ID is one for a group in your Space. Wait 30 minutes and reload the page                                                                                                                                                     |
| Handset is listed but reads **Unlicensed**, and never shows a **Last Seen** time | It has no license and is not reporting. Add licenses under **Settings** on the **Licenses** tab — see [Licensing](/amie-advanced/planning-and-installation/licensing.md)                                                                               |
| Handset is in the wrong group                                                    | It was enrolled with another group's ID. A handset that has joined one group is refused by another group's ID. Moving a handset between groups is not yet available \[GAP-devices-3]                                                                   |


---

# 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/planning-and-installation/connecting-devices.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.