Question 1

2N Fortis Commander - How to continue programming your site with new programming software and Access Commander 3.5

Accepted Answer

After updating the 2N Access Commander from the 3.4.2 version to the 3.5.0 version, it is not possible to use the previous software for configuring the 2N Fortis electronic locks.  Since the 2N Access Commander 3.5.0 version, it is necessary to use the 2N Fortis Commander. More information about the 2N Fortis Commander can be found in this FAQ article.  The export file from the 2N Access Commander 3.4.2 version is not compatible with the 3.5.0 version.  Also, the 2N Fortis Commander file is protected by a password for more security.    Here's the procedure for continuing with the 2N Fortis management.  Set up a 2N Fortis Commander project password in the "Settings -> Electronic Locks -> Fortis Commander -> Project file password" sectionDownload the 2N Fortis Commander from the same section and install it on the computer Download the 2N Fortis Commander project file in the same sectionOpen the project in the 2N Fortis Commander Make changes if necessaryClose the project in the 2N Fortis Commander and upload it back into the "Settings -> Electronic Locks -> Fortis Commander" section of the 2N Access Commander's web interface.

Question 2

2N Fortis Commander - overview and how to use it

Accepted Answer

Since the Access Commander 3.5 version, it is possible to configure 2N Fortis Electronic locks with the 2N Fortis Commander software. A project file needs to be downloaded from the "Settings -> Electronic locks -> Fortis Commander" section of the 2N Access Commander.  The 2N Fortis Commander software can be downloaded from the 2N Download Centre. The link is available in the "Settings -> Electronic locks -> Fortis Commander -> Download app" section of the Access Commander's web interface as well.    Every action in the 2N Fortis Commander is saved automatically and does not need to be confirmed.    Initial projects pageOpening a projectProject pageConnecting to a deviceConnected device detail page Actions pageEvents page Closing the project   Initial projects page When running the 2N Fortis Commander, it is possible to see the File and Help options (1), Instructions for opening a project/configuration file (2) and Recently opened projects with details about the files (3).     Opening a project To open a project, you can either open the project file, which was downloaded from the 2N Access Commander on your computer.  Or you can click on the Open project button and navigate to the project file, which was downloaded from the 2N Access Commander.  Either way, the 2N Fortis Commander will ask you for the password of the project file, which is set up in the "Settings -> Electronic locks -> Fortis Commander" section of the 2N Access Commander when downloading.        Project page The project page contains the information of 2N Fortis devices assigned to the Electronic locks pre-configured in the 2N Access Commander.    It is possible to search by a lock name (1), show/hide assigned doors (configured 2N Fortis devices) (2) and see the list of 2N Fortis devices (3).     When a new project from the first initialisation of 2N Fortis in 2N Access Commander is opened, there are no assigned devices at first, and they are shown as not configured.     Connecting to a device To connect to a 2N Fortis device, the computer running the 2N Fortis Commander needs to be equipped with Bluetooth.  Click on the "Connect to device" button and swipe the Lock set up & Service card to the electronic lock to enable the pairing mode. The lights on the 2N Fortis Cylinder or Handle will be blinking with a blue light.  Keep your computer close to the 2N Fortis Cylinder/Handle throughout the pairing process. Lock setup & Service cards can be created for your project in the Access Commander (Settings > Electronic Locks > Maintenance cards) section of the 2N Access Commander.     During the pairing/connecting process, it is possible to cancel it as well.    Once the 2N Fortis Commander connects to the 2N Fortis device, you will see the device's details.     Connected device detail page Actions page When connected to a 2N Fortis electronic lock with the 2N Fortis Commander, it is possible to disconnect from the device and see a few sections:  1 - Disconnect from the device 2 - Device name (if device is already assigned and configured) and the device type (2N Fortis Cylinder or 2N Fortis Handle) 3 - Device status, its serial number and firmware version 4 - Actions and Events tab - the Actions tab is shown by default 5 - Assign lock section to to assign it to the device pre-configured in the 2N Access Commander  6 - Device Lock/Unlock options  (Lock button also restore normal operation - after using Disassembly or Battery replacement buttons on 2N Fortis Cylinder) 7 - Disassembly option - available only for the 2N Fortis Cylinder to dismount the electronic lock  8 - Battery replacement option - available only for the 2N Fortis Cylinder, for removing the cylinder cover to replace the batteries  9 - Factory reset option - more information can be found in this FAQ article       Events page Each time the 2N Fortis Commander connects to the 2N Fortis device, it automatically pulls the Events from the device.  These events can be uploaded to the 2N Access Commander by uploading the 2N Fortis Commander project file back into the "Settings -> Electronic locks -> Fortis Commander" section of the 2N Access Commander's web interface.  No changes to the 2N Fortis device are necessary. Only to connect to the device to pull out the Events.     Closing the project After the changes have been made and the 2N Fortis Commander is disconnected from the devices, the information about the devices will be displayed. There is also a message display informing about the next step to upload the configuration to the 2N Access Commander.     The 2N Fortis Commander project needs to be closed so the file can be uploaded to the 2N Access Commander in the "Settings -> Electronic locks -> Fortis Commander" section of the web interface.  The project can be closed in the "File -> Close project section, and the view will be changed back to the Projects page.     Finally, after closing the 2N Fortis Commander project, it is possible to see all the projects and their dates with the option to open them again, if necessary.     When clicking on the file path of the 2N Fortis project file, the Windows file explorer is opened with the project file highlighted.     The last step is to upload the edited 2N Fortis Commander project to the 2N Access Commander in the "Settings -> Electronic locks -> Fortis Commander" section.

Question 3

2N Fortis deployment with 2N Access Commander and Fortis Commander

Accepted Answer

This FAQ article describes the initialisation and deployment of 2N Fortis Cylinders and Handles (also known as 2N Electronic locks) and configuration with 2N Access Commander.  This solution has the following prerequisites:    2N Access Commander version 3.5+At least one 2N OS device running FW version 2.50+ or 3.0+ or later, with a compatible RFID card reader (MIFARE ® DESFire® EV1/EV2/EV3 compatible) connected to the 2N Access Commander as well.For the configuration, the External RFID Card Reader 125kHz + 13.56MHz with NFC (USB) (part numbers 9137424E or 9137421E ) and the External USB driver (1.8.0 or higher) are required. It is also required to have a computer (laptop) equipped with Bluetooth and Microsoft Windows OS (recommended version 10+).   Some additional useful information: Supported cards are MIFARE ® DESFire® RFID cards EV1/EV2/EV3.2N provides MIFARE ® DESFire® RFID cards/fobs  EV3 4K (part numbers 11202601 and 11202602).One such 2N RFID access card can be used for access to up to 90 doors with the 2N Electronic locks, depending on the number of time profiles applied. However, the 2N Fortis Cylinders and Handles can be grouped so the 2N RFID access card can be used for more accesses. More information can be found in this FAQ article. If the card memory capacity is exceeded, data writing to the card will fail. A write failure event is recorded in the system access log.    Please make sure you have the External RFID Card Reader connected, the 2N Driver for External USB Readers installed, and set up with at least the following settings:      Where are credentials stored?  Unlike 2N OS IP devices, where access credentials are stored in the device, credentials for access are stored in MIFARE ® DESFire® cards as a list of allowed handles or cylinders.   How are the access rights updates made?  Information on user cards is updated by scanning the card on an RFID reader on a 2N OS device that the card is authorised for; therefore, at least one 2N OS device with a compatible RFID reader must be used.  To update information on cards, users must be authorized for that particular 2N OS device.    Table of article's content: Configuration of 2N Access Commander for 2N Electronic locks Configuring  2N Fortis devices in 2N Access Commander Configure each of 2N Electronic locks in your installation 2N Fortis Commander configuration Allowing an access to each lock in 2N Access Commander Program user cards and assign them to users Program additional maintenance cards Erase programmed card   Configuration of 2N Access Commander for 2N Electronic locks Go to the "Settings -> Electronic locks" section of the 2N Access Commander's web interface.  If there are no IP devices compatible with 2N electronic locks connected to 2N Access Commander, a message will be shown.     Add a compatible 2N OS IP device to Access Commander When a compatible 2N OS IP device is added to the 2N Access Commander, a message about the device not being configured will be displayed as well. It is because the encryption keys have not been generated in 2N Access Commander yet.  Click on the "Generate keys" button, select and confirm a Main Encryption key and continue by clicking on the "Generate" button. Note that the main encryption key is not visible in the application later on. We recommend making a copy of the selected key and storing it in a safe place.        After generating the key, the message about the 2N OS IP device configuration should disappear, and a message about encryption keys being set up should be shown (if the message about the device's configuration does not disappear, please refresh the page).  Double-check the 2N OS IP device in case the message is still showing up In case the message does not disappear even after a while or refreshing the page, please visit the configuration page of that particular 2N OS device itself and navigate to the section Hardware - Extenders (or Card reader) The Pair button associated to device's RFID reader needs to be greyed out. If it is not, click on it to pair the RFID reader in the device.     If all is set correctly, you shall see a message about encryption keys being set up in 2N Access Commander.     Configuring 2N Fortis devices in 2N Access Commander Now you need to add the 2N Electronic locks as devices to the 2N Access Commander. Initially, you need to add just a list of the names for each 2N Fortis device added.  Add the list of 2N Electronic locks to the 2N Access Commander Go to the "Devices" section, click on the +Device button, select the 2N Electronic lock option, name the lock and click on the Add button.            Add all your 2N Electronic locks and name them to suit their deployment locations or usage. After adding the 2N Electronic locks, it is possible to add the device to the correct zone (can be assigned later, after the lock is fully configured).     After all 2N Electronic locks are added to the 2N Access Commander, in the section "Devices", you can see the 2N electronic locks' status being NOT CONFIGURED.     Configure each of the 2N Electronic locks in your installation To fully configure the 2N Electronic locks with the 2N Access Commander, it is necessary to create a Lock setup & Service RFID card and export a 2N Fortis Commander project file containing a list of all your added 2N Electronic locks in 2N Access Commander, which will be imported into the 2N Fortis Commander software.   Create Lock setup & Service card First, go to the "Settings -> Electronic Locks" section and click on the Create button in the "Maintenance cards" section to create the Lock setup & Service card.     Select the Lock setup & Service option and the card expiration date, and click on Continue.     Place the MIFARE ® DESFire® card (EV1, EV2 or EV3) on the USB card reader and keep it there until the process is complete. You will hear a tone being played first and melody after a short while from the External USB RFID reader, signalling that the card is successfully configured. The pop-up window will disappear as well.     Please make sure you label the card in order to recognise what card it is later.   Export a 2N Fortis Commander project First, set up a password for the 2N Fortis commander project file.       After setting up the password, the option to download the 2N Fortis Commander and the project file will be available. After downloading the project file, please download the 2N Fortis Commander and install it on your computer.    2N Fortis Commander configuration When the 2N Fortis Commander is installed, it is possible to open the project file, which was downloaded from the 2N Access Commander on your computer.  The 2N Fortis Commander will automatically open and will ask for the password, which was created in the 2N Access Commander before the option for downloading the project file was available.      Or it is possible to open the installed 2N Fortis Commander software and open the project file which was downloaded from the 2N Access Commander by selecting the "Open project" option.     After selecting the project file, you will be asked for the password, which was created in the 2N Access Commander before the option for downloading the project file was available.     Now it is necessary to add the 2N Fortis electronic locks to the 2N Fortis Commander by connecting them to the 2N Fortis electronic locks.  Tap the service card to the electronic lock to enable the pairing mode. The lights on the 2N Fortis Cylinder or handle will be blinking with a blue light.  Pairing uses Bluetooth. Keep your laptop close to the 2N Fortis Cylinder/Handle throughout the pairing process. Service cards can be created for your project in the Access Commander (Settings > Electronic Locks > Maintenance cards) section of the 2N Access Commander.        Once the 2N Fortis Lock/Handle is paired and connected with the computer, it is possible to see the details about the device.  Now it is necessary to assign the connected 2N Fortis Handle/Cylinder to the device that was created in the 2N Access Commander. based on your preference.  Click on the "Assign" button, select the device from the list of 2N Fortis devices from the 2N Access Commander and confirm it.       After assigning the lock, the status will change to "Lock assigned", and it is possible to make adjustments (more can be found in this FAQ article).  When the 2N Fortis device is assigned and configured, you can disconnect from the 2N Fortis device.     After disconnecting, you can see a list of configured and assigned 2N Fortis devices.     To pair them with the 2N Access Commander, simply close the project and upload the same project file back to the 2N Access Commander. All changes in the 2N Fortis Commander are saved after every action.            After importing the 2N Fortis Commander file into the 2N Access Commander, the 2N Electronic locks should be shown as Configured in the "Devices" section    Allowing an acces to each lock in the 2N Access Commander Add 2N electronic locks to zones You can assign a Zone to the device if you have not done so before, and continue by assigning cards to users.       Program user cards and assign them to users When programming cards for users once the card is read in user's detail it has to be initialized specifically for 2N Electronic locks Place the MIFARE ® DESFire® card (EV1, EV2 or EV3) on the USB card reader and keep it there until the process is complete. You will hear a tone being played first and melody after short while from the External USB RFID reader signalling the card is successfully configured. The pop-up up window will disappear as well.   Do not forget to add the user to Groups.  HINT: The Zone has to be connected with Group of Users via Access Rules in 2N Access Commander in order to allow access.  Program additional maintenance cards Once a project in 2N Access Commander is generated, you can create additional Maintenance cards and select the expiration date of the card.  Please make sure you label the card in order to recognise what card it is later.   Lock setup & Service Used for switching locks to service mode and performing maintenance. Supports both factory default encryption keys (for new locks) and installation keys (for ongoing service).  Battery card This card is used for already programmed 2N Electronic Cylinders in the same 2N Access Commander project to remove the battery cover. You can check the 2N YouTube channel for a video about how to operate the Battery card.  Dissassembly card This card is used for already programmed 2N Electronic Cylinders in the same 2N Access Commander project to fix it to or remove it from the cylinder in the door.  You can check the 2N YouTube channel for a video about how to operate the Assembly/Disassembly card.    Erase a programmed card Programmed cards for 2N Electronic Locks can be erased in the "Settings - Electronic locks" section of 2N Access Commander.  Place the MIFARE ® DESFire® card (EV1, EV2 or EV3) on the USB card reader and keep it there until the process is complete. You will hear a tone being played first and melody after a short while from the External USB RFID reader, signalling that the card is successfully erased.

Question 4

2N Network Scanner - Locating 2N devices in the network

Accepted Answer

The 2N Network Scanner is a simple, freely available application for locating 2N devices in the network. After searching the network, the application shows the type, firmware version and IP address of all intercoms found on a chart. This simplifies the administration and installation of intercom systems.  Prerequisites A computer with Windows / MacOS operating systemSupported 2N devices 2N Access Commander2N Access Units2N Answering units2N IP Intercoms2N LiftIP units (not for 2N Lift8)2N SIP Speakers    Installation of 2N Network Scanner Download application from the product page and install it.   Locating 2N devices  After you run the software, it will scan connected networks and provide you with list of detected 2N devices.       If you need to rescan connected networks, please click on File - Refresh.      Or by right clicking on one device and choosing the Refresh option.       Changing IP settings of a detected 2N device Right click on the device and choose the Config option.If the device is grayed out and you can´t see the Config option,then the device does not support changing IP settings via 2N Network Scanner.     In configuration, you can change between DHCP and static IP settings.You need to confirm changes by entering a password used for the Admin user.    Browsing the web configuration of the device Double click on the detected device to browse its web configuration.    Or by right clicking on the device and choosing the Browse... option.       Filtering search results You have the option to filter search results by typing into the filter box.You can filter for IP address, serial number, display name or firmware version.

Question 5

Access Points - How to define access points in 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. Up to 2 Access Points (entry and exit) can be newly defined in 2N Access Commander for added devices.Access points are used to define the entry or exit of a zone. Their use is necessary if the device is located at the interface between two zones and allows accurate monitoring of users as they move through the zones.   Advantages    Better monitoring of user movements from one zone to another one  Possibility of using the Occupancy function  Better management of 2N Access Commander       In default the "Access points" are deactivated in the 2N Access Commander.  How to set up the access points  How to add the access points into a zone  Setting up and using multiple authentication together with the access points  Impact on Presence and Attendance    How to set up the access points In the web interface of the given unit (2N IP Intercom / 2N Access Unit ...), which has one or more modules for user authenticationgo to the Hardware > Extenders > Selected Module > Door > select Entry, or Exit, => in 2N Access Commander then Access Point 1 or 2.  Don't forget to save the settings by clicking on the corresponding button at the bottom right:   Then go to Services > Access Control > Entry Rules and Exit Rules - and verify that Access Enabled is checked if required.  Confirm again by clicking on Save at the bottom right:   In the 2N Access Commander's web interface go to the Zones section and click on the gear icon in the upper right.  Then check the "Enable access points" option to divide the used access devices (2N IP Intercom / 2N Access Unit ...)  Up to two "virtual" drives (Access Point 1 and Access Point 2) depending on whether you are at the device activated both the Entry Rules and the Exit Rules, or only one of the mentioned options (see previous point):   How to add the access points into a zone If you add a new device to the zone in 2N Access Commander after activating the "Enable access points" option (see the last point of the previous chapter).  You will see it as two different items - Entry and Exit:    You can also assign a zone for the given access points for the selected device directly in the Devices section under the given device by clicking on the field Access control - Zone Entered through Access Point 1, or ... 2 (confirm by clicking on the checkmark):     An access point to enter one zone can also be a point to exit another zone => the same access point of the given device cannot be used for entry or exit for more zones at the same time.     Setting up and using multiple authentication together with the access points Given that individual access points are now optional in 2N Access Commander, and not only entire devices, a zone-specific multiple authentication (MFA) policy can apply to both access points, including an access point to exit a given zone, which may also be for entering another zone. Therefore you can choose to apply the MFA (Multi-Factor Authentication) policy to a specific zone only to access points that allows access to that zone. In the 2N Access Commander web interface, go to the Zones > Selected Zone > Multi-factor authentication section.  Click on the desired credentials to be used for MFA (in this case Mobile Key and RFID card) and then confirm by clicking on Save at the bottom right:      Impact on Presence and Attendance     Presence - If the access points are set in 2N Access Commander accordingly, in the Presence of the given user we also see the zone and the device, in which is user currently "located":    Attendance - In the Attendance the user's "presence" ends, once he uses an access point not "leading" to any zone.

Question 6

Anti-passback - How to configure in 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.  The Anti-passback function enhances the access control system with monitoring of unauthorised re-entering of a reserved space.  STEP 1: Configure basic access for users.  STEP 2: Explanation of ACCESS POINT 1 and ACCESS POINT 2.  STEP 3: Configure ACCESS POINT 1 and ACCESS POINT 2 in devices.  STEP 4: Configure Area Restriction (Anti-passback area)  STEP 5: Add devices to Restricted AREA. Device can't be added  STEP 6: Set which ACCESS POINT is for Entry and which ACCESS POINT is for Exit There is an error message after adding the device  STEP 7: Select the Anti-passback mode  STEP 8: Anti-passback is configured STEP 9: Additional settings     Anti-passback requires:  Access Commander 3.0.1 and later (It is recommended to use the latest version) Access Commander Pro license or Unlimited license IP intercoms / Access Units with firmware 2.38 and later (It is recommended to use the latest firmware version)  At least two access readers (RFID / bluetooth / fingerprint / keypad)  No one can enter/exit area without authorization, there is no REX button, etc.  Permanent operation of Access Commander. Connection between Access Commander and devices must be ensured.       STEP 1: Configure basic access for users Before you start configuring anti-passback, you need to have users created in the system and their access assigned to the relevant doors. Without this, it won’t be possible to set up the access logic correctly.You can find the procedure in the official manual here:   STEP 2: Explanation of ACCESS POINT 1 and ACCESS POINT 2 There are two ACCESS POINTS (directions) - ACCESS POINT 1 and ACCESS POINT 2.Access Units and IP Intercoms with one reader, please set as ACCESS POINT 1 (follow STEP 3). If there are connected extension modules as well:A) All extension readers that are on the same door side as the main unit please set as ACCESS POINT 1 (the same as the main unit, follow STEP 3).   B) All extension readers that are on the opposite door side than the main unit please set as ACCESS POINT 2 (follow STEP 3).      STEP 3: Configure ACCESS POINT 1 and ACCESS POINT 2 in devices Go to device's web management. You can use Access Commander feature:        Version 3.0 or newer In your device go to section Access -> Access rules  and select ACCESS POINT 1 or ACCESS POINT 2 for access modules. ACCESS POINT 1 is substituted by "Door Entry" value, ACCESS POINT 2 is substituted by "Door Exit" value.   Door Entry, Door Exit:    "Door Entry" = ACCESS POINT 1"Door Exit" = ACCESS POINT 2    In this section you are setting: If there is only ACCESS POINT 1, please go to section Access -> Access rules, enable ACCESS POINT 1 (Entry) and disable ACCESS POINT 2 (Exit).If both ACCESS POINTS are used in the device, then please enable both ACCESS POINTS (Entry Rules and Exit Rules).If both ACCESS POINTS (Entry Rules & Exit Rules) are disabled, device can't be added to Anti-passback area in STEP 5.    At the same time you have to assign what module you set as Entry and what modules you set up as Exit.    If you are using your device for both entry and exit you need to allow both Entry and Exit and set modules you want to use for entry as entry module (or exit module) under Access -> Access rules -> Module -> Manage.  If you want to use the unit for Entry only, turn off the Exit, and assign all your modules as entry.  If you want to use the unit for Exit only, turn off the Entry, and assign all your modules as exit.   If you set up two devices, one for entry and second one for exit you can create area restriction where you have to use one for entrance and second one for exit:             Version 2.50 (LTS) or earlier Go to section Hardware - Extenders and select ACCESS POINT 1 or ACCESS POINT 2 for access modules. ACCESS POINT 1 is substituted by "Door Entry" value, ACCESS POINT 2 is substituted by "Door Exit" value.   Door Entry, Door Exit:    "Door Entry" = ACCESS POINT 1"Door Exit" = ACCESS POINT 2       If there is only ACCESS POINT 1, please go to section Services - Access control - Exit rules, enable ACCESS POINT 1 (Entry Rules) and disable ACCESS POINT 2 (Exit Rules).If both ACCESS POINTS are used in the device, then please enable both ACCESS POINTS (Entry Rules and Exit Rules).If both ACCESS POINTS (Entry Rules & Exit Rules) are disabled, device can't be added to Anti-passback area in STEP 5.      If you are using your device for both entry and exit you need to allow both Entry and Exit (ACCESS POINT 1 and ACCESS POINT 2) and set modules you want to use for entry as entry module under Access -> Access rules -> Module -> Manage and set modules you want to use for exit as exit modules.  If you want to use the unit for Entry only, turn off the Exit, and assign all your modules as entry.  If you want to use the unit for Exit only, turn off the Entry, and assign all your modules as exit.  If you set up two devices, one for entry and second one for exit you can create area restriction where you have to use one for entrance and second one for exit:             STEP 4: Configure Area Restrictions (Anti-passback area) Go to Access Commander - section Area restrictions - Area list and create restricted area for Anti-passback rule.      STEP 5: Add devices to Restricted Area. In the created Restricted area click on Add devices button:    Device can't be added    If a device cannot be added or you cannot see device after you add it to the Anti-passback area, please check in STEP 3 that at least one ACCESS POINT (Entry Rules or Exit Rules) is enabled.     STEP 6: Set which ACCESS POINT is for Entry and which ACCESS POINT is for Exit Click on configuration button and select which ACCESS POINTs (readers) are used for Entry to the area and which ACCESS POINTs (readers) are used to Exit the area:  Example:     There is an error message after adding the device Verify the device is added to the Zone - if the device was added to the restricted area but later removed from the Zone, the restriction will not work correctly.If there are "problems to be solved" as in the picture below, please go back to STEP 3 to check configuration of ACCESS POINTS ("Entry rule", "Exit rule" in devices). Make sure that all access rules on the devices are set up correctly.Make sure that all modules are correctly assigned to Entry or Exit. After resolving the issue we recommend to delete the device from the Anti-passback area and add it again.If the device is functioning correctly but still showing an error, try removing it from the Restricted Area and adding it again.If all the devices are set up correctly but still not working as expected (no anti-passback), try removing them from the area restrictions and adding them again.  STEP 7: Select the Anti-passback mode Go to Access Commander - section Area restrictions - choose your area, you want to set - "Restricted Area" (in my case):  Switch to log – no Anti-passback area access is limited if the rules are broken; the event is only logged with an optional administrator notification.  Switch to deny access – the Anti-passback area access is limited temporarily or permanently and unblocked as a result of the time limit, system administrator's instructions or exit passage.     STEP 8: Anti-passback is configured   This feature requires a permanent operation of Access Commander. Connection between Access Commander and devices must be ensured.     STEP 9: Additional settings There are additional settings for Anti-passback that you can find in Access Commander under Settings -> Anti-passback. Here you can set up which users would be exempt from Anti-passback (3) so it would not apply to them, whether you want users to be notified by email (4) if they are breaking the Anti-passback rule, or if you want area restrictions to unblock all users and reset the current count (5) of users in an area.

Question 7

Attendance and Presence - How to configure in 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.  Attendance is supposed to monitor user's arrivals and departures in 2N Access Commander.   Presence tells, whether the user is currently present on premises, and it works only in the IN-OUT Attendance mode. Presence is disabled in the FREE mode.     Attendance monitoring can be activated as an additional licensed feature for 2N Access Commander with Advanced (since the version 2.0) license or higher.     You need to have correct time settings set in devices connected to the 2N Access Commander as well as in the Access Commander itself. If not, Attendance monitoring feature may malfunction.    Go to the web interface of the 2N Access Commander.  Attendace can operate in various modes:  Free mode  IN-OUT mode for all devices  IN-OUT mode for selected devices    Free mode: Set working hours/days in the Companies → "Company" → Overview → Working time section as shown below:    Now set the FREE mode in the Settings → Configuration → Attendance section:  Last step is allowing Attendance Monitoring on each user that you wish to monitor:   It is also possible to enabled the attendance for selected users in the Users section:       IN-OUT mode for all devices: Set working hours/days in the Companies → "Company" → Overview → Working time section as shown below:  The next step is to set the access devices themselves. Go to Devices, select the device and click on Configure hardware on the device you want to configure.Then go to configuration of the device as shown below:  Now set for example the card reader for "Door Entry", as shown below, and for a wished device set then "Door Exit":  Then, Attendance needs to be set to IN-OUT for all devices:  Last step is allowing Attendance Monitoring on each user that you wish to monitor:   It is also possible to enabled the attendance for selected users in the Users section:    IN-OUT mode for selected devices: Set working hours/days in the Companies → "Company" → Overview → Working time section as shown below:  The next step is to set the access devices themselves. Go to Devices, select the device and click on Configure hardware on the device you want to configure.Then go to configuration of the device as shown below:  Now set for example the card reader for "Door Entry", as shown below, and for a wished device set then "Door Exit":  Then, Attendance needs to be set to IN-OUT for selected devices: The next step is to set the access devices themselves. Go to Devices, select the device and click on Configure hardware on the device you want to configure.Then go to configuration of the device as shown below:   Last step is allowing Attendance Monitoring on each user that you wish to monitor:   It is also possible to enabled the attendance for selected users in the Users section:

Question 8

Automatic startup of 2N Access Commander BOX after a power outage

Accepted Answer

Both 2N Access Commander BOX and 2N Access Commander BOX 2.0 can be set to automatically boot up when power is connected to it. This is particularly helpful if site where the BOX is installed encounters a power outage, so the BOX will start automatically once the power is restored. This tutorial is valid only for the hardware distribution – 2N Access Commander Box and 2N Access Commander box 2.0 Access Commander Box 2.0  If BOX is turned on, switch off the Box by short pressing the blue Power button on top of the Box.  Connect a display (VGA/HDMI/DisplayPort) and keyboard (USB) to the relevant port on the Box  Start the device boot up sequence by pressing the Power button  On the first screen press DEL to access the BIOS Utility Navigate to Advanced -> APM Configuration Select Restore AC Power Loss and pick Last State  Access commander Box  If BOX is turned on, switch off the Box by short pressing the blue Power button on top of the Box.  Connect a display (VGA/HDMI) and keyboard (USB) to the relevant port on the Box  Start the device boot up sequence by pressing the Power button:  Once BOX starts to boot up, please hit DEL or F12 button on connected keyboard.    You will enter BIOS of device, please navigate to Chipset tab and choose Power On option for parameter restore AC Power Loss    Save your changes in Save & Exit tab.

Question 9

Automation (Node-RED) in Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. In this article, we will go through the new Automation feature of the Access Commander available since the 3.2 version. The Access Commander's Automation feature is powered by the Node-RED editor, which is a programming tool for wiring together hardware devices, APIs and online services in new and interesting ways. It provides a browser-based editor that makes it easy to wire together flows using the wide range of nodes in the palette that can be deployed to its runtime in a single click. Basically, it is a low-code programming for event-driven applications.    First startAutomation statesAutomation editor (Node-RED) ExamplesFeedback  First start The Automation feature is located in the "Settings -> Configuration -> Automation" section and is turned off by default. You can enable it with the slider.         When the Automation is enabled for the first time, a new window will appear with information about the Automation feature, its examples and Access Commander-specific notes along with links for the official Node-RED documentation.  You can select to install example flows when first enabling the Automation feature. it is also possible to install the example flows later in the editor.         Once you enable the Automation feature, the state will change to Active and you can edit the flows (more about flows will be described later in this article).  It is also possible to show the window with the information about the Access Commander's Automation feature by clicking on the question mark.              You can show the Automation logs and download them in the .log format by showing more options.          Automation states There are five states of the Access Commander's Automation feature when enabled - No status, RUNNING, NOT RESPONDING, UNSTABLE and SAFE MODE.  No status When the Automation function is not enabled, the status does not show in the section and it is possible to see a "Disabled" message.        RUNNING When the Automation feature is enabled and there are no issues with the flows (more about flows later), the status of the Automation is RUNNING.         SAFE MODE The automation is enabled, but loading and running user nodes is suspended. The Automation feature makes it possible to access and fix flows or nodes which may cause instability or response issues. This mode does not persist through reboots of the 2N Acess Commander.         NOT RESPONDING The automation is running but not responding. In this state, the flows are not running. We recommend running the Automation in safe mode to check and fix possible issues. It is also possible to view logs of the automation.         UNSTABLE This state means that the automation is enabled but it is restarting frequently and the flows are not running. We recommend running the Automation in safe mode to check and fix possible issues. It is also possible to view logs of the automation.         Automation editor (Node-RED)  In this section, we will describe the Node-RED editor itself, its sections and components.  A new tab in your web browser will be opened when you click on "Open editor".         Once you open the editor you will access the editor's workspace described below.       1) On the left side you can find nodes.  Nodes are the building blocks of a Node-RED application. Each node performs a specific task, such as sending data, processing information, or interacting with an external device or service. Nodes are connected with wires.  Wires are the lines that connect nodes together. They show how data flows from one node to another.  These nodes are sectioned in groups. Most of them are standard Node-RED nodes which are explained in the Node-RED documentation. In the Access Comamdner automation, there are nodes made specifically for the Access Comamdner.  REST API - sends the defined HTTP API request. The input data contained in the body property is used as the request body of this request. The output from the node is the data from the response to the request. The selection and sorting of the output data can be specified in the Query parameter. Access log - retrieves records in the Access log and enables further processing of these records. The administrator can set up automated tasks that run when the 2N Access Commander records a defined log entry. Defining the action is done in the node settings. The output is specific data about the recorded event. A SignalR-based feature runs in the background of this feature. System log - retrieves records in the System log and enables further processing of these records. The administrator can set up automated tasks that run when the 2N Access Commander records a defined log entry. Defining the action is done in the node settings. The output is specific data about the recorded event. A SignalR-based feature runs in the background of this feature.  SignalR - reads data in the subscribed topic. Node fetches data in real-time, so it is suitable for scenarios where it has an automated task to fetch information from the 2N Access Commander without having to constantly poll. Dynamic SignalR - In comparison to the SignalR node, the Dynamic SignalR node allows for dynamic changes in data retrieval. It may be for example change of topic or a way of data retrieval based on input values. The output of this node is retrieved data from topics (Data) and also information about the success or failure of actions made by this node. Write System log - creates a record in System log in the web of 2N Access Commander. The record in the system log consists of severity, event name and event description. If any error happens during the process, it is recorded and the state of the node is updated. Node does not have any output.  2) This section is basically the "workplace" where nodes are wired making them flows. A flow is the complete set of nodes and wires that work together to achieve a task or automate a process. You can have multiple tabs for a more clear arrangement.  3) On the right side, you can see the information about the nodes, display the "Help" option and show the debug section, where the output from the flows can be exported.  4) by clicking the "Deploy" button, the flows are applied and started.  5) In the top right corner, you can see more options for the editor.    Import of flows In the top right corner click on the "burger menu" and select "Import".         Flows should be saved in a .json format. You can import the flows by writing the JSON code to the clipboard, uploading it from local storage or selecting examples by the Access Commander.         You can also select if you want to import the flow to the current flow tab or create a new flow tab. By clicking on the "Import" button, the import is finished.        Export of flows In the top right corner click on the "burger menu" and select "Export".       A new window will show where you can see all the nodes that can be exported. You can also display the JSON code of the flow.  There are two ways to export the flows.  1) You can download a .json file which can be uploaded or imported.  2) You can copy the JSON code and paste it where you need.          Examples  For more information about the examples, please, refer to the Access Commander manual at:  https://www.2n.com/en-GB/Manuals/22111/UUID-76d55fd6-6832-2275-b1ba-32d6a22f85f9   Feedback If you want to send us feedback or suggest an improvement, you can do so simply by clicking on the Please share your thoughts. link in the Automation section and a new window will appear. You can select if you want to be contacted back or not. All your feedback is reviewed by our Access Commander team. In case of technical issues, contact our technical support

