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 IP intercom into My2N - I don't have a card with the Security Code

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.   Dear customers, The My2N Management Platform is a powerful cloud-based platform that makes managing and configuring the devices in your project’s solution more efficient. My2N cloud includes video calling from an IP intercom to a smartphone or a tablet.     Prerequisites   2N IP intercom firmware version 2.36 or newerInternet connectivity, make sure that the DNS parameter is configured correctly If the static IP address is usedno additional license is required      My2N platform account For detailed information about how to access My2N and sign up, please read the following article: My2N cloud - registration and setup    Locate Serial Number and Security Code You can find them on the product ownership card that came with the box of your intercom.If you don´t have this card, continue to next step.   Login to the device´s web management and go to the section System - Auto Provisioning - My2N (Old Web Interface)         Login to the device´s web management and go to the section Integration - Auto Provisioning - My2N (New Web Interface)    Add 2N IP intercom into your My2N site After login to your My2N site continue to section Devices and then click the ADD DEVICE button. Choose the 2N Device option.   In a newly opened window, please fill in details about your 2N IP intercom.Fill in this device's serial number from its ownership card or its web management.Fill in this device's Security code from the same place.Alternatively you can click on SCAN QR CODE and point the camera of your laptop or phone at the ownership card to easy fill in this two details.Please note that one device (one serial number) can only be assigned to one My2N account at once.If you have already registered that intercom to a different My2N account, you need to remove it first.Tick on Remember security code to allow automatic connectivity back in case of accidental disconectivity.Fill in the intercom's name (defined by your requirements in order to easily identify this device).Continue to next step.     We recommend to keep the Automatic configuration mode (set by default) to allow My2N automatically configure the devices. Logging of access is optional feature to see device´s access logs in My2N portal. Now you can finish the process.     You have successfully added 2N IP intercom to your My2N site. Device status is Missing call settings, which means the call feature has not been set yet as described below.            What to do next for call feature Add the mobile device you wish to call from your intercom to your My2N account.You can follow this article: My2N - How to add smartphone or tablet     In order to make calls from the intercom to mobile devices over My2N, buttons on the intercom need to be configured to call the correct mobile devices.You can follow this article: My2N - Call setting

Question 5

2N IP intercom into My2N using the Security Code

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. Dear customers,  The My2N Management Platform is a powerful cloud-based platform that makes managing and configuring the devices in your project’s solution more efficient. My2N cloud includes video calling from an IP intercom to a smartphone or a tablet.     Prerequisites   2N IP intercom firmware version 2.36 or newerInternet connectivity, make sure that the DNS parameter is configured correctly If the static IP address is usedno additional license is required      My2N platform account For detailed information about how to access My2N and sign up, please read the following article: My2N cloud - registration and setup    Locate Serial Number and Security Code You can find them on the product ownership card that came with the box of your intercom.   Or login to the device´s web management and go to the section System - Auto Provisioning - My2N. (in the Old Web Interface)   Login to the device´s web management and go to the section Integration - Auto Provisioning - My2N (in the New Web Interface)     Add 2N IP intercom into your My2N site After login to your My2N site continue to section Devices and then click the ADD DEVICE button. Choose the 2N Device option.   In a newly opened window, please fill in details about your 2N IP intercom.Fill in this device's serial number from its ownership card or its web management.Fill in this device's Security code from the same place.Alternatively you can click on SCAN QR CODE and point the camera of your laptop or phone at the ownership card to easy fill in this two details.Please note that one device (one serial number) can only be assigned to one My2N account at once.If you have already registered that intercom to a different My2N account, you need to remove it first.Tick on Remember security code to allow automatic connectivity back in case of accidental disconectivity.Fill in the intercom's name (defined by your requirements in order to easily identify this device).Continue to next step.     We recommend to keep the Automatic configuration mode (set by default) to allow My2N automatically configure the devices. Logging of access is optional feature to see device´s access logs in My2N portal. Now you can finish the process.     You have successfully added 2N IP intercom to your My2N site. Device status is Missing call settings, which means the call feature has not been set yet as described below.            What to do next for call feature Add the mobile device you wish to call from your intercom to your My2N account.You can follow this article: My2N - How to add smartphone or tablet     In order to make calls from the intercom to mobile devices over My2N, buttons on the intercom need to be configured to call the correct mobile devices.You can follow this article: My2N - Call setting

Question 6

2N LTE Verso - Registration to My2N and basic setup

Accepted Answer

This guide describes how to connect 2N LTE Verso to LTE network and two following My2N services – 2N Mobile Video and 2N Remote Configuration.   Before starting please create your own My2N account according to this guide.      Insert a SIM card to 2N LTE Verso  Registering to LTE network  Registering the 2N LTE Verso to My2N cloud – 2N Mobile Video service  Entering the 2N LTE Verso's 2N Remote Configuration service   Insert a SIM card to 2N LTE Verso Before inserting a SIM card, it is necessary to disable the PIN code.You can do so by inserting the SIM to a standard cell phone. Most phones have the option to disable the the PIN in their settings.Here is an example from a Samsung phone. If you are not sure how to do it, please consult manual of your cell phone.      Registering to LTE network After inserting the SIM card to the 2N LTE Verso, you can observe behavior of  the red LED   placed under the Main Quick Dial Button to verify the status of the device.  Meanings of different signals are described in following table:   LED behavior  Meaning  Note  Diode is flashing after boot up  2N LTE Verso is connecting to the network  This is normal behavior.  Diode is off  2N LTE Verso is connected to the data network     Diode is illuminated for 5 seconds  SIM card error (SIM not inserted, PIN request enable or no active data service)  When this 5s timeout is over, another connection attempt is made and the LED starts flashing again.  Diode is flashing only  The LTE signal is insufficient  Check the area LTE signal coverage and antenna connection. Alternatively, use an appropriately placed external antenna. Caution – do not stick the external antenna to a metal surface!     SMS command 2N LTE Verso includes a set of SMS commands that help you identify the device state and configure the basic mobile data connection parameters. Send SMS in format state pwd= and intercom will return information about network and signal.       Registering the 2N LTE Verso to My2N cloud – 2N Mobile Video service Enter your My2N account, go to the Site you want to register the 2N LTE Verso, and follow these steps:  You can add the 2N IP intercom by clicking on the Devices button and then the ADD DEVICE button.   Select 2N Device.   In a new opened window, please fill in details about your 2N IP intercom.  Fill in the intercom's name (defined by your requirements in order to easily identify this device).  Fill in this device's serial number from the paper card that belongs to the device.  Fill in the security code from the same paper card.   You can find the Serial Number and My2N Security Code enclosed it the package.   The intercom will be seen as registered with missing call settings in a couple of minutes.    Meanwhile you can go ahead and add a device (or several) to be called when the button is pressed. Just click on the LTE Verso, device detail will open and then click on Call settings.    Now, you can make a call towards the device by pressing the button. With this, you have finished the basic set up.     Entering the 2N LTE Verso's 2N Remote Configuration service    2N’s free Remote Configuration enables you to fully configure 2N IP and LTE intercoms and Access Units using the   My2N   portal.   Accessing the intercom’s configuration interface only requires an Internet connection.       To enter the Remote configuration of your LTE Verso, go to the device detail and then click 2N Remote Configuration Services:  Then click Open Configuration:   Now your browser opens a new tab with LTE Verso's web interface. You can now log in and fully configure your intercom.      Keep in mind that users created in My2N and Button settings are synchronized with the My2N cloud and changes of these has to be made inside of the My2N account.

Question 7

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 8

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 9

