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 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 3

2N IP intercoms, Access Units, IP audio units - Firmware upgrade

Accepted Answer

We always recommend having the latest firmware on your devices.  This article will guide you through the upgrade procedure,  even if you currently have a very old version.    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.   Prerequisities 2N OS device (IP intercom, answering unit, or access unit) Internet connectivity for the 2N OS device in case of the online upgrade method   Feature properties The firmware upgrade does not delete your current configuration, but we recommend saving a backup configuration before starting. However, the process updates the configuration, which may render it incompatible with previous firmware versions.  You can select from online and offline upgrade method. 2N OS device also checks the firmware file to prevent upload of a wrong or corrupted file.     Click here for instructions for firmware 3.0 and newer. Read more about the differences in long-term support and active track 2N OS.   Firmware 2.50 and older (LTS) Configuration backup Configuration backups from version 2.45.x and higher are incompatible with 2.44.x and lower. We recommend saving a backup configuration file before each upgrade. You can proceed it in System - Maintenance.    Online upgrade method 2N OS device can download the right latest firmware file by itself.Just go to System - Maintenance and click on Upgrade Now button when the interom says that a new version is available.In case the current firmware is too old, it will upgrade the intercom to the next "intermediary" version. Use this procedure multiple times until the interface informs you that you are running the latest firmware version.In case you do not have Internet connection, follow the steps for offline upgrade.    You can read release notes here. Click on Proceed to start the upgrade.    2N OS device will automatically get restarted and new firmware will then be available. The whole update process takes less than a minute.  Offline upgrade method Depending on which 2N OS device model you have, please follow one of these sequences: For IP Force, IP Safety and IP Vario:-> 1.11.0 -> 1.16.1 -> 2.5.0 -> 2.9.1 -> 2.15.2 -> 2.17.1 -> 2.18.1 -> 2.31.1 -> 2.39.2 -> 2.44.0 -> the latest oneFor IP Style, IP Verso 2.0, IP Force 2.0 and IP One:-> 1.11.0 -> 1.16.1 -> 2.5.0 -> 2.9.1 -> 2.15.2 -> 2.17.1 -> 2.18.1 -> 2.31.1 -> 2.39.2 -> 2.42.0 -> the latest oneFor all other 2N OS device models:-> 1.11.0 -> 1.16.1 -> 2.5.0 -> 2.9.1 -> 2.15.2 -> 2.17.1 -> 2.18.1 -> 2.31.1 -> 2.39.2 -> the latest one All intermediary firmware versions for each 2N OS device can be downloaded here: 2N IP intercoms IP Vario, IP Safety, IP ForceIP Verso, IP Solo, LTE VersoIP Audio KitIP BaseIP UniIP Video KitIP OneSentrioIP StyleIP Verso 2.0 2N Access Units Access UnitAccess Unit 2.0Access Unit MAccess Unit QR 2N answering units ClipIndoor CompactIndoor TalkIndoor ViewIndoor View WiFi 2N IP audio units SIP Speaker HornSIP Speaker, SIP Converter  Then use the offline upgrade method guided below.When you are on the last intermediary version, you can use the online upgrade method mentioned later as well.Please note that some intercoms were launched later and thus some older firmware versions may not exist for them. Simply continue with the next higher version than it currently has. Go to System - Maintenance and click on Upgrade Firmware button.    Select the firmware file and start the upgrade.    The intercom will automatically get restarted and new firmware will then be available. The whole update process takes less than a minute.        Downgrade firmware If needed, it is possible to downgrade the firmware version to the lower one by uploading the older firmware file. In version 2.24, the Directory structure was changed and downgrading from versions 2.24 and above to versions lower than 2.24 will delete your Directory. Downgrading from versions 2.x to versions 1.x is not supported. If you downgrade the firmware on new devices with Axis ARPTEC processor (e.g. IP Style, IP Verso 2.0, IP One, IP Force 2.0), it will delete the current configuration.    Firmware 3.0 and newer Configuration backup Configuration backups from version 2.45.x and higher are incompatible with 2.44.x and lower. We recommend saving a backup configuration file before each upgrade. You can proceed it in System - Maintenance.    Online upgrade method 2N OS device can download the right latest firmware file by itself.Just go to System - Maintenance and click on Update button when the interom says that a new version is available.In case the current firmware is too old, it will upgrade the intercom to the next "intermediary" version. Use this procedure multiple times until the interface informs you that you are running the latest firmware version.In case you do not have Internet connection, follow the steps for offline upgrade.    You can read release notes here. Click on Update to start the upgrade.    2N OS device will automatically get restarted and new firmware will then be available. The whole update process takes less than a minute.   Offline upgrade method Depending on which 2N OS device model you have, please follow one of these sequences: For IP Force, IP Safety and IP Vario:-> 1.11.0 -> 1.16.1 -> 2.5.0 -> 2.9.1 -> 2.15.2 -> 2.17.1 -> 2.18.1 -> 2.31.1 -> 2.39.2 -> 2.44.0 -> the latest oneFor IP Style, IP Verso 2.0, IP Force 2.0 and IP One:-> 1.11.0 -> 1.16.1 -> 2.5.0 -> 2.9.1 -> 2.15.2 -> 2.17.1 -> 2.18.1 -> 2.31.1 -> 2.39.2 -> 2.42.0 -> the latest oneFor all other 2N OS device models:-> 1.11.0 -> 1.16.1 -> 2.5.0 -> 2.9.1 -> 2.15.2 -> 2.17.1 -> 2.18.1 -> 2.31.1 -> 2.39.2 -> the latest one All intermediary firmware versions for each 2N OS device can be downloaded here: 2N IP intercoms IP Vario, IP Safety, IP ForceIP Verso, IP Solo, LTE VersoIP Audio KitIP BaseIP UniIP Video KitIP OneSentrioIP StyleIP Verso 2.0 2N Access Units Access UnitAccess Unit 2.0Access Unit MAccess Unit QR 2N answering units ClipIndoor CompactIndoor TalkIndoor ViewIndoor View WiFi 2N IP audio units SIP Speaker HornSIP Speaker, SIP Converter  Then use the offline upgrade method guided later.When you are on the last intermediary version, you can use the online upgrade method mentioned later as well.Please note that some intercoms were launched later and thus some older firmware versions may not exist for them. Simply continue with the next higher version than it currently has. Go to System - Maintenance and click on Firmware upload button.    Select the firmware file and start the upgrade.    The intercom will automatically get restarted and new firmware will then be available. The whole update process takes less than a minute.     Downgrade firmware If needed, it is possible to downgrade the firmware version to the lower one by uploading the older firmware file. In version 2.24, the Directory structure was changed and downgrading from versions 2.24 and above to versions lower than 2.24 will delete your Directory. Downgrading from versions 2.x to versions 1.x is not supported. If you downgrade the firmware on new devices with Axis ARPTEC processor (e.g. IP Style, IP Verso 2.0, IP One, IP Force 2.0), it will delete the current configuration.In case the device is on firmware version 2.47 and higher, it is not possible to downgrade the firmware below version 2.47.

Question 4

2N IP Intercoms - Diagnostics and Troubleshooting

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 found an issue with our 2N IP Intercom? Don't worry, we will show you diagnostic tools and troubleshooting options to make everything running as expected.   Prerequisities 2N IP Intercom with the latest firmware,no additional license is required for any of mentioned step.   What you can try yourself Before contacting the technical support team (which will be described later on), you can try some few things yourself.Depending on your technical skills, you can choose from basic or advanced methods. Click here for instructions for firmware 3.0 and newer. Read more about the differences in long-term support and active track 2N OS. Firmware 2.50 and older (LTS) Basic methods Have you already restarted the device? You can proceed it also from the device web interface, System - Maintenance section.    Is there already the latest firmware? We always recommend to keep the system up-to-date. You can follow instructions in this article: 2N IP Intercoms - Firmware upgrade    Would you like to verify that the microphone and speaker are working properly?In section Services - Audio Test, let the speaker beep and the microphone pick it up .If all right, you will see the Passed test result.    You can verify the network address accessibility, for example to be sure IP Intercom can access the Internet or another device in the local network.In section System - Diagnostics you can run Ping tool, you may already use it in your computer command line.     Before contacting the technical support team, please always prepare Diagnostics package.It contains all the needed information, incl. device configuration, system logs and network traffic.Just start recording, replicate the issue, download the package.The records will be kept even if you reboot the device.      Advanced methods In system logs, you can see all the device states and processes (e.g. pressing a button, switch activation, calling answering unit).For a clear overview, go to section State - Events, where you can also filter the events.    It is also possible to download more detailed syslog file, especially for technical support purposes, in section System - Diagnostics - Syslog.This way will keep the records even if you reboot the device.When recording a Syslog for troubleshooting calls, in most cases is needed to enable Extended SIP logging. You can find it in Calling -> General Settings -> Advanced Settings -> Extended SIP Logging       Are you familiar with the network packet capturing (pcap)? Then you can start it and after replicating the issue also download here.Local Packet Capture Automatically launched upon boot upSaving into the device itself; limited buffer size, can be quickly utilizated if there is active video stream during capturing  Remote Packet Capture Manual launchingSaving into your computer via the web browser; buffer is not limited - recommended for longer capturing      In some cases can be helpful to return the device settings to the factory values. Please always backup your configuration first.You can follow instructions in this article: 2N IP Intercoms - Factory reset   Firmware 3.0 and newer Basic methods Have you already restarted the device? You can proceed it also from the device web interface, System - Maintenance section.    Is there already the latest firmware? We always recommend to keep the system up-to-date. You can follow instructions in this article: 2N IP Intercoms - Firmware upgrade    Would you like to verify that the microphone and speaker are working properly?In section Integration - Audio, let the speaker beep and the microphone pick it up .If all right, you will see the Passed test result.    You can verify the network address accessibility, for example to be sure IP Intercom can access the Internet or another device in the local network.In section System - Diagnostics you can run Ping tool, you may already use it in your computer command line.     Before contacting the technical support team, please always prepare Diagnostics package.It contains all the needed information, incl. device configuration, system logs and network traffic.Just start recording, replicate the issue, download the package.The records will be kept even if you reboot the device.      Advanced methods In system logs, you can see all the device states and processes (e.g. pressing a button, switch activation, calling answering unit).For a clear overview, go to section System - Event log, where you can also filter the events.    It is also possible to download more detailed syslog file, especially for technical support purposes, in section System - Diagnostics - Syslog capture.This way will keep the records even if you reboot the device.When recording a Syslog for troubleshooting calls, in most cases is needed to enable Extended SIP logging. You can find it in Calling -> Calls configuration -> Advanced Settings -> Extended SIP Logging      Are you familiar with the network packet capturing (pcap)? Then you can start it and after replicating the issue also download here.On-device network packet capture Automatically launched upon boot upSaving into the device itself; limited buffer size, can be quickly utilizated if there is active video stream during capturing  Network packet capture downloadManual launchingSaving into your computer via the web browser; buffer is not limited - recommended for longer capturing      In some cases can be helpful to return the device settings to the factory values. Please always backup your configuration first.You can follow instructions in this article: 2N IP Intercoms - Factory reset We are happy to help In case of any issue, feel free to contact the technical support of your local distributor or directly contact the 2N technical support team. Here are mentioned all the ways how you can contact the 2N technical support team: https://www.2n.com/support/technical-support We will be glad, if you can tell us following information for the smooth process, it will make it easier for both parties. Serial number of the devicesVersion of the firmware in the devicesProvide us the Diagnostics package from the device.We already mentioned the procedure in this article (at the end of the basic diagnostics methods).Please describe us your issue in detail to let us understand and replicate it at our side.If your issue can be clearly visible or heard eg. LED blinking, bad sound quality, please take pictures or record a video (by your phone) for us.You can attach it to the e-mail or upload it to your cloud storage (e.g. OneDrive or Google Drive) and send us just the download link. Please provide 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 that, incl. specifications of the controlled device (lock, gate, lights etc.).

Question 5

