Question 1

2N 2Wire - Installation and Configuration

Accepted Answer

2N 2Wire is a set of two convertor units that lets you connect any IP device installed at locations with no IP infrastructure to your network. Connect the device, such as an IP intercom, to one unit and a switch to the other unit. Then connect both convertor units to each other using the existing analogue wiring. This will transmit audio and video as well as supply power.   Prerequisites  2N 2Wire(2 pieces of 2N 2Wire converter units and 1 power supply adapter)  Specifications: Speed: 10/100 Base T, half/full duplex, auto-negotiationIEEE 802.3 af/at 40Watt Compliant PoE+Cable Type: 2Wire, Cat 5e., Cat 6. or similarImpedance: 25Ω to 100ΩTransmit Coverage: Typical 720ft (220m) @ Cat6 with PoE at far end; up to 2460ft (750m) possible; depends on wiring and interference      Product features  Using legacy analog 2 wire cabling for IP intercom connection including PoE power supply  Easy configuration, no IP address and network setup required, plug&play  Powering the IP-connected devices via PoE is possible up to a distance of 220m, twice the maximum Ethernet specification cable length.  You can connect up to 2 pairs of 2N 2Wire convertor units to a single switch. This means you can connect an intercom to several indoor stations as well as an IP camera.The pairing procedure must be proceeded first.    Basic installation      Install 2N 2Wire leader unit where your Ethernet cable ends and 2 wire cabling begins, plug in them.Do not connect 2N 2Wire units to PoE ports. If you don't have any non-PoE ports available, make sure to disable PoE on the port you're going to connect 2N 2Wire to.    Install 2N 2Wire follower unit where you need to convert 2 wire cable back to Ethernet at a remote location. Please observe polarity of the 2 wires. Connect the provided power supply to the leader unit.  Either of the units can be leader or follower.Leader unit is the one with connected power supply while follower is powered via 2 wires.  Blue Power LED indicators should indicate that both units are powered.      Use case scenarios  Single leader & Single follower      This is the simplest configuration and works straight out of the box.Just make sure you connect the 2 wires correctly to each adapter. Positive to positive & negative to negative.      Single leader & multiple followers This works straight out of the box as well.Multiple followers can be wired into a single leader, max. 3 followers can be connected to a leader.Again make sure to connect the 2 wire correctly to each adapter. Positive to positive & negative to negative.      Multiple leaders & Multiple followers If this configuration is required and you are installing multiple leader adapters on to a single network, it is very important to perform the pairing procedure (described below the pictures),otherwise you may experience network conflict issues.        The pairing procedure All units are in join mode. They will find each other and establish basic level encrypted communication.To use more leaders in the same network, we must return the units to an un-joined mode and then join them again.In case of adding another unit (e.g. as a replacement), you must repeat all the procedure again.Un-joining mode  Connect the power supply to the leader and connect the follower via the 2 wire connection.Do not connect them to the network or the IP device yet.Press and hold the ‘Grp’ button for 10 seconds, until you see all lights on the adapter go off.Then you should see only the power light illuminated.   Joining modeIn a single leader & single follower joining scenario, it doesn't matter which unit you put into this mode first.If you have multiple followers connected to a single leader, then you must connect all followers via the 2Wire connection to the leader first, then run individual joining procedures for each connected follower. To do this you must initiate the joining mode on the leader first and then the first follower. Then repeat this for each follower connected to the leader.         Connect the power supply to the leader and connect the follower via the 2 wire connection.Do not connect them to the network or the IP device yet.Press and hold the ‘Grp’ button for 2 seconds.After release, the ‘PoE’ light will begin steadily blinkingletting you know that the adapter is in ‘seek’ mode and is looking for another adapter to pair to.Once an adapter has found another adapter to pair to the ‘TWP LED’ will become static, letting you know pairing is complete.

Question 2

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 3

2N IP Eye issue - How to enable 2N IP Eye in Windows firewall?

Accepted Answer

If you have installed 2N IP Eye software in your computer and you can not see a popup window (with video from 2N IP Intercoms) at the time of an incoming call, the problem most likely resides in the firewall settings of your computer. In your Windows installation, go to section "Control Panel -> Windows Firewall" and click on "Advanced settings" as shown in the picture below.  On the left side of this window choose "Inbound Rules" and in the list of programs find 2N IP Eye. If there is a red icon, 2N IP Eye application is blocked by firewall and you have to change it manually.  So make a double click on this "Rule" and in "General" tab set the parameter Action to "Allow the connection". Then confirm those changes by "OK" button.  Do this change for both 2N® IP Eye rules. Then you should see that the icon changed according to the picture below.   As a last step do not forget to restart your computer! Otherwise the changes may not apply.  Now the Windows firewall is set properly and 2N IP Eye window should popup without any problems.

Question 4

2N IP Intercoms - How to add user access credentials

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 FAQ describes how to add access credentials to 2N IP intercoms and Access Units. These scenarios can be used on following devices:  2N IP Verso  2N IP Vario  2N IP Base  2N IP Force  2N IP Style  2N Access Unit  2N Access Unit 2.0  2N Access Unit M     RFID card access To add a new RFID card to the unit, you need to first find the ID of the card. Please put the card on the reader and then see the unit's log in Status -> Events. You will see the event "CardEntered", you need to see the "uid" parameter. Scroll to the right and copy it:   Now please go to Directory -> Users. You can either create a new user (1) or edit an existing one (2):  In User details, go to User Cards and paste the card ID here:  Now the RFID card access has been created.   Saving a new RFID card's ID can be also done with 2N USB RFID reader. A driver is needed for this device, more info is here. When the driver is installed, you can start scanning from the reader by clicking the button next to the field for Card ID.       Fingerprint access To setup a fingerprint access, go to Directory -> Users -> select User -> User Fingerprints -> click on one of the highlighted buttons. Left one is for assignment via 2N External Fingerprint reader. Right one is for assignment via reader module mounted on a unit:  Now select the finger you want to use and click Scan Finger:  Now you need to scan it 3 times and save it:  Now you can choose what this fingerprint will be used for by clicking on the highlighted button:  By default, Open door option is selected. Silent Alarm option is for triggering a silent alarm when this finger is scanned. F1 and F2 Automation option is for use in Automation scenarios. After you set the correct function, click Save and Quit.   PIN code access There are several ways of adding a PIN code access to the device:  1) The PIN code is associated with the respective Switch In this case, when the correct PIN is entered, unit will not show which User activated the switch, it will just show that the correct PIN was entered and the switch was activated. You can set this in Hardware -> Switches -> (for example) Switch 1 -> Activation Codes. You will also need to make sure that Keypad, DTMF or Keypad only option is active. After you enter the code, click Save:    2) The PIN code is associated with a User In this case, using a PIN code will generate an Event in the unit that will inform which User's PIN code was used. In this scenario, each User has their own PIN code(s). To configure this, go to Directory -> Users -> select the User -> User Codes:  PIN Code option - this PIN code will activate a Switch that is associated with Door (in Hardware -> Switches). Good for scenarios where each User needs their own PIN code and they need to control just one Switch. Switch codes - these codes are associated with respective Switch. User can control each Switch individually and those PIN codes are associated with this User only. The fields for codes here are greyed out if the respective Switch is not enabled. You can enable a Switch in Hardware -> Switches.    QR code To be able to use QR codes for authentication, you need to first enable this function, you can do so in Services -> Access Control -> Entry rules -> QR code reading:  To create a new QR code credential, go to Directory -> Users -> select a User -> User Codes:   PIN Code - this QR code is associated with a Switch that is assigned to Door, in Hardware -> Switches section  Switch codes - these codes are associated with respective Switch  You can enter numeric code with at least 10 digits and then click the button with QR symbol next to the field for entering the code. This will show you a QR code representing the digits entered:  You can download the image with QR code with the first button. Generate button will generate a new code. Apply Code will close the window and fill in the field for the code with the last generated code.   Virtual Card For more information about Virtual Card, please refer to this manual: Virtual Card ID – What is it for and how to set it up   Bluetooth access For more information about adding a bluetooth access credential, please refer to this manual: Bluetooth, 2N® Mobile Key - Opening door with Bluetooth   License Plate Recognition For more information about adding a car's license plate as an access credential, please refer to this manual:  License Plate Recognition (LPR) – how to configure it?     2N® Access Unit - Configuration backup - How to backup configuration and how to capture a trace?   Electric output - How to set electrical outputs on 2N Access Units

Question 5

Access credentials - How to add them to 2N 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. This FAQ describes how to add access credentials to 2N IP intercoms and Access Units. These scenarios can be used on following devices:  2N IP Verso  2N IP Vario  2N IP Base  2N IP Force  2N IP Style  2N Access Unit  2N Access Unit 2.0  2N Access Unit M    Access Credentials that can be used include:  RFID card access  Fingerprint access  PIN code access  1) The PIN code is associated with the respective Switch  2) The PIN code is associated with a User   QR code  Virtual Card  Bluetooth access  License Plate Recognition     RFID card access  Versions 2.50 (LTS) or earlier To add a new RFID card to the unit, you need to first find the ID of the card. Please put the card on the reader and then see the unit's log in Status -> Events. You will see the event "CardEntered", you need to see the "uid" parameter. Scroll to the right and copy it:   Now please go to Directory -> Users. You can either create a new user (1) or edit an existing one (2):    In User details, go to User Cards and paste the card ID here:  Now the RFID card access has been created.   Saving a new RFID card's ID can be also done with 2N USB RFID reader. A driver is needed for this device, more info is here. When the driver is installed, you can start scanning from the reader by clicking the button next to the field for Card ID.               Version 3.0 or later To add a new RFID card to the unit, you need to first find the ID of the card. Please put the card on the reader and then see the unit's log in System-> Event log.      You will see the event CardEntered, you need to see the uid:       Now please go to Directory. You can either create a new user (1) or edit an existing one (2):    In User details, go to User Cards and paste the card ID here:     Now the RFID card access has been created.   Saving a new RFID card's ID can be also done with 2N USB RFID reader. A driver is needed for this device, more info is here. When the driver is installed, you can start scanning from the reader by clicking the button next to the field for Card ID.           Fingerprint access  Versions 2.50 (LTS) or earlier To setup a fingerprint access, go to Directory -> Users -> select User -> User Fingerprints -> click on one of the highlighted buttons. Left one is for assignment via 2N External Fingerprint reader. Right one is for assignment via reader module mounted on a unit:  Now select the finger you want to use and click Scan Finger:    Now you can choose what this fingerprint will be used for by clicking on the highlighted button:    Now you need to scan it 3 times and save it:         Versions 3.0 and later To setup a fingerprint access, go to Directory -> Users -> select User -> Add credentials -> Fingerprints click on one of the highlighted buttons.        Now select the finger you want to use and click Scan Finger:          Now you need to scan it 3 times and save it:    Now you can choose what this fingerprint will be used for by clicking on the Confirm button:  By default, Open door option is selected. Silent Alarm option is for triggering a silent alarm when this finger is scanned. F1 and F2 Automation option is for use in Automation scenarios. After you set the correct function, click Confirm.      PIN code access There are several ways of adding a PIN code access to the device:      Versions 2.50 (LTS) or earlier 1) The PIN code is associated with the respective Switch In this case, when the correct PIN is entered, unit will not show which User activated the switch, it will just show that the correct PIN was entered and the switch was activated. You can set this in Hardware -> Switches -> (for example) Switch 1 -> Activation Codes. You will also need to make sure that Keypad, DTMF or Keypad only option is active. After you enter the code, click Save:  2) The PIN code is associated with a User In this case, using a PIN code will generate an Event in the unit that will inform which User's PIN code was used. In this scenario, each User has their own PIN code(s). To configure this, go to Directory -> Users -> select the User -> User Codes:  PIN Code option - this PIN code will activate a Switch that is associated with Door (in Hardware -> Digital Inputs). Good for scenarios where each User needs their own PIN code and they need to control just one Switch.Switch codes - these codes are associated with respective Switch. User can control each Switch individually and those PIN codes are associated with this User only. The fields for codes here are greyed out if the respective Switch is not enabled. You can enable a Switch in Hardware -> Switches.               Versions 3.0 or later  1) The PIN code is associated with the respective Switch In this case, when the correct PIN is entered, unit will not show which User activated the switch, it will just show that the correct PIN was entered and the switch was activated. You can set this in Integration -> Switches -> (for example) Switch 1 -> Activation Codes. You will also need to make sure that Keypad, DTMF  DTMF only or Keypad only option is active. After you enter the code, click Save:       2) The PIN code is associated with a User In this case, using a PIN code will generate an Event in the unit that will inform which User's PIN code was used. In this scenario, each User has their own PIN code(s).     To configure this, go to Directory -> Users -> select the User -> Add credentials -> PIN code/Switch code:      PIN Code option - this PIN code will activate a Switch that is associated with Door (in Integration -> Switches). Good for scenarios where each User needs their own PIN code and they need to control just one Switch.Switch codes - these codes are associated with respective Switch. User can control each Switch individually and those PIN codes are associated with this User only. The fields for codes here are greyed out if the respective Switch is not enabled. You can enable a Switch in Integration -> Switches.       QR code To be able to use QR codes for authentication, you need to first enable this function.     Versions 2.50 (LTS) or earlier You can do so in Services -> Access Control -> Entry rules -> QR code reading:  To create a new QR code credential, go to Directory -> Users -> select a User -> User Codes:   PIN Code - this QR code is associated with a Switch that is assigned to Door, in Hardware -> Digital Inputs section  Switch codes - these codes are associated with respective Switch  You can enter numeric code with at least 10 digits and then click the button with QR symbol next to the field for entering the code. This will show you a QR code representing the digits entered:         Versions 3.0 or later  You can do so in Access-> Access Rules -> Entry rules -> Settings -> QR code reading:        To create a new QR code credential, go to Directory -> Users -> select a User -> Add credentials -> PIN Code -> Generate QR Code:        PIN Code - this QR code is associated with a Switch that is assigned to Door, in Integration -> Switches section  Switch codes - these codes are associated with respective Switch    You can enter numeric code with at least 10 digits and then click the button with QR symbol next to the field for entering the code. This will show you a QR code representing the digits entered:     You can download the image with QR code with the Download the image button. Generate QR code button will generate a new code. Confirm will close the window and fill in the field for the code with the last generated code.    Virtual Card For more information about Virtual Card, please refer to this manual: Virtual Card ID – What is it for and how to set it up   Bluetooth access For more information about adding a Bluetooth access credential, please refer to this manual: Bluetooth, 2N® Mobile Key - Opening door with Bluetooth   License Plate Recognition For more information about adding a car's license plate as an access credential, please refer to this manual:  License Plate Recognition (LPR) – how to configure it?     Access Commander - Which devices can be connected?  Alcatel OmniPCX Enterprise (OXE) - How to set it up with 2N® IP Intercom