Answering Unit Registration and Configuration of Calls in My2N

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. There are two modes of the SIP registration of the 2N Indoor Compact unit in this example, to the My2N portal:    Local  - allows you to use the 2N Indoor Compact in your local network. The reason why you can choose this mode is to make the configuration of the intercom easier so it is not necessary for you to disable the automatic configuration and you can just simply add the 2N Indoor Compact in your local mode and the intercom will be configured automatically. In this mode, the 2N Indoor Compact has to be placed in the same LAN as the intercom.   Cloud  - this mode allows you to make the calls from the 2N Indoor Compact to the 2N Mobile Video application and vice versa. You can use this mode in situations where the unit is placed in a different LAN than the intercom.  2N Indoor Compact My2N Registration:  Security code  Local mode  Automatic configuration  Call settings  Unlock Settings   Cloud mode  DTMF Sending Receiving modes  Unlocking     Security code     Security code is included in the package with the device on the card.    Another way how you can obtain the security code is to go to the device setting section "System" (1) - "Auto Provisioning" (2) - "My2N Security Code" (3) You can quickly copy each credential by clicking on the copy buttons (4) on the right side Note that security code is shown in the firmware version 2.26 and higher In Old Web Interface:  In New Web Interface:  You will have to navigate through "Integration" (1) - "Auto Provisioning" (2) - "My2N" (3) - "General Information" (4) You can also generate a new security code (5)  If you do so, remember to verify the device's security code again in My2N   Local mode  You can add the 2N Indoor Compact by clicking on the "Devices" (1) button and then the "ADD DEVICE" (2) button. Then choose "2N Device" (3) option:     Fill out the "Device serial number" (4), then fill out the "Device Security code" (5)  It is recommended to check the "Remember security code" (6)  Optionally, you can also fill out a custom "Device Name" (7) and select or create new "Apartment" (8) if desired    In the next step you will be asked for selecting the "Configuration mode" (9) and "Connection mode" (10) For Automatic mode select "Automatic", for Local mode select "Local":    Click on "CLOSE" (11) to finish the configuration           Cloud mode  You have two options how to set up your 2N Indoor Compact:  You can use automatic or manual configuration mode   Mode selection is available while adding device (see above) or you can change the mode in device details  You can open device details by clicking on the "Devices" (1) and three dots (2) as shown below:   Automatic configuration First option is an Automatic Configuration mode (3):  This mode is used for comfortable configuration of your answering unit via My2N service    Call settings   You are able to configure switch codes and dial button of the 2N Indoor Compact  Select "Call Settings" (1), fill out the name under "Contact name" (2)  The select the call destination (3), which will be assigned to calling button, from the list of the devices connected in your MY2N account  Save the configuration (4)   Even in Automatic Configuration Mode you can add manually an user from the device's Web Interface:  You can specify the number to which the call should be established and SIP account which will be responsible for the forwarding of the call  The number of the device (Device ID) is shown in My2N portal Settings section  In this example the number is 4962898773 which is the ID of the registered Intercom in the site  You can specify this number in the Directory menu section of the 2N Indoor Compact  SIP account is defined by /2 parameter in the Phone number field  It is necessary to use SIP account number 2 for the proper function  In Old Web Interface:   In New Web Interface:    Unlock Settings  You can also change the unlock code sequence under "Unlock settings" (1)  The code can be changed under "Default unlock code" (2), by default the code is 00*  Save the configuration (3)       Answering modes Last step is to check the answering mode  Go under "Calling", "General Settings", "Incoming Calls"   Check if the "Call Answering Mode (SIP2)" or Local Answering Mode has been set to "Manual Pickup", accordingly with the choice you have made for calling   Make sure to save the configuration       Old Web Interface:  In New Interface:  DTMF Sending Receiving modes If you wish to activate switches over the call, make sure the DTMF  modes are set up correctly:  Go under the "Calling" (1)  Select the SIP account 2, or the Local Calls, accordingly with you initial choice, in this example "SIP 2" (2)  Then click on the "Audio" (3) tab  Locate the DTMF Section, check if the "DTMF Sending/Receiving" (4) is set up correctly (in Old and then in New Web Interface)    Unlocking You can also configure the "Default Unlock Code", which is by default configured in the Hardware - Switches section of the Intercom  Click on "Services" (1)  Select "Unlocking" (2)  Enter the default code under "Default Unlock Code" (3), for example "00"

Question 10

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 11

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 12

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 13

Automation, Callback - How to configure callback with 2N IP Intercom to My2N

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 feature enables you to use a callback, for example, to help with a demonstration at an exhibition or for testing if the 2N IP Intercom is functioning correctly with My2N and is able to make calls. You have 2 options for how to set the Callback function; you can allow all users or just selected users to use this feature. Thanks to this feature the 2N IP Intercom is able to call you back after activating the Callback feature.    Allow callback for every users in My2N  How to set callback in a My2N account Please add your smartphone or tablet and your 2N IP Intercom to your My2N account.    Now go to the "Device detail" page of a device and use one of the switches here to define a code (does not have to be the same as displayed here) that will enable the Callback function. You can also set a name for the switch, which will show up in the app itself.      How to set up callback on 2N IP Intercom Go to the section "Services -> Automation" and use one of the functions there. Then follow the example in the screen below and create the function. Enter the DTMF code you defined for the switch in MY2N (previous step) and set the delay to your preference, the delay determines when the 2N IP Intercom calls you back. GOLD license required.     Allow feature for selected users If you want to allow this feature only for selected users, you need to make a slight change in your Automation (add the Flip-Flop RS). Now enter multiple comma-separated user's numbers for each user who will have access to this feature.    Firmware & License info  2N OS v2.44 with GOLD license  Last updated on 25th of August 2024

Question 14

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 15

Axis network intercom into My2N

Accepted Answer

The My2N Management Platform is a powerful cloud-based platform that makes managing and configuring the devices in your project’s solution more efficient. My2N cloud includes video calling from an IP (network) intercom to a smartphone or a tablet.     Prerequisites   Axis network intercom Tested with Axis A8207-VE with firmware 11.10.83.Internet connectivity, make sure that the DNS parameter is configured correctly If the static IP address is used.      My2N platform account For detailed information about how to access My2N and sign up, please read the following article: My2N cloud - registration and setup                 In My2N account, add Axis intercom    Login to your My2N account, go to section Devices and add a new device. Choose the AXIS Intercom option.    Fill in its MAC address and device name.     Your Axis intercom has been successfully added to My2N.    In My2N account, find SIP Proxy details for Axis intercom The new device has status "Waiting for response" at this moment.Click on the added device to find the SIP Proxy registration details.    Open section 2N Mobile Video.     Use this SIP Proxy details for configuration of Axis intercom SIP account.      In Axis intercom web interface, enable SIP and configure SIP account In section Communication - SIP, enable SIP and allow incoming SIP calls.It is also advised to change the end calls after value to prevent long connection to the device.    Go to Accounts and add a new account.   Be sure, the new account will be set as active and default.    Now fill in the SIP Proxy details from My2NName - name the accountUser ID - in My2N, this parameter is named Device IDDomain name - in My2N, this parameter is named SIP Proxy AddressPassword - in My2N, this parameter is named Device PasswordAuthentication ID - the same as User IDTransport mode - select TCP      Axis intercom has been successfully registered to My2N.        In My2N account, find the device to be called and copy its DeviceID.   In our example, we will call to a smartphone with My2N app. Open its details.If you have added your smartphone into My2N account not yet, please follow the article in prerequisites.        Open section 2N Mobile Video.       Use this Device ID for configuration of Axis intercom’s call button.            In Axis intercom web interface, setup the call button In section System - Events, go to Recipients and add a new recipient.    Fill in the name, change type to SIP, fill in prepared Device ID into "To SIP address" parameter and save.    Go to Rules and add a new rule.If you have already some rule for the call button, you can just edit it.       Name the new rule, in the Condition part select Digital input is active and port Call button, in the Action part select Make call and our created recipient.      Now you can press the Axis intercom’s call button to reach your smarthphone with My2N app.    In Axis intercom web interface, set DTMF sequence for opening the door In section Communication - SIP, go to DTMF and add a new sequence.     Fill in the numeric sequence, describtion, assign it to My2N account and save.      In section System - Events, go to Rules and add another rule.If you have already some rule for opening the door, you can just edit it.    Name the new rule, in the Condition part select DTMF and your created DTMF sequence as DTMF Event ID,in the Action part select Toggle I/O once and Door as a port. You can adjust here also the Duration, time after which the door is closed again.      In My2N account, assign the same DTMF sequence under a new switch button   Open section Devices and continue to Axis intercom details.   Go to SWITCH CODES and assign DTMF sequence from Axis intercom here as DTMF Code.Symbol "*" will be added automatically just as a confirmation character, you can keep it here.Name the function and save.     During the call tap on the lock icon. The door is open.

Question 16

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 17

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 18

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 19

