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 Analog Intercom / Busy tone - Parameters setting

Accepted Answer

The call termination on 2N Analog Intercoms devices can be done as described below:  The busy or continuous tone *) after the call end.  The ringing tone *) after a predefined count of rings.  The subscriber 'at the other end' pressed  .  The preset maximum call duration has elapsed.  30 seconds after the switch use has elapsed.  A 2N Analog Intercom button was pressed during the call.  The  keypad button was pressed during the call (can be disabled).  *) The communicator is able to detect a permanent tone, busy tone and ringing tone even if the tone has two frequency components as in the UK, the U.S.A. (the so-called BTT tone) and in Canada. This new function does not require setting of any parameter. One of the tone components must be of 440 Hz.   In case that the device would not detect the Busy tone (or continuous tone) correctly you have to verify the setting of parameters described bellow 941 Minimum continuous tone time, if the tone is longer, the intercom hangs up. (default value 20=2s, range 10-99) 942 Minimum busy tone or pause duration, this parameter control the busy tone detection. They are used for call termination. (default value 8=0,08s, range 0-255) 943 Maximum busy tone or pause duration, this parameter control the busy tone detection. They are used for call termination. (default value 8=0,08s, range 0-255) 944 Maximum tone-pause difference, this parameter control the busy tone detection. They are used for call termination. (default value 8=0,08s, range 0-255)     Explanation of Parameters 942, 943, 944 Busy tone pic. 1 The parameter 942 has to set regarding to the shorter part of the busy tone. In case that the period of tone time is longer than pause time we must set the parameter for pause. Example The busy tone in the pic. 1 in the figure above is considerably longer than the pause time. Therefore, set parameter 942 according to the pause, to 200 ms, e.g., and parameter 943 according to the tone, to 600 ms, for example. In this case, however, the default values can be maintained for both the parameters. Since the tone – pause difference is 500 − 250 = 250 ms, set parameter 944 to 300 ms, for example.  In some cases can also help to increase parameter 944 also when 2N Analog Intercom is placed in a hall or corridor with a large decay time.

Question 3

2N Analog Intercom does not work after installation

Accepted Answer

Check with the help of the Manual, if the cables are connected correctly  2N Analog Intercom should play the „booting sound" when you connect the analogue telephone line.If not, contact your local 2N distributor

Question 4

2N Analog Intercom hangs up - does not hang up automatically

Accepted Answer

Make sure that the busy tone from the PBX is the standard PSTN busy tone  Check the settings of the 2N Analog Intercom (parameter 945, see the manual, chapter 9)  Record the busy tone (wav, mp3, aiff, wmv, arm) and contact your local 2N distributor

Question 5

2N Analog Intercom - How to provide all information to effectively resolve a technical issue

Accepted Answer

Dear customers, In case you have found some problems with the device, please report it to https://support.2n.cz/. If you do not have access informations, contact your account manager. Reported issue should contain following information:   Please describe us your problem in detail, so that we will be able to replicate the behaviour based on that description.   Exact problem description  Serial Number  Firmware version  Hardware version (PCB)  Configuration - list of all changed default parameters and their values  Any information that you think might help us to solve the issue

Question 6

2N Analog Intercom / Incoming call - does not accept the incoming call

Accepted Answer

Check if the CLIP function is OFF for telephone line, to which is 2N Analog Intercom connected  Check if 2N Analog Intercom is connected on telephone line in single way (no parallel interconnection)  Check the telephone line voltage (minimum must be 20V)    contact your local 2N distributor

Question 7

2N Contact Centre Solution installation

Accepted Answer

1) First of all – you need to upgrade your NetStar to version 4.2.0 or higher ( how to upgrade NS find on: How to make a firmware upgrade of 2N NetStar) or use Netstar SW version 1.2.2 or higher. 2) Create User in your NetStar (in section User- Users & Groups). By this User will Contact Centre communicate with NetStar!  We created User: connect. Now we need to create login and password to this user. (In section Users – User rights.)    3) Install the 2N Contact Centre Solution. HW requirements are ( 64b processor, 4GB RAM, 100GB HDD). It can be Virtual macine, Server or PC in the same LAN Network as 2N NetStar is! Software is distributed with Cent Os 6.4 systém – which will be installed as well. If you are going to install Contact Center Solution on the virtual PC you need to enable virtualization (used as the hardware acceleration) on the BIOS. Below all the step of installation are described.   4) Select the first option or just wait. 5) Then the systém will request to select one of the options below.    6) Installation will take approximately 15 minutes. After the installation is complete you will be requested to reboot the system.    7) In Network section it is important setup Bridge Adapter.  8) Eject installation disk from CD-ROM. Enter login and password. By default login is admin, password is 2n. 9) Select language and proceed with settings.    10) Then enter IP address of CCS or its domain name       11) Select network interface for communication with Netstar and users (in the figure there is only one available Ethernet interface)      12) Enter IP address of Netstar      13) Enter TCP port for communication with Netstar, by the dafault it is 6543      14) Enter login/password to connect to Netstar (we have created user the Contact Center user with login - connect and password - connect. After the connection is established you will be requested to press any key.      15) In this menu you can modify basic parameters of CCS      16) Connect to CCS via your web browser (recommended: Mozilla Firefox, Chrome, IE v.10) Use login: superadmin, password: 2n      17) Upload the license which you received from Technical support department and create a company by clicking to “+Add” button      Now your CCS is ready to be configured.

Question 8

2N IP Audio Control Panel setting

Accepted Answer

in menu Destinations & Zones go to bookmark All Destinations  Here you can create RTP destination: use right mouse click button (flow menu) in the field, where are displayed 2N Net Audio Decoder units or in left menu click on Create RTP destination.  Note: there is 1x RTP destination license for free. In case you would like to test multiple RTP destinations you need to get additional license. More information about the RTP license in this FAQ   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    Create the Session with some source e.g. playlist and in the field Destinations add your created RTP destination 1    This is all what you need to setup in 2N IP Audio Control Panel  BARIX unit setting  log in to the unit web interface  go to menu CONFIGURATION    go to Advanced Settings  choose Streaming  setup RTP mode ON  setup Recieve Audio from IP: Port according your setting in RTP destination which you have created in 2N IP Audio Control Panel      check the Audio setting: uLaw / 8 kHz (G.711)    Now you can receive on BARIX unit an audio stream from 2N IP Audio Manager. Do not forget that you can use BARIX unit also as a source of RTP stream. This depends on the type of BARIX unit which you use.

Question 9

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 10

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 11

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 12

2N IP Intercoms - External IP camera connection (Axis IP camera guide included)

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 add an external IP camera to the 2N IP Intercom to see second video stream e.g. during call. IP camera can be placed for example behind the front door as well as somewhere outside the building. This is very useful because you can check if the calling person is there alone, if he/she already enters the building, if there is some intruder next to him/her, etc. It is possible to specify which picture will be the first one that you see when somebody calls from the intercom – would it be a picture from internal camera or from external camera? Then you can easily switch between them. 2N IP Intercom is processing stream from external camera by itself, so SIP video call will use still the same codecs no matter what camera input is used.   Prerequisities 2N IP Intercom with the latest firmware2N IP AudioKit and 2N IP Uni are not supportedGOLD license is necessaryMore information you can find here: Model Differences and Function Licensing A supported answering unit for switching between internal and external camera during call2N Indoor Compact with the latest firmware2N Indoor Touch 2.0 with the latest firmware2N Indoor View with the latest firmwareMy2N app the latest versionMore information here: My2N platform - registration and setup of cloud calling3rd party video SIP phone IP camera providing RTSP stream Required resolution: 640 x 480 pxRequired coding format: H.264 Baseline or  MJPEGAlready tested IP cameras: 2N® IP Interoperability / IP Cameras Axis IP Camera instructions:Create a new stream profile in the camera with the following settings:H.264 Baseline or MJPEG coding format640 x 480 px resolution15 FPS frame rateBitrate limited to 5Mbps Use the following address to obtain the stream: rtsp://CAMERA-IP/axis-media/media.amp?streamprofile=PROFILE-NAME      Adding external IP camera to 2N IP Intercom Go to 2N IP Intercom web interface, section Hardware - Camera - External Camera.Enable the feature.Fill in RTSP stream address in following format: rtsp://ip_camera_address/parameters (parameters depends on the connected IP camera model).Fill in the username and password if the external IP camera requires authentication.After saving, you should be able to see Camera Preview if you configured everything correctly.       Common issues you can meet:State: Connected > Unsupported resolutionReason: Resolution is higher than 640 x 480 px or not in aspect ratio 4:3       State: Network errorReason: Wrong format of RTSP stream address, e.g. invalid IP address.        State: UnauthorizedReason: Invalid username or password         Select the default video source (from internal or external camera) Still you will be able to switch between them during call.        Switch between internal and external camera during call We will show you how to enable this feature on supported answering units. 2N Indoor Compact or 2N Indoor ViewGo to the device´s web interface - Directory - Devices.Add 2N IP Intercom to the devices list and enable viewing the external camera.Then you will see the camera icon during call.      2N Indoor Touch 2.0 Go to the 2N IP Intercom web interface. In section Hardware - Switches configure the switch, you chose for the control of the cameras, parameter "Switch Mode" has to be set to "Bistable".         In section Services - Automation configure the function to switch between cameras by activating the selected switch.More information: Automation manual        Now you have to tap and hold the padlock icon during call until the 4 locks representing 4 switches in the 2N IP Intercom appear. After that, you can easily switch between the cameras by tapping on a particular switch you've used in the 2N IP Intercom configuration.     My2N app Go to the My2N platform portal - Devices section and open the IP Intercom details.In the 2N Mobile Video part enable External Camera.Then you will see the camera icon during call.        3rd party video answering unit This devices can switch between internal and external camera by sending DTMF code thanks to set automation function in 2N IP Intercom.All the procedure is described in this video:       Get RTSP stream from 2N IP Intercom You can get RTSP stream also from our 2N IP Intercom to behave as an IP camera in VMS systems.   Go to 2N IP Intercom web interface - section Services - Streaming and enable RTSP server.Generate the RTSP Stream URL and create a user account for the stream authentication.         Now you can capture the stream e.g. by VMS system or VLC Player.VLC Player - How to watch and record video from 2N IP Intercom

Question 13

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 14

2N IP Intercoms - How to add user access credentials

Accepted Answer

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

Question 15

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 16

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 17

2N IP Intercoms – Integration with 3rd party NVR/VMS systems without ONVIF and RTSP

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've got a 2N IP intercom and would like to integrate it with your NVR or VMS systems. Your first choice would usually be to use ONVIF but this requires the GOLD license. Or maybe you'd just like to quickly take a look who's in front of your intercom from your web browser?   For cases like these, you can view the camera feed using HTTP API   Prerequisites 2N IP intercom with the latest firmware, equipped with a cameraNo additional license is required.   HTTP API setup Access the camera feed securely, in section Services - HTTP API, keep the Secure (TLS) connection and Digest authentication.    Then choose an Account, enable it, pick a Username and Password combination according to your preferences and in User Privileges enable Camera Access.    How to view the camera feed Enter the following string into any of the following programs and replace IP_address with your intercom's respective IP address.https://IP_address/api/camera/snapshot?width=1280&height=960&fps=15    You can adjust the following image parameters to save on bandwidth:https://192.168.1.100/api/camera/snapshot?width=1280&height=960&fps=15Width and Height define image resolution in pixels, 1280×960px is the maximum.FPS defines how many frames per second the stream will have, the maximum is 15.  If you're getting poor framerate or would like to save on bandwidth while keeping high resolution and framerate, you can change the default JPEG compression quality down to 50.    Where to view the camera feed Web browserThe easiest way to view the camera feed would be from your web browser. Just enter the above string into your web browser's search field. You'll be asked to enter the HTTP API Account credentials you filled in previously. Shortly after, the camera feed appears in your web browser.     VLC media playerVLC media player can open various media formats, one of which are network streams.Because VLC does not support digest authentication, at first we must go to the IP intercom web interface and change the Camera API authentication to Basic.    Now in VLC, go to "Media - Open Network Stream".  The following window opens, enter the above mentioned string.  If the IP intercom still has the self-signed HTTPS certificate, the following warning can be shown. To continue please view certificate and accept.   Now you should be asked to enter the HTTP API Account credentials you filled in previously.If you see some error message instead, close the message and repeat the previous steps.     NVR and VMS systemsThe same string would get you image in any NVR or VMS system that supports it.

Question 18

2N IP Vario - Reseting issue resets to default values after power supply reset

Accepted Answer

Remove the front panel from 2N IP Vario and check if you do not have jumper in the position for reset to default values according to the picture below. Jumper has to be in the position for normal operation!Note: it depends on the PCB version which jumper is used!    If you have 2N® IP Vario with display, please check if the switch on its right bottom corner is in "Normal" position according to the picture below.    For more information about jumpers and PCB versions please read the installation manual for appropriate 2N IP Intercom.  If the jumper is in "Normal" position and you still face automatic reboot procedure, please make hardware factory reset as shown above and then put the jumper back to the "normal" position!  If the previous step does not solve your troubles, then contact your local 2N distributor or 2N technical support via https://support.2n.cz/

Question 19

2N LTE Verso - How to perform factory reset

Accepted Answer

Factory Reset 2N LTE Verso is equipped with a RESET button. Press the button shortly (< 1 s) to restart the system without changing configuration. Follow the instructions below to reset the factory default values: Press the RESET button.Wait until the red and green LEDs on the device come on simultaneously (approx. 20 s).Wait until the red LED goes off (approx. 5 s).Wait until the green LED goes off and the red LED comes on again (approx. 5 s).Wait until the red LED goes off (another 5 s).Release the RESET button.  Firmware v2.26 and newer:  + SOUND SIGNALISATION - release the button after 4 short beeps immediately    Caution: In case of resetting the factory default settings on a device with a firmware v2.18 or newer it is necessary to reprogram the 2N Security Relay using the instructions from section Main and Extending Modules. From FW v2.26 the intercom performs audio feedback during the resetting procedure.  More information:        2N IP Intercoms (official 2N web)

