> 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/server-properties/alarm-transmission.md).

# Alarm Transmission

### Introduction

This tab enables you to assign the XYZ value of Contact ID Event Codes to Event Groups. See [External Alarm Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring.md) for an explanation of what Contact ID is, and for instructions on what else needs configuring for Contact ID.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Alarm Transmission** tab.

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

   This tab displays the default event mappings of the XYZ Event Codes for Contact ID, (i.e. the Event Groups they are assigned to).
3. Change any of the event mappings if required by clicking on the Event Group concerned and then selecting the appropriate Contact ID code from the drop-down list.

   **IMPORTANT:**

   Although these default event mappings can be changed, it is recommended you leave them as the defaults. If you do change any, all the Event Types in a Group will also be affected. See [XYZ Event Mappings](https://help.security.gallagher.com/knowledge-hub/configuration-client/appendices/xyz-event-mappings.md) for further details.
4. If you require a site wide account number to be used, enter either a four or six digit code in the **Account Code (ACCT)** field.

   * DC-09 protocol requires a 4 digit Account Code and CSV protocol requires a 4 OR 6 digit Account Code.
   * 0-9 and B-F are acceptable entries for the account code.
   * Leading zeros are acceptable.

   **Notes:**

   * If the Account Code is configured here, then all transmissions will use this account number unless it is overridden at Alarm Zone level.
   * Where DC-09 protocol is used for alarm transmission, the four least significant figures will be transmitted if the Account Code is longer than 4 digits, e.g.

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8663857fae9cb4808266d92b0915875d3f837ae2%2Fdc09_acctcode.png?alt=media) 3456 would be used.
5. If you require user identifiers (CCCs) to be non-unique (so different Cardholders can have the same user identifier), select the **Allow duplicate cardholder identifiers (Contact ID: CCC)** checkbox.

   **Notes:**

   * To deselect this check box, you must first make all existing user identifiers (CCCs) unique. Existing duplicates will not be automatically made unique.
   * To manually make all user identifiers (CCCs) unique, perform the following:
     1. Create a Cardholder Report grouped by Contact ID to identify Cardholders that have the same user identifier (CCC).
     2. Manually find and amend all duplicate user identifiers (CCCs) so that they are unique.
     3. Deselect the **Allow duplicate cardholder identifiers (Contact ID: CCC)** check box so that no future duplicates are created.
6. The **Account prefix** is for third party Alarm Receivers that support utilising the DC-09 "Line Card" station identification.

   When set to any value other than "0", the Transmitter ID (configured on the **Alarm Receivers** tab of the Alarm Transmitter properties) in the message to the receiver is no longer used and will be replaced by a combination of the **Account prefix** and the **Account Code**. This allows for an expanded range of station identifiers to be provided.

   **Notes:**

   * This is global default, which can be overridden for individual Alarm Zones, via their **Alarm Transmission** properties tab.
   * When using the Gallagher Alarm Receiver the **Account prefix** must be 0.
7. 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/server-properties/alarm-transmission.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.
