> 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-software/configure/alarm-transmission/alarm-transmission-monitoring.md).

# Monitoring

Configure, test, and troubleshoot alarm transmission to a monitoring station.

For an input to generate a Contact ID event that reaches a monitoring station, all of the following must be in place:

1. A **Controller**
2. A **Dialler** (IP or Analog) with a monitoring station configured and an **Account**
3. An **Alarm Zone** connected to the controller, with a **Group Identifier (GG)** configured. Selecting the Alarm Transmitter under the alarm zone's **Connections** makes it send Arm/Disarm messages to the monitoring station.
4. An **Input** with a **Zone identifier (CCC)** configured
5. An **Action Plan** that triggers an event of **Very Low Priority or higher** and has the dialler selected

![Minimum monitoring config showing the dialler and monitoring account](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-166f57cab77a0f57ad703543bca72aac2280cd5b%2FSECHUB-CCS-ALARM-monitoring-01-min-config-dialler-account.jpg?alt=media)

![Alarm zone with a Group Identifier configured](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5e091e150b3e559295ae32f965c39a02dd2d7145%2FSECHUB-CCS-ALARM-monitoring-02-alarm-zone-group-id.jpg?alt=media)

![Input with a zone identifier configured](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-826c5541a8688a61ea9197d7d4fdb30be433f858%2FSECHUB-CCS-ALARM-monitoring-03-input-zone-id.jpg?alt=media)

![Action plan with the dialler selected](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b33d6e6a6eb7adafd81cb852f0ea449008b824dc%2FSECHUB-CCS-ALARM-monitoring-04-action-plan-dialler.jpg?alt=media)

***

### Place the action plan

The action plan can be assigned at three locations, each with a trade-off:

| Location               | Pro                                      | Con                                           |
| ---------------------- | ---------------------------------------- | --------------------------------------------- |
| **Server Properties**  | Single set up                            | Entire system behaves the same                |
| **Alarm Zone**         | Quicker to set up                        | Everything on the alarm zone behaves the same |
| **Device** (the input) | Precise control of each item's behaviour | Takes a lot of time to configure              |

You can mix and match. There is a priority order when more than one applies:

1. Highest priority: configuration on the **Device** (the input, in this example)
2. Middle priority: configuration on the **Alarm Zone**
3. Lowest priority: configuration at **Server Properties**

So a setting on the alarm zone is overridden by whatever is set at the device.

***

### Verify the configuration

Two ways to test:

* **Live test:** activate the alarm and confirm receipt with the monitoring station.
* **Report test:** in the Configuration Client / Report, create a **Contact ID report**. A correctly configured input and zone produce output similar to:

```
1,08,Remote Alarm Zone 1
3,7949,1,130,08,010,Small Input 10,Open/Off
3,7949,1,140,08,010,Small Input 10,Test Events
3,7949,1,380,08,010,Small Input 10,Input Not Triggered
3,7949,3,130,08,010,Small Input 10,Open/Off
3,7949,3,140,08,010,Small Input 10,Test Events
3,7949,3,380,08,010,Small Input 10,Input Not Triggered
```

If an alarm zone or device is **not listed** in the report, it is **not configured** to send events.

***

### Duress inputs

Configuring a device (typically an input) with a Contact ID code of **121** or **126** results in **no message being transmitted** to monitoring. These codes are linked to a **user**, not a zone (usually assigned to a door), so they do not produce a zone event.

> **For monitored duress signalling, use Contact ID code 120 (Panic) instead.** See [Alarm Transmission - Ademco Format](/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-ademco-format.md) for the full code list.


---

# 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-software/configure/alarm-transmission/alarm-transmission-monitoring.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.