Question 20

2N LTE Verso - Registration to My2N and basic setup

Accepted Answer

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

Question 21

2N Meeting Room user guide

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 Meeting Room app is an application for simple room management. It shows actual and upcoming events and allows you to create new reservation of the meeting room directly from the application. This application makes the reservation process of the meeting room more flexible and more user friendly.      Basic features:     Show events for specific meeting room    Room reservation    You can see details of the event    Support Outlook, Exchange , Gmail and Zimbra calendars    Widgets ( weather forecast, time, custom logo)      Requirements    2N Indoor Touch 2.0 with firmware version: 4.3 and higher  2N Meeting Room app license (Part number: 91378396)           Content  How to activate 2N Meeting Room app First step is to activate the 2N Meeting Room application by using license. License can be loaded into the device by using web interface of the unit.      Once the license will be enabled on the unit, you can activate the 2N Meeting Room application in the same section on the web interface of the unit.       Warning   Once the 2N Meeting Room app is activated, the unit does not respond to any calls and the 2N Meeting Room app is the only application that will be running on the unit. You can disable the 2N Meeting Room application again.   The reason why you can't make the call to the 2N Indoor Touch 2.0 while 2N Meeting Room is active is to avoid unwanted calls and to keep the overview of meeting room events always on the the screen.   2N Meeting Room is running always on the foreground.     Connection to calendars Once the 2N Meeting Room app is active, you can see the following dashboard on the 2N Indoor Touch 2.0.   The following calendars can be used:  Zimbra  Outlook  System Account - Exchange / IMAP connection  Gmail  Demo account   Outlook connection Choose Outlook option and sign in.        Once you are signed in, you can choose specific calendar of the Outlook.       System account (Exchange) connection Choose System account option and add system account.    Choose Exchange and fill in your account details and follow the instructions.     You may be asked to activate device administration and also PIN code if the company has more restricted security polices.   Gmail connection Sign in to your Gmail account   Choose specific calendar       Home screen You can see the overview of the events by clicking on home button in the upper right corner.   There are 3 situations that may occur on the home screen  A meeting room is available - If the meeting room is available you can schedule ad hoc event directly from the home screen by clicking on "+" button and choose a specific time frame for the meeting. You can choose between 5 min, 15 min and 30 min time frame. Once added, temporary event will be scheduled in the calendar of the meeting room. This function can be used for the quick room reservation. If the meeting room is available, the green LED diode is active.  Upcoming event is scheduled and needs to be confirmed - Scheduled event needs to be confirmed before the start of the event, otherwise it will be erased from the meeting room calendar. You can enable automatic confirmation in the section Settings - Personal - Automatic confirmation  Meeting room is occupied - If the meeting room is occupied, you can see when the meeting ends, attendees of the meeting or cancel the meeting. Cancellation of the meetings can be enabled in the section Settings - Personal - Events that may be cancelled. If the meeting room is occupied, the red LED diode is active.     A meeting room is avaliable        Upcoming event is scheduled and needs to be confirmed               Meeting room is occupied

Question 22

2N NetStar - Initial configuration - How to start?

Accepted Answer

In this document you will learn how to set the initial configuration of 2N NetStar. After having read this document you should be able to:  connect to the NetStar via COM port (serial cable is attached to each NetStar delivery)  configure network, time and system service parameters via COM port  set the basic parameters of the NetStar with the help of configuration wizard  explain the basic difference between online and offline database   Connection to the NetStar via COM Each 2N NetStar delivery includes a standard serial cable for the PC – 2N NetStar connection. It is a six-core telephone cable which has RJ11 connector on one side and RS-232 female connector on the other side. For connection from your PC to 2N NetStar you need to use HyperTerminal program or Putty. Set the Serial communication with these parameters:  Transmission speed: 115 200Bd  Data bits: 8  Stop bits: 1  Parity: None  Flow control: None  After connection to the 2N NetStar you have to enter the correct username and password in order to get access to the Main Menu of the configuration interface. The default Administrator settings are as follows:  Username: Admin  Password: 2n   In Main Menu you can see four options for settings and you can also see there the actual firmware version that is loaded in 2NNetStar. It is very important information for you because “Administration tool” which is used for next configuration needs to have the same version as firmware version uploaded in 2N NetStar.  Configuration menu – number "1" in Main Menu If you press number 1 in Main Menu you will go to Configuration menu. In this menu you can set network parameters, bridges and time. In bridges section you can open some ports (e.g. for CTI communication) and in time section you can set the actual time and date.  The most important part of this menu is Network settings. In this section you can set IP address of CPU, network mask and default gateway. You can also choose whether you want to use DHCP or if you set static IP. Default IP address is 192.168.100.100 (see next picture). Next parameters that can be set are DNS servers, host name of 2N NetStar and domain name.    System menu – number "2" in Main Menu If you press number 2 in Main Menu, you will go to System menu. In this menu you can turn the internal web server, telnet server and SSH server on or off. You can also restore factory settings here or reboot the 2N NetStar.     Connection to the NetStar – Administrator tool First of all you have to verify firmware version which is uploaded on NetStar. You can do it easily if you use Putty program for connection to 2N NetStar and on the top left corner you will see the actual firmware version – it is visible in the first picture where there is the actual firmware marked with a red frame. After this you have to install Administrator tool to your PC – you can find this tool on the www.2n.com.  Administration tool – connection parameters When you have successfully installed the tool, you can launch it – you will have an icon on the desktop of your PC if you checked off this option during the installation or you will find it in the folder that you have selected for installation. Now you have to set new connection in Admin tool:  Create new group – see the step 1 in the picture below. Click on the “Create group” icon and select “On the same level”. I have named this group 3.1.10.  Add new PBX to this group – step 2 in the figure below. Click on the “Create PBX” icon and select “To group”. Then enter the name of PBX (in the example is Test_PBX) and click the OK button (step 3).  Fill in the connection parameters – you have to fill in connection name, choose one of the modes option (on-line = only on-line connection to the 2N NetStar, off-line = only off-line configuration of database or both). Next you have to set a method how you want to connect to NetStar:  TCP/IP – you have to set IP address of CPU and IP port  Modem - you have to set phone number  COM port  It is also possible to set timeout between attempts if the connection was unsuccessful or you can preset username and password for this connection.   After this setting you will see your Test_PBX in group 3.1.10 and two connections for this PBX. Make a double click on the “Local – on-line” connection and you will be connected to the 2NNetStar. Hardware installation wizard begins automatically.   Administration tool – hardware installation wizard Now you will be briefly acquainted with the installation wizard and with the most relevant quick start settings. First of all 2N NetStar needs to make hardware detection. In this case you have to set BRI configuration – if there are some BRI cards in the NetStar, ports will be selected by default.  TE = terminal equipment (receives sync from the opposite side)  NT = network termination (gives sync to the opposite side)  PTP = point to point communication  MPT = point to multipoint communication   When you select one of these options, you should click on “Next” button and automatic hardware configuration will be finished (see the picture below).  After finishing the hardware detection, you should press “Next” button and next installation wizard will start. This wizard will guide you through configuration of basic parameters of 2N NetStar for the first start-up. There are 8 sections you will go through and you can see them on the figures below (images are arranged in the same order as in the wizard):  Localization – set the destination where the 2N NetStarwill be deployed. In Advanced settings you can fill in numbers and prefixes that will be used for localization of calling numbers (figure below - part 1)  Time settings – set the actual date and time. You can do it manually or you can synchronize time of NetStar with network time server (NTP server) or you can get time from your computer (figure below - part 2)  Working scheme – select the working scheme in which you want to use 2N NetStar. There are four options:  PBX - classic PBX with SIP, ASL, cornet extensions, mobility extensions, etc.  Virtual PBC - 2N NetStar is e.g. structured for more companies in one building (each company has its own numbering plan, routing, special services, etc.)  GSM gateway - 2N NetStar is set as a basic gateway to GSM network  Hotel    Extensions definition – choose one of the options for extension settings. You can choose automatic extension settings (create a group to which all created extensions will be added and then set the numbers for ASL, SIP and cornet extensions. If you create some SIP extensions then default SIP proxy will be also automatically created). You can also import numbering plan from your PC or you can skip this option and set the extension later in the Administration tool (figure below - part 4)  Assistant settings – if you plan to use Assistant server (web server for users), you can start this server right now from wizard and you can also generate default logins for users – these users were created in the previous step (figure below - part 5)    SIP domain - set the domain name for SIP communication (figure below - part 6). This option is available only if you set some SIP extensions in previous step.  SMTP settings – create the SMTP account for email sending. You can specify server address and also email address for this account (next figure - part 7)   Router settings – choose one of four options for router settings. Each option has different number of routers and also different type of routers. You can also add some more routers to each of these groups (next figure - part 8):  ROUTER_CZ: there are 32 routers which can be configured in order to meet your requirements. You can specify routers for emergency calls, for local calls, for calls to national networks and GSM networks, etc. If you choose this router type, you can specify prefixes for AUTHORIZE_LO and AUTHORIZE_LO+GSM router (figure below - part 9).  ROUTERS_DEFAULT: there are only 6 routers for this option. You can find there Default, Authorize, Internal, PSTN, Services and SMS Services routers.  ROUTERS_BASIC: there are 14 routers in this section. You can find there same routers as was in routers_default plus there are routers for ME, PSTN, SMS in and out, etc.  ROUTERS_SK: there are the same routers as in router_CZ group but there are some more prefixes predefined.        On-line and Off-line database On-line database – it is an actual database saved in 2N NetStar. If you want to make changes in this database, you need to have on-line connection to NetStar (via TCP/IP, COM port or modem). Changes are saved to NetStar after you click on the “Save changes” button on the top menu. Off-line database – this database is saved on your computer and you can find it here:C:\Documents and Settings\Administrator\App Data\2N TELEKOMUNIKACE\Netstar\Tools\PbxX. You can verify the destination folder in properties of PBX (see figure 5 – PBX parameters window). When you connect to the 2N NetStar in off-line mode, the database from this folder will be uploaded – the name of this file is Db.xml. You can make changes in this off-line database without any impact to the 2NNetStar configuration. From off-line database mode you can connect to the NetStar by click on the “Connect” button on the top menu. Then you can select one of three options you have (see the figure below):  Load from PBX – you will load configuration from NetStar to off-line mode (configuration from NetStar will be saved to file Db.xml in you PC).  Save to PBX – you will save your off-line configuration to the NetStar (this configuration will be saved there and will be active!)  Move changes – you will only move changes that have been made in off-line mode to NetStar on-line configuration (you need not save all configuration to NetStar but only the difference between off-line and on-line configuration).

Question 23

2N NetStar SW - How to install and license 2N NetStar SW

Accepted Answer

This FAQ describes how to install 2N® NetStar SW. The 2N® NetStar SW is a virtual PBX that works the same as 2N® NetStar and offers the same 2N® Netstar Admin Tool as the hardware version. It has similar functionalities. With 2N® NetStar SW you can connect Softphones, IP phones or other solution working with SIP protocol.  Mandatory Software and Used ports   For use of 2N® NetStar SW and it's configuration software 2N® SW NetStar Admin Tool you need to have installed and enabled following software  Microsoft Visual C++ 2013 Redistributable (x86)  Microsoft Visual C++ 2015-2019 Redistributable (x86)  .NET Framework 3.5  .NET Framework 4.7        System capacity dependence on used HW    Installation of 2N NetStar SW  It is necessary to install setup+sw_version.exe, that you can download here     Installation of 2N NetStar SW in VirtualBox In VirtualBox it is necessary to add a new virtual PC where will be 2N® NetStar SW installed.The whole process is not shown in pictures below, only mandatory ones as the virtual machine configuration may vary for everyone.    Go to Storage -> Add optical drive  Add the .iso file which is in the installation folder of SW NetStar Admin ToolC:\Program Files (x86)\2N TELEKOMUNIKACE\2N NetStar SW\2N NetStar SW Admin Tool version Software\ISO -> netstar-pbx_version.iso  The .iso file is succesfully added to the virtual machine  Change the Network Adapter so you can connect to your SW NetStarUsually we use setting shown in the picture below, it may vary depending on your network setup.         For the installation use classical option not the graphical one.Choose the localization for you country.  It is necessary to specify IP address, mask and default gateway and name server for 2N NetStar SW. After that press Continue to install 2N NetStar SW.In our example we have used following IP addresses, they may differ depending on your network.  IP Address which will be assigned to the SW NetStar - later used for connection via SW NetStar Admin Tool  Network mask  Network gateway  DNS IP address    With Ping function you can check that 2N NetStar SW is available and working. Default login to NetStar virtual machine is followinglogin: rootpassword: 2n    2N Netstar SW Admin Tool  Rights   If you are setting up NetStar in a restricted environment and possibly on a PC without admin rights. Please check whether you will have an acces to following folders after installation.   C:\Users\username\Documents\2N TELEKOMUNIKACE\Netstar\C:\ProgramData\2N TELEKOMUNIKACE\Netstar\ C:\Program Files (x86)\2N TELEKOMUNIKACE\2N NetStar SW\2N NetStar SW Admin Tool 1.3.1\NsSwAdmin\Xml - Installation folder(it may varry depending on what path you have chosen during installation process)      The 2N NetStar SW Admin Tool has the same interface as the hardware version. To configure 2N® Netstar SW Admin Tool it is necessary to create PBX, configure IP address and connect to the PBX.  Click on Groups -> On the same level -> Name your group  Right click on the Group -> Create PBX -> To groupName the group - hit OK  Name the connectionFill the IP address of SW Netstar virtual machine - we used 192.168.1.78Optionally you can fill the login credentials which in default arelogin: adminpassword: 2n          Licensing  Trial license   Unlike on Hardware version of NetStar the Software one does not have a 800h trial license.   To be able to use and work with a SW Netstar you need to add a license. The license key is based on license ID serial number. You need to order a license based on this ID number as there is not any trial time period. You can program it without a license but the license is mandatory for functionality Connect to 2N Netstar SW Admin tool in online mode! The ID serial number can be found in the section Global Data -> Licenses -> Serial number