Bluetooth Card Mode - how to setup My2n App and use the 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. 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, for example, if some users have some old mobiles (Android 8 or 9 , or iOS 15). However, Offline Pairing cannot be done using Access Commander .   For a brand new site in My2N - Start with online pairing first! Once you have your 2N devices in My2N and first cloud access is assigned, you can also create offline paired credentials on the device itself - you must create a separate user in the device directory for that. If you create offline paired credential first, after enabling the cloud access, already created offline credentials will stop working.   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.  Card Mode - Overview Card Mode uses Bluetooth wireless communication technology between two devices over a distance. It is based on communication between two paired devices for secure authentication.   Minimum required Android / iOS versionAndroid version My2n App version iOS version My2n App version10 and higher*3.0.0 and higheriOS 16 and higher*3.0.0 and higher   *  Using Android 8 or 9 , or iOS 15 will partially work, advanced features will not be available. Functions Bluetooth is used for exchanging information between two devices for a short distance. This identification is provided by a unique code of the end devices that contains this technolgy, like almost every smartphone these days. There is a communication between the smartphone and 2N IP Verso intercom (or 2N Access Unit) equipped with a Bluetooth module. This communication is secure and based on public and private keys that are exchanged (we use RSA-1028 asymmetric encryption and AES-128 symmetric encryption). Requirement 2N IP Verso with firmware version 2.33 or higher.Bluetooth module (order no. 9155046) connected to 2N IP Verso (or to 2N Access Unit) via internal Verso bus cable.My2n App app version 3.0.0 for iOS and Android.Bluetooth enabled on the phone.Location enabled on phone (for Android only). *Xiaomi Poco phones may not be compatible with WaveKey when app is on background  Step by step guide - How to setup Online Pairing between My2n App and 2N IP Intercom 1) On an existing my2n site, create an Access Group:    And then edit it with device, user and eventually apartment :  Add all devices, the users will have access to with the Access group:  Add all users, the Access group allows using the previously added devices:  You can, then, add apartment the same way. It will be mandatory in case of apartment model site:  2) After, you will need to enable My2n App access for the user:   The site or company admin, when he will enable it will see this warning explaining that in case, some users are offline paired with this device, they will have their Bluetooth Access revoked shortly:    3) Once this done, the user, if he has the My2n App installed on his mobile with the required Android or iOS version, will see appear on his App the below feature that he will have to activate:  Step by step guide - How to setup Offline Pairing between My2n App and 2N IP Intercom   1)  Please open web configuration of 2N IP Intercom and navigate: In the Old Web Interface to section Hardware -->  Extenders and locate Bluetooth module.Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module In Pressing the Bluetooth symbol, you will be able to open the door by tapping the Bluetooth icon on the Bluetooth module.    In the New Web Interface to section Access --> Modules --> Bluetooth  Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module  2) Install My2n APP app from the official OS store (Google Play, iTunes) to the mobile device of the user you wish to assign Bluetooth access to. 3) In the intercom's web configuration please navigate to section Directory --> Users (1) and create the user you wish to grant Bluetooth access for.Fill in a username and scroll down to the User WaveKey parameter(2). Click on the Bluetooth icon as shown on the picture below to pair via this device, to the Bluetooth module with the app on the mobile phone.   Once you do, a PIN code for pairing with the app in a phone will be generated as shown on the image below:  Default PIN validity is 1 hour. You need to pair a mobile phone before this time expires.Note: PIN validity can be changed in section "Services --> WaveKey --> Pairing Mode Settings"   4) Please go to close proximity (1-2 meters) of the 2N IP Intercom you just configured for pairing with the app.   5) When in close proximity to 2N IP Intercom equipped with a Bluetooth module, run the application and tap the + sign (1) and then The Pairing PIN option (2). Enter the pairing PIN provided by the intercom or from Access Commander (3) in the appropriate section (4), and start Pairing (5). Finally you will have the confirmation of the successful Pairing (6).      6) The app will start searching for devices in proximity. Please note that if the Bluetooth is in touch mode, you need to touch the Bluetooth reader first to trigger the pairing sequence.:  From now, If you are using Offline or Online Pairing, you see the device(s), if you are using Bluetooth, touching the Bluetooth sign on the intercom will trigger the door:  7) If you want now to use the Card mode, make sure to allow it on the 2n device: In Old Web Interface under the section Hardware -->  Extenders and locate Bluetooth module. Add the In App option :  In the New Web Interface under section Access --> Modules --> Bluetooth Add the In App option :    And allow it on the App itself under Settings(1) -->  Access cards(2):  and    From now, If you are using Offline or Online Pairing, you see the device(s), if you are using card mode, start walking towards the BT reader.To open the door with your smartphone, swipe and hold the smartphone close to the Bluetooth module.

Question 20

Bluetooth Motion Mode - how to setup My2n App and use the 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. 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, for example, if some users have some old mobiles (Android 8 or 9 , or iOS 15). However, Offline Pairing cannot be done using Access Commander .   For a brand new site in My2N - Start with online pairing first! Once you have your 2N devices in My2N and first cloud access is assigned, you can also create offline paired credentials on the device itself - you must create a separate user in the device directory for that. If you create offline paired credential first, after enabling the cloud access, already created offline credentials will stop working.   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.  Motion Mode - Overview Motion Mode uses Bluetooth wireless communication technology between two devices over a distance. It is based on communication between two paired devices for secure authentication.   Minimum required Android / iOS versionAndroid version My2n App version iOS version My2n App version 10 and higher*3.0.0 and higheriOS 16 and higher*3.0.0 and higher   *  Using Android 8 or 9 , or iOS 15 will partially work, advanced features will not be available. Functions Bluetooth is used for exchanging information between two devices for a short distance. This identification is provided by a unique code of the end devices that contains this technolgy, like almost every smartphone these days. There is a communication between the smartphone and 2N IP Verso intercom (or 2N Access Unit) equipped with a Bluetooth module. This communication is secure and based on public and private keys that are exchanged (we use RSA-1028 asymmetric encryption and AES-128 symmetric encryption).  Requirement 2N IP Verso with firmware version 2.33 or higher.Bluetooth module (order no. 9155046) connected to 2N IP Verso (or to 2N Access Unit) via internal Verso bus cable.My2n App app version 3.0.0 for iOS and Android.Bluetooth enabled on the phone.Location enabled on phone (for Android only). *Xiaomi Poco phones may not be compatible with WaveKey when app is on background  Step by step guide - How to setup Online Pairing between My2n App and 2N IP Intercom 1) On an existing my2n site, create an Access Group:    And then edit it with device, user and eventually apartment :  Add all devices, the users will have access to with the Access group:  Add all users, the Access group allows using the previously added devices:  You can, then, add apartment the same way. It will be mandatory in case of apartment model site:  2) After, you will need to enable My2n App access for the user:  The site or company admin, when he will enable it will see this warning explaining that in case, some users are offline paired with this device, they will have their Bluetooth Access revoked shortly:    3) Once this done, the user, if he has the My2n App installed on his mobile with the required Android or iOS version, will see appear on his App the below feature that he will have to activate:  Step by step guide - How to setup Offline Pairing between My2n App and 2N IP Intercom 1)  Please open web configuration of 2N IP Intercom and navigate: In the Old Web Interface to section Hardware -->  Extenders and locate Bluetooth module.Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module In Pressing the Bluetooth symbol, you will be able to open the door by tapping the Bluetooth icon on the Bluetooth module.  In the New Web Interface to section Access --> Modules --> Bluetooth  Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module  2) Install My2n APP app from the official OS store (Google Play, iTunes) to the mobile device of the user you wish to assign Bluetooth access to. 3) In the intercom's web configuration please navigate to section Directory --> Users (1) and create the user you wish to grant Bluetooth access for.Fill in a username and scroll down to the User WaveKey parameter(2). Click on the Bluetooth icon as shown on the picture below to pair via this device, to the Bluetooth module with the app on the mobile phone.   Once you do, a PIN code for pairing with the app in a phone will be generated as shown on the image below:  Default PIN validity is 1 hour. You need to pair a mobile phone before this time expires.Note: PIN validity can be changed in section "Services --> WaveKey --> Pairing Mode Settings"   4) Please go to close proximity (1-2 meters) of the 2N IP Intercom you just configured for pairing with the app.   5) When in close proximity to 2N IP Intercom equipped with a Bluetooth module, run the application and tap the + sign (1) and then The Pairing PIN option (2). Enter the pairing PIN provided by the intercom or from Access Commander (3) in the appropriate section (4), and start Pairing (5). Finally you will have the confirmation of the successful Pairing (6).  6) The app will start searching for devices in proximity. Please note that if the Bluetooth is in touch mode, you need to touch the Bluetooth reader first to trigger the pairing sequence.  From now, If you are using Offline or Online Pairing, you see the device(s), if you are using Bluetooth, touching the Bluetooth sign on the intercom will trigger the door.  7) If you want now to use the Card mode, make sure to allow it on the 2n device: In Old Web Interface under the section Hardware -->  Extenders and locate Bluetooth module. Add theMotion Detection option :  In the New Web Interface under section Access --> Modules --> Bluetooth Add the Motion Detection option :  8) You will now need to enable the Motion Detection feature. In Old Web Interface, please navigate to the section Hardware --> Camera, then click on the Internal Camera tab. Make sure to enable the Motion Detection, and then select how sensitive you wish to set the motion detection to be by adjusting the Sensitivity Threshold. To optimize the motion detection you will have to adjust the Sensitivity Threshold and Detection Area as shown below.  In New Web Interface, navigate to Customization-->Camera-->Internal Camera and hit the Arrow  Then you will be redirected to the next page, and you will have to enable at least one profile for Motion detection:  And, as in the Old Web interface you will be able to Enable the profile, adjust the sensitivity threshold with multiple factors as the detection area:  Don't forget to SAVE your new settings From now, If you are using Offline or Online Pairing, you see the device(s), if you are using motion mode, start walking towards the 2 N intercom, and the door should be triggered by the Application.

Question 21

