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 Audio Kit Lite - Button does not work

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. Please check Hardware/Keypad/Keypad Mapping. The button is represented in Column1 and Row4. QuickDial button number has to be set and not * as shown on picture bellow.

Question 3

2N IP audio unit can not connect to the 2N&#174; IP Audio Manager - what could be the reason?

Accepted Answer

There could be several reasons, why 2N IP audio device: 2N® Net Audio Decoder / 2N® Net Audio Decoder Lite / 2N® Net Mic / 2N® Net Audio Encoder is not connected to the 2N® IP Audio Manager : 1. In factory default IP audio device obtain IP address automatically (DHCP client is ON).    CAUTION even if other devices in the network obtain IP address automatically, 2N IP audio unit does not have to due to the restrictions set by the IT department in the network. This setting automatically assigns IP addresses only to known/registered devices in the network based on their MAC addresses!  In case device did not obtain IP address automatically, go to menu Administrator > Net Audio device scanner . Displayed IP address in field DHCP would be: 0.0.0.0 (see picture below).For more details contact your IT department. In this case it could be MAC address restriction in the network. Provide MAC address of the device to your IT department and they will register it and allow automatic assignment of the IP addresses.Second option is to turn the DHCP client OFF and setup IP address manually. In this case it is necessary to know some free IP address which can be used for 2N® Net Audio Decoder unit in the network. It means that this IP address (the one you would like to use) is not assigned to any other IP device in the network (you can use ping command to check it). Do not forget to set up the IP mask = subnet of the network.Manual settings could look like this: IP address: 192.168.1.151 IP mask: 255.255.255.0   2. Firewall can also block connection of the unit to the 2N® IP Audio Manager   Do you have firewall switched ON? It can cause that if 2N® Net Audio Decoder unit disconnects from the server and then tries to connect again via the same port, firewall (eg, ESET Smart Security) will not let it go through. This is not the common issue but it could be one of the reason why you cannot see 2N® Net Audio Decoder units in menu Destinations & Zones.   Picture below shows the situation when the network automatically assigns IP addresses (there is DHCP server in the network) but the device (e.g. 2N® Net Audio Decoder unit is not recognized = IT department does not know its MAC address). In this case IP address for 2N® Net Audio Decoder unit would not be automatically assigned .  Picture below shows an example of manually assigned IP address and IP mask,when the DHCP client has been switched OFF:     3. Password for authorization is used: IP audio device authentication to the Server / Server authentication to the IP audio device.   IP audio device is not connected to the 2N® IP Audio Manager even all parameters as: IP address, domain, connection mode are set-up correctly? Most probably you have previously used password for device/server authorization.        To be sure, there is authentication password used. You would need to connect via Telnet to already connected unit to the 2N® IP Audio Manager. For security reason it is needed to "Enable telnet" connection in menu Destinations & Zones. Click on the unit which is already connected and in its parameters check option "Enable telnet".        More details about password authorization can be found in manual for Control Panel / Administration: Administrator#ServerAuthorisation

Question 4

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 5

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 6

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 7

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 8

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 9

2N IP Intercoms - User sounds uploading

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 upload up to 10 user sound files into the intercom and use them in your scenarios, e.g. to welcome your visitors with your voice message when opening the door.   Prerequisities 2N IP Intercom with the latest firmware(except 2N IP Uni, which does not support this feature) No additional license is required for 2N IP Intercom      Uploading a prepared sound file Needed parameters of the audio file(file with different parameters will be refused)FormatEncodingSampling Maximum sizeWAVPCM L8/L16, PCMA, PCMU, or G.7228 or 16 kHz256 kb   Here are suggested tools you can use to covert your sound file (e.g. in MP3) to be accepted by our devices On-line free tool - G711.org     Off-line free open-source tool - Audacity       Configuration in Intercom (firmware version 3.0 and higher) Upload the sound file to 2N IP Intercom via its web interface, section Services - User Sounds.      Recording a sound file directly to the 2N IP Intercom You can also record the sound directly to the device using your PC microphone.        Configuration in Intercom (firmware version 2.50 and LTS) Upload the sound file to 2N IP Intercom via its web interface, section Services - User Sounds.      Recording a sound file directly to the 2N IP Intercom You can also record the sound directly to the device using your PC microphone.

