Milestone XProtect
This guide explains how to integrate Milestone XProtect with PADS4 to retrieve alarms. PADS4 reads data directly from the Milestone SQL Server database, allowing real-time push notifications for optimized performance.
For more details on Milestone XProtect, visit: www.milestonesys.com.
Step 1: Create Alarms in Milestone XProtect
To enable PADS4 to retrieve alarms:
- Open XProtect Management Client.
- Navigate to the Alarms category.
- Create one or more Alarm definitions.
- Specify the trigger that will raise the alarm (e.g., tripwire detection, temperature alert).
- Ensure the Alarm Definition name matches the name used in PADS4 CTRL Center under Sensors to trigger incidents.
For details on creating incidents, refer to the How to Use Sensors section.
Step 2: Configure SQL Server to Allow PADS4 Access
PADS4 does not connect directly to Milestone; instead, it reads data from the SQL Server database. This approach enables SQL Server to send push notifications when data changes, improving system performance.
Allow SQL Server Network Connections
- Ensure that the SQL Server instance used by Milestone allows network connections.
- Check for firewall settings that might block access.
Test SQL Server Connectivity
- Install Microsoft SQL Server Management Studio (SSMS) on the PADS4 server.
- Try connecting to the Milestone database using SSMS.
- If the connection is successful, SQL Server and firewall settings are correctly configured.
Step 3: Enable SQL Server Authentication for PADS4
To allow PADS4 to connect to SQL Server, enable Mixed Mode Authentication:
- Connect to SQL Server using SSMS and Windows Authentication.
- Right-click on the SQL Server instance and select Properties.
- Navigate to the Security page.
- Under Server Authentication, select SQL Server and Windows Authentication Mode.
- Restart SQL Server for the changes to take effect.
Step 4: Create a SQL User Account for PADS4
A SQL user account is required to access the Milestone database. You can create one using SSMS (Graphical User Interface) or SQL scripts.
Option 1: Create a SQL User Using SSMS
- Connect to SQL Server via SSMS.
- Expand Security > Logins.
- Right-click on Logins and select New Login.
- Enter a Login Name (e.g.,
PADS4Reader
). - Select SQL Server Authentication and set a password.
- Uncheck “Enforce password policy”.
- Set the default database to
Surveillance
.
Grant Database Permissions
- Navigate to User Mapping.
- Select the Surveillance database.
- Assign db_owner role (to allow full access).
- Optionally, assign db_denydatawriter (to prevent modifications).
Option 2: Create a SQL User Using a Script
Alternatively, you can create a user with read-only access using the following SQL script:
- Replace
<password>
with a secure password. - Execute the script in SSMS.
After execution, the PADS4Reader
account is created and configured.
Step 5: Configure PADS4 CTRL Center for Milestone Integration
- Open PADS4 CTRL Center.
- Navigate to the Sensors section.
- Add a new Milestone sensor.
- Enter the SQL Server address, database name, username (
PADS4Reader
), and password.
Once configured, PADS4 can retrieve alarms from Milestone XProtect.
Conclusion
This setup enables real-time alarm retrieval from Milestone XProtect using SQL Server notifications. The integration allows automated incident creation in PADS4 based on alarm triggers from connected cameras.
For troubleshooting, verify:
- SQL Server network access.
- Firewall settings.
- SQL authentication mode.
- User permissions in SQL Server.
By following these steps, your PADS4 system will effectively monitor and respond to Milestone alarms.