Bluetooth Touch Mode - how to setup My2n App and use the 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. 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, for example, if some users have some old mobiles (Android 8 or 9 , or iOS 15). However, Offline Pairing cannot be done using Access Commander .    For a brand new site in My2N - Start with online pairing first! Once you have your 2N devices in My2N and first cloud access is assigned, you can also create offline paired credentials on the device itself - you must create a separate user in the device directory for that. If you create offline paired credential first, after enabling the cloud access, already created offline credentials will stop working.   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.  Touch Mode - Overview Touch Mode uses Bluetooth wireless communication technology between two devices over a distance. It is based on communication between two paired devices for secure authentication.    Minimum required Android / iOS versionAndroid version My2n App version iOS version My2n App version 10 and higher*3.0.0 and higheriOS 16 and higher*3.0.0 and higher   *  Using Android 8 or 9 , or iOS 15 will partially work, advanced features will not be available.  Functions Bluetooth is used for exchanging information between two devices for a short distance. This identification is provided by a unique code of the end devices that contains this technolgy, like almost every smartphone these days. There is a communication between the smartphone and 2N IP Verso intercom (or 2N Access Unit) equipped with a Bluetooth module. This communication is secure and based on public and private keys that are exchanged (we use RSA-1028 asymmetric encryption and AES-128 symmetric encryption). Requirement 2N IP Verso with firmware version 2.33 or higher.Bluetooth module (order no. 9155046) connected to 2N IP Verso (or to 2N Access Unit) via internal Verso bus cable.My2n App app version 3.0.0 for iOS and Android.Bluetooth enabled on the phone.Location enabled on phone (for Android only). *Xiaomi Poco phones may not be compatible with WaveKey when app is on background  Step by step guide - How to setup Online Pairing between My2n App and 2N IP Intercom 1) On an existing my2n site, create an Access Group:    And then edit it with device, user and eventually apartment :  Add all devices, the users will have access to with the Access group:  Add all users, the Access group allows using the previously added devices:  You can, then, add apartment the same way. It will be mandatory in case of apartment model site:  2) After, you will need to enable My2n App access for the user:   The site or company admin, when he will enable it will see this warning explaining that in case, some users are offline paired with this device, they will have their Bluetooth Access revoked shortly:  3) Once this done, the user, if he has the My2n App installed on his mobile with the required Android or iOS version, will see appear on his App the below feature that he will have to activate:  Step by step guide - How to setup Offline Pairing between My2n App and 2N IP Intercom 1)  Please open web configuration of 2N IP Intercom and navigate: In the Old Web Interface to section Hardware -->  Extenders and locate Bluetooth module.Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module In Pressing the Bluetooth symbol, you will be able to open the door by tapping the Bluetooth icon on the Bluetooth module.    In the New Web Interface to section Access --> Modules --> Bluetooth  Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module    2) Install My2n APP app from the official OS store (Google Play, iTunes) to the mobile device of the user you wish to assign Bluetooth access to. 3) In the intercom's web configuration please navigate to section Directory --> Users (1) and create the user you wish to grant Bluetooth access for.Fill in a username and scroll down to the User WaveKey parameter(2). Click on the Bluetooth icon as shown on the picture below to pair via this device, to the Bluetooth module with the app on the mobile phone.   Once you do, a PIN code for pairing with the app in a phone will be generated as shown on the image below:  Default PIN validity is 1 hour. You need to pair a mobile phone before this time expires.Note: PIN validity can be changed in section "Services --> WaveKey --> Pairing Mode Settings" 4) Please go to close proximity (1-2 meters) of the 2N IP Intercom you just configured for pairing with the app. 5) When in close proximity to 2N IP Intercom equipped with a Bluetooth module, run the application and tap the + sign (1) and then The Pairing PIN option (2). Enter the pairing PIN provided by the intercom or from Access Commander (3) in the appropriate section (4), and start Pairing (5). Finally you will have the confirmation of the successful Pairing (6).  6) The app will start searching for devices in proximity. Please note that if the Bluetooth is in touch mode, you need to touch the Bluetooth reader first to trigger the pairing sequence.  From now, If you are using Offline or Online Pairing, you see the device(s), if you are using Bluetooth, touching the Bluetooth sign on the intercom will trigger the door

Question 22

Call in sequence or parallel using My2N

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. Please note that currently, it is not possible to set up calling in sequence natively through the My2N portal, hence you need to do it manually in the intercom.          Mode   As recommended, leave the intercom in automatic mode, the My2N won't re-write the manually created user.          Create users manually   It requires more knowledge of 2N OS.      do not create any ring group (users won't be automatically created in the intercom's directory)        locate the device ID (phone number) for each user     use remote configuration service (or connect locally using the IP address of the intercom) and open the device's web interface     navigate to section Directory > Users  create separate users and use the Device ID as their phone numbers with the correct format "deviceID"/2 (e.g. 4901571323/2). You can add up to 3 phone numbers and then an User Deputy (3) if needed: In Old Web Interface: In New Web Interface:    "deviceID"/2 are made with this following id from My2N platform :  Cascade calls support different types of phone numbers, you can, under the same user use local calls syntax (device:xxxxxxxxxx), SIP calls syntax (sip:192.168.17.xx) or sip proxy calls syntax like for my2n (1436669863/2 , behind slash sign is the number of the used SIP Account)

Question 23

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 24

Cannot add a device to My2N/move a device to a different My2N account

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.  There are two reasons why you are not able to add the device to the My2N portal, the serial might be invalid or the device has been already added somewhere else: A notification will show up, explaining the possible cause   The Serial Number does not exist The serial number you have entered does not relate to any device, please double-check the validity of the number, correct any typo:  The serial number can be found on the back of most units, inside the web interface and on the CERTIFICATE OF OWNERSHIP (included in the box of our units):    The device is already added If the device is already added elsewhere, you must first delete it from the old My2N account to add it to yours If the device has been used by a previous owner, try contacting them and ask about deleting the device from their My2N account Generating a new My2N Security Code   If you do not have access to the old My2N account, please follow the steps below:   Click on the "System" (1) tab  Open the section "Auto Provisioning" (2)  Generate a new security code by clicking on the "Generate New" (3) button  This action will generate a new My2N security code  The old  My2N security code is therefore no longer valid In the Old Web Interface:    In the New Web Interface: Go to Integration (1)-->Autoprovisionning (2)-->My2N (3)Generate a new Security Code, The old one is therefore, no longer valid:   Performing a software factory reset If you would like to keep the configuration, now is the time to make a backup, in the Old Web Interface:  You can do so under the "Maintenance" (4) tab and "Backup configuration" (5) Reset the password for the device configuration (optional) and then click "Download"  Proceed to perform a software factory reset the device:  Click on the "Reset Configuration" (6) and "Network Settings and Certificates" (7)  Press the "Yes" (8) button to proceed  Once the Reset is done, the configuration of the device will be set to default values, including the network settings           In the New Web Interface: Go to System (4)-->Maintenance (5)Reset the device to default (6)-->Choose to reset everything and confirm the Reset (7)   You can now login back with the default credentials(admin/2n), choose a new password and register the device in your own new site following instructions from page: 2N IP intercom into My2N

Question 25

Change of billing information (company name & address) in My2N

Accepted Answer

If you want to change the billing information, please log into the  My2N  portal and follow the steps below.    click on the company selector  select the company you want to edit           The billing information can be changed only if no payment has been created by your company. If the company made at least one payment, please contact customercare@2n.com to change the company billing info for you.     open billing info menu  click on EDIT BILLING INFO

Question 26

Change to the new apartment license model in My2N

Accepted Answer

Please note that the old license model (ordered through Customer Care) is no longer supported therefore it is necessary to change it now before your site expires.          How the old license model looks like?     If your business model is  Custom  , you are using the old license model, which is no longer supported and cannot be prolonged.                   How to migrate to the new license model Migration to the new license model is a multi-step process and requires the cooperation of 2N Tech Support and the customer (company/site admin). The customer is required to create apartments and each device/user needs to be assigned to a corresponding apartment with a limit of 4 paid devices (phones, tablets, and 3rd party devices) per apartment.  Creating apartments and assigning devices  create an apartment     assign devices to a corresponding apartment     check if all devices are assigned to a corresponding apartment     repeat the process until all devices (excluding the intercoms) are assigned to the correct apartments       Once the model is changed by the technical support all users will be logged out from their application, it is necessary to log back in.       Contacting the 2N Tech Support If you have all devices assigned to a corresponding apartment, now contact 2N Tech Support and ask them to change the license model. You can contact 2N Tech Support using the My2N form or send a reply to an already-created ticket.    Changing the type Once you receive an e-mail from 2N Tech Support that the model has been changed, you need to set the type, as you were previously using the old apartment model it is wise to choose a new apartment model.                     Paying for the new model Once you have migrated to the new model, you can pay via credit card directly from the My2N portal and take advantage of automatic recurring payments or order an apartment license from your distributor in the form of a voucher code that you will have to activate manually, ordering numbers:  9137958 — My2N Annual Apartment Subscription (Where to buy?)  02683-001 — My2N Annual Apartment Subscription (Where to buy?) -   US & APAC ONLY           How many licenses you should order? If you are not sure how many licenses you need to buy; just check the site dashboard.    Even though 5 apartments are displayed, only 4 require a license because the fifth apartment is either empty or using a device in local mode. Per the picture below you need to order: 4x 9137958 OR 4x 02683-001 -  US & APAC ONLY

Question 27

Company Admin - Add/Delete

Accepted Answer

The Company admin role can be granted or remove only from the COMPANY level in the Company admins section.  Navigate to the COMPANY level You can move to the COMPANY level by clicking on the company in the top left corner (1) and selecting the company where you want to add or remove company admin or using the link in the section Site users - "Company admins" (1)   Add a new company admin Once you will be on the COMPANY level open the section Company admins (2)After opening the section, use the CREATE ADMIN button (3) and fill in the user's email, first and last name and click Create Admin (4).    Delete a company admin In the same Company Admin section at the COMPANY level, use the three-dot menu (5) and select Delete User (6).

Question 28

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 29