Question 6

Access logs of 2N Mobile Key

Accepted Answer

You can see access logs within your 2N Mobile Key application. Feature is available for both Android / iOS platforms. You can check the access logs in Settings - Access logs.  You can clear all logs and you can also remove individual log entries by swipe.   You can see the following info in the access logs:   Device name  Operation mode (Touch / tap)  Unlocking status (opened, failed - if failed, then why it is showed why)  Multiple authentication info      You can delete or mark access log as unintended / intended opening while you swipe its entry to half of the screen from right to left      Access Logs can be also exported and are part of report form.

Question 7

Auto Provisioning via TFTP

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.    Requirements    Firmware 2.30 and above  Enhanced Integration license or Gold. Up to version 2.34 (inclusive) you need the license/feature or Gold (if it includes it), and from version 2.35 onwards they are part of the Gold license.  TFTP server (e.g. SolarWinds TFTP)         In this document, we will show how to set & schedule firmware and configuration uploading to your intercom via TFTP. In our scenario, we will use the FREE software SolarWinds, but you can choose any TFTP server you like.     TFTP server configuration       SolarWinds TFTP server The configuration of the SolarWinds TFTP is pretty straightforward, you don't even need to do any special configuration and it will work right away.      But you can still make some further configuration:  You can change the location of the root directory (from where the configuration and firmware will be uploaded)    In the root directory, you can create folders for better organisation    You can also improve the security with changing the transfer mode to send only and allow a specific IP range                    Firewall For everything to work properly, you need to create a new inbound rule in your firewall:    Select a rule type "Port"    Select UDP protocol and specify a port 69  Once you create a rule, the TFTP server should be ready and the intercom should be able to connect successfully.                       2N IP Intercom configuration    First of all, you need to find the IP address of your PC, you can use a command line and type "ipconfig":    After you successfully found out your IP address you have to fill it into the IP Intercom in this format: tftp://ip_address:69If you've made folders in your root directory, you need to specify the correct location, otherwise, leave the "/" by default.    At this stage, you can also schedule, how often the intercom will check for any updates. The intercom can check for updates:  Manually  Daily  Weekly  Monthly                   Firmware     You cannot downgrade via TFTP, the update always results with a note "Firmware is up to date"   To upload the firmware to the units, the file name needs to be in the correct format (check the formats below). After you correctly re-name the file you need to save it to the correct directory (in our case C:\TFTP-Root\Firmware). The latest firmware can be found on our site: https://www.2n.com/en_GB/support/documents/firmware      File formats         MODEL  ID  EXAMPLE  2N IP Vario  hipv  hipv-firmware.bin  2N IP / LTE Verso  hipve  hipve-firmware.bin  2N IP Solo  hipso  hipso-firmware.bin  2N IP Base  hipba  hipba-firmware.bin  2N IP Force  hipf  hipf-firmware.bin  2N IP Safety  hipsf  hipsf-firmware.bin  2N IP Video Kit  hipvk  hipvk-firmware.bin  2N IP Audio Kit  hipak  hipak-firmware.bin  2N SIP Speaker Horn  sassh  sassh-firmware.bin  2N SIP Speaker  ss  ss-firmware.bin  2N SIP Audio Converter  sac  sac-firmware.bin                                   Configuration    To upload the configuration to the units, the file name needs to be in the correct format (check the formats below). After you correctly re-name the file you need to save it to the correct directory (in our case C:\TFTP-Root\Configuration). The backup configuration file must be sourced from the device itself, here is how to make a back-up: 2N IP Intercoms - Diagnostics and Troubleshooting If you want to have a specific configuration for one intercom you will have to substitute the "common" with a MAC address in this format: MODEL-XX-XX-XX-XX-XX-XX.xml      File formats     MODEL  ID  EXAMPLE  2N IP Vario  hipv  hipv-common.xml  2N IP / LTE Verso  hipve  hipve-common.xml  2N IP Solo  hipso  hipso-common.xml  2N IP Base  hipba  hipba-common.xml  2N IP Force  hipf  hipf-common.xml  2N IP Safety  hipsf  hipsf-common.xml  2N IP Video Kit  hipvk  hipvk-common.xml  2N IP Audio Kit  hipak  hipak-common.xml  2N SIP Speaker Horn  sassh  sassh-common.xml  2N SIP Speaker  ss  ss-common.xml  2N SIP Audio Converter  sac  sac-common.xml

Question 8

Calling locally between 2N IP intercom and 2N IP Phone D7A

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 explains how to make local calls and open door between 2N IP intercom and 2N IP Phone D7A.   In the 2N IP intercom's web interface, go to Directory -> Users -> Add User.Name the User and enter the phone number. The phone number is in format sip:IP_address, where IP address is the local IP address of the D7A phone. Save the settings afterwards.Go to Calling -> SIP1 -> make sure the SIP1 account is enabled. Do not change any other parameters here.Go to Calling -> General Settings -> set the Answering Mode for SIP1 to Automatic or Manual pickup, depending on how you wish to manage the incoming calls to the intercom.Now go to Hardware -> Switches ->Switch 1 -> Activation codes -> copy the code, this code will be used in the D7A's settings for door opening.   LOCAL SIP CALLS: In firmware 150.87.57.3, local calls are disabled by default. If you updated your D7A from an earlier version, or if you are trying to set up SIP calls on a local network, you need to enable IP Calls In and disable Accept SIP Trusted Server in Features > General Information.  To set the door opening button on the In D7A's ongoing call display, go to Features -> Door Phone -> name the Door Phone -> enter 2N IP intercom's IP address into the Phone Number field -> enter the unlock code copied from the intercom's web interface. It is needed to add star (*) behinf the code. In this example it would be "00*". To create a button for calling the intercom on the D7A's display, go to Dsskey -> Line Key -> Line Key1 -> enter the Intercom's IP address in Value and name it in Label. Leave Line as Auto.

Question 9

Card reader gets stuck

Accepted Answer

This FAQ refers to situation when the card reader (typically 125kHz version, but generally also 13.56MHz) is placed in the intercom and does not react to cards presented, while the rest of the intecom works OK. In any case please make sure you have latest firmware uploaded to the intercom. If the reboot does not help.  Is the card reader module connected properly to the intercom? Can you see the card reader module in Extenders, do you see card reader related menus? For example with Vario or Force, if card reader is connected, you see its electrical outputs in Switches.  Are you using correct cards? A 125kHz card is invisible for 13.56MHz card reader and vice versa. Try with a similar card reader whether you are using correct type of card. Also 125kHz HID Proximity cards need correct settings of HID Prox types as there are multiple variations.  Can you see card events in the Status part of the web interface or syslog? If so, then the card reader actually works, but there might be a problem with signalisation, such as volume turned all the way down.  If the reboot helps, but after some hours the card reader is stuck again, sometimes even after first lock activation.  Interference from another reader - Check if there is any other card reader of the same frequency close by. Especially with 125kHz readers, we do not recommend installing readers closer than 50cm from each other - they might be interfering. If the installation requires multiple readers to be so close, try to shield them from each other using metal back plates or wire grid.  Impulse from the lock - after the lock is deactivated, coil in the lock generates an discharge impulse which is closed via the intercoms output - this can interfere with the card reader.  Rearrange the cables from the lock. Try to lead them as far as possible from the card reader - if the cables are too long, do not store them in the intecom, either make them shorter or place them in the wall box.  Use low consumption locks - they generate smaller discharge peak.  Add a diode to the lock connector with polarity reverse to the door lock power supply from the intercoms output. The diode must not short-circuit the output of the intercom. Adding the diode should not affect the normal operation of the lock, but the discharge is discharged via diode, so it does not get into the intercom at all. The diode should be placed as close as possible to the door lock itself, ideally directly on the connector on the door lock. Diode should be min 1A/1000V, for example types 1N4007 or 1N5408

Question 10

Communication between 2N Indoor Compact and 2N IP intercom via Device ID

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 FAQ describes advantages of communication between 2N Indoor Compact and 2N IP intercom via Device ID and how to configure it properly.How to communicate via IP address is described in this FAQ: Setting up calls from and to 2N IP intercomThe aim of this page is to introduce how to communicate via 2N IP intercom’s Device ID.   Recommendation - use the latest firmware   We recommend using the latest firmware in 2N Indoor Compact and also 2N IP intercoms to ensure that all functions are available. 2N IP intercoms - Firmware upgrade  2N Indoor Compact with the latest firmware - here  2N IP intercom with the latest firmware - here  no license is needed  devices are in the same network, multicast is allowed in the network          Why to use 2N IP intercom’s Device ID in 2N Indoor Compacts’s configuration Communication via Device ID is a proprietary way and thanks to that you can activate 2N IP intercom's switch by 2N Indoor Compact when there is no call.  How to configure a 2N IP intercom?   Setup Intercom's Device ID Go to 2N IP intercom’s web management - section Calling - Local Calls and set the Device ID.    Setup Local Call receiving mode Go to 2N IP Intercom's web management - section Calling - General Settings and there you set   Local Call Receiving Mode  Always Busy - no calls allowed  Manual Pickup - pickup call manually by press of a button, you must define which button picks the call (picture below)  Automatic - Intercom automatically picks up the call     Setup Intercom's Switch code Go to 2N IP Intercom's web management - section Hardware - Switches and set the Switch code you want to use for activating the switch from 2N Indoor Compact  Make sure that the electric opener/lock is always connected to the intercom's 12V output using a security relay to make the installation safe. The motherboard relay is used for switching lights or other peripherals that do not have to be secured. It is always recommended that the 2N Security Relay (Part No. 9159010) is used for increased security.   How to configure a 2N Indoor Compact? Go to 2N Indoor Compacts’s web management - section Directory - Devices click on Find device and choose the device you want to add.    After you have added the device, the Device Name and Phone Number are automatically filled.You may then set your DTMF codes that you want to send to the intercom during the call, you can set up to 3. When you have more than 1 code set, a press of a padlock button during a call will show other 2 codes that you can choose from Unlock Button Function  Button 1,2,3 Code: Defines DTMF code to be sent to the 2N IP intercom during call    If no Button 1,2,3 Code is defined than Default Unlock Code will be used for unlocking. This code is also used to unlock the device outside the call.

Question 11

Communication via Device ID of 2N IP intercom

Accepted Answer

This FAQ describes advantages of communication between 2N Indoor Talk and 2N IP intercom via Device ID and how to configure it properly.How to communicate via IP address is described in this FAQ: Setting up calls from / to 2N IP intercomsThe aim of this page is to introduce how to communicate via 2N IP intercom´s Device ID.  Requirements   We strongly recommend using the latest Firmware  2N Indoor Talk with the latest firmware - here  2N IP intercom with the latest firmware - here  no license is needed  devices are in the same network, multicast is allowed in the network     Why to use 2N IP intercom´s Device ID in 2N Indoor Talk´s configuration Communication via Device ID is a proprietary way and thanks to that you can activate 2N IP intercom´s switch by 2N Indoor Talk when there is no call.   Configuration of 2N IP intercom  Setup Intercom's Device ID Go to 2N IP intercom´s web management - section Calling - Local Calls and set the Device ID.    Setup Local Call receiving mode Go to 2N IP Intercom's web management - section Calling - General Settings and there you set   Local Call Receiving Mode  Always Busy - no calls allowed  Manual Pickup - pickup call manually by press of a button, you must define which button picks the call (picture below)  Automatic - Intercom automatically picks up the call     Setup Intercom's Switch code Go to 2N IP Intercom's web management - section Hardware - Switches and set the Switch code you want to use for activating the switch from 2N Indoor Talk  Make sure that the electric opener/lock is always connected to the intercom's 12V output using a security relay to make the installation safe. The motherboard relay is used for switching lights or other peripherals that do not have to be secured. It is always recommended that the 2N Security Relay (Part No. 9159010) is used for increased security.        Configuration of 2N Indoor Talk Go to 2N Indoor Talk´s web management - section Directory - Devices click on Search registered devices and choose the device you want to add.   After you have added the device the Device Name and Phone Number are automatically filled.  You can call up to 2 devices from 2N Indoor Talk.  Start call with a short/long press: Choose whether you want to call this user by a short or a long press of a call button on the 2N Indoor Talk  Code after short press: Defines a DTMF code sent to the intercom during or outside the call  Code after long press: Defines a DTMF code sent to the intercom only during the call by long pressing the unlock button   If no Button 1,2,3 Code is defined than Default Unlock Code will be used for unlocking. This code is also used to unlock the device outside the call.

Question 12

Configuring email notification on 2N indoor Touch

Accepted Answer

This FAQ will explain how to configure the email client on 2N Indoor Touch unit. This email notification could be helpful in case of a missed call from any 2N intercom (except 2N IP Base and 2N IP Uni) because the notification can contain the picture of the person who has been trying to reach you.    2N Intercom SMTP settings   The first step is to configure the SMTP client on the intercom side like on the following figure:   Figure 1: SMTP settings        You can make a test and verify if the setting of the SMTP service is correct by using Email service diagnostics on the same section of the page Services->E-mail->SMTP->Email sending diagnostics.        In this example let's assume that i have assigned the user under the quick dial button of the intercom and i would like to receive the e-mail notification with the picture of the person who has been trying to call me. In this case it is necessary to configure the e-mail address to that specific quick dial button.    Figure 2: user E-mail setting      Settings when the email has to be sent can be found in the section: Services->E-mail->E-mail on call. For further details please read the following manual page:  https://wiki.2n.com/hip/conf/latest/en/5-konfigurace-interkomu/5-4-sluzby/5-4-3-e-mail           2N Indoor Touch SMTP client settings   To be able to access the E-mail client on the 2N Indoor Touch, you have to change the application on the main screen. This can be done in two way:  Via web interface (Figure 3)  Physically using the touchscreen (figure 4)                Figure 3: Configuration of the main screen via web interface   To be able to change the main screen layout and adjust the application shown there, you have to enter the settings.  Default password is: 2n.     Figure 4: Configuration of the main screen via touchscreen   Once the previous step is done, you can enter the e-mail application and login into your email account and receive the email notifications based on your setting.              Figure 5: E-mail client

