Syslog

The panel has the feature of sending logs to the Syslog server. In this tab, you can enter data for feature functioning. The log is cleared every 182 days.

SysLog Settings

To configure sending data to the Syslog server, you need:

Log in to the entrance panel web interface. By default, the username is admin and the password is 123456.
Go to Logs > SysLog server.
Enable the feature by ticking corresponding field.
Specify a tag that will distinguish this device data from other logs.
Select the required Syslog level. Messages in the log have levels, and the selected level will allow reading messages from the initial level to chosen one. For example, if you select level 5, the server will be able to read messages from 1st to 5th levels. You can check levels of messages coming from the panel in Event types table (Severity column).
Enter Syslog server address in URL field.
Indicate port required for the server work.
Submit settings.

By using the Download button, you can save the log to your device, and by clicking the Clear button, log entries will be deleted.

Message Format

The syslog message follows RFC 5424 standard.

The content of the event messages is:

EVENT:{event_type}:{arg1}:{arg2}:{argN}:{text}

Field description:

Field	Description
{event_type}	Event type identifier
{arg1} ... {argN}	Arguments characterizing the event (if any).
{text}	Readable description of the event in free form. Free to use: inside this field.

For example, the Door opened by general access code event might look like this:

EVENT:100:0000:
Door opened by general access
code:0000

where, 100 is an identifier of Door opened by general access code event, 0000 is an event argument (in this case, the key that opened the door) and, further, a free-form description of the event: Door opened by general access code: 0000.

SysLog example

Event types

Table with event types and their parameters:

ID	Description	Parameters	Facility	Severity	PRI
000	Any events not listed below		8	6	70
100	Door opened by general access code	Code number, door number	8	6	70
101	Door opened by access code	Code number, apartment number, door number	8	6	70
102	Door opened by card	Card number, apartment number, door number	8	6	70
103	Door opened by UKEY	Card number, apartment number, door number	8	6	70
104	Door opened by Face identifier	Face ID, apartment number, door number	8	6	70
105	Door opened by exit button		8	6	70
106	Door opened by call host	Subscriber number, apartment number, door number	8	6	70
107	Door opened from the web interface	Door number	8	6	70
108	Door opened by remote server	Door number	8	6	70
109	Door opened by free access button
110	Door opened by QR code	QR number, apartment number, door number	8	6	70
111	Access denied via multi factor access	One identifier	8	6	70
112	Access denied via multi factor access	Two identifiers	8	6	70
113	Access denied via multi factor access	Three identifiers	8	6	70
114	Access denied via multi factor access	Four identifiers	8	6	70
115	Access denied via multi factor access	Five identifiers	8	6	70
116	Access granted via multi factor access	One identifier	8	6	70
117	Access granted via multi factor access	Two identifiers	8	6	70
118	Access granted via multi factor access	Three identifiers	8	6	70
119	Access granted via multi factor access	Four identifiers	8	6	70
120	Access granted via multi factor access	Five identifiers	8	6	70
121	Access denied to identifiers without linkage to user	Identifier number, identifier type	8	6	70
122	Access granted by valid license plate	Plate, car owner, lock number	8	6	70
123	Access denied by invalid identifier plate	Plate, car owner	8	6	70
124	Access denied by unknown identifier plate	Plate	8	6	70
125	Cannot access lift module	User, error message	8	6	70
126	Successful lift call	User, destination area, lift name	8	6	70
127	Failed to call the lift	User, destination area, error message	8	6	70
128	Access granted for shared identifier	Identifier number	8	6	70
129	Access denied for shared identifier	Identifier number	8	6	70
200	The door is not closed for more than N seconds	Time in seconds, how long the door has been open	8	6	70
201	Door was closed		8	6	70
202	Door was opened with door sensor	Sensor type	8	6	70
203	Door was closed with door sensor		8	6	70
204	Door was opened with enter button		8	6	70
300	Unknown card/UKEY was used	Card number	8	6	70
301	Unknown access code was used	Code number	8	6	70
302	Invalid card was used	Card number, apartment number	8	6	70
303	Invalid access code was used	Code number, apartment number	8	6	70
304	Invalid UKEY was used	UKEY number, apartment number	8	6	70
305	Invalid Face ID was used	Face ID number, apartment number	8	6	70
306	Access denied by remote server		8	6	70
307	Invalid QR code was used	QR number, apartment number	8	6	70
308	Unknown QR code was used	QR number	8	6	70
309	The lock is open on alarm	Lock number, unlock time in seconds	8	6	70
400	SIP registration OK		8	6	70
401	SIP registration lost		8	6	70
402	Device booted		8	6	70
403	Email sent successfully	Recipient email, event ID	2	6	22
404	Email not sent	Recipient email, event ID	2	6	22
500	Outgoing call	Subscriber number, apartment number	8	6	70
501	Incoming call	Subscriber number	8	6	70
502	Outgoing call failed	Subscriber number, apartment number	8	6	70
600	Login to the web interface		10	6	86
601	Failed login attempt to the web interface		10	6	86

App Name

In addition, the log entry contains information about the model, software version and MAC address of the device.

Field format:

TAG:{model}_{version}_{mac}

Field description:

Field	Description	Example
TAG	Device tag (optional)	Panel near the road
{model}	Model name	AA-07B
{version}	Firmware version	3.5.0
{mac}	MAC address without separators	706979EEEEEE