CMS Connection

On Ajax integrations with the Central Monitoring Stations


By default, a hub sends events and alarms to the security company monitoring station via the SIM card only once. If an error occurs during transmission, an event or alarm will not be delivered, and Not connected status will be displayed in the Monitoring Station field in the screen of hub states. Such errors can occur due to the router settings used by the security company.

For your hub to ignore errors and re-send events to an ARC, enable the Ignore network registration errors and Disable communication check with the operator in the hub settings. You can do this in the Ajax apps:

  1. Devices
  2. Hub
  3. Settings
  4. Cellular

After enabling these options, click Back to apply the settings. If events are still not sent, please contact our Support Service.


With OS Malevich 2.9 update, when the panic button is pressed in the app, not only the event but also the smartphone coordinates are transmitted to the security company. System users can copy the coordinates from the events feed.

ajax mob app

The panic button is available in the space regardless of the hub presence.


Yes, it does.

To configure the communication of alarms and events from the hub to the ABsistems CMS, in Ajax Translator use the Manitou protocol and setup next Ping string: <?xml version=”1.0″?><Heartbeat/>

ajax support absistems

Yes, it does.

To configure the communication of alarms and events from the hub to the SBN CMS, use the SBN protocol in Ajax Translator.

ajax support sbn

Ajax PRO Desktop supports photo verification without additional settings.

Photo verification is also supported by:

  • Manitou
  • ABsistemDC(NG)
  • WBB
  • Horus
  • V1/F1
  • Kronos
  • eLipse
  • Sentinel
  • SoftGuard
  • MASterMind
  • Stages
  • SBN
  • Listener
  • LISA
  • AM/Win system

To configure photo transmission, please use Ajax Translator version 1.10 or later.

At the same time, photo verifications are accepted by all CMSs that support SIA, ADEMCO 685 and Contact ID protocols.



The second IP address is a backup in case of direct connection to the Central Monitoring Station (CMS).

If the main IP address is not available, the hub uses the second IP address to send events.


The direct connection (Monitoring Station tab) is the channel used to transmit hub events directly to the Central Monitoring Station (CMS) of the security provider, bypassing our server.

When direct connection is used, all events are communicated directly to the security company’s central monitoring station without affecting the functioning of the Ajax apps. If the direct connection is lost for any reason, the server acts as a redundant communication channel.


Featured articles

How to configure a space

TLS update for Ajax Translator users

What is Photo on Demand and how it works

Spelling error report

The following text will be sent to our editors: