Services#
Services in Access are required to select options for connecting to external systems.
All fields are required unless otherwise stated in the description.
Apacs#
This service is designed to interact with the APACS 3000 ACS.
Apacs functionality#
Main functions:
- adding devices that the biometric system will work with;
- receiving regular updates from the ACS software database;
- sending requests to add/change data in the local person storage;
- receiving identification events;
- sending a request to the ACS software about identiloginfication events;
- integration with LP5;
- integration with KBS: MTS, Alpha;
- logging of events about an attempt by an unidentified employee to pass through the turnstile.
Configuring parameters for connecting to the APACS ACS#
Service settings and possible values (Table 9):
Table 9. Setting up the APACS service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | User-defined service name | Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters. | - |
| bio_system_id | The identifier of the biometric system | - | - |
| host | IP address of the server with installed APACS software | IP address in the form X.X.X.X | - |
| port | Port on which APACS is deployed | - | 7010 |
| max_workers | Number of parallel threads for face replication | >0/10 | |
| enable_ssl | Data encryption method for network transmission. It depends on the type of network you are using. | On - https | Off |
| Off - http | |||
| login | Login of ACS software user. Input of Latin characters, numbers and symbols is supported. | User created in APACS ACS software | - |
| password | The user's password created in the APACS ACS software. | The input of Latin letters, numbers and symbols is supported. | - |
| feature_profile | The profile key belonging to the master key of the system. The key data is located in the APACS ACS software: Help → About the program | - | - |
| rabbitmq_login | Username from RabbitMQ from Apacs | The input of Latin letters and numbers is supported | - |
| rabbitmq_password | The password of the user from RabbitMQ from Apacs | The input of Latin letters and numbers is supported | - |
| card_format_source | The type of map format for uploading organization codes and their offsets. For more information, see below | - | - |
| enable_controller_creation | Enabling replication of ApacsController controllers | On - replication is enabled | On |
| Off - replication is disabled | |||
| card_priority_number | A priority marker for maps. All cards with the same priority number will have higher priority | Numeric values greater than or equal to 0 | - |
The master key can be found in any Apacs client application in the Help → About section.
The type of card format (card_format_source) can be found in any Apacs client application in the Console tab → System Root section → Hardware Server section → select a network driver → select a controller → Group: Card Format section → select any card format → General tab → field ""The type of the object"".
Bastion#
This service is designed to interact with the Bastion 2 and 3 ACS.
Bastion functionality#
Main features:
- adding devices that the biometric system will work with;
- receiving regular updates from the ACS software database;
- sending requests to add/change data in the local person storage;
- receiving identification events;
- sending requests to the ACS software about identification events;
- integration with CBS MTS;
- logging events about an attempt by an unidentified employee to pass through the turnstile.
Bastion settings#
The following settings are used when creating a new service (Table 10):
Table 10. Bastion Service Configuration
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| bio_system_id | Drop-down list for selecting the biometric system identifier (LP5 or CBS) in Access. | - | - |
| host | IP address of the server with installed Bastion software | IP address in the form of X.X.X.X or site.domain | - |
| port | ONVIF port of Bastion service | - | 10112 |
| enable_ssl | SSL encryption support for messages. It must be activated if necessary to maintain confidentiality. When activated, the load on the device and the message transmission time increases | On - https | Off |
| Off - http | |||
| username | Bastion ONVIF user login. Input of Latin characters, numbers and symbols is supported. | The user created in Bastion | - |
| password | Bastion ONVIF user password. Input of Latin characters, numbers and symbols is supported. | User password | - |
| vl_access_host | IP address of the server where Access is installed | IP address in the form of X.X.X.X or site.domain | - |
| vl_access_port | Port of the server where Access is deployed | - | 9091 |
Bolid#
The service is designed to interact with the [Bolid] ACS (../bolid#bolid-scud).
Bolid settings#
The following settings are used when creating a new service (Table 11):
Table 11. Setting up the Bolid service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| bio_system_id | Drop-down list for selecting the ID of the Luna service in Access. | - | - |
| host | IP address of the server with installed Bolid software | IP address in the form X.X.X.X | - |
| port | Bolid service port | - | 8090 |
| max_workers | Number of data replication handlers from the Luna list to Bolid. If there is a large amount of data, it is recommended to set from 2 to 5. | >0 | 10 |
| enable_ssl | SSL encryption support for messages. It must be activated if necessary to maintain confidentiality. When activated, the load on the device and the message transmission time increases | On - https | Off |
| Off - http | |||
| login | Username of the Bolid user. It is set in the Bolide software: DB → Passwords → The password type is ""Remote control"" | The user created in the bolid. The input of Latin letters, numbers and symbols is supported. | - |
| password | Bolid user password. Input of Latin characters, numbers and symbols is supported. | User password | - |
| token_ttl_sec | Time to refresh the access token (in seconds). Find the value of the TokenLifeTime field in the file ProgramData\BolidIntegrServ\settings.ini |
It is not recommended to change this Parameter | 300 |
CbsAkbars#
Used to obtain the descriptor ID in CBS Akbars from a photo.
Configuring parameters for connecting to CbsAkbars#
Service settings and possible values (Table 12):
Table 12. Configuring the CbsAkbars service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| host | IP address or LP5 domain name in CBS | IP address in the form X.X.X.X. or site.domain. | - |
| port | Port for connecting to LP5 in CBS | - | 5000 |
| enable_ssl | SSL encryption support for messages. Must be activated if privacy is required. When activated, the load on the device and the message transmission time increase | On – active | Off |
| Off – inactive | |||
| token | VisionLabs token for access to CBS. | - | - |
CbsAlpha#
It is used to get the identifier of the descriptor in CBS Alpha from a photo.
Only LUNA PLATFORM 5.10 and later is supported.
A service for synchronizing two lists from CbsAlpha. The service tracks changes in the cbs list and compares them with persons from the luna list. If there are duplicates of persons, then the duplicate is deleted from the luna list.
Setting up parameters for connecting to CbsAlpha#
Service settings and possible values (Table 13):
Table 13. Setting up the CbsAlpha service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | The name of the service specified by the user | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| host | FRS IP address in KB | IP address in the form of X.X.X.X or site.domain. | - |
| port | Port for connecting to the FRS in CBS | - | 5000 |
| enable_ssl | SSL encryption support for messages. It must be activated if necessary to maintain confidentiality. When activated, the load on the device and the message transmission time increases | On – active | Off |
| Off – inactive | |||
| username | Username of the FRS user | - | - |
| password | Password of the FRS user | - | - |
| account_id | UUID of the FRS user | - | - |
| handler_id | UUID of the handler for handling pass events, created in the FRS. | UUID of the handler | - |
| default_list_id | UUID of the ID of the FRS list that employees will be synchronized with | The ID of the list created in the FRS. | - |
| face_detection_threshold | The minimum threshold for face recognition is | 0...1 | 0.5 |
| event_receiving_mode | The mode for receiving events from LP5 (from version 5.53.0). Optional field | None - do not listen to events | websocket |
| websocket protocol using a persistent connection | |||
| webhook - HTTP callbacks. Client - Luna Platform, server - Luna Access | |||
| vl_access_host | IP address of the server on which Access is installed | IP address in the form X.X.X.X | - |
| vl_access_port | The port of the server where Access is deployed | - | 9091 |
| vl_access_basic_username | Login for interacting with Access | - | - |
| vl_access_basic_password | Password for interacting with Access | - | - |
| max_greatest_side_size | During replication, resize the larger side of the photo to the specified size, maintaining the proportions (Blank value - do not resize the photo) | -,0...1920 | - |
| cbs_list_id | ID of the EBS list of persons | - | - |
| synchronisation_interval_hours | The frequency of starting synchronization of the luna (default) list and cbs list. | Hours 0...100 | - |
CbsMts#
Used to retrieve the descriptor identifier in the MTS CBS from a photo.
Configuring CbsMts settings#
Service settings and possible values (Table 14):
Table 14. Setting up the CbsMts service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | User-defined service name | Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters. | - |
| host | FRS IP address in CBS | IP address in the form of X.X.X.X or site.domain. | - |
| port | Port for connecting to the FRS in CBS | - | 5558- |
| enable_ssl | SSL encryption support for messages. It must be activated if necessary to maintain confidentiality. When activated, the load on the device and the message transmission time increases | On – active | Off |
| Off – inactive | |||
| urn | Path to the directory of persons in CBS | - | /cbs/persons |
| token | VisionLabs token for access to MTS CBS | - | - |
| timeout | Timeout time in seconds when connecting to the service fails. It is necessary to take time if there is a large delay between servers. | The time is selected taking into account the network delay to maintain performance. | 10 |
| cert_name | The name of the certificate to connect to the CBS. Certificate storage directory `/tls/ | - | - |
CbsVtb#
Used to obtain the descriptor ID in the VTB CBS by photo.
Configuring parameters for connecting to CbsVtb#
Service settings and possible values (Table 15):
Table 15. Configuring the CbsVtb service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| auth_host | IP address or domain name of the server for obtaining the VTB CBS authorization token | IP address in the form X.X.X.X. or site.domain. | - |
| auth_port | Server port for receiving the VTB CBS authorization token | - | - |
| auth_enable_ssl | SSL encryption support for messages. Must be activated if privacy is required. When activated, the load on the device and the message transfer time increase | On – active | Off |
| Off – inactive | |||
| auth_client_id | Client ID for receiving the VTB CBS token | - | - |
| auth_client_secret | Client key for receiving the token | - | - |
| host | IP address or domain name of the CBS | IP address in the form X.X.X.X. or site.domain. | - |
| port | Port for connecting to the CBS | - | 5000 |
| enable_ssl | SSL encryption support for messages. Must be activated if privacy is required. When activated, the load on the device and the message transfer time increase | On – active | Off |
| Off – inactive | |||
| user_session_id | User session ID for sending photos for matching | - | - |
| ibm_client_id | ibm_client ID for sending photos for matching | - | - |
| system | VTB CBS system parameter. Requested from a VisionLabs representative | - | - |
| channel | VTB CBS system parameter. Requested from a VisionLabs representative | - | - |
| process_code | VTB CBS system parameter. Requested from a VisionLabs representative | - | - |
| signer_service_id | Drop-down list for selecting the CryptoPro service | Added CryptoPro service | - |
CryptoPro#
Used to sign detections before sending them for identification to the biometric system.
Configuring parameters for connecting to CryptoPro#
Service settings and possible values (Table 16):
Table 16. Configuring the CryptoPro service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | User-defined service name | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| host | IP address or domain name of the service | IP address in the form X.X.X.X. or site.domain. | - |
| port | Port for connecting to the service | - | - |
| api_key | Service access token | - | - |
| cert_serial_number | Serial number of the target certificate (you can get a list of installed certificates via API: http://host:port/docs) | - | - |
| cert_pin | PIN code of the target certificate | - | - |
| signature_type | Type of subscription being created | PKCS7 | - |
| CADES_BES |
EyelsProxy#
Configuring parameters for connecting to EyelsProxy#
Service settings and possible values (Table 17):
Table 17. Setting up the EyelsProxy service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | The service name specified by the user | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| host | IP address or domain name of the server | IP address in the form X.X.X.X. or site.domain. | - |
| port | Port for connecting to the server | - | - |
Gate#
The service is designed to interact with Gate PACS.
Configuring Gate settings#
Service settings and possible values (Table 18):
Table 18. Gate Service Configuration
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | User-defined service name | Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters. | - |
| luna_id | Drop-down list for selecting the Luna service identifier | - | - |
Luna#
The service is designed to redirect data from/to LP to external systems and devices.
Supported versions: 5.10 and higher.
Luna settings#
The following settings are used when creating a new service (Table 19):
Table 19. Setting up the Luna service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| host | IP address of the server where Luna is installed | IP address in the form of X.X.X.X or site.domain | - |
| port | Port of the server where Luna is deployed | - | 5000 |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| username | Username of the LP5 user. Filled in if account_id is not specified | - | - |
| password | The LP5 user's password. Filled in if account_id is not specified | - | - |
| account_id | UUID of the LP5 user. If specified, the username and password fields are not required | - | - |
| handler_id | UUID of the handler for working with passage events, created in Luna | - | - |
| default_list_id | UUID of identifier the LP5 list with which the employees will be synchronized | The identifier of the list created in LP5. | - |
| face_detection_threshold | The minimum threshold for face recognition is | 0...1 | 0.5 |
| event_receiving_mode | The mode for receiving events from LP5 (from version 5.53.0). Optional field | None - do not listen to events | websocket |
| websocket protocol using a persistent connection | |||
| webhook - HTTP callbacks. Client - Luna Platform, server - Luna Access | |||
| vl_access_host | IP address of the server on which Access is installed | IP address in the form X.X.X.X | - |
| vl_access_port | The port of the server where Access is deployed | - | 9091 |
| vl_access_basic_username | Login for interacting with Access | - | - |
| vl_access_basic_password | Password for interacting with Access | - | - |
| max_greatest_side_size | During replication, resize the larger side of the photo to the specified size, maintaining the proportions (Blank value - do not resize the photo) | -,0...1920 | - |
LunaAceConverter#
Service for sending data received from LUNA ACE devices to LP5. The received request from the device is redirected to the RRL, then a response is generated for the device based on the received response from the LP5.
Supported version LUNA ACE 1.2.23
LuaAceConverter settings#
The following settings are used when creating a new service (Table 20):
Table 20. Setting up the LUNA ACE service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| luna_id | Drop-down list with Luna service IDs in Access | - | - |
Setting up LUNA ACE#
1․ Connect to the device via SSh.
2․ Open the file: vi /opt/luna_ace/ace_device.conf .
3․ Specify the URL of the LunaAceConverter service in the luna_platform_address parameter.
To get the URL of the service, you need to go to the created LunaAceConverter service in Access and copy the full path from the browser search bar:
http://<ip_address>:9092/service/<UUID>
4․ Change to the directory: cd /opt/luna_ace/services/ace_device
5․ Restart the device: restart
LunaCars#
Software and hardware integration required for communication between LUNA CARS and barriers (boom barriers, sliding gates, bollards, and others) for vehicle access control.
Supported LUNA CARS modules:
- LUNA CARS API: v.4.0.15;
- LUNA CARS Stream: v.3.0.20;
- LUNA CARS Analytics: v.4.0.8;
Access links to LUNA CARS Analytics backend.
Events in the queue are of type CarDetectionEvent.
LunaCars settings#
The following settings are used when creating a new service (Table 21):
Table 21. Setting up the LunaCars service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| host | IP address of the server where LUNA CARS is installed | IP address in the form of X.X.X.X or site.domain | - |
| port | Port of the server where LUNA CARS is deployed | - | 8080 |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| api_port | Port of the server where LUNA CARS API is deployed | - | 8100 |
| login | LUNA CARS Analytics administrator login. Input of Latin characters, numbers and symbols is supported. | - | admin@test.ru |
| password | LUNA CARS Analytics administrator password. Input of Latin characters, numbers and symbols is supported. | - | admin |
| event_expiry_time | After how many seconds events can be skipped as obsolete. It is necessary to reduce the time to ~15 seconds if the vehicle flow is constant | >10 | 60 |
| min_license_plate_accuracy | Minimum accuracy of vehicle registration plate recognition | The value is formed at the design stage and corrected at the testing stage (0,00...1,00) | 0,6 |
| event_memory_time | Time during which the service does not create a repeat event for the same vehicle (in seconds). It is necessary to increase the value if the vehicle stands in the recognition zone for a long time in the queue for entry, etc. | 60…180 | 90 |
| timeout | Timeout for an unsuccessful attempt to connect to the service. It is necessary to increase the time if there is a large delay between servers | The time is selected based on the delay in the network to maintain performance | - |
LunaStreams#
A service for working with LunaStreams.
LUNA Streams is a service of VisionLabs FaceStream.
The service is designed to:
- receive a list of stream names from LUNA Stream for subsequent transmission to the ACS;
- generating a detection event based on a frame from LUNA Stream for subsequent sending for matching to Luna, CbsMts or CbsAlpha.
Supported version is:
- FaceStream 5.1.6 or newer;
- LunaStreams 0.2.1 or newer.
Configuring LunaStreams settings#
Service settings and possible values (Table 22):
Table 22. Setting up the LunaStreams service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | User-defined service name | Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters. | - |
| host | IP address of the server with installed LunaStreams | IP address in the form X.X.X.X | - |
| port | The port of the server where LunaStreams is deployed | - | 5160 |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| handle_event_interval | The delay interval between receiving a detection from a single source. | 1...10 | 3 |
Parsec#
This service is designed to interact with the Parsec ACS to ensure the passage of recognized persons through a turnstile/door with a magnetic lock.
Parsec functionality#
Main features:
- Transfer the list of employees to the local person storage,
- Adding/editing/deleting employees in the local person storage,
- receiving detection events from devices.
Parsec settings#
The following settings are used when creating a new service (Table 23):
Table 23. Setting up the Parsec service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| bio_system_id | Drop-down list for selecting the biometric system identifier (LP5 or CBS) in Access. | - | - |
| host | IP address of the server where Parsec is installed | IP address in the form of X.X.X.X or site.domain | - |
| port | Port of the server where Parsec is deployed | - | - |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| username | Parsec user login. Input of Latin characters, numbers and symbols is supported. | - | - |
| integration_key | The Parsec integration key. It is used as a password to connect to the service. | - | - |
| vl_access_host | IP address of the server where Access is installed | IP address in the form of X.X.X.X or site.domain | - |
| vl_access_port | Port of the server where Access is deployed | - | 9091 |
PercoWeb#
The service is designed for interaction with the [PERCo-Web] ACS (../perco#percoweb-scud).
PercoWeb functionality#
Main features:
- adding devices that LP5 will work with;
- receiving regular updates from the ACS software database;
- sending requests to add/change data to LP5;
- receiving identification events;
- sending requests to the ACS software about identification events;
- logging events about an attempt by an unidentified employee to pass through the turnstile.
PercoWeb settings#
The following settings are used when creating a new service (Table 24):
Table 24. Setting up the PercoWeb service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| bio_system_id | Biometric system identifier | - | - |
| host | IP address of the server where PERCo-Web is installed | IP address in the form of X.X.X.X or site.domain. | - |
| port | Port of the server where PERCo-Web is deployed | - | - |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| login | PERCo-Web user login. Input of Latin characters, numbers and symbols is supported. | The user created in PERCo-Web | - |
| password | PERCo-Web user password. Input of Latin characters, numbers and symbols is supported. | User password | - |
| token_ttl_min | The validity period of the security token. The value must match the PERCo-Web software, location of the PERCo-Web Manager → Settings → Advanced Settings → The lifetime of the session. | Minutes 0...10000 | 1440 (1 day) |
| - | - | max_workers | The maximum number of threads that can be used for face replication |
Rusguard#
The service is designed to interact with ACS RusGuard.
Rusguard functionality#
Main functions:
- adding devices that the biometric system will work with;
- getting regular updates from the database BY ACS;
- sending requests to add/change data in the local person storage;
- receiving identification events;
- sending a request to the ACS software about identification events;
- logging events about an unidentified employee's attempt to pass through the turnstile;
- integration with CBS is possible.
Configuring settings for connecting to Rusguard#
Service settings and possible values (Table 25):
Table 25. Configuring the Rusguard service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | The name of the service specified by the user | Any text names. Latin and Cyrillic alphabet input is supported. It is not recommended to enter more than 30 characters. | - |
| bio_system_id | Biometric system identifier | - | - |
| host | IP address or domain name of the server with Rusguard installed | IP address in the form of X.X.X.X. or site.domain. | - |
| port | The port of the server where Rusguard is deployed | - | 8089 |
| max_workers | The maximum number of streams that can be used for face replication. | >0 | 10 |
| enable_ssl | Method of data encryption during network transmission. Depends on the type of network used. | On - https | Off |
| Off - http | |||
| target_photo_number | The number of the photo in the ACS that is used for replication. | 0...100 | 1 |
| target_card_type_id | ID of the replicated card type. If the field is empty, any employee card is replicated. The available IDs of the card types are displayed in the Info block. | - | - |
| replicate_session_interval_sec | The frequency of synchronization of the ACS database and Access storage. You must specify the minimum allowed synchronization time, since Access does not receive notifications from external systems about adding/removing an employee. | Set in seconds 0...100/5 |
Salto#
The service is designed to interact with the SALTO ACS.
Configuring settings for connecting to Salto#
When creating a new service, the following settings are used (Table 26):
Table 26. Configuring the Salto service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | The name of the service specified by the user | Any text names. Latin and Cyrillic alphabet input is supported. It is not recommended to enter more than 30 characters. | - |
| bio_system_id | Biometric system identifier | - | - |
| host | IP address or domain name of Salto. | - | - |
| port | The port of the server where Salto is deployed. | - | 8100 |
| enable_ssl | Method of data encryption during network transmission. Depends on the type of network in the solution. | On - https | Off |
| Off - http | |||
| login | Login of the Salto user. Input of Latin letters, numbers, and symbols is supported. | User created in Salto | - |
| password | The password of the Salto user. Input of Latin letters, numbers, and symbols is supported. | User's password | - |
| max_workers | The maximum number of streams that can be used for face replication. | >0 | 10 |
Sigur#
The service is designed to interact with the Sigur ACS.
Sigur functions#
Main functions:
- adding devices with which LP5 and LUNA CARS will work;
- receiving regular updates from the ACS software database;
- sending requests to add/change data in LP5;
- receiving identification events;
- integration with CBS: MTS, VTB, Ak Bars;
- sending a request to the ACS software about identification events.
- logging events about an attempt by an unidentified employee to pass through the turnstile.
Setting parameters for connecting to Sigur ACS#
To add a service, you need to create it with the following settings (Table 27):
Table 27. Setting up the Sigur service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| bio_system_id | Drop-down list for selecting the biometric system identifier (LP5 or CBS) in Access. | - | - |
| host | IP address or domain name of Sigur. | IPv4 or site.domain | - |
| luna_cars_id | LunaCars service identifier in Access. | - | - |
| mark_for_ignore | When synchronizing with Sigur, if this combination is found in the body of an employee's request, the request is ignored. This option is necessary for separating different copies of Sigur in one system. | Any string value | - |
| ignore_replication_field_name | The name of an additional field responsible for ignoring during replication. The field must be of a logical type and answer the question: Ignore the employee during replication? (Yes/No) | Any string value | - |
| additional_person_field | Name of the additional field from the employee card where the descriptor ID is written | Any string value | - |
SigurThroughDatabase#
The service provides integration with the Sigur ACS through a direct connection to its database.
Access synchronizes employee data from the Sigur database, taking into account only those users who have an access card.
Upon successful identification of an employee in the Luna biometric system, Access sends his card number to the GateController or PusrController intermediate controllers physically connected to the Sigur ACS. These controllers transmit commands to open/close the passage.
Integration is carried out directly with the Sigur database, without using the API
Sigur does not initiate a connection with Access — data is transmitted only in one direction (from Access to Sigur via controllers)
Sigurthdatabase functionality
Main functions:
- adding devices with which SRL will work;
- receiving regular updates from the database on ACS;
- sending requests for adding/changing data to the SRL;
- receiving identification events;
- sending a request to the ACS software about identification events;
- logging of events about an attempt by an unidentified employee to pass through the turnstile.
LP5 Integration Options#
Each LP5 integration (Table 28) uses the Luna service.
Table 28. LP5 Integration Options
|Service |Device |Pipeline |-- |-- |------ |-- |------ |SigurThrough Database + PusrController/GateController |Beward |LunaEventListener + SendThermalEventToLuna/SendToLuna | |BioSmart |LunaEventListener + SendToLuna | |Dahua |LunaEventListener + SendToLuna | |Dahua Thermo |LunaEventListener + SendThermalEventToLuna | |Fortuna315 |LunaEventListener + SendThermalEventToLuna | |HikvisionCamera |LunaEventListener + SendToLuna | |HikvisionCamera Thermo |LunaEventListener + SendThermalEventToLuna | |HikvisionTerminal Thermo |LunaEventListener + SendThermalEventToLuna | |LunaFast4A1 |LunaEventListener + SendToLuna | |Panda |LunaEventListener + SendThermalEventToLuna | |UniUbi |LunaEventListener + SendThermalEventToLuna/ SendToLuna | |VKVision02 |LunaEventListener ||R20Face |LunaEventListener + SendToLuna
Configure settings for connecting to Sigurthdatabase#
When creating a new service, the following settings are used (Table 29):
Table 29. Configuring the Sigurthdatabase service
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | The name of the service specified by the user | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| bio_system_id | Biometric system identifier | - | - |
| host | IP address or domain name of the Sigur database. | IP address in the form of X.X.X.X. or site.domain. | |
| port | Sigur database port. | - | 3305 |
| - | - | max_workers | The maximum number of threads that can be used for face replication |
| db_username | Username used to connect to the Sigur database | - | - |
| db_password | Sigur database user password | - | - |
Strazh#
The service is designed to interact with the [STRAZH] ACS (../strazh#strazh-scud).
- Supports integration with CBS MTS.
Strazh settings#
To add a service, you must create it with the following settings (Table 30):
Table 30. Configuring the Strazh service
| Parameter | Description | Values | Default value |
|---|---|---|---|
| name | Service name specified by the user | Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters | - |
| bio_system_id | Biometric system identifier | - | - |
| login | Strazh user login. Input of Latin characters, numbers and symbols is supported. | The user created in Strazh | - |
| password | Strazh user password. Input of Latin characters, numbers and symbols is supported. | User password | - |
| host | IP address of the server where Strazh is installed | IP address in the form of X.X.X.X or site.domain. | - |
| port | Port of the server where Strazh is deployed | - | 443 |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| max_workers | The maximum number of threads that can be used for face replication. | 1-10 | 10 |
| additional_person_field | Name of the additional person field from the ACS, where the descriptor identifier will be written. | - | - |