EvTrack is a software Eco-system designed for visitor management and physical access control and supports 2N Access Control and Intercoms.
Tested Configurations
Device | Required License | RFID | PIN | Call Main Button 1 | Access Time Profile | Validity |
---|---|---|---|---|---|---|
2N Access Unit 2.0 | - | Yes | Yes | - | Yes | Yes |
2N Verso 1 Button with Keypad and RFID | 2N Enhanced Integration (Part No. 9137907) | Yes | Yes | Yes | Yes | Yes |
Please make sure to configure a valid NTP Server under Devices > New. Without a valid NTP server scheduling and event log will be unreliable. By default, EvTrack server will try and configure “pool.ntp.org”
Step 1: Configure 2N Device API Access
Enabled HTTP API Services
a. Connection Type: Secure (TLS)
b. Authentication: Digest
Configure an API Account:
a. Specify a Username/Password
b. Select the Required User Privileges
Step 2: Configure the device under Configuration > Devices
a. Select Device Type as “2N Helios Unit API Driver”
b. Complete Fields
i. Device Name (Logical Name)
ii. Device Address (IP Address or Hostname)
iii. Device Port (HTTPS Port of the 2N Device. Default: 443)
iv. Device Username (Configure API Username)
v. Device Password (Configure API Password)
vi. Timezone (Timezone of the device used for scheduling)
vii. NTP Server (Specify an NTP server that is accessible by the 2N Device)
Step 3: Confirm the device connection status
Once the device has been added the system will try and connect and display the connection status under the “Status” column. Please refer to Annex A - Troubleshooting if the device is Offline or Authentication Failed.
Step 4: (Optional) Map a Person Office Extension to Intercom Calling Button 1
2N IP Intercoms are capable of making direct IP calls, without a PBX. For Direct Dialing applications fill in the "Telephone Other" field in format "sip:ip_address" or "sip:x@ip_address"
Status | Description | Troulbleshooting |
---|---|---|
Online | The device is connected and receiving log events. | - |
Offline | The device is offline. | - Check Device is physically installed. |
- Check Device IP Address and Port. | ||
- Check Device has power. | ||
N/A | Device is Disabled. | - Enable Device. |
Authentication Failed | Unable to authenticate device. | |
- Make sure u are not using the device admin credentials. | ||
- Ensure that Digest Authentication has been enabled | ||
- Ensure HTTPS is enabled. | ||
- Ensure that the Device has the correct Licensing (ie. 2N Enhanced Integration(Part No. 9137907) | ||
- Ensure that function is enabled. |