Question 10

Backup and setting restore - 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. You can backup and restore setting of 2N Access Commander using its database. You can only backup or restore complete settings, all at once:  Backup and restore of settings in 2N® Access Commander  Local Backup  Samba Server backup Samba Server Configuration   Periodic Backup  Restore the backup file   Backup and restore of settings in 2N® Access Commander  Local Backup In the web interface of the 2N Access Commander go to Settings and locate "System backup":  Then click on the pencil icon in Storage, choose "Local" Storage and confirm by clicking on "Save":  Then click on "Back up now", you can set password for the back-up file, and confirm by "Save":  Then after the backup process and logging into the web interface you will see the note about a successful local backup, together with its date/time, size and version of the software:        Samba Server backup In the web interface of the 2N Access Commander go to Settings and locate "System backup":   Samba Server Configuration Following part explains how to configure the connection to the Samba server (of the Computer or Shared Network Folder) Click on the pencil icon to edit Storage, choose "SMB" Storage:Under "Server Address" input the IP Address of the Samba server (of the Computer/Shared Network Folder)Under "Login name" input the login name (of the Computer/Shared Network Folder)Under "Password" input the login password (of the Computer/Shared Network Folder)Finally confirm by clicking on "Save":  Then click on "Back up now", you can set password for the back-up file, and confirm by "Save":  After the update process and ogging back into the web interface you will see the note about a successful "Smb" backup, together with its date/time, size and version of the software:      Periodic Backup If you have set up a "Local", or "Samba", backup Storage - according to one of the previous 2 chapters, you can set to be it saving periodically. In the web interface of the 2N Access Commander go to Settings and click on pencil icon to set the Periodic backup:   Here you define the frequency (monthly / weekly / daily), day of the week and backup time. You can also set a password for the file. Finally confirm by clicking on SAVE:       Restore the backup file In the web interface of the 2N Access Commander go to Settings and click on "Restore from file". Then you click on SELECT FILE to choose the backup file from directory or drag and drop the file, fill in the backup password and confirm by clicking on the RESTORE button:

Question 11

Beta testing

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.  The nerve centre of our access control solution is 2N® Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer.   You can join beta testing of both Access Commander software and of compatible device firmware before their official release. Once 2N® Access Commander is upgraded to the latest beta version, downgrade to the preceding version cannot be performed.   Prerequisities 2N® Access Commander the latest version, no additional license is required.   Disclaimer  As part of beta testing, new 2N product software and firmware versions can be offered to you before public release. I hereby agree with the use of the test software and firmware beta version for 2N® Access Commander and supported devices and are aware of all and any functionality limitations and consequences associated with the nature of this version, and by using this version I also agree that this test version has been provided without any guarantee and that 2N TELEKOMUNIKACE a.s. shall not be held liable for function limitations and damage, if any, incurred as a result of the test version functionality limitations. I acknowledge that 2N TELEKOMUNIKACE a.s. provides the beta versions for testing purposes only.     Joining beta testing Login to web interface of 2N Access Commander and in section Settings, opt-in beta testing.     Access Commander will offer beta upgrade when available.

Question 12

Bluetooth authentication - How to configure it in 2N&#174; Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. This article describes: Pairing via connected devicePairing via external USB Bluetooth Dongle Requirements:  2N Access Commander running on the latest version2N Access Commander license: Advanced or higher2N Access Unit, IP Style, IP Verso or IP Verso 2.0 intercom with the latest firmwareMobile device that supports Bluetooth v4.0 a higher, with My2N app and active Bluetooth (and GPS location for Android phones)Optionally: external USB Bluetooth Reader dongle and 2N USB driver, which you can download here: https://www.2n.com/en_GB/products/external-bluetooth-reader-usb          Pairing via connected device Before you start: Navigate to section Companies, select one and click on it:Click the three dots button near 'Pairing devices' in the 'Mobile key' section and select 'Edit':Define which 2N device(s) with Bluetooth module can be used by users for the pairing process and saveSet the Pairing time, which defines how much time the users will have to pair their smartphone with selected 2N devices via Bluetooth. By default the time is set to 1 hour:   How to pair via Bluetooth: Go to the Users sectionCreate a new user or choose an existing user, make sure they are assigned to an Access GroupNavigate to the 'Credentials' section in the user's profileClick 'Add credential' and select My2N app:Press 'Pair using devices': You will see the pairing code along with the expiration time:Additionally, you will be given an option to send the pairing code via email by clicking the mail button:  Continue on your mobile device: Make sure that you have enabled Bluetooth and Location Services on your mobile deviceOpen My2N app and get near the selected 2N deviceClick the + button in the top right corner, then select 'Pairing PIN':          Enter the pairing PIN and click 'Next':          Click 'Start pairing':                    Once you enter the correct code, the mobile device will be assigned to your user in 2N Access CommanderYou can now gain access by using your My2N app:               Pairing via external USB Bluetooth Dongle How to pair via the USB Bluetooth Dongle:  Download and install the latest version of the 2N USB Driver here:    https://www.2n.com/en_GB/products/external-bluetooth-reader-usbConnect the USB Bluetooth Dongle to your PC and verify that you can see it connected via the USB Driver toolAfter installation, run the USB Driver and open the settings window by right clicking on the USB Driver icon:Open the 'Bluetooth Reader' folder and make sure that the dongle is listed as a device, as seen on the screenshot below:Open 2N Access Commander and go to section Settings > Credentials > Enabled USB reader:Switch on the External USB Bluetooth Reader:Go to Users section, choose a user who you want to pairClick 'Add credential' and select the My2N app:Select 'Pair using reader' to display the pairing PIN:Continue in My2N app on your mobile device according to the instructions above

Question 13

Call logs - How to use them in 2N Access Commander

Accepted Answer

Requirements: Access Commander 3.6 and later (It is recommended to use the latest version)IP intercoms with firmware 2.50 and later (It is recommended to use the latest firmware version) Please note that it might work with older firmware too but some information such as "Call duration" or "Peer" would not appear Permanent operation of Access Commander. Connection between Access Commander and devices must be ensured.   Description: Call Logs is a feature of Access Commander that allows the administrator to see what calls were made through intercoms or from outside devices to intercoms, along with related details. Note that this is only a call log and it is not possible to use this feature to actually make and store recordings of the calls. This feature enhances installation security and allows the administrator to track calls and especially doors opened through remote DTMF codes. Call logs are available for all SIP intercoms and Lift communications but not for Answering units.   NOTE: This feature is only accessible by administrator.      Information: On the Call Log page, you can see an entry for each call with multiple details about them. Please note that a new entry is shown only after the call has ended. Type - Direction of the call. It is symbolized by either blue arrow pointing down for incoming call or green arrow pointing up for outgoing calls. Time - what time was call registered Doors unlocked - if there was DTMF signal sent to unlock the door during the call Device - 2N intercom, by clicking on device name or blue icon next to it you can go directly to the device details in Access Commander Peer - Who is the source of direction of the call. It can be an user on the site where you have an option to go to the user information by clicking on the name or blue user icon next to the name or it can be sip number Duration - how long have call lasted, only shows a number if the call was successful Termination reasons - this shows the status of the call. Its can be normal when the call was successfully answered. Rejected for call that were manually rejected. No response for calls that were not picked up and Failure if some problem occurred.   By opening individual logs you can see some additional information:    Here you can find more detailed information about the call, such as: SIP Call-ID, SIP Account, Session detail, Device time.   There are available tools to filter logs, export logs and to manage columns in the top right corner.  You can filter logs based on all available attributes by setting up filters. You can then export these logs as a CSV file. There is also an option to manage the columns, where you can choose what information is displayed.        Its possible to set maximum retention time for call logs separate from other Access Commander logs and you can setup this period in Access Commander Settings -> Log retention -> Edit log retention limits

Question 14

Compatibility Mode in Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. Compatibility Mode allows 2N devices to change the way they compare RFID card IDs with the database of users. When enabled, it compares only the last 4 bytes of the card ID instead of the full ID. Some older RFID card types, such as EM Marine, may not work properly without Compatibility Mode. Enabling this feature ensures compatibility with these cards. You can configure Compatibility mode individually on each device in Services > Access Control > Advanced or through Access Commander (version 3.3 and later). How to configure Compatibility Mode in Access Commander version 3.3 and later Navigate to Settings > CredentialsClick on the blue pen icon near 'Compatibility Mode setting'Select one of the three options: Disable on all devices: Disable Compatibility Mode on all connected devices.Enable on all devices: Enable Compatibility Mode on all connected devices.Keep device settings: Retain existing Compatibility Mode settings on each device (default setting after updating to Access Commander  version 3.3)Click 'Save' How to configure Compatibility Mode in device configuration Navigate to Services > Access Control > AdvancedTick the checkbox next to 'Compatibility Mode'Click 'Save'

Question 15

CSV Import of users with their details

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. It also allows uploading of users from a CSV file, including their contact and access (code and card number) details, so you can prepare a list of users, their cards, codes, etc. to a file and then upload them to Access Commander at once.       Prerequisities  2N Access Commander the latest version   License Advanced / Pro / Unlimited for 2N® Access Commander    Feature properties  Users can be imported only to the Company, where the import will proceeded.  The function cannot delete users. One-time import is proceeded via a CSV file uploaded via the web interface. The following attributes can be imported: user name, email, 3 phone numbers, code,card number,groups,employee's ID.    If you would like to be able to also remove users and set periodic proceeding, please follow another article related to CSV synchronisation:2N® Access Commander - CSV Synchronisation to import / remove users with their details     CSV file preparing In the Access Commander's web interface, go to Companies and open your company details.     In the three dots menu select Import users from CSV.      Download the sample CSV file, after opening you can see how to enter the parameters.      For a better orientation in the CSV file you can use a Visual Studio Code editor.     Enter the parameters and save.  comma separated, no spaces;   in the case of an unused parameter, we simply do not write anything, so there will be more commas in a row depending on how many parameters we omit;   in the case of two card numbers for the same user, do not write a comma between them, but a semicolon ";"    The file can get corrupted if you save it the wrong way. It is necessary to to save it in UTF-8 coding and with EOL conversion to UNIX.            CSV file import   Let import your CSV file by clicking on the "Select file" and selecting the CSV file from your directory.Check the listed data and if all is fine, confirm by clicking on "Start import".If the data were written correctly, the users will be added to the "users" section of the Access Commander with the defined parameters.              CSV file import check in System log You can check the state of the import in System log.

Question 16

CSV Synchronization -  import / remove / update users and user's details

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. It also enables synchronisation of users from a CSV file, including their contact and access data, so you can prepare / edit the list of users, their cards, codes, etc. in the file and then synchronise it within the 2N® Access Commander.   Prerequisities  2N® Access Commander the latest version   License Pro or Unlimited for 2N® Access Commander  Optionaly your own FTP server for storing CSV file   Feature properties  Users can be imported into any Company within 2N Access Commander or deleted from it.  Synchronisation is proceeded via a CSV file uploaded via the web interface or from the FTP network storage, periodic synchronisation is supported. The following attributes can be imported: employee ID, user name, company, email, card number, code, 3 phone numbers, virtual number, groups.    CSV file preparing In the Access Commander's web interface, go to Settings - User synchronisation and download the sample CSV file.    After opening the file you can see how to enter the parameters.    For a better orientation in the CSV file you can use a Visual Studio Code editor.      Enter the parameters and save.  comma separated, no spaces;   in the case of an unused parameter, we simply do not write anything, so there will be more commas in a row depending on how many parameters we omit;   in the case of the "Group Call" and "Is Deleted" parameters, we give "TRUE" or "FALSE", depending on whether we want the next telephone number to be called in parallel with the previous one, or for the user to be or not to be deleted;  in the case of two card numbers for the same user, do not write a comma between them, but a semicolon ";"  The file can get corrupted if you save it the wrong way. It is necessary to to save it in UTF-8 coding and with EOL conversion to UNIX.     CSV file manual / automatic import from the FTP network storage Click on the pencil icon in the "User synchronisation" section to set up the synchronisation.         Enter your FTP server details together with the name and suffix of the file.If the file on the server is in a folder (e.g. "data"), the full path must be entered here, e.g. ftp://test.com/data/users.csvSince the Access Commander 3.2 version it is possible to use the TLS secure connection with the TLS certificate verification option.           Click on SAVE to proceed with the synchronisation.It is possible to set a regular automatic synchronisation once per hour / day / week and its time.     If all is right, the synchronisation is successful.    CSV file manual import via the web interface Click on the Import CSV file button and select your CSV file.      After confirmation, if the file is fine, the synchronisation is successful.    CSV file synchronisation check in System log You can check the state of the synchronisation in System log.

Question 17

Dashboard and widgets in 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.ň Since the version 2.0 2N Access Commander has a new Dashboard section, where you can add system widgets,and monitor and control various elements within 2N Access Commander according to your own needs.   Widget settings are unique for each 2N Access Commander administrator, and at the same time one widget can be added more than once, with different settings.     Overview of available widgetsAdding widget onto the DashboardMoving a widget within DashboardRemoving widgetWidget configurationWidget "Device State", "Access Logs" and "System Logs"Widget "Door"Widget "Lockdown"Widget "Occupancy" Overview of available widgets  Adding widget onto the Dashboard In the menu on the left in the 2N Access Commander's web interface, the Dashboard section is located at the very top.Click on the plus button at the bottom right and then add the selected widget to the dashboard:  Moving a widget within Dashboard To change the position of the widget, left-click on the symbol on the top left of the widget and simply drag it with the mouse:  Removing widget Click on the menu next to the given widget at the top right and select the Delete option:   Widget configuration Click on the drop-down menu next to the given widget (top right) to display its options and settings,where we can also filter what we see on the selected widget, or freely rename the widget itself:  Widget "Device State", "Access Logs" and "System Logs" In the drop-down menu they contain a filter (see the picture below), where we can select which events, or devices, will be displayed on the widget:  Widget "Door" With this widget - here (in the picture below) named IP Verso - we can also hold open the door for a different number of minutes (see picture below).In the displayed menu it is also possible to turn off the camera feed, switch to a possible external camera, go to the configuration of the given device (within 2N Access Commander) and use the Change device option to select another device for the widget.   The door can also be opened directly (or the assigned switch) on the widget using the button at the bottom right :  After loading the Dashboard, it takes some second for the camera image to load (for saving reasons it is always reloaded). Widget "Lockdown" Specified more in the relevant chapter of the following FAQ: Lockdown feature in 2N Access Commander Widget "Occupancy" Specified more in the relevant chapter of the following FAQ:

Question 18

Deep clean cookies and site data of Access Commander's webpage

Accepted Answer

This FAQ article explains how to clean cookies and cache in web browsers (Google Chrome, Mozilla Firefox, Microsoft Edge), including a deep clean using the dev console (F12).    Google Chrome Settings Dev console Mozilla Firefox Settings Dev console Microsoft Edge Settings Dev console  Google Chrome Settings  To clear cache and cookies in the Google Chrome web browser, please follow the official guide from Google.  https://support.google.com/accounts/answer/32050?hl=en&co=GENIE.Platform%3DDesktop Dev console Open the dev console by pressing F12 or right-clicking anywhere on the page and selecting "Inspect".  In the dev console, go to "Application -> Storage" section, confirm the "including third-party cookies" option and click on the "Clear site data" button.     Then show all options of the "Cookies" section and click on the "Clear" option after right-clicking on the page.  The page should be the IP address of the 2N Access Commander.     Now reload the page by clicking on the Reload button next to the address line or by pressing Ctrl+R.  Mozilla Firefox Settings  To clear cache and cookies in the Mozilla Firefox web browser, please follow the official guide from Mozilla.  https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox Dev console Open the dev console by pressing F12 or right-clicking anywhere on the page and selecting "Inspect".  Navigate to the "Storage" tab, expand the storage types (Cookies, Local Storage, etc.), and right-click the host and choose "Delete All".     Now reload the page by clicking on the Reload button next to the address line or by pressing Ctrl+R.  Microsoft Edge Settings  To clear cache and cookies in the Microsoft Edge web browser, please follow the official guide from Microsoft.  https://support.microsoft.com/en-us/windows/manage-cookies-in-microsoft-edge-view-allow-block-delete-and-use-168dab11-0753-043d-7c16-ede5947fc64d Dev console Open the dev console by pressing Ctrl+Shift+J or right-clicking anywhere on the page and selecting "Inspect".  In the dev console, go to "Application -> Storage" section, confirm the "including third-party cookies" option and click on the "Clear site data" button.     Then show all options of the "Cookies" section and click on the "Clear" option after right-clicking on the page.  The page should be the IP address of the 2N Access Commander.     Now reload the page by clicking on the Reload button next to the address line or by pressing Ctrl+R.