Configuration of the switch codes on the My2N Cloud

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 is showing you how to configure the switch codes within the My2N cloud to be able to open doors. In case you don't have an electric lock connected to the intercom, please read the following articles before configuring the switch:   Electric locks in 2N IP Intercom accessoriesConfiguration of electrical outputs on 2N IP Intercoms Step-by-step Guide Firstly it is necessary to configure the switch codes under the intercom in your My2N account.   1) On your My2N site, go to section devices -> choose the intercom you want to configure -> click on the 3 dots -> choose option "edit device".      2) Now, go to the section switch codes. Here you may enable/disable the particular switch, change the DTMF code for each switch and decide if the switches are managed by My2N or not.    3) The codes are uploaded into the intercom automatically if you have selected the option "managed by My2N". However you can also take a look into the intercom settings and verify if the codes have been uploaded into the intercom or in case you have chosen the option "not managed by My2N"  the codes can be configured in the following section Hardware -> switches in the web interface.   Switch 1 would be used to control the connected electric lock to the Output1.            In the Old Web Interface:            In New Web Interface:  Switch 2 would be used to control the gate connected to the Relay1:            In the Old Web Interface:               In the new Web Interface:  Switch 3 would be used to control IP WebRelay via HTTP commands, controlled output would be set to none. Gold License required for sending HTTP commands.            In Old Web Interface:              In the New Web Interface:  Switch 4 would be used to to control the connected electric lock to the Output1 when the code is entered by keypad only.             In the Old Web Interface:                In the New Web Interface:  4) In case of some issues with the opening of the door via the DTMF code, please verify the following section Calling -> SIP 2 -> Audio -> DTMF receiving and enable both  SIP INFO/RTP. In the Old Web Interface:    In the New Web Interface:

Question 30

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 31

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 32

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 33

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 34

Delivery solution with My2N automation

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. Description Imagine that you have a separate delivery room in your apartment building, your package arrived and you are not at home, how can you receive it, how can you grant access for the delivery guy and also "follow" him to the delivery room with usage of My2N? Sure you can have two intercoms with the display or same amount of buttons for each resident, so the delivery guy could call you also from the indoor intercom, but this may cause impracticality for the delivery guy (as he needs to find you on the list and call you again) and overall higher cost of the installation, in that case, you can use following automation to "forward" the call automatically to the indoor intercom. In that case, you can have only one button unit at the door to the delivery room.    How to set up My2N & Intercom's switches First of all, you need to have your devices and users added to your My2N account and assigned them under its correct button. In the Switch Codes tab, you need to fill another switch code for the delivery solution. This code is then used in the automation to trigger the whole event. To be able to also open the door for the delivery guy you need to synchronise this code with your already setup switch for the door, in our example, we used Output 1 for opening the doors that we've synchronised with the Switch 2 (Delivery) so when we trigger the delivery button in the app it will also trigger the Switch 1 simultaneously.   Make a secondary switch for the delivery solution       Synchronise the delivery switch with the door switch (Intercom at the Main Entrance) In the Old Web Interface:    In the New Web Interface:          Automation & HTTP API In order to make this work, you need to make automation that will send an HTTP command to the other unit, to start calling the number that was called from the main entry device. But first is necessary (recommended) to set up an Account on the delivery room device that has a call control privileges and will authorise the HTTP command, it could be also done without authorisation but it is considered as a security flaw. Download automation: Delivery.amAfter that you are ready to make or upload the automation to the main entry device; please fill the DTMF code according to the Switch 2, that you've filled in the My2N. Please use the correct username and password that you've set for the HTTP account and fill the Formatter with the following HTTP command: https:///api/call/dial?number={1}/2The delay determinates after how many second the delivery room unit will call back to the Mobile Video app after you let the delivery guy in, please set at least 5 seconds so the previous call is properly ended.   Set up HTTP API account (Intercom inside, at the delivery room)     Create automation (Intercom at the Main Entrance)       Requirements    Active My2N account (paid or trial)  Two intercoms (firmware 2.30 or higher)  Enhanced Integration license (Order No. 9137907) for both intercoms           Compatible hardware and adjustable parameters   Date of automation design: 09/07/2020 Firmware Version: 2.30.2.39.7   List of compatible Hardware:  2N IP Verso  2N IP Solo  2N IP Vario  2N IP Base  2N IP Force  2N LTE Verso  List of adjustable automation parameters:  DTMF code  Delay (to maintain reliability do not use lower than 5 seconds)  IP address for the HTTP command  Username & password for the HTTP request         Note   When you have multiple users under one calling number (ring group) the delivery room unit will call back to everybody in the same ring group, not just the one number that picked up the call on the main entry unit.

Question 35

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 36

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 37

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 38

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 39

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 40

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 41

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 42

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 43

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 44

Firmware Update via My2N

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 My2N Management Platform allows you to easily update the firmware of your 2N OS devices.  Update via My2N  Log into the My2N portal and locate the device  Select correct My2N Site (1)  Open the "Devices" (2)   Open the Device details Click on the desired device (3), or, click on the tree dots (3) on the right side and select "Edit device" (4)   Perform the update remotely  View the release notes "See the benefits" (5) containing all changes and improvements  Update the device using one of the UPDATE (6) buttons Upgrade process will reboot the unit, causing it temporarily show as "Offline" in the My2N device overview    Update via device's web interface    If the update via My2N won't be possible, you can always try to use the intercom's web interface to update the firmware using a file or online update.     We recommend doing a configuration backup before you proceed with the update.     Open the Remote Configuration  Expand the Remote Configuration Services menu by clicking on the arrow (1)  Click on the "OPEN CONFIGURATION" (2)     Intercom's web interface  Fill out the login credentials (3) Log into the Intercom (4) Note, device password is not linked to the My2N account password: From Old Web Interface:   From The New Web Interface:   Perform the update manually Click on the "System" (5) In the Old Web Interface:  In the New Web Interface:   Select the "Maintenance" (6) tab and then click on the "Upgrade Now" (7) buttonIn the Old Web Interface:              In the New Web Interface:      Upgrade process will reboot the unit, causing it temporarily show as "Offline" in the My2N device overview

Question 45

How to add a 3rd party SIP device/Application

Accepted Answer

In order to make calls from 2N IP Intercoms to other devices such as 3rd party applications or devices, you need to add them to My2N first.  Requirements:      2N IP device added in the My2N account  3rd party device or application which supports:  SIP (Protocol for signaling)  Codec G.711a/G.711u (PCMA/PCMU) for audio  Codec H.264 for video      Step by step guide   In the My2N account go to Devices (1) and select ADD DEVICE (2)  A new window will appear, please select add 3rd Party device (3) by clicking on it    In the next step, you need to name the device and assign it to a user. You can also select an apartment for a better management  Then click NEXT (4)      The device's login credentials will be sent to the chosen user's email address     Confirm your choice by clicking on the NEXT button. You then have an opportunity to add the newly created device to an intercom’s button. When you are done click on the FINISHED (5) button    Once you finish by clicking on the FINISHED button, an email will be sent to the user's email address and you will get a confirmation dialogue window  Now you have successfully added your 3rd party application or device to your My2N account, you can hit CLOSE (6)    Now you will have to register the 3rd party application to the My2N account using provided credentials (username, password, SIP proxy address)  The credentials for registration can be found in the device detail, click on the DEVICE (7)         Open the Mobile Video tab (8), make sure it is ACTIVATED  As you can see, the Status info (9) is currently "Needs configuration"  Observe the SIP Proxy details and copy them into the corresponding SIP registration account in your SIP device:  Device ID is the phone number/username for SIP Registration  SIP Proxy Address is both SIP Proxy address and SIP Registrar address  Secured Calls - Only UDP or TCP can be used     If the registration is successful on both ends, the Device status/Status info will change to Registered (10)  Configuration of a 3rd party device is done

Question 46

How to change credit card information

Accepted Answer

If you want to change the credit/debit card information due to expiration of the card or you wish to use a different card, follow the instructions bellow:    Short guide on the website  Go under "Subscriptions, licenses" (1), click on " How to change credit card" (2)  Check the short guide (3)    Step by step guide  The recurring payment has to be disabled to change the credit card info  Go under "Subscriptions, licenses" (1), see the "Recurring payment" and select "DEACTIVATE" (2)      If you don't see the "DEACTIVATE" (2) button, that means recurring payments are not active, to enter new credit card details please proceed by clicking on the "ACTIVATE" (3) button  Once you will deactivate your recurring payments you need to activate them again by clicking on "ACTIVATE" (3), but now use a different credit card  If you don't see the "ACTIVATE" (3) button please proceed by clicking on "Purchase subscription for the 2N Mobile Video service" (4) shown bellow      After choosing the monthly or annual subscription your will be redirected to the payment gateway where you fill in the new card details:    Please note that once you will re-activate the subscription, a new payment will be processed which means that you will pre-purchase additional credits

Question 47