Question 10

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 11

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 12

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 13

Automation, Call Delay - how to set a different ring time for diferent call destinations

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 ring time limit can be set in the "Calling -> General Settings -> Outgoing calls -> Ring Time Limit" section of the web interface of the 2N IP intercom. It is set for 32 seconds by default so for example, when the Quick Dial Button 1 is pressed the intercom will dial the 1st number of the assigned user. In case the call is not picked up within 32 seconds, the intercom will start dialing the second number for 32 seconds and so on until the last number is called. You can create automation where you can set different ring time limits for different destinations.   Scenario: There is an intercom at the main entrance of an office building, 1 answering unit at the reception and 2 smartphones with a 2N Mobile Video app that belongs to receptionists. When the Quick Dial Button is pressed we want the intercom to call the answering unit and dial for 30 seconds. If the call is not answered during those 30 seconds, we want the intercom to call 1st receptionist's smartphone and dial for 50 seconds. In case the receptionist does not pick up as well, the intercom will call 2nd receptionist and dial for 30 seconds.    For the scenario and the automation to properly work, the button setting must be empty:        This automation will start calling the first number, after 30 seconds it ends the call, waits for 3 seconds and starts dialling the second number. After 50 seconds the automation ends the call, waits for another 3 seconds and then starts dialling the third number for 30 seconds. After that, the dialling ends. Also, when the call is connected, the automation will stop all delays, which prevents dialling the next numbers.

Question 14

Automation, Multicast - How to receive 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.43.1 with GOLD license  Last updated on 25th of June 2024

Question 15

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 16

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 17