Question 19

Device IP Callback

Accepted Answer

Since version 3.3 of the 2N Access Commander, it is possible to configure the detection of an address change  on connected 2N IP device which are ouside of the same network segment as Access Commander is.  This function is helpful when 2N IP devices do not have a static IP address configured, and there is a possibility that the IP device's IP address changes, or with large installations where the devices are not on the same subnet.    This function can be configured in the "Settings -> Configuration -> Network -> Detect device IP address change" section of the 2N Access Commander's web interface.     Then select one or both of the options, and save the settings.   Detection via network scanner - Recommended if all devices are in the same network segment. It works within the same segment using a discovery protocol. Detection via device callback - Suitable for large networks (with many segments). The device informs Access Commander via HTTP if it knows its address (domain name or static IP). Enter the domain name or static IP address in the field below.     You need to fill in 2N Access Commander's own IP address or domain name and 2N Access Commander will configure connected 2N IP devices, so the 2N IP devices outside of the 2N Access Commander's network or subnet would stay connected to the 2N Access Commander in case of a 2N IP device's IP address changes.  For this to happen, 2N IP devices needs to be already added in 2N Access Commander (from 2N Access Commander itself) and be in online state with 2N Access Commander.  It cannot be used for devices not yet added in to 2N Access Commander.

Question 20

Device Security - Certificate Validation feature

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. Starting with Access Commander version 3.3, software now offers a new 'Certificate fingerprint validation' option as a part of the Device certificate validation feature. This option adds an additional level of security and ensures that the device that Access Commander is communicating with is an approved 2N device. This can be convenient for Access Commander users who would like to continue using self-signed certificates, just with an extra layer of security.  The default setting is 'None', which implies that the communication between Access Commander and 2N devices is still encrypted, but certificates are not being validated.  When you enable the 'Certificate fingerprint validation' option, devices with unrecognized certificate fingerprints will become unsynchronized until you manually approve them. Please see the steps on how to achieve that below. When you enable the 'Full certificate validation (PKI)' option, communication with devices will be subject of complete certificate check according to PKI rules and using this option devices will require certificates signed from trusted authorities.  How to manually approve the fingerprint certificate Before you proceed, make sure that your 2N devices are running on firmware version 2.46 or newer. In device configuration: Navigate to System > Certificates > User CertificatesLocate [Signed by Device]Click on the information button next to itCopy the Fingerprint ID and click 'OK'  In Access Commander: Navigate to Devices > SecurityClick on the blue pen icon next to 'Device certificate validation'Select 'Certificate fingerprint validation' and click 'Save'Go back to 'Devices' and select the device you earlier found and copied the Fingerprint ID ofOn the error message, click 'Review & approve'Compare the Fingerprint ID to the one you copied earlier. If it matches, click 'Approve'The device will synchronize with Access Commander in about a minute. Repeat for as many devices as necessary.

Question 21

Diagnostics logs

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.  The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time.Have you been asked by the 2N technical support team for diagnostics logs from 2N Access Commander? You can get them easily from its web interface.   Prerequisities 2N Access Commander, the latest version of the software;no additional license is required   Collecting diagnostics logs Login to web interface of 2N Access Commander and go to section Settings - Troubleshooting.Click on Generate logs button.Wait till logs are created. It may take a while in case more log information are present within 2N Access Commander.Once completed, download them to your computer by clicking on the showed button.            If you have older version of the system with different look of the web interface, please click here. Login to web interface of 2N Access Commander and go to section Settings - DIAGNOSTICS.  Click on CREATE LOGS button.     Wait till logs are created. It may take a while in case more log information are present within 2N Access Commander.      Once completed, download them to your computer by clicking the button which is green now.

Question 22

Display - How to set up display of a device in 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. If 2N IP Intercom equipped with a display is added in 2N Access Commander, the contacts on the given display are set directly in 2N Access Commander for the specified device.    Requirements Intercom: IP Vario with display, IP Verso with display module,IP Verso 2.0 with display module or IP Style. It is always recommended to use the current version of 2N Access Commander to ensure full functionality and support for the latest firmware on the device. Contacts from a group other than the one that has access to the zone where the device with the display is located are not synchronized with the device. In this case, it is necessary to create that contact in duplicate, adding it to the group with access to the zone where the device is located, and fill in only the phone number (not the access data).       Setting the display  In the web interface of 2N Access Commander, go to the Devices section and select the device   Next: Administration > Display Configuration > Configure (see image below with the red box below).   Here we can add individual items to the display depending on which button we will use here. In order for the changes to take effect on the device's display, it is necessary to click on the Save button (see the red box on the picture below).  There are elements available which allows you to add various object to display:  Create a folder (by clicking on the name of the folder you will get to it so that you can add users or a call group or another sub-folder here, again using the buttons  on the screen top right).  Create a call group (by clicking on the name of the call group you will get to it so that you can add users here - again with the given button top right). Users within such a call group will then be dialed in parallel (at once).  Add a user who is already created in the Access Commander.  Add a group already created within Access Commander. Users from the given group will be displayed individually. There also elements which allows to do certain operations with already placed objects:  Click on this button to edit the folder name, resp. calling group.   By checking these pin icons on the right, you can give priority for the contacts, moving them to top in display's contacts order.  Click on this button to remove object such as the contact from the display configuration.       Then you can see the display configuration directly in the device's detail - see the picture below.      In case of the IP Vario, the contacts of the display buttons are also configured in Access Commander - see the tab in the red box in the device's detail in the picture below.(just one contact can be selected for buttons 1 - 4, again using the pin button; by the delete button we can remove the contact then)

Question 23

Door section - configuration on the 2N IP Intercoms

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. INFO:  2N IP intercoms family contains menus "Hardware-> Digital inputs-> Door", "Services->Access Control->Entry Rules/Exit Rules" and "Services-> Integration-> Genetec Synergis"  in the web interface. These menus offer the following: Even easier configuration of the 2N IP intercoms. It concentrates all settings related to the physical door controlled by the intercom.The installer is now able to set up different global Entry and Exit rules and different global modes of authentication (double authentication via code and RFID code, triple authentication via code, RFID card and Bluetooth, and so on) instead of configuring it for each user.Configuration of the REX button.Integration with Genetec Synergis access control system.  Configuration of the Door section Go to the section "Hardware-> Digital inputs-> Door". It offers the following settings:   Door Lock This section defines which switch from the section "Hardware->Switches" is used for the physical door lock (or door strike). You also need to configure a particular switch in that section (Switch 1 in the picture). Logic in this section stays the same. You just pick a particular Switch (in our case "Hardware->Switches->Switch 1") and choose a physical output for the parameter "Controlled Output" as shown in the picture below.   Door Open Sensor In this part, you can configure all settings related to a door sensor (it can be the magnetic contact from 2N for instance, ordering no. 9159012).  Assigned Input - Choose a physical input on the intercom where is the door open sensor connected. It can be either input on the main unit itself or on a card reader or on an I/O module.Input mode - Choose between two modes of the input. "Inverted" for the normally closed button and "Non Inverted" for the normally opened button.Unauthorised Door Open Detection - Enable this checkbox to track unauthorized door opening. Once the intercom detects that the door was opened (via the assigned input and door sensor) but the assigned switch from the section "Door" was not activated, it generates an event "UnauthorisedDoorOpen" to the event log. This event can be pulled via the HTTP API and it is also visible in the 2N Access Commander which can operate with this event further. Door Open Too Long Detection - Enable this checkbox to detect when the door is opened too long (someone puts an obstacle in it's way and it can't be closed for instance). After the timeout "Maximum Door Open Time" from below is exceeded, an event "DoorOpenTooLong" is generated in the event log. This event can be pulled via the HTTP API and it is also visible in the 2N Access Commander which can operate with this event further. Maximum Door Open Time - Defines the timeout for the "Door Open Too Long Detection" checkbox. REX Button This section configures the so-called request on exit button, which allows to open the door when exiting a building. Once the button is pressed, the door is opened. Assigned Input - Choose a physical input on the intercom where the REX button is connected. It can be either input on the main unit itself or on a card reader or an I/O module.Input mode - Choose between two modes of the input. "Inverted" for the normally closed button and "Non Inverted" for the normally opened button. Genetec Synergis This section allows integration with a part of the Genetec Security Center platform and in particular with the Genetec Synergis access system. The intercom FW contains the RIO protocol of Genetec which is used for the communication with the Genetec server. If configured, the intercom forwards an ID of every swiped card (or Bluetooth and finger print if the virtual card ID is used) to the server which has a database and it verifies whether it is valid or not. Based on that, the intercom will either open the door or not.  All you need to do in this section is enabling the "Enable" checkbox and fill in the "Synergis Server Address" with the actual IP address of your server and the credentials ("Username" and "Password"). The "Connection state" shows whether the connection is established successfully or not. Section "Services-> Integration-> Genetec Synergis".   Configuration of the Entry Rules and the Exit Rules The picture below shows the layout of the "Entry Rules menu". The parameters are explained below the picture. Services->Access Control->Entry Rules".    Entry Rules This section serves for configuration of a multiple entry rules with a different authentication modes.  The authentication modes are configured globally here and it is not possible to configure it for each user.  Access Enabled -  2N Access Commander does not affect this checkbox.Access Profiles - This section allows configuration of multiple access rules. The Access Rule from the 2N Access Commander (Zone+Group+Time profile) is applied on the 1st and the 4th row. As the intercom applies the first matching rule (starting from the top), you do not have to be worried that the 4th row will enable an access 24/7 as it does not have any time profile. The time profile for the 2nd and the 3rd row is not configured by the the 2N Access Commander at the moment and you can configure it manually. Multiple authentication set for the zone is applied on this row, you can disable these rows by the checkboxes. The "Zonal code" checkbox is related to the parameter with the same name in the Advanced Settings. The checkbox enables opening of the door via this code. What this code is described below. Advanced Settings Zonal code - You can set one global PIN code for the whole Zone in the 2N® Access Commander ("Zone Access PIN code" ). This code is then filled in here. It is highly recommended to set this parameter over 2N Access Commander only! Where you can configure this code on the side of the server is shown below.    Virtual Card to Wiegand - In case you use the virtual card ID (you can add it to each user in the section "Directory->Users" and in the section "Access cards" on page of particular user), you can forward this ID to Wiegand interface by picking a group. Wiegand group for each Wiegand module can be configured in the section "Hardware->Extenders" for 2N IP Verso and in the section "Hardware->Card reader" for the other 2N IP  intercoms.  Silent Alarm Enabled - If enabled, you can add a virtual code higher by 1 then an user access code. So for instance if the access code is 0000 then the silent alarm will be triggered by 0001. You can operate with the Silent Alarm further more in the Automation section - event "SilentAlarm".Limit Failed Access Attempts - If enabled after 5 invalid access attempts it is not possible to access by any mean for 30 seconds.   Service cards Plus Card ID - Add one service card to add RFID cards to the Directory. Once you swipe the plus card any following card is added to the Directory if it is not full.Minus Card ID -   Add one service card to delete RFID cards from the Directory. Once you swipe the minus card, any following card is deleted from the Directory.    Anti-Passback System is checking where the user is according to attendance history and where the user is according to the used reader location.If those places are different, access is granted. If those places are the same, anti-passback rule has been unset.Soft mode - Anti-passback event is alerted, user can enter.Hard mode - Anti-passback event is alerted, user can´t enter. Exit Rules  Exit rules are NOT affected by the 2N Access Commander anyhow at the moment. As you can see in the picture below, the Exit rules have the same parameters as the Entry Rules. So besides the fact that nothing is being configured by the the 2N Access Commander server, everything described above for the Entry rules is also applied here. There is just one difference. You have a checkbox for each Access rule, where you can define whether it should be possible to open the door via the REX button when this rule is applied.    Card reader configuration The last thing you need to do is configuration of the card reader or readers (in case you use Entry and Exit rules both). You can configure the reader either in the section "Hardware->Extenders" for  2N IP Verso or you can do it in the section "Hardware->Card reader" for the other 2N IP intercoms. You need to define two things. The first is the parameter "Door" where you can pick whether the reader will be on the Entry or the Exit side. So the options are "Door Entry" and "Door Exit". The second thing is the parameter "Associated Switch" which defines which switch will be controlled by the card reader. You can pick one of the 4 switches in the section "Hardware->Switches" or the "Door Lock Switch" which was defined in the beginning of this article. In our case we use the Door Lock Switch.

Question 24

Electronic lock groups - how to efficiently set up more 2N Fortis devices in an installation

Accepted Answer

2N Fortis Cylinders and Handles use the MIFARE ® DESFire® EV1/EV2/EV3 RFID cards.  One such 2N RFID access card can be used for access to up to 90 doors with the 2N Electronic locks, depending on the number of time profiles applied. However, the 2N Fortis Cylinders and Handles can be grouped since the Access Commander 3.5 version, so the 2N RFID access card can be used for more accesses.  In this FAQ, we will go through the configuration.    Standard configuration Lock groups Applying the changes to the 2N Fortis devices through the 2N Fortis Commander   Standard configuration Standardly, it is possible to assign 2N Fortis Cylinders and Handles to a Zone, the same as other 2N OS devices in the 2N Access Commander, in the "Devices -> device -> Access Control" section.  That way, the Group of users have access to the specific Zone with devices through configured Access Rules.        Lock groups To use the RFID access card for more accesses, it is necessary to create Lock groups by clicking on the +Lock group button in the "Devices -> Lock groups" section of the 2N Access Commander.        After naming the group and creating it, it is possible to see the Locks (1) and Zones (2) sections.     To group the 2N Electronic locks and assign them to a Zone, simply add the locks to the Locks section and select the Zone for the Lock group.                It is also possible to assign the Electronic lock to the Lock group in the device's detail in the "Devices -> device -> Lock Groups" section.     Applying the changes to the 2N Fortis devices through the 2N Fortis Commander For the lock group configuration to be applied to the 2N Fortis devices, it is necessary to use the 2N Fortis Commander software and connect to the affected 2N Fortis devices. First, export the 2N Fortis Commander project file in the "Settings -> Electronic Locks -> Fortis Commander" section    Open the 2N Fortis Commander project file with the 2N Fortis Commander software and enter the previously configured password for the project file.     Connect to the 2N Fortis electronic locks, which were assigned to the groups, by clicking on "Connect to device" and presenting the Lock setup & Service card on the 2N Fortis electronic lock.     Disconnect from the device - the 2N Fortis Commander has already updated the electronic lock's configuration when it was connected.     Then close the project and import it back into the 2N Access Commander.

Question 25

External USB RFID reader 125kHz EMarine - Usage without any additional driver

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   You can use our external USB RFID reader to add RFID cards/fobs to the 2N IP Intercom´s and 2N Access Unit´s users directly from your computer.This guide will show you how to use this USB 125KHz RFID reader (9137420E).  If you have our USB 13.56MHz+125kHz RFID reader (9137421E/9137424E),please follow another article below, because of necessary additional driver.External USB readers - Driver installation & usage    Prerequisities 2N USB 125KHz RFID reader (9137420E) 2N IP intercom or 2N Access Unit with the latest firmware, equipped with 125 kHz RFID reader Optionally 2N Access Commander the latest version English keyboard in the computer system   Installation To use the USB 125 kHz RFID reader, you do not need a specific driver. It works similar to a keyboard, sending codes of top (row) numeric keyboard.  Connect the USB reader to the USB port of your computer. Setup English keyboard in the system.   Reading 125 kHz RFID card 2N IP intercom or 2N Access Unit Go to the web interface of the device, section Directory - Users - specific user - User Cards.Click your mouse on the Card ID field. Make sure it is completely empty.Swipe your RFID card over the USB reader (the code is automatically translated from DEC to HEX) and save.     2N Access Commander Use your web browser to open the web configuration, go to Settings - Credentials section and enable the reader to use.     In Users section add the RFID card to the user using connected USB reader.

Question 26

Factory reset of the 2N Access Commander Box

Accepted Answer

2N Access Commander Box is a fully plug and play solution with pre-installed software 2N Access Commander on a mini-pc. You don’t need to arrange separate server host hardware or access to an existing server for installation. Now we will look on how to proceed a factory reset of this product.Please note, resetting will erase all user data (users, devices, logs, other settings and licences), so it is necessary to backup all user settings before you start.2N Access Commander - Backup and restore of settings   Prerequisites Hardware distribution of 2N Access Commander2N Access Commander Box, order no. 91379030 or 2N Access Commander Box 2.0, order no. 1120120E / 1120120GB / 1120120US  2N Access Commander SW distribution does not support factory reset. You have to do a new clean installation of 2N Access Commander.2N Access Commander – how to install it to Virtual System   A display (VGA/HDMI) and a keyboard (USB)   Factory reset procedure Please click on the part you are interested in and it will be displayed for you.   2N Access Commander Box Connect a USB keyboard and VGA or HDMI display to the relevant port on the Box.  If the device is already running, switch it off by short pressing the blue power button on top.  Wait at least 10 sec after powering off, then start the device by short pressing the power button.  During the reboot sequence, a blue box will appear on the screen. Unless you break the boot sequence, the machine will start to boot normally after a few seconds. To break the initial boot up sequence, it is necessary to react quickly (by any key) and the blue box will remain on screen.  Here you should choose the option “Recovery mode – Restore system factory settings”.  Eventually the screen can look like these pictures, then please select the marked option.   After the final confirmation, the process of factory reset automatically starts (cca. 10 min. duration)  The device performs the final reboot and waits for the login credentials (default = root/2n).  You are forced to change the password and you get this console window thereafter.  Check and set the basic settings (such as LAN parameters, time, password) in the Advanced Menu. Most of the parameters you will find also in the web interface of 2N Access Commander.  The Box is in the factory state now, including the initial (purchased) version of the AC application. The factory reset is in fact a reinstallation of the AC from a separate factory backup partition. 2N Access Commander - How to make a software upgrade          2N Access Commander Box 2.0 Connect a VGA or HDMI display to the relevant port on the Box.  Connect a USB keyboard to one of the relevant ports on the Box.  If the device is already running, switch it off by short pressing the blue power button on top.  Wait at least 10 sec after powering off, then start the device by short pressing the power button.  During the reboot sequence, a blue box will appear on the screen. Unless you break the boot sequence, the machine will start to boot normally after a few seconds. To break the initial boot up sequence, it is necessary to react quickly (by any key) and the blue box will remain on screen.  Here you should choose the option “Recovery mode – Restore system factory settings”.  After the final confirmation, the process of factory reset automatically starts (cca. 10 min. duration)  The device performs the final reboot and waits for the login credentials (default = root/2n).  You are forced to change the password and you get this console window thereafter.  Check and set the basic settings (such as LAN parameters, time, password) in the Advanced Menu. Most of the parameters you will find also in the web interface of 2N Access Commander.  The Box is in the factory state now, including the initial (purchased) version of the AC application. The factory reset is in fact a reinstallation of the AC from a separate factory backup partition. 2N Access Commander - How to make a software upgrade

Question 27

Firmware compatibility across 2N Access Commander versions

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer. We always recommend to keep the firmware and software version up-to-date. However if needed, in table below, you can find which firmware installed on our devices is supported and can be connected to which version of 2N Access Commander. 2N OS devices includes 2N IP Intercoms, 2N Access units and some of 2N answering units (2N Indoor Talk, 2N Indoor View, 2N Indoor Compact, etc...).Full list of supported devices is available in manual.    2N Access Commander version  Supported firmware of 2N OS based devices  Supported firmware of 2N Indoor Touch 2.0  3.5.1 / 3.5.2   2.45, 2.46, 2.47, 2.48, 2.49, 2.50, 3.0, 3.1   4.3.x or newer  3.5   2.45, 2.46, 2.47, 2.48, 2.49, 2.50, 3.0   4.3.x or newer  3.4.2   2.43, 2.44, 2.45, 2.46, 2.47, 2.48, 2.49   4.3.x or newer  3.4.1   2.43, 2.44, 2.45, 2.46, 2.47, 2.48, 2.49   4.3.x or newer  3.4   2.43, 2.44, 2.45, 2.46, 2.47, 2.48   4.3.x or newer  3.3.1   2.42, 2.43, 2.44, 2.45, 2.46, 2.47   4.3.x or newer  3.3   2.40, 2.41, 2.42, 2.43, 2.44, 2.45, 2.46    4.3.x or newer  3.2.2   2.40, 2.41, 2.42, 2.43 ,2.44, 2.45    4.3.x or newer  3.2.0  2.40, 2.41, 2.42, 2.43 ,2.44, 2.45   4.3.x or newer  3.1.1  2.39, 2.40, 2.41, 2.42.2, 2.43, 2.44  4.3.x or newer  3.0.1  2.38, 2.39, 2.40, 2.41, 2.42.2, 2.43  4.3.x or newer  2.7.1  2.36, 2.37, 2.38, 2.39 ,2.40, 2.41, 2.42.1  4.3.x or newer  2.7.0  2.36, 2.37, 2.38, 2.39, 2.40, 2.41  4.3.x or newer  2.6.1  2.35, 2.36, 2.37, 2.38, 2.39, 2.40  4.3.x or newer  2.5.1  2.33, 2.34, 2.35, 2.36, 2.37, 2.38  4.3.x or newer  2.5.0  2.33, 2.34, 2.35, 2.36 ,2.37  4.3.x or newer  2.4.1  2.33, 2.34, 2.35, 2.36  4.3.x or newer  2.3.1  2.33, 2.34, 2.35  4.3.x or newer  2.2.0  2.32, 2.33, 2.34  4.3.x or newer  2.1.0  2.31, 2.32, 2.33  4.3.x or newer  2.0.2  2.30, 2.31, 2.32  4.3.x or newer  1.17  2.29, 2.30, 2.31  ---

Question 28

