> 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/architecture.md).

# Architecture

AMIE Advanced has three parts: the AMIE Agent app on each Versity handset, the AMIE cloud run by Spectralink, and the console you open in a web browser. Nothing needs to run on your premises.

![Handsets on the customer network send metrics through the corporate firewall and the public internet to the AMIE cloud; administrators view the results in the console.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-c648985c32ad142f6951e12d288fa195e5cdf731%2Famie-architecture.png?alt=media)

## The AMIE Agent

The AMIE Agent is an app on every Versity handset. It collects diagnostic data — battery, device, network and call metrics, together called telemetry — and sends it to the AMIE cloud. It is configured with an enrollment ID that tells AMIE which [Space](/amie-advanced/introduction/how-your-space-is-organized.md), and which group in that Space, the handset belongs to. See [Connecting handsets](/amie-advanced/planning-and-installation/connecting-devices.md).

## The path the data takes

Telemetry leaves the handset over your Wi-Fi network, passes outward through your corporate firewall and across the public internet, and arrives at the AMIE cloud. The connection is opened by the handset and encrypted in the same way a web browser's connection to a secure website is. The cloud stores the telemetry, analyzes it, and makes the results available to the console.

Everything a handset sends travels over a connection the handset opened itself. Your firewall therefore needs outbound rules only — see [Network requirements](/amie-advanced/planning-and-installation/network-requirements.md).

## The console

The console is a web page. Administrators and users sign in to it from any computer running Google Chrome with internet access, and review the status of the fleet and the insights AMIE draws from it: which batteries to replace, which handsets have gone quiet, where calls are failing. The console reads from the AMIE cloud; it has no connection to your handsets or your network. What each user sees is decided by the group they were placed in and by their role — see [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md).

## What is sent

The AMIE Agent reports about the handset: its battery's charge, health and temperature; its model, software and storage; the access point and network it is on and the signal it sees; its extension and phone number; which apps are consuming its battery; and when calls started and ended, with a quality score for each. [How AMIE works](/amie-advanced/introduction/how-it-works.md) gives examples of each category. It does not capture call audio or the internal data of any app.


---

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