How to configure 2N Indoor Touch 1.0 to make and receive calls through My2N

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. There are two modes of the SIP registration of the 2N Indoor Touch unit to the My2N portal:    Local  -  this mode is free of charge   and allows you to use the 2N Indoor Touch in your local network. The reason why you can choose this mode is to make the configuration of the intercom easier so it is not necessary for you to disable the automatic configuration and you can just simply add the 2N Indoor Touch in your local mode and the intercom will be configured automatically. In this mode the 2N Indoor Touch has to be placed in the same LAN as the intercom.    Cloud  - this mode allows you to make the calls from the 2N Indoor Touch to the 2N Mobile Video application and vice versa. You can use this mode in the situations where the unit is placed in a different LAN than the intercom.     1. Local mode  You can add the 2N Indoor Touch by clicking on the Devices button and then the ADD DEVICE button. Then choose 2N Device option.   Figure 1: add new device  Figure 2: choose 2N device      In the next step you will be asked for putting of the serial number of the device and then you will name it.Finally you will confirm it by clicking on Next below right. Indoor Touch devices do not have security code.     Figure 3: add device serial number and 2N Indoor Touch identifier     Name the device - this is a name which will be shown in your My2N account (in this example the name of the device is Entry Hall)2N Indoor Touch identifier - this is the device name of the 2N Indoor Touch - see the picture below for the location of the Identifier (in this example the identifier is 2NIndoorTouch-540956           Figure 4: 2N Indoor Touch identifier 2. Cloud mode In My2N press button Devices in order to see your devices. Find your 2N Indoor Touch you wish to manually register to My2N.Press Details button (right arrow icon) to edit details of your 2N Indoor Touch unit.  Figure 5: Cloud registration In device details, switch Connection mode to Cloud by clicking on it.  Figure 6: Cloud registration The SIP registration details can be obtained in the 2N Indoor Touch device detail setting in your account (refer to Figure 4). In device detail, click on the arrow on the right to the "2N Mobile Video" section and then you will see the SIP Proxy credentials.  Figure 7: SIP proxy details Now, you need to enter the SIP details to the 2N Indoor Touch unit, either locally or over its web configuration interface. Locally - tap on the 2N IP Mobile icon.  Figure 8: 2N Indoor Touch cloud registration In app please tap on My2N Mobile Video  Figure 9: 2N Indoor Touch cloud registration On next screen activate My2N Mobile Video  Figure 10: 2N Indoor Touch cloud registration   On next screen, insert login details for your device obtained from My2N (  please use device details from your My2N account  ) and press Login button  Figure 11: 2N Indoor Touch cloud registration   If you entered correct details, your 2N Indoor Touch successfully registers to My2N.    Figure 12: 2N Indoor Touch cloud registration     What to do next: Once you configure all your devices, please see below which step needs to be taken next.  - Please set intercom's buttons in order to point them to mobile device you wish to call from intercom to.    In order to make calls from intercom to 2N Indoor Touch devices, buttons on intercom needs to be configured to call correct 2N Indoor Touch devices. For detailed information how to set buttons, please visit following article: How to configure call settings for the IP intercom

Question 48

How to configure 2N Indoor Touch 2.0 to make and receive calls through My2N

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. There are two modes of the SIP registration of the 2N Indoor Touch 2.0 unit to the My2N portal, 2N Indoor Touch 2.0   does not require any further subscription:      Local  -   and allows you to use the 2N Indoor Touch 2.0 in your local network. The reason why you can choose this mode is to make the configuration of the intercom easier so it is not necessary for you to disable the automatic configuration and you can just simply add the 2N Indoor Touch 2.0 in your local mode and the intercom will be configured automatically. In this mode, the 2N Indoor Touch 2.0 has to be placed in the same LAN as the intercom.    Cloud  -    and     allows you to make the calls from the 2N Indoor Touch 2.0 to the 2N Mobile Video application and vice versa. You can use this mode in situations where the unit is placed in a different LAN than the intercom.    Caution   2N Indoor Touch 2.0 require firmware version 4.7 or higher           1. Local mode  You can add the 2N Indoor Touch 2.0 by clicking on the Devices button and then the ADD DEVICE button. Then choose the 2N Device option.       In the next step, you will be asked for putting the serial number of the device, then you will name it and put the 2N Indoor Touch 2.0's ID.Finally, you will confirm it by clicking on NEXT below right (and also on one upcoming window).                Device name - this is a name that will be shown in your My2N account  (in this example the name of the device is Indoor Touch 2.0)   Device ID - this is the device name of the 2N Indoor Touch 2.0 - see the picture below for the location of the ID   (in this example the ID is IDT20)               2. Cloud mode  In My2N press the button Devices in order to see your devices. Find your 2N Indoor Touch 2.0 you wish to manually register to My2N.Press the Details button (three dots icon) to edit the details of your 2N Indoor Touch 2.0 unit.    In the device's details, switch Connection mode to Cloud by clicking on it (see below).     The SIP registration details can be obtained in the 2N Indoor Touch 2.0 device detail setting in your account (refer to the previous picture). In device detail, click on the arrow on the right to the "2N Mobile Video" section and then you will see the SIP Proxy credentials.    Now you need to enter the SIP details to the 2N Indoor Touch 2.0 unit, either over its web configuration interface (or locally).In the web interface go to Intercoms > My2N and enter here the My2N details from the previous step according to the picture below and confirm it by clicking on USE (below right on the picture below).        Please set the intercom's buttons in order to point them to the device you wish to call from the intercom.         In order to make calls from the intercom to 2N Indoor Touch 2.0 devices, buttons on the intercom need to be configured to call it. For detailed information on how to set buttons, please visit the following article: How to configure call settings for the IP intercom

Question 49

How to configure call settings for the IP intercom from My2N platform

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.  Prerequisites:  2N IP intercom  firmware version 2.32 or higher   .   2N IP intercom  needs to be connected to the Internet  .     2N IP intercom  needs to be set in Automatic mode in My2N.      Completed Step 2 - Where to call?  - you need to have at least one other device already added to My2N (smartphone, tablet...).         Step by step guide In My2N press button Devices and then click on the intercom device to access the configuration of the 2N IP intercom.   Then click on Call Settings.     A new window will appear. You will need to give a name to the label (1), this name will be visible in the device's directory. Then, you need to choose which device (smartphone, tablet or answering unit) you wish to call, when someone presses a dedicated button(2) of the 2N IP intercom. You can choose up to 10 destinations for each button (but only one apartment at the same time). Don't forget to save (3).   After you save your settings, the 2N IP intercom is configured by My2N immediately. Now you have successfully configured call settings for the 2N IP intercom. You can configure another one by repeating previous steps and choosing different intercom added in your My2N account. All the buttons if they point to at least one destination will automatically pushed in the device's directory. They won't in case it is existing but not pointing to any destination. Moreover, in automatic mode, the button number one will be automatically pushed to the main button of the intercom. In the Old Web Interface:    In the New Web Interface:

Question 50

How to enable and use Multifactor Authentication (MFA) in My2N Platform

Accepted Answer

If MFA is enabled, only mobiles or tablettes with at least iOS 3.9.0 App version and Android 3.7.4 will work. If in the whole company, one device does not fulfil the minimum prerequisites, the MFA won't be enabled. From now, all administrators will be able to enable and use Multifactor Authentication (MFA) in order to login their My2n account. Here are the steps for enabling it and then to use it. How to enable MFA For that, the administrators will have to login in their account. Onced logged, they will need to select to select their account (1), then select their User Profile (2):    He will see a new page, in which he he will be able to enable MFA (3), but at this moment Two-factors recovery codes are still greyed-out:    After selecting to enable Two-factors authentication, a pop-up window will appear asking to download a "safe" authenticator, if he still does not have any installed. Moreover, he is warned that if he is using the My2N mobile app, setting up two-factor authentication will log him out of it. And he is invited to click on NEXT (4):  For this example, we have chosen to use Google Authenticator. A new pop-up window appears with a QR code and a code to use in the Authenticator App:  On the Application, click on + sign (5), and choose which method you want to use, The QR code (7) or the setup key (6):  After scanning the QR code or entering manually the code, a new line will appear on your App with the account information (8) and the PIN (9) which can be used, and the time validity of this PIN (10)(max approx 30sec):  In case the PIN will shortly looses its validity (less than 10 sec), you will see that its color will change as its time validity. In this case, it migh be worth waiting few seconds and getting a new PIN:  However, while the authentication code is valid, enter the value in the platform (11) and save (12):  Then, finally, you will see a last pop-up windows with 12 recovery codes. You will, now, have the possibility to copy them in a safe place (13). You will be able to save them later, but once confirmed they are saved (14), you will be able to confirm them (15)     How to use MFA Now, you have enabled Multifactor authentication and copied somewhere the recovery codes. Next time you will need to long in, you will see the changes. The very first step is always the same. Same URL, same user name (email) and same password and login page:    But, then, you will have to write down the code provided by the Authenticator App and, then, log in.  In case the code has expired you will see this message and you will have to write down a new code:  Finally, you are logged in. In case you lost access to your Authenticator. You have lost your mobile, or forgot it, or any other reason, you can hit the Can't access authenticator link:  This is the moment to use the recovery codes you have already saved previously:    You can choose any of them and use it on the page you will get after clicking the link. I will use the first one, but any of them is valid:  You are now logged in again. If you go under your account section/user profile, you can see the recovery codes codes:   The one which has been already used is blurred. It is a one time  code, so it is not valid any longer. But you can use, in future , any the of unused codes for the same purpose. You can copy the remaining valid ones, delete all of them or generate new ones. In this case don't forget to save them again in a safe place.   Finally, you might want to momentally or always stop using the authenticator. In this case, just go to the same section and hit Disable two-factor authentication :  And you will have to confirm it, by hitting the unlink button:      If you would need to use it again, you will need to re-enable it as shown at the beginning of the FAQ.   What if admins loses access to the MFA authenticator and does not have generated recovery codes   In case this situation happens, the admin will have to create a ticket to support by calling to the appropriate number or by filling the form on https://www.2n.com Then: We will ask him for another admin on the site to prove that it is actually him that wants the reset of the MFA - Potentially for Site admins this can be company admin or another Site adminIf there is no one else to confirm we will ask him for any other way to prove his identity (Call/ID etc.)Request will be created to the dedicated team (AiO) to remove the second factor from his profileRecommendation will be given to the admin to generate recovery codes next time

Question 51

How to generate HAR file for Chrome

Accepted Answer

Opening the Developer tools If you are having issues with My2N website in Chrome, open the page you are having issues on in Chrome (My2N in our example):  Access the Developer tools of Chrome which you can open by clicking on the 3 dots in the top right-hand corner (1) -> More tools" (2) -> Developer tools (3)  You can also right-click on the page and select "Inspect"  Alternatively you can use Ctrl+Shift+I or simply press F12 key on your keyboard   Preparing to record the logs  Once you have the Developer tools open go to "Network" (1) and check the "Preserve log" (2)  Make sure the logs are being recorded which is indicated by the red recording circle (3)   Clearing the logs  If you happen to click elsewhere before the test begins you can clear the log by clicking on the "Clear network log" (1) button Clearing the logs will not stop the recording    Recording and downloading the logs Now you are ready to start replicating the issue:  When you click on any interactive feature on the website a log will be recorded on the right side (1)  Replicate the issue, step by step  Then download the logs by clicking on the "Export HAR" dowload button (2)  Downloaded HAR file can then be sent to our support for further analysis

Question 52

How to provide logs from the My2N application

Accepted Answer

There are 2 ways how you can download or send us the logs from the My2N application. This method works for both Android and iOS platforms.        Method 1: Using report form The first way how to send us the logs is to use the report form directly in the My2N application. This option is the best if you don't have any active cases and you are not in touch with 2N Technical Support yet. You can just simply click on the option "Report a problem" in the settings of the app.       Please note that to be able to effectively analyse logs sent from the app - 2N Technical Support needs as much info related to the issue as possible. Please do not forget to always specify:  Time/date of the issue (call with the issue)  Ticket number - in case you are already in touch with 2N Technical Support and you are sending new logs related to the issue/case which has been already reported to 2N Technical Support.  Proper description - what exactly is happening, what do you see/hear, when it is happening, during incoming or outgoing calls, the app in foreground or background (closed or locked phone), etc.         Method 2: Send logs to your email (if you already have a ticket with Tech Support) This second approach is better in case, that you are already in touch with 2N Technical Support and you are requested to provide new/additional logs. You can send the logs directly to your email and then attach the logs to the case which is already opened at 2N. Logs can be downloaded by tapping 7x on the version of the application in Settings > About the app and sending the logs to your mail or saving it to your smartphone.    If you are able to easily replicate the issue, it is better to start with a clean log file before you replicate it, here is how to delete all old logs, so you can provide our Technical Support with logs that contain only the reported issue:   Do not delete the logs if the issue occurred in the last 2-3 days (maximum size of the log file) and you are not able to easily reproduce it

Question 53

How to purchase subscription in My2N

Accepted Answer

In order to be able to use the My2N service which is out of the trial period, it is necessary to pay a monthly/annual subscription per non-2N device. The process of how to enable the subscription is described below.  Step by step guide Upon the first sign-up, you receive a 30-day free trial period of the My2N Mobile Video service. During this trial, you may test all its features with an unlimited amount of devices.It is always recommended to proceed with the free trial prior to your first paid subscription purchase.You can see your current account status in the section Dashboard. When you would like to pay a subscription for the first time, you are able to do it in the section Subscriptions, licenses. Firstly, select the desired company and site you want to activate the subscription on, then in the section Subscriptions, licenses select 2N Mobile Video.   Pricing information about the service is described in the section Subscriptions, licenses and > 2N Mobile Video > Purchase details > Details or in the section Dashboard > pricing.    Please be aware that the VAT fee is included by default. If you want to shop VAT free, please contact our Customer Service support. This process is necessary due to the fraud protection. It is required to prove the identity of the buyer. For more information please take a look at the section Terms and conditions.     To be able to proceed to the next step, please enable the checkbox: Recurring payment. Website automatically shows you how many devices you have and how much you will be charged for the devices. You can cancel the subscription in the section Subscriptions, licenses at any time.   In the next step, you have an overview of your payment details. Please double-check them. It is also necessary to enable the checkbox. The direct payment method made from the account at the moment is by using a credit card. Only distributors can use the wire transfer method of payment for a specific amount of credits.       If you do not want to use a credit card, you can purchase a voucher from one of our distributors. You can learn how to use the voucher in this article: My2N - 2N Mobile video credit vouchers            After clicking on 3D Secure Payment button you will be redirected to the payment gateway where you have to fill in the credit card details. After the successful process, you will see the following text in the new tab. You can close this tab. You will also receive an invoice by email.   Please be aware that you are giving up the right to withdraw the contract in the period defined by the law with the confirmation of the check boxes and the payment. For more information please see Terms and Conditions.          You can verify your billing information in the section Dashboard -> Check Your Billing Info.  In the section Dashboard, you can see if your payment has been processed and your service is Active. You can see the total cost of the payment and also the details of when the next payment will be done.  You are also able to deactivate your monthly subscription here by clicking on the DEACTIVATE button in the Subscriptions, licenses section.      • Be aware that once you will deactivate Mobile video service, the service will be deactivated immediately, however the money won't be returned for the rest of month in which the service has been deactivated.• If you activate the service within the same month again, you don't need to make any new payment for this month.     In this section, you can also see details whenever you change your payment or your account. There are 3 basic scenarios that can happen with your account and payments.   Your trial period expired If your free trial period expires, you can see it in the section Dashboard. You can activate your monthly subscription in the section Subscriptions, licenses.        Subscription expired   In case that the payment hasn't been processed for some reason, for example, because of the credit card expiration or low amount of money on your account, the following information can be seen in the section Dashboard.   You will be informed by an email on the day of the regular monthly subscription, that this situation occurred. You have  3 days  period in which you can fix the issue with the payment however  your service will be still active. If you don't fix the issue with the payment within these 3 days, the service will be   deactivated.       A new device has been added during the month Once you will decide to add a new device to the My2N Mobile Video service, you will see the following information in the section Dashboard. You can see the subscription for the new device and the subscription for the next month including the new device. You can pay for the new device immediately and you will be able to use the new device. Payment will be processed for the new device only and the price will include days from the activation till the end of the month only (not the whole 30 days).   If you don't pay for the new device in the current month, you won't be able to use this device, however, the regular subscription for the next month will include the new device as well.      What if my device has been stolen or I have changed the device If you wish to replace your device, you can erase the old one and add the new one. There will be no change in the service or payments. You have to fulfil the amount of paid devices only.

Question 54

How to set up My2N app access

Accepted Answer

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, for example, if some users have some old mobiles (Android 8 or 9 , or iOS 15). However, Offline Pairing cannot be done using Access Commander .   For a brand new site in My2N - Start with online pairing first! Once you have your 2N devices in My2N and first cloud access is assigned, you can also create offline paired credentials on the device itself - you must create a separate user in the device directory for that. If you create offline paired credential first, after enabling the cloud access, already created offline credentials will stop working. 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.     Minimum required iOS / Android versionAndroid versionMy2n App versioniOS versionMy2n App version10 and higher*3.0.0 and higheriOS 16 and higher*     3.0.0 and higher   * Using Android 8 or 9 , or iOS 15 will partially work, advanced features will not be available. Functions Bluetooth is used for exchanging information between two devices for a short distance. This identification is provided by a unique code of the end devices that contains this technolgy, like almost every smartphone these days. There is a communication between the smartphone and 2N® IP Verso intercom (or 2N Access Unit) equipped with a Bluetooth module. This communication is secure and based on public and private keys that are exchanged (we use RSA-1028 asymmetric encryption and AES-128 symmetric encryption). Requirement   2N IP Verso with firmware version 2.33 or higher Bluetooth module (order no. 9155046) connected to 2N® IP Verso (or to 2N Access Unit) via internal Verso bus cable. My2n App app version 3.0.0 for iOS and Android Bluetooth enabled on the phone Location enabled on phone (for Android only)   Step by step guide - How to setup Online Pairing between My2n App and 2N IP Intercom 1) On an existing my2n site, create an Access Group:                                     And then edit it with device, user and eventually apartment :        Add all devices, the users will have access to with the Access group:      Add all users, the Access group allows using the previously added devices:      You can, then, add apartment the same way. It will be mandatory in case of residential model site. 2) After, you will need to enable My2n App access for the user: But then you will see under site users that the option is greyed out and crossed:     So you will need to first allow it. For that, you can either directly click on the crossed icon, then choose ACCESS section and CHANGE CONFIGURATION:      And you will be redirected automatically to the Site settings section. Or you can directly go to the Site settings section and check the Manage My2N app section checkbox:        You will see new windows with several warnings, asking you to choose the best option for BT connection, and claiming that managing access using both 2N Access Commander and My2N simulteanously is not a supported scenario.  Therefore, if you think that this is the best option for you, all can decide to continue by hitting NEXT :      You will see a new window, showing you if one or more location IDs that  have already been used in the site, or not. If you do see a location ID with format acxxxxxxx , be aware that you are certainly using Access Commander, at least were using Access Commander in past. Then, you can decide to go forward by hitting NEXT button:  The last chance for you to change your mind and decide to keep working, eventually with Access Commander regarding BT access, is then offered to you by default. In this case just hit CONFIGURE:    If you finaly decide to want to use My2n Online pairing for BT access, choose Manage via My2N:      If you finally decide to want to use My2N Online pairing for BT access, choose Manage via My2N. If you recognize that an already existing location ID is the one created when you offline paired a mobile with a physical device (Not Thru ACOM), you can choose it and the user using offline pairing will be able to have the Offline pairing working. Or you can choose to generate one randomly or set your own ID. Or you can generate a new ID for online pairing and afterward offline-pair a mobile directly with the intercom or the Access Unit, and it will work. Then hit on CONFIGURE.   Now, the My2n App Access icon  is no longer crossed and you can enable it directly by hitting directly the new icon or by using the "..."          3) Once this done, the user, if he has the My2n App installed on his mobile with the required Android or iOS version, will see appear on his App the below feature that he will have to activate:        4) The app will start searching for devices in proximity.        From now, If you are using Online Pairing, you can see all devices in proximity that you are entitled to use.       Here is the link for How to set up Offline Pairing