HTTP REST API

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. There is available HTTP REST API which gives the opportunity to completely control 2N Access Commander, including read, modify, create or delete data from it for integration purposes with any possible 3rd party systems in real-time, since no direct access to Access Commander's database is provided.   Prerequisities 2N Access Commander the latest version (for actual API endpoints v3);no additional license is required, available in every Access Commander installation.   Technical information  HTTP REST API documentation including release changes can be found on the following link:https://wiki.2n.com/acc/2.7/en/6-http-api/6-1-http-api-verze-3 (it takes a while to be fully loaded)You can also use the inbuilt endpoint list in your 2N Access Commander:https://ip_or_name_address/support/api/ API endpoints are available on the address: https://ip_or_name_address/api/v3/ Using HTTPS protocol with TLS 1.2 for communication on default port 443 In default, uses self-signed certificate, SSL certificate verification needs to be disabled in order to start communication with API in this case.Optionally, CA signed certificate can be installed to 2N Access Commander as described in the following article: SSL - CA signed user certificate. Then Access Commander needs to be accessible on name address which matches name address in the certificate instead of an IP address.   Communication with API is secured by username and password authentication. After initial authentication, every other command to API is authenticated by cookies which Access Commander send as a response to successful login. The supported commands format is JSON only. Supported methods are GET, POST, PUT, DELETE, PATCH.It is possible to create user with all details included in one command or send data in certain commands in bulk, please refer to the HTTP REST API documentation.   Login methods Username and passwordIt is not possible to use it together with 2FAAPI tokensCan be set in Access Commander by System admin. It is possible to set access rights mode Read Only / Read + Write; with possible expiration. Copying the created key is possible only until you reload the page or navigate away after creating.      Finding out which command to send Let’s say we would like to login to Access Commander using an API in order to be able to use other commands. We can easily see how it can be done on the web of 2N Access Commander itself because the web interface is using the same HTTP REST API to access all data. The following procedure will show how you can see which commands and parameters are used for each operation with data: Load the Access Commander web interface in your web browser and open the web browser debug console by pressing F12 -> Network -> XHR (Chromium based browsers). This will show a console in your web browser where we can see all the commands as you can see on the image below:    In order to see which command with which parameters is sent to API for login request, fill in login name and password in your web browser with enabled debugging console from previous step and press LOGIN button. Access Commander will login in and in the web browser debug console you can see multiple requests and one of them is the login request we are looking for, select it by clicking on it.   In its Header you can see it uses PUT method and which endpoint it calls (/login)In its Request you can see which in which syntax data are sent.Using those data from web browser you can easily replicate this command in your application.After successful login, you will be also able to see in Response cookie required for commands which will follow.      How to use commands from your application To demonstrate this example we will use an application known as Postman, which is able to send HTTPS commands and read responses to its requests.    For the first time using the Access Commander after importing the appliance, it is needed to use the web interface to login as the administrator ("Admin") to change the default password ("2n")     In Postman settings, please disable the SSL certificate verification first. There is no domain that can sign the certificate and a self-signed is not considered as trusted automatically by default.      In Postman, fill in the header as you saw in the previous example from your web browser debug console. Fill in also Body with request data you could see in the previous example. Don’t forget to set the right method and Body as JSON.Once you send the data to Access Commander API, when login is successful you will receive 200 OK a response along with other data and authentication cookies.     If you have created the API token, you can fill in it here:        Examples of commands and operations using HTTP REST API   In this section, we are ready to post the commands. First of all, we use the valid credentials to login:  (Let's consider we have an Access Commander using an IP 192.168.0.108, username: Admin, password: Admin1234)     Login with username CommandPUT https://192.168.0.108/api/v3/loginBody (data to be sent){ "login":"Admin","password":"Admin1234","longTimeLogin":true }   Authenticate commands using API Token If there is generated API token in Access Commander, it must be present in every command sent.     List of current users Now we want to receive a list of users with all the parameters.CommandGET https://192.168.0.108/api/v3/usersBody (data to be sent){ }     Getting information about a specific user Each user has a unique ID called UUID. It is possible to get it by the command "List of current users".(Lets say our user has a UUID: 6de07172-b17b-4fb3-a42e-385ac786bb29) CommandGET https://192.168.0.108/api/v3/users/6de07172-b17b-4fb3-a42e-385ac786bb29Body (data to be sent){ }     Adding an existing user to a group We need to know first the Id of the group we want to add the user to. CommandGET https://192.168.0.108/api/v3/groupsBody (data to be sent){ }Answer  {     "items": [         {             "Members": [ ],             "Name": "Technical support",             "Id": "f5425bc3-7697-4b91-9b1b-c607d28f0196",             "Company": {                 "Id": 1,                 "Name": "My Company"             },             "MemberCount": 0,             "Type": "Group",             "Revision": 0         }     ],     "count": 1 }   Now we will include the group Id in the command. In the body we will define UUID of the user, get by the command "List of current users". CommandPUT https://192.168.0.108/api/v3/groups/f5425bc3-7697-4b91-9b1b-c607d28f0196/membersBody (data to be sent)  [   {     "Id": "e4a5857d-a3c1-4514-8c19-3a5c80359d52",   } ]       Adding new RFID card to existing user For the body of the command we need to know UUID of the user, here presented as "Id" parameter. (You can get UUID by the command "List of current users".)CommandPATCH https://192.168.0.108/api/v3/usersBody (data to be sent)  [   {     "Id": "e4a5857d-a3c1-4514-8c19-3a5c80359d52",     "Operations": [       {         "value": "ABCDE12345",         "path": "/AccessCredentials/Cards/-",         "op": "add",       }     ]   } ]       Updating RFID card of existing user We will use the same command as for adding, but we will change the operation ("op") parameter to "replace" and in the "path" define order of the card, beginning from zero.We need to know UUID of the user, here presented as "Id" parameter. (You can get UUID by the command "List of current users".)CommandPATCH https://192.168.0.108/api/v3/usersBody (data to be sent) [   {     "Id": "e4a5857d-a3c1-4514-8c19-3a5c80359d52",     "Operations": [       {         "value": "123456789",         "path": "/AccessCredentials/Cards/0",         "op": "replace",       }     ]   } ]      Creating new PIN code for existing user The procedure is similar as for cards, just the path is changed for Pin usage.We need to know UUID of the user, here presented as "Id" parameter. (You can get UUID by the command "List of current users".)CommandPATCH https://192.168.0.108/api/v3/usersBody (data to be sent)  [   {     "Id": "e4a5857d-a3c1-4514-8c19-3a5c80359d52",     "Operations": [       {         "value": "5678",         "path": "/AccessCredentials/Pin",         "op": "add",       }     ]   } ]       Deleting the PIN code Now we will change the operation ("op") parameter to "remove".We need to know UUID of the user, here presented as "Id" parameter. (You can get UUID by the command "List of current users".)CommandPATCH https://192.168.0.108/api/v3/usersBody (data to be sent){ } Answer [   {     "Id": "e4a5857d-a3c1-4514-8c19-3a5c80359d52",     "Operations": [       {         "path": "/AccessCredentials/Pin",         "op": "remove",       }     ]   } ]        In case of using not supported API v2 which is unavailable in actual versions of 2N Access Commander, click here. Technical information   HTTP REST API documentation including release changes can be found on the following link:https://wiki.2n.com/acc/2.7/en/6-http-api/6-2-http-api-verze-2 (it takes a while to be fully loaded)  API endpoints are available on the address: https://ip_or_name_address/api/v2/ Using HTTPS protocol with TLS 1.2 for communication on default port 443 In default, uses self-signed certificate, SSL certificate verification needs to be disabled in order to start communication with API in this case.Optionally, CA signed certificate can be installed to 2N Access Commander as described in the following article: SSL - CA signed user certificate. Then Access Commander needs to be accessible on name address which matches name address in the certificate instead of an IP address. Communication with API is secured by username and password authentication. After initial authentication, every other command to API is authenticated by cookies which Access Commander send as a response to successful login.The supported commands format is JSON only.Supported methods are GET, POST, PUT, DELETE, PATCH.     Finding out which command to send Let’s say we would like to login to Access Commander using an API in order to be able to use other commands. We can easily see how it can be done on the web of 2N Access Commander itself because the web interface is using the same HTTP REST API to access all data. The following procedure will show how you can see which commands and parameters are used for each operation with data:    Load the Access Commander web interface in your web browser and open the web browser debug console by pressing F12 -> Network -> XHR (Chromium based browsers). This will show a console in your web browser where we can see all the commands as you can see on the image below:       In order to see which command with which parameters is sent to API for login request, fill in login name and password in your web browser with enabled debugging console from previous step and press LOGIN button. Access Commander will login in and in the web browser debug console you can see multiple requests and one of them is the login request we are looking for:     Select mentioned login request by clicking on it.  In its Header you can see it uses PUT method and which endpoint it calls (/login)  In its Request you can see which in which syntax data are sent.  Using those data from web browser you can easily replicate this command in your application.  After successful login, you will be also able to see in Response cookie required for commands which will follow.           How to use commands from your application To demonstrate this example we will use an application known as POSTMAN which is able to send HTTPS commands and read responses to its requests.  For the first time using the Access Commander after importing the appliance, it is needed to use the web interface to login as the administrator ("Admin") to change the default password ("2n")   While accessing the Access Commander using the REST API and using for example the app Postman, please, disable the SSL certificate verification first. There is no domain that can sign the certificate and a self-signed is not considered as trusted automatically by default.   Open the Postman and fill in the header as you saw in the previous example from your web browser debug console. Fill in also Body with request data you could see in the previous example. Don’t forget to set Method as PUT and Body as JSON.      Once you send the data to Access Commander API, when login is successful you will receive 200 OK a response along with other data and authentication cookies.      Examples of commands and operations using HTTP REST API   In this section, we are ready to post the commands. First of all, we use the valid credentials to login:  (Let's consider we have an Access Commander using an IP 192.168.0.250, username: Admin, password: Admin1234)     Login CommandPUT https://192.168.0.250/api/v2/loginBody (data to be sent){ "login":"Admin","password":"Admin1234","longTimeLogin":true }     List of current users Now we want to receive a list of users with all the parameters.CommandGET https://192.168.0.250/api/v2/usersBody (data to be sent){ }     Getting information about a specific user Each user has a unique ID called UUID. It is possible to get from the previous command. (Lets say our user has a UUID: e7207ded-b864-424b-ad0f-e06b9d8f7527) CommandGET https://192.168.0.250/api/v2/users/e7207ded-b864-424b-ad0f-e06b9d8f7527Body (data to be sent){ }     Creating a new user Now we want to create a new user with the name UserAPI. This user will belong to the company with the ID=1.CommandPOST https://192.168.0.250/api/v2/usersBody (data to be sent){ "Name":"UserAPI","Company":{"Id":1} } In the answer, there will be a parameter e.g..:   "Id":  "09e7eab1-7b80-4071-89c9-4969a61354e1"     Adding existing user to a group We need to know first the Id of the group we want to add the user to. CommandGET https://192.168.0.250/api/v2/groupsBody (data to be sent){ }Answer{     "count"   :   1   ,     "data"   : [   {     "Name"   :   "Home"   ,     "Id"   :   "511720dc-ef0b-4e7c-b63a-4a54b350792d"   ,     "ModifiedGuid"   :   0   ,     "Company"   : {     "Id"   :   1   ,     "Name"   :   "My Company"   },     "Users" : [ ],    "VisitorCards" : [ ]  } ] }  After that, we can use the answer for adding the user to the specific group: We need to know UUID of the user. (You can get UUID by the command "List of current users".) CommandPUT https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1/groupsBody (data to be sent){  "Id"   :   "511720dc-ef0b-4e7c-b63a-4a54b350792d" }      Adding new RFID card to existing user  If there is no card added yet, first you need to read user GUID first and then use it in command to add the card for that user. ModifiedGUID is not needed when user has no card added yet on that position. CommandPOST https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1/cardsBody (data to be sent){ "Identification":"12345678" }     Updating RFID card of existing user First you need to get the user UUID by the command "List of current users" and then use it in command to modify the card for that user. For maintaining database consistency, we need to use a specific ID for each parameter to prevent multiple processes from modifying data at the same time. This is called ModifiedGUID  and we need to get this information from the parameter before we change it. Let's say another process changed the RFID card number 3 times already to the number 12342622. We are going to find out this now. CommandGET https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1Body (data to be sent){ } Answer"Cards"  : [ {  "Identification"  :  "12342622"  ,  "Description"  :  ""  ,  "Id"  :   "25d79b1f-8612-4c44-859b-e04f89e19bb5"   ,    "ModifiedGuid"  :  3  }  Now we know the ModifiedGUID=3 and we can change the card number to 12121212 (note: we are adding the ID of the card position to the URL):CommandPUT https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1/cards/25d79b1f-8612-4c44-859b-e04f89e19bb5Body (data to be sent){   "Identification"   :   "12121212"   ,    "ModifiedGuid"   :   3    }      Creating 2 codes (1234, 9876) for existing user "Ordinal" is ID of a code.We need to know UUID of the user. (You can get UUID by the command "List of current users".)CommandPOST https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1/codesBody (data to be sent){   "SwitchCode"   :   "1234"   ,   "User"   :{   "Id"   :   "e7207ded-b864-424b-ad0f-e06b9d8f7527"   },    "Ordinal"   :   0    }  CommandPOST https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1/codesBody (data to be sent){   "SwitchCode"   :   "9876"   ,   "User"   :{   "Id"   :   "e7207ded-b864-424b-ad0f-e06b9d8f7527"   },    "Ordinal"   :   1    }      Deleting the 2nd code from existing user We need to know the code ID and the ModifiedGuid first as well as UUID of the user. (You can get UUID by the command "List of current users".)CommandGET https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1Body (data to be sent){ } Answer"Codes"  : [ {  "Ordinal"  :  0  ,  "SwitchCode"  :  "1234"  ,  "Id"  :  4  ,  "ModifiedGuid"  :  0  ,  "Collisions"   : [ ] }, {  "Ordinal"  :   1   ,  "SwitchCode"  :  "9876"  ,  "Id"  :   5   ,  "ModifiedGuid"  :   0   ,  "Collisions"   : [ ]  } ],  To the URL we need to put the ID of the code we want to delete.CommandDELETE    https://192.168.0.250/api/v2/users/09e7eab1-7b80-4071-89c9-4969a61354e1/codes/5Body (data to be sent){  "Identification"   :   "12121212"   ,   "ModifiedGuid"   :   3   }

Question 29

Import of users from device

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. It also allows importing users from 2N IP intercom or 2N Access Unit, including their access methods (bluetooth and finger print as well), so you can keep already listed users from the current system.   Prerequisities 2N Access Commander the latest version, import is supported by a virtual machine (VirtualBox, VMWare, Hyper-V) and also by a Box (miniPC) distribution. 2N IP intercom or 2N Access Unit with the latest firmware version, containing users to be imported. No additional license is required for 2N Access Commander or 2N devices.   Feature properties The procedure works only if the device has never been registered in your Access Commander. Only unique users (according to UUID - User Unique ID) in the device can be imported. It is not possible to import from another device if it contains the same users (according to UUID). All the users from the device are imported into one Company at once,it is not possible to move users between companies.   Initial state of the system In the device there are users that we would like to import to our Access Commander.The device has never been used in our Access Commader.    In our example, 2N Access Commander contains no users at this moment. It is the typical scenario but not necessary for the import.    Backup configuration of 2N device and 2N Access Commander Go to device´s web management - System - Maintenance and make a configuration backup of your device.    Go to Access Commander´s web management - Settings and make a system backup of your Access Commander.    Importing users from the device to Access Commander Go to Access Commander´s web management - Devices and add your device to Access Commander.DO NOT ASSIGN ANY ZONE TO THIS DEVICE, ALL THE USERS WOULD BE DELETED FROM THE DEVICE.      Go to Companies and open your Company details.    In the three dot menu select Import users from device, select the device and confirm.     Users have been imported to your Access Commander.    Importing users in System log You can check the state of the import in System log.    Next steps  Now you can add the device to the zone and continue with access rule configuration.Video - 2N® Access Commander - Basic setup guide

Question 30

