> 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/configuring-items-for-contact-id/configuring-alarm-zones-for-contact-id.md).

# Configuring Alarm Zones for Contact ID

1. Click **Configure** from the menu bar, then **Alarm Zones**.

   The **Alarm Zone** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the Alarm Zone and select **Properties**.
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-140eb5181f441f82b7bf899448357ae9b92b3642%2Fcid_alarmzone.png?alt=media)
4. Enter a Group identifier (the GG value) to be used for Contact ID reporting.
5. If you require an individual Account code for each Alarm Zone, click the **Use this account code** radio button, and enter a four-digit Account code depending on the protocol, (i.e. DC-09 protocol requires a 4 digit Account Code and CSV protocol requires a 4 OR 6 digit Account Code).

   **Notes:**

   * 0-9 and B-F are acceptable entries for the Account code, and leading zeros are acceptable.
   * The Account code you enter on this property page overrides the site wide Account code.
   * If the Account code is left blank, when a save is attempted, the default setting will revert back to the site wide value.
6. If you require an individual Account prefix for each Alarm Zone, click the **Use this account prefix** radio button, and enter a hexadecimal Account prefix.

   **Notes:**

   * The Account prefix you enter on this property page overrides the site wide Account prefix.
   * If the Account prefix is left blank, when a save is attempted, the default setting will revert back to the site wide value.
   * CSV protocol does not use an Account prefix.
7. From the drop-down list in the Connections section, select the Alarm Transmitter/Dialler you wish to use for reporting when this Alarm Zone changes state.

   **Note:**

   With an Alarm Transmitter/Dialler selected, when the Alarm Zone state changes from armed to disarmed, Contact ID will transmit an event message, and when it changes from disarmed to armed Contact ID will transmit a restore message providing it is an event that has a 'Return to Normal' event. See [Events with Restorals](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/event-viewer/events-with-restorals.md) for a list of the events that have restorals.
8. 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.


---

# 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/configuring-items-for-contact-id/configuring-alarm-zones-for-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.