Question 55

How to set up Offline Pairing

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, for example, if some users have some old mobiles (Android 8 or 9 , or iOS 15). However, Offline Pairing cannot be done using Access Commander .   For a brand new site in My2N - Start with offline pairing first! And always use the very same device for all offline paired users. Once you have your offline paired users, you can also create online paired users from the platform. You will need to go to Site Settings/Access/Configure and then choose Manage via My2N  then Yes, and I want it to keep working - you will find the device which has been used for Offline pairing, so choose it. And finally Configure. All users which will have Enable My2N App Access enabled and which will be part of an or more access rules will be online paired.  Minimum required iOS / Android versionAndroid versionMy2n App versioniOS versionMy2n App version10 and higher*3.0.0 and higheriOS 16 and higher*     3.0.0 and higher   * Using Android 8 or 9, or iOS 15 will partially work, advanced features will not be available. Functions Bluetooth is used for exchanging information between two devices for a short distance. This identification is provided by a unique code of the end devices that contains this technology, like almost every smartphone these days. There is a communication between the smartphone and 2N® IP Verso intercom (or 2N Access Unit) equipped with a Bluetooth module. This communication is secure and based on public and private keys that are exchanged (we use RSA-1028 asymmetric encryption and AES-128 symmetric encryption). Requirement   2N IP Verso with firmware until 2.50, 3.0 only give PIN code and newer one gives QR codes. Bluetooth module (order no. 9155046) connected to 2N® IP Verso (or to 2N Access Unit) via internal Verso bus cable. My2n App app version 3.0.0 for iOS and Android, for QR code pairing 4.1.0 on Android and 4.4.0 on iOS are the minimum versions  Bluetooth enabled on the phone Location enabled on phone (for Android only) *Xiaomi Poco phones may not be compatible with WaveKey when app is on background    Step by step guide - How to setup Offline Pairing between My2n App and 2N IP Intercom   To improve the user experience and streamline the device pairing process, we have introduced a new QR code-based pairing method. This update is part of our ongoing effort to enhance usability and security, particularly in scenarios where using PIN could be riskier. QR code pairing simplifies the process while increasing strong cryptographic verification, supporting offline pairing use-case. Online pairing remains unchanged. Users can now pair their device with an intercom by scanning a QR code that contains the intercom’s public key information. This QR-based pairing method is accessible directly from the main dashboard and is added next to the the existing PIN code method. 1)       Please open web configuration of 2N IP Intercom and navigate: In the Old Web Interface to section Hardware -->  Extenders and locate Bluetooth module.Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module In Pressing the Bluetooth symbol, you will be able to open the door by tapping the Bluetooth icon on the Bluetooth module.                                                   In the New Web Interface to section Access --> Modules --> Bluetooth  Launch Authentication by "On device" is selected and you can specify the distance (Signal Range) within which your smartphone will communicate with the Bluetooth module      2) Install My2n APP app from the official OS store (Google Play, iTunes) to the mobile device of the user you wish to assign Bluetooth access to. 3) In the intercom's web configuration, please navigate to section Directory --> Users (1) and create the user you wish to grant Bluetooth access for.Fill in a username and scroll down to the User WaveKey parameter(2). Click on the Bluetooth icon as shown on the picture below to pair via this device, to the Bluetooth module with the app on the mobile phone.                                                                                          Firmware 2.32 to 3.0.2                                                                     Once you do, a PIN code and a QR code for pairing with the app in a phone will be generated as shown on the image below: Default PIN validity is 1 hour. You need to pair a mobile phone before this time expires.Note: PIN validity can be changed in section "Services --> WaveKey --> Pairing Mode Settings". The lenght of the PIN code is not changeable. It just has been increased for security reason 4) Please go to close proximity (1-2 meters) of the 2N IP Intercom you just configured for pairing with the app. 5) When in close proximity to 2N IP Intercom equipped with a Bluetooth module, run the application and tap the + sign and then The QR Code option (1), Scan the QR code obtained from the device's web interface (2), Click on Start Pairing (3) and once done, confirm by hitting OK (4)     If you choose to use the PIN option:      tap the + sign and then The QR Code option (1), Enter the pairing PIN provided by the intercom or from Access Commander (2), Click on Start Pairing (3) and once done, confirm by hitting OK (4)   6) The app will start searching for devices in proximity. Please note that if the Bluetooth is in touch mode, you need to touch the Bluetooth reader first to trigger the pairing sequence.          From now, If you are using Offline or Online Pairing, you will see the devices you are paired with.   Here is the link for Online pairing :  How to set up My2N app access