Axis Network I/O Relay - Controlling using HTTP commands

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.   Prerequisities 2N IP Intercom, 2N Access Unit or 2N Indoor Station with the latest firmware Additional GOLD license is neccessary for 2N IP intercom AXIS A9210 Network I/O Relay Module (Order numbers: 2N - 1120303, Axis - 02861-001) - 1 Relay Output    AXIS A9910 I/O Relay Expansion Module (Order numbers: 2N - 1120304, Axis - 02862-001) - 4 Relay Output      Finding the device in the network  The following steps help you find the Axis device on your network  Install and run the 2N IP Utility  Make sure that you are on the same network as the Axis I/O Relay Module  Locate the Axis I/O Relay Module in the device list and click on the IP Address (1)  Then, click on the "Load web interface" button (2)    If you are configuring a brand new device or device that has been reset to Factory Defaults, create a new Account and fill out the password (3)      Lastly, log into the unit (4), using the created credentials          Connecting and configuring the Axis I/O Relay Modules  The following article shows details about AXIS Relay configuration, operation and interconnection between the AXIS A9210 and AXIS A9910 A9210 Detailed manual can be found here  Go under the "Device" tab and "I/Os and relays" (1)  You can check the general Relays overview - change it's name, enable or disable it manually (2)  Under "Toggle port URL" you can see ON and OFF HTTPS commands (3)     A9910 Detailed manual can be found here  First, connect the A9910 Extending Relay Module to the main A9210 Relay Module using the picture below     Follow closely the interconnection shown above (GND -> GND, A -> A, B -> B), use only the shown connectors RS485 (on AXIS A9210) and EXP IN (on AXIS 9910)  Next, set the desired Address of the A9910 Extending Relay Module on the DIP Switch connector according to this chart:    Go under the Device tab and I/Os and relays (1)  Select the AXIS A9910 (2)  An Encryption Key (3) has to be generated in order to add the AXIS A9910       You can generate the Encryption Key by pressing the Generate Key button (5)  You can also export the Encryption Key (6)  Then click OK (7) and proceed further    Make sure that the Encryption enabled (8) is showing  Then click on the Add AXIS A9910 (9) button  Lastly, select a name, used RS485 port, and module Address - as selected on the DIP switch of the device, then hit Save (10)    Once added the expansion module will list the available I/O ports, relays, it's name, address, serial number and upgrade button (11)  You can check the general Relays overview - change it's name, enable or disable it manually (12)  Under Toggle port URL you can see ON and OFF HTTPS commands (13)        Controlling the Axis I/O Relay Module from 2N Units  How to control the Axis device from 2N Units  Detailed API Commands can be found in the VAPIX Library  AXIS A9210 Network I/O Relay (1120303 A) ONhttps://192.168.1.2/axis-cgi/io/port.cgi?action=1%3A%2FOFFhttps://192.168.1.2/axis-cgi/io/port.cgi?action=1%3A%5CON for 2 Secondshttp://192.168.1.2/axis-cgi/io/port.cgi?action=1%3A%2F2000%5C    Sending HTTP commands to AXIS Network I/O Relay by 2N IP intercom or 2N Access Unit  Firmware 3.0+  Login to 2N IP Intercom web interface, section Integration and Switches (1) and select the desired Switch 1-4 (2)  Set up the time limit for the switch to activate by adjusting the Switch-On Duration, under the Configuration (3)    Then under the HTTP Commands set up the Switch-On / Switch-Off HTTP Commands and enter the Login credentials of the AXIS Network I/O Relay, then use the commands from the previous table (4) and save           Firmware 2.50 (LTS):  Login to 2N IP Intercom web interface, section Hardware (1), then select the Switches (2) and lastly select the desired Switch 1-4 (3)  Set up the time limit for the switch to activate by adjusting the Switch-On Duration (4)  Then under the HTTP Commands set up the Switch-On / Switch-Off HTTP Commands and enter the Login credentials of the AXIS Network I/O Relay, then use the commands from the previous table (5) and save.   Now every time when the 2N IP Intercom's switch is activated, the AXIS Network I/O Relay is triggered on and after 1 second triggered off.More information about Switch settings in our manual: 2N IP Intercom - Configuration manual        Sending a HTTPS Command to the 2N Units from AXIS Relay Module when Input is triggered  The following article shows how to set up the AXIS Relay Module to send a HTTPS command to 2N Units Please refer to the 2N HTTP API guide here  First, select the System (1) tab, then Events (2) tab  Next select the Recipients tab and click on Add recipient (3)      Fill out the window accordingly with the corresponding name, connection type, URL and HTTP API account credentials (4) of the 2N Unit - see manual here  Lastly confirm with Save (5)   Next, select the previous window under System and Events - Rules and click on the Add a rule (6)   Select a name (7)  Choose a condition (8) from the list, you wish to send the HTTPS command to the 2N Unit when it is fulfilled  Select a port on the AXIS A9210 (ports from connected AXIS A9910 can be selected as well) (9)  Choose an action and recipient (10) from the list  Next select the corresponding query string suffix (for 2N Units available here) and a method (11)  Lastly confirm with Save (12)     Now, when the corresponding condition is met, the action will be performed - Input activated -> 2N Unit receives into it's Automation HTTP Trigger with ID "BEEP" - it will play a sound *1 - "Modern Ringtone"

Question 18

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 19

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 20

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 21

Connection and configuration of a door contact to 2N IP Intercom/Access Unit

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. A door sensor can provide you information about the state of the door and provide some actions in particular situations, such as announcing an audio message when the door has been opened too long, also sending an email, call and more. Same can be configured in case of an unauthorized door opened. A door sensor can be connected to all 2N IP intercoms with the exception of IP Uni, to an input contact (Input1, Input2, Ext.In1, ...). Connection of a door sensor: First of all it is needed to connect the door sensor to the input of the 2N IP Intercom or 2N Access Unit. For more information, refer to the section Requirements below. How to assign and how to process the information from the door sensor: It is needed to assign the input to the door sensor, go to the section Hardware -> Digital inputs -> Door -> Door Open Sensor ->Assigned Input.  Enable the check box (GOLD license is required) Door Opened Too Long Detection and Unauthorized Door Open Detection  Automation (GOLD license required): There are three event blocks in the automation related to the Door sensor.  DoorOpenedTooLong, UnauthorizedDoorOpened. Some automation examples:  Requirements: For 2N IP/LTE Verso - an input is simply in the PCB. No special requirements. Additional inputs are available.   2N IP Solo - an input is simply in the PCB.  For 2N IP Vario - a Card Reader 125kHz is required.  For 2N IP Force - an Additional Switch + Tamper or any ´type of a Card Reader is required.  For 2N IP Safety - an Additional Switch + Tamper is required.  For 2N IP Base - an input is simply in the PCB. No special requirements.  2N Audio/Video Kit – 2 input connectors are equipped. No special requirements.  2N Access Unit - 3 input connectors are equipped. No special requirements.  2N Access Unit 2.0 - 2 input connectors are equipped. No special requirements.