2N IP Intercoms - Factory reset

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, If needed, you can return the device to the factory settings. In case you can access the web interface (know the login password), you can backup the configuration and use the software reset with possibility to keep the network settings. Otherwise there is available the hardware reset.   The factory reset erases the licence key (if entered) as well, we recommend you to store it for entering it back after the procedure.In case of on-line installation, the device can get the license back from our license server by itself.   Prerequisites 2N IP Intercom with the latest firmware if possible(especially in case of software reset)   Software reset Click here for firmware 3.0 and newer. Read more about the differences in long-term support and active track 2N OS. Firmware 2.50 and older (LTS) At first backup your configuration in IP Intercom web interface, section System - Maintenance.    Now on the same place click on Reset Configuration button and confirm it, you can choose if keep the network settings.The procedure is completed in a while and you are asked for the new login password.       Firmware 3.0 and newer At first backup your configuration in IP Intercom web interface, section System - Maintenance.    Now on the same place click on Reset Configuration button and confirm it, you can choose if keep the network settings.The procedure is completed in a while and you are asked for the new login password.   Hardware reset Please click on the part (model) you are interested in and it will be displayed for you.    2N IP Audio/Video Kit Press and hold the RESET button.     Watch and hear (if connected speaker) this LED / beep sequence   approx. 15 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 seconds__  _     __  ___  _     __  ___  _     __  ___  _     __  ___  _     __  _🔈 )🔈 ))🔈 )))🔈 ))))  Release the RESET button immediately when the last step starts (when you hear 4 beeps).If pressed longer till finishing boot, then factory reset is not proceeded.        2N IP Base Press and hold the RESET button.   Watch and hear this LED / beep sequenceapprox. 15 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 seconds__  _     __  ___  _     __  ___  _     __  ___  _     __  ___  _     __  _🔈 )🔈 ))🔈 )))🔈 ))))  Release the RESET button immediately when the last step starts (when you hear 4 beeps).If pressed longer till finishing boot, then factory reset is not proceeded.      2N IP Force/Safety The procedure depends on version of PCB, you can find this information here:    PCB version 555v5 (the actual procedure) Press and hold the RESET button.   Watch and hear this LED / beep sequence approx. 15 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 seconds__  _     __  ___  _     __  ___  _     __  ___  _     __  ___  _     __  _🔈 )🔈 ))🔈 )))🔈 ))))  Release the RESET button immediately when the last step starts (when you hear 4 beeps).If pressed longer till finishing boot, then factory reset is not proceeded.      PCB version 555v4 and 555v3 Press and hold the SW1 button.Wait for the first sound signalization and then release the button.     PCB version 555v2 Disconnect the device from the power supply. Move the short-circuit jumper on connector X6 into the Default setup position.                   Reconnect the power supply and wait for the signalling sound.  Disconnect the device from the power supply.   Move the short-circuit jumper on connector X6 into the Normal operation position.             Reconnect the power supply.        2N IP One  Disconnect the device from the power supply.  Press and hold the CONTROL button.    Connect the device to the power supply.  Keep holding the button for a few seconds and then release it.       2N IP Solo Press and hold the RESET button.    Watch and hear this LED / beep sequence approx. 15 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 seconds__  _     __  ___  _     __  ___  _     __  ___  _     __  ___  _     __  _🔈 )🔈 ))🔈 )))🔈 ))))  Release the RESET button immediately when the last step starts (when you hear 4 beeps).If pressed longer till finishing boot, then factory reset is not proceeded.        2N IP Style  Disconnect the device from the power supply.  Press and hold the CONTROL button.    Connect the device to the power supply.  Keep holding the button for a few seconds and then release it.      2N IP Vario The procedure depends on version of PCB, you can find this information here:      PCB version 535v8 (the actual procedure) Press and hold the RESET button.    Watch and hear this LED / beep sequence approx. 15 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 seconds__  _     __  ___  _     __  ___  _     __  ___  _     __  ___  _     __  _🔈 )🔈 ))🔈 )))🔈 ))))  Release the RESET button immediately when the last step starts (when you hear 4 beeps).If pressed longer till finishing boot, then factory reset is not proceeded.   PCB version 535v5, 535v2, 535v1, 530v2  Switch 2N  IP Vario off.   Connect the jumper into the resetting (default setting) position(put the display switch into the F_RES position in the display-equipped models with 535v1 and 535v2 board versions).     Switch 2N  IP Vario on and wait for the start signalling sound.   Switch 2N  IP Vario off.   Remove the jumper from the resetting (default setting) position(put the display switch into the NORMAL position in the display-equipped models with 535v1 and 535v2 board versions).     Switch 2N  IP Vario on.          2N IP Verso Press and hold the RESET button.    Watch and hear this LED / beep sequence approx. 15 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 secondsapprox. 3 seconds__  _     __  ___  _     __  ___  _     __  ___  _     __  ___  _     __  _🔈 )🔈 ))🔈 )))🔈 ))))  Release the RESET button immediately when the last step starts (when you hear 4 beeps).If pressed longer till finishing boot, then factory reset is not proceeded.        2N IP Verso 2.0  Disconnect the device from the power supply.  Press and hold the DEFAULT button.     Connect the device to the power supply.  Keep holding the button for a few seconds and then release it.          2N IP Uni Press and hold the RESET button for more than 20 seconds (eventually for 40 seconds if there is firmware 2.19 and older).

Question 6

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 7

2N IP Intercoms - IP Address retrieval

Accepted Answer

2N IP Intercoms - IP Address retrieval You have to know your intercom IP address to log in to the integrated web server. Upon purchase or factory reset, the device is set to the dynamic IP address mode – it retrieves the IP address automatically if there is a properly configured DHCP server in the LAN. If no DHCP is available, you can operate it in the static IP address mode.    You can retrieve the IP address by our 2N® Network Scanner 2N® Network Scanner - Locating 2N devices in the network   Or you can let the intercom tell you the IP address by itself (guided in this article).   Prerequisities 2N IP Intercom connected to your local network. Possibility to reboot the device.   How to retrieve the IP address by the inbuilt speaker Reboot the 2N IP Intercom (disconnect it from the power supply and reconnect again) Once the device is booted (you can hear the second sound signal), do the specific procedure within 30 seconds described later for each IP intercom model. If you miss this time period, it is necessary to reboot the device again. 2N IP Intercom reads its IP address via its inbuilt speakers.If you hear 0.0.0.0, it means the intercom has not obtained the IP address from the DHCP server(DHCP server is not available, not presented in network or does not have any free IP address to assign).    Specific procedure for each IP intercom model 2N® IP Vario press 5x the quick dial button(versions with 3 or 6 buttons - use the middle quick dial button on the right side)    2N® IP Force, 2N® IP Safety press 5x the first quick dial button  2N® IP Verso, 2N® IP Verso 2.0, 2N® IP Solo press 5x the quick dial button on the main unit      2N® IP Base press 5x the first quick dial button    2N® IP Uni press 5x the first quick dial button    2N® IP Onepress 5x the quick dial button           2N® IP Style Wait until the end of the introductory animation on the display after starting/restarting the device. The moment the home screen appears (after approx. 20 s), place your finger in the left-hand upper corner of the display for approx. 5 s.     2N® IP Audio, 2N® Video Kit press and hold the RESET buttonwait until 1 beep is heard (the red and green LEDs go on simultaneously on the device, located between LAN connector and RESET button)release the RESET button immediately

Question 8

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

Accepted Answer

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

Question 9

2N Student Monitoring System with 2N IP Intercoms

Accepted Answer

Info   This FAQ describes, how you can configure 2N VoiceBlue Next gateway (You can also use 2N VoiceBlue Max, 2N BRI Lite/Enterprise or 2N StarGate and 2N BlueTower as the configuration is basically the same) together with 2N IP intercoms and 2N Access Unit for the school scenario. You can configure the intercom to send SMS message through the gateway as a confirmation that a student has arrived to school. Once student will swipe the card to open the door, SMS to a parent cellphone is sent. Below you can find a step by step configuration for both devices. FW version of 2N IP Intercom has to be v2.16 or higher and for 2N VoiceBlue Next has to be at least v1.26.3. Please keep in mind that even when you have multiple entrances with intercoms, you still need only one gateway!            How to configure 2N VoiceBlue Next  Note: As the very first step please make sure that the license for Email2SMS feature is uploaded into your 2N VoiceBlue Next gateway. This license is sold as a package for 10 users (you can buy licence for 10, 20, 30, etc. users) and you can have up to 200 licensed users in the gateway. If you want to verify whether you have the correct license uploaded in your gateway, go to section "Management -> License key". You should see the licenses called SMSE and SMSUx and in the "Active" row. SMSE indicates that Email2SMS function is enabled and SMSUx indicates number of licensed users where x stands for this number (see the picture below). If there's not a license for Email2SMS (SMSE) then you won't see the "Messaging" on the top menu. For each intercom you need one Email2SMS licence in the gateway!    Configuration steps  Modules grouping In the first step go to section "Messaging –> Modules grouping" and enable SMS server – check the appropriate check-box. Next add GSM modules to SMS groups in order to facilitate incoming/outgoing SMS routing. It can be done based on your requirements e.g. according to the GSM provider, etc. The last step in this section is to assign SMS groups created in the previous step to the User groups if you want to use messaging with different routing rules. The GSM gateway can contain up to 4 User groups and up to 4 SMS groups.      Add User As a next step you need to skip to the section "Messaging –> Users", click on the "Add" button and create new SMS user(s) who will send and receive SMS messages. There are several parameters in this section which have to be set. You need to select the communication protocol for SMS processing (SMTP/POP3) and assign the user to User group. Also do not forget to define the Login name (without domain) and Password to log into the SMS server via your e–mail client. You can see all parameters from this section in the picture below where was created user "Helios IP" with the login "SMS" and password "Helios". Once you fill in all parameters, click on the "OK" button. The user will be added and after that you have to make one more click to the "Save settings" button in the bottom right corner of the page (blue circle label in the picture).    General settings Set the parameters of domain in the "Messaging –> User Group –> General settings" sub-menu. The domain is automatically assigned to the user´s login in the selected User group and it represents the user´s e–mail address. In this section you can also define some parameters for POP3 and SMTP such as subject of email, maximum SMS per email, next you can add “From” field as well as “Subject” to SMS (see the picture below). In our example (in the previous step) a new user was created with login name "SMS". In this section we will set domain as: gateway.com. Then the e-mail address of the user with rights to access the SMS server will be SMS@gateway.com. The “@” character is completed automatically and it is not included in the domain´s field.    Outgoing SMS routing As a last step you need to specify routing rules for outgoing SMS – it is done in the "Messaging –> User Group –> Outgoing SMS routing" menu where you click on the "Add" button. In this section you will specify mainly these parameters:  Message to SMS group – the SMS group via which the outgoing SMS will be routed  Action type – define how to process outgoing SMS. You can choose from two options: Submit from user (SMS can be sent only from selected users) or Submit from all users (enable sending SMS from all the SMS group users).  Submit from user – choose a user who can send SMS (this is used only if "Submit from user" was selected)  Time limitation - here you can set time limitation for when is the routing active. So for instance you can set this only for morning, when students are arriving to school.  Day limitation - choose days when the routing will be active. For instance only business days when school is opened.  Note: do not forget to enable the SMS server as shown in the first step (there is a check-box)! In the picture below there is shown settings for User Group 1. Messages (emails) from all users in this User group are routed via SMS group 1. It means that these emails will be transferred to SMS and sent only via GSM modules assigned to SMS group 1. It is GSM module 2 in our example (as you can see in the picture from step 1).      How to configure 2N IP intercoms Note: Please keep in mind that Enhanced integration (up to v2.35) or Gold (v2.35 onwards) license is needed in order to use email features!  Configuration steps  Add user firmware v2.24.0 and later:Go to section "Directory->Users" choose a user or create a new one. Fill "Name" (use name of the student, it will be used in the SMS), "E-mail" (email has to be in format phone_number@domain, so in our case 721642053@gateway.com for instance, number is phone number of the parents cell phone), "Card ID" (fill ID of the students card or fob).      SMTP configuration Go to section "Services->E-mail->SMTP" and check "SMTP E-Mail Service Enabled". Then fill "Server Address" (IP address of the gateway) if you did not change port in the gateway, then leave it as it is - port 25. Then fill "Username" and "Password", use credentials you used for user you created in the gateway, in case of Username you have to use domain as well. So credentials for this example are SMS@gateway.com/Helios. In the last step fill some email to field "From Address". As you are sending SMS messages in this scenario, it does not matter what you will fill there, you can even fill there address you made up, however this field is mandatory and has to be filled.    SMS configuration Go to section "Services->E-Mail->E-Mail on Access".  Fill administrator e-mail address in the section Send to E-mail Address. In this section set "All Accesses" for "Send E-Mail At". To the field "Body" fill the message you want to send when student arrives to school. You can see example in picture below, we used variables $User$ (this variable will be substituted by name of the student who used the card) and $DateTime$ (this variable will add current time and date to the message). Please find list of available variables below:  $User$ - Called username  $DateTime$ - Current date and time  $AuthId$ - User authentication ID  $DeviceName$ - Intercom identification  Last thing you have to do in this section is uncheck "Attach Snapshot".  If you will swipe valid card now, 2N IP Intercom will send and email to the gateway and it will send SMS message to the predefined cell phone.   Set time on 2N IP intercom Go to section "System->Date & Time", pick the right "Time Zone" and if possible, you can synchronise the intercom with NTP server. If NTP server is not available, then you can synchronise the intercom with your browser by clicking on "Synchronise with browser".     Switch configuration You also need to configure the intercom to open the door once the student swipes a card or fob. Go to section "Hardware->Extenders", find your card reader and again choose on of the switches for "Associated Switch".     Once you will set appropriate switch to be controlled by the card reader, then you can configure the switch itself. Go to section "Hardware->Switches" and pick Switch you choose before. If switch is not enabled, then do so by checking "Switch Enabled". There are three the most important settings for the switch. By "Switch-On Duration" you can define for how long the switch will be activated. "Controlled output" define which physical output will be controlled by the switch, you can choose from available relays or active 12V output. By "Output Type" you can define whether you are using normal locks (Normal) or inverted locks (Inverted).

