> 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/sample-messages.md).

# Sample Messages

### **Example 1: Alarm Message**

Account 1234 is reporting a Perimeter Burglary Alarm on Zone 15 of Partition 1.

The message will be sent as:

**1234 18 1131 01 015**

where:

<table data-header-hidden><thead><tr><th width="100.111083984375"></th><th></th></tr></thead><tbody><tr><td><strong>1234</strong></td><td>= The account number (1234)</td></tr><tr><td><strong>18</strong></td><td>= The message type used to identify the message as Contact ID</td></tr><tr><td><strong>1131</strong></td><td>= The Event Qualifier (1) for a new event, followed by the Event Code for Perimeter Burglary (131)</td></tr><tr><td><strong>01</strong></td><td>= The partition number (01)</td></tr><tr><td><strong>015</strong></td><td>= The zone number (015)</td></tr></tbody></table>

**Note:** The checksum has been removed from this example.

***

### **Example 2: Restoral Message**

Account 1234 is reporting a Restore of a Perimeter Burglary Alarm on Zone 15 of Partition 1.

The message will be sent as:

**1234 18 3131 01 015**

where:

<table data-header-hidden><thead><tr><th width="100.11114501953125"></th><th></th></tr></thead><tbody><tr><td><strong>1234</strong></td><td>= The account number (1234)</td></tr><tr><td><strong>18</strong></td><td>= The message type used to identify the message as Contact ID</td></tr><tr><td><strong>3131</strong></td><td>= The Event Qualifier (3) for a restoral, followed by the Event Code for Perimeter Burglary (131)</td></tr><tr><td><strong>01</strong></td><td>= The partition number (01)</td></tr><tr><td><strong>015</strong></td><td>= The zone number (015)</td></tr></tbody></table>

**Note:** The checksum has been removed from this example.


---

# 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/sample-messages.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.
