CMS Connection

You can use an empty space for 180 days from the date the space was created or from the date the last device was deleted. After this period, an empty space will be deleted.

To avoid space configuration loss, the system sends a notification after 173 days from the date the space was created or from the date the last device was deleted.

The system will delete the empty space even if it is armed. The user can delete the empty space only when the system is disarmed. When the space is deleted (automatically or manually), its events are also deleted.

You can create and use a limited number of empty spaces. Ajax space is empty when no Ajax hub, Ajax camera, Ajax NVR video recorder, or Yale smart lock is added.

You can create and use:

• 100 empty spaces as a user,
• 1000 empty spaces as a PRO or a company.

If a space is empty, you cannot arm it or use the panic button in Ajax apps.

You can still create and use an unlimited number of spaces with devices.

Yes, you can delete the offline hub from armed space. This can be helpful if the hub fails while the system is armed and there is no way to replace the hub using data transfer. If the hub is removed from the space, the user can continue to use Ajax cameras, Ajax NVR video recorder, and Yale smart lock added to the space.

Admin or Installer with system configuration rights can delete the offline hub from armed space.

To do this, in the Ajax apps:

1. Select a space.
2. Go to the Devices tab and select the hub you want to delete.
3. Go to the hub settings by clicking on the gear icon .
4. Tap Remove hub.

You can delete the offline hub from armed space if this hub is not connected to the monitoring station.

No, when the space is deleted (manually or automatically), its events are also deleted. You cannot restore it.

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.

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/>

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 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.