Installation name of 2N Access Commander

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. Since the Access Commander 3.2 version it is possible to configure an installation name.  This installation name will be shown in the application header (for example the name of the web browser tab), emails (authorisation credentials emails, system notification emails, etc. and the authenticator app if configured for the user (multifactor authentication).    You can set up the installation name in the "Settings -> Configuration -> Installation name" section of the Access Commander web interface. By clicking on the pencil icon you can change the installation name and confirm it with the check icon.        After the installation name is changed, the name will be shown in the two previously mentioned sections. You can find some examples below.    Web browser    Emails

Question 31

Installation of virtual machine and Box solutions

Accepted Answer

The nerve centre of our access control solution is 2NAccess Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer. The 2N Access Commander is distributed as an image for server installation (2N Access Commander Virtual Machine) or as a software pre-installed on mini-PC (2N Access Commander Box 2.0). Virtual machine solution is scalable and by nature of virtualization systems can receive additional hardware resources from the physical computer it runs on, therefore this solution is suitable for installation of any size and is operating system independent.Box 2.0 solution has a limit to a maximum of 7000 connected 2N IP devices.Now we will look on how to install the product.   Installation Please click on the part you are interested in and it will be displayed for you.    2N Access Commander Virtual Machine Prerequisites Requirements for the host computer: VT-X virtualisation technology activated in the BIOS,How to enable virtualization on your computerHardware elements according to the count of connected 2N devices,Recommended hardware elementsSupported virtualization platform Oracle VirtualBox / VMware (6.5 and higher) / Hyper-V    Requirements for the virtual machine: Minimum system resources requirements already set in a distributed virtual image,it is not recommended to lower them.    Guide Deploy on your computer one of the supported virtualization platforms (Oracle VirtualBox / VMware / Hyper-V).    Download and extract the Access Commander image file for your virtualization platform from 2N webpage (click here).    Import downloaded virtualization file from your computer to virtualization platform,choose the used network interface and generate a new MAC address.(Example demonstrates usage of VirtualBox platform)    Run imported virtual machine If no DHCP is present, you can setup network in the linux interface, among another parameters like backup options, time settings, SSH, etc.Default login: root / 2n  If DHCP is present, you will see its IP address so you can go directly to the web interface where you can set all the setup parameters as well.           2N Access Commander Box Prerequisites Hardware distribution of 2N® Access Commander2N® Access Commander Box, order no. 91379030 A display (VGA/HDMI) and a keyboard (USB) in case DHCP is not present.   Guide Connect LAN cable and power supply to to the relevant port and start the device by short pressing the power button on top.    If DHCP is present, you can locate 2N Access Commander in the network by our application 2N Network Scanner (click to download)2N® Network Scanner - Locating 2N devices in the network    If no DHCP is present, connect also a USB keyboard and VGA or HDMI display to the relevant port.Now you can setup network in the linux interface, among another parameters like backup options, time settings, SSH, etc.Default login: root / 2n           2N Access Commander Box 2.0 Prerequisites Hardware distribution of 2N® Access Commander2N® Access Commander Box 2.0, order no. 1120120E / 1120120GB / 1120120US A display (VGA/HDMI) and a keyboard (USB) in case DHCP is not present.   Guide Connect LAN cable and power supply to to the relevant port and start the device by short pressing the power button on the front side.     If DHCP is present, you can locate 2N Access Commander in the network by our application  2N Network Scanner (click to download)2N® Network Scanner - Locating 2N devices in the network    If no DHCP is present, connect also a USB keyboard and VGA or HDMI display to the relevant port.Now you can setup network in the linux interface, among another parameters like backup options, time settings, SSH, etc.Default login: root / 2n           Configuration The Access Commander interface is available via its IP address in a web browser.   If you don´t know 2N Access Commander´s IP address, you can locate it in the network by our application 2N Network Scanner (click to download)2N Network Scanner - Locating 2N devices in the network    Open your web browser and open the page in IP address provided by Access Commander in order to access its configuration. Default login: admin / 2n    Now you can start with the basic settings configuration like server date and time, network settings, SSH & root password change.Please note, when you change the configuration method to DHCP, you also change the server’s IP address which may result in a connection loss.If you change the IP address to static, you will be automatically redirected to the new IP address.       Continue with the rest access control configuration...Video - 2N® Access Commander - Basic setup guide

Question 32

Keyboard layout - How to set different keyboard layout in Linux of 2N Access Commander

Accepted Answer

2N Access Commander (Linux terminal) is using US English pc105 keyboard layout.  In order to change the keyboard layout, you need to take the following steps:    Access the Linux terminal of the 2N Access Commander and log in using the root username and password. The default credentials are root/2n.How to access the Linux terminal? In case of virtual machine you can access the Linux terminal by using the virtual machine terminal from virtualization.In case of BOX or BOX 2.0 you can do that by connecting display and keyboard to the computer.You can use for both types of 2N Access Commander distributions access over SSH if enabled.   After logging in, please Select Advanced Menu in GNU/Linux Configuration Console and press Enter.If using default password, you will be asked to change it to secure password of your own. Please do it.     Continue to Quit, press Enter, choose Quit again and press Enter.           Once you are in terminal, please edit file /etc/default/keyboard using editor "nano".To edit this file you have to type following command:nano /etc/default/keyboard   Edit line "XKBLAYOUT" and change it to the desired keyboard layout: XKBLAYOUT=fr - for AZERTY XKBLAYOUT=uk - for AZERTY XKBLAYOUT=us - for QWERTY XKBLAYOUT=de - for QWERTZ XKBLAYOUT=cz - for QWERTZ XKBLAYOUT=sk - for QWERTZand many more...   Save your changes and leave back to terminal:nano - press "ctrl+x" and then press "y" and Enter to confirm changes  Restart the 2N Access Commander by entering the reboot command or selecting the Reboot option in the Linux interface.   Now you have the keyboard layout changed to your modified settings.

Question 33

LDAP - Users synchronisation from a remote directory

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer.2N Access Commander can be also synchronised with other directories using the LDAP protocol.   Prerequisities 2N Access Commander the latest version;license Pro or Unlimited requiredRemote directory supporting LDAP;tested with MS Active Directory, OpenLDAP, Apache DS.   Connection to the remote directory  Log in to your 2N Access Commander installation web interface.  Open the Companies section and click on the company to which you want to import users from the given directory.       In the company settings select the USER SYNCHRONISATION tab and click on Create LDAP configuration.  Fill in the Server name, Login name, Password and LDAP schema (Base DN) and save. Since the 3.2 version of the Access Commander, it is possible to use the TLS secure connection with the TLS certificate verification option.       As an example, the figure uses the Administrator account (from the directory), which is located in the directory in the container ACUsers on the acom.local directory domain.    Universal Login name: CN=,CN=,DC=,DC=Just in case of MS Active Directory the input can be: Administrator@acom.local   LDAP Schema (BaseDN): OU=,DC=,DC=If the users we want to import are deeper in the directory hierarchy, you must fill in the full path. For example, for users who are located in the Sales organisational unit, which is part of the 2N organisational unit, which is already at the root of the directory in the acom.local domain, the schema looks like this: OU=Sales,OU=2N,DC=acom,DC=local        Including user contacts and accesses for import  In the user synchronisation options, click on Edit schema button.        Here we define the User filter, User name and names of the attributes under which the given information is located in the directory.  In case of MS Active Directory, we can use the already preset User filter "(&(objectclass=user)(objectcategory=person))", thereby importing only users that have user in the "objectclass" attribute and person in the "objectcategory" attribute.More information here:  https://docs.classic.secureauth.com/display/KBA/Active+Directory+Attributes+List  In case of synchronisation from other directories, it is necessary to adjust the filter accordingly to match the requirement of the given directory.     In the case of cards or PIN codes, we often have to use the box for another item, as there is usually no space in the directory for a card identifier or PIN code. The following example shows that for the identifier of card 1 we used the Description field in the directory and for the PIN code the Fax field in the user detail. Therefore, in order to be able to import the given information, it is necessary to set up 2N Access Commander to search for this information in the given user's detail fields in the directory.   PIN Code we entered for example into the "Fax" field in the directory - the name of this attribute in the directory is: facsimileTelephoneNumber  Card Number #1 we entered for example into the "Description" field in the directory - the name of this attribute in the directory is descriptionFor the second card a separate field must be selected in the user's detail.        Synchronisation options  Users removed from LDAPChoose what Access Commander should do (no change / deactivate / delete) if a user in the given directory is deleted.Users disabled in Active DirectoryIf the user is deactivated in the directory, it will be imported and deactivated in Access Commander (he won't have access to the door, it won't be able to call him).Group synchronisationSynchronisation of the membership, you need to manually create those groups in your Access Commander database. This was done to prevent importing all unnecessary groups, that are not tied with access.We will show you in more detail later on.Avatar synchronisation If users have a photo assigned to them in the directory, it can also be imported.Following referralsImports the given users from any other repositories of the given directory. Nested searchImports the given users also from subfolders (organisational units or containers) of the selected BaseDN directory.Pagination: If Access Commander asks the directory for a user, they are sent on so-called pages (to avoid server overload).Define here how many users will be sent on one "page" (the value must not exceed the value set in the directory).     Starting synchronisation Automatic synchronisationThe users can be synchronised to 2N Access Commander automatically, we choose between hourly, daily and weekly intervals.    Test LDAP connectionYou can check if the LDAP connection is ready.   Finally, you can start the synchronisation now to download the users from the given directory to the 2N Access Commander.You can find the imported users in the Users section under the given Company in the 2N Access Commander.       Group membership for imported users This is not an import of the groups from the LDAP directory, this is only a synchronisation of the membership, you need to manually create those groups in your Access Commander first. This was done to prevent importing all unnecessary groups, that are not tied with access. Create groups in the Access Commander, keep in mind that the name of the group is case sensitive and must be exactly the same as you use in your remote directory.      Enable synchronisation in the Access Commander and edit group schema settings according to your needs.                 Additional Group DN: CN=do not insert BaseDN as it will be automatically used according to the LDAP schema set in previous steps)   Group Filter: In our example, we used a filter for MS Active Directory (&(objectClass=group)(member=*)), thereby synchronising the users with groups that have "groupin the "objectclass" attribute and "member" in the "objectcategory" attribute and they are also simultaneously created in the Access Commander.  The default Group Name ("cn") and Group Member ("member") above may apply only to MS Active Directory, and in case of synchronisation from other directories, those that differ must be adjusted according to the given directory.        Now you can import the LDAP settings and check if everything is properly synchronised and the users are assigned to the correct groups.          Delete LDAP connectivity If needed, you can completely delete the LDAP configuration.      If you have older version of the system (2.7 and older) with different look of the web interface, please click here.  Connection to the remote directory  Log in to your 2N® Access Commander installation.Make sure you have the Integration License activated (Settings > Licenses > LDAP synchronisation: Yes).Open the Companies section and enter the edit of the company to which you want to import users from the given directory:In the company settings select the LDAP tab and click on CREATE (LDAP configuration): Fill in the Server name, Login name, Password and LDAP Schema and click CREATE at the bottom right. As an example, the following figure uses the Administrator account (from the directory), which is located in the directory in the container Users on the acom.local directory domain.SSL is not used here - the connection to the server is therefore unsecure.    Universal Login name: CN=,CN=,DC=,DC= Just in case of MS Active Directory the input can be: Administrator@acom.local LDAP Schema (BaseDN): OU=,DC=,DC= If the users we want to import are deeper in the directory hierarchy, you must fill in the full path.For example, for users who are located in the Sales organisational unit, which is part of the 2N organisational unit, which is already at the root of the directory in the acom.local domain, the schema looks like this: OU=Sales,OU=2N,DC=acom,DC=local      Including user contacts and accesses for import After creating a connection to the remote directory, click the USER SCHEMA SETTINGS button:Here we define the User filter, User name and names of the attributes under which the given information is located in the directory. In case of MS Active Directory, we can use the already preset User filter "(&(objectclass=user)(objectcategory=person))",thereby importing only users that have user in the "objectclass" attribute and person in the "objectcategory" attribute. In case of synchronisation from other directories, it is necessary to adjust the filter accordingly to match the requirement of the given directory. The default User Name ("cn") and attributes below may apply only to MS Active Directory, and in case of synchronisation from other directories, those that differ must be adjusted according to the given directory.  Then confirm by clicking on the CHANGE button. Synchronisation advanced settings Set other parameters of the LDAP synchronisation   Nested searchImports the given users also from subfolders (organisational units or containers) of the selected BaseDN directory.Follow referralImports the given users from any other repositories of the given directory.Import user's photoIf users have a photo assigned to them in the directory, it can also be imported.Disable users when disabled in Active DirectoryIf the user is deactivated in the directory, it will be imported and deactivated in Access Commander (he won't have access to the door, it won't be able to call him).Treating removed usersChoose what Access Commander should do if a user in the given directory is deleted. Either No Change, or Deactivate, or Delete in Access Commander.PaginationIf Access Commander asks the directory for a user, they are sent on so-called pages (to avoid server overload).So define here how many users will be sent on one "page" (the value must not exceed the value set in the directory).   Starting synchronisation  If you need users from the given directory to be synchronised to 2N® Access Commander automatically,set the parameter Periodical import time, where we choose between hourly, daily and weekly intervals,select the minute, hour or day of the regular synchronisation and confirm by clicking on the CHANGE button:   Finally, you can validate the LDAP configuration by clicking on the appropriate button below and by clicking the IMPORT button (above left) information about users from the given directory will be downloaded to the 2N® Access Commander (see the picture below). You can find the imported users in the Users section under the given Company in the 2N® Access Commander.At the top left you can check the Last import status under the appropriate fieldand you can completely delete the LDAP synchronisation with the DELETE CONFIGURATION button at the bottom left.    How to import an RFID card identifier or PIN code with the user Click the USER SCHEMA SETTINGS button: Here we define the names of the attributes in the directory from which the individual information is downloaded. In the case of cards or PIN codes, we often have to use the box for another item, as there is usually no space in the directory for a card identifier or PIN code.The following example shows that for the identifier of card 1 we used the Description field in the directory and for the PIN code the Fax field in the user detail.Therefore, in order to be able to import the given information, it is necessary to set up 2N® Access Commander to search for this information in the given user's detail fields in the directory:     The names of the individual attributes (for MS Active Directory) are then described here: https://docs.classic.secureauth.com/display/KBA/Active+Directory+Attributes+List) Example:  PIN Code we entered for example into the "Fax" field in the directory - the name of this attribute in the directory is: facsimileTelephoneNumber  Card Number #1we entered for example into the "Description" field in the directory - the name of this attribute in the directory is:description  For the second card a separate field must be selected in the user's detail.        Group membership for imported users     This is not an import of the groups from the LDAP directory, this is only a synchronisation of the membership, you need to manually create those groups in your Access Commander first. This was done to prevent importing all unnecessary groups, that are not tied with access.   If you have done all of the steps above, you now should have users in your database with their accesses, phone numbers etc. Now you can create groups in the Access Commander, keep in mind that the name of the group is case sensitive and must be exactly the same as you use in your remote directory.                    After you create all the necessary groups, you need to enable synchronisation in the Access Commander and edit group schema settings according to your needs                    Additional Group DN: CN= (do not insert BaseDN as it will be automatically used according to the LDAP schema set in previous steps)   Group Filter: In our example, we used a filter for MS Active Directory (&(objectClass=group)(member=*)), thereby synchronising the users with groups that have "group" in the "objectclass" attribute and "member" in the "objectcategory" attribute and they are also simultaneously created in the Access Commander.The default Group Name ("cn") and Group Member ("member") above may apply only to MS Active Directory, and in case of synchronisation from other directories, those that differ must be adjusted according to the given directory.    Now you can import the LDAP settings and check if everything is properly synchronised and the users are assigned to the correct groups

Question 34

License Plate Recognition (LPR)

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   2N devices can use recognized license plates as another credential for entry or exit. License plates may be assigned to a user and their validity is controlled by the same access rules as their other credentials.   Prerequisites 2N IP Intercom (except 2N IP Uni) or 2N Access Unit with the latest firmware no additional license is required  optionally 2N Access Commander (latest version) no additional license is required  Axis network camera with ARTPEC-6 / ARTPEC-7 / ARTPEC-8 chip(verify the suitable camera with Axis according to chosen LPR app below)additional license from Axis can be required according to selected LPR app  License Plate Recognition app Vaxtor VaxALPR On Camera (version 2.2.15+) - for license, please contact Vaxtor https://www.vaxtor.com/contact/or Axis License Plate Verifier (version 2.1+)     Feature properties License plate recognition (LPR) works outside of Access Profiles set in Services - Access Control - Entry or Exit Rules, and as such can’t be combined with other credentials for combined authentication.  Version 3.0 or later If the feature is enabled and a valid HTTP request is received, this event is recorded into the event log of the 2N device as LicensePlateRecognized with the following parameters:   ap ... access control direction, entry (0) or exit (1) session ... ID of the authentication session  licensePlate ... the license plate recognized by the camera    valid ... whether the licensePlate has the right to enter (true) or not (false) uuid ... linking to a specific user ID, if licensePlate isn’t assigned to any users, the uuid parameter will be left out      Optionally, a snapshot containing a recognized license plate may be attached to the LPR HTTP request. The device receiving these requests can then store up to 5 most recent snapshots, downloadable by 2N Access Commander via access log.One license plate should always be assigned to one user, otherwise its access rules may not be applied correctly if different users have different access rules. The first match found in the directory will be used for authentication.      Version 2.50 (LTS) or earlier If the feature is enabled and a valid HTTP request is received, this event is recorded into the event log of the 2N device as LicensePlateRecognized with the following parameters:   ap ... access control direction, entry (0) or exit (1) session ... ID of the authentication session  licensePlate ... the license plate recognized by the camera   valid ... whether the licensePlate has the right to enter (true) or not (false) uuid ... linking to a specific user ID, if licensePlate isn’t assigned to any users, the uuid parameter will be left out       Optionally, a snapshot containing a recognized license plate may be attached to the LPR HTTP request. The device receiving these requests can then store up to 5 most recent snapshots, downloadable by 2N Access Commander via access log.One license plate should always be assigned to one user, otherwise its access rules may not be applied correctly if different users have different access rules. The first match found in the directory will be used for authentication.          2N device configuration Let’s configure the intercom or access unit first to have everything prepared for the integration. If you use Access Commander to manage your device, you only need to set up HTTP API access in this section, and then please continue to the next section: 2N Access Commander configuration      Version 3.0 or later Go to Integration - HTTP API section. Now click on the "Switch to the old interface" button to continue setup in the old interface (switch to the 2.50 (LTS) section for this setup)   Go to Access - Access Rules section. Enable Entry, Exit, or both, depending on whether the device your camera is connected to functions as an entry point, an exit point, or both.If the 2N device is connected to 2N Access Commander, then the following settings are managed by it.     After you enable either Access, Exit or both, go to the License plate recognition section on the same page click on the "Switch to the old interface" button to continue setup in the old interface (switch to the 2.50 (LTS) section for this setup)  Go to Directory section.If the 2N device is connected to 2N Access Commander, then the following settings are managed by it. Here, create a user and add their license plates in Credentials > Add credentials > License plateYou can enter up to 20 license plates, each license plate can contain up to 10 characters – spaces are ignored.             Version 2.50 (LTS) or earlier  Go to Services > HTTP API section.  In the Services tab, make sure Access Control API is enabled.We recommend using Secure (TLS) / Digest as connection / authentication type.       Then continue to Account # tab, enable it, enter credentials you’d like to use, and tick the Access Control privilege for CONTROL.         Go to Services - Access Control section.If the 2N device is connected to 2N Access Commander, then the following settings are managed by it. In the Entry Rules or Exit Rules tab, Advanced Settings part, select Opening by License Plate from the License Plate Recognition dropdown menu.         Go to Directory - Users section.If the 2N device is connected to 2N Access Commander, then the following settings are managed by it. Here, create a user and add their license plates under Car Fleet Management. You can enter up to 20 license plates separated by commas, each license plate can contain up to 10 characters – spaces are ignored.          2N Access Commander configuration (optional)     If the 2N device is connected to 2N Access Commander, then most of settings, incl. LPR, are managed by it.But still you have to configure the device’s HTTP API credentials directly in the device configuration as described in the previous section. Go to Devices section. Open details of the device you already prepared for LPR.        Assign the device to the proper zone.       If you see there "Lift control activated" message, please deactivate this feature first.          Go to Zones section.Open used zone details.      Enable License Plate Authentication.       Go to Users section.Assign one ore more license plates to the user.          Verify that this user is assigned to the correct group.        Go to Access rules section.Create an access rule matching the target group and zone.      Go to Settings - CAM logs section.Optionally, here you can configure getting photos of recognized license plates.Create a new CAM log.      Select the Car license plate recognized as monitored event.      Then select devices you want to receive photos from.         The function is ready to use.       Go to Access log section. You will see a record once a license plate is recognized. You can expand its details and if there are CAM Logs available, you will see this small icon. Once you click it, you should see an overview of all attached photos.                 If you have older version of the system with different look of the web interface, please click here.   When a 2N device is connected to 2N Access Commander, then most of its settings are managed by it. Thus, LPR settings will be managed by 2N Access Commander, but still you have to configure the device’s HTTP API credentials as those are device dependent.  Configure your 2N Access Commander as you normally would. Then open details of the device you already prepared for LPR  and make sure it has Lift Control turned off and that it’s assigned to the proper zone.  Then go to this Zone’s detail and enable License Plate Authentication.  Users can have their license plates assigned  under Accesses>Car License Plates, click ADD, enter one or more license plates, and confirm by clicking create.     Verify that this user is assigned to the correct group  and create an Access Rule for it.  Optionally, if you’d like to get photos of recognized license plates, you can create + NEW CAM LOGS. Name the log accordingly, select “Car license plate recognized” and click create.  Then ADD all devices you want to receive photos from to this CAM Log.  Once everything is configured, Access Logs will show up once a license plate is recognized.  You can expand its details and if there are CAM Logs available, you will see this small icon.  Once you click it, you should see an overview of all attached photos.          LPR app installation into Axis network camera and configuration   There are two options to choose from, click on the selected option to view the guide.    Vaxtor VaxALPR On Camera   We’ll only configure the most important settings, for detailed information please see the VaxALPR user manual:https://vaxtor.com/wp-content/uploads/2021/01/VaxALPR-On-Camera-Axis-Camera-Integration-EN_2.0-May-2020.pdf    Log in to suitable Axis network camera with ARTPEC-6 / ARTPEC-7 / ARTPEC-8 chipand enter Settings.       Go to the Apps tab and add the new one. Locate the .eap file from Vaxtor.Once appeared in the list of installed apps, click on it.           Activate your license key you have got from Axis for this scenario.     Then start the app and open it to go to its configuration.        Open the hamburger menu and select Reporting.        Scroll down to Optional reports and enable 2N. Fill in your 2N device’s IP address and configure the rest based on the security settings and credentials you entered in the HTTP API section of the 2N device. Save.      Open the hamburger menu again and enter Settings.       The Location part contains settings which define the countries whose license plates should be recognized. You can select up to 10.        In the Plate & Mode part you can set the minimum number of characters.       In the Video part you can set the minimum and maximum character height. Optimal settings are dependent on numerous factors, please see the VaxALPR manual for more details.        In the Environment part, you have the option to adjust how often can the same plate be authorized, what’s the maximum angle under which OCR should recognize license plates and most importantly, when to report a recognized plate.         The OCR part lets you fine tune the LPR confidence.        The Watermark part lets you adjust the images sent to 2N devices. Leave the Maximum JPEG size filter set to 0 as the maximum image size sent to 2N devices is 256 kB anyway – if the compressed file is bigger than that, it won't be sent. Thus you should adjust JPEG quality accordingly, we recommend setting it to 50 if your camera has a resolution around 1920×1080 px. For lower image resolutions or when "Perform report crop to 640×480" is checked you can set the quality to a higher value.      The Summary & Submit part contains an overview of all previously configured settings. Save the changes you made     Now, if everything is configured properly and a license plate is recognized, it’ll be sent into your 2N device. Based on whether this plate is valid or not, the barrier/door will open.      Received license plates will be shown in the 2N device web interface, section Status - Events Log.             Axis License Plate Verifier     We’ll only configure the most important settings, for detailed information please see the ALPV user manual:https://help.axis.com/en-us/axis-license-plate-verifier    Log in to suitable Axis network camera with ARTPEC-6 / ARTPEC-7 / ARTPEC-8 chipand enter Settings.       Go to the Apps tab and add the new one. Locate the .eap file from Axis.Once appeared in the list of installed apps, click on it.        Activate your license key you have got from Axis for this scenario.     Then start the app and open it to go to its configuration.     We will go throw the initial settings wizard.Select Access control type of system.      Select Barrier mode to Open to all.      If your camera view is upside down, change Image rotation to 180.    Next steps do not require any changes.         After the wizard we will adjust one more parameter in the Settings tab. Please enable Self-signed certificate in the Security part.      In the Integration section, Direct integration part, Enter your 2N device’s IP address and HTTP API credentials.Select HTTPS as connection type and enable the integration.     Now, if everything is configured properly and a license plate is recognized, it’ll be sent into your 2N device. Based on whether this plate is valid or not, the barrier/door will open.    Accordion summary… Received license plates will be shown in the 2N device web interface, section System - Events Log.      Version 2.50 (LTS) or earlier  Received license plates will be shown in the 2N device web interface, section Status - Events Log.

Question 35

Licensing since the version 2.0 in 2N Access Commander

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time.   Since the version 2.0, new license tiers are used  What will happen to my licenses after updating from version 1.17 ? Click to see the answer.       When updating 2N Access Commander to version 2.0, the following warning has to be confirmed:    After the update, you will see another warning regarding the possibility of automatic switching to the relevant license according to the new model. After clicking the presented button and confirming next information, the license is renewed. The new license covers the existing number of users and devices and the given functions.     If a licensed device has ever been added as a licensed one in 2N Access Commander 2.0 or higher, the license will be renewed automatically without the warning.If you try to add a new device or user that no longer "fits" into the current license, you will be prompted to order the corresponding (higher) license.        Where can I find information about the license in use: The web interface of the 2N Access Commander > Settings > Licenses (see picture below). The section shows the number of available (remaining) of the total number of owned licenses for device management, users and users with extended rights.At the same time, the date of uploading the last license is indicated here. Each additional uploaded license will replace the original one. Licenses do not add up. Version 3.0+   In virtual machine, upon initial installation, a trial license is available with a free conversion to the Basic license tier after which the advanced functions will be unavailable. The trial license cannot be reactivated.  In Access Commander BOX, upon initial start, the Basic license is available. The BOX does not support trial license.      Then you can select from Advanced, Pro and Unlimited tiers requiring purchasing.   Basic  Advanced  Pro  Unlimited  free on clickduring initial Trial   order number 91379031  order number 91379032 (from Trial or Basic) order number 91379034 (upgrade from Advanced)   order number 91379033 (from Trial or Basic) order number 91379035 (upgrade from Pro)       Features available in each type of license:   Licenses:   Trial  Basic  Advanced  Pro  Unlimited  2N Part No.   n/a  n/a  91379031  91379032  91379033  Axis Part No.   n/a  n/a  02309-001  02310-001  02311-001  Maximum User Count   5  50  300  1000  Unlimited *  Maximum Device Count  (both activated and deactivated)   1  5  30  100  Unlimited   Maximum Administrator/Manager Count   5  1  5  1000   Unlimited   Access and System Logs    ✓    ✓    ✓    ✓    ✓   Access Rules   ✓   ✓   ✓   ✓   ✓   API Management   ✓  ✓  ✓  ✓  ✓  Account Activation/Deactivation   ✓  ✓  ✓  ✓  ✓  Failed Access Attempts Limit   ✓  ✓  ✓  ✓  ✓  Silent Alarm   ✓  ✓  ✓  ✓  ✓  Zone Code   ✓  ✓  ✓  ✓  ✓  Device Monitoring   ✓  ✓  ✓  ✓  ✓  Log Management   ✓  ✓  ✓  ✓  ✓  User Import from CSV or Device   ✓  ×   ✓  ✓  ✓  Bulk Firmware Administration   ✓  ×  ✓  ✓  ✓  Multi-Factor Authentication   ✓   ×  ✓   ✓   ✓   User Rights   ✓   ×  ✓  ✓   ✓   Notification  ✓   ×   ✓   ✓   ✓   Presence  ✓   ×   ✓   ✓   ✓   API access keys   ✓   ×  ✓   ✓   ✓   Cam Logs  ✓   ×   ✓   ✓   ✓   Lift access control ✓  ×   ✓   ✓   ✓   Dashboard widgets  ✓   ×   ✓   ✓   ✓   Mobile credential support  ✓   ×   ✓   ✓   ✓   Visitor Management   ✓  ×  ✓   ✓   ✓   Occupancy Management   ✓ × ×  ✓  ✓  Synchronisation (LDAP & CSV)  ✓   ×   ×   ✓   ✓   Anti-passback  ✓   ×   ×   ✓   ✓   Attendance monitoring(separate license, order number 91379036) ✓  Optional  Optional  Optional  Optional    * Unlimited within the maximum capabilities of the software platform, refer to Recommended Hardware      How to get the license    Select one of the connected devices (2N IP Intercom or 2N Access Unit) and send its serial number to your distributor together with information which license tier you would like to get.A license file will be generated, after uploading the file.The license will be valid as long as the licensed device is connected (the device serves as a hardware key).      Uploading the license file The Settings - License section allows you to upload a new license by loading the license file from your local disk.Each additional uploaded license will replace the original one. Licenses do not add up.      Suspension of the license The license may be suspended if the license device is disconnected from 2N Access Commander for a longer period of time. When the license is suspended, all devices switch to the inactive state. The time for which 2N Access Commander will be functional depends on the time for which the licensed device was connected. The longer it has been connected, the longer it has to be reconnected. The date and time when the license is suspended are displayed in the license overview.        The license can be reactivated by reactivating the device, to which the license is bound, to the active state. After activating the licensed device, all others will be activated. If you upload a new license, you must first activate the device on which the new license is generated. After activating the licensed device, all others will be activated.

Question 36

Lift access control - configuring 2N systems

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. You can setup 2N RFID/Keypad/Bluetooth/Fingerprint equipped IP units to control which floors authorized user can access. The whole scenario allows interconnection of 2N IP units with AXIS A9188 I/O Relay Modules, which tells the lift which floor can be accessed after a person authorizes using the 2N IP unit as shown on the following image  Types of most typical scenarios are: A 3rd party RFID card reader in the lift cabin is connected over Wiegand to a 2N Access Unit or located at the top of the shaft or in the Machine room. The 2N Access unit communicates over IP with the Axis A9188, which is connected to the Lift Controller. The Lift Controller uses CANbus (or similar) to control the buttons in the Lift Car.A 2N Access Unit or supported intercom is installed in the lift cabin requiring an Ethernet cable connection from the machine room. This is the most convenient scenario. The 2N device communicates again over IP with the AXIS A9188 in the same way as above.A 2N Access Unit or supported intercom is installed in the lift cabin, which does not have an Ethernet connection. 2N 2Wire converters are used to bring IP connectivity and PoE through the Lift car’s traveling cable over available 2 wires. This provides IP connectivity for communication between the  2N device and the Axis A9188, which is linked with the Lift Controller.    Requirements  Lift control solution requires: (Optional) 2N Access Commander 1.13 and later. Starting with 2N Access Commander 2.0 you need at least an Advanced license for lift control.2N OS 2.27 and later. 2N Access Commander 2.0 requires firmware 2.32 for compatibility.Lift license (part of the Gold license - 9137909) for IP intercoms.The license is available for the following models: 2N IP Style, 2N IP Verso, 2N IP Force, 2N IP Safety, 2N IP Vario.AXIS A9188 I/O Relay Module (2N order no. 9160501, AXIS order no. SKU 0820-001) firmware 1.65.0.2 or newer       Technical parameters    AXIS A9188 communicates with lift I/O Relay Module using its relays wired to lift system  2N devices communicate with AXIS A9188 via IP protocol HTTPS  Time for relays open/close time is set by 2N IP unit to 10s (can be changed) which directly corresponds with time person have after his/her authorization on 2N IP unit to push floor button in the lift  One 2N device can connect to up to 8 AXIS A9188 I/O Relay Modules  Multiple 2N devices are not recommended to connect to same AXIS A9188 I/O Relay Module         The following guide will explain, how to set the whole scenario to allow a person access to certain floors in the lift using their credentials (RFID, Code, Bluetooth or Fingerprint). Configure the 2N unit to communicate with the AXIS 9188 I/O Relay Module  Make sure the 2N device has Gold license (Lift feature included) installed and firmware 2.27 or newer is used.  Connect the 2N unit to the AXIS A9188 I/O Relay Module in section Hardware - Lift Control by specifying the IP address of AXIS A9188.  Make sure you fill in the authentication as well (admin credentials for the AXIS relay module - root/root by default).    All AXIS A9188 I/O Relay Modules connected to the same 2N unit needs to have same administrator user with the same password (root for example) - maximum of 8 AXIS A9188 I/O Relay Modules can be connected to one 2N unit allowing for a maximum of 64 floors         2N Access Commander Version 3.0+ Create a Zone for each Floor in the section Zones. It is correct that these Zones will not have any device assigned, since lift enabled devices cannot be added to any Zone. Assign each zone to the Company which contains users who are allowed access to that particular floor (multiple Companies can be selected if needed).  Users should be placed in groups which will later be granted access to particular floors.Navigate to Access Rules and begin creating rules to define which zones or floors each group may access. For example, the group ‘Company A Sales Team’  can be paired with the zone ‘first floor’ to allow the users of that group access to the first floor.  Optionally, Time profiles can be set within Access rules which will restrict access to that floor within desired time frames. If none or Empty Time profile is used it means access will be allowed 24/7.    Enable lift control usage in added devices in the device details page in Access Commander.  If you add to Access Commander device with lift control license, it will become automatically enabled for Lift Control)    To finally setup which users can access which floor, in device details go to Management and create Floor assignment according to the physical connection of relays between AXIS A9188 and the lift itself (for example relay io_1_1 on AXIS A9188 is physically connected to lift that 1st floor will become available for Groups of users which have in Access rules defined rules for Zone 1st floor).   Since up to 8 AXIS A9188 can be connected, you need to know which relay belongs to which AXIS A9188 I/O Relay Module: io_1_1 in Floor list stands for first connected AXIS A9188 to 2N unit and its first relay io_1_2 in Floor list stands for first connected AXIS A9188 to 2N unit and its second relay io_2_1 in Floor list stands for second connected AXIS A9188 to 2N unit and its first relay etc...    From now all users, which are part of Groups associated in Access rules with Zone 1st floor and have valid credentials, when they authorize on 2N IP unit in lift cabin will be able to use lift button for 1st floor.   (Optional) Setup floor to allow access to anyone who presses the lift floor button  In order to allow access to floor without the need to authorize person using an RFID card, in device details go to Management and create Floor assignment according to the physical connection of relay between AXIS A9188 and lift itself (for example relay io_1_2 on AXIS A9188 is physically connected to lift which 2nd floor will become available for anyone who just presses a 2nd-floor button in the lift). From now, anyone who presses the button for 2nd floor will be able to access that floor.   Optionally, Time profile can be set, which will restrict access to that floor for desired time frames. If none of the Time profiles is used it means 24/7 allowed access.    IP Intercom/Answering unit lift setup ( Access Commander 3.0+)  RequirementsLift control from 2N OS answering units requires:  2N® Access Commander 3.0 and later (optional)2N OS 2.32 and later   The setup is quite easy once you finished all the previous steps in this guide. You can create a user that will stand in for your 2N OS based answering unit – in this example, we’re using several 2N® Indoor View units. Name these users according to your preferences, we named them Apartment 101 – 2N Indoor View etc.  Calling more devices at the same time It's important to note here that one user can have up to three numbers, thus you don't have to create more users for flats that have up to three answering units, be it 2N® Indoor View, 2N® Mobile Video etc. If it's necessary to call more than three devices, create more users and assign them to one quick dial button as described two steps below.  Make sure each user residing on the 1st floor is assigned to a group that has access to this floor – in our case, it’s 1st floor group as shown a few steps before in Access Rules.Now go to devices and open device detail of an intercom and configure its quick dial buttons or touch display to call all users and devices in e.g. Apartment 101:  Now that this is ready, go to the intercom’s web interface via Configure Device.   Access Commander Version 2.7 or older    Create a Zone for each Floor in the section Zones. It is correct that these Zones will not have any device assigned, since lift enabled devices cannot be added to any Zone.    Assign each zone to the Company which contains users who are allowed access to that particular floor (multiple Companies can be selected if needed).    Users should be placed in groups which will later be granted access to particular floors.    Navigate to Access Rules and begin creating rules to define which zones or floors each group may access. For example, the group ‘Company A Sales Team’ can be paired with the zone ‘first floor’ to allow the users of that group access to the first floor.    Optionally, Time profiles can be set within Access rules which will restrict access to that floor within desired time frames. If none or Empty Time profile is used it means access will be allowed 24/7.     Enable lift control usage in added devices in the device details page in Access Commander.   If you add to Access Commander device with lift control license, it will become automatically enabled for Lift Control)        To finally setup which users can access which floor, in device details go to Management and create Floor assignment according to the physical connection of relays between AXIS A9188 and the lift itself (for example relay io_1_1 on AXIS A9188 is physically connected to lift that 1st floor will become available for Groups of users which have in Access rules defined rules for Zone 1st floor).    Since up to 8 AXIS A9188 can be connected, you need to know which relay belongs to which AXIS A9188 I/O Relay Module: io_1_1 in Floor list stands for first connected AXIS A9188 to 2N unit and its first relay io_1_2 in Floor list stands for first connected AXIS A9188 to 2N unit and its second relay io_2_1 in Floor list stands for second connected AXIS A9188 to 2N unit and its first relay etc...      From now all users, which are part of Groups associated in Access rules with Zone 1st floor and have valid credentials, when they authorize on 2N IP unit in lift cabin will be able to use lift button for 1st floor.  (Optional) Setup floor to allow access to anyone who presses the lift floor button  In order to allow access to floor without the need to authorize person using an RFID card, in device details go to Management and create Floor assignment according to the physical connection of relay between AXIS A9188 and lift itself (for example relay io_1_2 on AXIS A9188 is physically connected to lift which 2nd floor will become available for anyone who just presses a 2nd-floor button in the lift).From now, anyone who presses the button for 2nd floor will be able to access that floor.      Optionally, Time profile can be set, which will restrict access to that floor for desired time frames. If none of the Time profiles is used it means 24/7 allowed access.          IP Intercom/Answering unit lift setup Access Commander 2.7 or lesser   Requirements   Lift control from 2N OS answering units requires:  2N Access Commander 2.0 and later (optional)  2N OS 2.32 and later       The setup is quite easy once you finished all the previous steps in this guide. You can create a user that will stand in for your 2N OS based answering unit – in this example, we’re using several 2N Indoor View units. Name these users according to your preferences, we named them Apartment 101 – 2N Indoor View etc.  Calling more devices at the same time   It's important to note here that one user can have up to three numbers, thus you don't have to create more users for flats that have up to three answering units, be it 2N Indoor View, 2N Mobile Video etc. If it's necessary to call more than three devices, create more users and assign them to one quick dial button as described two steps below.              Make sure each user residing on the 1st floor is assigned to a group that has access to this floor – in our case, it’s 1st floor group as shown a few steps before in Access Rules.    Now go to devices and open device detail of an intercom and configure its quick dial buttons or touch display to call all users and devices in e.g. Apartment 101:    Now that this is ready, go to the intercom’s web interface via Configure Device .     Door and lift control   Now you can decide whether to combine (1) door and lift control or (2) have it separated.         Switch for lift control Activate the switch by entering DTMF (activation code) and therefore send the following HTTP request. Replace the values in  red  with your own values: https://  LiftDeviceIP   /api/lift/grantaccess?user=$CallUuid$&duration=  seconds  https://127.0.0.1/api/lift/grantaccess?user=$CallUuid$&duration=5 (example) *LiftDevice = either 127.0.0.1 (if the very same device is controlling the lift) or some other device (where the Axis relay is connected)    Optional parameter duration   Please note that &duration=seconds in the HTTP request is optional. You may specify it to keep the lift buttons activated longer than specified in the image below – this value is used by all other credentials or when duration isn't specified in the HTTP request.      The HTTP request uses LIFT API that’s part of Access Control API of the 2N device in the lift that controls the Axis A9188 relay module.     2N OS answering unit setup   2N answering unit support   All 2N answering units may be used for lift control, this includes even our most basic units such as 2N Indoor Talk and 2N IP Handset. More advanced answering units, such as 2N Indoor View and 2N Indoor Compact have an optional LIFT icon checkbox to make the lift button easier to identify; 2N Indoor Touch 2.0 and 2N Mobile Video will receive the LIFT icon functionality in the upcoming updates. Basically, any device that can send DTMF may be used for lift control.      This setting is identical for 2NOS only and Access Commander included. To configure a 2N OS answering unit, access the web interface of the unit. This unit needs to have devices corresponding with phone numbers of intercoms that are going to call it, in this example we’re using device:Verso, but you can use other syntaxes depending on network setup. Add a new device or edit an existing one.  The last step is to set up Unlock Buttons – as you can see, we set up separate ones for door control and lift control. If LIFT is checked, its icon will change to make it easier to differentiate between the two.  Once this Main entrance – 2N IP Verso device (whose device name is Verso) calls the Apartment 101 – 2N Indoor View user, the 2N Indoor View recognizes it and shows the appropriate unlock buttons.  Tapping either of these will either open the door or start the lift action and send the HTTP request to the 2N device in the lift which then enables the appropriate buttons on the lift control panel via the Axis A9188. It’s important to note that 2N Access Commander serves as a synchronization server to make sure that the $CallUuid$ of the called user/device corresponds with the Uuid of a user in the 2N device that manages the lift. As this is an additional feature, you may still use this 2N device to enable lift buttons directly e.g. via Bluetooth or RFID.    2N Mobile Video setup Configuration of 2N Mobile Video is described in this Video – 2N Mobile Video: registration and setup or here: Switch codes – How to unlock the door?   2N  IP Handset setup Configuration of 2N IP Handset's call features and switch codes is described here: Direct call – How to set up a 2N IP Handset for a direct SIP call (without PBX) and how to open door   2N Indoor Touch 2.0 setup Configuration of 2N Indoor Touch 2.0 is described in this Video – Setting up calls between 2N Indoor Touch 2.0 and 2N IP intercoms or here: How to set up calls from/to 2N IP intercoms?    Last update  2022-10-24    Devices used  2N IP Verso  2N Access Unit 2.0  2N Indoor View  AXIS A9188-VE Network I/O Relay Module    Licenses required  Gold license (For IP intercoms)  Lift Module – only for the device that controls the lift    Compatible 2N intercoms for calls and lift control  2N IP Style  2N IP Verso  2N IP Force  2N IP Safety  2N IP Vario    Compatible 2N devices for lift control  2N IP Style  2N IP Verso  2N IP Force  2N IP Safety  2N IP Vario  2N Access Unit 1.0  2N Access Unit 2.0  2N Access Unit M    Compatible 2N answering units  2N Indoor View  2N Indoor Compact  2N Indoor Talk  2N Mobile Video  2N IP Handset  2N Indoor Touch  2N Indoor Touch 2.0

