> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ports.md).

# Network ports

Reference Controller 7000 network ports, protocols, traffic direction, and TLS support.

## This page answers

* Which ports does a Gallagher controller use?
* Which direction is each port, and what is it for?
* Which versions of TLS are supported?

The ports used by Gallagher controllers for network communication.

These ports also apply to Controller 7000 SDC.

***

## Port table

| Port                  | Protocol | Direction | Purpose                                                                                                                                         |
| --------------------- | -------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| 80\*                  | TCP      | Inbound   | Gallagher Technical Support Diagnostics using HTTP                                                                                              |
| 137‡                  | UDP      | Inbound   | Browsing requests of NetBIOS over TCP/IP                                                                                                        |
| 138‡                  | UDP      | Inbound   | Browsing datagram responses of NetBIOS over TCP/IP                                                                                              |
| 1072                  | TCP      | Inbound   | Inbound communication with Gallagher Command Centre Server and other Gallagher Controller devices using encrypted proprietary Bertbus Protocol  |
| Assigned by TCP stack | TCP      | Outbound  | IP Alarms transmission using DC09 protocol (if configured)                                                                                      |
| Assigned by TCP stack | TCP      | Outbound  | Outbound communication with Gallagher Command Centre Server and other Gallagher Controller devices using encrypted proprietary Bertbus Protocol |

\* Port 80 is open only when **DIP Switch 1 is ON**.\
‡ Ports 137 and 138 are open only when **DIP Switch 6 is OFF**.

***

## TLS support

A Gallagher controller running a supported version of Command Centre supports **TLS 1.2 and TLS 1.3** connectivity, as long as the server it is connected to also supports the protocol.

***

## Notes

* **Port 1072** is the primary communication port for all controller-to-server and controller-to-controller traffic.
* From **CC version 8.50 onwards**, the controller initiates the outbound TCP connection to the server. The server does not initiate connections to the controller.
* The Bertbus Protocol on port 1072 is encrypted (AES 256-bit).
* If another application is using port 1072, the FT Controller Service will fail to bind and controllers will not come online. See [Firewall Issues](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-firewall-issues.md) and [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md) for diagnosis.

***

🔗 **Related**

* [Firewall Issues](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-firewall-issues.md). Opening these ports through Windows Firewall.
* [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). Testing port 1072 with telnet, TNC, and netstat.
* [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU). Variants, specifications, and accessories.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ports.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.