Question 13

Configuring Wildix VoIP PBX with 2N IP Intercom

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 2N IP Intercom can be integrated into a Wildix VoIP PBX which is a SIP Protocol based IP PBX. 2N IP Intercom operates as an SIP subscriber and can stream its video to the IP telephone. No additional equipment is needed for full integration of the door intercom in the telecom system . Tested models: PBX WGW08 - WGW16 - WGW40 - WGW90 - WGW250 - WGW500 - WGW1000 - WGW5000 Hotel PBX WGWH20 - WGWH50 - WGWH100 - WGWH250 - WGWH500 - WGWH1000 Tested versions:  WMS 2.0  WMS 3.0  Compatibility test:  Audio call  Video call  DTMF transfer  1. As a very first step configure new user in Wildix PBX. Select the PBX IP address from your WEB browser and go to section "User" (Utenti) and add a new user.   2. Click “+” and fill the extension number (Interno) and description (Nome).    3. Select the dialplan > TAB Dialplan.   At the end of this procedure and after the configuration of 2N IP Intercom (step n. 4) you can see the status of this new user as showed in the picture below:   The green led shows that 2N IP Intercom is registered on PBX. If you place a mouse on the "user", you will see the information about it: name, IP address and transport type. 4.From 2N IP Intercom side go to the section Calling -> SIP1 -> Configuration. Fill in "User ID" and "Password" which matches to the "ID" and "Password" set in the Wildix side, and “Domain”, “Proxy Address” and “Registrar Address”. See below:  To verify that you have successfully registered 2N IP Intercom terminal into Wildix PBX side, go to the section Services -> Phone Status in the 2N IP Intercom.

Question 14

Connecting WaveStore VMS to 2N IP Intercom

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.   WaveStore VMS is the linux based platform for video monitoring. WaveStore is distributed as the whole operating system in the .iso file. Tested Wavestore software was in version 5.48.33 with IP Intercom firmware version 2.11.1.  How to configure 2N IP intercom? First notice is about licences to IP intercom. WaveStore needs ONVIF technology and RTSP server support from the intercom side. Both these services are enabled by Enhanced Video licence (order number 9137906). In section Services -> Streaming -> ONVIF/RTSP enable RTSP Server. The default user is already created as admin/2n (Username/Password). Example of the setting this service in the picture bellow.  Following picture represents example of RTSP server settings.    How to setup WaveStore VMS system? After the WaveStore server installation you can connect directly on the server via WaveView software as the part of basic configuration. To enter the setup menu you need to login as the default user: install/a (username/password) and change the View to Setup. As the first step is recommended to configure the network according to local network or use the DHCP server. When the network is properly installed you can connect remotely to this server via the same software. Please keep in mind, after any changes in the setting, allways click on SAVE icon.  New device can be added in Devices section by a simple click on the button: Discover ONVIF Cameras or add Camera manually. Following window with discovered camera will appear. Select the camera in our case it will be 2N IP Intercom and click on the Add IP Capture button. Login screen to the particular camera appears, insert the login parameters.  Now you can see 2N IP Intercom in the Device tree. You need to change type to RTSP instead of ONVIF. In network capture setting set Camera type to Custom. Please check colomn IP address of the camera (whole address without port specification) and mark the option use custom port and fill 554.  After this setting you can see list of paired devices in the table Device Tree. If the camera should be viewable by a common user it has to be enabled. Users can be managed in section Users. The default password "a" is attached to every new created user after first login it will appear the window for changing this password.  So now you can see the video stream from 2N IP Intercom. If you also want to hear the audio you have to add audio track according to picture bellow (blue rectangle).  New Audio track will appear in Device tree under particular device. You have to enable AUDIO and audio Track too, according to pictures bellow.   Last thing is to pair Video and Audio tracks. This can be done in video track settings by a selecting one of Audio link.  After all these settings you can see Video and hear the audio from 2N IP Intercom also from the Main page.

Question 15

Connection of 2 devices to one lock

Accepted Answer

Connection of two 2N devices to one lock using potential outputs  Graphic  Info: To prevent damaging the unit, please install diodes to both power supplies that are connected to the same terminal on the lock.     Schematic  Info: To prevent damaging the unit, please install diodes to both power supplies that are connected to the same terminal on the lock.     Connection of two 2N devices to one lock using non-potential relays  Graphic  Info: For the lock connection, we highly recommend using the output with installed 2N Security Relay (Part No. 9159010) for enhanced installation security.    Schematic  Info: For the lock connection, we highly recommend using the output with installed 2N Security Relay (Part No. 9159010) for enhanced installation security.   Connection of one 2N device and 3rd party controller using potential outputs  Graphic  Info: To prevent damaging the unit, please install diodes to both power supplies that are connected to the same terminal on the lock.    Schematic  Info: To prevent damaging the unit, please install diodes to both power supplies that are connected to the same terminal on the lock.     Date of release: 27. 5. 2021   Used devices in manual: 2N IP Verso (firmware version 2.32)2N Access Unit 2.0 (firmware version 2.32) List of compatible Hardware: 2N IP Verso2N IP Vario2N IP Force2N IP Safety2N IP Base2N IP Solo2N Access Unit 1.0 & 2.02N Access Unit M

Question 16

Easy unlock and call hang in one step

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 Configuration Note: The Gold License is required.    In our example, the intercom has IP Address 192.168.50.20.   In the intercom's web interface, go to Hardware -> Switches  -> Switch1 and type to the Switch-On Command field:  192.168.50.20/api/call/hangup?session=1   Now, it is needed to setup the security for this feature. There are 2 ways to go on. Unsecured: Please, go to Services  -> HTTP API -> Services, put Connection Type to Unsecure (TCP) and Authentication to None for Phone/Call API.  Secure - password protected: Please, go to Services -> HTTP API -> Services, setup Connection Type to Unsecure (TCP) and Authentication to Digest for Phone/Call API.  Please, go to Services -> HTTP API -> Account 1, enable the account and create your credentials (User Name, Password) and check Monitoring and Control check boxes for Phone/Call Access.  Return to the Hardware -> Switches -> Switch1 and use the credentials for the HTTP Command.  Now it is ready to use unlocking and hanging up procedure in one step.

Question 17

Homebridge plugin for 2N intercoms

Accepted Answer

The Homebridge 2N Intercom plugin enables seamless integration of 2N intercoms with Apple HomeKit via Homebridge and our API, allowing users to control doors, stream live video, and receive doorbell notifications.   Prerequisites  2N intercom with the latest firmwareGOLD license for 2N intercom in case of using RTSP streamEnabled HTTP API "Switch"/"Call"/"Camera" service and created a dedicated account with proper rights.More information in our HTTP API manual.Enabled RTSP Server (if needed) and created a dedicated account for it.More information in our FAQ article. How to define the plugin Please follow the instructions in this plugin page.

Question 18

How to control 2N Indoor Touch via Automation of 2N IP intercom

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   This FAQ describes how to control 2N Indoor Touch with HTTP API with 2N IP intercom. On the side of the 2N Indoor Touch HTTP API license is needed, ordering number is 91378395. On the side of the intercom you will need Enhanced integration license as Automation will be used, ordering number is 9137907. Below you will find screenshots of configuration with brief description of how to configure such function. Scenarios below serves mainly as a demonstration of possibilities given by HTTP API and examples of how to control your touch panel in this way. You can easily adjust them or use different ones with help from the HTTP API manual here.         How to control relay/output of 2N Indoor Touch via 2N IP Mobile This function enables you to control the outputs of your touch panel via the native 2N application called 2N IP Mobile. The output will be triggered by one of the lock buttons in the application showed below. All four locks will appear after you hold the button lock in the preview of a particular intercom. Those four locks are representing four switches in the 2N IP intercom web interface.  For our scenario we chose button one which is representing Switch 1. This switch can be configured in section "Hardware->Switches->Switch 1". Because these switches also serve to control the outputs of the intercom itself, you can optionally set parameter "Controlled Output" to "None". This will ensure that no output of the intercom will be triggered together with an output of the touch panel once the Switch 1 will be triggered.   Now we define the HTTP command which the intercom sends to itself once the lock button on the touch panel will be pressed. This HTTP command will be used in the next step, where the Automation function will be created. This command has to be entered in the field "Switch-On Command" and URL looks like this:    http://192.168.50.157/enu/trigger/test    Part "http://192.168.50.157/enu/trigger/" is mandatory. The string at the end (test) can be replaced by a custom one. The IP address has to be replaced by IP address of your intercom.  In the next step you need to create automation function to control 2N Indoor Touch via its HTTP API. To create an Automation scenario, click on edit of one of the functions as shown on the picture below.Then create the scenario by dragging-and-dropping and connecting the objects from the left side of the screen. The description of the function is below.  Event.HttpTrigger Name=Test - This Event serves to detect the HTTP command you created in the previous step. If you chose a custom string instead of Test, then please fill the right one for "Name="  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/login?login=Admin&password=2n; Event=1 - This object ensures, that once the HTTP command from the HttpTrigger is received, then the intercom will send the HTTP command with authentication credentials to create a session with the touch panel. The IP address has to be replaced by actual IP address of your 2N Indoor Touch.  Event.Delay StartEvent=1; Delay=300mss - Delay on the third row ensures that session is opened properly, before intercom will send next HTTP command. Hence that the delay starts as soon as the HttpTrigger receives the http command.  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/gpio?action=set&name=relay1&type=value&value=1;Event=3 - This command will trigger relay1 of the touch panel after the delay from the Delay object and will set it to "value=1" (at the end of URL). Values in the URL are described in HTTP manual here.  Event.Delay StartEvent=3; Delay=3s - After this delay another command will be sent and the relay will be set back to 0. So this delay defines, for how long the relay will be closed.  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/gpio?action=set&name=relay1&type=value&value=0;Event=5 - This command will open the relay after the delay from the Delay object. You can see that the command is exactly the same as the command from the 4th row. Except for the value at the end which was changed to "value=0".      Export for sandbox style automation: click to download   Last step will be to enable Unsecure HTTP API for your 2N Indoor Touch. You will go to the web interface of your Indoor Touch then to the Device Section and finally to the System Administration, then check the Insecure HTTP Access like in the picture below.      How to minimize 2N IP Mobile once call is ended This feature is achieved by automation function only, so you don't need to configure switches like in previous scenarios. This function ensures, that everytime a call between the 2N Indoor Touch and the 2N IP intercom is terminated, the application is minimized. How to create such a function is described below:  Event.CallStateChanged State=terminated - This Event detects the end of a call and triggers the Action.  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/login?login=Admin&password=2n; Event=1 - This row ensures, that once the HTTP command from the CallStateChanged object is received, then the intercom will send HTTP command with the authentication credentials to create a session with the touch panel. The IP address has to be replaced by actual IP address of your 2N Indoor Touch.  Event.Delay StartEvent=1; Delay=300ms - Delay ensures that the session is opened properly, before the intercom will send the next HTTP command.  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/hipm?action=minimize; Event=3 - After the Delay ends, the intercom sends the HTTP command which will minimize the app. Description of this command can be found here.     How to restart 2N Indoor Touch via 2N IP Mobile Now you will learn how to achieve a restart of the 2N Indoor Touch by pressing the lock button in the app again. As the first three pictures are basically identical for this scenario, please refer to the previous one. We chose to use Switch 2 for this scenario represented by lock 2 in the app. You need to go to section "Hardware->Switches->Switch 2". If you want to disable controlled output on the intercom again, then the procedure is exactly the same as in previous step. You need to change parameter "Controlled Output" to "None". Then you need to fill "Switch-On Command" again. We chose this URL for this scenario:   http://192.168.50.157/enu/trigger/test1   Part "http://192.168.50.157/enu/trigger/" is mandatory. String at the end (test1) can be replaced by a custom one. The IP address has to be replaced by IP address of your intercom. Now you need to create the automation function. Whole function is described below:  Event.HttpTrigger Name=Test1 - This Event serves to detect the HTTP command you created in the previous step. If you chose a custom string instead of Test1, then please fill the right one.  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/login?login=Admin&password=2n; Event=1 - This row ensures, that once the Event from the first row is detected, then the intercom will send HTTP command with authentication credentials to create a session with the touch panel. The IP address has to be replaced by actual IP address of your 2N Indoor Touch.  Event.Delay StartEvent=1; Delay=300ms - Delay on the third row ensures that session is opened properly, before intercom will send next HTTP command.  Action.SendHttpRequest uri=https://192.168.50.236/api/v1/maintenance/resetdevice; Event=3 - Once the Delay from the 3rd row ends, intercom sends HTTP command to restart the 2N Indoor Touch. The IP address has to be replaced by the IP address of your touch panel. Description of this command can be found in manual here.

Question 19