Question 37

Lockdown feature in 2N Access Commander

Accepted Answer

2N Access Commander enables emergency "lockdown" of connected units withineither single device, arbitrarily defined groups, given zones, companies or all devices (in all companies).   Does not work for: offline, inactive and devices with incompatible firmware older than 2.32.If the device does not become online until after the lockdown has been applied, it will also automatically go into lockdown.     By the buttons at the given entities The button for lockdown is always located in the settings of the given entity (device / zone / company) in the relevant section of the 2N Access Commander's web interface.See the following pictures:    Lockdown for particular device    Lockdown release for particular device    Lockdown for a zone:    Lockdown release for a zone:     Lockdown for a whole company:    Lockdown release for a whole company:      Lockdown for all devices connected to the 2N Access Commander:  Lockdown release for all devices connected to the 2N Access Commander:       By widget on Dashboard  In the 2N Access Commander's web interface, in the Dashboard section, select the "Lockdown" widget:    We will add devices or zones for which we want to manage the lockdown using the widget (we can also name the widget):    Emergency lock is then performed for the given units using the LOCKDOWN button:     Then we see the locked state of the devices and in the same way we can cancel the lockdown again:

Question 38

Logs management

Accepted Answer

In the 2N Access Commander, it is possible to see certain logs with the possibility to export them with a specific time zone. By default, the log time is in Coordinated Universal Time (UTC). More detailed description can be found in the 2N Access Commander manual.  The logs are also part of the 2N Access Commander backup file. If the backup of the 2N Access Commander is imported, all the logs are imported as well. More information about the 2N Access Commander backup can be found in this FAQ article.    Log types System logAccess Log Export Log export date and time settingsLog export    Log types System log The System Logs page shows a list of events and notifications that have been generated. It can be found in the "System log" section of the web interface.  The system log list provides the following data on each event and notification: Severity (info, warning, error)Time of the event.Category to which the action falls (Device state, Import, User synchronisation, System, User actions, Area limits)Entity concerned (device, user, zone, visitor...)Brief description of the eventAuthor Click the row to open detailed information on the selected record.    Note Those logs are displayed so that the user may observe based on their user rightsData is written in English in the logs       Access Log The Access Logs page shows records of successful/unsuccessful authentication attempts and emergency lockdown records. It can be found in the "Access log" section of the web interface.   The Access log list includes: Category Access enabledAccess deniedPublic AccessLocking – device lockdown Time of the eventUser who executed the actionGiven the user’s companyZone where the action happenedDevice on which the action happenedAuthentication used for the attempt (PIN, QR code, etc.)     Click the row to open detailed information on the selected record.    Note Those logs are displayed so that the user may observe based on their user rights Data is written in English in the logs       Export Log export date and time settings Since the 2N Access Commander version 3.5, it is possible to configure the Log export date and time, which will be shown in the exported CSV file.  The setting can be found in the "Settings -> Configuration -> Server date and time" section of the web interface.  Simply edit the parameter, select if you want to use the Coordinated Universal Time (UTC) or a locally configured time for the 2N Access Commander and confirm the selection.          Log export To export the logs, click on Export above the list to download the list in a CSV file.  The export will be shown in the selected time.

Question 39

Management over the Internet

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer.   You can easily manage 2N IP Intercoms and 2N Access Units with 2N Access Commander over the Internet as well as 2N Access Commander web interface itself. Since all of them behave like any standard IP device, you can use standard network techniques for interconnection.   Prerequisites 2N Access Commander, no additional license is required.2N IP Intercom or 2N Access Unit, no additional license is required.Device is connected to different network than 2N Access Commander.     Manage 2N IP devices with 2N Access Commander over the Internet    NAT and Port forwarding Since connection is established from 2N Access Commander to each 2N IP device, all 2N IP devices must be reachable over the Internet. In standard environment, such 2N IP devices will have private IP addresses and only one shared public IP address actually reachable from the Internet.You need to use NAT / Port forwarding on the site with 2N IP devices (SITE B and Router B on the image below).Each 2N IP device listens on port 443 for an incoming connection.You do not need to perform this action on SITE A, just make sure that 2N Access Commander is allowed to access the Internet.    When network configuration on SITE B in our example is set correctly, you can add each 2N IP device from SITE B to 2N Access Commander on SITE A manually using SITE B´s Public IP and assigned Public port in the format :.The device scanner inside 2N Access Commander cannot be used in this scenario.With its specific implementation on your sites and network devices, any company network administrator will be able to help you.               Site-to-site VPN Connects two portions of a private network or two private networks.For example, this allows to have routed connections with separate offices, or with other organizations, over the Internet.Both 2N IP devices and 2N Access Commander can act as in the same local network.   With its specific implementation on your sites and network devices, any company network administrator will be able to help you.         Manage 2N Access Commander web interface over the Internet The same network techniques you can apply also to allow different users to connect to 2N Access Commander web interface which listens on port 443 as well.

Question 40

MIFARE DESFire EV2/EV3 - How to install 2N PICard Commander and program cards

Accepted Answer

Product Description 2N PICard Commander is a software used for the encryption of access card credentials. The app creates projects which generate a set of encryption and reading keys. The reading keys from these projects can then be imported into a 2N device or 2N Access Commander which will then take care of the distribution into 2N devices connected to the 2N Access Commander. The 2N PICard Commander technology is used to encrypt the MIFARE DESFire EV2 and MIFARE DESFire EV3 cards.  Requirements The main requirements are installed 2N PICard Commander, RFID USB reader and writable Mifare Desfire EV2 or EV3 cards (either existing or purchased from 2N). Detailed information can be found in the 2N PICard Commander manual.   Licensing You need to install 2N PICard Commander first.Once installed you will need to add the license. The license is tied to the USB reader. You will need the Device key which can be found under Help/License:  At the bottom, you will see the Device key of the connected USB reader (the USB reader has to be connected to the PC where the 2N PICard Commander is running). Once the license file is loaded it will be confirmed in the 2N PICard Commander app.   If you connect a USB reader other than the licensed one, you will be notified in the app as the new reader would have to be licensed as well.      Getting started By creating new projects you can encrypt access card groups in different modes. Each project can be set up for a specific use of these cards.Each project generates unique encryption and reading keys. Only one key can be imported into a 2N device or 2N Access Commander.   To start a new project select the Start new project button or File/New project (CTRL + N). To open an already existing project you can select it at the bottom of the application or select the Open project button and open it from a file. Alternatively, select File/Open project (CTRL + O).   Setting up a new project When you start a new project you need to set these parameters:  Project name – Name of the project  Project description – Any notes you would like to mention     Next, you need to select a main encryption key (MEK). Make sure it is unique and strong enough. The 2N PICard Commander app uses the MEK to generate key sets for card encryption. If you lose the project, a new one can be created with this MEK to access the encrypted cards since the key sets are generated based on this MEK. This means that two projects with the same MEK will have the same key sets.     MEK cannot be shown nor changed later!        Mode selection There are 3 modes to choose from for the project.      Selecting Card will be used only for access control with 2N will enable Random ID which cannot be disabled afterwards!       Selecting Card is already used for other applications is irreversible     Once you have completed previous steps you will be able prompted to save your project.The file will be saved as projectname.picprj.You also have the option of protecting the project file with a password.    A forgotten password cannot be viewed or changed at a later date    Advanced settings     Encrypting cards Once the project is set up you can start encrypting cards.Start by selecting Add card button under Card encryption.  This will show you a prompt to place the card on the reader and leave it there. Once you do so you should see the change in the window. If the card is compatible, you can click on the Encrypt button.      In case there is some issue with the card you will also be notified:   The card cannot be personalized – 2N PICard Commander doesn’t have access to the MEK of the presented card. Not enough free space on the card – There is not enough space on the card to upload the 2N PICard technology. Unsupported card – The program doesn’t support the presented card’s type Only Mifare DESFire EV2 or EV3 are supported – The presented card is MIFARE DESFire EV1 Communication failure with card – The reader couldn’t read the card. Place the card on the reader and do not remove it before the encryption process is complete.     Once the encryption process is completed you will get confirmation on the screen    Read keys export In order for the 2N readers to access the data on the card they need to know the read key of the project. You can either export the read keys for a 2N device as a file or into the 2N Access Commander which will then distribute them to devices connected to it. To export the keys, press the Export button on the main screen (or Project/Export reader keys) This will open a window where you can select how you want to export the keys.    To export the read keys as a file, select where the file should be saved and choose a password.  Once exported, you can upload the file into the 2N unit  Select the .picrok file and fill in the password.  Or you can upload the file to Access Commander: Version 3.0+  Version 2.7.1 or older  Alternatively, you can export the read keys directly into the 2N Access Commander by filling Access Commander's IP address and admin account credentials.  Once the keys are imported, make sure to also pair the reader on the 2N device.This function is found under Hardware/Extenders:    Formatting the card To format the whole card or delete the 2N PICard application open the Project/Format card. Here you can choose whether you want to completely format the card or only delete the app.     Practical tips Here you will find some practical tips and situations you can encounter while using 2N PICard Commander.    What if I lose the project file? You need to know the Main Encryption Key. If you lose a project file, you can create another one with the same MEK and you will be able to edit the existing cards within that project or add new ones.As mentioned above, the encryption keys are based on the MEK so as long as the MEKs in different projects match you are able to add and/or edit cards.     How to solve a situation when there are both Picard-compatible and Picard-incompatible readers on the site?  In this situation you will need to use two parts of one card – one using the 2N PICard Commander application and the other using a format readable by a reader incompatible with 2N PICard Commander – a public one (i.e. card's serial number, etc..)This way you will make sure the user has correct access with one card.     How do I ensure the best security using 2N® PICard Commander? The most secure way is to use only 2N PICard cards. To further support this it is recommended to disable all the other card types on the reader (Hardware/Extenders) and use a project using ID randomization.Along with a strong MEK and the project file safely stored you ensure the best security.     How can I write a PICard credential on a card already being used by a customer? First, you need to know the PICC master key of the respective card. The card must be also set in a way that it requires the PICC master key to be entered to write a 2N PICard application on it. Then you may create a new project in a standard way as described above. When selecting the card mode, select the “Card is already used for other applications (advanced settings).

Question 41

Migrate configuration from old installation to new one (the same version)

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time.It also allows migrating configuration from your current installation to a new one (the same versions).   Prerequisites Two installations of 2N Access Commander;no additional license is required for themYour source installation the latest possible versionNew installation the same version as the source installationInstallation of virtual machine and Box solutionsUpdate of the system    Feature properties The procedure can be applied only between the same 2N Access Commander versions.Supported by a virtual machine (VirtualBox, VMware, Hyper-V) and also by a Box (mini PC) distribution.Virtual machine configuration can be migrated to another virtual machine or to Box distribution as well.Box distribution configuration can be migrated to virtual machine or to another Box distribution as well. After the migration the source installation can no longer be used.It is turned off automatically and its web server is deactivated (you can´t access it more).   Web interface method In the source installation...Go to Settings - Configuration section, enable SSH and set the root password.     In the new installation... Go to Settings - System backup section and click on Migrate.      Fill in details about the source installation of 2N Access Commander (IP address and root user credentials), confirm by clicking on Migrate.      After a successful migration the source installation can no longer be used.It is turned off automatically and its web server is deactivated (you can´t access it more).The new Access Commander now contains all data from the source Access Commander.Please check if everything works properly.    Linux console method If you would like to import to a virtualization platform, install the new image of Access Commander the same version.Installation of virtual machine and Box solutionsIf you would like to import to a Box distribution, connect a VGA or HDMI monitor and USB keyboard to the device with Access Commander the same version.In the source installation...login to the linux console as root,note IP address,enable SSH connection,do not turn it off, it must be still running.        In the new installation...login to the linux console as root;If you login for the first time, use the factory password 2n and then set new strong password.check the network settings, IP address must be unique, not the same as used for the source installation.        Go to the section "Backup and Restore" - "Import", fill in the IP address of the source installation, enter the root password and complete the process.          After a successful migration the source installation can no longer be used.It is turned off automatically and its web server is deactivated (you can´t access it more).The new Access Commander now contains all data from the source Access Commander.Please check if everything works properly.Your system will be synchronized only with new Access Commander now.The source installation is prepared for deleting after checking of the new installation.      If you have older version of the system with different look of the web interface, please click here. Web interface method In the source installation...Go to Settings - SSH section, enable SSH and set the root password.     In the new installation... Go to Settings - SYSTEM BACKUP section and click on IMPORT.      Fill in details about the source installation of 2N Access Commander (IP address and root user credentials), confirm by clicking on IMPORT.      After a successful migration the source installation can no longer be used.It is turned off automatically and its web server is deactivated (you can´t access it more).The new Access Commander now contains all data from the source Access Commander.Please check if everything works properly.    Linux console method If you would like to import to a virtualization platform, install the new image of Access Commander the same version.Installation of virtual machine and Box solutionsIf you would like to import to a Box distribution, connect a VGA or HDMI monitor and USB keyboard to the device with Access Commander the same version.In the source installation...login to the linux console as root,note IP address,enable SSH connection,do not turn it off, it must be still running.        In the new installation...login to the linux console as root;If you login for the first time, use the factory password 2n and then set new strong password.check the network settings, IP address must be unique, not the same as used for the source installation.        Go to the section "Backup and Restore" - "Import", fill in the IP address of the source installation, enter the root password and complete the process.          After a successful migration the source installation can no longer be used.It is turned off automatically and its web server is deactivated (you can´t access it more).The new Access Commander now contains all data from the source Access Commander.Please check if everything works properly. Your system will be synchronized only with new Access Commander now.The source installation is prepared for deleting after checking of the new installation.

Question 42

Milestone integration - How to setup with 2N Access Commander

Accepted Answer

2N Access Commander can be integrated into the Milestone XProtect camera system using the 2N Plugin for XProtect Access tool.It allows you to monitor events and control devices from 2N Access Commander directly in the Milestone Xprotect Smart Client application.   For detailed information on how to work with the XProtect Access module, use the VMS documentation and the Milestone XProtect Smart Client software.     This article applies to the following products and licenses:  2N Access Commander (version 3.2.0 or higher)  "Access control door" license for Milestone Xprotect (information on added licenses can be seen in: Milestone XProtect Management Client > Basics > License Information) provided by Milestone Systems A/S   XProtect Access module - version 2018 or newer (XProtect Enterprise, Professional, Corporate, Express, Expert)  2N plugin for Xprotect Access (version 1.6.0.113 or higher)  Gold license should be installed on 2N IP Intercom to ensure faultless operation of the plugin (license is not required for 2N Access Unit) Trial Gold license on 2N IP Intercom can be enabled for approximately 30 days     Installation of the 2N Plugin for XProtect Access  Configuration of XProtect Access  How to project changes made in 2N Access Commander settings into the Milestone XProtect Access system  How to remove 2N Access Commander from Milestone Xprotect Access Control  Adding hardware (not only camera)       Installation of the 2N Plugin for XProtect Access Download the plugin from Download Center on 2N website in section Download Center Run the 2N Plugin for XProtect Access installation file on the same computer where the XProtect Event Server service is active:    The installation program automatically detects the location (folder) of the XProtect Event Server and installs the plugin in the correct subfolders:     Finally, the installation file automatically restarts the service for the Xprotect Event server.If this does not happen for any reason, you must restart the XProtect Event Server manually using the Milestone XProtect Management Client, or using Windows services.      Configuration of XProtect Access  Open the application Milestone XProtect Management Client. Create a new integration by right-clicking on the Access Control section and selecting "Create new...":     In the next step name the integration and select 2N Access Control as the "Integration plug-in", then other parameters will appear:   Fill in the given parameters and continue with the "Next" button. Parameter:Assignment:NameThe name of the access system within the software Milestone XProtectAddressNetwork IP address of the 2N Access CommanderPortNetwork port for the connection with 2N Access Commander (default is 443)UsernameUser name of the admin account in the 2N Access Commander (default is "admin")Password or API Key Administrator's password in the 2N Access Commander, or the API Access Token    Note: You can use API Key from the Access Commander instead of the Username/Password combination. For API Keys you will need at least Advanced license for 2N Access Commander     The XProtect Event Server will establish a connection with the 2N Access Commander and load individual entities from the access system.Milestone XProtect Management Client will then display a list of these downloaded entities from 2N Access Commander - continue by clicking the "Next" button:    The "Associate Cameras" window will appear - we will now skip, as this can be done later and the procedure is below in this FAQ in the chapter "Adding Hardware".    So we click on "Next" and then a window will appear that we have successfully added the integration, which we close by clicking on the "Close" button. This completes the initial configuration and the 2N plugin is active.      How to project changes made in 2N Access Commander settings into the Milestone XProtect Access system If changes are made in 2N Access Commander, such as adding, removing or renaming a device, these changes must then be saved in the Xprotect Access module.  Within Windows, restart Milestone XProtect Event Server in Services:      In the Milestone XProtect Management Client, in the Access Control section, double-click the integration in the right column and on the General Settings tab then on "Refresh Configuration" (XProtect Event Server then reads the changes from 2N Access Commander):       Verify that the loaded changes match the actual configuration, and if so, confirm them by clicking "Apply":      How to remove 2N Access Commander from Milestone Xprotect Access Control If you only want to remove the created integration, in Milestone XProtect Management Client right-click on it and select "Delete" and then confirm:   To completely uninstall the plugin:  Remove all settings from Milestone Xprotect related to integration with 2N Access Commander.  Uninstall 2N Plugin for XProtect Access from the computer where it was installed.        Adding hardware (not only camera)  In the web interface of the 2N IP Intercom go to the Services > Streaming section and enable the RTSP server:        Go to the Milestone Xprotect Management Client application, Servers section, Recording Servers subsection, where you right-click on the given server (PC) within "Recording Servers" in the next column and select the "Add Hardware" option:   Wizard "Add Hardware" appears, where you select the "Express" option (for automatic detection of devices on the network) or "Manual" (for manual addition), and click on "Next":    Then click on "Add" on the right and add the User name and Password corresponding to the Name and Password of the activated ONVIF account on 2N IP Intercom - see the picture on the right (Enhanced Video license required on the intercom) - and click "Next" in the wizard:    In case of manual configuration - check the "ONVIF" option and click on "Next":    In case of manual configuration - fill in the IP address of the device to be added (and optionally check "Use HTTPS" for encrypted network communication) and click on "Next".Use the "Add" button (right) to add another device at once:    Now in each of the listed configuration modes - after clicking on the "Next" button (2x) for the device to be added, select, whether you add a microphone, speaker, or logic inputs and outputs as the active device in addition to the camera. Click "Next" to continue:    Click on the briefcase icon next to "Default camera group": And after clicking on the "plus" button at the bottom left, name the group in which the camera will be:  Confirm by clicking on "OK" and then on "Finish". Similarly we may add other mentioned hardware in addition to the camera. Go to the Access Control section > created integration with 2N Access Commander > Doors and Associated Cameras tab > click on the selected unitand find the added camera in the given folder on the right, which you drag with the mouse under the 2N unit - see the picture below.   Click the floppy icon in the upper left (within the Milestone XProtect Management Client) to save the changes. Launch the Milestone XProtect Smart Client application, click on "Setup" on the top right, then add a new "View" on the left and click on "Setup" again:   Click on the added "View", then on the camera in the group and drag it with the mouse to the desired window:  Added:  Further procedure for general configuration can be found in our Interoperability manual - here, or Integradion Hub - here

Question 43