Question 10

Access key - How to configure on the 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 1.0 and 2N Indoor Touch 2.0 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.    How to set the Access Key in the 2N Intercom  How to set the Access Key in the 2N Indoor Touch 1.0  How to set the Access Key in the 2N Indoor Touch 2.0  How to add Intercom units to the Indoor Touch device    How to set the Access Key in the 2N Intercom Navigate to the section Calling (1), Local Calls (2),  Configuration - Connection to answering units (3)Fill in the "Access Key" field, to enable authentication for the 2N Helios IP Mobile application.You can add up to 3 Access Keys as shown below:   How to set the Access Key in the 2N Indoor Touch 1.0 Once the 2N Indoor Touch 1.0 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 Helios 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 same Access Key in the application first. Go to the section Settings (2), enter the Indoor Touch Settings (3) and set the same key as set on the intercom side, see the pictures below:    Fill out the Access Key (4) with the same value as you have set in the Intercom:    How to set the Access Key in the 2N Indoor Touch 2.0 Once the 2N Indoor Touch 2.0 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 "Intercoms" 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 same Access Key in the application first. Go to the section Settings (2):          Enter the 2N IP Mobile Settings (3) and set the same key as set on the intercom side, see the pictures below:  Fill out the Access Key (4) with the same value as you have set in the Intercom:  How to add Intercom units to the Indoor Touch device The application automatically scans your LAN network and searches for all connected 2N IP Intercoms with the same Access Key. You can easily add them in the "Devices" section by clicking on the "+" button (5).    By clicking on the specific row in the LAN devices list you can add selected intercoms (6):    By clicking on the checkbox in the right upper corner you can add all of them at once:      By clicking on the confirmation button (7) you have just added the desired local devices to the list:    The application is ready to call:

Question 11

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 12

Automation, Black/whitelist - How to block or allow specific numbers to call an 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.       Our intercoms don't support black/whitelisting by default. However, you can do it using a PBX or automation. If you'd like to use automation, you'll need GOLD license.  Basic setup — information The Number parameter at the CallStateChanged event can contain a phone number or an IP address. The following is an example of a whitelist. If you'd like to make a blacklist, just swap action AnswerCall for the EndCall one. Please note that it's better to set up a whitelist, since blacklists can be easily bypassed by changing your number to a different one. For whitelisted values, you need to know the exact number that can get through.   Whitelist — single number       Whitelist — multiple numbers       Blacklist — single number      Firmware & License info  2N OS v2.44 with GOLD license  Last updated on 29th of August 2024

Question 13

Automation, Calling two numbers from 2N IP Intercom over GSM gateway with a single SIM card

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.  Target scenario This manual describes how to call two GSM numbers from 2N IP intercom over GSM gateway with one SIM card only. The scenario is that we would like, after pushing the button on the intercom, make a call to a GSM number (number 1) and if this call is not answered, intercom starts ringing the next number. If this were configured in a standard way, i.e. assigning numbers to the user and using Group calling, intercom would get busy tone when trying to reach the second number. This is caused by limitations of GSM technology — any GSM call takes way longer (few seconds) to hang up. On the other hand, SIP call is hung practically immediately. Therefore there must be added a delay between hanging up the first call and making the second call. This scenario requires to be configured in Automation:      Variables  KeyPressed - defines which key must be pressed to begin the sequence. In this example, Key 1 (first intercom button) is used.  BeginCall 1 - here you can define which GSM number or user must be first called. 123456 is used as an example number in this case.  BeginCall 2 - here you can define which GSM number or user must be called after nobody answered on the first number. 456789 is used as an example number in this case.  Delay 1 (D1) - defines how long will it ring on the first GSM number.  Delay 2 (D2) - must be always higher than Delay 1. D2-D1=delay between hanging up on the first number and making a call to the second number. We recommend 5 seconds difference to make sure the first GSM call is properly hung.  Delay 3 (D3) - must be always higher than Delay 2. D3-D2=ring time when ringing on the second GSM number.  Rest of the variables must be set exactly as you see on the picture above.   Firmware & License info  2N OS v2.44 with GOLD license  Last updated on 11th of July 2024

Question 14