How to provide all information to effectively resolve a technical issue with 2N OS 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.   In case you have found some issue with 2N OS device, please report it to Technical Support. If you do not have access information, contact your account manager.Or you can report your issue by creating a ticket - here. The reported issue should contain the following information:  Describe us the issue in a close detail, so that we will be able to replicate the behavior at 2N Tech Support.   Send us the description of the LAN topology, NATs, IP addresses, etc.    If your issue can be clearly visible or heard e.g. LED blinking or bad sound quality, please take a picture or record a video (e.g. on a phone) and send us this behavior.   You can attach it to the e-mail or upload it to e.g. WeTransfer, Dropbox, Google Drive and send us the download link.    Know the Device Information The serial number and the current FW version of your 2N OS device.It is highly recommended to use always the newest FW version available on 2N web page - here  Backup the Configuration Send us the current configuration of the device - in the pictures below there is shown how to do that.   Capture the Wireshark trace Catch the Wireshark trace on 2N OS device. Here first of all activate the capturing by "Start" button, make a call and deactivate the capturing by "Stop" button. Then download hiptrace.pcap file and send it to the support. Because the buffer for trace is limited, it is really necessary to start the trace right before you will make a test call.    Capture an internal Syslog on 2N OS device.   If 2N Tech support asks you for a Syslog they usually want the setting that is shown in the picture below. Unlike in Wireshark trace the buffer is not limited by size but time. Please set the Required Saving Time + Severity level according to 2N Tech support needs.   After setting press the "Start" button and the Syslog will automatically stop after the time you defined in  Required Saving Time, then save the syslog.txt file and send it to us.  6. Capture an external Syslog on 2N OS device.     The external syslog is often use to capture syslog messages immediately after rebooting the device which often can't be done by internal Syslog.    Please fill the Severity Level according to 2N Tech support needs. You will need a syslog server where the messages from the device will be sent.    Set the Server Address in our example we use 192.168.1.15 - IP Address of a PC where SyslogWatcher is installed   7. Using SyslogWatcher - download here       Start the server - it will take a few seconds until you see any messages  Stop server - press after you are done with capturingExport - press this button to export messages to fileExport Settings - Choose the time from/to according to what 2N Tech support demands (1h, 24h)Custom files (CSV/XML/TXT/JSON/etc.) - type of file  Export folder - choose path to save the fileFilename - name of the file (in default it is date of Syslog capturing) -> export the file with .txt suffix and send it to us

Question 20

How to send/receive separate multicast streams on 2N IP Intercoms via 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.   Every 2N IP Intercom can receive/send one multicast stream by default with the basic license. If you wish to receive/send more multicast streams (up to 5 different multicast IP addresses or ports) then you need Enhanced integration license (up to v2.35) or Gold license (v2.35 onwards) which enables you to configure this feature via Automation. It is very useful if you have for example a building with 2 separated floors – 2N IP Intercoms on the 1st floor are listening on multicast IP address 224.10.10.1 and port 10 000 (represented by 2N IP Video Kit in the example below), then 2N IP Intercoms on the 2nd floor are listening on 224.10.10.2 and port 10 000 (represented by 2N IP Safety). Once you press the button on any of these intercoms on the 1st floor you will make an announcement to all other intercoms on the 1st floor. The same will happen once you press the button on any of the intercoms on the 2nd floor – you will multicast to all intercoms on the 2nd floor. Once you finish your announcement you press the button again and the multicast stream will finish — but let's imagine that you also need a few intercoms that are able to make an announcement to the 1st floor as well as the 2nd floor and also receive announcements from both these floors. In this case you will need an intercom with two buttons at least (or with a keypad).  How to configure intercoms (2N IP Verso) on the 1st floor? As mentioned previously all intercoms should be able to send multicast traffic once the quick dial button is pressed and also receive multicast if any other intercom is transmitting. Therefore we will set two functions in the section "Services -> Automation" for each intercom. Send multicast: Once you press a specific quick dial button on any of intercoms from the 1st floor (it will be 2N IP Video Kit in our example) then you engage conversation with all intercoms on this floor. Complete configuration of “Function 1” is shown in the picture below – when the first quick dial button is pressed for the first time, condition on the 2nd row is met and it will trigger actions on the 4th and 5th rows, i.e. 2N IP Video Kit sends specific multicast request (command=group01) to all other intercoms and starts sending multicast traffic. Based on the request these intercoms open a multicast channel and are able to receive multicast traffic (on IP address 224.10.10.1 and port 10 000). Once you finish your announcement then you press the first quick dial button again to stop the multicast sending. In this case 2N IP Video Kit sends another multicast command to all the intercoms (command=stopgroup01) and stops sending the multicast stream. Note: Sometimes it is also very useful to check somehow if the first quick dial was pressed for the first time (to establish a multicast session) or for the second time (to finish a multicast session). This indication can be configured with some of our intercoms – you can use LED diode or a button of 2N IP Safety which is always shining (idle time – no multicast stream initiated from this intercom) and once you press the button for the first time (to begin multicast a session) then this LED or button starts blinking (example below – 250ms shining and 250ms not).   Receive multicast: All other intercoms on the 1st floor have to be configured that once they receive a specific multicast request (group01 in our example) they will activate a channel and start listening on a specific multicast IP address and port. After that, once the announcement from the selected intercom is finished, then another multicast request is received (stopgroup01) and multicast channel is closed.       How to configure intercoms (2N IP Safety) on the 2nd floor? Configuration of intercoms on the 2nd floor will be almost the same as shown previously (1st floor) but in this case all intercoms send (and listen) multicast stream to IP address 224.10.10.2 and port 10 000. Also multicast request which activates / deactivates the channel was changed to "group02" for activation and to "stopgroup02" for deactivation. Send multicast:      Receive multicast:        How to configure 2N IP Audio Kit which can communicate with intercoms on the 1st floor as well as on the 2nd floor? Configuration of these selected intercoms which can send multicast traffic to the 1st floor as well as to the 2nd floor is a combination of two previous configurations. But keep in mind that these intercoms need to have at least 2 quick dial buttons (or a keypad). In this case you have to configure three functions in the Automation section. Function 1 is absolutely the same as shown for 2N IP Video Kit (1st floor intercom), Function 2 is the same as for 2N IP Safety (2nd floor intercom) and Function 3 ensures that you can receive multicast from 1st floor intercoms as well as from the 2nd floor intercoms. Send multicast (Send_To 1st Floor - downloadable here):    (Send_To 2nd Floor - downloadable here):          Receive multicast from different floors (Receive from 1st + 2nd Floor - downloadable here):          Note: All commands used in the Automation section are thoroughly described in our Automation manual altogether with corresponding examples. The manual is available on our web page: Automation Manual                   More information:        2N IP Intercoms (official 2N web)

Question 21

How to use Group Authentication / Access key in communication between 2N IP Intercoms and 2N Indoor Touch

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 2N IP Mobile application in 2N Indoor Touch can communicate with all 2N IP Intercoms in the local network (and vice versa) by default. In order to increase basic security of the installation for certain scenarios we have implemented an optional access authentication for the 2N IP Mobile application in 2N IP Intercoms by an adjustable Access Key. Thanks to the Access key settings, only selected mobile applications with the key set in the Group Authentication field of the application can detect the intercom connected in the same network.   2N IP intercom FW & license   It is strongly recommended to use the latest FW version on 2N IP Intercoms - available here or via the automatic update feature. The Group Authentication/Access key feature does not require any additional license for the 2N IP Intercom.        Navigate to the section "Calling -> Local Calls -> Configuration" and fill in the "Access Key" field in Connection to answering units to enable authentication for the 2N IP Mobile application as shown in the picture below. You can add up to 3 Access Keys.   How to set 2N Indoor Touch? Once the 2N Indoor Touch is connected to the local network and powered (over PoE or using an external 12V DC/2A power supply) it will boot up and you see its initial screen (launcher). By clicking on the 2N IP Mobile application icon in the right upper corner you can open it and access its settings.  To be able to detect and add a key protected 2N IP Intercom in the local network, you need to set the equal Access Key in the application first. Go to the section "Settings - 2N Helios IP Group Authentication" and set the same key as set on the intercom side, see the pictures below.   The application automatically scans your LAN network and searches for all connected 2N IP Intercoms with the equal Access Key/Group Authentication identification.You can easily add them in the "Devices" section by clicking on the "+" button.   By clicking on the specific row in the LAN devices list you can add selected intercoms only or by clicking on the checkbox in the right upper corner you can add all of them at once.   By clicking on the confirmation button  you have just added the desired local devices to the list and the application is ready to call.

Question 22

HTTP API - Configuration upload

Accepted Answer

You can edit various configurations in the 2N IP Intercoms via HTTP API commands:  Configuration backupRTSP Configuration example H.264 parametersConfiguration ExampleHTTP API Test Tool The HTTP API was designed for controling selected 2N IP Intercom functions via the HTTP protocol. It enables 2N IP Intercoms to be integrated easily with third party products, such as home automation, security and monitoring systems.Below is an example how you can change configuration  parameters of the 2N IP Intercom (video framerate/resolution) and upload them into the 2N IP Intercom via HTTP API. You can find a complete manual on this page: 2N IP Intercom HTTP API manual Once you download the config backup from the intercom, you can open it in Notepad++ or any other text editor (or Web Browser).  Configuration backup After downloading the config.xml file and opening it, you can see the configuration:  You can collapse (1) and expand (2) each category of the configuration file:     RTSP Configuration example In the picture you can see the section for RTSP:   For the H.264 codec, you can see:  - 1 - 3 - 4   These numbers correspond with the settings on 2N IP Intercoms — the number means always the position of the parameter, as shown on this screenshot above.  H.264 parameters   Video Framerate: 30 fps - (number 1 in the config file)      Video Resolution: VGA - (number 3 in the config file)    Video Bitrate: 512 kbps - (number 4 in the config file)      The logic for those parameters is always the same - always start from 0.  For example, Video Resolution in IP Vario with Camera: 0 - QCIF (176x144)1 - QVGA (320x240)2 - CIF (352x288)3 - VGA (640x480)   The /api/config function helps you upload or download the device configuration. The function is part of the System section and the user must be assigned the System Control privilege for authentication if required. The function is available with the Enhanced Integration licence (up to v2.35) or included in the basic installation (v2.35 onwards). Use the PUT method for configuration upload. The reply is in the application/json format and includes no other parameters.  Configuration Example If the command is sent successfully, following line will be returned: PUT /api/config{ "success" : true} HTTP API Test Tool  The put request can look like this  https://192.168.50.163/api/config  where the 192.168.50.163 is the IP address of the intercom.You can try this by using the HTTP API test tool available on https://2N_IP_Intercom_address/apitest.html     The example is in the attached picture, you need to upload the xml file with the configuration:

Question 23

Induction loop for 2N IP Intercoms and Answering units

Accepted Answer

Induction loop is a part of sound system installations for hearing impaired persons that are equipped with a special hearing aid capable of receiving reproduced sound via a magnetic field receiver. The system is defined by the IEC 60118-4 standard. See which our induction loop you can use in which our IP Intercom or Answering unit.   Prerequisites Supported 2N IP Intercom or 2N Answering unit with the latest firmware,no additional license is required.2N Induction loop according to selected 2N IP Intercom or 2N Answering unit:9155041 9159050 9159054 2N Clip optionally integrated 2N Indoor Compact,2N Indoor Talk,2N Indoor View  ✓ 2N IP AudioKit,2N IP VideoKit ✓ 2N IP Force,2N IP Safety ✓ 2N IP Style ✓  ✓ 2N IP Uni ✓ 2N IP Vario ✓  2N IP Verso,2N IP Verso 2.0  ✓  ✓      Installation Please click on the selected induction loop to see the instructions:  9155041 for IP Style, IP Verso, IP Verso 2.0 The module contains two bus connectors, that are fully interchangeable and can be used either as inputs from the basic unit or outputs to other modules.   Location of bus connector on 2N IP Intercom:2N IP Style 2N IP Verso 2N IP Verso 2.0        9159050 for IP Force, IP Safety, IP Style, IP Uni, IP Vario, IP Verso, IP Verso 2.0 The induction loop amplifier can be wall mounted with the use of an internal induction loop where a signal covering is requested. Outdoor use is possible thanks to the IP65 covering. A four-wire cable of the length of one meter is mounted to the supplied product for easier connection to the intercom. In the cable are two wires for 12 V DC supply and two wires for signal input, the wires are connected into interconnection connector. If you shorten the cable, follow the colour marking. Before wall mounting, run the cable through the hole that you have prepared.Then mark two mounting holes on the wall, through the amplifier front.Remove the amplifier and drill the mounting holes. Use a drill of the diameter of 6 mm.Use the plugs and screws included in the delivery.After fastening, cover the screws with the blanks supplied.Use the supplied connectors to connect the amplifier to the intercom and power supply. The A connector is connected to the amplifier four-wire cable. Insert a special intercom-connecting cable supplied with the amplifier and 12 V power supply outlets to the B connector. Connect the special cable to the intercom and connect the power supply to the mains. You can place the mated A and B connectors into the 2N IP Intercom cover. The connectors help you connect stripped cables. Open the connector by pushing a thin screwdriver onto the white spots at its front and close the connector by sliding the movable part through a side gap.Finally, test the amplifier function using a suitable receiver for hearing impaired persons or magnetic field communication tester. No other settings are required.    Location of Induction loop connector on 2N IP Intercom:IP Force and 2N IP Safety 2N IP Style 2N IP Uni    2N IP Vario      2N IP Verso 2N IP Verso 2.0      9159054 for Indoor Compact, Indoor Talk, Indoor View, IP Audio Kit, IP Video Kit The induction loop amplifier can be wall mounted with the use of an internal induction loop where a signal covering is requested. Outdoor use is possible thanks to the IP65 covering. A four-wire cable of the length of one meter is mounted to the supplied product for easier connection to the intercom. In the cable are two wires for 12 V DC supply and two wires for signal input, the wires are connected into interconnection connector. If you shorten the cable, follow the colour marking. Before wall mounting, run the cable through the hole that you have prepared.Then mark two mounting holes on the wall, through the amplifier front.Remove the amplifier and drill the mounting holes. Use a drill of the diameter of 6 mm.Use the plugs and screws included in the delivery.After fastening, cover the screws with the blanks supplied.Use the supplied connectors to connect the amplifier to the intercom and power supply. The A connector is connected to the amplifier four-wire cable. Insert a special intercom-connecting cable supplied with the amplifier and 12 V power supply outlets to the B connector. Connect the special cable to the intercom and connect the power supply to the mains. You can place the mated A and B connectors into the 2N IP Intercom cover. The connectors help you connect stripped cables. Open the connector by pushing a thin screwdriver onto the white spots at its front and close the connector by sliding the movable part through a side gap.Finally, test the amplifier function using a suitable receiver for hearing impaired persons or magnetic field communication tester. No other settings are required.    Location of Induction loop connector on 2N Answering units and 2N IP Intercoms:2N Indoor Compact, 2N Indoor Talk, 2N Indoor View 2N IP Audio Kit and 2N IP Video Kit

