Previous page Next page
General Information
To ensure the stable and correct operation of Axxon Datacenter, the following limitations and recommendations must be met. These are divided into two categories: limitations related to the architecture of the cloud solution and settings for using SMS/email notifications. Compliance with these limitations and recommendations ensures the reliable and uninterrupted operation of Axxon Datacenter and allows you to timely receive important information about events at the facilities.
Limitations when working with the Axxon Datacenter cloud solution
The following rules apply during the initial stage of using the Axxon Datacenter cloud solution. If these rules are met, we can ensure the integrity of the system, proper licensing, and the ability to support it.
| Limitation | Comment |
|---|---|
Only AxxonSoft specialists can configure the supervisor. Independent changes to the supervisor configuration are prohibited | The supervisor is a critical component that manages the interaction of the cloud service with the Axxon One peripheral servers. Unqualified intervention can lead to loss of connection with objects and disruption of the system |
| You must not exceed the limit of cameras established for a unit. The number of cameras in each unit must strictly comply with the project documentation and the licenses acquired | Exceeding the limit can cause failures in video stream processing, incorrect analytics performance, and licensing issues |
You must create divisions within a single subscriber sequentially. You can create a new division only after you fully configured the previous division | Sequential creation is necessary for correct synchronization of configurations between the cloud service and Axxon One servers. Parallel creation can lead to data conflicts |
You must not mix different types of cameras and detectors in a single unit. If you initially create a unit for cameras with a specific set of detectors, you cannot add cameras with different detectors to it | Each unit must be homogeneous in its functional purpose. Mixing detector types disrupts the logic of event processing and can lead to unpredictable system behavior |
You must not remove the root user from the system | The root account is required for service interactions between the cloud service and Axxon One servers. Removing the root account results in a connection break and the inability to perform centralized management |
Recommendations for configuring SMS and email notifications
The Axxon Datacenter cloud solution supports sending SMS and email notifications about camera alarms. To ensure delivery of notifications, make sure the following conditions are met:
Attention!
If these conditions aren’t met, there can be delays in message delivery, message loss, or complete failure to send messages. We recommend testing notifications after configuration.
| Condition | Description |
|---|---|
| Frequency of alarm generation | Alarms must be generated less than once every 10 minutes on all cameras. Sending messages too frequently can be considered spam by email and SMS providers, leading to blocking |
| Correct time zone in the detector | The detector that generates an alarm must be configured to the correct time zone (for example, "Nighttime" if notifications are only needed at night). This prevents unwanted generation of events and sending messages outside of working hours |
| The Initiate if not active macro parameter | In the macro that sends notifications, select the Initiate if not active parameter. This ensures that the message is sent even if the detector is temporarily disabled or scheduled to be inactive |