Question 56

How to unlock the door with the switch codes in My2N

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 is showing you how to configure the switch codes within the My2N service to be able to open doors. In case you don't have an electric lock connected to the intercom, please read the following articles before configuring the switch:    Electric locks in 2N IP Intercom accessories  Configuration of electrical outputs on 2N IP Intercoms  Switch parameters description   Step-by-step Guide Firstly it is necessary to configure the switch codes under the intercom in your My2N account.   Figure 1: How to add the switch code - My2N portal   Once you click on the edit button you will see the details of your intercom and the section Switch codes. In this section, you can configure your switch code for each switch. In this example, I have defined code 1234* for the switch one. You can also define your own name for the switch. The name of the switch is shown in your 2N Mobile Video application.   Figure 2: Switch codes setting   The code is uploaded into the intercom automatically however you can also take a look into the intercom setting and verify if the code has been uploaded into the intercom or in case of manual configuration the code can be configured in the following section Hardware->switches. In the Old Web interface:    Figure 3: Switch codes intercom setting - global code  In the New Web Interface:     In case of some issues with the opening of the door, please verify the following section and enable only SIP INFO DTMF receiving (the most reliable way) in the section Calling > SIP2 > Audio Make sure that SIP INFO (RFC-2976) is checked as it is the protocol used by 2N devices and RTP (RFC-2833) as well as it it often used by third party devices. In the Old Web interface:  Figure 5: DTMF intercom setting In the New Web interface:

Question 57

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 58

I did not received an e-mail

Accepted Answer

If you did not receive an e-mail to activate your My2N account or reset your password:  Check the validity of your e-mail address you have entered  Check your SPAM folder  If the SPAM folder is empty, please check with your e-mail administrator/provider if the domains  below are not blocked:   q1.mail4eshop.com - (88.208.103.192)  q1.mailq.cz - (88.208.103.164)  q2.mailq.cz - (88.208.103.165)  q3.mailq.cz - (88.208.103.166)  q4.mailq.cz - (88.208.103.167)  If none of the above has helped you resolved the issue, please contact our 2N Technical Support here.

Question 59

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 60

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 61

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 62

Integration the Grandstream HT801 with 2N IP Intercom

Accepted Answer

In this manual, we will show, how to integrate the Grandstream HT801 with our intercoms using direct calls and SIP Proxy.   Requirements    intercom firmware version - 2.30.2  HT801 firmware version - 1.0.21.4  optionally SIP Proxy - My2N, NetStar (4.4.21), etc.          Direct calls      HT801 configuration There is no need for any configuration of the HT801 to be able to receive calls directly, you just need to know its IP address. The IP address can be retrieved by pick up the phone, press *** and after you enter a voice menu select parameter 02. If you have correctly enabled DHCP server the HT801 will tell you its IP address.  In order to make a call from the HT801, you need to access the menu first with pressing *** and using parameter 47.  After the message is played you need to dial an IP address of the called device divided with * and accept it with # or wait few seconds (for example 192*168*50*142#).          Intercom configuration  Create a user for the HT801 and assign it an IP address, that you've found in the previous step in this format sip:    Assing this user under a Quick Dial Button.    If you also want to receive calls from the HT801, you need to set the correct Answering Mode in the intercom, it is set to busy by default.       SIP Proxy      HT801 configuration     1. First you need to register Grandstream HT801 in My2N, see this FAQ: How to add a 3rd party SIP device/Application        2. Connect the HT801 to your network and find its IP address, the IP address can be retrieved by pick up the phone, press *** and after you enter a voice menu select parameter 02. If you have correctly enabled DHCP server the HT801 will tell you its IP address.     3. Use this IP address to connect via the web interface, default credentials are admin/admin.         4. Enter the FXO PORT configuration and fill up the credentials for registering to PBX (use the credentials from My2N).             Intercom configuration 1. First, register your 2N IP Intercom in My2N, see this FAQ: 2N IP intercom into My2N using the Security Code 2. In My2N configure calls from 2N IP Intercom to Grandstream HT801, see this FAQ: How to configure call settings for the IP intercom

Question 63

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 64

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

Management Platforms

The My2N Management Platform

2N Access Commander

List of Faqs