Question 24

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 25

Intergration Loxone Miniserver with 2N intercom

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.  Basic orientation    Loxone Miniserver (Gen 2) FW Version: v10.3.11.25  2N IP Intercom FW: v2.28    Example project file  You can download the project file here.    Loxone config tool is divided into a few sections:  Property menu allows you to define the parameters of a specific object such as name, destinations for http commands etc. The available parameters are different for each object.  General menu that allows you to assign new objects to the specific periphery section. This menu differs for each periphery.  Periphery menu that allows you to add specific objects to your project space.  Project space allows you to place objects from the Periphery menu by using drag and drop method. Interconnection of each object is done here.     Local calls configuration  Loxone Miniserver configuration The first step is to let the Loxone mini server know, that the button has been pressed on the intercom side. To be able to achieve it, the http commands will be used. In the Loxone mini server the object called Virtual Input is used. Click on Virtual Inputs in the periphery menu and select Virtual input from the upper general menu. A new virtual input will be created. You can drag and drop this virtual input to your project.  In this example the virtual input is called „trigger“. The name can be assigned to the input in the left property menu by changing the parameter called name (UUID).  The name of the input is the key parameter here, because it is used in the http command sent from the intercom. Another object which will be use is called „User defined intercom (Door Controller)“. This object can be added to the project by selecting network devices in the Periphery menu and selecting Add Network Device - User defined intercom in the upper general menu.     A new Door Controller object will be created in the Network devices. In this example the intercom is called 2N Intercom. The name can be changed again in the left property menu. Now the connection to the intercom needs to be configured. You need to configure the following parameters in the left property menu to be able to make local calls:  Picture when ringing –the video preview configuration  URL video stream (local) – the video stream during the call configuration  User name for Camera – login credentials to access the video from intercom  Password for Camera - login credentials to access the video from intercom  Host for audio (local) – destination IP address for the SIP call    Genral intercom’s http API syntax:   http://      /api/camera/snapshot?width=      &height=      &fps=        For more info regarding to the HTTP API commands of the intercom click here.   Example of the configuration:  Picture when ringing – http192.168.50.188/api/camera/snapshot?width=640&height=480&fps=15  URL video stream (local) - http:// 192.168.50.188/api/camera/snapshot?width=640&height=480&fps=15  User name for Camera – Admin  Password for Camera - Admin  Host for audio (local) – 192.168.50.188   Another parameter that can be configured is called Name for the function 1,2 and 3. This parameter allows you to create a button in the Loxone app which can be used to open the door on the intercom. You can assign the name for the button. In this example the button is called Lock. If the button will be pressed in the app, the specific output on the Door controller object is triggered. These outputs are called Q1, Q2 and Q3 and need to be added to the object.    Please note that the doors can be connected directly to the 2N intercom or to Loxone mini server. In this example the lock is directly connected to the intercom, so to be able to open the doors on the intercom, Q1 output needs to be connected to a digital output object called DTMF COMMAND which sends the http command to the intercom. How to configure this object is written in the next paragraph.  If the doors are connected to Loxone (Loxone is the one who decides if the doors are open), the Digital Output 1 can be connected to some other object / periphery in the Loxone. This scenario is out of the scope of the guide.  The last step is to add a Virtual Output object which sends an http command to the intercom to open the doors. Select Virtual Outputs in the periphery menu and create a new output by choosing Virtual Output object in the upper menu.       Once the new output is created (in this example VQ1), the virtual output command needs to be assigned from the upper menu and needs to be connected to Q1 output of the Door controller object.  Select the newly created output from the periphery menu (in this example the output is called VQ1) and define the IP address of the intercom in the property menu. In this example the IP address of the intercom is 192.168.50.188.  Select the Virtual output command object from the periphery menu (it is called DTMF COMMAND in this example) and define the http command.  The Http command can control the HTTP API or automation in the intercom. In the example the automation function is used however HTTP API works exactly in the same way just the HTTP command is in a different format. You can check HTTP API manual for more info. The following command has been used in this example:  General syntax: http:///enu/trigger/  Example: http://192.168.50.188/enu/trigger/dtmf    key name – is used in the automation on the intercom side as a trigger for some set of actions. In this example the key name is dtmf.     Intercom configuration On the intercom side, the automation needs to be configured (the enhanced integration license is required).  Once the main quick dial button is pressed, the intercom sends the http command towards the Loxone mini server. The command which controls virtual input has the following format : General syntax:    :    @     /dev/sps/io//     Where  UUID - name of the virtual input object in Loxone  Action – on / off commands  Example: admin:admin@192.168.50.182 /dev/sps/io/trigger/on   Login credentials can be changed in the periphery menu, in the section users. You can also create new users and use them instead of the admin access in the HTTP command. Object SendHttpRequest is sending an HTTP command to the Loxone mini server. Because this object has its own fields for username and password, the URL format is only 192.168.50.182 /dev/sps/io/trigger/on. The delay object is also triggered during the button press with a 5 second delay and then the intercom sends the http command for the deactivation. Example: admin:admin@192.168.50.182 /dev/sps/io/trigger/off Optionally you can also add a PlayUserSound object so once the button will be pressed, the intercom can play some user sound to notify the user in front of the intercom that the intercom is trying to establish the call. Another object is HttpTrigger where the key for dtmf is used. So once the intercom receives the http command in the format http://192.168.50.188/enu/trigger/dtmf, the intercom activates switch 1. Last step is to set incoming call in the intercom to automatic answering mode in the section Calling – General Settings  and HTTP API access for the video stream.        External calls To be able to make an external call to the intercom from the Loxone app which is out of your LAN, several configuration adjustments needs to be done:  Create a SIP account on some free public SIP server which allows you to make anonymous incoming calls and adjust the configuration in the intercom and in the Loxone mini server.  Register your Loxone mini server  Setup port forwarding on your router for the Loxone app access and video stream  Add push notification  The Loxone app / Mini server is always the one who is initializing the SIP call and the calls are anonymous which means that the Loxone mini server is not registered anywhere and trying to establish the peer to peer call.   In case of external calls – only the intercom needs to be registered to the SIP Proxy. Configuration of the door controller is used by the Loxone app on the smartphone and here you only have the options for a SIP host and a user-id. This ID is NOT for the app itself but used to make an anonymous call to the intercom that has been registered as a SIP client with specific credentials. The app is NOT a full SIP client, so it does not register with a SIP provider. The Loxone app can make outgoing calls as an anonymous SIP user to the intercom by using the user-ID as a "phone number" for the destination (the intercom).  SIP account configuration To be able to make an external call, the call needs to be sent to some proxy server which is able to receive calls from unknown sources. In this example server called antisip.com is used. Once the account is created, the intercom needs to be connected to the server. This can be done in section Calling  - SIP 1 or SIP 2 - Configuration In this example the details obtained from anitsip.com are:  Intercom configuration looks like this:   Now the intercom is registered on the antisip.com service and the Door controller settings need to be adjusted to be able to make a call from the mini server to the intercom. In the property menu of the Door Controller the following parameters need to be adjusted:  Host for audio (external) – the domain name of the service  Audio username (external) – contact which the Loxone will be calling  URL video stream (external) - router's public IP address needs to be specified      Port forwarding The next step is to create the port forwarding rules in your router to be able to connect from the Loxnone app to the mini server via the internet. Loxone provides a remote connection service. The first step is to register your Loxone mini server on their website. Once the device is registered, the Loxone mini server has a specific domain name to which it is connected. The domain name is dns.loxonecloud.com/. The Loxone server detects and stores info about your router public IP address and defined ports (specified in the Loxone mini server configuration - described in the next paragraph) and once the Loxone app, which is placed somewhere in the internet, wants to connect to your mini server which is placed on the LAN, the request is sent to the same domain name and the Loxone DNS server forwards the request to your public IP address with specific port numbers. If the port forwarding rules are done correctly, your router forwards this request to the Loxone miniserver placed on your LAN. Note that the default password to access the Loxone miniserver cant be used for remote connection. So a password change is required to be able to remotely connect to the Loxone mini server. Password can be changed on the user settings.      It is necessary to specify which ports will be used for access to the Loxone mini server from the internet. This can be done in the details of the Loxone miniserver. In this example the ports for incoming communication to the Loxone miniserver are 8003 and 8443.        The next step is to configure port forwarding in your router. In this example the router port forwarding details are:  Incoming traffic to public IP address of the router on port 8003 and 8443 will be forwarded to the IP address of the Loxone miniserver (in this example the ip address is: 192.168.50.182) to ports 80 and 443.   The port forwarding needs to be specified also for the video stream. In this example again the he port forwarding is done on port 8003 (external) to port 80 (LAN).    The last step is to enable push notification for your smartphone. The push notification mechanism allows you to wake your Loxone app. Each app is closed in IDLE state by the Android / iOS platform and the only mechanism how to wake the app and receive a call is to usethe in built Android / iOS push notification mechanism. Make sure that you have enabled push notifications for the Loxone app. Then add push notification object from Periphery menu into your Loxone project.

Question 26

KNX connectivity with 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.   Our 2N IP Intercoms can cooperate with KNX, an open standard for commercial and residential building automation.We will show you how to setup these scenarios:  Signalization of pressed button on the 2N IP Intercom into the KNX system.  Activation of the door lock connected into the 2N IP Intercom via the KNX system.    Prerequisites 2N IP Intercom with the latest firmware and connected door lock.GOLD license is required to use automation interface.The device must be equipped with at least one free input and output.Most of our devices have at least one input on the main unit, here is an exception: 2N IP Force & 2N IP Safety & 2N IP Variorequiring additional module2N IP Unidoes not have input at all  KNX System using KNX actor with at least one free input and output.     Connection diagram                 2N IP Intercom configuration Go to section Services - Automation and setup the function to activate Relay 1 when the quick dial button is pressed.   Go to section Hardware - Digital Inputs - Door and assign IP Intercom´s input for exit button scenario.    Go to section Hardware - Switches and be sure, Switch 1 is enabled and set for the proper controlled output (where the door lock is connected).

Question 27

