# Overview This guide explains how to configure an alarm panel to send Contact-ID or SIA messages to a Milestone XProtect server using the ORBNET Event Gateway. It covers prerequisites, configuration steps on both the alarm panel and the XProtect server, firewall and port considerations, and verification steps. ## Prerequisites - Administrative access to the Milestone XProtect server (ability to install software and restart services). - Network access to the alarm panel (IP address and ability to configure its alarm messaging). - The alarm panel’s account number (also called account ID) and a list of alarm points (names, types, and zone assignments). - Access to the server firewall or a person who can create firewall rules. - Optional: A floor plan image (PNG or JPEG) showing the area covered by the alarm panel (useful for mapping alarms to locations in XProtect). # STEPS ## Step 1 - Prepare the ORBNET Event Gateway 1. Download the ORBNET Event Gateway installer ahead of time so it’s ready for installation. - Event Gateway - Downloads (Create and account and download from the ORBNET website). [Event Gateway - Downloads](https://orbnetsys.com/EventGateway#downloads) 2. ORBNET Event Gateway - 30 Days trial license included. ## Step 2 - Configure the Alarm Panel 1. On the alarm panel’s configuration interface, locate the Alarm Message Sending settings. 2. Select the message protocol: Contact-ID or SIA (choose whichever the panel supports). 3. Set the receiver/recipient address to the IP address (or hostname if supported) of the XProtect Management Server. 4. Note the TCP/IP port the panel uses to send alarm messages. Record this - you’ll need it when configuring Event Gateway and the server firewall. 5. Record these panel details: - Panel IP address - Account number / account ID - List of alarm points: for each point include name, type (e.g., intrusion, tamper, fire), and zone/partition - (Optional) Floor plan image file (PNG or JPEG) ## Step 3 - Configure the Milestone XProtect Server 1. On the XProtect server, confirm which TCP port will be used to receive Contact-ID/SIA messages. Typically this is a TCP port (confirm from your alarm panel settings). - If the panel uses a default port, note that value. If you choose a custom port, record it. 2. Create a firewall rule to allow incoming connections on the chosen TCP port: - Allow inbound TCP traffic to the XProtect server IP on the port the panel uses. - Restrict the rule to the alarm panel’s IP (or subnet) where possible for added security. 3. Install the ORBNET Event Gateway: - Run the ORBNET Event Gateway installer on the Milestone XProtect server. 4. After installation, you will need to restart the XProtect Event Server service to apply changes. Make sure you have rights to restart services or coordinate with your administrator. ## Step 4 - Add the Alarm Panel in ORBNET Event Gateway 1. Open Event Gateway management interface. 2. Asd a new Event Gateway Receiver: - Set the receiver type to handle Contact-ID and SIA messages. - Under “General” (or equivalent settings), configure the receiver to listen on the TCP port you recorded from the alarm panel. - Configure any additional settings (e.g., allowed source IPs, timeouts) to match your environment and security best practices. 3. Save the receiver configuration. ## Step 5 - Apply Licensing and Restart Service 1. Go to Event Gateway Licensing in the Event Gateway interface. 2. Apply the license for the alarm panel (or for the Event Gateway instance as required by your license). 3. Save your license changes. 4. Restart the Milestone XProtect Event Server service to ensure the receiver is actively listening on the configured port. ## Step 6 - Verify Connectivity and Messaging 1. Ensure the server firewall rule is in place and active so incoming communications can reach the server on the configured TCP port. 2. On the Event Gateway Receiver page, monitor incoming messages: - Check that Contact-ID/SIA messages from the alarm panel appear in the receiver’s message log. - Confirm messages contain the expected account number and point identifiers. 3. Trigger a test alarm on the alarm panel (if possible) and confirm the message arrives at the Event Gateway. 4. If messages do not arrive: - Re-check the alarm panel’s receiver IP/hostname and TCP port. - Confirm the alarm panel is sending messages (view panel logs if possible). - Verify firewall rules and that the Event Server service is running and listening on the configured port. - Check that the Event Gateway receiver configuration matches the panel protocol (Contact-ID vs SIA) and account settings. ### Optional: Map Alarm Points to XProtect Visuals - Use your list of alarm points and optional floor plan image to map alarms to cameras, zones, or views inside XProtect for more effective incident handling. - Include zone names and camera references in the Event Gateway or XProtect alarm mapping interface if applicable. # Troubleshooting Tips - Common causes for communication failure: - Incorrect port or IP configured on the alarm panel. - Firewall blocking inbound traffic to the server port. - Event Gateway not licensed or not restarted after configuration. - Protocol mismatch (Contact-ID vs SIA) between panel and receiver. - Use packet capture (tcpdump/Wireshark) on the server to verify that messages reach the server IP and port. - Temporarily permit all incoming TCP to the port from the panel to rule out firewall/network filtering, then tighten scope once working. # Summary Checklist - [ ] Event Gateway installer downloaded - [ ] Event Gateway license available - [ ] Alarm panel IP and account number recorded - [ ] List of alarm points (names, types, zones) prepared - [ ] Floor plan (optional) gathered - [ ] Panel configured to send Contact-ID or SIA to Milestone server IP - [ ] TCP port noted and firewall rule created for inbound TCP on server - [ ] Event Gateway Receiver added and configured for Contact-ID / SIA - [ ] License applied and XProtect Event Server restarted - [ ] Incoming messages verified and successful test alarm performed