Automation, DoorOpenTooLong - Securing door against excessively long opening 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.   Securing the door against being open for too long is possible on 2N IP Intercoms . This feature is very useful for buildings with you have doors without handle (only with a knob) and you want to increase the security. It can be useful in banks, financial centers, offices, labs, server rooms and many others. Just imagine that you have door lock connected to one of relays in 2N IP Intercom and also door magnetic contact. The magnetic contact is cut off when the door is open. If that takes longer than the configured time (for example 15 seconds), the 2N IP Intercom will recognize it and will trigger an alarm.    How to set it up?  All necessary steps for settings of this feature are shown in the figures below. You will have to configure one switch, an automation and you will also have to use one INPUT.  It is also required to own a GOLD license for the 2N IP Intercom.   How to configure Switch 1  This switch controls the OUTPUT 1 to which the door lock connected. It is set in Monostable mode which means that after activation of this switch the door is door opened for 5 seconds (it may be changed depending on your specifications).     How to configure the security feature  You need to enable feature Door Open Too Long Detection for the specific Switch (in our case for Switch 1) and set which INPUT is the magnetic door sensor connected to.     How to set up Automation section  The settings blow mean that when the 2N IP Intercom detects a logical change in the INPUT from the magnetic lock and the door will stay open for more than 60 seconds, the automation will trigger an alarm sound or any other defined action (such as sending an HTTP command, an e-mail etc.      Firmware & License info  2N OS v2.44 with GOLD license  Last updated on 23rd of August 2024

Question 15

Automation, Multicast - Configuring Lock/Unlock all feature 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.   "Lock all" or "Unlock all" features are very useful once you need to activate all switches (lock or unlock - it depends on the settings of switches made in section "Basic settings -> Switch X") connected to 2N IP Intercoms in your network. Just pick a master 2N IP Intercom which will send multicast request to all connected intercoms after you enclose predefined RFID card or enter a specific code from your phone or keypad. This feature is very helpful when there's a fire in the building or when you face any danger inside the building and you need to evacuate all the people. In that case you enclose the card to RFID card reader and all doors will be opened. Lock all and unlock all features can be used especially in schools, factories, offices and other large places where you have many intercoms.   How to set up 2N IP Intercom to send multicast requestAll necessary steps for settings of Lock all feature are shown in the figure below:  The settings above mean that if anybody encloses the RFID card (ID of this card has to be 2800A6FC50) to the card reader then two actions happen simultaneously. During the first action multicast request is sent to all other intercoms (this command is sent to multicast IP address 235.255.255.250: 4433 which is set by default). The second action activates the switch connected to this intercom (this setting is optional and it depends whether you have any switch connected to this 2N IP Intercom). How to set up 2N IP Intercom receiving multicast requestsSettings for all other 2N IP Intercoms which accept multicast requesst and trigger specific action is shown in the picture below. First of all you need to specify the command that will trigger actions – this command has to be the same as the one sent in “MulticastRequest” from the previous figure (accepted in IP address 235.255.255.240:4433 by default). Based on the configuration below, Switch 1 is activated and also predefined user sound is played (e.g. any announcement for evacuation, alarm, siren, etc.).

Question 16

Automation, Multicast paging - How to configure paging from 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.   Paging from 2N IP Intercom is a feature that can be used for emergency calls or just for any announcement that will be sent to all other intercoms (or to specific group of intercoms). These devices have to receive multicast stream on predefined multicast IP address and port. Then you just press a button on 2N IP Intercom and you can start talking to other intercoms, play announcements or play any emergency tones (e.g. for evacuation of the building).    How to set up 2N IP Intercom which will send multicast  The settings above mean that if any user presses the quick dial button 5 on the 2N IP Intercom, then the user 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 all devices that are listening on the specific IP address and port (in our example: IP address is 239.0.0.239 and port is 21212). If you want to stop multicast traffic, you just press the quick dial button 5 again but for such behaviour you have to the use two conditions as shown in the figure above.  How to set up receiving on 2N IP IntercomsIf you want to receive a multicast traffic on your 2N IP Intercoms, you have to set specific multicast IP address and port. In our example IP address 239.0.0.239 and port 21212 are used. This setting is shown in the figure below.   As the next step go to the "Services->Automation" section and configure that the 2N IP Intercom will play user sound once it receives a specific multicast request. In our example user sound #2 recorded in the intercom is played.

Question 17

Automation, Multicast - Receiving multicast paging from up to 5 sources

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.   Each 2N IP Intercom can receive and send one multicast stream without any license. However, if you need your intercom to listen to multiple sources – maybe up to five at once (or send multicast to different addresses), then you will need an Enhanced Integration (up to v2.35) or Gold license (v2.35 onwards), which will allow you to set up the functionality via Automation. Such scenario may be useful, for example, in an area with several multistorey buildings with several departments, where:  the intercoms in the 1st building will listen to multicast at the address 224.1.0.0 and port 11000,   the intercoms in the 2nd building will listen to multicast at the same address (or different – e.g. 224.2.0.0) and port 12000, etc.,   the intercoms on the 1st floor of the 1st building will listen, as well, to the multicast again at the same address (or different – e.g. 224.1.1.0) and port 11100,   the intercoms on the 2nd floor of the 1st building will listen, as well, to the multicast again at the same address (or different – e.g. 224.1.2.0) and port 11200, etc.   the intercoms in the 1st department on the 1st floor of the 1st building will also listen to multicast, e.g. at address 224.1.1.1 and port 11110,   the intercoms in the 2nd department on the 1st floor of the 1st building will also listen to multicast, e.g. at address 224.1.1.2 and port 11120, etc.   and at the same time the intercoms in all buildings, floors and departments will listen to multicast, e.g. at address 224.0.0.0 and port 10000.  In other words, in such scenario, each 2N IP Intercom listens on 4 different multicast addresses and ports at once. There must be no odd port numbers used (e.g. 10001, 10003, 10011 etc.)  How to set up the 2N IP Intercom to receive multicast paging from up to 5 sources?  Navigate to "Services->Streaming->Multicast->Multicast Audio Receiving" (see image below)  We will adjust the following parameters (eg. the multicast source that will be listened to by intercoms in all buildings together), thus enabling reception from one common source:Multicast Receiver Enabled:  ✔  Receive IP Address: 224.0.0.0Receive Port: 10000Codec: the corresponding codec (which was selected for the respective multicast paging as well)   Navigate to "Services -> Automation" section -> select a free function -> create and save the given automation (see the picture below).Connect the required number of "StartMulticastRecv" blocks according to how many multicast addresses and ports, respectively, you want to be able to receive multicast streams from at once.We can set up reception from up to 4 other sources as we have channels 0 - 3 available here, each of which can be used only once.The example below shows what the automation in the intercom would look like on the 1st department of the 3rd floor in the 2nd building (according to the scenario described in the introduction).Then reboot the intercom "System -> Maintenance" - Restart, because in this case we have the "Rebooted" event set. Firmware & License info  2N OS v2.44 with GOLD license  Last updated on 25th of August 2024

Question 18

Automation, UnauthorisedDoorOpen - Securing doors against unauthorised door opening 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.       Securing the door against unauthorised access can be configured on 2N IP intercoms thanks to the accessories available. First of them is Magnetic door contact (order number 9159012) and the second one is Departure button (order number 9159013). This feature is very useful for buildings where you have doors without a handle (only with a knob) and you're looking to increase the security. It can be used in banks, financial centres, offices, labs, server rooms and many more. Just imagine that you have the door's lock connected to one of the relays in 2N IP intercom and also door magnetic contact and eventually a departure button. If you press the departure button which is placed inside the building (while 2N IP Intercom being outside) or if you authenticate on an inside module of the intercom, then the door will be unlocked and magnetic contact will be cut off. In this case, the door is opened and you can exit the building. If the magnetic contact is cut off but the door is not opened by the 2N IP intercom (nobody has pressed the departure button, swiped the card over RFID reader or used any other method of authorization), then it's most likely an unauthorized access via breaking in. This unauthorized access to the building will trigger an alarm should you set it up.  How to set it up? All necessary steps for settings of this feature are shown in the figures below. You will have to configure one switch, an automation and you will also have to use one input. You will also need to have either Enhanced integration or Gold license — this license is necessary for Automation features in general.   Switch configuration This switch controls the Output 1 to which is door's lock connected. Set in monostable mode, meaning that after activation of this switch the door will remain open for 5 seconds (it may be changed depending on your needs using the Switch-On Duration option).     How to configure Unauthorised Door Open Detection You need to enable the feature Unauthorised Door Open Detection for the specific Switch (in our case for Switch 1) and set which input is the Magnetic door sensor connected to.If you use the Departure (REX) button, you also have to assign an unique input to it.     How to set up the Automation  The settings above mean that if 2N IP Intercom detects logical change in the input from the magnetic lock, it verifies whether the door opening was authorized and if wasn't, the Automation will trigger an alarm sound, or executes any other action such as sending a HTTP command to a security desk, sending an email etc.

Question 19

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 20

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 21

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 22

Certification for web authentication

Accepted Answer

Certificates are commonly used to identify server or device to which we are trying to connect. Nowadays digital certificates for web application are used according to the ITU X.509 standard.    The certificate is issued by some trusted issuer or Certification Authority (also shortened to CA) and assigns public key to either domain name or IP address. If certificate is issued for different IP address or domain name, than the destination really has, modern web browser will usually inform us that the web page can be forged.   Certificates are issued on limited time (for security reasons), after this time it is needed to renew validity of the certificate (often a year for server and client applications with reserve of a few days). After the expiration of a certificate web browsers will point out that the certificate is invalid because of authentication fo server will not pass.   Connectivity to our devices web interface is provided by secured HTTPS protocol, which requires valid certificate. We are sure you have already encountered this "invalid security certificate" warning in your web browser...     Prerequisites 2N IP Intercom / 2N Access Unit / 2N Answering unit / 2N SIP Audio based on 2N OS with the latest firmwareno additional license is required    Issuing certificate   Certification authority on the InternetIt is possible to find many CAs on the Internet, most of them offer trusted certificates that are issued on the domain name. Many of these CAs are already assigned to trusted root CAs in your web browser.    Your own certification authorityIt is possible to create your own CA, however it is needed to import certificate of such CA in to the web browser.We will show you example of using OpenSSL certificate toolkit under a linux based system (e.g. Ubuntu).More information you can find also here: https://ubuntu.com/server/docs/opensslhttps://jamielinux.com/docs/openssl-certificate-authority/introduction.html  Open a linux command line (terminal)Create a Certification Authority Start the procedure by this command  admin@ubuntu:~$ openssl req -out ca.crt -new -x509         During command processing you will be prompted for password creation and verification. This password will be used to protect your private key so the key file cannot be used to issue assign unauthorised certificates with your private key. Enter PEM pass phrase:  YourPassword123 Verifying - Enter PEM pass phrase: YourPassword123          Now fill in data about your CA (use your own data, below is just an example)   You are about to be asked to enter information that will be incorporated into your certificate request.What you are about to enter is what is called a Distinguished Name or a DN.There are quite a few fields but you can leave some blankFor some fields there will be a default value,If you enter '.', the field will be left blank. ----- Country Name (2 letter code) [AU]: CZState or Province Name (full name) [Some-State]: PragueLocality Name (eg, city) [ ]: PragueOrganization Name (eg, company) [Internet Widgits Pty Ltd]: 2NOrganizational Unit Name (eg, section) [ ]: TechsupportCommon Name (e.g. server FQDN or YOUR name) [ ]: TestUserEmail Address [ ]:         (we left this blank)              Two files have been created (you can find them in /home) ca.crtcontaining certificate of our CAprivkey.pemcontaining private key of our CA, needed to sign and issue new certificates by this CA                   Create CSR (Certificate Sign Request) with RSA (cryptographic algorithm) Private Key Start the procedure by this command (name IPINTERCOM can be changed) admin@ubuntu:~$ openssl req -newkey rsa:2048 -noenc -keyout IPINTERCOM.key -out IPINTERCOM.csr           This file has been created (you can find it in /home) IPINTERCOM.keyRSA (cryptographic algorithm) Private Key               Now fill in data about the certificate and its owner.(use your own data, below is just an example)Very important item is Common Name which must contain IP address or Domain Name under which the 2N device can be accessed. Without this correct parameter authentication won't be made correctly and web browser will inform you that this web page is untrustworthy.   You are about to be asked to enter information that will be incorporatedinto your certificate request.What you are about to enter is what is called a Distinguished Name or a DN.There are quite a few fields but you can leave some blankFor some fields there will be a default value,If you enter '.', the field will be left blank. ----- Country Name (2 letter code) [AU]: CZState or Province Name (full name) [Some-State]: PragueLocality Name (eg, city) [ ]: PragueOrganization Name (eg, company) [Internet Widgits Pty Ltd]: 2NOrganizational Unit Name (eg, section) []: TechsupportCommon Name (e.g. server FQDN or YOUR name) [ ]: intercom.localEmail Address [ ]:         (we left this blank)   Please enter the following 'extra' attributes to be sent with your certificate request A challenge password [ ]:         (we left this blank)An optional company name [ ]:         (we left this blank)             This file has been created (you can find it in /home) IPINTERCOM.csrcontaining new certificate request                Create configuration file containing the DNS entries Open a text editor and insert this content (this are not terminal commands), save as "Cert.conf".  authorityKeyIdentifier=keyid,issuer basicConstraints=CA:FALSE subjectAltName=@alt_names [alt_names] DNS.1=intercom.local  If you are generating for IP address, make sure to change "DNS.1" to "IP.1" instead.          Sign the CSR (Certificate Sign Request) with your CA (Certification Authority) Start the procedure by this command (use the files from the previous steps) admin@ubuntu:~$ openssl x509 -req -sha256  -CA ca.crt -CAkey privkey.pem -in IPINTERCOM.csr  -out CERT.crt -days 365 -CAcreateserial -extfile Cert.conf            Now just enter the pass phrase for the privkey.pem Certificate request self-signature oksubject=C =CZ, ST = Prague, L = Prague, O = 2N, OU = Techsupport, CN = intercom.local Enter pass phrase for privkey.pem: YourPassword123             This file has been created (you can find it in /home) CERT.crtcontaining the certificate for the device                  Loading CA certificate into browser This is step needed for certificates created by your own CA (e.g. by OpenSSL), in case of trustworthy CA from the Internet, you can pass this section. In the browsers go to Settings - Privacy - Security and just import the certificate authority file (in our case CA.crt).Here is an example for Firefox:              Loading device certificate into the device Please go to section System - Certificates - User Certificates and upload a new certificate.You will need the device certificate file CERT.crt, intercom RSA private key IPINTERCOM.key and the private key password.It is possible that some Internet Certification Authorities will give you just one file containing both certificate and private key. This file must be then uploaded in both User Certificate and Private Key boxes.       Please go to section Services - Web Server and assign this certificate for web interface.    Finally, please go to section System - Maintenance and restart the device.With new start new certificate and key will be used for HTTPS communication.

Question 23

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 24

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 25

Configuration of electrical outputs on 2N IP Intercoms

Accepted Answer

What are electrical outputs good for Electrical outputs are connectors on electronics of 2N IP Intercoms where you can connect door lock, alarm system, home automation system, signalling light etc. Basically anything that can be controlled by electrical signal. What electrical outputs are available Generally there are two types: Active output - two connectors, either gives no voltage, or it provides voltage. The voltage is from 8 to 14V DC, and can provide up to 700mA current, depending on which intercom. Details about electrical outputs are always mentioned in technical parameters in Installation manual, which is available for each intercom separately. They are also listed below.Relay (passive) output - three connectors, NO normally open, C common, NC normally closed. Two of these three should be used. Always connect the C, and either NO (circuit is disconnected by default) or NC (circuit is connected by default). 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. What are the switches in the configuration of 2N IP Intercom In terminology of the 2N IP Intercoms, we use Switch as a subject in settings which representents a set of parameters. Switch says what is the PIN code, time profile, which electrical output and some other parameters. You always have four switches, no matter how many actual electrical outputs are on that particular intercom. This makes possible to have multiple switches linked to one electrical outputs. You can thus set two different sets of settings for our output. Examples on using two switches with one electrical output, for example intercom with keypad controlling shop front door: PIN code 1234* opens the door for 5 seconds, so an employee can walk in. Manager of the day has a different code 4321* which triggers the door to be open, until they are closed again with code 4322*. That means, employee can get into the building, but only manager can open the shop in the morning and close it in the evening.The employees code 1234* from above can be limited by a time profile to work one hour before opening hours and one hour after shop hours. Manager would use a different code for opening of the door for himself, which would work 24/7. What if I need more settings For more complicated scenarios, control of more outputs etc, we recommend using the Automation scripts. What are the options of particular intercom types 2N IP Verso 2.0 Number of switches: 4 Number of electrical outputs: 1 active output and 1 relay on main unit, 2 relays on each I/O module.  Relay: switching contact, max. 30 V / 1 A AC/DCActive output: 8 – 12 V DC depending on the power supply, max. 600 mA  (PoE: 10 V; adapter: source voltage –2 V), max. 600 mA 2N IP Verso and LTE Verso Number of switches: 4 Number of electrical outputs: 1 active output and 1 relay on main unit, 2 relays on each I/O module. Maximum of 29 additional I/O modules. Relay: NO/NC contact, up to 30 V / 1 A AC/DCActive output: 8 up to 12 V DC depending on power supply (PoE: 10 V; adaptor: power supply voltage minus 2 V), max 400 mA IP Style Number of switches: 4 number of electrical outputs: 1 active output and 1 relay on main unit, 2 relays on each I/O module Relay: passive switch, make and break contact, up to  30 V / 1 A AC/DC NO/NC contact terminalsActive output: 10–12 V / 600 mA DC  2N IP Force and Safety Number of switches: 4 Number of electrical outputs: 1 active output and 1 relay on main unit, 2 relays on additional switch or card reader Relay: NO and NC contacts, up to 30 V / 1 A AC/DCActive output: 9 up to 13 V DC depending on power supply (PoE: 9 V; adaptor: power supply voltage minus 1 V), max 700 mA IP Solo Number of switches: 4 Number of electrical outputs: 1 active output and 1 relay on main unit. Relay: NO/NC contact, up to 30 V / 1 A  AC/DC Active output: 8 up to 12 V DC depending on power supply (PoE: 10 V; adaptor: power supply voltage minus 2 V), max. 600 mA  IP One Number of switches: 4 Number of electrical outputs: 1 active output and 1 relay on main unit. Relay: 30 V / 1 A AC/DC NO contact Active output: 12 V DC, max. 600 mA  2N IP Vario Number of switches: 4 Number of electrical outputs: 1 output on main unit, alternatively active or relay  (select by jumpers), one more relay on additional switch, two more relays on card reader module Relay: NO and NC contacts, up to 30 V / 1 A AC/DCActive output: 10 up to 14 V DC depending on power supply (PoE: approx. 14 V; adaptor: same voltage as power supply), max 700 mA 2N IP Base Number of switches: 2 Number of electrical outputs: 1 active output and 1 relay on main unit Relay: NO/NC contact, up to 30 V / 1 A AC/DCActive switch output: 8 up to 12 V DC depending on power supply (PoE: 10 V; adaptor: power supply voltage minus 2 V), max 400 mA 2N IP Uni Number of switches: 1 Number of electrical outputs: 1 active output and 1 relay, not separately controlled Relay: NO and NC contacts, up to 30 V / 1 A AC/DCActive output: 8 up to 12 V DC depending on power supply (PoE: 9 V; adaptor: power supply voltage minus 2 V), max 500 mA 2N IP Audio Kit and Video Kit Number of switches: 4 Number of electrical outputs: 2 active outputs and 1 relay Relay: NO and NC contacts, up to 30 V / 1 A DC or 125 V / 0.3 A ACActive output: PoE: 10 V; adaptor: power supply voltage minus 2 V, maximum 11V, max 400 mA

Question 26

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 27

Congifuring more unlock buttons in 2N Answering Units

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   You can set the 2N answering units to unlock up to multiple locks either during a call or without a call.    2N IP Intercom configuration  2N Indoor Talk configuration  2N Indoor Compact configuration  2N Indoor View configuration  Last update  Devices Used  Licences required   2N IP Intercom configuration First, you need to set activation codes for switches in the intercom. Go to the “Hardware -> Switches” section in the web interface and set different codes for each switch. You can also choose desired controlled output or set the HTTP command for each switch.       2N Indoor Talk configuration After setting the Activation codes in the IP intercom, go to the web interface of the 2N Indoor Talk. Then go to the “Directory -> Devices -> “Added intercom” -> Unlock Button Function” section and fill in the Switch activation codes there.  After that everything is set correctly, and you can open the first lock/switch on the 2N Indoor Talk by short-pressing the Lock symbol and by long-pressing the lock symbol you open the second lock.    2N Indoor Compact configuration After setting the Activation codes in the IP intercom, go to the web interface of the 2N Indoor Compact. Then go to the “Directory -> Devices -> “Added intercom” -> Unlock Button Function” section and fill in the Switch activation codes there.  After that everything is set correctly, and you can open desired lock/switch on the 2N Indoor Compact by clicking on the Lock symbol and choosing the lock.        2N Indoor View configuration After setting the Activation codes in the IP intercom, go to the web interface of the 2N Indoor View. Then go to the “Directory -> Devices -> “Added intercom” -> Unlock Button Function” section and fill in the Switch activation codes there.  After that everything is set correctly, and you can open desired lock/switch on the 2N Indoor View by clicking on the Lock symbol and choosing the lock.     Last update  2024-11-12    Devices Used  2N IP Verso (FW v2.45.0.59.2)  2N Indoor Talk (FW v2.44.0.57.3 )  2N Indoor Compact (FW v2.45.0.59.2 )  2N Indoor View (FW v2.45.0.59.2 )    Licences required  License is not needed – standard function

Question 28

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 29

Direct call without SIP Proxy registration

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 Intercom is capable of making direct IP calls without the need of registration to SIP Proxy (PBX), using Device ID (2N devices) or IP address (any SIP device). Registration to SIP Proxy is described in this article: SIP Proxy registration   Prerequisites 2N IP Intercom with the latest firmware,no additional license is required.Another SIP device to be called.(2N Answering unit / 2N IP Intercom / 3rd party SIP device)Be sure, it is capable to receive the call.   Click here for instructions for firmware 3.0 and newer. Read more about the differences in long-term support and active track 2N OS. Firmware 2.50 and older (LTS) Basic calling configuration Click on the part according to what device you would like to call.  2N Answering unit or 2N IP Intercom Call features are disabled by default.Go to the calling and also called device web interface, section Calling - Local Calls - Configuration and enable the feature. Ensure that all devices in your network operate in the same mode, configured via Calling > Local Calls > Configuration > Network Identification > Local Calls Compatibility Mode For networks with legacy devices, such as 2N Indoor Touch, the Local Calls Compatibility Mode must always be enabled. This mode is exclusive and doesn't allow calling with devices in a different mode. By default this parameter is disabled that means that: SIPS and SRTP are now enforced for Local Calls after a factory reset.     Assign the called device to the user.You can use the inbuilt scanner or set the user manually. Using inbuilt scanner Go to the calling device web interface, section Directory - Users and click the Find Device button.        Select the devices and click the Add button.       Set the user manually Go to the calling device web interface, section Directory - Usersand open the existing user or create a new one by clicking the Add User button.         Find the part User Phone Numbers and fill in the first Phone Number in format device:DeviceID.     In default, Device ID is in format Model-SN, e.g. 2NIndoorView-5412345678. In the called device, you can adjust it in section Calling - Local Calls - Configuration.      If you wish to start the call by pressing the button, you need to assign the user to the button in section Calling - Dialing - Quick Dial Buttons.            any SIP device (2N and also 3rd party) Call features are disabled from default.Go to the 2N calling device web interface, section Calling - SIP 1 - Configuration and enable the feature.Ensure enabling calling also in the called device.      Set the user Go to the 2N calling device web interface, section Directory - Usersand open the existing user or create a new one by clicking the Add User button.    Find the part User Phone Numbers and fill in the first Phone Number in format sip:IPaddress (e.g. sip:192.168.1.101).IPaddress is IP address of the called device. If it is under SIP Proxy and there is no SIP Proxy registration, you can use also format sip:extension@IPorDomain (e.g. sip:100@192.168.1.1).      If you wish to start the call by pressing the button, you need to assign the user to the button in section Calling - Dialing - Quick Dial Buttons.         Calling more devices You can set more devices to the user and call the next device if the previous one is busy.      You can also assign a deputy user (with another 3 devices) to ensure answering call even if you are busy at all three phone numbers.      If you need to call the devices at once, enable parameter Group call to next number.        Alternatively, you can make multiple users with one or more phone numbers and assign them all to one button.        Firmware 3.0 and newer Basic calling configuration Click on the part according to what device you would like to call.  2N Answering unit or 2N IP Intercom Call features are disabled by default.Go to the calling and also called device web interface, section Calling - Local Calls - Configuration and enable the feature. Ensure that all devices in your network operate in the same mode, configured via Calling > Local Calls > Configuration > Identification in network > Local Calls Compatibility Mode For networks with legacy devices, such as 2N Indoor Touch, the Local Calls Compatibility Mode must always be enabled. This mode is exclusive and doesn't allow calling with devices in a different mode. By default this parameter is disabled that means that: SIPS and SRTP are now enforced for Local Calls after a factory reset.     Assign the called device to the user.You can use the inbuilt scanner or set the user manually. Using inbuilt scanner Go to the calling device web interface, section Directory and click the Add local device button.        Select the devices and click the Add to directory button.       Set the user manually Go to the calling device web interface, section Directoryand open the existing user or create a new one by clicking the Add record button.         Find the part User Phone Numbers and fill in the first Phone Number in format device:DeviceID.      In default, Device ID is in format Model-SN, e.g. 2NIndoorView-5412345678. In the called device, you can adjust it in the section Calling - Local Calls - Configuration.       If you wish to start the call by pressing the button, you need to assign the user to the button in section Calling - Dialing - Quick Dial Buttons.             any SIP device (2N and also 3rd party) Call features are disabled from default.Go to the 2N calling device web interface, section Calling - SIP 1 - Configuration and enable the feature.Ensure enabling calling also in the called device.      Set the user Go to the 2N calling device web interface, section Directoryand open the existing user or create a new one by clicking the Add record button.     Find the part User Phone Numbers and fill in the first Phone Number in format sip:IPaddress (e.g. sip:192.168.1.101).IPaddress is IP address of the called device. If it is under SIP Proxy and there is no SIP Proxy registration, you can use also format sip:extension@IPorDomain (e.g. sip:100@192.168.1.1).      If you wish to start the call by pressing the button, you need to assign the user to the button in section Calling - Dialing - Quick Dial Buttons.          Calling more devices You can set more devices to the user and call the next device if the previous one is busy.      You can also assign a deputy user (with another 3 devices) to ensure answering call even if you are busy at all three phone numbers.      If you need to call the devices at once, enable the parameter Call together with next.          Alternatively, you can make multiple users with one or more phone numbers and assign them all to one button.

Question 30

Door lock does not open after dialing 00

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.  Prerequisites 2N IP Intercom with the latest firmware,no additional license is required.   Click here for instructions for firmware 3.0 and newer. Read more about the differences in long-term support and active track 2N OS.   Firmware 2.50 and older (LTS) Why code 00 does not work for opening door   This code can be entered only from your phone (IP phone, softphone, etc.).For usage on the keypad please create a new code.      The code for opening the door has to be confirmed with * (00*).Resp. if you enable "Legacy switch code", then the confirmation is not necessary.      Check that all 3 types of DTMF receiving modes are enabled.     If still the same, please continue to this article: Diagnostics and Troubleshooting Firmware 3.0 and newer Why code 00 does not work for opening door   This code can be entered only from your phone (IP phone, softphone, etc.).For usage on the keypad please create a new code edit the existing one. Go to Integration, then click the three dots on an exsiting code to edit or click the edit icon to add a new code.         The code for opening the door has to be confirmed with * (00*).Resp. if you enable "Legacy switch code", then the confirmation is not necessary.      Check that all 3 types of DTMF receiving modes are enabled.     If still the same, please continue to this article: Diagnostics and Troubleshooting

Question 31

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 32

Electric locks in 2N IP Intercom accessories

Accepted Answer

Our 2N IP Intercoms and 2N Access Units can trigger the door lock, e.g. when users are authorized and need to open the door. What is the difference between locks offered among 2N IP Intercoms accessories?   Order numberPictureExtra functionElectricityNote932071E  (BEFO 11211)12V / 230 mA DCThis is ordinary electric lock that is opened by connecting 12V to its terminals - it stays unlocked until voltage is present.932081E  (BEFO 11221)momentum pin12V / 230 mA DCThis lock is opened by 12V on its terminals, but it stays opened even when voltage is disconnected. It stays unlocked till somebody went through the door  –  so it can be unlocked only by short voltage impulse.932091E  (BEFO 11211MB)mechanical blocking12V / 230 mA DCThis lock is the same as the first one, but there is a mechanical switch on its body that allows to unlock it permanently.932061E  (BEFO 211211)door signalling12V / 230mAA regular lock with a built-in contact to indicate whether the door is open or closed. 932072E  (BEFO 31211) fail-safe12V / 170mA DCThe failsafe lock is closed when electricity is switched on. When electricity is interrupted, the lock is opened. 932062E  (BEFO 321211)fail-safe, door signalling12V / 170mA DCThe failsafe lock is closed when electricity is switched on. When electricity is interrupted, the lock is opened. It contains a built-in contact to indicate whether the door is open or closed.11202101 12V / 290mA Designed for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; short sheet metal front cover version (130 mm); 16 mm width. 11202101-L 12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; long sheet metal front cover version (250 mm); 16 mm width.11202102momentum pin12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; short sheet metal front cover version (130 mm); 16 mm width.11202102-Lmomentum pin12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; long sheet metal front cover version (250 mm); 16 mm width.11202103mechanical blocking12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; short sheet metal front cover version (130 mm); 16 mm width.11202103-Lmechanical blocking12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; long sheet metal front cover version (250 mm); 16 mm width.11202104door signaling12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; including a door state monitoring micro switch: open/closed; short sheet metal front cover version (130 mm); 16 mm width.11202104-Ldoor signaling12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; including a door state monitoring micro switch: open/closed; long sheet metal front cover version (250 mm); 16 mm width.11202105 fail-safe12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; under voltage: opener secured, blocked at voltage interruption: opener unblocked, door can be opened; short sheet metal front cover version (130 mm); 16 mm width.11202105-L fail-safe12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; under voltage: opener secured, blocked at voltage interruption: opener unblocked, door can be opened; long sheet metal front cover version (250 mm); 16 mm width.11202106fail-safe, door signaling12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; under voltage: opener secured, blocked at voltage interruption: opener unblocked, door can be opened;  including a door state monitoring micro switch: open/closed; short sheet metal front cover version (130 mm); 16 mm width.11202106-Lfail-safe, door signaling12V / 290mADesigned for door frame installation, intended for such narrow profiles as aluminium, wood or PVC in particular; under voltage: opener secured, blocked at voltage interruption: opener unblocked, door can be opened;  including a door state monitoring micro switch: open/closed; long sheet metal front cover version (250 mm); 16 mm width.11202201(SAM 7255)self-locking,panic function10-24V DC / 250 mA, permanently loaded Electromechanical lock; dimensions: 170 x 80 x 15 mm; standard front side of lock: 230 x 22 x 3 mm, R11, stainless; 72/55 self-locking lock with panic function; a key is necessary for door opening from the outside (or an electric pulse from a connected 2N IP intercom / reader); convenient solution for emergency exits. 11202201-M(SAM 7255)self-locking,panic function,monitoring10-24V DC / 250 mA, permanently loadedElectromechanical lock; dimensions: 170 x 80 x 15 mm; standard front side of lock: 230 x 22 x 3 mm, R11, stainless; 72/55 self-locking lock with panic function; a key is necessary for door opening from the outside (or an electric pulse from a connected 2N IP intercom / reader); convenient solution for emergency exits.11202202(SAM 9235)self-locking,panic function10-24V DC / 250 mA, permanently loaded Electromechanical lock; dimensions: 180 x 50 x 15 mm; standard front side of lock: 270 x 22 x 3 mm, R11, stainless; 92/35 self-locking lock with panic function; a key is necessary for door opening from the outside (or an electric pulse from a connected 2N IP intercom / reader); convenient solution for emergency exits. 11202202-M(SAM 9235)self-locking,panic function,monitoring10-24V DC / 250 mA, permanently loadedElectromechanical lock; dimensions: 180 x 50 x 15 mm; standard front side of lock: 270 x 22 x 3 mm, R11, stainless; 92/35 self-locking lock with panic function; a key is necessary for door opening from the outside (or an electric pulse from a connected 2N IP intercom / reader); convenient solution for emergency exits.11202107(Maglock MEX100)12V DC / 250 mA, Holding force: 1800N, Weight: 1,2 kg; Dimensions: 166 x 40 x 22 mm; used as a door holding supplement, not replacing the lock; consists of two parts: supplied part and counterpart; under voltage: door cannot be opened; at voltage interruption: magnets get disconnected, door opens 11202501(Magnetic handle P300RP)12V DC / 550 mA, Holding force: 3000 N (1x 300 kg); Dimensions: 400 x 105 x 63 mm; fully replaces a mortise lock and handle; under voltage: door cannot be opened; at voltage interruption: magnets get disconnected, door opens; suitable for wooden, metal and glass doors 11202401(ED100)230 V  Opening speed (90°): 3-7 seconds; Protection level: IPI2D, Weight: 8,5 kg; Dimensions: 620 x 197 x 82 mm; low energy simple door operator; contactless operation; can be interconnected with a motion sensor and electronic access control system; applicable for right / left doors; in / out opening versions    We can offer you also cable protectors. Order numberPictureNote11202301(Cable protector FX290)  Provides secure passage and protection of the supply cable between the door frame and the door leaf. Total lenght: 290 mm, Outer diameter: 14.5 mm, Inner diameter: 10,5 mm; Length of flexible pipe: 150 mm; Surface: nickel  11202302(Cable protector FX510)  Provides secure passage and protection of the supply cable between the door frame and the door leaf. Total length: 510 mm, Outer diameter: 14.5 mm, Inner diameter: 10.5 mm; Length of flexible pipe: 370 mm; Surface: nickel 11202303(Cable protector FX300G) Provides secure passage and protection of the supply cable between the door frame and the door leaf. Total length: 440 mm, Outer diameter: 14.5 mm, Inner diameter: 10 mm; Length of flexible pipe: 300 mm; Surface: grey terminal, steel pipe 11202304(Cable protector FX500G) Provides secure passage and protection of the supply cable between the door frame and the door leaf. Total length: 640 mm, Outer diameter: 14.5 mm, Inner diameter: 10 mm; Length of flexible pipe: 500 mm; Surface: grey terminal, steel pipe

Question 33

Gmail SMTP Service - How to configure with Intercom units

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. Requirements: The E-mail (SMTP) functionality is available only with the Gold license The 2N IP Intercom supports these ports:  25  587     Google mail configuration   Google account settings - Create an App password (with 2-Step Verification)   2N IP Intercom Configuration      Google account settings - Create an App password (with 2-Step Verification) Google allows only the secure way to connect your Gmail account with the 2N IP Intercom. With this option, you will get a one-time password that you will use to log in to the SMTP settings in the 2N IP Intercom.  First of all, you need to activate 2-Step Verification for your Google account  Create a Custom app (1), here: https://myaccount.google.com/apppasswords      In the next step, you will have to select a Custom device and name it (2) for better identification  Then Click "Generate" (3):    A unique password will be generated (4), that you'll use later in the 2N IP Intercom configuration  Note down the password, then press the "DONE" (5) button:   2N IP Intercom Configuration    After you have set your Google account, you now need to set the 2N IP Intercom as well:  Go under the "Dialing" (1) tab and select "E-Mail" (2)  Enable the SMTP Service (3)  Fill out the "SMTP Server Settings" (4):  "Server Address" (SMTP server is smtp.gmail.com)  "Server port" is 587 (SSL/TLS encryption) or 25 (STARTTLS)   Set the "Security Type" accordingly to the selected port   Fill out the "SMTP Server Login" (5):  "Username" is your email address complete with domain (@gmail.com)  "Password" is the unique password created under "App Passwords"  Set the "Client Certificate", by default the "Signed by Device" is selected   Enter the sender email address under "Common E-Mail Settings" and "From Address" (6)  You can test the configuration by entering your email under "Test Email Address" (7)  Click on "Apply & Test" (8), a test email will be sent to your inbox   Lastly, save the configuration (9)         If you get a message Test email FAILURE, please double check the validity of entered credentials to this manual, otherwise please contact our support: Technical Support - 2NMake sure you have a Gold License activated, otherwise you can activate a Trial License (limited to 800 hours) to test out the features (System - License - Activate Trial License)

Question 34

Grandstream GXV3140 - How to set it up with a 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.   Note: The IP addresses used will always vary depending on your network. In the example below, the IP address 192.168.3.165 for the 2N IP Intercom and the IP address 192.168.3.166 for the Grandstream GXV3140 are used.  How to set up a 2N IP IntercomHow to set up a Grandstream GXV3140 IP Phone How to set up a 2N IP Intercom Setting up the 2N IP Intercom is very easy. First, it is necessary to create a new user in the blue section directory and assign him a phone number - in our case it will be a direct call (peer to peer) to the GXV3140 phone. For this reason, we enter a phone number in the form sip:IP_address (or sip:x@IP_address), where IP_address is the IP address of the GXV3140  phone. The setting corresponds to the picture below.  In the next step, go to the "Calling -> SIP 1" section, enable the SIP 1 account and fill in the "Domain" field with the IP address of the 2N IP Intercom.  We can adjust the video codec settings and video resolution. These settings can be made in the section "Calling -> SIP 1-> Video" section, where you can set the maximum resolution for the given intercom model (VGA in this case for the 2N IP Verso intercom), change the frame rate and also the video bitrate. We also enable "Use sendrecv Attribute for Video" in the advanced SPD settings option.   Finally, we need to assign the user to the quick dial button of the 2N IP Intercom in the section "Calling -> Dialing-> Quick Dial Button".   How to set up a Grandstream GXV3140 IP Phone Be sure to leave the Use Random Port field blank in this setting.  In the next picture you can find the SIP settings for Grandstream. Set the Local SIP Port to 5060.  In General Settings, you need to specify the IP address of the SIP server. This is the IP address of the 2N IP Intercom.

Question 35

Grandstream GXV3175v2 - How to set it up with a 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 Grandstream GXV3175v2 is a 7-inch touchscreen IP phone with Wi-Fi connectivity and a variety of features, supporting a range of audio codecs and video codecs (H.264, H.263 and H.263+). One of the features supported on the GXV3175v2 that is described in this FAQ is "video preview". This is a video preview of the doorman before you pick up the call, i.e. you can very easily see who is standing at your door before you pick up the call and start talking to the caller.   Note: The IP addresses used will always vary depending on your network. In the example below, the IP address 192.168.50.199 for the 2N IP Intercom and the IP address 192.168.50.196 for the Grandstream GXV3175v2 are used.  How to set up the 2N IP IntercomHow to set up the Grandstream GXV3175v2 IP Phone How to set up the 2N IP Intercom Setting up the 2N IP Intercom is very easy. First, it is necessary to create a new user in the blue section directory and assign him a phone number - in our case it will be a direct call (peer to peer) to the GXV3175v2 phone. For this reason, we enter a phone number in the form sip:IP_address (or sip:x@IP_address), where IP_address is the IP address of the GXV3175v2  phone. The setting corresponds to the picture below.  In the next step, go to the "Calling -> SIP 1" section, enable the SIP 1 account and fill in the "Domain" field with the IP address of the 2N IP Intercom.  We can adjust the video codec settings and video resolution. These settings can be made in the section "Calling -> SIP 1-> Video" section, where you can set the maximum resolution for the given intercom model (VGA in this case for the 2N IP Verso intercom), change the frame rate and also the video bitrate. We also enable "Use sendrecv Attribute for Video" in the advanced SPD settings option.  Finally, we need to assign the user to the quick dial button of the 2N IP Intercom in the section "Calling -> Dialing-> Quick Dial Button".  How to set up the Grandstream GXV3175v2 IP Phone The easiest way to set up this IP phone is via the web interface, but there is also an option to set up the phone directly via the touch screen. The following describes how to set up the phone via the web interface. In the first step it is necessary to enable and set up the first user account "Account 1". As it was said at the beginning of this article, we will set up the connection between the intercom and the IP phone directly, so we will fill in the "SIP Server" field with the IP address of the 2N IP Intercom to which the IP phone will register. It is not necessary to fill in the authorization name and password in this case.  Next, go to "Call Settings" and make sure that the correct numbering plan is used for the first account. If you see a different numbering plan, then overwrite it according to the image below, or you can copy it from the settings for account 2 or account 3.  Next, go to the "Advanced setting - General settings" section of your phone's advanced settings and make sure the "Use Random Port" box is not checked. If this box is checked, then uncheck it.  In the last step, set "Preview" (i.e. preview the video from the intercom before picking up the call) in the "Maintenance" section. Preview is one of the options that can be selected for incoming call settings (see image below). Once you have set this up and saved it, don't forget to confirm the configuration by pressing the "Apply" button in the top right corner of the screen.  Finally, check that the IP phone is indeed registered to the 2N IP Intercom and test the direct call from the doorphone to the intercom and back.

Question 36

Grandstream GXV3240 - How to set it up with a 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.   Used model Grandstream GXV3240: hardware revision - V1.7A, system version : 1.0.1.27, recovery version : 1.0.1.3, boot version : 1.0.1.3, kernel version : 1.0.1.3, Android version : 4.2.2   Note: The IP addresses used will always vary depending on your network. In the example below, the IP address 192.168.50.199 for the 2N IP Intercom and the IP address 192.168.50.196 for the Grandstream GXV3240 are used.  How to set up a 2N IP IntercomHow to set up a Grandstream GXV3240 IP Phone How to set up a 2N IP Intercom Setting up the 2N IP Intercom is very easy. First, it is necessary to create a new user in the blue section directory and assign him a phone number - in our case it will be a direct call (peer to peer) to the GXV3240 phone. For this reason, we enter a phone number in the form sip:IP_address (or sip:x@IP_address), where IP_address is the IP address of the GXV3240  phone. The setting corresponds to the picture below.  In the next step, go to the "Calling -> SIP 1" section, enable the SIP 1 account and fill in the "Domain" field with the IP address of the 2N IP Intercom.   We can adjust the video codec settings and video resolution. These settings can be made in the section "Calling -> SIP 1-> Video" section, where you can set the maximum resolution for the given intercom model (VGA in this case for the 2N IP Verso intercom), change the frame rate and also the video bitrate. We also enable "Use sendrecv Attribute for Video" in the advanced SPD settings option.   Finally, we need to assign the user to the quick dial button of the 2N IP Intercom in the section "Calling -> Dialing-> Quick Dial Button".   How to set up a Grandstream GXV3240 IP Phone The easiest way to set up this IP phone is via the web interface, but there is also an option to set up the phone directly via the touch screen. The following describes how to set up the phone via the web interface after the phone has been reset to factory defaults:  In the first step it is necessary to enable and set up the first user account "Account 1". As mentioned at the beginning of this article, we will set up the connection between the intercom and the IP phone directly, so we will fill in the "SIP Server" field with the IP address of the 2N IP Intercom.  Next, go to the "SIP Settings" and turn off "SIP registration".  Finally, activate the changes you have made.

Question 37

Grandstream GXV3275 - How to set it up 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 Grandstream GXV3275 is a 7-inch touchscreen IP phone with Wi-Fi connectivity and a variety of features, supporting a range of audio codecs and video codecs (H.264, H.263 and H.263+).   Note: The IP addresses used will always vary depending on your network. In the example below, the IP address used is 192.168.48.151 for the 2N IP Intercom and the IP address 192.168.51.97 for the Grandstream GXV3275.  How to set up the 2N IP IntercomHow to set up the Grandstream GXV3275 IP phone How to set up the 2N IP Intercom Setting up the 2N IP Intercom is very easy. First, it is necessary to create a new user in the blue section directory and assign him a phone number - in our case it will be a direct call (peer to peer) to the GXV3275 phone. For this reason, we enter a phone number in the form sip:IP_address (or sip:x@IP_address), where IP_address is the IP address of the GXV3275 phone. The setting corresponds to the picture below.  In the next step, go to the "Calling -> SIP 1" section, enable the SIP 1 account and fill in the "Domain" field with the IP address of the 2N IP Intercom.   We can adjust the video codec settings and video resolution. These settings can be made in the section "Calling -> SIP 1-> Video" section, where you can set the maximum resolution for the given intercom model (VGA in this case for the 2N IP Verso intercom), change the frame rate and also the video bitrate. We also enable "Use sendrecv Attribute for Video" in the advanced SPD settings option.  Finally, we need to assign the user to the quick dial button of the 2N IP Intercom in the section "Calling -> Dialing-> Quick Dial Button".   How to set up the Grandstream GXV3275 IP phone The easiest way to set up this IP phone is via the web interface. The following describes how to set up the phone via the web interface. We start from the default IP Phone settings - available in the "Maintenance/Upgrade" section.   Scroll down on this page and click on the "reset" button to put the IP Phone to the default settings.  The next step is to enable and set up the first user account "Account 1" in the "general setttings -> account-> account 1" section. As it was said at the beginning of this article, we will be setting up a direct connection between the IP Intercom and the IP phone, so we will fill in the "SIP Server" field with the IP address of the 2N IP Intercom to which the IP phone will register. It is not necessary to fill in the authorization name and password in this case.  Then go to "SIP Settings -> Account -> Account 1" and uncheck the SIP registration box.  To enable the Video Preview function, i.e. displaying the video from the intercom on the phone screen before picking up the call, you must enable the function in the menu "Advanced Settings  -> Call Features". The Video Preview feature on the GXV3275 is supported from FW 1.0.1.50.   At the end don't forget to save all changes using "Apply configuration changes" as shown on the pictures above.

Question 38

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 39

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 40

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 41

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 42

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 43

HTTP Commands – How to configure them in Answering units

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.    HTTP API TESTool  Intercom Setup Indoor Talk Indoor Compact  Indoor View  HTTP API TESTool You can find the HTTP commands in the HTTP API manual or by accessing the HTTP API TESTool which is part of every 2N IP Intercom and can help you create valid HTTP commands for the desired request type.  You can access the TESTool by entering the intercom’s IP address and writing /apitest.html at the end (for example https://192.168.49.88/apitest.html)  The HTTP command for triggering Switch 1 on the 2N IP Intercom is https://IP_address/api/switch/ctrl?switch=1&action=on   Intercom Setup First, configure the HTTP API Account in the 2N IP Intercom or 2N Access Unit:  Click on "Services" (1), then select "HTTP API" (2)  Make sure the HTTP Account is enabled (3)  Next, fill out the "Username" and "Password" (4)  Next, select the desired function (5) you wish to allow to be monitored/controlled with selected HTTP API Account  Lastly, save (6)   Indoor Talk Indoor Talk does allow only for one HTTP Command, by long-pressing on the unlock button:  Click on "Services" (1), then select "HTTP Command" (2)  Under the "HTTP Command Setting" - fill out the "URL", "NAME", "USERNAME" and "PASSWORD" (3):  URL - In this example "https://192.168.49.88/api/switch/ctrl?switch=1&action=on"  NAME - In this example called "Open Door"  USERNAME - Input the Username of the HTTP API Account created in the IP Intercom  PASSWORD - Input the Password of the HTTP API Account created in the IP Intercom  Lastly, save (4)  Indoor Compact Indoor Compact does allow up to three HTTP Commands, with selectable Icons that will show up on the display:  Click on "Services" (1), then select "HTTP Command" (2)  Under the "HTTP Command Setting" - fill out the "URL", "ICON", "NAME", "USERNAME" and "PASSWORD" (3):  URL - In this example "https://192.168.49.88/api/switch/ctrl?switch=1&action=on" ICON - In this example an icon of a "Door" is selected NAME - In this example called "Open Door"  USERNAME - Input the Username of the HTTP API Account created in the IP Intercom  PASSWORD - Input the Password of the HTTP API Account created in the IP Intercom  Lastly, save (4)  Indoor View Indoor View does allow up to three HTTP Commands with selectable Icons, per multiple categories of the commands:  Home Screen HTTP Command Setting - HTTP Triggers accessible from the homescreen display  In-Call HTTP Setting - HTTP Triggers accessible during a call  External Camera HTTP Command Setting - HTTP Triggers accessible while viewing an external camera   To configure the HTTP Command for the homescreen in Indoor View:  Click on "Services" (1), then select "HTTP Command" (2)  Under the "HTTP Command Setting" - fill out the "URL", "ICON", "NAME", "USERNAME" and "PASSWORD" (3):  URL - In this example "https://192.168.49.88/api/switch/ctrl?switch=1&action=on" ICON - In this example an icon of a "Door" is selected NAME - In this example called "Open Door"  USERNAME - Input the Username of the HTTP API Account created in the IP Intercom  PASSWORD - Input the Password of the HTTP API Account created in the IP Intercom  Lastly, save (4)

Question 44

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 45

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 46

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 47

Issues accessing the web interface on macOS

Accepted Answer

Our intercoms use HTTPS protocol for accessing their web interface. HTTPS unlike HTTP requires a certificate for authentication. The certificates for 2N devices are signed by the device itself (self-signed) and not by the certification authority hence the browser will mark it as a potential threat.    macOS 10  In macOS 10 when you entered the IP address of your 2N device you would have been presented with "Your connection is not private" as shown below.This had a simple solution -> click on Advanced -> Proceed to IP address (unsafe) and you were taken to the webpage of your 2N device:        macOS 11 Big Sur and newer (12 Monterey, 13 Ventura, 14 Sonoma, 15 Sequoia) With the new macOS update 11, you will not be given the option to Proceed to IP address (unsafe).But there is a workaround for you if you are using a chromium-based web browser e.g. Google Chrome.Workaround: Click anywhere on the blank background and type thisisunsafe on your keyboard and you will be taken to the login webpage of 2N Device      In order to access the web interface of our devices, they need to be on firmware version 2.31 and newer. If you don't own a Windows or a Linux machine, hence you don't have a way how to upgrade the unit, you can upgrade the firmware via a Remote Configuration tool iny My2N. This is a best optin to access the configuration using iOS or iPadOS.   Remote Configuration You can access the web interface via Remote Configuration in our My2N service. The Remote Configuration feature is free for any number of devices and is usable on both macOS and iOS devices. Here are the steps needed: 1. Create an account (if you don't have one yet) here. 2. Log in to your My2N account, click Devices, then ADD DEVICE and select 2N Device.  3. Enter the serial number and security code of the device. If you lost your paper card with the Security Code, this option is not available for you (the Security Code could be found only in the web configuration):  6. Now select the device in the Devices List. At the bottom of the page, you will see Remote Configuration Services.  5. When you click on the rectangle with the Remote Configuration Services, two options will appear. Click on Open configuration. The login page of the intercom will be open on a new tab.

Question 48

Language mutation - How to create own language mutation for 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.   It is possible to create your own language mutation for 2N IP Intercoms since firmware v2.8 and higher.    Go to the Menu Services->Web server->User localization and download the original language file as shown in the picture below:      2. Download the original file containing all the user interface texts in English. The file format is XML; The name of the file is "rs_en"     3. Open this file in a text editor, for example Notepad. While translating, modify the value of  elements only. Do not modify the id values. The language name specified by the language attribute of the  element will be available in the selections of the Web interface language parameter. The abbreviation of the language name specified by the languageshort attribute of the  element will be included in the language list in the right-hand upper corner of the window and will be used for a quick language switching.   4. Below you can find an example which part of the text you can change:     5. After you finish the translation save the file in .xml format again. You can change the name of the file. Our recommendation is to save the file in format rs_XYZ.xml   6. Upload the file into the 2N IP Intercom:

Question 49

License - How to get a license 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. When delivered, all 2N IP Intercoms come with a free license. The only exception is 2N IP Vario with display, keypad, and camera (optional) which comes with preloaded Gold license. If you want to buy an additional license for any other models, the procedure is as follows:  If licensed features are required immediately or you just want to test all features supported by your 2N IP Intercom, please activate an 800 hour trial period in web interface of the unit. Go to section "System → License → Trial License".  Please check with your Account Manager or local reseller to find out whether you need a license or not. Devices running 2N OS 2.35 or higher now come preloaded with more features thanks to the simplification of our licensing policy. Enhanced Audio, Enhanced Security and NFC licenses are now free, along with HTTP API functionality that was previously part of Enhanced Integration. You can also find more information about license policy in "2N IP Intercom Configuration manual" – 3.2 Function Licensing As a result of the simplification, the only available licenses are:  Gold (Part No. 9137909) – which contains all remaining functions except for  InformaCast (Part No. 9137910, Axis Part No. 01381-001) – which allows the use of the SingleWire InformaCast protocol.  All other licenses were discontinued, but our devices are still compatible with them. This means that if your device with 2N OS 2.34 only has, for example, an Enhanced Integration license, and you update it to 2N OS 2.35 or higher, you’ll now have your original license plus what was in Enhanced Audio, Enhanced Security and NFC licenses for free.   Info   Codec G.729 can be used without a license key in SW versions 2.25 and higher. No licensed features are available for the 2N IP Uni.    The license overview does not apply to the US, Canada, Mexico, Caribbean, and Central and South America.    Once you choose the appropriate license, please contact your 2N reseller. If you are a 2N partner, you can contact our Customer Care department at  customercare@2n.com  and they will generate it for you. Please do not forget to specify serial number of your 2N IP Intercom in your request.    All available licenses for specific device are listed in the "2N IP Intercom Configuration manual" - 3. Model Differences and Function Licensing

Question 50

Management over the Internet

Accepted Answer

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

Question 51

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 52

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 53

No video? Try to check the following solutions!

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   If the video is not working, there could be many things that can prevent a video stream to be visible. Let's check the solutions below:  Easy  1.1 Check if your intercom is equipped with a camera  1.2 Check if the camera is not damaged  1.3 Try to re-install the application  1.4 Try to use different connectivity  1.5 Try to use a different phone (same network)   Medium  2.1 Check if the H.264 codec is enabled  2.2 Check if the H.264 payload is correctly set up  2.3 Enable/Disable Adaptive Video Quality  2.4 Disable HW video decoding   Hard  Check if your firewall does not block certain ports  The video still does not work   Please note that trying every possible step before reporting an issue from the app, and specifying in which scenario the video does not work, will increase your chances of resolving the situation more quickly. Please do not forget to mention if the video is working on different connectivity or with a different phone/operating system (and if they are on the same network).    Always check if you are running the latest possible version on the intercom and on the 2N® Mobile Video application!   Easy 1.1 Check if your intercom is equipped with a camera   If you do not have access to the intercom's web interface, you can check visually if the intercom has a camera or not:     Login to the intercom's web interface  Navigate to the green section Status > Device  Look for "Device Features"       1.2 Check if the camera is not damaged You can check the camera stream in the Intercom device:  Login to the intercom's web interface  Navigate to section Hardware > Camera > Common Settings  Open the "Live Preview"  Visually inspect the camera stream     1.3 Try to re-install the application   This procedure might differ based on your operating system, please refer to your device manufacturer's instructions:     Find the 2N Mobile Video application on your phone  Uninstall the app  Install the app back from the app store (Google Play/App Store)  Login back to the app using the QR code  Make a call and check if the video is working     1.4 Try to use different connectivity  If the video is not visible on the Wi-Fi  Try to use a different Wi-Fi network (public, friend's, neighbour's, hotspot from the mobile network)   If the video is not visible on mobile data   If possible check with a different SIM card     1.5 Try to use a different phone (same network)  Try to use a different phone on the same network  If possible try to use a phone with a different operating system (Android/iOS)    Medium   2.1 Check if the H.264 codec is enabled Make sure the video codec (H.264) is correctly set up in the Intercom unit:  Login to the intercom's web interface  Navigate to the section Calling > SIP 2 > Video  H.264 codec should be enabled (preferably set as 1 (highest))      2.2 Check if the H.264 payload is correctly set up Make sure the video codec (H.264) payload is correctly set up in the Intercom unit:  Login to the intercom's web interface  Navigate to the section Calling > SIP 2 > Video  Open the menu Extended Codec Settings (hidden by default)  Check if the default payload for Baseline Profile, Packetization Mode 1 is 123  Check if the default payload for Baseline Profile, Packetization Mode 0 is 124  If not, change the payload to default values and save the changes        2.3 Enable/Disable Adaptive Video Quality Sometimes enabling/disabling the Adaptive Video Quality will resolve issues related to the video not showing up properly:  Login to the My2N portal  Navigate to the device (Intercom)  Open the 2N Mobile Video menu  Disable/Enable the Adaptive Video Quality  Test if you can see the video      2.4 Disable HW video decoding   This setting is available for Android only:     Open the 2N Mobile Video application  Open the configuration  Scroll all the way does and open Advanced Settings  Turn OFF the Video HW decoding  Restart the application     To reset the application it is not sufficient just to throw away the app from the task manager (recent apps list), you need to force stop the app in the phone's settings! Please refer to your device manufacturer's instructions:  Example: (phone settings > apps > see all apps > Mobile Video > FORCE STOP)      Hard   Check if your firewall does not block certain ports   Improper setup of your firewall can cause an outage of your network connectivity, 2N is not responsible for any incorrect changes done by the customers. If you are not sure what you are doing please check with your ISP.     Open your router's web interface (or your firewall directly if it is not part of the router)  Navigate to the section firewall  Set up a rule in your firewall   ServiceProtocolDirectionPortRTP (video/audio packets)UDPOut 30 000 - 31 999      The video still does not work If you have gone through all the steps and video still does not show up: Contact your Intercom Administrator, Property Manager or person responsible for configuration of the Intercom/My2N siteContact us here: Technical Support - 2N

Question 54

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 55

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 56

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 57

Setting up call from a 2N IP intercom to a 2N Indoor Talk and vice versa

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  Indoor Talk unit is designed for an audio communication with the 2N  IP Intercom. You can see all intercoms connected to the LAN, you are able to accept incoming audio calls, make outgoing calls to 2N  IP Intercom and also control locks connected to the intercom.  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 licence is needed     How to configure 2N IP Intercom? Go to the section  "Directory – Users", press Create new user.Fill in the Name. If you want to call the 2N  Indoor Talk unit, the Phone number has to be filled in a format: "sip: ip address". In our example the ip address “192.168.49.62” is being used, please see the picture below.    In the next step you can set the intercom to automatically pick up the incoming calls in order to easily reach it at any time.Go to the section  "Calling – Genetal Settings" and enable Automatic Pickup for incoming calls for both SIP1 and SIP2, see the picture below.  A next step is to set a DTMF code by which the Switch can be triggered.Go to  "Hardware - Switches" and add an Activation code.  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. Last step is to assign the recently created contact to quick dial button.Go to  "Calling - Dialing" click on the Add user to the quick dial button and choose desired users.   List of connected devices on 2N IP intercom   A list of registered Device names can be easily viewed on the 2N  IP intercom in the menu  Calling - Local Calls, see the example below.       How to configure 2N Indoor Talk? Once the 2N  Indoor Talk is connected to the local network, go to its web page - section Directory - Devices. Press Search registered devices and choose the device you want to add.    After you have added the device Device Name and Phone Number are filled automatically. In our example we use IP address instead of Device ID, so please fill the Phone Number with IP address of the intercom. In our example we use "sip:192.168.50.11" as a phone number. Please see the picture below.  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      List of available devices on 2N Indoor Talk   A list of available intercoms can be easily viewed on the 2N  Indoor Talk in the menu  Calling - Local Calls, see the example below.

Question 58

Setting up calls from and 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.   The 2N Indoor View unit is designed for audio and video communication with 2N IP intercoms. You can see all intercoms connected to the LAN, you are able to accept incoming calls, make outgoing calls to 2N IP intercoms and also control locks connected to the intercoms.  Recommendation - use the latest firmware   We recommend to use the latest firmware in 2N Indoor View and also 2N IP intercoms to ensure that all functions are available.    How to configure a 2N IP intercom? As a very first step go to the section Directory – Users, create a new user and set the Phone Number to be dialed once you press the appropriate button on the intercom. If you want to call the 2N Indoor View unit, the number has to be filled in the following format: "device:devicename". In our example the device name “IndoorView” is being used as in the picture below.  In the next step you can set the intercom to automatically pick up incoming calls in order to reach it easily at any time. Go to the section Calling – Gerenal Settings and enable Automatic Pickup for Local Calls, see the picture below.  As a next step go to the section Calling – SIP 1 and fill in the Domain field. For direct calls it is recommended to fill in the IP address of your intercom as shown in the picture below (IP address of the intercom in this example is 192.168.50.10).       A list of available 2N indoor units and their device names can be easily displayed in the 2N IP intercom in the menu Calling  – Local Calls. The list can be viewed by clicking "Show" next to the "Show LAN Device list". See the example below.    Last step is to assign the contact to a quick dial button in the Calling - Dialing section of the configuration.    How to configure 2N Indoor View? Once the 2N Indoor View is connected to the local network, go to its web interface, section Calling – Local Calls. To be able to receive calls from 2N IP intercoms you need to set the Device ID there. The Device ID is used by the intercom for call routing instead of its IP address.  To be able to call from 2N Indoor View to a 2N IP intercom go to 2N Indoor View web interface, section Directory – Devices and add the 2N IP intercom to the device list. Device list is available via 2N Indoor View's onscreen menu.    To be able to activate a 2N IP intercom's switch during a call, open the intercom's tab in Devices, and fill in a valid unlocking DTMF code.

Question 59

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 60

Seznam SMTP service - How to configure with Intercom units

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.   Requirements: The E-mail (SMTP) functionality is available only with the Gold license The 2N IP Intercom supports these ports:  25  587  Seznam mail configuration  Seznam account settings  Creating a password for CalDAV / SMTP   2N IP Intercom Configuration  Seznam account settings Utilizing the Sezman SMPT function requires the account to have 2-Factor Authentication enabled. Once the 2-Factor Authentication is enabled, an additional password will have to be created which will be used for SMTP services. For enabling 2-Factor Authentication please follow the Seznam guides found here: 2-Factor - Seznam or here: CalDAV / SMTP - Seznam      Creating a password for CalDAV / SMTP  Go the Seznam.cz profile, select "Seznam Account" (1) and then "Account Security" (2):  Select "Add authentication device" (3):  Fill out the password of your own Seznam account (4):  Enter a "Device Name" (5):  Use an Authenticator to scan the QR code/enter the key (6):  Check if your phone number is correct a confirm (7):  Locate "Password for applications" and click on "Set" (8):  Fill out the "2-Step Verification" (9):  And then click on "Save Changes" (9):    2N IP Intercom Configuration After completing the new password for the CalDAV protocols, you will need to configure the SMTP server on the 2N Intercom.  First, enable the SMTP Service (10) and enter the Server Address and Server Port, in this case, the SMTP server is smtp.seznam.cz and port 25 (STARTTLS) or port 587 (TLS Secured)  The next step is input and logs into the server with your credentials  The Username is your full e-mail address including the domain, then enter the CalDAV protocol password you created in the Password field (in step 9)  The From Address settings will be the same e-mail address that you entered in the credentials  You can verify the credentials and settings by clicking on "Apply & Test" (11):    If you get a message Test email FAILURE, please double check the validity of entered credentials to this manual, otherwise please contact our support: Technical Support - 2N  Make sure you have a Gold License activated, otherwise you can activate a Trial License (limited to 800 hours) to test out the features (System - License - Activate Trial License)

Question 61

SIP Proxy registration

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 Intercom can be registered to SIP Proxy (PBX) and dial its extensions like you know from an IP phone, using the extension number. Direct call without SIP Proxy registration is described in this article: Direct call without SIP Proxy registration   Prerequisites 2N IP Intercom with the latest firmware,no additional license is required.SIP Proxy registration detailsFor calling you need extension number of another SIP device registered under the same SIP Proxy.     Explanation of IP Telephony Terms  SIP (Session Initiation Protocol)A phone call signalling transmission protocol used in IP telephony. It is primarily used for setting up, terminating and forwarding calls between two SIP devices (the intercom and another IP phone in this case). SIP devices can establish connections directly with each other (Direct SIP Call) or, typically, via one or more servers: SIP Proxy and SIP Registrar.2N IP Intercoms support three ways of SIP signalling:  User Datagram Protocol (UDP),the most frequently used unsecured signalling method.  Transmission Control Protocol (TCP), less frequent, yet recommended unsecured signalling method.  Transaction Layer Security (TLS), where SIP messages are secured against third party monitoring and modification.   SIP ProxyIP network server responsible for call routing (call transfer to another entity closer to the destination). There can be one or more SIP Proxy units between the users.  SIP RegistrarAn IP network server responsible for user registration in a certain network section. As a rule, SIP device registration is necessary for a user to be accessible to the others on a certain phone number. SIP Registrar and SIP Proxy are often installed on one and the same server.  RTP (Real-Time Transport Protocol)A protocol defining the standard packet format for audio and video transmission in IP networks. 2N IP Intercom uses the RTP for audio and video stream transmission during a call. The stream parameters (port numbers, protocols and codecs) are defined and negotiated via the SDP (Session Description Protocol).      Click here for instructions for firmware 3.0 and newer Read more about the differences in long-term support and active track 2N OS. Firmware 2.50 and older (LTS)   SIP Proxy registration 2N IP Intercom allows two independent SIP accounts to be configured. Thus, it can be registered under two extension numbers, with two different SIP exchanges and so on. Both the SIP accounts process incoming calls equivalently. Outgoing calls are primarily processed by account 1, or, if account 1 is not registered (due to SIP exchange error, e.g.), by account 2. You can also select the preferred account number for outgoing calls in the user settings. Go to 2N IP Intercom web interface, section Calling - SIP 1 (or SIP 2) - Configuration. Enable SIP Account.Fill in Device Identity. Display Name ... name to be displayed on the called party´s phone.Phone Number (ID) ... unique identification (extension) under SIP Proxy.Domain ... domain name of the registration service, typically the same as SIP Proxy and Registrar address.  Fill in Authentication. Authentication ID ... alternative user ID for the authentication; if empty, Phone Number (ID) will be used.Password ... the password for authentication under PBX. Fill in SIP Proxy. Proxy Address ... SIP Proxy IP address or domain name.Proxy Port ... SIP Proxy port, in default using 5060 (for UDP, TCP) or 5061 (for TLS).Backup Proxy Address ... SIP Proxy IP address or domain name when the main proxy fails to respond.Backup Proxy Port ... backup SIP Proxy port, in default using 5060 (for UDP, TCP) or 5061 (for TLS). Fill in SIP Registrar. Registration Enabled ... enable intercom registration with the set SIP Registrar.Registrar Address ... the SIP Registrar IP address or domain name.Registrar Port ...  SIP Registrar port, in default using 5060 (for UDP, TCP) or 5061 (for TLS).Backup Registrar Address ... SIP Registrar IP address or domain name when the main proxy fails to respond.Backup Registrar Port ... backup SIP Registrar port, in default using 5060 (for UDP, TCP) or 5061 (for TLS).Registration Expiry ... the registration expiry affecting periodically sent registration requirements.Registration State – see the current registration state (unregistered, registering..., registered, unregistering...). If needed, there are also other advanced parameters, incl. SIP Transport Protocol selection.        Assign the called device to the user We can now assign an extension to the user according to a dialling plan of the SIP Proxy server. Go to the 2N IP Intercom web interface, section Directory - Usersand open the existing user or create a new one by clicking the Add User button.  Find the section User Phone Numbers and fill in the Phone Number parameter by the extension number of the called device in format extension/used SIP account.Examples: 199/1 to call 199 by SIP 1 account199/2 to call 199 by SIP 2 account         If you wish to start the call by pressing the button, you need to assign the user to the button in section Calling - Dialing - Quick Dial Buttons.     Firmware 3.0 and newer    SIP Proxy registration 2N IP Intercom allows four independent SIP accounts to be configured. Thus, it can be registered under four extension numbers, with four different SIP exchanges and so on. All the SIP accounts process incoming calls equivalently. Outgoing calls are primarily processed by account 1, or, if account 1 is not registered (due to SIP exchange error, e.g.), by account 2, etc.. You can also select the preferred account number for outgoing calls in the user settings. Go to 2N IP Intercom web interface, section Calling - SIP 1 (or SIP 2/3/4) - Configuration. Enable SIP Account.Fill in Identification in network. Display Name ... name to be displayed on the called party´s phone.Phone Number (ID) ... unique identification (extension) under SIP Proxy.Domain ... domain name of the registration service, typically the same as SIP Proxy and Registrar address. Authorisation ID ... alternative user ID for the authentication; if empty, Phone Number (ID) will be used.Password ... the password for authentication under PBX. Fill in SIP Proxy. Proxy Address ... SIP Proxy IP address or domain name.Proxy Port ... SIP Proxy port, in default using 5060 (for UDP, TCP) or 5061 (for TLS).Backup Proxy Address ... SIP Proxy IP address or domain name when the main proxy fails to respond.Backup Proxy Port ... backup SIP Proxy port, in default using 5060 (for UDP, TCP) or 5061 (for TLS). Fill in SIP Registrar. Allow Registration ... enable intercom registration with the set SIP Registrar.Registrar Address ... the SIP Registrar IP address or domain name.Registrar Port ...  SIP Registrar port, in default using 5060 (for UDP, TCP) or 5061 (for TLS).Backup Registrar Address ... SIP Registrar IP address or domain name when the main proxy fails to respond.Backup Registrar Port ... backup SIP Registrar port, in default using 5060 (for UDP, TCP) or 5061 (for TLS).Registrar Expiration Time ... the registration expiry affecting periodically sent registration requirements. If needed, there are also other advanced parameters, incl. SIP Transport Protocol selection.        Assign the called device to the user We can now assign an extension to the user according to a dialling plan of the SIP Proxy server. Go to the 2N IP Intercom web interface, section Directoryand open the existing user or create a new one by clicking the Add record button.   Find the section Phone Numbers and fill in the Phone Number parameter by the extension number of the called device in format extension/used SIP account.Examples: 199/1 to call 199 by SIP 1 account199/2 to call 199 by SIP 2 account         If you wish to start the call by pressing the button, you need to assign the user to the button in section Calling - Dialing - Quick Dial Buttons.

Question 62

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 63

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 64

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.

Lijst met veelgestelde vragen