MicroSIP - Direct call with 2N IP Intercom

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. MicroSIP is open source portable SIP softphone for Windows OS allowing you to provide high quality VoIP calls via open SIP protocol.   Prerequisites 2N IP Intercom with the latest firmware,no additional license is requiredMicroSIP softphone the latest version (https://www.microsip.org)installed on your computer with Windows OS   2N IP Intercom configuration In the web interface, go to the Directory - Users section and add a new user.    In the new user details, fill in the name and Phone Number in format "sip:PC_IP_ADDRESS" and save.Instead of "PC_IP_ADDRESS" use IP address of your computer.If you don´t know, how to find it, open a Windows command line and enter the "ipconfig" command. Go to the Calling - Dialing section and add the new user to the quick dial button and save.  Go to the Calling - SIP 1 section and enable SIP account to activate calling feature.   Stay in the same section, go to the Device Identity part, make a note of the Phone Number (ID) value, then enter the IP Intercom IP address in the Domain field and make a note of it as well.Go to the Advanced Settings part, set the SIP Transport Protocol to UDP and save.    In the Video tab, go to Extended Codec Settings and enable H.264 Constrained Baseline Profile, Packetization Mode 1, this is the video Codec which is used by MicroSip to call outside, and then,  go to the Advanced SDP Settings part and enable the "Use sendrecv Attribute for Video" parameter and save.This setting is necessary only in case you will use video calls. In case you need to have bidirectional video with 2N IP style or Third Party devices, don't forget to activate it.       Go to the Calling - General Settings section, in the Incoming Calls part, set the Call Answering Mode (SIP1) to Automatic and save.This setting is necessary only in case you will need to call from MicroSIP to the IP Intercom.    To be able to open door during call, go to Hardware - Switches sectionand verify proper configuration for your scenario.Make a note of set Activation Code with DTMF accessibility.    MicroSIP configuration and usage  Go to MicroSIP Settings.   In Settings, be sure that necessary audio and video codecs are enabled.  In Settings, enable Local Account and Save.  Let´s try the IP Intercom call.    During the call, you can open the door by dialing the switch activation code, confirmed by * .In our case, dial  00*  .  Let´s try call from MicroSIP to the IP Intercom.Enter the IP Intercom identity details (noted from its web interface) in format  ID@Domain,in our case  111@192.168.50.15 , and start the audio or video call.  Now we will make calling from MicroSIP and dialing switch activation codes much easier using the shortcut buttons.

Question 28

Milestone XProtect and 2N IP Intercom integration

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.    With physical and cyber security threats on the rise, it’s more important than ever to level up your business security systems. Milestone XProtect video management software (VMS) connects your cameras, sensors, analytics, and sites in one easy-to-manage interface. We will show you how our 2N IP Intercom can be part of it.   Prerequisites 2N IP Intercom with the latest firmware (the article created on version 2.44);additional GOLD license is necessary.Milestone XProtect (the article created on version 2023 R1)   Connecting 2N IP Intercom to Milestone XProtect  Enable ONVIF in 2N IP Intercom Go to 2N IP Intercom web interface, section Services - Streaming - ONVIF / RTSP, and enable RTSP Server.     In the User Accounts part, create the user account with administrator access level.    In the Transmission Quality Settings part, make sure that UDP Unicast Enabled is checked.       Add 2N IP Intercom to Milestone XProtect   On the side of Milestone server (via Milestone XProtect Management Client),go to Servers - Recording Servers menu and do the right click on your server. Select Add hardware...      Choose the hardware detection method. The express is the easiest, it scans the local network, however we will look on the Address range scanning method where you can adjust the scanning range.    Add and select the user account created in 2N IP Intercom web interface.    To speed up the scanning, select just common ONVIF drivers.    Specify the network ranges to scan for hardware. Select using HTTPS.    Once the scan is finished, select your hardware to add.    System collected information about the hardware. Continue to the next step.     Now choose the available peripheries of the intercom to use.Typically, you will use camera, microphone, speaker and some inputs and outputs.     Add the device to groups. If you did not create the groups yet, you have to do it now.    Once the procedure is finished, you will see added devices and their peripheries, incl. camera preview.If Milestone is not able to connect to the camera, then please check your firewall settings.     Now the device appears in the Devices menu where you can adjust some settings, e.g. name of the periphery.       Operation in Milestone XProtect Right now you can start Milestones XProtect Smart Client which is surveillance window for video monitoring (for security guys).  Video Preview Drag selected camera and drop it into any window on the right side.     Outputs control You can also activate selected output from this client.     Two-way audio    You can also set microphone for listening-in and also select appropriate speaker to which you want to talk when holding the button "Talk".     Overlay buttons Add some special buttons for relay activation or for talking to the speakers to the Video preview window.Click on the "Setup" button on the top right corner. Then everything is based on drag and drop principle.

Question 29

Milestone XProtect Smart Client - log operator's actions

Accepted Answer

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

Question 30

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

Accepted Answer

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

Question 31

Multicast Stream configuration with IP Audio Manager

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.      Sending or receiving multicast stream from/to 2N IP Intercom is a feature that can be used for emergency calls or just for any announcement that will be sent from/to 2N IP Audio Manager. How to set both scenarios can be found in description below.  How to receive multicast stream from 2N IP Audio Manager If you want to set 2N IP Intercom as a audio destination for 2N IP Audio Manager  , you must connect it as a RTP destination.   2N IP Audio Manager setting  Open 2N IP Audio Control Panel and go to section Destinations & Zones. Here click on right mouse button and choose the option "Create RTP destination".    Then choose created RTP destination and specify IP Address and Port on which your   2N IP Intercom   will be  listening.    As a last step in 2N IP Audio Manager  settings go to Sessions, create a new session and assign previously created RTP destination as the destination for audio broadcasting.     2N IP Intercom setting Configuration on 2N IP Intercom side is very easy, all you need to do is to go to the section Services -> Streaming -> Multicast and activate the multicast receiving. In Address and Port parameters specify the same IP address and port which you added to 2N IP Audio Control Panel.        How to send multicast stream to 2N IP Audio Manager If you want to use 2N IP Intercom for making announcements to all speakers connected to  2N IP Audio Manager  , you must connect it as new RTP source.  2N IP Audio Manager setting Open  2N IP Audio Control Panel   and go to section Audio Sources. Here create new RTP source and specify for it Port and IP address on which you will be sending announcements.  When the RTP source is created, go to section Sessions and create a new session. Here add a new RTP destination as audio source, specify units or zones to which you want to broadcast and the activate the session.    2N IP Intercom setting For setting the paging function on 2N IP Intercom you have to use Automation feature. How to do this is described in this FAQ: Automation, Multicast paging - How to configure paging from 2N IP Intercoms  The settings mean that if any user presses the quick dial button 5 on the  2N IP Intercom (for this settings you need to have the intercom with 6 buttons), then the user´s sound is sent as a multicast request to all other devices. This sound takes 2 seconds. After that period of time you can start talking and  2N IP Intercom  will stream this multicast traffic to 2N IP Audio Manager   . If you want to stop multicast streaming, you just press the quick dial button 5 again.   Note: All commands used in the Automation section are deeply described in our 2N Automation manual where you can find also some examples. This manual is available on our web pages:https://wiki.2n.com/hip/auto/latest/en

Question 32

OpenVPN server & client

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 guide describes connecting 2N IP intercom, 2N LTE intercom or 2N Access Unit to the user’s remote LAN by OpenVPN server.   Disclaimer    Please note that this guide and its content is provided "as is" without warranty of any kind, express or implied. Therefore by using it you hereby agree that you are aware of this content functionality, limitations and consequences, you acknowledge that the guide content is provided for limited purpose.   2N TELEKOMUNIKACE a.s. shall not be held liable for function limitations, security limitations or damage, if any, incurred as a result of using this guide.   Please also note that various Linux distributions or versions may not accept all commands shown in this guide and 2N TELEKOMUNIKACE a.s. does not provide support for Linux.        Prerequisites     2N IP Intercom / 2N LTE Intercom / 2N Access Unit with the latest firmwareno additional license is requiredLinux PC with this applications: openvpn (server)stunnel4bridge-utilslshw Network requirements: Public IP address at the router on local network side where OpenVPN server is, accessible from the Internet with a possibility of redirecting TCP port 443 to LAN (DMZ for OpenVPN server optional).DHCP at the local network side where OpenVPN server is.Intel PRO/1000T Server compatible network controller with enabled Promiscuous Mode   IT knowledge requirements: bash scripting,certificates, Linux command line (bash),networking,SSL,VPN        Technical network information Solution is designed for OpenVPN to be installed on Linux.2N OpenVPN server is designed to connect 2N devices exclusively, 3rd party devices or software may not be able to connect properly.This connection creates network bridge and thus enables connection to 2N device in the same way as it would be in the local network, so it can be used as usual (for calls, video surveillance of its IP camera, 2N Access Commander connection, etc.). Device which is in the same local network as OpenVPN server does not need to be connected to VPN, since all devices connected over VPN will have local network IP addresses from local DHCP.      2N device obtains IP address from local network DHCP where OpenVPN server is, uses network protocols like ARP, can perform broadcast and so on.VPN connection is pushed through stunnel for additional level of security.In case you cannot put OpenVPN server machine to DMZ and you need to use standard LAN and private address, you need to setup port forwarding so incoming connections from Internet to OpenVPN server reach target machine. You will also need to allow such communication on router's firewall.   Configure the local network on its router – set DHCP IP reservation for OpenVPN server virtual machine (based on MAC address of virtual machine's ethernet port). DHCP server will always assign the same IP address.Configure port forwarding if needed - forward public port to port 443 TCP on IP address assigned by DHCP for OpenVPN server.Choose public port number above 1024 TCP to avoid using privileged ports.    2N OpenVPN server installation   All examples shown in this article are for Debian 10 and require to be run with elevated rights, either login as root or use proper command to gain required rights. On the Linux machine, deploy stunnel4, openvpn, bridge-utils and lshw via command in the command line.apt-get install -y stunnel4 openvpn bridge-utils lshw >/dev/null Create certificates for OpenVPN. You need server certificate, server key, ca and intercom certificate with intercom key. Then you need to put those certificates to correct folders for stunnel, openvpn and intercoms. You can do it manually or use the script below. This script will generate unique certificates each time it is run and put them in /tmp/certs folder. Then it moves all required certificates to appropriate folders. It also generates client certificates for IP Intercoms / Access Units and place them to folder /root/certs from where you can download them.To make script run, you need to save it in EOL conversion to UNIX and encoding UTF-8 format as .sh file, then upload it and apply chmod a+x to make script executable.In the script example, the intercom.key password is set to Test1234, but due to security we recommend to create your own certificates with own password and settings, use this example as a reference only. 2N TELEKOMUNIKACE a.s. does not hold any responsibility if example certificates will not be secure enough. #!/bin/bash ################################################################################ # Settings                                                                     # ################################################################################ # Certificates C_C=""     # Country Name (2 letter code) C_ST=""    # State or Province Name C_L=""     # Locality Name C_O=""     # Organization Name C_OU=""    # Organizational Unit Name C_CN=""    # Common Name ################################################################################ VERSION=1.0 ################################################################################ print_step() {     echo -n "${1} ... " } print_ok() {     echo "[ OK ]" } check_error() {     if [ $1 -ne 0 ]; then         echo         echo         echo         echo "Error: $2"         echo         exit $1     fi } print_step "Generating certificates" TMP_CERTS=/tmp/certs EC=prime256v1 EC_PARAMS=ec-${EC}-params.crt PASS=Test1234 rm -rf ${TMP_CERTS} mkdir ${TMP_CERTS} check_error $? "can't generate certificates" touch ${TMP_CERTS}/index.txt ${TMP_CERTS}/index.txt.attr check_error $? "can't generate certificates" echo "01" > ${TMP_CERTS}/serial.txt check_error $? "can't generate certificates" cat ${TMP_CERTS}/openssl.cnf [ ca ] default_ca      = CA_default [ CA_default ] database        = ${TMP_CERTS}/index.txt serial          = ${TMP_CERTS}/serial.txt policy          = policy_default [ policy_default ] commonName      = supplied EOF check_error $? "can't generate certificates" openssl ecparam -name ${EC} -out ${TMP_CERTS}/${EC_PARAMS} &>/dev/null check_error $? "can't generate certificates" subj="/C=${C_C}/ST=${C_ST}/L=${C_L}/O=${C_O}/OU=${C_OU}/CN=${C_CN:-Certificate Authority}" openssl req -subj "${subj}"                                                  \             -passout pass:${PASS}                                            \             -new -x509 -newkey ec:${TMP_CERTS}/${EC_PARAMS}                  \             -days 3650 -sha256                                               \             -keyout ${TMP_CERTS}/ca.key -out ${TMP_CERTS}/ca.crt             \         &>/dev/null check_error $? "can't generate certificates" subj="/C=${C_C}/ST=${C_ST}/L=${C_L}/O=${C_O}/OU=${C_OU}/CN=${C_CN:-Server Certificate}" openssl req -subj "${subj}"                                                  \             -new -nodes -newkey ec:${TMP_CERTS}/${EC_PARAMS}                 \             -keyout ${TMP_CERTS}/server.key -out ${TMP_CERTS}/server.csr     \         &>/dev/null check_error $? "can't generate certificates" subj="/C=${C_C}/ST=${C_ST}/L=${C_L}/O=${C_O}/OU=${C_OU}/CN=${C_CN:-Intercom Certificate}" openssl req -subj "${subj}"                                                  \             -new -nodes -newkey ec:${TMP_CERTS}/${EC_PARAMS}                 \             -keyout ${TMP_CERTS}/intercom.key -out ${TMP_CERTS}/intercom.csr \         &>/dev/null check_error $? "can't generate certificates" openssl ca -config ${TMP_CERTS}/openssl.cnf                                  \            -passin pass:${PASS}                                              \            -cert ${TMP_CERTS}/ca.crt -keyfile ${TMP_CERTS}/ca.key            \        -outdir ${TMP_CERTS} -days 3650 -md sha256 -batch                 \        -in ${TMP_CERTS}/server.csr -out ${TMP_CERTS}/server.crt          \         &>/dev/null check_error $? "can't generate certificates" openssl ca -config ${TMP_CERTS}/openssl.cnf                                  \            -passin pass:${PASS}                                              \            -cert ${TMP_CERTS}/ca.crt -keyfile ${TMP_CERTS}/ca.key            \        -outdir ${TMP_CERTS} -days 3650 -md sha256 -batch                 \        -in ${TMP_CERTS}/intercom.csr -out ${TMP_CERTS}/intercom.crt      \         &>/dev/null check_error $? "can't generate certificates" print_ok ################################################################################ rm -rf /etc/stunnel/keys mkdir /etc/stunnel/keys cp ${TMP_CERTS}/ca.crt /etc/stunnel/keys/ca.crt check_error $? "can't set stunnel service" cat ${TMP_CERTS}/server.crt >/etc/stunnel/keys/server.pem check_error $? "can't set stunnel service" cat ${TMP_CERTS}/server.key >>/etc/stunnel/keys/server.pem check_error $? "can't set stunnel service" rm -rf /etc/openvpn/server/keys mkdir /etc/openvpn/server/keys cp ${TMP_CERTS}/ca.crt /etc/openvpn/server/keys/ca.crt check_error $? "can't set openvpn service" cp ${TMP_CERTS}/server.crt /etc/openvpn/server/keys/server.crt check_error $? "can't set openvpn service" cp ${TMP_CERTS}/server.key /etc/openvpn/server/keys/server.key check_error $? "can't set openvpn service" rm -rf /root/certs mkdir /root/certs cp ${TMP_CERTS}/ca.crt /root/certs check_error $? "can't copy intercom certificates" cp ${TMP_CERTS}/intercom.key /root/certs check_error $? "can't copy intercom certificates" cp ${TMP_CERTS}/intercom.crt /root/certs check_error $? "can't copy intercom certificates"        Configure stunnel via command in the command line. cat /etc/stunnel/stunnel.conf   [openvpn] accept  = 443 connect = 1194 CAfile  = /etc/stunnel/keys/ca.crt cert    = /etc/stunnel/keys/server.pem verify  = 2 EOF     Configure OpenVPN service via command in the command line. cat /etc/openvpn/server/server.conf     local 127.0.0.1 server-bridge dev   tap proto tcp-server port  1194 ca   /etc/openvpn/server/keys/ca.crt cert /etc/openvpn/server/keys/server.crt key  /etc/openvpn/server/keys/server.key dh   none tun-mtu 1500 script-security 2 auth-user-pass-verify /bin/true via-file client-to-client duplicate-cn auth   none cipher none up   "/etc/openvpn/server/up.sh" down "/etc/openvpn/server/down.sh" verb 0 EOF        Configure scripts for OpenVPN service and give them the proper file rights via commands in the command line. cat /etc/openvpn/server/up.sh    #!/bin/bash TAP="\${1}" MTU="\${2}" . ./settings.sh dhclient -x \${ETH} ip link set \${ETH} promisc on mtu \${MTU} ip link set \${TAP} promisc on mtu \${MTU} up brctl addbr \${BR} brctl setfd \${BR} 0 brctl addif \${BR} \${ETH} \${TAP} dhclient \${BR} EOF    chmod +x /etc/openvpn/server/up.sh     cat /etc/openvpn/server/down.sh     #!/bin/bash . ./settings.sh dhclient -x \${BR} ip link set \${BR} down brctl delbr \${BR} ip link set \${ETH} promisc off dhclient \${ETH} EOF     chmod +x /etc/openvpn/server/down.sh   cat /etc/openvpn/server/settings.sh     ETH=$(lshw -quiet -class network -short | awk '/^\/0\//{print $2}')  ETH=${ETH} BR=br0 EOF     chmod +x /etc/openvpn/server/settings.sh                  Bridge network traffic properly via commands in the command line. Do not run commands in this step over SSH as they include bringing ETH interface down which will result in connection loss.  sed -i 's/inet dhcp/inet manual/' /etc/network/interfaces   sed -i '/br0/d' /etc/network/interfaces     cat >/etc/network/interfaces      # openvpn bridge br0 allow-hotplug br0 iface br0 inet manual EOF      ifdown ${ETH} &>/dev/null   ifup ${ETH} &>/dev/null    systemctl enable stunnel4.service &>/dev/null    systemctl enable openvpn-server@server.service &>/dev/null                             Restart OpenVPN and asociated services via commands in the command line.  systemctl restart openvpn-server@server.service    systemctl restart stunnel4.service        Check if stunnel and openvpn service are running via commands in the command line,otherwise repeat previous step.   lsof -i 4                     If firewall is installed, enable ports 1149 and 443 to be accepted via commands in the command line. (example configuration uses TCP protocol for OpenVPN)  ufw allow 1149/tcp   ufw allow 443/tcp     systemctl restart ufw        Connect 2N device to 2N OpenVPN server  You need to upload certificates downloaded from OpenVPN server to 2N device and configure OpenVPN connection in 2N device. You will use same client certificates for every 2N device connecting to this VPN. After successful connection, 2N device will receive DHCP address from local network where 2N OpenVPN server is and will appear to local network as local device. Go to 2N device (you want to connect to 2N OpenVPN server over Internet) web interface, section System - Certificates, Upload ca.crt file to CA Certificates, upload intercom.crt and intercom.key files to User Certificates.           Go to section System - Network - OpenVPN, enable it, set the following and save.Default Interface: NoSet to Yes if 2N device connected via VPN is supposed to communicate outside local network connected over VPN.Otherwise, 2N device will route such traffic via its own connection and will not route it to VPN.Server Address: Public IP (which belongs to router where 2N OpenVPN server is)Server Port: Public Port (port used for forwarding on router where 2N OpenVPN server is - for example 1443)Trusted Certificate: Select the uploaded certificateClient Certificate: Select the uploaded certificate     Press Start button to connect to 2N OpenVPN server.