Question 24

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 25

2N OfficeRoute & Alcatel OXO connected via SIP trunk

Accepted Answer

2N OfficeRoute has these parameters:  IP address 192.168.92.200  Listening port: 5060/5065  firmware version 2.3.11  Alcatel OXO parameters:  IP address 192.168.92.246  Incoming port: 5060  version 7.7.1   Settings of 2N OfficeRoute  Settings of SIP trunk for Listening port 5060  a. Switching SIP proxy off  Default settings for SIP destination port in Alcatel OXO is 5060. 2N®OfficeRoute has port 5060 used by internal SIP proxy. That is why the SIP proxy has to be switched off for this case.  b. Creating a new SIP trunk At menu Telephony services → Devices → SIP lines add a new line. For a new SIP line:   Fill in SIP server address as IP address of Alcatel OXO, listen port 5060.   Highlight or change a priority of codecs which should be used for this trunk.  Uncheck Register with proxy checkbox  Write some description of this trunk.     2. Settings of SIP trunk for Listening port 5065 In this case it is not necessary to switch SIP proxy off.   Creating a new SIP trunk At menu Telephony services → Devices → SIP lines add a new line.     For a new SIP line - the recommendation as above.      3. Configuration of the LCR (Least Cost Routing) At Telephony services → LCR disable all rules which are not routed into GSM.   Remove all rules from Telephony services – LCR – Normalization.    4. Incoming calls Incoming calls can be routed to some DDI in OXO. For our case it is number 100 which will be dialed into our SIP trunk for all incoming calls. Create a new Operator rule in Telephony services → GSM routing → Operator. Operator number is a number which will be dialed into chosen VoIP line for incoming call.   Assign the Operator service with GSM modules which should use this incoming rule. You can do it at Telephony services → GSM routing → GSM. Create here a new rule for each GSM module and choose the service  Remove all normalization rules in GSM routing menu.     Alcatel OXO configuration  Setup a count of VoIP-Trunk channels for VoIP trunk to OfficeRoute.   2. Choose Trunk group and check Public trunk checkbox. Change Link Category settings.  3. At Link Category menu setup all necessary parameters.  4. Assign Trunk Groups.  5. Setup Numbering plans table. As Base settings choose ARS.  6. Check Public numbering plan for incoming calls. 7. At Trunk Groups List assign List ID with Index at menu Numbering → Automatic Routing Selection → Trunk Groups List.  8. Setup IP address of 2N OfficeRoute, codecs, bandwidth and GW keep-alive timeout for VoIP trunk at menu Numbering → Automatic Routing Selection → Automatic Routing: Prefixes.  9. At menu Numbering → Automatic Routing Selection → Gateway Parameters setup listening port 5060. If you want to use 2N OfficeRoute with different listening port (for example 5065), just setup the number of the port here.

Question 26

2N Records Manager installation

Accepted Answer

Requirements: NetStar firmware version 4.2.0 or higher    1. Create User in your NetStar (in section User- Users & Groups):  This user account of Records Manager will communicate with NetStarIn this case, we created user "connect"  Next, create a login and password to this user Section Users – User rights  2. Install the 2N Records Manager. HW requirements are 64bit processor, 2GB RAM, 100GB HDD, processor must support Virtualization technology. It can be Virtual machine, Server or PC in the same LAN Network as 2N NetStar is! Software is distributed with CentOs 6.4 system – which will be installed as well. If you are going to install Records Manager on the virtual PC you need to enable virtualization (used as the hardware acceleration) on the BIOS. Below all the step of installation are described.      3. Select the first option or just wait. 4. Then the system will request to select one of the options below (we recommend option "Use All Space")      5. Installation will take approximately 15 minutes. After the installation is complete you will be requested to reboot the system.      6. Eject installation disk from CD-ROM. Enter login and password. By default login is admin, password is 2n.   7. Select language and proceed with settings.    8. Type hostname. It can be any name    9. Select network interface      10. You can use IP address obtained from DHCP server or configure static    11. To access Records Manager you can use domain name or IP address. If you select domain name as the option, it is also necessary to update your local DNS server with new entry. Domain name must look like records.company.com    12. The wizard will create a storage folder where all the records will be saved. Wizard will request a password to access given directory from Netstar. After you enter the password you will be requested to enter name of folder where all the records will be stored:          13. After you finish system setup there will appear a window with the following options:    14. Now system is set. Run any web browser and type IP address/domain name of installed Records Manager. Default login is superadmin, password is 2n      15. Upload the license file which you got from Technical Support    16. Then add new NetStar to the system and fill in required information and add created folder for storing records   IMPORTANT!  The communication port is always 6543, Sys. user is the user which was created in NetStar in the beginning of this manual.   17. Now all the users of NetStar are visible in Records Manager. There are 3 roles available for given users  Admin - can manage all the users and managers. He is not able to configure NetStar in Records Manager.  Manager - can see all the records of his users. For example, it can be manager of department who has certain amount of employees.  Agent - employee. He can see and manage his own records.      All the users are able to access Records Manager via web browser using their credentials which can be set in NetStar      18. Configuration of Records Manager is completed. Now configure Storage Manager in NetStar. Create new LAN physical storage and fill in IP address of Records Manager, user name/password (it was set in point 13 of given manual, login is always admin) and storing folder

Question 27

2N SIM Star blocks FW upgrade on gateways

Accepted Answer

If you have some gateways connected to 2N SIM Star Server and you want to make firmware upgrade of any of these gateways directly from PRI config program (BlueTower, StarGate) or via web interface (VoiceBlue Next, new CPU for StarGate and BlueTower), it could happen that you will not be able to do that. You will select the newest FW, upload it to the gateway and see the message, that firmware has been successfully upgraded.  Firmware upgrade via PRI config tool    Firmware upgrade via web interface    Then the gateway will be restarted automatically in order to load new firmware, but after that there will be still the old FW version in the gateway. The reason may be simple – it is because of 2N SIM Star where is uploaded one FW version common for all specific gateways connected to it. Once you will change this firmware file in 2N SIM Star, all gateways connected to it will be upgraded (downgraded) automatically. You can verify the required FW version for a gateway in 2N SIM Star.   Solution for manual upgrade If you want to make FW upgrade manually, you have two options:  Remove uploaded firmware file from 2N SIM Star - this can be done in section "SIM Server –> GW & SB/SC firmware" and then click on the "Remove" button next to the specific firmware file. Once you remove this file, you will be able to make FW upgrade manually on the gateway.   Disconnect your gateway from 2N SIM Star and make an upgrade as shown in the first picture (via PRI config tool or via web interface - it depends on the gateway). But do not connect this gateway back to SIM Star - if you do that, then FW will be upgraded / downgraded to required FW version.

Question 28

2N SIM Star shows a low ACD value

Accepted Answer

2N SIM Star shows a low ACD value   Make sure that the SIM card credit and validity check is set correctly – lower ACD may result in the fact that an incoming call is forwarded to the IVR services informing of a low credit, etc.

Question 29

2N SIM Star shows a low ASR value

Accepted Answer

Make sure that your SIP Proxy does not send a count of GSM calls higher than the GSM gateway capacity.  If the frequent SIM card change is set, reduce the maximum count of calls via the GSM gateway – the GSM modules are temporarily unavailable for standard calls while being in the process of recharging (especially the IVR type), virtual incoming calling or SIM replacement.

Question 30

2N SmartCom/2N SmartCom PRO - Basic configuration

Accepted Answer

In the very first step you should read the manual which you can find on 2N Telecommunication website http://www.2n.cz/en/products/m2m/smartcom/downloads/  You can also find there: a leaflet, a presentation, software, firmware. In the section software please find and install 2NSmartCOM (further just SmC) configuration program.  Very important is to use the cable which is attached in the box (version 410100W a 410101W). RS232 9 female/RS232 9 female has to be crossed!!!    Connector 1 Connector 2 Function2 3 Rx ← Tx3 2 Tx → Rx4 6 DTR  →  DSR5 5 Signal ground6 4 DSR  ←  DTR7 8 RTS  →  CTS8 7 CTS  ←  RTS  When you connect SmC to your PC, you can then find out which COM port does your SmC use.  Run 2N SmC configuration program. In communication settings you should choose the appropriate COM port, where is your SmC placed.Then set following features:Speed[bd/s] 115200Data bits 8Stop bits 1Parity noneFlow control noneSerial port password is not set by default!!! This password is useful to protect your Smc against access and configuration by not allowed persons. If you want to use it follow FAQ "How to set password against unauthorized configuration 2N SmartCom".Confirm "OK".   Load configuration - It will read basic information about SmC and SIM card which is inserted in. (Local IP address, Signal level, Operator, Serial number, Firmware version, SIM number, GSM module specification).Continue configuration:  Mode: TCP client (with 2N SmartCom server)/Standalone (without 2N SmartCom server).GPRS APN: Set APN (access point network) assigned by an operator.Server IP address: Set IP address SmC server, where you want to register SmC.Server port: Set listening port of SmC server.PIN: Set PIN SIM card.Password: To register to SmC server.  7. Save new configuration by the button "Save and restart".

Question 31

2N SmartCom PRO / Factory reset - How to make a factory reset

Accepted Answer

Factory reset - jumpers:  disconnect 2N SmartCom PRO from the power supply  loosen the screws and remove the upper part of the case    connect the jumper as shown in the figure above (Interconnect pins 3 and 5)  now reconnect the power supply. Upon power up, the Flash memory is deleted and the factory default values are reset for all ports    remember to remove the jumper to avoid deletion of the settings upon every start!        Factory reset - AT command:     at^scfres    following command make the software factory reset. The command only sets the default parameters without deleting the Flash and EEPROM data memories.          Factory reset - SMS:     SC FRES PWD=  send SMS to initiate the terminal factory reset.  you will get a response SMS - "Factory Reset Initialized" and the command will be executed

Question 32

2N SmartCom PRO - Input circuits

Accepted Answer

2N SmartCom PRO is equipped with three inputs, which are mutually galvanically connected with the GND reference point (have a common GROUND). The input circuits can work in three modes – voltage, current or logical levels – as configured.  disconnect 2N SmartCom PRO from the power supply before opening the cover  loosen the screws and open the box lid to get access to the PCB jumpers.  The figures below show the location of the current/voltage/S0 switching jumpers:    Note: If you want to use voltage mode and current mode properly, you need to calibrate 10-bits A/D converter connected to the input terminals (IN1, IN2, IN3). But keep in mind that an uncalibrated input is still functional (but can read values less precisely).    Voltage Measurement Voltage can be measured in the range between 0 and 10 V DC. Make sure that the 2N SmartCom PRO jumpers are set as shown in the figure above before using this mode.   Current Measurement Electric current can be measured in the range between 4 and 20 mA. Make sure that the 2N SmartCom PRO jumpers are set as shown in the figure above before using this mode   An example is given for the ADC circuit 1 (scadc1). To read circuit 2(3), replace 1 with 2(3) in the command (scadc2/scdc3). at^scadc1="get_value"  The command performs measurement on the selected interface and sends the calibrated value measured.  at^scadc1="adc_value"  The command performs measurement and returns the value from the A/D converter.  at^scadc1="calib_min"  Automatic interface calibration according to the currently measured value.  at^scadc1="calib_max"  Automatic interface calibration according to the currently measured value.  at^scadc1="threshold_low",1200  Manual calibration setting (minimum values). Setting options: 0–4090.  at^scadc1="threshold_high",3250  Manual calibration setting (maximum values). Setting options: 0–4090.  at^scadc1="save"  The command saves the changes.    Logical Level Monitoring You can monitor the logical levels of voltage and current signals. Use other commands than those intended for classic measurements and define the threshold levels. Again, use the AT commands for reading values on input circuits. at^scdin1="get_value"  The command detects the logical level on the selected interface and sends the value 1/0  at^scdin1="calib_min"  Automatic interface calibration according to the currently measured value  at^scdin1="calib_max"  Automatic interface calibration according to the currently measured value  at^scdin1="threshold_low",1400  Manual calibration setting (minimum values). Setting options: 0–4090  at^scdin1="threshold_high",3450  Manual calibration setting (maximum values). Setting options: 0–4090  at^scdin1="save"  The command saves the changes.

Question 33

2N SmartCom PRO M-Bus overview

Accepted Answer

