> 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/configuration-client/site-installation/hardware/creating-controllers/onelink-configuration.md).

# OneLink Configuration

### Introduction

OneLink utilises Gallagher Cloud Services to enable Controller 7000s to connect to the on-premises Command Centre Server over the internet.

### Prerequisites

OneLink prerequisites are:

* An active Care Plan and enrolment in CEIP are required in order to activate OneLink connections.
* Ensure an active Care Plan then contact your Gallagher Rep.
* Enable CEIP follow the instructions in the “Product Alerts and Customer Experience Improvement Program” topic in the *Command Centre Client help file*.
* Minimum versions are vEL9.30 Command Centre and vCR9.30 MR1 for Controller.

### Licensing

* OneLink is a subscription service and connections can be activated or deactivated at any time without contacting Gallagher via the Configuration Client.
* Refer to [OneLink-Pricing-Flyer.pdf](https://media.gallagher.com/m/165323ffa47615a7/original/OneLink-Pricing-Flyer.pdf) for further information.
* Managing Cloud license allocation and subscription status can be checked via the **Subscription Summary** tab of the Cloud Licensing Viewer in the Command Centre Client. 'Allocation' is the number of connections in use and the number of purchased subscriptions, (e.g. 2/4). Exceeding the number of purchased subscriptions incurs pro-rata charges. Purchased subscriptions remain available for use until the end of the subscription period.

  For further detail, refer to the **Command Centre Web Release Note** in the `'Release Notes'` directory of the Command Centre installation files.

### Set up

The OneLink set up process is split into four parts, as follows:

<details>

<summary>Network Preparation</summary>

1. Configure your firewall to allow TCP outbound traffic on port 443 with a source of your internal Command Centre server, and destination of the following DNS or IP addresses.

   **Note:** There is no need to allow any inbound traffic to your Command Centre server.

   If you are configuring firewall rules based on IP address, please allow the following static IP addresses:

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><em><strong>Australian Command Centre Cloud:</strong></em></p><ul><li><strong>DNS address:</strong> commandcentre-ap-southeast-2.security.gallagher.cloud</li><li><strong>IP addresses:</strong> 52.62.211.7 and 54.79.91.203</li></ul><p><em><strong>Australian Gallagher Gateway Region:</strong></em></p><ul><li><strong>DNS address:</strong> commandcentre-api-au.security.gallagher.cloud</li><li><strong>IP addresses:</strong> 3.106.1.6 and 3.106.100.112</li></ul><p><em><strong>United States Gallagher Gateway Region:</strong></em></p><ul><li><strong>DNS address:</strong> commandcentre-api-us.security.gallagher.cloud</li><li><strong>IP addresses:</strong> 44.193.42.111 and 3.209.194.103</li></ul><p><em><strong>Global Cloud Services API Gateway:</strong></em></p><ul><li><strong>DNS address:</strong> services.security.gallagher.cloud</li><li><strong>IP addresses:</strong> 15.197.141.103 and 76.223.78.39</li></ul></div>
2. The controller requires a stable internet connection and access to DHCP and DNS services. If a firewall is in place, it must allow TCP outbound traffic from the controller to:
   1. **Controller Registration Service:**

      <https://controller-onboarding.security.gallagher.cloud:443>
   2. **Controller Gateway:** wss\://controller-gateway.security.gallagher.cloud:443
   3. **Trusted Issuer Service:** <http://controller-onboarding.security.gallagher.cloud:80>

</details>

<details>

<summary>Cloud Configuration</summary>

1. Enable a connection to the Gallagher Cloud before configuring a OneLink Connected Controller.

   See [Connecting to the Cloud](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud.md) for instructions.

   **Note:** Command Cente must be connected to the Gallagher Cloud.

</details>

<details>

<summary>Controller Configuration (Registration)</summary>

1. Configure the Controller for OneLink as appropriate.

   See [Creating Controller 7000s or 6000s](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/creating-controller-7000s-or-6000s.md) or [Creating a Controller 7000 Single Door](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/creating-a-controller-7000-single-door.md) for the complete procedure for configuring a Controller.
2. On the **Network** tab:
   1. Enter the **MAC Address** for the Controller.

      The MAC Address for each Controller is stuck to the actual Controller PCB.

      **Note:** A MAC address range is included in your license file and will be checked against when a MAC address is saved here. If you receive a *"MAC address out of range"* error message, check your license file to see what range is valid.
   2. Enter the correct **Serial Number** of the Controller.

      The Serial Number can be found printed on one of the Controller labels.
   3. Click the **OneLink** radio button.

      You will be asked to accept the Cloud Terms and Conditions.
   4. Click the **Apply** button.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3842b2358c99bb31fbd241928e09fcfbbeefc445%2Fcontroller_networktab_onelink.png?alt=media)

      In the **Cloud setup** section, the status *"Registered to connect via OneLink"* indicates that the Controller has been registered in the Controller Registration Service in the Gallagher Cloud. Although registered, the Controller still needs to be connected to the server (via the Activation process next) within 14 days or the registration will expire on the date and time given.

      **Note:** If registration does expire, you will need to re-register by clicking the **Refresh** button.

</details>

<details>

<summary>Controller Activation</summary>

1. Check the Controller software version is 9.30+.

   **Note:** This may be indciated on the packaging for recently manufactured controllers, otherwise the controller must be upgraded via Command Centre before it is OneLink capable.
2. Turn DIP Switches 2 and 7 ON.
3. Connect the Controller to an internet connection.
4. Power on the Controller.
5. The Controller will automatically:
   1. Retrieve details of the Controller Gateway URL from the Controller Registration Service.
   2. Connect to the Controller Gateway which will forward the connection request to Command Centre.
   3. Command Centre authenticates the Controller and a connection is established.
   4. Communication between the Controller and Command Centre Server continues through the Controller Gateway.
6. Once the Controller comes online and the Run LED is in a consistent single flash state, (typically this can take up to two minutes), turn the DIP Switches OFF.

</details>


---

# 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/configuration-client/site-installation/hardware/creating-controllers/onelink-configuration.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.