Question 33

Password recovery in 2N OS devices

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.   Have you forgotten your login password to the web interface of 2N OS based device and there is no other authorized administrator?      Then the only possible solution is a hardware factory reset returning the password back to "2n", after first using it, you will be required to setup a new strong password.    Factory reset procedure Please follow one of these articles: Video - 2N OS devices - Factory Reset procedure(universal video guide)2N IP Intercoms - Factory reset(deeper look on location of factory reset button on IP Intercoms)    Changing login password in the web interface After successful login in the web interface, you can go to section Services - Web Server and change the login password.

Question 34

Setting up 2N IP Intercom with SNOM 760 phone

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 FAQ describes how to configure direct (P2P) call between 2N IP intercoms and IP phone SNOM 760/ SNOM D765. It is also describing how to display video from 2N Helios IP intercoms on the phone before answer by Function buton. Further more it describes how to configure Function button for direct call to 2N IP Intercom and also how to set one of this buttons to send DTMF or HTTP command for switch activation of 2N IP intercoms. This FAQ was made for FW version of 2N IP intercoms 2.14.2 and higher.  How to configure direct call on 2N Helios IP intercom   In first step go to section "Directory->Users" and fill "Phone number" in format "sip:ip_address_of_the_phone) (in our case it is sip:192.168.1.2)      In next step go to section "Services->Streaming->JPEG" and enable "JPEG Video Activated by Call" to enable video activation before answer  .      Now you have to enable HTTP API for camera, by this you will allow the phone to download the video. Go to section "Services->HTTP API" a "Camera API" set to "Unsecure" and "None".     In this step set the intercom to automatic pickup of incoming calls. Go to section "Calling->General Settings->Incoming Calls". Configure the section based on picture below.       How to configure direct calls on IP phone SNOM 760   Optionally you can set static address on the phone which will be called by the intercom (we recommand to do this - of course intercom can call to address obtained from DHCP server, but there is a chance that after dissconnection the phone from the network and connection again, the phone will get different IP address). You can adjust the address in section Advanced Settings->Network". Optionally also by the buttons on the phone in menu "Menu->Network->IP address".      In section "Advanced Settings"->SIP/RTP you can check whether the port is set to standard 5060 or you can change it, if you want to use different one.     In section "Advanced Settings->QoS/Security" set parameter "Filter packets from registrar" to "OFF"     After you will finish the configuration, please reboot the phone, then all the changes will apply.       How to configure video preview on IP phone SNOM 760  In first step you can optinally change "Phone number (ID)" in section "Calling->SIP 1->Configuration". In default value is 111 and in the next step you have to fill this number in web interface of the SNOM phone.     In next step open the web intarface of the SNOM phone and go to section "Operation->Directory" and to field "Number" fill the number from the first step (in this case 111). To field "Action-Url" fill  "http://ip_address_helios/enu/snom820-video.xml"       How to display video from 2N Helios IP intercom on IP phone SNOM 760 via function button  Go to section "Setup->Function keys". Choose a button, which you want to use, and for "Type" choose "Action URL". To field "Number" fill URL  "http://ip_address_helios/enu/snom820-video.xml". Field "Short text" can be optionally used for buttons function description.           How to configure direct call from IP phone SNOM 760 to 2N Helios IP intercom  Stay in section for Function keys configuration, pick a button and choose "Speed dial" and fill "SIP:ip_address_of_intercom".      How to configure switch activation on 2N Helios IP intercom from IP phone SNOM 760 via DTMF  Still in the same section choose "DTMF" and fill desired code (in this example it is 00).       How to configure switch activation on 2N Helios IP intercom from IP phone SNOM 760 via HTTP command  Still in the same section choose "Action URL" and fill URL "http:// ip_address_of_intercom/api/switch/ctrl?switch=1&action=trigger     In second step you have to disable security for switch API. Go to section "Services->HTTP API" and set "Switch API" to "Unsecured" and "None".

Question 35

Setting up Grandstream GXV3672 for external camera for 2N IP Intercom

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.  Open a web browser with IP address of your GrandStream GXV3672HD camera.  You will see the opening screen as described below, go to Menu Configuration and enter the Username and PasswordBy default Username: admin  Password: admin  Set the video steam in Menu Basic Setting -> Video & Audio as is described in the picture below and press Save  That is all for the IP camera settings 3. In the next step open the web browser with IP address of your Helios IP device and enter the Username and password In menu Hardware -> Camera -> Common Settings enable Video Source „External camera“    In menu Hardware -> Camera -> External Camera in the field will be RTSP Stream Address „rtsp://x.x.x.x:554/0“, where x.x.x.x is the IP address of your external IP camera Username is in default „admin“ and password „admin“ as well.      Remember: The IP address is just an example, it will be different in your network It is strongly recommended to change the basic default setting in order to increase the security

Question 36

SIP Proxy registration on 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.

Question 37

SNOM 870 - Setup with 2N IP Intercom

Accepted Answer

In Menu Setup - Advanced Settings - SIP/RTP setup following parameters:  Network Identity(port): 5060  Filter Packets from Registrar: OFF   In Menu Setup - Advanced Settings - QoS/Security setup following parameters:  Listen on SIP TCP port: ON

Question 38

Starting manual for integration with 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.   This document serves to streamline integration of 2N IP Intercoms with 3rd party systems. Typical examples of integration are described here for better orientation in intercoms configuration and their manuals. The document has been made for FW version v2.13, however, it refers to chapters from manuals which stays same when the new versions are released. Current versions of the manuals are always available here. Apart from the installation manuals, which are describing physical connection of a particular models, their inputs/outputs, installation etc., all manuals are common for all models of 2N IP Intercoms. For the most common scenarios we have created FAQ section with manuals, where we describe configuration of different functions and scenarios step by step.    1. Description of 2N IP Intercoms All 2N IP Intercoms are based on SIP protocol therefore they offer all advantages of VOIP services similarly as classical SIP phones. Configuration is made via web interface directly from a web browser. Comparison of offered models can be found in common configuration manual in chapter 3. Model Differences and Function Licensing (here). All basic features are available without any additional licences, if some feature is licensed, then it won't be possible to edit it and it will be grey in the web interface. Which licences are currently active can be simply verified in section System->Licences in web interface. All the licensed features described here are available with a Gold license (Part. No. 9137906)   2. Configuration of 2N IP Intercoms As already mentioned, all SW configuration is made via web interface and it is described in common configuration manual here. In default intercoms are configured to DHCP mode and credentials are admin/2n. Address from DHCP can be discovered simply directly with button on intercom. How to do that is described in this FAQ.  Every editable parameter is described in manual mentioned above. For parameters, where is available to choose from more options, all these options are described. If you will stay on some parameter with cursor of your mouse for a while, then a Pop Up help will appear. This help briefly describe what this particular parameter do and in which format you have to fill it. See picture below. firmware v2.23.1 and older:   firmware v2.24.0 and later:   If native features of intercom are not enough to make your scenario functional, then it is possible to purchase Gold license (Part. No. 9137906) to make Automation section available. This section allows you to program your own functions. Logic of this feature recognizes three basic variables:  Event  Action  Condition  Event is for example pressed button, received HTTP command, particular time, change of output status etc., by this Events Actions are triggered. Action is for example send HTTP command, send mail with picture from integrated camera, switch activation etc. So for example when 1st quick dial button is pressed (Event), intercom will send mail to predefined address with photo of person standing in front of the intercom (Action). Meeting of this actions can be dependent on Condition, which can be status of time profile, call status, status of one of the inputs etc. If we apply this on our example with sending mail after button press, then we can put there Condition with time profile. So the mail will be send only when the button is pressed and the time profile is active (for example only during bussines days), see picture below. All available Events, Actions and Conditions are described in detail including all possible parameters in common Automation manual here.   3. Streaming of audio and video from 2N IP Intercoms via RTSP and HTTP access to camera 2N IP Intercoms allows watching of stream directly from camera including audio. To make this function available, it is necessary to buy Gold license (Part. No. 9137906) licence. This function is described more in detail in common configuration manual in chapter 5.4.2 Streaming (here). Example of how it is possible to display this stream is described in this FAQ, which describes how to set VLC player for receiving video. Where to configure streaming can be seen in picture below. You can use 4 different URL's for stream:  rtsp://ip_address_of_intercom/ - this will show stream based on parameters configured in RTSP fold  rtsp://ip_address_of_intercom/h264_stream - this will show stream with H.264 codec  rtsp://ip_address_of_intercom/mpeg4_stream - this will show stream with MPEG-4 codec  rtsp://ip_address_of_intercom/mjpeg_stream - this will show stream with MJPEG codec  Access to camera HTTP API is secured in default. So if you won't set this security on device, which will get the stream from intercom, then you have to disable this function in section Services->HTTP API. For Camera API set Unsecured for Connection Type and None for Authentication.   In fold JPEG you can configure the easiest way of streaming with aid of JPEG/HTTP and MJPEG/HTTP methods. For download of JPEG please use this URL:  http://ip_address_of_intercom/api/camera/snapshot?width=W&height=H  For MJPEG this URL:  http://ip_address_of_intercom/api/camera/snapshot?width=W&height=H&fps=N  Values W a H specify resolution of image (supported resolutions are 160x120, 320x240, 640x480, 176x144, 322x272, 352x288, 1280x960 - only for models equipped with 1MPix camera) Value N specify number number of pictures per second (you can choose from 1 up to 10). For sections Services->HTTP API is applied same configuration as above.   4. Configuration of Onvif on 2N IP Intercoms 2N IP Intercoms support international standard ONVIF, which makes them fully compatible with other ONVIF systems. To enable this function you have to purchase licence Gold license (Part. No. 9137906). Configuration of ONVIF is described in detail in common configuration manual in chapter 5.4.2 Streaming (here).   5. HTTP API on 2N IP Intercoms 2N IP Intercoms offers application interface HTTP API which enables control some of the features with HTTP protocol.This interface is described in common IP HTTP API manual. It enables even closer integration with third party systems like security systems, home automation systems, monitoring systems etc. HTTP API offers this services:  System API – Enables changes of configuration, tracking of intercom status and upgrade of intercom.  Switch API – Enables control and status tracking of switches, for example opening the door locks etc.  I/O API – Enables control and status tracking of logical inputs and outputs of intercoms.  Camera API – Enables control of camera and watching of video from it.  Display API – Enables control of display and showing of user information on display  Phone/Call API – Enables control and tracking of incoming and outgoing calls.  For trial of HTTP API you can use integrated tool on address https://ip_address_of_intercom/apitest.html. HTTP API also can be used for downloading logs from the intercom. 500 event can be stored in memory of log for example key presed, numeric code entered, RFID card detection, call status changed etc. RFID card detection can be used for integration with 3rd party attendance system. Logging including all messages in HTML is described in common Event Logging manual.   6. Integration of 2N IP Intercoms with security systems  Thanks to inputs/outputs, which can be found on 2N IP Intercoms, it is possible to integrate the with 3rd party security systems. Typical example is Tamper switch. It is module, which detects opening of body of the intercom. This allows to create function in Automation (which is described above) which defines what will happen in case of unauthorized access to intercom. Example of this for 2N IP Force is described in this FAQ. In this case intercoms is configured to play alarm sound from user sounds after unauthorized access to scare off the burglar. However for integration with security system it is possible to connect input of security system to one of the intercom outputs and create function, which will ensure that after unauthorized access, logical 1 will appear on this output and alarm will be triggered. Example of such function is in picture below.   Another example of integration with security system is signalization of secured/unsecured. Output of security system is connected to input of the intercom. When the system is secured then there is logical 1 on input of the intercom and pictogram of lock on the intercom is shining. If the system is unsecured then there is logical 0 on the input of the intercom and pictogram is not shining. Example of such function created for 2N IP Verso is in picture below.   7. Installation of 2N IP Intercoms As already mentioned in this document, the installation manuals are different for each model of 2N IP Intercom. For download of these manuals you have to choose the right model on the guidepost page here and then download an installation manual. Whole installation is always described in this manuals starting with attaching to wall and ending with connection of additional modules. Very important chapter in all of these manuals is chapter Electric installation where all the inputs/outputs of the intercoms are described, also connection of the jumpers for different functions of inputs/outputs etc.

Question 39

