> For the complete documentation index, see [llms.txt](https://docs.callonalarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.callonalarm.io/equipment-configuration/sia-dc-09-alarm-panels-configuration.md).
# SIA DC-09 Alarm Panels Configuration
This guide explains how to configure your alarm panel to connect to CallOnAlarm using the SIA DC-09 protocol.
{% hint style="info" %}
Note: The configuration steps below are generic and apply to most alarm panels. Menu names may vary slightly depending on your manufacturer (Hikvision, Dahua, VESTA, Ajax, Paradox, DSC, etc.).
{% endhint %}
***
## Prerequisites
Before you begin, make sure you have:
* [ ] A CallOnAlarm account
* [ ] A connection created in your CallOnAlarm dashboard
* [ ] Your **Account Number** (found in your connection settings)
***
## Configuration Steps
{% stepper %}
{% step %}
### Access Monitoring Station Settings
Navigate to your alarm panel's monitoring station configuration:
```
Settings > Device > Panel > Monitoring Station
```
or
```
Settings > Network > ARC (Alarm Receiving Centre)
```
{% hint style="info" %}
Tip: Look for terms like "Monitoring Station", "ARC", "Central Station", or "Reporting" in your panel's menu.
{% endhint %}
{% endstep %}
{% step %}
### Configure Connection Parameters
Enter the following settings:
Parameter
Value
Protocol
SIA or SIA-DCS
Account Number
Your account number from CallOnAlarm dashboard
Server Address
sia.callonalarm.io
Port
5001
Encryption
Disabled / Inactive
{% endstep %}
{% step %}
### Configure Timing & Retry Settings
| Parameter | Recommended Value | Notes |
| ------------------ | ----------------------- | ------------------------------------------------- |
| Periodic Test | > 1 hour (e.g., 90 min) | Automatic test report sent to verify connectivity |
| Retry Attempts | 2 - 3 max | ⚠️ Higher values may trigger multiple phone calls |
| Retry Delay | 30 seconds | Time between retry attempts |
| Heartbeat Interval | 30 - 60 seconds | ⚠️ Only if accessible (see note below) |
{% hint style="warning" %}
Important about retries: Each successful alarm transmission may trigger a phone call. If your panel retries multiple times before receiving an ACK, this could result in multiple calls for the same event. We recommend setting retries to 2–3 maximum.
{% endhint %}
{% hint style="warning" %}
Heartbeat Interval: Most alarm panels do not expose this setting. However, if your panel allows you to configure the heartbeat interval, you **must** set it between 30 and 60 seconds. Values outside this range may cause connection issues or trigger server-side protections.
{% endhint %}
{% endstep %}
{% step %}
### Enable Monitoring
* Enable the monitoring station / ARC reporting
* Ensure the connection is set to **Active**
{% endstep %}
{% step %}
### Test the Connection
Most alarm panels include a manual test feature:
* Look for **"Test Connection"**, **"Manual Test"**, or **"Send Test Report"**
* Trigger the test
* Check your CallOnAlarm dashboard → **Events** tab
* Verify the test event appears in the logs
{% endstep %}
{% step %}
### Save Configuration
Once the test is successful:
* **Save** your configuration
* **Exit** the settings menu
* Verify the panel shows "Connected" or "Online" status (if available)
{% endstep %}
{% endstepper %}
***
## Troubleshooting
| Problem | Possible Cause | Solution |
| ------------------------------- | -------------------------- | --------------------------------------------------- |
| Connection failed | Wrong server address | Verify: `sia.callonalarm.io` port `5001` |
| Test not appearing in dashboard | Wrong account number | Double-check account number matches your connection |
| Connection timeout | Firewall blocking outbound | Ensure TCP port 5001 outbound is allowed |
| Encryption error | Encryption enabled | Disable encryption in panel settings |
***
## Manufacturer-Specific Guides
#### Standard Configuration (Most Panels)
Most manufacturers (Hikvision, Dahua, Ajax, Honeywell, DSC, Paradox, etc.) provide separate fields for each connection parameter:
| Field | Value |
| -------------- | ------------------------------------ |
| Server / Host | `sia.callonalarm.io` |
| Port | `5001` |
| Account Number | Your account number from CallOnAlarm |
***
#### URI-Based Configuration (VESTA and others)
Some manufacturers, like **VESTA**, require a single URI string to configure the SIA connection:
```
ip://account_number@host:port/SIA
```
**Replace the following:**
| Placeholder | Value |
| ---------------- | ---------------------------------------------- |
| `account_number` | Your account number from CallOnAlarm dashboard |
| `host` | `sia.callonalarm.io` |
| `port` | `5001` |
**Example:**
If your account number is `12345678`, the URI would be:
```
ip://12345678@sia.callonalarm.io:5001/SIA
```
> **VESTA compatible panels:** HSGW, HPGW, MZ, HMGW, and all panels supporting IP/GPRS/4G reporting.
***
## Need Help?
If you're having trouble configuring your alarm panel:
* Check the **Events** tab in your connection dashboard for diagnostic information
* Refer to the [Simple SIA over TCP Protocol](/hardware-integration/simple-sia-over-tcp-protocol.md) documentation for technical details
* Contact us at
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.callonalarm.io/equipment-configuration/sia-dc-09-alarm-panels-configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.