Milestone XProtect - Alarm event from 2N device on Milestone XProtect

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   With physical and cyber security threats on the rise, it’s more important than ever to level up your business security systems. Milestone XProtect video management software (VMS) connects your cameras, sensors, analytics, and sites in one easy-to-manage interface.  Our 2N Access Units, 2N IP Intercoms and 2N Access Commander via 2N Plugin for XProtect Access integration for XProtect Access tool can be part of it and it is also possible to configure an Alarm event in the Milestone XProtect Smart Client such as door opening, door forced open, tamper switch activated, or other actions. Prerequisites  2N Access Commander 3.3.0  2N Access Unit or 2N IP Intercom connected to the 2N Access Commander Configured Milestone XProtect with 2N Access Commander via 2N Plugin for XProtect Access integration(According to this article: Milestone integration - How to setup with 2N Access Commander | FAQs | 2N )   Configuration steps  Device Event Configuration  Rules and Events Configuration    Device Event Configuration  After successfully adding a device to the Access Commander and synchronizing the devices with Milestone via a plugin, add the desired event:  Select the Access Control (1) tab and the Access Commander (2)  On the bottom of the screen, click on the Access Control Settings (3)  Lastly enable the selected event and configure it as an Alarm (4)   After finishing the setting up the events save the configuration      Changes should take effect and the configuration will be detected in the Milestone Smart Client (5):     Rules and Events Configuration You can assign a custom rule which triggers an action, based upon an event:  Go under Rules and Events (1) in the Milestone XProtect Management Client  Right-click on the Rules tab on top and then select Add Rule (2)      Event can be configured by selecting the desired rule type (3)   Click on the highlighted link (4)  Then select the desired Access Control Event (5)      Select the desired 2N Units from the Sources list (6)  Click Add (7) to import the device into the Selected list (8)       Set up the performed action, in this case Start recording on an assigned device (9) Click "OK" and "Next"     Then set up the action duration or stop action  Lastly - click on the Finish (10)

Question 44

Milestone XProtect - How to add, monitor and control door units stored in 2N Access Commander

Accepted Answer