Static IP address in 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.   In default setting, 2N IP Intercom uses a dynamic mode, the IP address is obtained from DHCP server. In case you need to use a static IP address, you set it in the device web interface or by quick dial button.   Prerequisites 2N IP Intercom connected to local network;no additional license is required   Web interface method Go to device web interface, section System - Network - Basic, disable the option "Use DHCP Server" and enter the network parameters.      Static IP Address Static IP address of the intercom, which is used together with the below mentioned parameters if the Use DHCP Server parameter is disabled.  Network MaskSubnet identification.  Default GatewayAddress of the default gateway, which provides communication with off-LAN equipment.  Primary DNSPrimary DNS server address for translation of domain names to IP addresses.  Secondary DNSSecondary DNS server address, which is used in case the primary DNS is inaccessible.     Quick dial button method In case that you do not have the possibility to change the settings via web interface, you can do it manually via quick dial buttons. The following network parameters will be set after the static IP address mode is switched on and the device is restarted: IP address: 192.168.1.100Network mask: 255.255.255.0Default gateway: 192.168.1.1   Connect (or, if connected, disconnect and reconnect) 2N IP Intercom to the power supply.Wait for the first sound signal.Now you have only 30 seconds (from security reasons) to apply the quick dial button procedure according to your 2N device model. After this time it won´t work and you must restart the device again. Click below to see the instructions.   2N IP Base Press 15 times the first quick dial button on the unit.Up to 2s intervals are allowed between the presses.  Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.              2N IP Force    The procedure is different according to number of buttons.  1 or 2 buttons  Press 15 times the first quick dial button on the unit.Up to 2s intervals are allowed between the presses.     Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.          4 buttons Press buttons 1, 1, 1, 2, 2, 3 sequentially.Up to 2s intervals are allowed between the presses.        Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.                2N IP One Press 15 times the quick dial button on the unit.Up to 2s intervals are allowed between the presses.  Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.          2N IP Safety Press 15 times the first quick dial button on the unit.Up to 2s intervals are allowed between the presses.  Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.              2N IP Solo Press 15 times the quick dial button on the unit.Up to 2s intervals are allowed between the presses.  Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.        2N IP Style    This device has no physical quick dial button but you can use the touch display to enter the Network Setting.  Place your finger in the left-hand upper corner of the display for approx. 5 s.            2N IP Uni Press 15 times the first quick dial button on the unit.Up to 2s intervals are allowed between the presses.  Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.        2N IP Vario    The procedure is different according to number of buttons on the main unit.  1 button  Press 15 times the quick dial button on main the unit.Up to 2s intervals are allowed between the presses.      Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.        3 buttons Press buttons 1, 1, 1, 2, 2, 3 sequentially.Up to 2s intervals are allowed between the presses.       Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.        6 buttons Press buttons 4, 4, 4, 5, 5, 6 sequentially.Up to 2s intervals are allowed between the presses.       Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.                 2N IP Verso and 2N IP Verso 2.0 Press 15 times the first quick dial button on the main unit.Up to 2s intervals are allowed between the presses.  Switching is signalled with the sound signal, the device will restart automatically.  The device has now static IP address. You can repeat the procedure to return back to DHCP address.

Question 40

Time Profiles

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 create and assign time profiles to limit usage of various functions, e.g. calling a user or opening the door by the access method.   Prerequisites 2N IP Intercom or 2N Access Unit with the latest firmware;no additional license required (however some functions mentioned here can require a license)   Time Profiles description You can create up to 20 time profiles in the web interface, section Directory - Time Profiles,and use them globally during functions configuration.    In section Directory - Holidays, you can define the bank holidays and then assign them different time intervals in section Directory - Time Profiles.Permanent holidays are green and variable holidays (valid for the particular year only) are blue.    Apart mentioned 20 globally accessible time profiles, you may also set individual time profiles used just for specific function.     Examples of where you can use them User Phone numbers(only for 2N IP Intercoms)You can determine when to call a phone number of a user according to a set time profile.    User Access SettingsYou can restrict user access during a certain time.    Switch HoldAdditional GOLD license is requiredYou can determine how long you want to keep the switch triggered.    Multi-factor authenticationYou can set different authentication mode according to different time profile.    Automation functionAdditional GOLD license is requiredUse the ProfileState condition to limit triggering Action by the Event.

Question 41

Troubleshooting basics – Configuration backup, network trace, syslog and ping tool on 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. Dear customers, In case you have found any issue with the device, please report it to https://support.2n.com/. If you do not have access informations, contact your account manager.Or you can report your issue by creating a ticket - here. Reported issue should contain following information: Please describe us your issue in detail, so that we will be able to replicate the behaviour based on that description. Send us the description of the LAN topology, NATs, IP addresses, etc.  If you have an issue regarding electrical circuit please send us a diagram of your eletrical circuit. Including specifications of the device being controlled by 2N IP Intercom eg. Magnetic locks, Electro-magnetic locks, Lights etc.  If your issue can be clearly visible or heard eg. LED blinking, bad sound quality, please take a picture or record a video (eg. on a phone) and send us this behaviour. You can attach it to the e-mail or upload it to eg. WeTransfer, Dropbox or Google Drive and send us the download link.    Configuration backupNetwork trace Local Packet Capturing - "Short" traceRemote Packet Capturing - "Long" trace Local SyslogSyslog server Ping tool    Configuration backup How to back up the current device configuration can be seen in the picture below.   Backup and firmware update notice  Make sure to always back up your device's configuration before you start firmware update. Newer configuration file might not be compatible with your previous FW should you need to use it due to some compatibility issues etc.    Notice: It's highly recommended to always use the latest FW version available on the  2N webpage before you report a technical issue! The issue you might be facing may already be fixed.      Please always send us information about your intercom's FW version and its serial number.   Network trace How to capture network traces on 2N IP intercoms?   Buffer length warning Because the buffer for traces is limited, it is really necessary to start the trace right before you make the test call and then stop it before it reaches the maximum buffer size – 4096kB!    Caution: If there is a video stream active during the trace the files can grow large.   Local Packet Capturing - "Short" trace The advantage of the local packet capturing is that it is automatically launched upon boot up so it is possible to download the trace including already ended call while you have to manually launch the remote packet capturing. First of all, start the capture by clicking the "Start" button, make a call and stop the capture by clicking the "Stop" button, then click the "Download" button to download the trace file (hiptrace.pcap) and send it to us.        Remote Packet Capturing - "Long" trace Similarly, you can use remote packet capturing. This has no limit so it can be used for longer tests. Start the capture by clicking the "Start" button, choosing how long it should be traced for. Once the time limit is reached or stopped manually by the "Stop" button the trace will be downloaded automatically.    Send us the description of used LAN topology, NATs, IP addresses, devices you're trying to integrate with, etc. that might help in solving the issue.   Local Syslog You can either set up a Syslog server or use the local Syslog which can run up to 7 days (it can be interrupted at will). If the local Syslog is too large the beginning might be overwritten. Local Syslog is not suitable for troubleshooting sudden restarts as some of the messages might not be saved before the reboot. We recommend using a Syslog server for situations like these.  The controls are the same as with the network trace.   Syslog server  The 2N IP intercoms allow you to send system messages to the Syslog server including relevant information on the device states and processes for recording, analysis and audit. It is unnecessary to configure this service for common intercom operations.   The advantage of the external Syslog is that it captures logs even around the reboot (good for troubleshooting issues with sudden restarts etc.). Set the Server Address in our example we use 192.168.1.15 - IP Address of a PC where Syslog server is installed (such as Wireshark or Syslog Watcher)    Using SyslogWatcher - download trial hereStart the server - it will take a few seconds until you see any messages  Stop server - press after you are done with capturingExport - press this button to export messages to fileExport Settings - Choose the time from/to according to what 2N Tech support demands (1h, 24h) Custom files (CSV/XML/TXT/JSON/etc) - type of file  Export folder - choose the path to save the fileFilename - the name of the file (in default it is the date of Syslog capturing) -> export the file with .txt suffix and send it to us      Ping tool Ping tool allows you to ping internet addresses. This way you can check whether the device itself has a proper internet connection.

Question 42

Video issue - 2N IP Intercom does not send video during a call

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.   We will show you, how to resolve no video during a call from 2N IP Intercom.   Prerequisites 2N IP Intercom with a camera and the latest firmware,no additional license is required.SIP video phone to be called by 2N IP Intercom.   Resolving the issue Go to 2N IP Intercom web interface - homepage.Can you see the video preview from the camera?       If the answer is no video, please check, if your device should be really equipped by a camera;and eventually continue to this article: 2N IP Intercoms - Diagnostics and Troubleshooting   If the answer is yes, the video works there properly, please continue with next steps.    Call to another SIP video phone.Disconnect 2N IP Intercom from your SIP proxy (if it is connected to any) and call directly to your SIP video phone which supports codecs H.264 or H.263.If you can see the video now, please check settings of H.264 (or H.263, H.263+) codecs in your SIP proxy.More information in this article: Direct call without SIP Proxy registration   Try a lower resolution.Go to 2N IP Intercom web interface, section Calling - SIP 1 (call by sip:IPaddress) or Local Calls (call by device:DeviceID),in tab Video, set CIF resolution for the used codec, save and check the difference.    In the same section, check the Payload type settings.For example, Cisco CUCM requires payload type set to 98 or 99.In the Advanced SDP Settings, enable Use sendrecv Attribute for Video.      Are you familiar with PCAP (network packet capturing)?Then capture a network trace (more information in this article: 2N IP Intercoms - Diagnostics and Troubleshooting )and check the RTP packet flow. If you still have troubles with video transmission, please continue to this article:2N IP Intercoms - Diagnostics and Troubleshooting

Question 43

Virtual Card ID

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 set the Virtual Card ID for user identification to Wiegand after validation via the Bluetooth/biometric reader. Each user can have just one virtual card. The Virtual Card ID is a sequence of 6–32 characters: 0–9, A–F.  Prerequisites 2N IP Intercom or 2N Access Unit with the latest firmware and the Wiegand interface;no additional license is required.More information about Wiegand interface:   Wiegand interface - Function overview    Virtual Card ID to the user  In 2N device web interface, go to section Directory - Users,fill in the Virtual Card ID into the existing or new user´s User Cards part, it does not have to be the same as the RFID Card ID, which can be sent to Wiegand as well.       Sending Virtual Card ID to Wiegand Go to section Services - Access Control - Entry Rules and activate sending of the Virtual Card ID to Wiegand by selecting the Group that corresponds to the Wiegand module setting as we will show later.  Go to section Hardware - Extenders - Wiegand module and verify, that Output Wiegand Group matches the previous step setting.

Question 44

Virtual Numbers and Telephone Mode

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.   On 2N IP Intercoms, you can start the call also by the keypad or touch display. We will show you how to setup and use it in two different scenarios.   Prerequisites 2N IP Intercom with keypad or touch display and the latest firmware;no additional license is required.   Scenarios  Virtual Numbers Call the user by dialling e.g. an apartment number on the keypad, instead of selecting the user from the directory or using the Quick Dial Button. In 2N IP Intercom web interface, go to section Calling - General Settings - Outgoing Callsand enable Calling Virtual Numbers.      Go to section Directory and assign a virtual number to a user.      Use the virtual number on the keypad and start the call to the user by pressing 📞 symbol.       Telephone mode Dial SIP Proxy extensions directly,not available for 2N IP Style and 2N LTE Verso. 2N IP Intercom requires registration to SIP Proxy. More information in this article:   SIP Proxy registration on IP Intercoms In 2N IP Intercom web interface, go to section Calling - General Settings - Outgoing Callsand enable Telephone Mode.     Use the keypad to call the SIP Proxy extension by pressing 📞 symbol, then dial the extension number and confirm again by 📞 symbol.

Question 45

VLC media player - watch and record video from 2N IP Intercom

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.    2N IP intercoms integrate an RTSP server allowing for audio/video streaming to VMS and other camera systems. VLC media player is one of several programs which can be used to watch and record the video stream as well.   Prerequisites  2N IP Intercom with the latest firmware;additional GOLD License is requiredVLC media player the latest version installed in your computer;https://www.videolan.org/    2N IP Intercom - enabling RTSP server In IP Intercom web interface, go to section Services - Streaming - ONVIF / RTSP,enable RTSP Server and click the pencil icon to setup Stream URL.      Setup User Account for securing the stream.     If you would like to limit who can see the stream, fill in IP addresses to "Authorised IP address", then you will be able to watch the stream only from that IP addresses.        VLC media player - watch the RTSP stream  Open your VLC media player and go to Media - Open Network Stream... menu. Enter the whole IP Intercom´s RTSP Stream URL (incl. "rtsp://" at the beginning) and user account details.           If does not work properly, then please go to Tools - Preferences - Input / Codecs menu,switch to "RTP over RTSP (TCP)" value, save and try the stream again.      VLC media player - record the RTSP stream During running stream, go to Playback menu and click Record to start or stop recording.    The recorded videos are automatically saved to your videos directory (for Windows users:  C:\Users\Videos ).

Question 46

Web interface access - 2N IP intercoms

Accepted Answer

From an internet browser PREREQUISITES: Your computer and the 2N device which you want to access must be connected in the same Local Area Network.To access the web interface of a 2N device you will need its IP address. The easiest way to identify the IP address of your device is to find it in 2N Network Scanner. You can download this simple program here.As shown below, 2N Network scanner shows you all devices connected to the same LAN as your computer. You can search in the list by IP address, Serial Number, Display Name and Version.     STEPS: 1. Type or paste the IP address in the browser and press Enter or simply double-click its line in 2N Network Scanner. 2. Because of certificate settings in 2N devices, your browser will display a warning message. (Examples below.) Do not worry about this message and proceed to the login page. It is safe to do so. Click "Advanced" and continue to the website.         Once you proceed, the login page appears. In the top left corner and the top right corner, you can see the model name of the device. In the top right corner, you can also find the serial number of the device.  Default credentials are:Username: adminPassword: 2n In case the credentials were changed and you do not know them, the only way to access the device is to perform a factory reset, which deletes the current configuration. 3. Once you enter the correct credentials, click "Login". Now you are in the web interface of a 2N IP Intercom and you can configure your device.   Note: After a period of inactivity, you will be automatically logged out.   From My2N Web Platform Log in your My2N account and access the correct site. Go to Device detail page of your IP Intercom. Expand the 2N Remote Configuration Services section at the bottom by clicking the title. Click Open Configuration button.  Follow the instructions above from STEP 2.

2N IP Force 2.0

List of Faqs