2N SmartCom PRO can be equipped with M-Bus interface and can collect data from up to 5 M-Bus devices (with extender it can be up to 250 M-Bus devices). This website describe possible scenarios and some examples how to collect and use M-Bus messages with 2N SmartCom PRO. 2N SmartCom PRO can be configured via hyperterminal software or 2N SmartCom Terminal Config software. The SmartCom terminal can be set to a Standalone mode unit or TCP Client mode unit connected to 2N SmartCom Server.In TCP client mode terminals are connected to the server and you can very easily manage them via 2N SmartCom Control Panel software.  End device (water meter, electricity meter, heat meter etc…) To be able connect the end device to 2N SmartCom PRO terminal you need to know at least M-Bus setting of the end device (can be in meter´s manual):  Primary address  Speed [bd/s]  Data bits  Stop bits  Parity    2N SmartCom PRO M-Bus settings You need to set all M-Bus parameters in 2N SmartCom PRO. You can do the settings using SmartCom Terminal Config Software or via at commands using serial / telnet terminal software. Settings M-Bus: speed 2400bd/s - data bits 8 – stop bits 1 – parity – none at^scport2="baudrate",2400 Set Baudrate at^scport2="DATA_BITS",8 Set data bits at^scport2="STOP_BITS",1 Set stop bits at^scport2="PARITY",0 Set parity at^scport2? Check settings at^scport2="save" Save settings         M-Bus data readout from 2NSmartCom PRO Data can be read using 2N  SmartCom PRO in two modes either Transparent mode or using Autonomous Metering System functionality:  Transparent mode:  2N® SmartCom PRO is used as communication data channel and data are not stored in 2N® SmartCom PRO internal memory. Application / script, reading M-Bus data from meter is running on remote server site and reading data using 2N® SmartCom PRO communication interface. Data are stored on server site in the application or file. There are no data available in case the 2N® SmartCom PRO is not available over IP network  Autonomous Metering System (AMS)  With AMS functionality 2N SmartCom PRO can read and store M-Bus data from meter autonomously in predefined interval. Read data are stored to internal memory of 2N SmartCom PRO. Data are stored in original M-Bus format. Data are presented in the 2n® SmartCom PRO internal memory even when the WAN connection is not available. So you can easily read them out from the memory when connected to the terminal (no matter whether it is local RS232 or telnet connection). It can prevent missing data in case the IP network is not available.   M-Bus messages and parsing  Original M-Bus format: You can work with M-Bus messages in original format defined by M-Bus standard. All types of M-Bus messages are described for example on website http://www.m-bus.com/, messages are in HEX format. You can request the data from meter by sending commands to M-Bus meter directly through the SmartCom PRO terminal for example from hyperterminal or some software which support HEX strings. In Standalone mode you need to use telnet for SmartCom PRO terminal communication (IP address of 2N ® SmartCom PRO and port 10002).In TCP Client mode you can create and use virtual port (serial or TCP port), that virtual port can be mapped to 2N ® SmartCom PRO M-Bus interface.    Autonomous Metering System (AMS)  2N SmartCOM PRO can be set to reads data from M-Bus end device autonomously and store data in internal memory. Format of stored M-Bus message in internal memory: ^SCDATA:,,,,,,,  - typ of record - AMS  - time mark  - sequential number of saved record  - name of protocol  - index of device from table of devices  - number 0 = without error  - not used in M-Bus  - raw data Raw data: at^scdata="get_oldest",3 ^SCDATA: "AMS",1427985840,25036,"MBUS",1,0,"","685E5E6808007268170308653299068E0000000C13911800000B22730404046D3510E2 14326C00000C786817030806FD0C0A000100FA010DFD0B05313248465701FD0E004C1374180000426CDF1C0F37FD170000000000000000027A2500027825004116"    Script that runs on you Server / PC:  You can create your own script for parsing M-Bus messages. Examples of testing scripts are available on request from 2N support. Those scripts are based on linux library libmbus (http://www.rscada.se/libmbus/). Data are processed and saved to TXT, CSV, and similar files format. Examples:  Data from water meter Siemens parsed by libmbus library      8031768 LSE 153 Siemens WFH21 Hot water 13 00 0000     Instantaneous value Volume (m m^3) 1913 2015-06-22T13:49:42     Instantaneous value On time (hours) 42417 2015-06-22T13:49:42    ....  Instantaneous value Time Point (date) 2014-12-31 2015-06-22T13:49:42     Manufacturer specific 37 FD 17 00 00 00 00 00 00 00 00 02 7A 25 00 02 78 25 00 2015-06-22T13:49:42        Processed data from electricity meter stored in CSV file:    Processed M-Bus data from meters can be imported to traffic grapher or other tool you are used to use. Traffic grapher is not included in 2N® SmartCOM PRO or 2N® SmartCOM Server. You can use you preferred tool.     M-Bus monitoring software  You can use M-Bus monitoring software which will analyze and display data from 2N® SmartCom PRO. Example: You can create your account in Energy monitoring cloud service Smart – me (http://smart-me.com). How this example works:  Via 2N® SmartCom PRO read M-Bus data.  2N® SmartCom Server processed data using additional script which sends the final data format requested from Smart-me to your account at Cloud service Smart – me  You can display results online

Question 34

2N SmartCom PRO  - Terminal error buffer code description

Accepted Answer

An error buffer is implemented in each terminal to store data on terminal operation errors. To display the buffer contents use either the terminal (an AT command) or an SMS.  SMS: The SMS displays the last 10 errors starting with the most recent one. SC ERR PWD= [CLR] This command includes one optional parameter – CLR. If you add this string after the password in the command SMS, you will receive an SMS showing the current buffer contents and all errors will then be deleted from the terminal memory. The following reply will come from the terminal after processing:1:8,10 2:3,10 1:1,0 7:8,10 6:8,7 5:7,40 4:11,848   AT COMMAND: Error codes are obtained by AT^SCERR? which response is: ^SCERR: {id}> {ID}, {Additional value}id - Sequence number of the error since the last start-up.ID - Error identification. See table below.Additional value - Detailed information   This table describes the meaning of the 2N® SmartCOM PRO reset error codes.   ID  Name  Additional value  Description  0  ERR_TYPE_NO_ERROR     No error  1  ERR_TYPE_SIM_PRESENCE     SIM not detected  2  ERR_TYPE_SIM_FEW_PIN_ATTEMPTS  pin attempts left  Too few attempts left  3  ERR_TYPE_SIM_PIN_ERROR  CME error  Incorrect PIN  4  ERR_TYPE_SIM_BUSY     SIM is busy  5  ERR_TYPE_GSM_REGISTRATION_LOST     GSM unregistred  6  ERR_TYPE_GSM_REGISTRATION_TIMEOUT     Could not register to the network  7  ERR_TYPE_COMMAND_RETRIES  Command channel state  GSM module does not respond on the command channel  8  ERR_TYPE_DATA_RETRIES  Data channel state  GSM module does not respond on the data channel  9  ERR_TYPE_MUX_WAIT_OPEN     Timeout for openning the MUX channel  10  ERR_TYPE_PSPRAS_INVALID_ARG_CNT     Unexpected count of parameters (PIN attempts read)  11  ERR_TYPE_CME_COMMAND  CME error  CME error on command channel  12  ERR_TYPE_CMS_COMMAND  CMS error  CMS error on command channel  13  ERR_TYPE_CME_DATA  CME error  CME error on data channel  14  ERR_TYPE_CMS_DATA  CMS error  CMS error on data channel  15  ERR_TYPE_CME_UPGRADE  CME error  CME error on command channel while upgrading  16  ERR_TYPE_CMS_UPGRADE  CMS error  CMS error on command channel while upgrading  17  ERR_TYPE_CME_UPGRADE_DATA  CME error  CME error on data channel while upgrading  18  ERR_TYPE_CMS_UPGRADE_DATA  CMS error  CMS error on data channel while upgrading   19  ERR_TYPE_SC_CLIENT_UNABLE_TO_CONNECT     Could not connect to the remote server  20  ERR_TYPE_SC_UPG_ERROR  UPG error code  Upgrade failed  21  ERR_TYPE_SC_UPG_BLOCK_ERROR     Did not get all requested data  22  ERR_TYPE_SC_MEMORY_ALLOCATION_ERROR     Memory allocation failed  23  ERR_TYPE_SC_SPECIFICATION_ERROR     Cannot find the SC specification (serial num etc.)  24  ERR_TYPE_PROTOCOL_RETRIES     Server not responding  25  ERR_TYPE_SC_UPG_MAXIMUM_RETRY_CNT     Upgrade failed three times  26  ERR_TYPE_MBUS_SHORT_CIRCUIT     MBUS short circuit  27  ERR_TYPE_GSM_COMMAND  Command channel State  General error on command channel  28  ERR_TYPE_GSM_COMMAND_UPGRADE Command channel State General error on command channel while upgrading  29  ERR_TYPE_GSM_DATA Data channel state General error on data channel  30  ERR_TYPE_GSM_DATA_UPGRADE Data channel state General error on data channel while upgrading       Command channel states GSM module set-up state set.   ID  Name  0  COMMAND_SUB_STATE_AT  1  COMMAND_SUB_STATE_FACTORY_RESET  2  COMMAND_SUB_STATE_MUX_STARTUP  3  COMMAND_SUB_STATE_MUX_STARTUP  4  COMMAND_SUB_STATE_ECHO_OFF  5  COMMAND_SUB_STATE_MODUL_MANUFACTURER  6  COMMAND_SUB_STATE_MODUL_TYPE  7  COMMAND_SUB_STATE_MODUL_FW_VERSION  8  COMMAND_SUB_STATE_GET_IMEI  9  COMMAND_SUB_STATE_READ_OPERATOR_NAME  10  COMMAND_SUB_STATE_ERROR_REPORT  11  COMMAND_SUB_STATE_EVENT_REPORT  12  COMMAND_SUB_STATE_MESSAGE_FORMAT  13  COMMAND_SUB_STATE_SIM_PIN  14  COMMAND_SUB_STATE_SIM_PIN_ATTEMPT_STATUS  15  COMMAND_SUB_STATE_INSERT_SIM_PIN  16  COMMAND_SUB_STATE_GET_IMSI  17  COMMAND_SUB_STATE_GET_ICCID  18  COMMAND_SUB_STATE_DELETE_ALL_STORED_MESSAGES  19  COMMAND_SUB_STATE_SIGNAL_QUALITY  20  COMMAND_SUB_STATE_FIELD_STRENGTH  21  COMMAND_SUB_STATE_ASK_NETWORK_REGISTRATION  22  COMMAND_SUB_STATE_NETWORK_REGISTRATION_INDICATION  23  COMMAND_SUB_STATE_CHARACTER_SET  24  COMMAND_SUB_STATE_LIST_ALL_UNREAD_MESSAGES  25  COMMAND_SUB_STATE_SHOW_TEXT_MODE_PARAMS  26  COMMAND_SUB_STATE_NEW_MESSAGE_INDICATION  27  COMMAND_SUB_STATE_CLOSE_CONNECTION  28  COMMAND_SUB_STATE_OTHER  29  COMMAND_SUB_STATE_START_UP_LED_SEQUENCE  30  COMMAND_SUB_STATE_IDLE_AT  31  COMMAND_SUB_STATE_INIT_COMPLETE  32  COMMAND_SUB_STATE_SEND_RESPONSE_MESSAGE_CMD  33  COMMAND_SUB_STATE_SEND_RESPONSE_MESSAGE_TEXT  34  COMMAND_SUB_STATE_START_IP_STACK  35  COMMAND_SUB_STATE_NET_OPT_AUTO_SWITCH_ON  36  COMMAND_SUB_STATE_OPEN_GPRS_BEARER  37  COMMAND_SUB_STATE_SET_APN  38  COMMAND_SUB_STATE_SET_USER_NAME  39  COMMAND_SUB_STATE_SET_PASSWORD  40  COMMAND_SUB_STATE_START_GPRS_BEARER  41  COMMAND_SUB_STATE_GET_LOCAL_ADDRESS  42  COMMAND_SUB_STATE_GET_PEER_ADDRESS  43  COMMAND_SUB_STATE_CREATE_TCP_SERVER  44  COMMAND_SUB_STATE_CLOSE_CLIENT  45  COMMAND_SUB_STATE_WISMO_DIRECT_ACCESS  46  COMMAND_SUB_STATE_RESTART_CLOSE_ALL_CONNECTIONS  47  COMMAND_SUB_STATE_READ_OPERATOR_ID_START  48  COMMAND_SUB_STATE_READ_OPERATOR_ID  49  COMMAND_SUB_STATE_READ_OPERATOR_NAME_START  50  COMMAND_SUB_STATE_GSM_BANDS_GET  51  COMMAND_SUB_STATE_GSM_BANDS_SET  52  COMMAND_SUB_STATE_RTC  53  COMMAND_SUB_STATE_RTC_SAVE     Data channel states Data communication state set.   ID  Name  0  DATA_SUB_STATE_OTHER  1  DATA_SUB_STATE_START_DATA_EXCHANGE  2  DATA_SUB_STATE_WAIT_FOR_CONNECT  3  DATA_SUB_STATE_ECHO_OFF  4  DATA_SUB_STATE_SET_URC_TYPES  5  DATA_SUB_STATE_CLOSE_START  6  DATA_SUB_STATE_PRE_PPP_WAIT  7  DATA_SUB_STATE_SEND_PPP  8  DATA_SUB_STATE_CLOSE_AT  9  DATA_SUB_STATE_DATA_CHANNEL_CLOSED  10  DATA_SUB_STATE_CREATE_TCP_CLIENT  11  DATA_SUB_STATE_WAIT_FOR_CONNECTION_TO_PEER  12  DATA_SUB_STATE_WAIT_FOR_CONNECTION_TO_PEER  13  DATA_SUB_STATE_TEST_SIGNAL_QUALITY  14  DATA_SUB_STATE_TEST_READ_OPERATOR_NAME  15  DATA_SUB_STATE_TEST_SIM_CHECK  16  DATA_SUB_STATE_TEST_ASK_NETWORK_REGISTRATION  17  DATA_SUB_STATE_TEST_GET_LOCAL_ADDRESS     UPG error codes Response codes for firmware upgrade call.   ID  Name  0  UPG_RESP_OK  1  UPG_RESP_FINISHED  2  UPG_RESP_HTTP_ERROR  3  UPG_RESP_TARGET_ERROR  4  UPG_RESP_PORT_ERROR  5  UPG_RESP_PATH_ERROR  6  UPG_RESP_TARGET_HEADER_ERROR  7  UPG_RESP_HW_VERSION_ERROR  8  UPG_RESP_TIMEOUT_ERROR  9  UPG_RESP_FW_MARK_ERROR  10  UPG_RESP_CRC_CHECK_ERROR  11  UPG_RESP_FW_LENGTH_ERROR  12  UPG_RESP_FW_VERSION_ERROR

