> 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/external-alarm-monitoring/assigning-the-alarm-transmitter-dialler-to-a-controller.md).

# Assigning the Alarm Transmitter/Dialler to a Controller

### Introduction

Once an Alarm Transmitter/Dialler has been created in Command Centre, it must then be assigned to a Controller.

### Before you begin

Before you begin this procedure ensure you have performed [Configuring an Alarm Transmitter/Dialler](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/configuring-an-alarm-transmitter-dialler.md).

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Select the Controller you wish to assign the Alarm Transmitter/Dialler to.
3. Click the **Alarm Transmission** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e693299c08ceebdacd33bdc6d814a3d9cc73921b%2Fcontrolleralarmtransmission.png?alt=media)
4. Enter a Zone identifier (CCC) to be used for Contact ID reporting.

   **Notes:**

   * This field will accept 3 Hex digits 0-9, B-F.
   * The default of 000 can be left if you do not wish to indicate a specific zone or user information.
5. Are you assigning an IP Alarm Transmitter or an Alarm Dialler to this Controller?

   <table><thead><tr><th width="174">If an...</th><th>then...</th></tr></thead><tbody><tr><td>IP Alarm Transmitter,</td><td>from the drop-down list select the <strong>IP Alarm Transmitter</strong> you want to connect to this Controller.</td></tr><tr><td>Alarm Dialler,</td><td><ol><li>Click the <strong>Serial Devices</strong> tab.</li><li>From the drop-down list, select the <strong>Alarm Dialler</strong> you want to connect to this Controller.<br><br><strong>Note:</strong> The Controller can communicate with either an Alarm Dialler or an Elevator HLI, but not both, using the Controller serial port connection.</li></ol></td></tr></tbody></table>
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

   **Note:** If a 'Push Configuration' is performed on an IP Alarm Transmitter, then all Controllers that have an Alarm Transmitter configured will have their Alarm Transmission configuration resent. Performance on all these Controllers will be reduced for a short period of time. This should be less than a minute. Access to doors will be affected at this time. It is recommended that this is only performed at the appropriate time for the site concerned.

### Result

An Alarm Transmitter/Dialler has been assigned to a Controller.

### Next

[Configuring Items for Contact ID](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/configuring-items-for-contact-id.md)


---

# 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/external-alarm-monitoring/assigning-the-alarm-transmitter-dialler-to-a-controller.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.