Question 22

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 23

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 24

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 25

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 26

External IP Relay 9137410E & 9137411E - Controlling using HTTP commands from a 2N IP intercom or 2N Access Unit

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.   Do you need an intercom to switch on lights or call a lift, but the switched devices are far away and laying cables all the way to the intercom isn’t an option? Use an external IP relay, which is controlled using HTTP commands from a 2N IP intercom or Access Unit. The command is sent to the relay in unsecured form.    Prerequisities 2N IP intercom or 2N Access Unit with the latest firmwareAdditional GOLD license is neccessary for 2N IP intercom External IP Relay from 2N 9137410E (1 output)9137411E (4 outputs)    Web interface of External IP Relay Control page If you have your IP relay in the default setting, open your web browser and enter IP address 192.168.1.2, then you should be able to see control page depending on the version of the product you own. If you are not able to access the IP relay web interface, then please check if your computer is in the same network as IP relay (PC must have an IP address 192.168.1.x).    Setup page For entering the IP relay setup page, type to web browser http://192.168.1.2/setup.htmlUsername: adminPassword: webrelayNow you can configure its parameters according to your needs.e.g. network parameters (change IP address), look of the control page, relay pulse duration.      Detailed information about the IP relay settings and additional features is found in the manual linked below. Manual for External IP Relay     HTTP commands to control External IP Relay outputs   External IP Relay with 1 output (9137410E) Pulsehttp://192.168.1.2/state.xml?relayState=2ONhttp://192.168.1.2/state.xml?relayState=1OFFhttp://192.168.1.2/state.xml?relayState=0    External IP Relay with 4 outputs (9137411E) Pulserelay 1http://192.168.1.2/state.xml?relay1State=2relay 2http://192.168.1.2/state.xml?relay2State=2relay 3http://192.168.1.2/state.xml?relay3State=2relay 4http://192.168.1.2/state.xml?relay4State=2ONrelay 1http://192.168.1.2/state.xml?relay1State=1relay 2http://192.168.1.2/state.xml?relay2State=1relay 3http://192.168.1.2/state.xml?relay3State=1relay 4http://192.168.1.2/state.xml?relay4State=1OFFrelay 1http://192.168.1.2/state.xml?relay1State=0relay 2http://192.168.1.2/state.xml?relay2State=0relay 3http://192.168.1.2/state.xml?relay3State=0relay 4http://192.168.1.2/state.xml?relay4State=0    Sending HTTP commands to External IP Relay by 2N IP intercom or 2N Access Unit Login to 2N IP Intercom web interface, section Hardware - Switches.For the used switch setup Switch-On Duration and Switch-On and Switch-Off HTTP Commands, use the commands from the previous table.   Now every time when the 2N IP Intercom´s switch is activated, the IP relay is triggered on and after 5 second triggered off.More information about Switch settings in our manual: 2N IP Intercom - Configuration manual

Question 27

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 28

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 29

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 30

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 31