Question 35

2N StarGate - Multiple outbound SMS web users

Accepted Answer

In this FAQ you will see how to configure multiple outbound SMS web users feature on 2N StarGate gateway. There are several important steps which have to be followed for proper settings of this feature.  Introduction and requirements Note: As a very first step please make sure that the license for Multiple outbound SMS web users feature is uploaded into your 2N StarGate gateway. This license is sold as a package for 10 users (you can buy licence for 10, 20, 30, etc. users) and you can have up to 200 licensed users in the gateway. If you want to verify whether you have the correct license uploaded in your gateway, go to section "Management -> License key". You should see the licenses called SMSW and SMSUx in the "Active" row. SMSW indicates that Multiple outbound SMS web users function is enabled and SMSUx indicates number of licensed users where x stands for this number (see the picture below). If there is not a license for Multiple outbound SMS web users (SMSW) then you will not see tab "Messaging" on the top bar!   How to set multiple outbound SMS web users From firmware version 1.25 you can create SMS users which then can access web interface of gateway and login in order to send messages. Please see necessary steps below:  own proper license - SMSW in gateway info needs to be present and you require to have at least one user (SMSUxx)      SMS Server enabled: Yes (checked box) - can be found in Messaging -> SMS Server      user(s) needs to be configured. Can be found in Messaging -> Users  user needs to have associated Access Type either Web - testing or Web     routing for outgoing SMS needs to be configured for user - can be found in Messaging -> User Group x (depends on what user group is used for previously created user - in our example it is group 1) -> Outgoing SMS routing.     Proper SMS group and user needs to be chosen in order to assign GSM modules which will be used for such SMS sending. In our example, we assign user we created to SMS Group 1 and then we assign SMS Group 1 to all GSM modules.    When above steps are done and saved in to gateway, user with defined username and password can login to gateway's web interface and send SMS.

Question 36

2N Starpoint IP Phones - How to synchronize phonebook with 2N NetStar

Accepted Answer

Please download actual fw from ftp.2n.cz (at least 6.42.9.2)  Set up in the phone the IP address of NetStar: (NetStar provides a fttp server for the phone)   Set up in NetStar a group, in which the SIP phone belongs :   FW: 2  .6.x     Programming tool: 2.6.x

Question 37

2N Student Monitoring System with 2N IP Intercoms

Accepted Answer

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

Question 38

2N VoiceBlue Lite with my PBX station - Can I use?

Accepted Answer

Yes, If your PBX is IP PBX or if consists SIP proxy functionality.  2N VoiceBlue Lite  matches SIP RFC3261 standard.

Question 39

