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

# Network requirements

AMIE Advanced needs no inbound access to your network. Handsets open every connection themselves, and the console is a web page hosted by Spectralink.

## Firewall rules

Allow the Versity handsets, and the computers that will open the console, to reach the following destination:

| Destination         | Port            | Direction | Used by                                                                                   |
| ------------------- | --------------- | --------- | ----------------------------------------------------------------------------------------- |
| `*.spectralink.net` | 443/TCP (HTTPS) | Outbound  | Handsets sending their device telemetry data; browsers opening the console and signing in |

No inbound ports need to be opened and no port forwarding is required. Keep a firewall between your handsets and the internet as you would for any other device.

## TLS (HTTPS) inspection

If your firewall inspects encrypted traffic by terminating the handsets' connections and opening its own, the handsets will not trust the certificate the firewall presents and will not connect. Exclude the destination above from inspection for handset traffic.

## Email

AMIE sends sign-up, password-setup and one-time-code emails from a `spectralink.net` address. Allow that domain on your email servers, and tell new users to check their junk folder if a code does not arrive.

## Checking the rules

Once handsets are configured, the message **AMIE is connected** at the top of the AMIE Agent app confirms that a handset can reach AMIE — see [Connecting handsets](/amie-advanced/planning-and-installation/connecting-devices.md#check-that-handsets-are-reporting).


---

# 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/network-requirements.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.