How to integrate 2N IP Devices with MS Teams

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 integration will allow you to make audio calls from our intercoms to linked MS Teams accounts and is handled by Microsoft SIP Gateway - for more details please see https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan   Requirements: 2N IP Device with firmware version 2.46.1 or newer MS Teams license* (this license is not part of the standard GOLD license and needs to be purchased separately)  EMEA license number: 9137921AXIS license number: 03160-001  MS Teams account (https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan) For a single 2N device, it's recommended to use a Microsoft Teams Shared device license.Microsoft Teams Shared Devices licensing - Microsoft Teams | Microsoft Learn *MS Teams license is only required for 2N IP Intercoms and SIP Audio Devices   Please note that the MS Teams integration is not available on OEM product versions    Step by step guide for direct MS Teams integration Checking intercom and license requirements  For firmware 3.0 and newer 1) Navigate to section System - License and check whether your intercom have MS Teams Integration license activated. You can find this license in Paid License section:    For firmware 2.50 and LTS (Long Term Support) 1) Navigate to section System - License and check whether your intercom have MS Teams Integration license activated. You can find this license in Paid Licenses section:     For firmware 2.46 1) Navigate to web interface of your intercom, section System - Features. Once there make sure that Microsoft Teams feature is in state Running. You can change this state by clicking on button Start/Stop in the action column. If you turn on this feature you have to restart your intercom in order for this change to take place. 2) If you cannot find Microsoft Teams in list of Beta features make sure to check whether your intercom is updated to firmware 2.46.1 or newer.      3) Navigate to section System - License and check whether your intercom have MS Teams Integration license activated. You can find this license in Paid Licenses section:      4) Backup the configuration and update to the latest firmware version   Configuring Intercoms to connect to MS Teams provisioning server  For firmware 3.0 and newer 1) After you check whether you have correct license and whether your Microsoft Teams license is running you can navigate to menu Integration - Calling - MS Teams.    2) You need to get provisioning address specific for your region (your region will be based on where your intercom will be connecting from, region in which MS Teams user is located can be different). This address can be found at official Microsoft webpage: https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure  3) Click on Microsoft Teams Enabled checkbox in order to enable integration and changes to be made to this page. Afterward navigate to Provisioning Server Settings and fill in your specific provisioning address into Server Address field. Then click on Save in order to save changes made to the page.  4) You can view boarding process in tab Configuration Update Status. You should have status Updated in both common config and private config part  5) Sign In button will now become available on top of the page, in section Service.  6) Click on Sign In button. This should bring up link to MS Teams website and pairing code.  7) Open website link in your web browser and copy Pairing code into marked field. Then click on Pair button 8) You should receive successful authorization message. If not, try to go back into your intercom web interface, close window with the pairing code and then open it again. This will generate new pairing code for you which you can try to input into pairing website again. 9) In your intercom web interface you should now see your intercom in Online status and a notification about successful registration to the terminal SIP server. You can also view a phone number that is assigned to your intercom by the MS Teams service. If the registration does not go through, you can click on the Update button and wait.     For firmware 2.46.1 to 2.50 and LTS (Long Term Support) 1) After you check whether you have correct license and whether your Microsoft Teams license is running you can navigate to menu Services - Integration - MS Teams.       2) You need to get provisioning address specific for your region (your region will be based on where your intercom will be connecting from, region in which MS Teams user is located can be different). This address can be found at official Microsoft webpage: https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure        3) Click on Microsoft Teams Enabled checkbox in order to enable integration and changes to be made to this page. Afterward navigate to Provisioning Server Settings and fill in your specific provisioning address into Server Address field. Then click on Save in order to save changes made to the page.    4) You can view boarding process in tab Configuration Update Status. You should have status Updated in both common config and private config part  5) Sign In button will now become available on top of the page, in section Service.     6) Click on Sign In button. This should bring up link to MS Teams website and pairing code.   7) Open website link in your web browser and copy Pairing code into marked field. Then click on Pair button    8) You should receive successful authorization message. If not, try to go back into your intercom web interface, close window with the pairing code and then open it again. This will generate new pairing code for you which you can try to input into pairing website again.  9) In your intercom web interface you should now see your intercom in Online status. You can also view phone number that is assigned to your intercom by the MS Teams service.     Creating users using MS Teams phone number You can now create users in 2N IP Intercoms using MS Teams phone numbers in order to call from intercom directly into MS Teams desktop or phone application.  For firmware 3.0 and newer 1) Navigate to menu Directory and click on Add User button.   2) Fill in fields Name and Phone Number. Choose call type MS Teams, the phone number needs to be entered in format msteams: followed by full phone number you have been provided by MS Teams for receiving unit. After you enter the phone number, press the Confirm button and save the user.  3) In case you also need to receive calls from MS Teams to your intercom, you can change call answering mode (how calls will be accepted). By default MS Teams incoming calls are in mode Manual Pickup which means you need to press button on your intercom to accept the call. This can be changed to Do not accept calls ( always busy - automatic rejection) or Answer Automatically (calls will be immediately connected). You can change this setting in following menu: Calling - General Settings - MS Teams call answering mode    For firmware 2.46.1 to 2.50 and LTS (Long Term Support) You can now create users in 2N IP Intercoms using MS Teams phone numbers in order to call from intercom directly into MS Teams desktop or phone application. 1) Navigate to menu Directory - Users and click on Add User button.  2) Fill in fields Name and Phone Number. Phone number needs to be entered in format msteams: followed by full phone number you have been provided by MS Teams for receiving unit. After you enter both name and phone number you can save these information by button Save.     3) In case you also need to receive calls from MS Teams to your intercom, you can change call answering mode (how calls will be accepted). By default MS Teams incoming calls are in mode Manual Pickup which means you need to press button on your intercom to accept the call. This can be changed to always busy (automatic rejection) or automatic pickup (calls will be immediately connected). You can change this setting in following menu: Calling - General Settings - MS Teams answering mode