2N VoiceBlue Next GSM gateway - How to configure it with 2N IP intercoms?

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. This guide describes basic steps to configure Peer to Peer communication between 2N IP intercoms and 2N VoiceBlue Next GSM/UMTS gateway to be able to make calls intercom  GSM network. All names and IP addresses are only for this example, please change this information according to your names and IP plan.  Wiring  Connect 2N IP intercom to an IP network, 2N VoiceBlue Next has to be connected to the same IP network.The values in our example:2N IP intercom - 192.168.50.1422N VoiceBlue Next - 192.168.50.66Mobile phone number - 734123456    2N IP intercom settings  You need to specify IP address and subnet mask for your 2N IP intercom.    Select a contact which is mapped for one touch call (e.g. for button #1 on your 2N IP intercom). You need to modify Phone number for this contact according to the desired phone number you would like to call through the GSM gateway (sip:mobile_number@IP_address_of_VBN). In the following picture there is 192.168.50.66 an IP address of 2N VoiceBlue Next and 734123456 is the mobile phone number, so you set: sip:734123456@192.168.50.66.    Set up SIP settings according to the next picture. IP addresses should match to the IP of 2N VoiceBlue Next.    Allow the intercom to automaticaly accept all Incoming calls.     Settings of 2N VoiceBlue Next gateway   You need to specify IP address and subnet mask for your 2N VoiceBlue Next in the menu Ethernet configuration.    In the VoIP parameters check option Send 200 OK on REGISTER request to allow "virtually" register 2N IP intercom to 2N VoiceBlue Next.    The gateway is set to process all outgoing call requests to the GSM network in default, but you also need to define the IP address of the 2N IP intercom in the SIP proxy (GSM->IP): setting in order to process the incoming calls from GSM to the intercom.    In the GSM incoming groups set mode Accept incoming calls + dialtone and DTMF dialing timeout[s]:to 0.     And also set the phone number of the intercom (111) in the List of called numbers. Now you can easily call your mobile phone by pressing the dial button on the intercom and also reach the intercom directly from the mobile phone by calling the SIM card in the gateway. Please note that 2N VoiceBlue Next gateway can handle voice calls only, there is no support for the video stream in this scenario even if your 2N IP intercom intercom is equipped with a camera.

Question 40

2N VoiceBlue Next GSM gateway - How to configure it with 2N IP intercoms?

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface. This guide describes basic steps to configure Peer to Peer communication between 2N IP intercoms and 2N VoiceBlue Next GSM/UMTS gateway to be able to make calls intercom  GSM network. All names and IP addresses are only for this example, please change this information according to your names and IP plan.  Wiring  Connect 2N IP intercom to an IP network, 2N VoiceBlue Next has to be connected to the same IP network.The values in our example:2N IP intercom - 192.168.50.1422N® VoiceBlue Next - 192.168.50.66Mobile phone number - 734123456    2N IP intercom settings  You need to specify IP address and subnet mask for your 2N IP intercom.    Select a contact which is mapped for one touch call (e.g. for button #1 on your 2N IP intercom). You need to modify Phone number for this contact according to the desired phone number you would like to call through the GSM gateway (sip:mobile_number@IP_address_of_VBN). In the following picture there is 192.168.50.66 an IP address of 2N® VoiceBlue Next and 734123456 is the mobile phone number, so you set: sip:734123456@192.168.50.66.    Set up SIP settings according to the next picture. IP addresses should match to the IP of 2N® VoiceBlue Next.    Allow the intercom to automaticaly accept all Incoming calls.     Settings of 2N® VoiceBlue Next gateway   You need to specify IP address and subnet mask for your 2N VoiceBlue Next in the menu Ethernet configuration.    In the VoIP parameters check option Send 200 OK on REGISTER request to allow "virtually" register 2N IP intercom to 2N® VoiceBlue Next.    The gateway is set to process all outgoing call requests to the GSM network in default, but you also need to define the IP address of the 2N IP intercom in the SIP proxy (GSM->IP): setting in order to process the incoming calls from GSM to the intercom.    In the GSM incoming groups set mode Accept incoming calls + dialtone and DTMF dialing timeout[s]:to 0.     And also set the phone number of the intercom (111) in the List of called numbers. Now you can easily call your mobile phone by pressing the dial button on the intercom and also reach the intercom directly from the mobile phone by calling the SIM card in the gateway. Please note that 2N® VoiceBlue Next gateway can handle voice calls only, there is no support for the video stream in this scenario even if your 2N IP intercom intercom is equipped with a camera.

Question 41

2N VoiceBlue Next - How to configure it with Auerswald PBX?

Accepted Answer

Following FAQ page describes how a 2N VoiceBlue Next can be connected to Auerswald PBX using SIP trunk.  Parameters of 2N VoiceBlue Next:  Example IP address 192.168.1.2  Incoming port: 5080  Firmware: 1.25.0.28.4   Auerswald equipment parameters:  COMpact VoIP 5010, COMpact VoIP 5020, COMmander Basic.2 and COMmander Basic  Example IP address: 192.168.1.3  version: 4.2F Build 000     How to set 2N VoiceBlue Next? After having logged on to the 2N VoiceBlue Next, navigate to “Gateway configuration” on the menu tree in the left column, then choose “VoIP parameters”. Set following parameters:  Use CLIP from INVITE field: to value "From"  Use DIAL from INVITE field: to value “To”  Send 200 OK on REGISTER request: to enabled  Replace CLIP from GSM with Caller ID: to enabled  Above is important because otherwise the Auerswald PBX won’t register to the 2N VoiceBlue Next or incoming GSM calls won’t be displayed correctly on the phones’ displays. Please see image below:  Next, please scroll down in “VoIP parameters” until and set “Codec priority” . Please make sure here that G711a(8) is chosen as priority 1, then G711u(0) followed by G729(18). Further down under “IP addresses” fill in connection details to your Auerwald PBX. Enter the IP address of the PBX in the following fields (lets assume IP address of Auerswald PBX is for example 192.168.1.3):  SIP proxy (IP->GSM)  SIP proxy (GSM->IP)  Note: You can also set the SIP port. Remember that Auerswald already uses port 5060 for internal calls so you need to choose different one, for example 5080 w To make sure that no other equipment can access the 2N® VoiceBlue Next check the box “no reply on other IP addresses’ requests:”. Leave the rest unmodified. Click on the save button (button right, the icon with the paper sheet and the pen).      How to set Auerswald PBX?  Login as administrator to your Auerswald PBX (regular username is “admin“).  Then please find the sub-menu “Voice over IP (VoIP)” in the menu “COMset” -> “External numbers”.  Click on “Provider”. In an empty field of the column named “Provider name” on the right half of the screen enter a name for your 2N GSM gateway, e.g. “2N”. Then click on the disk symbol on the left side to save that entry.  After this click on the “Configure” button in the right column. Your screen should look like this:    Once you clicked on “Configure” you will see following page:    Please fill out the fields “Domain”, “Outbound proxy”, “SIP port (1...65535)”, and “Codec settings” as illustrated in the screenshot above.  In the field “Domain” you enter the IP address of your 2N VoiceBlue Next GSM gateway. The factory settings are “192.168.1.2” but if you changed it in the configuration page of the 2N VoiceBlue Next, make sure to enter the correct IP address here accordingly. In the field “Outbound proxy” you choose “manually” and enter the same IP address as in the “Domain” field, it’s the IP address of the 2N VoiceBlue Next in your network. In the field “Port” you enter the SIP port number that you have entered / will enter in the configuration pages of the 2N VoiceBlue Next. Usually that is 5060, but please keep in mind that the Auerswald PBXs use this SIP port exclusively for their extension lines (the internal parties) and that there was no option in former firmware versions to change it. Therefore, in this example, we changed the SIP port to 5080. You can take whatever you like, but make sure to have the same port open on your 2N VoiceBlue Next and that it is different than the port used for the internal calls (PBX’s extensions). “Codec settings”: Make sure only to choose “G.711” as priority number 1 and to leave the other entries blank. Otherwise you will receive a SIP response 415 (Unsupported Media Type) when you make outgoing GSM calls from your PBX via your 2N VoiceBlue Next.  Go to the field “Format of called telephone number” and set it to “send as dialled”. “Format of own telephone number” should be set to “Only MSN or main number and DDI”.“Type of number presentation” should be set to “In the display text”. Choose “Anonymous” for “Method of number presentation suppression”.Check the box named “Trust transferred telephone number” and uncheck the one named “Internationalise unknown telephone numbers”.  After having set everything click on “Action Accept” to save your settings.   Click on “Accounts” on the menu tree on the left side. It’s right below “Provider”. You will see similar page to following picture:     Make sure that you choose “PTMP connection” (point to multi-point) for the provider “2N”, that means for your 2N VoiceBlue Next and give the account a name by entering this in the field “Account name”, e.g. “GSM Gateway”. Save this setting by clicking on the disc symbol in the left column.  Click on “Configure”. You will see a page similar to picture below:      Enter MSNs (multiple subscriber numbers) that will be used by the 2N VoiceBlue Next to assign calls to certain extensions lines in your PBX.You can enter whatever you like here. In this case we chose “1111” to “4444” for the 4 SIM card modules of the 2N VoiceBlue Next with 1111 being the number called by 2N VoiceBlue Next if there is an incoming GSM call on the first SIM module etc.  Give a name to the MSNs to identify them easily, e.g. “GSM GW (SIM 1)” to “GSM GW (SIM 4)”. Leave “Ringer rhythm” on “1 x long”.It is very important to set the fields above with country code and area code to make sure that outgoing calls are dialled correctly and incoming calls are displayed correctly.So enter your country code the way it is dialled in your country in the field “Country prefix” (in this case we have Germany’s country code “0049”) and in the field “Area code” enter your area code numberthe way you would usually dial it (in this example the number is “05306”, the area code of the city of Cremlingen in Germany).You will also need to enter a number to identify this VoIP line within your PBX. This is an internal number used to choose this VoIP line specifically and make external calls with it. Enter whatever you like here that fits the internal numbering scheme of your PBX.In our example the number is 1501.  The fields “User name” and “Password” are mandatory. You have to enter something here. It is not important what you enter as the 2N VoiceBlue Next will accept any user name and password and acknowledge it with a “200 OK” on registration.  Make sure you click on “Action -> Accept -> Execute” to save your entries!  Next you click on “Call distribution” in the menu tree on the left. It’s below “Accounts” and “Telephone numbers”Here you will find your MSNs that you entered before to identify the SIM modules 1 to 4 of 2N VoiceBlue Next (in our case that was 1111, 2222, 3333, and 4444). HHere you can assign extension numbers, internal numbers, team numbers etc. to these MSNs so that certain internal phones will ring once there is an incoming GSM call from 2N VoiceBlue Next.After having assigned your internal numbers to the MSNs make sure you click on “Action -> Accept –> Execute” to save your setting.      Choose “Routing” and then “VoIP and GSM Routing” from the menu tree in the left column.This is where you can set the PBX’s least cost routing functionality.Please enter the code numbers of the cell phone networks in your country (in this case we see the first three digits of the code numbers of the German cellular network operator, 015, 016, and 017) and choose the VoIP trunk line that we set up earlier named “GSM Gateway”.In case the 2N VoiceBlue Next should not be reachable due to any reason you can set fallback lines here, too. In this case ISDN lines have been chosen as fallbacks under the columns named “2nd dialling” and “3rd dialling”.      Finally make sure that the IP address of 2N VoiceBlue Next is listed in the white list of the PBX.Otherwise, if the registration fail, the PBX might add 2N VoiceBlue Next to the blacklist and then there will be no more connection to 2N VoiceBlue Next possible.      Please also make sure that the internal parties are allowed to access the VoIP trunk to the 2N VoiceBlue Next.You can set this feature up in the menu tree on the left: COMset -> Internal numbers -> Subscriber (scr) -> Properties -> Exchange line settings + subscriber selection in the list field at the top.

Question 42

2N VoiceBlue Next - How to set? (version 1.19 and lower)

Accepted Answer

2N VoiceBlue Next is designed to reduce the costs of outgoing calls to GSM networks. The main advantage is the ability to expand the IP PBX to include a GSM gateway and make use of a LCR which selects the best GSM operator depending on the called number.   How to connect 2N VoiceBlue Next  Connect the 2N VoiceBlue Next via Ethernet cable directly to the computer. Change the IP address setting in the configuration of your PC (e.g. 192.168.1.33 and Subnet Mask 255.255.255.0)  Open your web browser and enter the default IP address of GSM gateway 192.168.1.2 with the default credentials (Admin/2n). If web page does not appear, make a factory reset of gateway with RESET button on front panel. Press it for 10 seconds. After this time gateway restarts and you can reload the page.  In the gateway configuration and Ethernet configuration you are able to change the IP address.    How to set up connection to the opposite device (PBX)  For the setting of the trunk between the 2N VoiceBlue Next and your PBX you need to configure SIP proxy (GSM→IP) for GSM incoming calls. SIP proxy (IP→GSM) is designed for secure communication just with traffic from your PBX. You can specify the IP address and port which will accept SIP packets from.  In case you leave there 0.0.0.0 in SIP proxy(IP->GSM) gateway will be open for traffic from all IPs. !!! This can lead to misuse of the equipment by an unauthorized person !!!!    How to configure LCR table Situation...  Let's say we have SIM cards of two GSM operators:  T-Mobile: Using the following prefixes (602, 606, 607, 723, 724) and it requires that you dial the number from your mobile phone with the international prefix (+420). All numbers have a nine digit length with the operator prefix but without the international prefix.  Vodafone: Using the following prefixes (901, 902, 907, 909) and requires you to dial the number with the prefix (+420). All numbers have a nine digit length with the operator prefix and without "+420".   First we have to assign modules to two GSM outgoing groups (for each operator).The first step which we have to do is to place the SIM cards into the SIM holders. We will start with modules 0 using the T-mobile operator SIM. Module 2 will follow the same procedure but using the Vodafone SIM.   Configuration of GSM outgoing groupsYou are able to set up different setting for each GSM group (CLIR, free minutes, Virtual ring tone, roaming and others).  Prefix listsWe have to create two network lists, the first one for T-mobile and the second one for Vodafone.  T-mobile network list:We configure the normalization of Called party number in the Table of replaced prefixes (the number in front of the slash mark is replaced by number behind the slash mark. If there is not any number in front of the slash mark, it equals to "everything").We also have to fill in the Table of prefixes with all prefixes of the T-mobile operator. Because all numbers are 9 digits length, it is not necessary to specify it for each prefix, we can use the parameter Default count of digits and fill there the value 9.For the match in prefix list, the Table of replaced prefixes, Table of accepted prefixes and Digits count must correspond with the called number.  Vodafone network list:We configure the normalization of Called party number in the Table of replaced prefixes (the number in front of the slash mark is replaced by number behind the slash mark. If there is not any number in front of the slash mark, it equals to "everything"). We also have to fill in the Table of prefixes with all prefixes of the Vodafone operator. Because all numbers are 9 digits length, it is not necessary to specify it for each prefix, we can use the parameter Default count of digits and fill there the value 9.   LCR TableWe have to configure rows in the LCR table where we bind together GSM Outgoing groups with Prefix lists. Click on ADD button (or edit the first line of LCR table) to add the first line and configure it the following way for the T-mobile: Click on ADD button to add the second line and configure it for the Vodafone.Now you can see two LCR lines in the LCR table:    Incoming calls  For incoming calls you can define 2 groups with the different behavior and assign them to the GSM modules. The settings are similar with GSM groups assignment for outgoing calls.  In GSM incoming groups you can define the behavior for each GSM incoming group. Choose the mode to Reject, Ignore, Accept incoming calls or Callback.  With mode Accept..., you can define the list of called numbers which will be automatically dialed after DTMF dialing timeout in case the customer does not press any button within the specified time. From the configuration, you can see 5 seconds for DTMF dialing and after that the call will be routed to the extension 100 in your PBX (if you set up SIP proxy (GSM->IP) in VoIP parameters). If you want immediate connection set DTMF dialing timeout to 0.    SIM cards  In the Gateway control and module control you can see the status of the SIMs. The recommendation for quality of the signal is between -65 and -85dBm.  The logged SIM card is indicated by switched off the led diode on the 2N VoiceBlue Next

Question 43

3CX - How to interconnect with 3CX?

Accepted Answer

2N VoiceBlue Next has these parameters:  IP address 192.168.50.51  Incoming port: 5060  Firmware version: 01.00.03rc3   3CX PBX parameters:  IP address 192.168.50.115  Incoming port: 5060  Software version: 9.0    2N Voice Blue Next settings  SIP trunk interconnection For the setting of the trunk between the 2N VoiceBlue Next and your PBX you need to configure SIP proxy (GSM→IP) for GSM incoming calls. SIP proxy (IP→GSM) is designed to secure communication with traffic from your CCM only. You can specify the IP address and port from which SIP packets will be accepted. In case you leave there 0.0.0.0 it will be open for all traffic.   Configuration of the LCR (Least Cost Routing) The GSM operator has e.g. in our country prefix 6 and 7 with nine digits in a number. The setting is below.     You need to create LCR rule for defined prefixes. The GSM group defines a way for the outgoing call routing. An appropriate SIM card is selected based on the GSM groups assignment.   3. Configuration of GSM outgoing groups You are able to set up different settings for each GSM group (CLIR, free minutes, virtual ring tone, roaming and others)  4. Incoming calls For incoming calls you can define 2 groups with the different behaviour and assign them to the GSM modules. The settings are similar with GSM groups assignment for outgoing calls.  In GSM incoming groups you can define the behaviour for each GSM incoming group. Choose the mode to Reject, Ignore, Accept incoming calls or Callback.  You can define the list of called numbers which will be automatically dialled after DTMF dialling timeout if the customer does not press any button within the specified time. From the configuration you can see 10 seconds for DTMF dialling and after that the call will be routed to the extension 100 to your 3CX PBX (if you set up SIP proxy (GSM->IP) in VoIP parameters).     3CX PBX SETTING  You can download the 3CX PBX for free. Then you can activate a free version by registering the product and using a demo license key (Settings → Activate License) and the 3CX system will be changed to Commercial Edition (3CXPSDEMO) where all features are available. Demo license is not limited by time.    You can check differences between Free version and Commercial Edition in this document on page 11.   Create an Extension Use the button Add Extension and fill up Extension Number and ID and Password.    Create a new SIP trunk Add → VOIP Provider in the menu of the 3CX PBX. Use the name of provider and choose Generic SIP Trunk. Then use the button NEXT.   Fill up the IP address and the listening port of the 2N® VoiceBlue Next.  Fill up the External number (this number will be identification of call - FROM and CONTACT field)  Set up the the extension where incoming call will be routed from the 2N VoiceBlue Next.     Set up Outgoing rules  Prefix called from the extension  Set up the range of extension which can use this trunk (e.g. 111-120)  SIP trunk and Strip Digits (0 will be striped in this case)  Set up codecs and turn off registration of the SIP trunk. This setting is in VOIP Providers → Advanced  Create inbound rules specify numbers or range numbers that could be dialled from 2N® VoiceBlue Next. You can use "*" for all numbers. specify the SIP trunk from which the number will come specify the extension, ring group or voice mail where the call will be connected    Make a call You can register your SIP phone or download the 3CXPhone from 3CX web page for free: http://www.3cx.com/VOIP/voip-phone.html Register your SIP phone to the 3CX PBX and make an outgoing call with specified prefix to GSM via 2N VoiceBlue Next.

Question 44

Access credentials - How to add them to 2N device?

Accepted Answer

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

Question 45

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 46

Adding external Axis camera to 2N Indoor Touch 2.0

Accepted Answer

You are able to add an external Axis camera into the 2N Indoor Touch 2.0. There are two ways how you can switch between the streams from external and internal cameras. The first option is to add Axis camera directly to the 2N Indoor Touch 2.0. The second option is to connect any IP camera to the intercom and use automation to be able to switch between the streams. Prerequisities:   Prerequisities    Axis camera (tested with Axis P3225-LVE MK II)  Firmware version  3.3.0.2.0  or higher           You can add only Axis camara into the 2N Indoor Touch 2.0. However there is a work around in case that you have different IP camera.  Step by step guide In order to assign the external IP Axis camera to the 2N Indoor Touch 2.0 you need to open the device list.    Figure 1 Then choose the intercom to which you would like to assign the camera. In this example it is Verso with IP address 192.168.50.134 and go into the details.    Figure 2 In the detail of the intercom you can enable the external camera option and you only need to configure the IP address of the camera ( in this example 192.168.50.172), login and password. You don't need to know the streaming URL, just the IP address of the camera.    Figure 3 Now you will be able to switch between the video streams during the video preview or video call by using the camera button on the right upper corner.    Figure 4 You can change the resolution and codec type in the Axis camera in the following section (Figure 5 - new web interface | Figure 6 - old web interface):    Figure 5: New web interface of the axis camera    Figure 6: Old web interface of the axis camera

Question 47

Alcatel-Lucent OXE (OmniPCX Enterprise) R12: How to interconnect with 2N VOICEBLUE NEXT

Accepted Answer

2N VoiceBlue Next firmware Version 1.37.3.40.3    Alcatel-Lucent OXE (OmniPCX Enterprise) R12    Functionality  Incoming and outgoing call, opening the door  2N VoiceBlue Next Configuration  Please set all usual Network settings according to usual practice. Do not use Authorization ID nor fill out any password. For both options described further is the setting of 2N VoiceBlu Next the same.     2N VoiceBlue Next has these parameters:  IP address 192.168.92.200  Incoming port: 5060  Firmware version: 1.37.3.40.3   Alcatel OXE parameters:  IP address 192.168.92.246  Incoming port: 5060  Version 12.2   Alcatel OXE configuration - Option - SIP  Create Trunk group, Type T2 - MINI SIP or SIP      Go to SIP Gateway settings     SIP Gateway - fill out number of SIP Trunk Group    After this please restart the Alcatel OXE.  Make sure that trunk channels are free.     SIP Proxy - set minimal authentication method to SIP     2N VoiceBlue Next configuration  1. SIP trunk interconnection For the setting of the trunk between the 2N VoiceBlue Next and your PBX you need to configure SIP proxy (GSM→IP) for GSM incoming calls. SIP proxy (IP→GSM) is designed to secure communication with traffic from your PBX only. You can specify the IP address and port from which SIP packets will be accepted. In case you leave there 0.0.0.0 it will be open for all traffic.     2. Configuration of the LCR (Least Cost Routing) The GSM operator has e.g. in our country prefix 6 and 7 with nine digits in a number. The setting is below.   You need to create LCR rule for defined prefixes. The GSM group defines a way for the outgoing call routing. An appropriate SIM card is selected based on the GSM groups assignment.       3. Configuration of GSM outgoing groups You are able to set up different settings for each GSM group (CLIR, free minutes, virtual ring tone, roaming and others). In case you don´t have a Ring back tone, set up Delay for ALERTING to option 4.      4. Incoming calls For incoming calls you can define 2 groups with the different behaviour and assign them to the GSM modules. The settings are similar with GSM groups assignment for outgoing calls.   In GSM incoming groups you can define the behaviour for each GSM incoming group. Choose the mode to Reject, Ignore, Accept incoming calls or Callback.   You can define the list of called numbers which will be automatically dialled after DTMF dialling timeout if the customer does not press any button till the specified time. From the configuration, you can see 10 seconds for DTMF dialling and after that the call will be routed to the extension 101 to your PBX (if you set up SIP proxy (GSM->IP) in VoIP parameters).

Question 48

Alcatel OXO - How to interconnect with Alcatel OXO 7?

Accepted Answer

2N VoiceBlue Next has these parameters:  IP address 192.168.92.200  Incoming port: 5060  Firmware version: 01.00.03i10   Alcatel OXO parameters:  IP address 192.168.92.246  Incoming port: 5060  version 7.7.1    2N VoiceBlue Next configuration  SIP trunk interconnection For the setting of the trunk between the 2N VoiceBlue Next and your PBX you need to configure SIP proxy (GSM→IP) for GSM incoming calls. SIP proxy (IP→GSM) is designed to secure communication with traffic from your PBX only. You can specify the IP address and port from which SIP packets will be accepted. In case you leave there 0.0.0.0 it will be open for all traffic.   Configuration of the LCR (Least Cost Routing) The GSM operator has e.g. in our country prefix 6 and 7 with nine digits in a number. The setting is below. You need to create LCR rule for defined prefixes. The GSM group defines a way for the outgoing call routing. An appropriate SIM card is selected based on the GSM groups assignment.   Configuration of GSM outgoing groups You are able to set up different settings for each GSM group (CLIR, free minutes, virtual ring tone, roaming and others). In case you don´t have a Ring back tone, set up Delay for ALERTING to option 4.   Incoming calls For incoming calls you can define 2 groups with the different behaviour and assign them to the GSM modules. The settings are similar with GSM groups assignment for outgoing calls. In GSM incoming groups you can define the behaviour for each GSM incoming group. Choose the mode to Reject, Ignore, Accept incoming calls or Callback. You can define the list of called numbers which will be automatically dialled after DTMF dialling timeout if the customer does not press any button till the specified time. From the configuration, you can see 10 seconds for DTMF dialling and after that the call will be routed to the extension 101 to your PBX (if you set up SIP proxy (GSM->IP) in VoIP parameters).     Alcatel OXO configuration  Setup a count of VoIP-Trunk channels for VoIP trunk to 2N® VoiceBlue Next    Choose Trunk group and check Public trunk check box. Change Link Category settings    At Link Category menu set up all necessary parameters    Assign Trunk Groups    Setup Numbering plans table. As Base settings choose ARS    Check Public numbering plan for incoming calls.  At Trunk Groups List assign List ID with Index at menu Numbering → Automatic Routing Selection → Trunk Groups List   Setup IP address of 2N VoiceBlue Next, codecs, bandwidth and GW keep alive timeout for VoIP trunk at menu Numbering → Automatic Routing Selection → Automatic Routing: Prefixes    At menu  Numbering → Automatic Routing Selection → Gateway   Parameters set up listening   port 5060. If you want to use 2N VoiceBlue Next with any different listening port (for example   5065), just set up the number of the port here.

Question 49

Allwin (billing software) does not work

Accepted Answer

Please check following settings:  NsBridge.dll in Allwin folder does correspond with fw in NS  Port 6991 is opened on NS (Console - Bridges)  Make sure the Port 6991 is not blocked by an Antivirus software

Question 50

AMS (Autonomous Metering System) - protocol IEC 62056-21

Accepted Answer

2N SmartCOM PRO supports communication protocol IEC62056-21 for reading data. This functionality is provided by special FW which is distributed on request.   In this FAQ 2N SmartCOM PRO is set for reading data from electricity meter. Electricity meter with RS485 and standard IEC62056-21 support had been used.   RS485 parameters need to be set as the very first step. Connect to the 2N SmartCOM PRO via putty and use the set of following at commands: Settings RS485: speed 2400bd/s - data bits 7 – stop bits 1 – parity – even at^scport2="baudrate",2400 - set baudrate at^scport2="DATA_BITS",7 - set data bits at^scport2="STOP_BITS",1 - set stop bits at^scport2="PARITY",1 - set parity even at^scport2? - check settings on RS485 at^scport2="srestart" - save settings and restart RS485 interface   AMS AT commands: at^scams=? - display available commands for AMS and parameters of these commands  at^scams="enable",1 - switching on AMS system (0 means switch off) at^scams="dev_add",2,"IEC62056-21","947834","3M" - add device to the table Where 2 - RS485 port of 2N SmartCOM PRO"IEC62056-21" – defined used protocol in string form,"947834" - serial number of device used like device address"3M" is time interval. Supported reading intervals "1M", "2M", "3M", "4M", "5M", "6M", "10M", "12M", "15M", "20M", "30M", "1H", "2H", "3H", "4H", "6H", "8H", "12H", "1D"   at^scams? – show listed devices  at^scams="dev_remove",1-32 – remove one device on defined position at^scams="dev_clear" – remove all devices   Reading data from electricity meter:   Direct reading data: at^scams="direct_read",2,"IEC62056-21","947834",2400   Where 2 is a port of 2N SmartCOM (PRO),"IEC62056-21" – defined used protocol in string form,"947834" serial number of device used like device address2400 is baudspeed   Reading saved data from 2N SmartCOM PRO at^scdata=? - display available parameters for work with data "MESS_CNT" - number of saved messages in memory "GET_SPACE" – available memory in bytes "GET_OLDEST" – listing of oldest message "GET_FILTERED" – listing messages by applied filter "DEL_OLDEST" – delete oldest message "DEL_ALL" – delete all saved messages    Example: Check how many messages are saved and display 4 oldest messages. Delete all saved messages from 2N SmartCOM PRO internal memory: at^scdata= "MESS_CNT"at^scdata="get_oldest",4at^scdata="del_all"

Question 51

AMS (Autonomous Metering System) - protocol M-Bus

Accepted Answer

FAQ describes how to set 2N SmartCOM PRO ETH for AMS function. 2N SmartCOM PRO ETH with this function can reads data using M-Bus interface automatically and store data in internal memory. Firmware which supports this feature for 2N SmartCOM PRO ETH is SCE_1-12-0-12-24 or higher, this FW is distributed on request, please ask 2N. FAQ shows an example with electricity meter INEPRO PRO 380-M with M-Bus support   Unit can be configured via hyperterminal tool (e.g. putty) or software 2N SmartCom terminal config ati3 - Check firmware version    (Primary address of electricity meter = 1, secondary address = 15020416, baudrate=2400, databits=8, stopbits=1, parity=even)  at^scport2="BAUDRATE",2400 at^scport2="DATA_BITS",8 at^scport2="STOP_BITS"",1 at^scport2="PARITY",1 at^scport2="SRESTART" - Save configuration and restart port at^scport2? - Show actual port settings    AMS AT commands:  Primary address:   (meter´s primary address = 1)  at^scams=? - Display available commands for AMS and parameters of these commands   at^scams? - Show added devices and AMS function settings   at^scams="enable",1 - Enable AMS function (0 = AMS turned off)      at^scams="dev_add",2,"MBUS","1@2400","1M" - Add meter do AMS table Where: 2 - M-Bus port of 2N SmartCOM PRO unit "MBUS" - protocol for communication "1@2400" - primary address and baudrate "1M" - time interval. Supported time interval: "1M", "2M", "3M", "4M", "5M", "6M", "10M", "12M", "15M", "20M", "30M", "1H", "2H", "3H", "4H", "6H", "8H", "12H", "1D"   at^scams="dev_remove",1-32 - Remove device from defined position at^scams="dev_clear" - Delete all devices from AMS table  Primary addresses 254 a 255: The address 254 (FEh) and 255 (FFh) are used to transmit information to all participants (Broadcast). With address 255 none of the slaves reply, and with address 254 all slaves reply with their own addresses. The latter case naturally results in collisions when two or more slaves are connected, and should only be used for test purposes.Quotation: http://www.m-bus.com/mbusdoc/md5.php   at^scams="direct_read",2,"MBUS","254@2400" - one time jednorázové vyčtení bez uložení do paměti jednotky 2N SmartCOM PRO    at^scams="dev_add",2,"MBUS","254@2400","1M" - AMS vyčítání na adrese 254    Secondary address:  (secondary address of electricity meter = 15020416)   Some devices support only primary addresses.   Secondary address is always eight digit long.          A) use AT command for detecting connected M-Bus devices AT^SCAMSADD=,,,, AT^SCAMSADD=2,"MBUS",2400,"1M",1 ^SCAMSADD: 65286,1,"1,15020416" Unit 2N SmartCOM PRO ETH detected 1 meter with secondary address 15020416 and add this device to the table.     B) use SMS for detecting connected M-Bus devices send SMS in the form: SC AMSADD PWD= QTY= PORT= PROTOCOL= INT= [BAUDRATE=] BAUDRATE is optional      C) add device manually to AMS - secondary address is known AT^SCAMS="DEV_ADD",2,"MBUS","*15020416@2400","1M" Where: 2 - M-Bus port of unit 2N® SmartCOM PRO "MBUS" - protocol for communication "*15020416@2400" - secondary address and baudrate "1M" - time interval. Supported time interval: "1M", "2M", "3M", "4M", "5M", "6M", "10M", "12M", "15M", "20M", "30M", "1H", "2H", "3H", "4H", "6H", "8H", "12H", "1D"      D) add device manually to AMS - with "wild cards".  Wild cards - you can use letter "F" in secondary address of meter (it can cause collisons at bus)  Secondary address for meters in range between 150204700 and 15020499 with default baud speed 2400 Bd: "*150204FF@2400" AT^SCAMS="DEV_ADD",2,"MBUS","*150204FF@2400","1M"      One time readout, do not stored data to 2N SmartCOM PRO internal memory (direct_read):  works for primary and secondary address  at^scams="direct_read",2,"Mbus","1@2400" Where: 2 - M-Bus port of unit 2N SmartCOM PRO M-Bus - protocol for communication 1@2400 - address and baudrate     Read data from internal memory of 2N SmartCOM PRO (at^scdata): at^scdata=? - Return available commands for at^scdata "MESS_CNT" - Number of saved messages in memory of 2N SmartCOM PRO unit "GET_SPACE" - Available memory in bytes "GET_OLDEST" - Listing of oldest message "GET_FILTERED" - Listing messages by applied filter "DEL_OLDEST" - Delete oldest message "DEL_ALL" - Delete all saved messages   Example: AT^SCDATA? AT^SCDATA="GET_OLDEST",18     Original format of M-Bus message: ^SCDATA: "AMS",1471376881,18372,"MBUS",1,0,"","684B4B680801721604021592B00102AB0000000C04710700008C1004710700008C2004000000001C04580800009C1004580800009C2004000000002C0487000000AC100487000000AC2004000000000A16"   Format of M-Bus message:   ^SCDATA:,,,,,,,  - typ of record - AMS  - time mark  - sequential number of saved record  - name of protocol  - index of device from table of devices  - number 0 = without error  - not used in M-Bus  - raw data

Question 52

AMS error codes description (M-Bus, IEC 62056-21, S0, IN, ONF)

Accepted Answer

Question 53

AMS for IN1 IN2 IN3 (pulses S0, analog value, digital value)

Accepted Answer

This FAQ describes how to set 2N SmartCOM PRO ETH for AMS function. 2N SmartCOM PRO can with this function automatically read data from the INPUTS and store data in the internal memory. This feature is available for all units with firmware 1.13.X   2N SmartCOM PRO ETH is equipped with three inputs (IN1, IN2, IN3) Input Interfaces:  Voltage range: 0–10 V DC  Current range: 0–20 mA DC  Digital input with threshold level setting  S0 pulse inputs (You can increase the S0 bus resistance against interference if necessary by connecting PullUp voltage from the power supply or an internal 3V6 supply)    Disconnect the 2N SmartCom PRO from the power supply before opening the cover. Be careful while handling the jumpers to avoid damaging the device!     Make sure that the 2N SmartCOM PRO ETH jumpers are set as shown in the following image        Pulse counting on S0 inputs  pulse counting on S0 inputs  at^scpulse1="start"                                               - enable pulse counting on input 1. at^scams="ENABLE",1                                               - enable AMS functionality. AT^SCAMS="DEV_ADD",128,"AIN_DIN","1/PULSE/ABS","5M"               - absolute value of pulses on input 1 each 5 minutes at^scpulse2="start"                                               - enable pulse counting on input 2. AT^SCAMS="DEV_ADD",128,"AIN_DIN","2/PULSE/REL","5M"               - relative (difference between two readouts) value of pulses on input 2 each 5 minutes Possible time intervals:                                          -  "1M", "2M", "3M", "4M", "5M", "6M", "10M", "12M", "15M", "20M", "30M", "1H", "2H", "3H", "4H", "6H", "8H", "12H", "1D"   at^scams?                                                         - Show added devices ^SCAMS: 1> 128,"AIN_DIN","1/PULSE/ABS","5M" ^SCAMS: 2> 128,"AIN_DIN","2/PULSE/REL","5M" AT^SCAMS="DEV_REMOVE",1                                           - Remove device from defined position  at^scdata="get_oldest",50 ^SCDATA: "AMS",1461340261,12091,"AIN_DIN",1,0,"","131"           - results from port 1      ^SCDATA: "AMS",1461340381,12093,"AIN_DIN",1,0,"","228"           - results from port 1  ^SCDATA: "AMS",1461340441,12094,"AIN_DIN",1,0,"","234"           - results from port 1  ^SCDATA: "AMS",1461340681,12098,"AIN_DIN",2,0,"","21"            - results from port 2    Analog value on input Calibrate 2N SmartCOM PRO ETH inputs before measurement -    Current measurement: - range between 4 and 20 mA. Voltage measurement: - range between 0 and 10V DC. at^scams="ENABLE",1                                               - enable AMS functionality. AT^SCAMS="DEV_ADD",128,"AIN_DIN","1/ADC/CAL","1M"                 - calibrated value will be store to memory (range  0 - 100) input 1 AT^SCAMS="DEV_ADD",128,"AIN_DIN","2/ADC/ABS","1M"                 - output from A/D converter will be stored to memory (range 0 - 1023) input 2 Possible time intervals:                                          - "1M", "2M", "3M", "4M", "5M", "6M", "10M", "12M", "15M", "20M", "30M", "1H", "2H", "3H", "4H", "6H", "8H", "12H", "1D"   at^scams?                                                         - Show added devices ^SCAMS: 1> 128,"AIN_DIN","1/ADC/CAL","1M" ^SCAMS: 2> 128,"AIN_DIN","2/ADC/ABS","1M"   AT^SCAMS="DEV_REMOVE",1                                            - Remove device from defined position   at^scdata="get_oldest",50 voltage was the same on both inputs - 6,45V ^SCDATA: "AMS",1464185101,7112,"AIN_DIN",1,0,"","56"                - calibrated value on input 1 ^SCDATA: "AMS",1464185101,7113,"AIN_DIN",2,0,"","521"               - output value from A/D on input 2 voltage was the same on both inputs - 4,45V ^SCDATA: "AMS",1464185160,7114,"AIN_DIN",2,0,"","354"                - calibrated value on input 1 ^SCDATA: "AMS",1464185160,7115,"AIN_DIN",1,0,"","38"                 - output value from A/D on input 2 voltage was the same on both inputs - 10,2V ^SCDATA: "AMS",1464185221,7116,"AIN_DIN",1,0,"","92"                 - calibrated value on input 1 ^SCDATA: "AMS",1464185221,7117,"AIN_DIN",2,0,"","848"                - output value from A/D on input 2    Digital value on input Calibrate 2N SmartCOM PRO ETH inputs before measurement -   Current measurement:                                                 - range between 4 and 20 mA. Voltage measurement:                                                 - range between 0 and 10V DC. at^scams="ENABLE",1                                                  - enable AMS functionality. AT^SCAMS="DEV_ADD",128,"AIN_DIN","2/DIN","1M"                        - digital value on input 2 will be stored in memory every minute possible time intervals:                                              - "1M", "2M", "3M", "4M", "5M", "6M", "10M", "12M", "15M", "20M", "30M", "1H", "2H", "3H", "4H", "6H", "8H", "12H", "1D"  At^scams? ^SCAMS: 1> 128,"AIN_DIN","1/ADC/CAL","1M" ^SCAMS: 2> 128,"AIN_DIN","2/ADC/ABS","1M"                                ^SCAMS: 3> 128,"AIN_DIN","2/DIN","1M"                                - reading digital value on input 2 is on third position  AT^SCAMS="DEV_REMOVE",1                                             - Remove device from defined position  Voltage was 4,45V - logical 0 ^SCDATA: "AMS",1464186241,7150,"AIN_DIN",3,0,"","0" ^SCDATA: "AMS",1464186241,7151,"AIN_DIN",1,0,"","39" ^SCDATA: "AMS",1464186241,7152,"AIN_DIN",2,0,"","360"   Voltage was 6,45V - logical 1 ^SCDATA: "AMS",1464186301,7155,"AIN_DIN",3,0,"","1" ^SCDATA: "AMS",1464186301,7153,"AIN_DIN",1,0,"","56" ^SCDATA: "AMS",1464186301,7154,"AIN_DIN",2,0,"","524"       Direct read one time readout, not stored to 2N® SmartCOM PRO internal memory AT^SCAMS="DIRECT_READ",128,"AIN_DIN","1/ADC/CAL"                     - readout of current signal value on IN1, result is calibrated (range 0-100) AT^SCAMS="DIRECT_READ",128,"AIN_DIN","2/DIN"                         - readout of current signal value on IN2 and this value is transformed to a logical value (range 0 - 1) AT^SCAMS="DIRECT_READ",128,"AIN_DIN","1/PULSE/ABS"                   - read current count of pulses on IN1

Question 54

Analogue modems - supported protocols by 2N&#174; EasyGate and 2N&#174; SmartGate

Accepted Answer

Following protocols are supported: V.90, V.34, V.32bis, V.32, V.22bis and V.22. Some of these protocols allow a higher speed than the speed supported by GSM network. The transmission in GSM network is always limited to 9,6 kbps (CSD).

Question 55

APS reader - Connection of lock and card reader (APS) including jumper configuration to 2N IP Vario

Accepted Answer

Various ways to connect the APS: Lock with external power supply - no APS connected Lock with internal power supply - no APS connected Lock with external power supply - APS connected Lock without external power supply - APS connected - power source from APS is used for the lock - power source from APS is used for the lock    Note the position of jumpers on the device shown bellow.   Lock with external power supply - no APS connected  Lock with internal power supply - no APS connected  Lock with external power supply - APS connected  Lock without external power supply - APS connected - power source from APS is used for the lock

Question 56

Asterisk - How to interconnect with Asterisk?

Accepted Answer

2N VoiceBlue Next has these parameters:  IP address 10.0.0.20  Incoming port: 5060   Asterisk parameters:  IP address 10.0.0.10  Incoming port: 5060    Scenario  If we have an IP network in which Asterisk PBX, several SIP phones and 2N VoiceBlue Next are connected, the configuration would be as shown in the figure below. Furthermore, suppose that the network is addressed as shown in the figure and GSM numbers are all numbers starting with 6, 7 and containing 9 digits.     2N VoiceBlue Next settings  SIP trunk interconnection For the setting of the trunk between the 2N VoiceBlue Next and your Asterisk PBX, you need to configure "SIP proxy (GSM→IP)" for GSM incoming calls. "SIP proxy (IP→GSM)" is designed only for secure communication with the traffic from your Asterisk. You can specify the IP address and port where the IP packets will be accepted. If you leave there "0.0.0.0", the traffic will be unsecured. To enable incoming calls to Asterisk, you can register the 2N VoiceBlue Next directly into the Asterisk system. You can register it as "Friend" types in case you require registration based on username and password or "peer" type (on based of IP address and port). SIP registrar...an Asterisk IP address which registers the gateway Registration domain - IP address where the gateway is going to be registered Username...username under which the gateway shall be registered Password...registration password    Configuration of the LCR (Least Cost Routing) You have to specify prefixes for the operators in the country you are currently located. An example of this would be that in Czech Republic prefix 6 and 7 have a 9 digits number. The setting is displayed below.  You need to create specific guidelines connecting prefixes with the GSM group. In the "GSM group" you will specify settings for SIM cards assigned to this specific group. In the "GSM group assignment" you can assign the module for the appropriate GSM outgoing group.    Configuration of GSM outgoing groups You are able to have different setting for each GSM group (CLIR, free minutes, virtual ring tone, roaming and others)   Incoming calls For incoming calls you can define 2 groups with the different behaviours and assign them to the GSM modules. The settings are similar with "GSM groups assignment" for outgoing calls.  In GSM incoming groups you can specify the traits for each GSM incoming group. Choose the mode to Reject, Ignore, Accept incoming calls or Callback.  You can define the list of numbers called. The number will be automatically dialled after the DTMF dialling has timed out. This happens when the customer does not press any button until the specific time. At this point, the number will be routed to the extension 100 to your Asterisk (if you set up SIP proxy (GSM->IP) in VoIP parameters).     Asterisk settings  Now add a few lines into the Asterisk configuration for proper routing of outgoing calls to the 2N VoiceBlue Next gateway and receiving calls coming from the GSM gateway to Asterisk.   Outgoing calls The core of Asterisk connection is saved in the /etc/asterisk/extensions.conf file. Open this file in your favorite editor and add the following lines: exten=>_6XXXXXXXX,1,Dial(SIP/${EXTEN:0}@10.0.0.20,,r) exten=>_7XXXXXXXX,1,Dial(SIP/${EXTEN:0}@10.0.0.20,,r) Once you have saved and closed the file, restart Asterisk. From this point forward, all calls starting with 6 and 7 should be routed to the 2N VoiceBlue Next gateway.  Incoming calls It is highly recommended to make few restrictions for incoming calls in order to prevent unauthorised people from calling over your system. Since the 2N VoiceBlue Next system works with the SIP, modify the /etc/asterisk/sip.conf file where the 2N VoiceBlue Next section could look as follows: [general] port = 5060 bindaddr = 0.0.0.0 allowgues=no context = sip disallow=all allow=ulaw [VoiceBlueNext] type=peer host=10.0.0.20 username=voiceblue secret=password fromdomain=10.0.0.20 Furthermore restart the Asterisk after saving the file. Then the Asterisk will be ready to receive calls coming from the 2N VoiceBlue Next gateway.  What to do in case of trouble:  First of all check our web page faq.2n.cz and try to see if there is any solution to your problem. In case you cannot find the proper answer, use the link: How to report an issue on the 2N  VoiceBlue Next.    Here is the the direct link: https://jira.2n.cz/confluence/pages/viewpage.action?pageId=22513331

Question 57

Audio files - Progress tones - Required format in 2N Netstar

Accepted Answer

Wav, 8kHz, 8bit, mono, A-law.

Question 58

Audio-relay card - How to set up jumpers on NetStar

Accepted Answer

Please check HW manual –  pages 25-26.

Question 59

Audio - What can I do when call is connected but I can't hear any voice? (RTP packets are empty)

Accepted Answer

In this case please check a gain of your DSP processor. You can do it by AT command  at&v0  . In the response of this AT command you can see parameter  g01  which should have value 2,32,32. In case that you see value 2,0,0 you have to use  at%g01=2,32,32  to set this parametr properly. This applies only for firmware 2.07.35b02 and lower.

Question 60

Audio - What should I do if I can't hear ringback tone?

Accepted Answer

Please go to GSM Outgoing groups and set "Delay for CONNECT" = 0   and "Delay for ALERTING"=4   in all groups.   If you want to hear the tone and voice messages (like "We are sorry, the called party is not available.") from GSM network then verify that "Send 180 Ringing instead of 183 Session Progress" is disabled in VoIP parameters and that "Generate virtual tone" is disabled in GSM outgoing groups.   If you want to overwrite tones and voice messages coming from GSM network with generated tone by gateway then set appropriate "Ring tone" in GSM Basic Parameters and select "Generate virtual tone" in GSM Outgoing groups. Verify that "Send 180 Ringing instead of 183 Session Progress" is disabled in VoIP parameters.   If you want to overwrite tones and voice messages from GSM network by ring-back tone from IP PBX/IP Phones then enable "Send 180 Ringing instead of 183 Session Progress" in VoIP parameters.

Question 61

Audio - What to check if I have voice quality issue?

Accepted Answer

You need to check following points:  Signal quality – The quality of the signal must be in the range -65dBm and -85dBm in the module without call activity. You can check the quality of the signal in the configuration of the 2N VoiceBlue Next (Gateway control –> Module control) or by using the command at&qall from the hyperterminal or putty.  A Switch setting – Check, if the port is in the mode of FULL DUPLEX. Half duplex doesn't make sense for UDP RTP packet. In case there is just one call via this port, the quality can be satisfactory, but with more call traffic the issue with voice quality is present.  The best tool how to check if it´s caused by defective 2N VoiceBlue Next or other things is to connect the 2N VoiceBlue Next to the PC and make a direct SIP call from software phone as SJ phone. Use the called number in this format: sip:phonenumber@ipaddressofVoiceBlueNext

Question 62

Audio - What to check if You can't hear the ring-back tone?

Accepted Answer

Please check that you have latest firmware version (download section) and following settings:  Delay for ALERTING in GSM outgoing groups is set on 1 and higher  If you enable Virtual Ring Tone in GSM outgoing groups you must set Ring Tone in GSM basic parameters so gateway knows the tone to generate. Be aware that this setting overrides Ring tone (which can also contain e.g. the information that the calling party is not reachable, notice about transferred number, ringing tone etc.) and replaces it by the virtually generated ringing tone.

Question 63

Audio - What to check if you have voice quality issue?

Accepted Answer

You need to check following points:  Signal quality – The quality of the signal must be in the range -65dBm and -85dBm in the module without call activity.You can check the quality of the signal in the configuration of the 2N VoiceBlue Next (Gateway control –> Module control) or by using the command at&qall from the hyperterminal or putty.  Switch setting – Check if the port is in the mode of FULL DUPLEX. Half duplex does not make sense for UDP RTP packet. In case there is just one call via this port, the quality can be satisfying, but with more call traffic the issue with voice quality appears.  The best tool how to check if it is caused by defective 2N VoiceBlue Next or another things is to connect the 2N VoiceBlue Next to the PC and make a direct SIP call from software phone as SJ phone. Use the called number in this format: sip:phonenumber@ipaddressofVoiceBlueNext.

Question 64

AutoCLIP routing - How to set AutoCLIP routing?

Accepted Answer

What is AutoCLIP?  The GSM gateway automatically stores information about outgoing calls to the AutoCLIP routing table. When a person calls back the call is routed directly to the original number. If original number is not available the call is routed to the next number set up in the configuration (e.g. receptionist).    How to set in 2N VoiceBlue Next?  Parameters need to be set are in field Others   Time to keep CLIP in table - set the time duration for which records are to be kept in the AutoCLIP routing table.  Add record only for unconnected call - only unconnected outgoing calls (missed calls on a mobile phone) are stored in the AutoCLIP table.  Delete record for connected answer - if the call back is answered, the record in the AutoCLIP table will be deleted.  In the AutoCLIP routing table you can see the record of unconnected call.    When the user (737276015) has a missed call and returns that call, he will be directly forwarded to destination 11 as shown in the AutoCLIP routing table and also in the trace bellow.

Uit productie

2N Indoor Touch 2.0

2N IP Vario

2N LTE Verso

2N Analog Force

2N Analog Safety

2N Analog Uni

2N Analog Vario

2N EasyGate PRO

2N Indoor Touch

2N Net Audio Systems

2N NetStar

2N SmartCOM

2N StarGate / BlueStar / BlueTower

2N VoiceBlue Lite

2N VoiceBlue Max

2N EasyGate

2N SmartGate

2N SpeedRoute / EasyRoute

2N BRI Lite-onderneming

2N KantoorRoute

2N VoiceBlue Next

Lijst met veelgestelde vragen