2N Access Commander can be integrated into the Milestone XProtect camera system using the 2N Plugin for XProtect Access tool.It allows you to monitor events and control devices from 2N Access Commander directly in the Milestone Xprotect Smart Client application.     You must first configure the Milestone XProtect Management Client and the XProtect Access module, if you haven't done that yet, please follow this FAQ first:Milestone integration - How to setup with 2N Access Commander | FAQs | 2N      Access Control interface In the Milestone Xprotect Smart Client application, go to the Access Control (1) section and the Doors (2) subsection, where you can immediately see whether a specific "door" is closed or open. At the top right you can also see the camera image of the selected "door" (3):  Door Trigger  Activated by clicking on the "Trigger" button (1) on the right (after clicking on the given door in the list on the left) you can also control it (or the assigned switch on the given unit) and at the bottom you can also see directly the door State (2), whether it is open (as in the picture below)  You can see the current state (2) under the camera picture:   Door Lockdown  Activated by clicking on the "Lockdown" button (1) - and using the "Normal operation" button next to it, the lockdown is deactivated again  You can see the current state (2) under the camera picture:   Door Hold Open  The door can be kept open using "Hold Open" button (1) and using the "Normal operation" button, the door can be closed.  You can see the current state (2) under the camera picture:         Live interface with map You can import a map to better manage the view of the interface:  Prepare a map of the object (floor plan in JPEG / BMP / PNG format)  In the Milestone XProtect Management Client, in the Live view section, click on "Setup" (1) in the upper right and left in the Views subsection firstly click on the "View" (2) where you want to add the map.  Then in the System Overview subsection drag the "Map" (3) object to the selected window of the chosen "View".  A window will appear where you can name the map (4) and after clicking on the "Browse" (5) button, select the map from your directory.  Click "OK" (6) to confirm:   Your map will appear in that window If the toolbox does not automatically appear - right-click on it and select "Toolbox" (7)  In the Toolbox (7), click on the door icon (8) and then click on "2N Access Commander" on the right (or the appropriate name of the integration created in Milestone XProtect Management Client) - in this example - "Offices 2N" (9).  Then you can see the relevant 2N door units, which you can drag and drop (9) to the appropriate place on the map.  In the same way you can also place the camera and other available elements on the map. Finally click on the "Setup" (10) button again at the top right.       Now on the map you can see the status of the door, which you can also control by right-clicking on the selected door icon, see bellow:  "Trigger" to activate the given switch (=> open the door).  "Lockdown" to permanently lock.  "Hold open" to keep door opened.  "Normal operation" to cancel the lockdown or stop holding door.   Overlay buttons You can add an overlay buttons to the live stream, like so: You can check this article for detailed procedure how to add the additional overlay buttons, under "Overlay Buttons"  - Milestone XProtect and 2N IP Intercom integration | FAQs | 2N    Door Status Icons   Examples of icons representing the different states of doors:        Note - If no input is assigned in the web interface of the 2N unit in the Hardware > Digital Inputs > Door Open Sensor section, where the door sensor should be physically connected,you will see in the Milestone XProtect Management Client at the given door,that it is "Without sensor", resp. crossed-out sensor icon at the bottom left of the door on the map, and of course you don't know then, whether that door is really physically open or not:           Alarm Manager interface (with map) To register alerts when a door is open for a long time or when a door is opened unauthorized, make the necessary settings for the mentioned functions directly on the unit - see here: Door open too long Detection of long open doors at 2N IP Intercom Unauthorised door opening Detection of unauthorized door opening at 2N IP Intercom Access control events  In the Milestone XProtect Management Client go to the Access Control (1) section and click on the added integration with 2N Access Commander in the column Access Control (2) on the right.  In the new window select the Access Control Events (3) tab below and for the items "Door Forced Open Alarm" and "Door Open Too Long Alarm" select "Alarm" as the Event Category (4) on the right:    Then save the made changes at the top left. Alarm Definition  Go to the "Alarms" (1) section and the "Alarm Definitions" (2) subsection, where in the next column right-click on Alarm Definition Information and select "Add New":  Select a Name (3) the alarm.  For Triggering event select "Access Control Event Categories", "Alarm" and the given door unit (4).  For Related map select the map you have created (see the previous chapter "Live" interface with map") (5).  Under Related cameras (6) you can also select the camera (of the given unit), the image of which you will then see together with the given alarm (see the blue frame in the picture above).   Then save the changes again at the top left.  Recorded Alarms  In the Milestone XProtect Smart Client application go to the Alarm Manager section, where in case of activation of the created alarm (see the list at the bottom of the picture).  You will see the added map with icons on the left side (which can be used to control the selected door as in the "Live" section) and at the same time a flashing red circle around the door appears.  On the right you will also see the image from the assigned camera, with the recording of which you can then continue working.  You will see the same on the map in the "Live" interface and the name of the alarm as well as in the "Access Control" interface for the given door on the "Doors" tab.

Question 45

Milestone XProtect - How to display video tracks and event information surrounding an access by a user from 2N Access Commander

Accepted Answer

2N Access Commander can be integrated into the Milestone XProtect camera system using the 2N Plugin for XProtect Access tool.It allows you to monitor events and control devices from 2N Access Commander directly in the Milestone Xprotect Smart Client application.     You have to configure the Milestone XProtect Management Client and the XProtect Access module, firstly. If you haven't done that yet, please follow this FAQ: Milestone integration - How to setup with 2N Access Commander     Supported access credentials are:  RFID card  Code  Bluetooth  Fingerprint or License plates QR Code      Step by step guide  Cardholders in Management Client  Access Monitor  Access Monitoring  Access Control  Image Control  Cardholders in Smart Client    Cardholders in Management Client In the Milestone XProtect Management Client, Access Control section - an added integration with 2N Access Commander, verify whether the required users / RFID card holders and other credentials users have been synchronized from the 2N Access Commander:  Select "Access Control" (1) tab  Select "Access Commander" (2) under the selection  Select "Cardholders" (3) and check the desired user info (4)    Access Monitor  In the Milestone Xprotect Smart Client, in the Live interface, click on "Setup" (1) at the top right, then on the selected "View" (2) on the left and then from "System Overview" drag the "Access Monitor" (3) box to the field with the image from the given camera.  In the new window "Access monitor Settings" (4) then select the unit as "Door" (5) and confirm by clicking on "OK" (6) (at the end press the "Setup" (1) button at the top right again):   Access Monitoring In the Milestone Xprotect Smart Client application you then see information about the accesses of the added card users - directly in the Live section at the camera view field:   Access Control Or especially in the Access Control section on the Events tab, where you can see exactly who has ever authenticated, and you can play back the recording from the given camera also from the time before and after that access event:   Image Control  The introductory image is from the time the card is inserted by the user, but it is possible to play back a recording of the camera from the entire time when motion was detected in connection with this event (and 3 seconds before and after motion detection), even backwards.  You can further zoom in on the images by intuitively "cropping" the desired area with the mouse or using the controls on the left side:   Cardholders in Smart Client  In the "Access Control" (1) section, click on the "Cardholders" (2)  All events can be displayed here (within the above-mentioned "Events") related to the given user by clicking on "View cardholder events" (3) on the right:

Question 46

Milestone XProtect Smart Client - log operator's actions

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   With physical and cyber security threats on the rise, it’s more important than ever to level up your business security systems. Milestone XProtect video management software (VMS) connects your cameras, sensors, analytics, and sites in one easy-to-manage interface. Our 2N IP Intercoms or 2N Access Commander via 2N Plugin for XProtect Access tool can be part of it and it is also possible to log every operator's action from Smart Client such as door opening (trigger), lockdown, etc.   Prerequisites Configured Milestone XProtect with our 2N IP Intercoms or 2N Access Commander via 2N Plugin according to this articles: Milestone XProtect and 2N IP Intercom integrationMilestone XProtect and 2N Access Commander integration      Creating a rule     In Milestone XProtect Management Client go to Rules and create a new rule.       Select which event to detect on which device periphery.        Optionally select conditions to apply.    Select an action to perform, e.g. creating a bookmark in video recording timeline,and also on which devices.         Finish creating the rule.        Applying the rule  In the Smart Client, trigger the event and go to the recording preview.  Click on the saved bookmark.

Question 47

Milestone XProtect - Video Pop-up on 2N Device's Action

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. After adding 2N IP devices as an ONVIF camera into Milestone XProtect and integrating Milestone XProtect with the 2N Access Commander (Milestone integration - How to set up with 2N Access Commander), it is possible to set up a video pop-up window in response to a specific action on the 2N IP device.    This function utilises the ONVIF virtual inputs, which need to be set up in the 2N device's automation function and in Milestone XProtect Management Client's rules and access notifications sections.    With the video pop-up window, it is possible to display a video from the 2N IP device, listen to the audio, and utilise the push-to-talk function if the computer with the Milestone XProtect Smart Client has a microphone connected.    This article applies to the following products and licenses:  2N Access Commander (version 3.4.2 or higher)  XProtect Access license for Milestone XProtect (information on added licenses can be seen in: Milestone XProtect Management Client > Basics > License Information), provided by Milestone Systems A/S (XProtect variants)  2N plugin for Xprotect Access (version 1.6.0.113 or higher)  2N Gold license should be installed on a 2N IP Intercom to ensure faultless operation of the plugin  Trial Gold license on 2N IP Intercom can be enabled for approximately 30 days    2N IP device configurationONVIF virtual inputs mappingMilestone XProtect Management configuration Access Request NotificationRule creation Video pop-up window   2N IP device configuration In the "Services -> Automation" section of the 2N IP device's web interface, it is necessary to create a function based on which action should trigger the ONVIF virtual output.  Here's an example where the ONVIF output is triggered by the first call button.     Please note that the port (1) may differ from 2N models (more about port mapping later). We also recommend changing the ONVIF virtual input event's level to "low" with a delay after a few seconds (2).    ONVIF virtual inputs mapping In the "Devices -> Inputs -> Project folder" section of the Milestone XProtect Management Client, it is possible to see all available inputs.     To find out which input of the connected 2N IP device in the Milestone XProtect Management Client is triggered by the port from the automation function, select the folder containing the inputs, perform the action which should trigger the ONVIF virtual input, and watch which input in the "Info" section (3) gets triggered. You will need the information later when configuring rules.         Milestone XProtect Management configuration In the Milestone XProtect Management Client, we will need to create an access control notification and then run it based on a received action with a rule.    Access Request Notification Go to the "Access Control -> "Connected Access Commander" -> Access Request Notification" section and add a new Access Request notification and create a name for it (4).     Assign the hardware components, such as camera, speaker and microphone, by selecting the components of the 2N IP device, and select a sound alert.        After selecting the 2N device's components, add a command, select the Trigger [source] and save the configuration with the save button in the top left corner (6).     Rule creation Go to the "Rules" section, right-click on the Rules (2) and select "Add Rule" from the menu.  A new window will be opened where the event and action will need to be selected.     In the new window, name the rule, select "Perform an action on " (1) in the "Rule type" section and click on the bold event (2) in the "Edit rule description" section.     A new window will be opened, where the event "Input Activated" needs to be selected in the "Events -> Devices -> Configurable Events" section.      Then, it is necessary to select the input of the 2N IP device.  Click on the bold devices/recording server/management server (1) in the "Edit rule description" section and select the input of the 2N IP device in the newly opened window, and confirm it by clicking on the "OK" button.         Now you can proceed by clicking on the "Next" button, which will show the available conditions that can be added if needed (not the case in this example).    Then click on "Next" to get to the window with "Select actions to perform" (1).   In this section, select the "Show " (2), which will add the Show parameter of the Rule. Then click on the bold Access Request Notifications (3).     A new window will appear, where it is necessary to select the previously created access request notification.      After selecting the access request notification, you can notice the rule description being configured.  You may proceed by clicking on the "Next" and then the "Finish" button.        Video pop-up window By performing the event (KeyPressed in this case) selected in the 2N IP device's automation, the video pop-up window is displayed based on the Access Request Notification and the Rule.  It is possible to listen to the audio and speak by using the push-to-talk buttons (1).

Question 48

Network proxy settings in 2N Access Commander – what they are and when to use them

Accepted Answer

This article explains the purpose of the proxy settings in the Access Commander. It describes what a proxy is, when (and when not) to configure it, and what each field in the proxy configuration means. It’s meant to help to understand the settings — not to set up own proxy server.  Requirements 2N Access Commander 3.4.2 or newer Proxy Settings Some organizations use proxies to control access, add security, or monitor usage. A proxy server is a server that sits between software and the internet.  If you are using a normal home or office internet connection, you usually don’t need to change these settings. You only need to enter proxy details if:  Your IT department or network administrator has given you proxy settings.  You are on a managed or restricted network that requires all traffic to go through a proxy.  If you are unsure, just leave these fields empty. 2N Access Commander will connect directly without a proxy. Settings explanation   HTTP proxy – For standard web traffic (http://) from 2N Access Commander to internet. HTTPS proxy – For secure web traffic (https://) from 2N Access Commander to internetFTP proxy – For file transfers using FTP.Don’t use proxy for – enter Domains or IP addresses that should connect directly, without using the proxy. Localhost and 127.0.0.1 never use a proxy automatically.  Example: .example.com (all addresses under domain example.com) Example: 192.168.1.0/24 (local network range) - if you need to not use proxy for connection between 2N Access Commander and 2N OS devices fill in the local network which 2N OS devices belongs to.  Example: 192.168.1.10 (direct IP address) - if you need to not use proxy for connection between 2N Access Commander and 2N OS device fill in the IP address of that 2N OS device.    If you haven’t been told by your IT administrators to enter anything here, you can safely leave the fields empty.

Question 49

Occupancy Management in 2N Access Commander

Accepted Answer

This article describes:  STEP 1: Configure basic access for users.  STEP 2: Explanation of ACCESS POINT 1 and ACCESS POINT 2.  STEP 3: Configure ACCESS POINT 1 and ACCESS POINT 2 in devices.  STEP 4: Configure Area Restriction (Occupancy)  STEP 5: Add devices to Restricted AREA. Device can't be added  STEP 6: Set which ACCESS POINT is for Entry and which ACCESS POINT is for Exit There is an error message after adding the device  STEP 7: Enable the 'Occupancy' toggle      The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.      Occupancy management requires:  Access Commander 3.0.1 and later (It is recommended to use the latest version) Access Commander Pro license or Unlimited license IP intercoms / Access Units with firmware 2.38 and later (It is recommended to use the latest firmware version)  At least two access readers (RFID / bluetooth / fingerprint / keypad)  No one can enter/exit area without authorization, there is no REX button, etc.  Permanent operation of Access Commander. Connection between Access Commander and devices must be ensured.    Occupancy lets you keep track of how many people are in a restricted area at any given moment. It works by counting entry and exit events at access-controlled doors, giving you a real-time view of how many people are inside the zone. It also allows you to limit the maximum number of people that is able to enter this area.      STEP 1: Configure basic access for users Before you start configuring occupancy management, you need to have users created in the system and their access assigned to the relevant doors. Without this, it won’t be possible to set up the access logic correctly.You can find the procedure in the official manual here:   STEP 2: Explanation of ACCESS POINT 1 and ACCESS POINT 2 There are two ACCESS POINTS (directions) - ACCESS POINT 1 and ACCESS POINT 2.Access Units and IP Intercoms with one reader, please set as ACCESS POINT 1 (follow STEP 3). If there are connected extension modules as well:A) All extension readers that are on the same door side as the main unit please set as ACCESS POINT 1 (the same as the main unit, follow STEP 3).   B) All extension readers that are on the opposite door side than the main unit please set as ACCESS POINT 2 (follow STEP 3).      STEP 3: Configure ACCESS POINT 1 and ACCESS POINT 2 in devices Go to device's web management. You can use Access Commander feature:        Version 3.0 or newer In your device go to section Access -> Access rules  and select ACCESS POINT 1 or ACCESS POINT 2 for access modules. ACCESS POINT 1 is substituted by "Door Entry" value, ACCESS POINT 2 is substituted by "Door Exit" value.   Door Entry, Door Exit:    "Door Entry" = ACCESS POINT 1"Door Exit" = ACCESS POINT 2    In this section you are setting: If there is only ACCESS POINT 1, please go to section Access -> Access rules, enable ACCESS POINT 1 (Entry) and disable ACCESS POINT 2 (Exit).If both ACCESS POINTS are used in the device, then please enable both ACCESS POINTS (Entry Rules and Exit Rules).If both ACCESS POINTS (Entry Rules & Exit Rules) are disabled, device can't be added to Area restrictions in STEP 5.    At the same time you have to assign what module you set as Entry and what modules you set up as Exit.    If you are using your device for both entry and exit you need to allow both Entry and Exit and set modules you want to use for entry as entry module (or exit module) under Access -> Access rules -> Module -> Manage.  If you want to use the unit for Entry only, turn off the Exit, and assign all your modules as entry.  If you want to use the unit for Exit only, turn off the Entry, and assign all your modules as exit.   If you set up two devices, one for entry and second one for exit you can create restricted area where you have to use one for entrance and second one for exit:             Version 2.50 (LTS) or earlier Go to section Hardware - Extenders and select ACCESS POINT 1 or ACCESS POINT 2 for access modules. ACCESS POINT 1 is substituted by "Door Entry" value, ACCESS POINT 2 is substituted by "Door Exit" value.   Door Entry, Door Exit:    "Door Entry" = ACCESS POINT 1"Door Exit" = ACCESS POINT 2       If there is only ACCESS POINT 1, please go to section Services - Access control - Exit rules, enable ACCESS POINT 1 (Entry Rules) and disable ACCESS POINT 2 (Exit Rules).If both ACCESS POINTS are used in the device, then please enable both ACCESS POINTS (Entry Rules and Exit Rules).If both ACCESS POINTS (Entry Rules & Exit Rules) are disabled, device can't be added to restricted area in STEP 5.      If you are using your device for both entry and exit you need to allow both Entry and Exit (ACCESS POINT 1 and ACCESS POINT 2) and set modules you want to use for entry as entry module under Access -> Access rules -> Module -> Manage and set modules you want to use for exit as exit modules.  If you want to use the unit for Entry only, turn off the Exit, and assign all your modules as entry.  If you want to use the unit for Exit only, turn off the Entry, and assign all your modules as exit.  If you set up two devices, one for entry and second one for exit you can create area restriction where you have to use one for entrance and second one for exit:             STEP 4: Configure Area Restrictions (Occupancy area) Go to Access Commander - section Area restrictions - Area list and create restricted area to monitor occupancy.      STEP 5: Add devices to Restricted Area. In the created Restricted area click on Add devices button:    Device can't be added    If a device cannot be added or you cannot see device after you add it to the restricted area, please check in STEP 3 that at least one ACCESS POINT (Entry Rules or Exit Rules) is enabled.     STEP 6: Set which ACCESS POINT is for Entry and which ACCESS POINT is for Exit Click on configuration button and select which ACCESS POINTS (readers) are used for Entry to the area and which ACCESS POINTS (readers) are used to Exit the area:  Example:     There is an error message after adding the device Verify the device is added to the Zone - if the device was added to the restricted area but later removed from the Zone, the restriction will not work correctly.If there are "problems to be solved" as in the picture below, please go back to STEP 3 to check configuration of ACCESS POINTS ("Entry rule", "Exit rule" in devices). Make sure that all access rules on the devices are set up correctly.Make sure that all modules are correctly assigned to Entry or Exit. After resolving the issue we recommend to delete the device from the Anti-passback area and add it again.If the device is functioning correctly but still showing an error, try removing it from the Restricted Area and adding it again.If all the devices are set up correctly but still not working as expected (no anti-passback), try removing them from the area restrictions and adding them again.       STEP 7: Enable the 'Occupancy' toggle In this section you can also set up the Occupancy limit by clicking the blue pen icon and choosing what happens when the limit is exceededHere you can also enable Anti-passback. Occupancy and Anti-passback can be enabled at the same time. You can find out more information on Anti-passback in this article: Anti-passback - How to configure in 2N Access Commander       Occupancy Widget   Go to the Dashboard section and click the '+' button in the bottom right corner Select 'Occupancy'  from available widgetsYou can configure and rename it by clicking the three dots icon on the widget   This widget is useful for monitoring Occupancy in real time.

Question 50

Offline Bluetooth pairing and modes (Tap In App, Touch On Device, Card, Motion Detection)

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   To be able to use BT in My2n App , you have 2 different ways to pair your mobile with another 2N intercom or another 2N Access Unit. Online Pairing and Offline Pairing. We do recommend using cloud pairing exclusively as you can then easily manage all credential types for all users in My2N at one place. But you can use Offline pairing in case you are using Access Commander or if some users have some old mobiles (Android 8 or 9 , or iOS 15) and cannot use anything else that the old MobileKey App. For already running My2N site - If your site in My2N already uses offline paired credentials which you have created on the devices by enabling online pairing (enable My2N app access for at least 1 user) all offline paired credentials will be revoked. We recommend switching those offline paired users to online pairing. If not possible, you must create offline paired access for those users again.    Prerequisites 2N IP intercom or 2N Access Unit with Bluetooth interface and the latest firmware,no additional license is required (except the Motion Detection mode requiring GOLD license)My2N app the latest version on the mobile phone (Android 10 and later or iOS 16 and later) with enabled BluetoothOptionally for a centralized management you can choose from those two solutions (then you do not need to pair with each door device)2N Access Commander (at least Advanced license tier)My2N platform (access control is free of charge)          Pairing the My2N app with 2N device  2N device configuration Go to 2N device web interface, section Directory - Users, here open an existing user or create a new one.      In the User Basic Information part, fill in at least the name and save.    In the Access Settings part, you can limit the access validity, typically for guest access purposes.    In the WaveKey part, click the middle button with the Bluetooth symbol to generate the Pairing PIN.     In default, the pairing PIN validity is limited to 1hour. You can adjust this in the section Services - Access Control - WaveKey.      My2N app configuration       Tap the + icon and enter the prepared pairing PIN.      Go nearby the pairing device and start the pairing.         WaveKey modes configuration and usage by My2N app Bluetooth (WaveKey) authentication is available in 4 modes, please click on the one you are interested in:  Tap In App mode    Go to 2N device web interface, section Hardware - Extenders, here locate the Bluetooth module.Check that In App mode is activated as Start Authentication. It is also possible to specify the distance (Signal Strength) within which your smartphone will communicate with the Bluetooth module.     Go to close proximity of the device, open the My2N app and select the door you wish to access.            Touch On Device mode    Go to 2N device web interface, section Hardware - Extenders, here locate the Bluetooth module.Check that On Device mode is activated as Start Authentication. It is also possible to specify the distance (Signal Strength) within which your smartphone will communicate with the Bluetooth module.    Go to My2N app settings - Access cards section and enable background scanning.      Go in front of the device and tap the reader part or Bluetooth symbol (according to used 2N device) to open the door.                   Card mode    Go to My2N app settings - Access cards section and enable background scanning and card mode.  Swipe the smartphone across the Bluetooth symbol as you would have a card.Please be advised that sensitivity will be increased within confined metallic spaces such as small elevators.               Motion Detection mode    Please be advised that this mode requires GOLD licence because of using motion detection.     Go to 2N device web interface, section Hardware - Extenders, here locate the Bluetooth module.Check that Via Motion Detection is activated as Start Authentication. It is also possible to specify the distance (Signal Strength) within which your smartphone will communicate with the Bluetooth module, the optimal is Long.    Go to section Hardware - Camera - Internal Camera and enable the Motion Detection feature. You can also select how sensitive you wish to set the motion detection to be by adjusting the Sensitivity Threshold and Detection Area.     Go to My2N app settings - Access cards section and enable background scanning.     Walk towards the 2N device to activate the motion detection. If you are authorized, the door will open.                If you are using the no more supported 2N Mobile Key app ...  If you are using the no more supported 2N Mobile Key app, click here to see the instructions for it.     Pairing the 2N Mobile Key app When in close proximity to 2N IP Intercom equipped with a Bluetooth module, run the application and tap on the PAIR NEW DEVICES button      Android  iOS        The app will start searching for devices in close proximity.      Android  iOS        The app will ask for authorization. Please insert the pairing code you generated in the previous steps and tap on CONFIRM button.      Android  iOS                Using the 2N Mobile Key app  Tap In App mode If you have already paired the 2N Mobile Key app with the 2N IP Intercom equipped with a Bluetooth module, go to close proximity of BT reader.Open the 2N Mobile Key app and select the door you wish to access. Tap the button in the app to open the door.      Android  iOS     If you are authorized, the door will open, and a green circle will appear.       Android  iOS             Touch On Device mode  In the app settings enable Unlock door on the background (Android) or Background scanning (iOS).       Android  iOS      Go in front of the device and tap the reader part or Bluetooth symbol (according to used 2N device) to open the door.      Card mode  In the app settings go to Modes (Android) or Advanced (iOS) and enable Card mode, you can also adjust its sensitivity.       Android  iOS           Android  iOS           Android  iOS     Swipe the smartphone across the Bluetooth symbol as you would have a card.Please be advised that sensitivity will be increased within confined metallic spaces such as small elevators.                                                Motion Detection mode   Please be advised that this mode requires GOLD licence because of using motion detection.        Go to 2N device web interface, section Hardware - Extenders, here locate the Bluetooth module.Check that Via Motion Detection is activated as Start Authentication. It is also possible to specify the distance (Signal Strength) within which your smartphone will communicate with the Bluetooth module, the optimal is Long.                                       Go to section Hardware - Camera - Internal Camera and enable the Motion Detection feature. You can also select how sensitive you wish to set the motion detection to be by adjusting the Sensitivity Threshold and Detection Area.                                       In the app settings enable Unlock door on the background (Android) or Background scanning (iOS).       Android  iOS             Walk towards the 2N device to activate the motion detection. If you are authorized, the door will open.

Question 51

QR code creating and sending over e-mail

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer.You can also use generated QR codes as an access credential of users and visitors and send it over e-mail.   Prerequisites 2N Access Commander the latest version;no additional license is required. 2N device with AXIS ARTPEC-7 chip and the latest firmware( Access Unit QR , IP One , IP Style , IP Verso 2.0 );no additional license is required.      Creating a QR code for a user  In 2N Access Commander web interface, go to section Users,open an existing user or create a new one.     Add credential here.        The QR code can be directly printed or sent over e-mail (requires SMTP server configured in 2N Access Commander).Video - 2N Access Commander - How to set SMTP and notifications          Creating a QR code for a visitor  In 2N Access Commander web interface, go to section Visitors,open an existing visitor or create a new one.     Add credential here.     The QR code can be directly printed or sent over e-mail (requires SMTP server configured in 2N Access Commander).Video - 2N Access Commander - How to set SMTP and notifications      You can also create a user with privilege to manage visitors and activate him simplified user interface for his mobile phonewith possibility to share the QR code in another application.More information here: Simplified User Interface for Visitors management         If you have older version of the system with different look of the web interface, please click here.   Creating a QR code for a user  In 2N Access Commander web interface, go to section Users,open an existing user or create a new one.   Go to Accesses tab and generate the QR code.  The QR code can be directly printed or sent over e-mail (requires SMTP server configured in 2N Access Commander and e-mail address at the user).Video - 2N Access Commander - How to set SMTP and notifications        Creating a QR code for a visitor  In 2N Access Commander web interface, go to section Visitors,open an existing visitor or create a new one.     Add QR code here.     The QR code can be directly printed or sent over e-mail (requires SMTP server configured in 2N Access Commander and e-mail address at the user).Video - 2N Access Commander - How to set SMTP and notifications                   Supported 2N device configuration QR code reading must be enabled in the devices.Please enable it in the 2N device web interface, section Services - Access Control - Entry / Exit Rules.    If 2N Access Commander´s access rules are set properly, you will find QR codes in your device, in section Directory - Users, as 10 to 15-digit PIN.The QR code can be optically different then QR code in 2N Access Commander, but if the 10 to 15-digit PINs are the same, then it will work.

Question 52

Reports - what data are exported

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time.Within Reports feature you can export summary data on added users based on 4 pre-configured filters to CSV file.Be careful, some of them contain sensitive information.   Prerequisites 2N Access Commander the latest versionrequired license tier:  Advanced / Pro / Unlimitedrequired user role:  Admin  (or User manager just for Mobile Key report)    Download Reports Go to 2N Access Commander web interface, section Reports and click the download button on the right side to export in CSV file.       Pre-configured filters Pictures from the exports are only examples from our demo system https://acdemo.2n.com/. Do not belong to any existing system.    Mobile Key - paired and unpaired users with pairing time remaining In the CSV file, you will find a list of users along with the Bluetooth pairing status. The status could be either "Paired" or "Pairing", and the pairing time is also provided.       Users – access rules with groups, zones, devices and time profiles In the CSV file, you will find a list of all users along with details about the groups they belong to, the devices they have access to in specific zones, and any time restrictions that have been implemented.        Users – detailed export (SENSITIVE INFORMATION) In the CSV file, you will find all user details (incl. e-mail, role, access methods), sorted by the company.       Users – global synchronisation export (users with User Number assigned) (SENSITIVE INFORMATION) In the CSV file, you will find only users with assigned User Number together with their details.  After editing, you can import it back.More information here: 2N Access Commander - CSV Synchronisation to import / remove users with their details

Question 53

SMTP and notifications - How to set in 2N Access Commander

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer. The E-mail function helps you send notifications or access passwords to users. E-mails are sent using the SMTP.  Prerequisites 2N Access Commander the latest version   Advanced license or higher for 2N Access Commander   Your or some 3rd party SMTP server

Question 54

SMTP Gmail service configuration in 2N Access Commander

Accepted Answer

For the needs of e-mail communication (forgotten user passwords, notifications, or distribution of Bluetooth access data), it is possible to use the SMTP public service of Google.Gmail in the role of SMTP server in 2N Access Commander offers greater security options for e-mail communication than standard freely available SMTP services.     Requirements & Ports  Application version: 1.17 and newer The 2N Access Commander supports these ports: 25587   Google account settings Due to the enhanced security of Google services, you are not able to use the Gmail SMTP server right away. You have to set up the 2-Step Verification firstly.  Create an App password (with 2-Step Verification) This is the only way to connect your Gmail account with the 2N Access Commander.With this option, you will get a one-time password that you will use to log in to the SMTP settings in the 2N Access Commander.   After you activated the 2-Step Verification for the Google account, please visit this site: https://myaccount.google.com/apppasswordsIn the next step, you will have to create a new app specific password, and name it for better identification.Then it will generate a unique password that you'll use later in the 2N Access Commander configuration.   The password cannot be displayed anymore after you press the DONE button!  2N Access Commander configuration After you have successfully set up your Google account, you now need to set up the 2N Access Commander as well.   In the web interface of the 2N Access Commander go to Settings > (Configuration) EMAIL > enable the SMTP service and click on some of the SMTP SETTINGS: Enter the Server Address and Port - in this case, the SMTP server is smtp.gmail.com and port 587 (TLS encryption) or 25 (unsecured).The User name is your full e-mail address including the domain, then enter the Google App Password - it will be stored only in the 2N Access Commander.The Default sender address will be the same as the user name which was filled above.Enable the TSL, validation of the server certificate, and Legacy mode and hit the CHANGE button to save it.   You can also test, whether you've set everything correctly. Enter a valid Test E-mail Address (an address to which your test email will be sent) and click on SEND TEST E-MAIL. You should be able to receive an e-mail with a testing message.  If you get a message Test email FAILURE, please double check that you set everything correctly according to this manual, otherwise please contact our support: https://support.2n.com    If you are having issues with sending an e-mail, try to enable or disable (default) the Legacy mode.

Question 55

SSH - How to connect over SSH to 2N Access Commander

Accepted Answer

SSH is used for secured remote access to computer systems. That's why we introduced a new layer of security by disabling SSH access by default and enforcing the use of a stronger password when SSH is enabled. Therefore, if you need SSH access to 2N Access Commander you need to enable SSH first. It is possible to enable the SSH from the web interface, but it can be set in the Linux of the virtual machine or BOX or BOX 2.0 as well.   This feature needs to be enabled to successfully import data between different installations of 2N Access Commander on installation from which data are imported.    Web interface set up  After you log in to the web interface of the 2N Access Commander you can find the SSH setting in the bottom section of the Settings - Configuration (1) tab. The SSH is disabled by default so you need to enable it by clicking on the "Disabled" button (2).    The SSH connection is secured with the root password to the Linux Console. After clicking first time on the "Disabled" button you will be asked to change the password for root user, if that password is not secure one.  After setting a new password the SSH connecting will be enabled. You can change the root password for Linux Console and SSH connection by clicking on the "Change password" button.   When clicking on the "Change password" button the "Set root user password" window will pop up and you will be asked to enter the current password, create a new one and repeat it for confirmation.  Now you will be able to connect to the 2N Access Commander box or virtual machine by entering the IP address of the 2N Access Commander to some SSH client with the set password. Here is an example with the MobaXterm SSH client. Linux Console set up In case of virtual machine you can do that by accessing the virtual machine terminal from virtualization. In case of BOX or BOX 2.0 you can do that by connecting display and keyboard to the computer. In both cases you need to login to the Linux as root user.  After logging in, please Select Advanced Menu in GNU/Linux Configuration Console    Continue to SSH - Allow SSH connection:  Go to ( ) Enabled, hit Space to set it to  ( * ) Enabled it and then press Enter to  the change:  The SSH connection is secured with the root password to the Linux Console. After enabling it for first time you will be asked to change the password for root user, if that password is not secure one.  SSH is now enabled and you can now access the Linux of 2N Access Commander remotely.

Question 56

SSL / TLS - CA certificate - How to add certificate authority to Linux of 2N Access Commander

Accepted Answer

In case you need to allow 2N Access Commander machine to communicate with your IT infrastructure such as proxy server etc.. while having in your company CA which 2N Access Commander machine does not know, you can teach the 2N Access Commander machine to recognize your CA and allow secured communication between your IT infrastructure and 2N Access Commander machine.  prepare your CA certificate which is used to sign certificates used in your IT infrastructure in .crt format (use .key or other format for password protected CA certificate)  connect to Access Commander's linux and login as root user  Navigate to folder /usr/local/share/ca-certificates/ using following command:cd /usr/local/share/ca-certificates/  create new folder named by your CA certificate name (it is recommended to use own folder for each CA certificate you wish to add)mkdir myCAcertdir   Where myCAcertname shall be name of your CA certificate.    copy the CA certificate files to newly created folder  set proper privilege levels for folder and filesFor folder:chmod 755 /usr/local/share/ca-certificates/myCAcertdirFor files:chmod 644 //usr/local/share/ca-certificates/myCAcertdir/myCAcert.crtchmod 644 //usr/local/share/ca-certificates/myCAcertdir/myCAcert.key  run command to load newly added certificates to linux using following command:update-ca-certificates   You shall see that 1 or more certificates has been added. If you see that no certificates has been added, please check if you have supported file suffixes (.crt,.key,etc...)       You can see if the CA certificate has been properly added by running following commads:   awk -v cmd='openssl x509 -noout -subject' '     /BEGIN/{close(cmd)};{print | cmd}' < /etc/ssl/certs/ca-certificates.crt      In order to make Access Commander accept the recent changes, please reboot whole Access Commander:reboot

Question 57

SSL / TLS - User certificate - How to add CA signed user certificate to 2N Access Commander web

Accepted Answer

You can install CA signed SSL certificate to 2N Access Commander web page, so anyone accessing its website will not receive security warning in web browser. Access Commander needs to be accessible via name address instead of and IP address. To do so, certain aspects needs to be met.  You need domain name for web page of Access Commander so instead of accessing it via IP address you can use name address  You need to generate certificate for domain name of Access Commander and you need some Certification Authority to sign it, making it trusted.    How to install certificates Once you receive signed certificate from CA, you need to do following steps  copy certificates for your domain to linux of Access Commander virtual machine, for example to folder /etc/apache2/ssl/You should have following 2 files: private.key and signedoriginal.crt  modify file /etc/apache2/ssl/certificate.conf to match new certificates  change following link of certificate files to location of your files, for example: SSLCertificateKeyFile /etc/apache2/ssl/private.key SSLCACertificateFile /etc/apache2/ssl/signedoriginal.crt    Please, note that the key or certification file can have different formats (.pem,...) that can also be used.    Once you save your changes, please run following command to restart apache2 server: systemctl restart apache2  So when you now access the web interface of your Access Commander, you will get information that communication is secured.

Question 58

Static IP address - How to set up static IP address in 2N Access Commander

Accepted Answer

2N Access Commander is set in default to obtain an IP address from DHCP server. If you don´t have DHCP server in your network or if you require to set static IP address for your 2N Access Commander installation, then you need to do following: Login to web of 2N Access Commander or connect to the Linux terminal of 2N Access Commander.   Web of Access Commander settings You can access the option to set the static IP address  in Network settings.  The option is available once you login in to Access Commander web as an admin or user with admin privileges.  Please navigate to Settings - Configuration (1) and on Network settings, please choose to Set manual configuration (2).   Set requested IP address and relevant parameters according to your network and Set configuration settings    Linux of 2N Access Commander settings In case of virtual machine you can do that by accessing the virtual machine terminal from virtualization or by using SSH connection. In case of BOX or BOX 2.0 you can do that by connecting display and keyboard to the computer or by using SSH connection. In both cases you need to login to the Linux as root user.  After logging in, please Select Advanced Menu in GNU/Linux Configuration Console  Choose Networking  Select Static IP  Set requested IP address and relevant parameters according to your network and Apply settings

Question 59

Time profiles - managing time restricted access  for 2N Fortis

Accepted Answer

Time profiles are supported for 2N Fortis in 2N Access Commander version 3.4 or newer. However some limitations apply. Time profiles in 2N Access Commander are an optional feature used to limit access for users to specific days and time periods.They can be assigned to access rules, which define the relationship between a group of users and a Zone (where devices are assigned).When 2N Fortis  devices are part of that Zone, time profiles can also control when those devices are accessible.   Limitations of time profiles for 2N Frotis:  Time profiles are supported only in access rules, not directly on devices or users. Time profiles are saved on each programmed  user card for 2N FortisEach 2N Fortis programmed user card can hold a maximum of 4 time intervals per day.If multiple 2N Fortis  devices are involved, each can have its own set of up to 4 intervals per day. Example of data stored in card:     DeviceDayAllowed Time IntervalsLock 1MondayINT1, INT2, INT3, INT4Lock 1MondayINT3, INT5Handle 6MondayINT1, INT6, INT4, INT8Handle 2TuesdayINT5, INT6, INT7, INT8     Merging of Time Profiles: If a user in 2N Access Commander is a member of multiple groups that use different time profiles for access to the same 2N Fortis device,Access Commander will merge the intervals and attempt to create a combined time profile (not visible to user).However, even after merging, the resulting time profile cannot exceed 4 intervals per day per 2N Fortis device the card has access to.   Additional Notes:  Access Commander will indicate whether a time profile is valid or invalid for 2N Fortis.              Holiday settings are not supported for 2N Fortis compatible time profiles in 2N Access Commander.

Question 60

Time settings - How to configure in 2N Access Commander

Accepted Answer

Since 2N Access Commander version 2.2 you are able to configuration SSH, time and IP address directly from the web interface, next to the Linux console. Configuration setup via the web interface    Configuration setup via the linux interface  How to setup time automatically using NTP server  How to setup time manually    Configuration setup via the web interface   In section Settings → Configuration you can see the Server date and time section where you can configure the details (NTP/Manual tiem setting, device time synchronisation, Timezone, ...):        Configuration setup via the linux interface: You can access 2N® Access commander's operating system (Linux) via console or SSH. While logged in you will see blue Access Commander configuration console, which offers access to various settings including, but not limited to time settings.  Choose Advanced Menu in the Access Commander console:   Then select Time:   Select Time zone and use a button Select:   Select a desired time zone. First, choose the correct area:    Then select the city:      How to setup time automatically using NTP server:  Select NTP and press the button Select:    Specify the address of the NTP server you would like to download the time from: A few examples:ntp1.sh.cvut.cz or use an IP address: 147.32.127.250chronos.csr.net or use an IP address: 194.35.252.7time-a-g.nist.gov or use an IP address: 129.6.15.28      How to setup time manually  Select Manual and press the button Select:    Setup the correct time and choose Apply:

Question 61

Troubleshooting of issue with 2N Access Commander

Accepted Answer

The nerve center of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Have you found an issue with our 2N Access Commander? We will show you how to contact the 2N Technical support team and what information should be prepared before contacting.   Prerequisities 2N Access Commander, the latest version of the software if possible;no additional license is required for collecting diagnostics logs.   We are happy to help In case of any issue, feel free to contact the 2N technical support team. Here are mentioned all the ways how you can proceed it: https://www.2n.com/support/technical-supportWe will be glad, if you can tell us following information to help us with resolving your issue and providing our feedback much faster.  Detailed description of the issuePlease describe to us your issue in detail, so that we will be able to replicate the behavior based on that description.    Diagnostics logsPlease download diagnostics logs by following this steps: More information: Diagnostics logs   The software version you use If you do not use the latest version available, we strongly recommend to perform update of the system.More information: Update of 2N Access Commander  Information about current license tierMore information: Licensing in 2N Access Commander Do you use virtual machine or 2N Access Commander Box solution?In case of the virtual machine, which supported virtualization platform do you use? (VMware / Hyper-V / VirtualBox)   Network topologyPlease attach network topology diagram of connection between 2N Access Commander and devices (intercoms, access units, ...) including IP adressing and information about used VPNs, VLANs, etc...   Complete backup of your installation (optional)For more complex issues, please send us the current configuration backup of the system.More information: Backup and setting restore Factory reset of BOX, BOX 2.0 (optional)In case you have a backup of your configuration, you can try to reset your 2N Access Commander BOX or 2N Access Commander BOX 2.0 to factory default values. This cannot be done for virtual machine.Factory reset will erase all data in device. More information: Factory reset of the 2N Access Commander Box

Question 62

Two-factor (2FA) authentication in 2N Access Commander

Accepted Answer

Two-factor authentication provides a higher level of security for the Access Commander user account. To log in, the user enters the login data and has to confirm the login using an authentication application. Once the administrator turns on two-factor authentication, the user will be prompted to interconnect the user account with an authentication application of their own in the next login.  The administrator sets two-factor authentication in Settings > Configuration > Two-factor authentication.The administrator can choose which users will be requested to use two-factor authentication. Even unset by administrator, each user can use two-factor authentication optionally. Any user logged in to Access Commander can setup the authenticator app in their profile (user icon positioned top right on the Access Commander page)   Setting up 2FA authenticationOptional authentication scopeMandatory for users with a role authentication scope Mandatory authentication scopeSupported authenticator apps Setting up 2FA authentication As an administrator, navigate to Settings > Configuration > Two-factor authentication   Optional authentication scope Two-factor authentication is voluntary. Users can enable two-factor authentication in their profiles, see Two-Factor Authentication Enable.    Scan offered QR code with authenticator app in your mobile phone and confirm adding it to Access Commander with code you receive in your authenticator app.  Mandatory for users with a role authentication scope Every user that has been assigned a role has to verify the login using an authentication application. After user with assigned role login in to Access Commander, the prompt for adding authenticator app will appear and have to be set. Users with no role in Access Commander can add the authenticator app optionally after login in their profile.  Mandatory authentication scope All users must verify their logins using an authentication application. After any user login in to Access Commander, the prompt for adding authentication will appear and have to be set..  Supported authenticator apps Most modern authenticator apps are supported such as Google authenticator app, Microsoft authenticator app, iOS built-in privacy and security and many others.

Question 63

Update of the system

Accepted Answer

The nerve centre of our access control solution is 2N Access Commander. Use it for managing access to the building and monitoring the status of 2N access devices in real time. Its intuitive user interface lets you set up the system quickly and delegate everyday activities directly to the customer.cWe recommend to keep the system up-to-date.   Prerequisities 2N Access Commander, no additional license is required.Internet connectivity for 2N Access Commander is necessary, the update is only possible on-line.Be sure, the network configuration is set properly, you can eventually follow this article:2N Access Commander - Static IP address setupBefore updating please always make a system backup according to this instructions:2N Access Commander - Backup and restore of the system   Feature properties The update must be proceeded incrementally to the next sequential version. It is not possible to jump to the latest version directly.It is not possible to downgrade the Access Commander from the current version to older.   Update of 2N Access Commander version 3.0 and higher Go to 2N Access Commander web interface, section Settings, part System update. You will see a notification about available update, please follow this procedure:      During preparation of necessary components to update the system you will loose the access to the system, please be patient and wait few minutes till the update process starts. When all necessary components are ready to update the system, you will see an update console window showing process status.      Do not turn off or reboot the appliance during the update process. It is necessary to wait for the blue "Go to login" button showed when the update is complete.       Now you can login back and repeat the procedure up to the latest available version.       If you have older version of the system with different look of the web interface, please click here. Update of 2N Access Commander version 2.7 and lower Go to 2N Access Commander web interface, section Settings, part SYSTEM UPDATE. You will see a notification about available upgrade, please follow this procedure:          During preparation of necessary components to upgrade the system you will loose the access to the system, please be patient and wait few minutes till the upgrade process starts. When all necessary components are ready to upgrade the system, you will see an upgrade console window showing process status.      Do not turn off or reboot the appliance during the upgrade process.In some versions, the upgrade is still being performed even the message "The upgrade has finished." appears. After this message, watch the "GO TO LOGIN" button. It is gray during performing upgrade and green, when the upgrade is complete.      Now you can login back and repeat the procedure up to the latest available version.

Question 64

Vega LPR integration with 2N IP Intercoms and Access Units

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. 2N devices can now use recognized license plates as another credential for entry or exit. This function can be enabled on any device that supports “Door” functionality. License plates may be assigned to a user and their validity is controlled by the same access rules as their other credentials.   License plate recognition (LPR) works outside of Access Profiles set in Hardware>Door>Entry or Exit Rules, and as such can’t be combined with other credentials for combined authentication.     Prerequisites Vega camera configuration 2N device configuration 2N Access Commander configuration (optional) Access logs entries   Prerequisites  Suitable Vega - Automatic Number Plate reader with following firmware or newer  Firmware version = VEGA BASIC 12.68.1 ITA-EU Sep 14 2021 15:16:04 Plate Reader lib = Tattile Plate Reader Ver.3.170.000 Traffic Interface lib = 1.135 TOS version = 4.38.1 Boot version = 2.40   2N device with FW 2.33+  2N IP/LTE Intercoms (apart from 2N® IP Uni)  2N Access Units      Vega camera configuration  Enable Template Message Action for OCR Read Event   Configure Template with following parameters: Enable: Yes Server IP: 2NdeviceIP Server Port: 2NdevicePort (default 80) Protocol: HTTP_post Content Type: application/json Url: api/lpr/licenseplate Authentication: AUTH_DIGEST Username: Yourusername Password: Yourpassword Jpeg Quality: 50 Crop Image: 640x480 Context Jpeg Quality: 50    Upload template of JSON body  use following format:   { "lprUuid": "${YEAR}-${MONTH}-${DAY}-${HOUR}-${MIN}-${SEC}", "accessPoint": 0, "plateText": "${PLATE_STRING}", "plateImage": "${IMAGE_OCR}" }       2N device configuration  Set Camera HTTP API to Unsecured (TCP) Digest   Set Account 1 to match credentials used in Vega camera and enable Access Control privilege   Enable License Plate Recognition on 2N device   Add user and enter LP of car as an access credential in to Car Fleet management     2N Access Commander configuration (optional)  Version 3.0+ When a 2N device is connected to 2N Access Commander, then most of its settings are managed by it. Thus, LPR settings will be managed by 2N Access Commander, but still you have to configure the device’s HTTP API credentials as those are device dependent.  Configure your 2N Access Commander as you normally would. Then open details of the device you already prepared for LPR  and make sure it has Lift Control turned off and that it’s assigned to the proper zone.    Then go to this Zone’s detail and enable License Plate Authentication.    Users can have their license plates assigned under Overview → Credentials section, click Add Credential, enter one or more license plates, and confirm by clicking create.             Verify that this user is assigned to the correct group   and create an Access Rule for it.    Optionally  , if you’d like to get photos of recognized license plates, you can create  + CAM LOGS  . Name the log accordinglyand after creaion select the  Car license plate recognised.         Then  ADD  all  devices  you want to receive photos from to this CAM Log.    Once everything is configured, Access Logs will show up once a license plate is recognized.      Access logs entries In 2N IP device you can see that user has been authenticated by LPR:     Similarly you can see Access Log entry in Access Commander if used:

ファクスの一覧