Question 32

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 33

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 34

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 35

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 36

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 37

KNX connectivity with 2N IP Intercoms

Accepted Answer

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

Question 38

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 39

License Plate Recognition (LPR)

Accepted Answer

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

Question 40

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 41

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

Accepted Answer

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

Question 42

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 43

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 44

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 45

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 46

REX button connectivity

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 certain situations (e.g. in areas with higher level of security such as an ATM room or kindergarten), you want to control the door opening even when person is leaving. For this purpose you can connect REX (Request To Exit, or just "Exit") button to 2N IP Intercom or 2N Access Unit and once the button is pressed, device triggers the lock.       Prerequisities 2N IP Intercom or 2N Access Unit with the latest firmware; no additional licence is required.The device must be equipped with at least one free input.Most of our devices have at least one input on the main unit, here is an exception:2N IP Force & 2N IP Safety & 2N IP Variorequiring additional module2N IP Unidoes not have input at all, does not support REX button connectivity Any REX (exit) button with prepared two wirese.g. the one from 2N: https://www.2n.com/products/exit-button   Connectivity Connect REX button to the device input via two wires. Here is a demonstration on 2N IP Verso, another models can be little different, please check their installation manual.Normally opened (the first picture) or normally closed (the second picture) type, both have the same connectivity, but the configuration will be different.     Configuration Go to device web interface, section Hardware - Digital Inputs.Check the assigned switch to see if it is the one used for access control, usually the default Switch 1 value is the right one.Assign the input to which you´ve connected the REX button in previous step (in our case "Input 1")and set the right input mode; Non Inverted for Normally opened type, Inverted for Normally closed type.

Question 47

RTP destinations - How to test it with VLC media player?

Accepted Answer

In case you would like to test RTP destinations and you do not have any devices which supports this feature, you can use VLC media player instead of the device. This "how to manual" will show you, how easy it is to set it up and make it work. As a first step download the VLC media player and run the installation on your PC.  Setting up 2N IP Audio Control Panel  run 2N IP Audio Control Panel – use the Tray Icon in the right bottom corner  RTP destinations feature is under the license, but in default is 1x RTP license for free. To test this feature you do not need any licence.  In case you need to use more than one RTP destination, ask for license: 1x RTP add on license order number: 914202E. Send your request to email:  sales@2n.com or to your sales representative. Together with the license order send the ID key of the computer on which is the 2N® IP Audio Manager running. This ID key can be found in menu: Administrator/ Licences - see picture below:    use the Add licence button to upload it  choose the path to the licence key on your PC  licence will be added and displayed in field Licence features – see picture below    Now you can create more RTP destinations up to the license limit    Creating RTP destination  in menu Destinations & Zones go to bookmark All Destinations. Here you can create RTP destination: right mouse click button in the field, where are displayed 2N® Net Audio Decoder units or in left menu click on Create RTP destination.    after creating RTP destination you can edit its properties: Audio codec, IP address, Port, TTL parameter keep it in default (-1), or according your network setting you can change the value.  if you are going to use VLC media player on the same PC where does 2N® IP Audio Manager run, it is needed to change at least the port 6999 – this port is a communication port of 2N® IP Audio Manager and it is therefore already occupied and the RTP stream would not have to work.    go to menu Sessions and Create session, add some source e.g. play-list or internet radio and use the RTP destination as a destination together or instead of 2N® Net Audio Decoder units.   Setting up the VLC media player  run the VLC media player  go to menu Media and choose option Open Network Stream    enter the full IP address, including the protocol and port from which stream you want to capture.    you can now listen to the music via RTP stream which you have created.   TIP: for better sound quality you can use/setup in RTP destination a better codec for streaming: Linear PCM 16bit Stereo

