> 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/setting-up-contact-id.md).

# Setting up Contact ID

### Introduction

This topic is separated into four individual procedures that make up the process for setting up Contact ID, as follows:

#### 1. Setting the Country Code

Setting the Country Code for an Alarm Transmitter/Dialler is done once you have physically connected the Alarm Transmitter/Dialler to the Controller. There are two methods for setting the country code, therefore use the method applicable to your situation. Either:

* via the Controller Diagnostics web page, or
* if circumstances do not permit for you to use the web page, the modem can be connected via a serial cable.

Refer to [Setting the Country Code](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/setting-the-country-code.md) for both procedures.

#### 2. Creating an Alarm Transmitter/Dialler Output (optional)

If you want to receive visual or audible acknowledgements when Alarm Zone armed messages are received by the monitoring company, an output(s) needs to be created for the Alarm Transmitter/Dialler.

**Notes:**

* More than one output can be configured for the Alarm Transmitter/Dialler, (e.g. an audio output and a visual output).
* Ensure you set the output to pulse when activated.

Refer to [Creating Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md) for the procedure.

#### 3. Configuring an Alarm Transmitter/Dialler

An Alarm Transmitter/Dialler gets configured in Command Centre, and is required to dial the monitoring company in three basic situations:

* When an alarm occurs or restores.
* When an Alarm Zone changes state between armed and any other state.
* Periodically to indicate that the Transmitter/Dialler is still functioning.

Refer to [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) for the procedure.

#### 4. Assigning the Alarm Dialler to a Controller

Once an Alarm Transmitter/Dialler is configured, it needs to be assigned to a Controller in Command Centre.

( **Note:** Contact ID messages will be lost if a Controller is restarted for any reason.)

Refer to [Assigning the Alarm Transmitter/Dialler to a Controller](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/assigning-the-alarm-transmitter-dialler-to-a-controller.md) for the procedure.

#### 5. Configuring Items for Contact ID

The items that are required to report Contact ID events need to be configured to do so by assigning CCC codes to them, and if you wish, CCC codes to card users who set and unset alarms.

The Alarm Zones that will be used for Contact ID also need to have GG codes assigned to them.

**Note:** Each Alarm Transmitter/Dialler must have a separate Alarm Zone for its reporting.

Lastly, you need to select which Action Plan will have an Alarm Transmitter/Dialler assigned. This action will start alarm dial out to the Monitoring Company.

**Note:** When setting the Action Plan to use an Alarm Transmitter/Dialler, ensure that the corresponding XYZ value is appropriate, as some of the Command Centre defaults may not be appropriate to your Monitoring Company.

Refer to [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) for the procedure.


---

# 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/setting-up-contact-id.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.
