Sentinel Integration Setup

Sentinel Integration Setup

The integration with Sentinel requires the Sentinel Administrator to make a few changes to the software settings.  There are three parts to this integration.
  1. Special Instructions Setup:  This portion is what automates an operator's connection to the CHeKT video monitoring portal during an alarm.  When an operator begins processing an alarm the Special Instructions will dynamically generate the proper URL and automatically open Google Chrome and present the cameras of that customer site to the operator. 
  2. XML Integration.  This allows the CHeKT Portal and devices to transmit Contact ID Alarm signals into automation software.  The Bridge hardware has the capability to be a transmitter on a customer account, allowing your monitoring center to audit actions and system supervisory information on accounts.  See item 3 for a list of the custom alarm codes CHeKT can transmit.
  3. Create Contact ID Alarm Codes: You will need to add any of the custom CHeKT alarm codes to Sentinel.  Click here for the current code list.

1. XML Integration - Connecting CHeKT's Cloud to your Sentinel XML Receiver

In your Monitorsoft Sentinel alarm receiving software your will need to build an XML Event Processor Signaling Type for CHeKT's cloud communicator.
  1. Sentinel->Admin->Signaling Configuration->Signaling Types
  2. Create a Type
  3. Name: CHeKT
  4. LineHandler: XML Event Processor
  5. Signaling Type: Port and ID
  6. Change Network Address Label: Device ID
  7. Apply Settings
Once this is complete, you need to create the cloud XML connector from your CHeKT management portal.  dealer.chekt.com
  1. Login to your CHeKT Dealer account.  dealer.chekt.com
  2. Go to the Dealer Settings


  1. Under Integration, Select XML Alarm Receiver
  2. Press "New Receiver" in the top right.
  3. Brand: Sentinel
  4. Name & Description: User Preference
  5. Visibility:
    1. External Dealers: This connection is visible to all CHeKT Dealers.  With this option we recommend establishing a Required Passkey
    2. Sub-Dealers: This option is used only for certified resellers of the CHeKT platform.
  6. Required Passkey:  (Optional)
  7. URL: Multiple URL can be added to support failover situations.
    1. This url is the connection to your XML Receiver.  (Example: http://15.15.15.15:1313/XMLEventProcessor/Service/EventProcessor)
  8. Enable: Yes
  9. Save Settings

2. Special Instruction Setup - In Sentinel

Build global system variables in Sentinel.
  1. Sentinel->Admin->Settings
  2. Filter: url
  3. Settings
  4. Special Instruction URL Behavior: Open in Default Browser
  5. Special Instruction Token 1:  https://monitoring.chekt.com/monitoring?site={UserReference}&zone={ZoneNumber}   
  6. The values in the Token string are case sensitive.  
  7. Apply Settings


Apply Special Instruction Token to a customer. 
  1. Open Customer Record
  2. Go to Actions
  3. Special Instructions Tab
  4. In the Special Instructions URL use: {Token1}
  5. Save Settings
  6. Now this Special Instruction can be applied based on the monitoring center preferences.
  7. *(This step must be done on each new CHeKT Customer.)


Once the above steps are complete you can proceed to 
  1. CHeKT Contact ID Codes
  2. Setting up your first customer.

Sentinel Monitoring Station Notes:
  1. Monitoring station will need to add the Contact ID codes for CHeKT and the default zone definitions used in the Sentinel Zone Templates used for each CHeKT Account.
  2. Each Bridge registered to a customer in the CHeKT Portal communicates as a zone number; 901, 902, 903....
Special Note:  Sentinel will reject communcaiton is zone numbers contant leter values.
  1. Each camera registered to a Bridge has a default zone number of 901A, 901B, 901C, 901D.  Sentinel does not support letters in the zone number field and these defaults must be changed.
If your central monitoring station needs to incorporate the CHeKT Alarm codes into Event Translations Codes, you will need to contact Sentinel.
Sentinel Website Support
  1. https://docs.monitor.uk/sentinel/v/3.141/administrator-guide/signalling/cctv-and-audio-systems/chekt-also-optex-bridge

    • Related Articles

    • MicroKey Integration Setup

      The integration with MicroKey has three specific requirements. Setting up your CHeKT Cloud Connetion to MicroKey. - Information Below Setting up you MicroKey Action Plan - Click Here Adding CHeKT Contact ID Codes to MicroKey - Click Here Setting up ...
    • Dice Integration setup

      The integration with Dice has two specific requirements.  Setting up a subscriber account to access CHeKT during an alarm, and  setting up the the DICE XML Receiver. 1. Setup CHeKT Video on a Subscriber Account Go to Data Entry Select the Add Ons Tab ...
    • Patriot Integration Setup

      (Version 6.9 or newer required) A receiver URL:Port can be defined in the CHeKT Dealer Portal under the "Gear;" the customer will open a path through the firewall into the server for their selected Port. Patriot will need to assist with this ...
    • MASterMind Integration Setup

      With MASterMind there are two levels of integration. (Version 6.44 or newer required) Launching the CHeKT portal when an alarm is received Receiving XML Signals from the CHeKT Portal Launching CHeKT from MASterMind There are a few steps necessary to ...
    • Bold Integration Setup - URL Launch & XML Receiver

      The integration with Bold has two specific requirements.  Setting up an Action Pattern and your XML Receiver.  Once this is complete you will connect the CHeKT XML Server to your XML Receiver. 1. Bold XML Receiver Setup You will need the Bold FEP or ...