Question 48

Scheduler - How to set up

Accepted Answer

To make a scheduled announcement, proceed the following steps (this setting was made in FW version 1.3.9.78.21):  In Audio Sources - create a playlist which will consist of the message, announcement, music file(s) which you want to play at the scheduled time  In Sessions - create new session, insert the playlist with announcements into this session (from previous step) and on the right side add a destination where the announcement should be played at the scheduled time  Start the session by pressing the PLAY button. The playlist then starts playing, so click the STOP button ON THE PLAYLIST, not on the session. Now the playlist in active session is ready to play using the Scheduler  Drag the PLAY icon and drop it on the Session below. When you drop it, you may shift it to the time that you want - this will modify the DELTA TIME in Action properties (on top right side of the screen)  click on Save configuration In Scheduler - click on CREATE EVENT and enter the START TIME   Now wait for the scheduled time and at that time will be the Announcement played

Question 49

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 50

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 51

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 52

Time Profiles

Accepted Answer

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

Question 53

Troubleshooting basics – Configuration backup, network trace, syslog and ping tool on 2N IP Intercoms

Accepted Answer

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

Question 54

Video - 2N IP intercoms - Calling multiple destinations in sequence and in parallel by pressing one button

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 firmwareAn answering unit based on SIP protocol   Video tutorial Please note, in firmware 2.43, the 2N OS Web GUI has been reorganized,dialing methods and SIP account details are now in    the new section Calling   .

Question 55

Video - 2N OS devices - Factory Reset procedure

Accepted Answer

Video - 2N OS devices - Factory Reset procedure Prerequisites  2N OS device with RESET button Access Unit, Access Unit 2.0Indoor CompactIndoor TalkIndoor ViewIP Audio KitIP BaseIP ForceIP SafetyIP SoloIP VersoIP Video KitIP UniLTE Verso        or 2N OS device with CONTROL button IP OneIP StyleIP Verso 2.0(all Axis ARPTEC processor devices)  Factory reset procedure using RESET button  Factory reset procedure using CONTROL button Find the CONTROL button, located among the main unit connectors.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.

Question 56

Video - Configuration of 2N IP intercom with 2N IP Eye

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 Eye is a freely available application that displays video from an IP intercom on your PC in the event of an incoming call. This makes it the ideal solution if you have a regular desktop IP telephone that does not display video. The application can also be used as a video surveillance tool.  Prerequisites 2N IP intercom with the latest firmwareAn answering unit based on SIP protocol for using video pop-up functionality during call2N IP Eye (the latest version) installed on your PC, download application here   Video tutorial

Question 57

Virtual Numbers and Telephone Mode

Accepted Answer

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

Question 58

Virtual Sound Card - Login was unsuccessful

Accepted Answer

While first attempt to log in to the 2N IP Audio Virtual Sound Card you might experience access right conflict. This conflict results as login was unsuccessful message.  This situation is caused by different set of access rights used during installation and the set of user attempting to open the application. Delete the configuration database file config.db in order to resolve this conflict.It can be found on the path C:\ProgramData\2N TELEKOMUNIKACE\2N NetSpeaker\Virtual Sound Card\2.0.4.0.16_BRANCH-rel (valid for Windows 7).  During next attempt to open the application is new configuration database file created with correct access rights. In case you are still experiencing login problems, please, check user settings in 2N® IP Audio Control Panel.

Question 59

VoIP trunk - How to setup with IP phone

Accepted Answer

Thanks to the VoIP interface integration you can do live announcement to the 2N Net Audio Decoder system from any IP phone or IP PBX/SIP proxy. In this FAQ you can see an example of using IP phone in mode point-to-point (without registration to the IP PBX). What is important to know:  VoIP trunk is used as an Audio Source in Session with defined destinations  VoIP trunk is always created between 2N IP Audio Manager and IP devices (IP phone, IP PBX / SIP proxy)  VoIP trunk supports two modes:  point-to-point (not registered) IP device is calling IP address of the PC on which is 2N IP Audio Manager running and port which is defined in VoIP input  registered to proxy - VoIP trunk is registered to the account created on IP PBX/SIP proxy. To make an announcement you are calling number of the account under which is VoIP trunk registered.   After the call is established, caller can hear a GONG and after that can do the announcement  Supported codecs: G.711a   Setting up the announcement: To make an announcement via 2N IP Audio Manager we use IP phone, which is not registered to IP PBX. Call (VoIP trunk) would be in mode point-to-point. From IP phone we would call IP address of the PC on which is running 2N IP Audio Manager and port which is defined in Local VoIP input. 10.0.14.23 - IP address of the PC on which is installed 2N IP Audio Manager 5061 - listening port in created VoIP trunk 10.0.14.37 - IP address of the IP phone. To make a call we are going to use speed dial button.  run 2N IP Audio Control Panel applicationin menu Audio Sources click on Create VoIP input. Choose mode Local VoIP input. If needed you can change listening port. Save configuration.    in menu Sessions create new Session and add VoIP input as a source. Add destinations to which should be the announcement routed.    that is all what you need to setup in 2N IP Audio Control Panel  IP phone setting (Well T26)  In the next step, set the call from IP phone under the speed dial button, so you do not have to manually dial the entire string of characters that should be dialled when using point-to-point mode.Speed dial button - setup the following string: sip: x@10.0.14.23: 5061 (x - non existing user, 10.0.14.23 - IP address of the 2N® IP Audio Manager , 5061 - VoIP input listening port )    by this step is all needed setting done. To make an announcement press the speed dial button and after the GONG sound you can start to talk.  Tip: to dial only number of the extension/account e.g. 101 you need to use IP PBX/SIP proxy and registered VoIP trunk. When you hear GONG but no voice, check if you are not running ethernet and WiFi connection at the same time. As a next option you can try to switch OFF and ON 2N® IP Audio Manager.

Question 60

Web scheduler - How to work with 2N IP Audio Web Scheduler

Accepted Answer

n case you would like to connect to the 2N IP Audio Web Scheduler you will need User name, Password and Authorization. All can be set in the program Control panel by your Administrator in the Section Users and groups      Web Scheduler is available at   https://manager_ip_address:4433   or   https://web.scheduler.cz:44  33 if the network administrator sets a domain name for access.   1. Login: Enter the address into the browser to display the login page. Enter your user name and password and confirm.   2. Calendar: View the calendar in a weekly or monthly mode. The month view shows the day plan events for each day of the month.   The week view displays the event time too. Click the event to display the day plan detail.    3. Day Plans: The Day plans menu displays a list of all daily plans created.  The list includes the following columns:  Name – day plan name  Colour – colour in the calendar  Priority – day plan priority  Delete – delete a day plan  Click a list row to display the day plan details. Click  to create a new day plan.     4. Events    Time – event start time    Type – even type (playlist only for now)    Name – playlist name    Delete    Click  to create a new event.   Click an event in the list to edit the event details.     As the whole playlist is always played, make sure that the playlist content is as long as the event duration.     5. Destination: You can add devices, zones or all destinations.    Name  Delete    Click  to create a new destination.      6. Recurrence: Use the icon or click any of the Recurrence parameters to set recurrence.   Range of recurrence  Start – day plan start date  No end date – unlimited day plan recurrence  End after number of recurrences – deactivate the day plan after a defined count of recurrences  End by certain date – deactivate the day plan on the defined day  Daily recurrence  Recur every day – recur the day plan every day  Recur on certain weekdays – select weekdays and holidays  Recur one day in a month – select a day in a month  Weekly recurrence  Recur every week – recur the day plan every week  Recur every odd/even – select odd or even weeks  Select week to recur – select a week in a month  Exceptions  Date – exception date  Day plan – apply/do not apply the day plan on this day  Delete  Click  to create a new exception. Click an exception in the list to edit the exception details.  Exception date  Apply/Do not apply the day plan on this day  Apply every year  General Properties  Name – day plan name  Priority – day plan playing priority  Colour – day plan colour in the calendar  Caution    Do not set identical priority values (including sessions) to avoid unwanted behaviour.      7. Setting The menu consists of the following two sections:  Holidays – define holidays  User account – language (English or Czech) and calendar (Show weekends in the Calendar) settings  Holidays Click  to add a holiday. Click a holiday in the list to edit the holiday details.

Lista pytań