AutoCLIP routing is enabled but not working

Verify gateway settings: Check in GSM Incoming groups that Time to keep CLIP in table [hours]: value is higher than 0. Verify PBX settings PBX must transmit a number which is calling. You can check via Utils/Report capture if PBX is correctly set. Please see examples of correct and wrong call requests from PBX in the gateway trace:e02/gxx--> setup.ind (011) GRP-E/0/00 CHA-2 CDN- 603603603 CGN- (05/8) *** wrong ISDN SETUP message , CGN is not providede02/gxx--> setup.ind (011) GRP-E/0/00 CHA-2 CDN- 603603603 CGN- 1111 (05/8) *** correct ISDN SETUP message , CGN is providedCDN is the dialed number, CGN is the calling number

Calling - A call is not disconnected immediately

The release of the call in GSM network can take up to 2 s. If you experience longer delay, it can be caused by gateway or by PBX settings. Usually the connection stays active because of simulation of the analogue line. If call is disconnected in the analogue line, you can hear a busy tone. This is not typical anymore in ISDN networks but you can simulate this behaviour and generate busy tone up to 30 s. On the gateway side you can set following: If call stays up while being disconnected from GSM side. Go to ISDN parameters and set Busy tone on None. (This will turn off busy the tone generation from the gateway.) If call stays up while being disconnected from PBX side. Go to GSM Basic parameters and set Busy tone on None. (This will turn off the busy tone generation from the gateway). If call is not cut after this settings, then set this parameter to Disabled. (If PBX requests to keep line active in disconnection message then gateway will ignore this request and the call will be ended)

Calling - Outgoing call through BRI Lite/Enterprise is rejected

Please check following items: Presence of a valid license key (Gateway control - Firmware/License) The communication protocol on the line from your PBX to the gateway has to be set to Euro ISDN DSS1 according to Q.931 Proper settings of the NT/TE modes on the gateway (Gateway configuration - ISDN parameters - ISDN BRI port settings) which must correspond to the other party settings The ISDN port modes are set to accept calls from the BRI port (Gateway configuration - ISDN port modes - ISDN BRI port) The SIM cards are properly inserted and their PIN code request is disabled or it has the same PIN code as it is set in the gateway (Gateway configuration - GSM basic parameters - SIM cards PIN code) The SIM cards are logged to the network correctly - both LEDs labelled as GSM1 and GSM2 must be off (they are blinking during logging process, but they switch off after they are logged successfully) The GSM modules have got good signal strength between -60dB and -80 dB (Gateway control - Diagnostics) The SIM cards are active, they have credit and they are not blocked by the GSM operator If you use CLIR function Enabled in the gateway (Gateway configuration - GSM outgoing call - CLIR function), check if this feature is enabled (activated) on the SIM card by the GSM operator The dialled number is in correct format, it matches one of the Network Lists and this Network List is actively used in the LCR section The default count of digits is set to the value that corresponds to the length of the dialled number (Gateway configuration - Number of digits dialled from ISDN resp. Gateway configuration - Prefixes - Default count of digits) If you have set Max. number of called minutes, make sure those minutes have not been already exceeded The Time limitation of SIM card (which part of the day shall be used) is set correctly The selection of GSM modules which will be assigned to the ISDN channel (Gateway configuration - GSM basic parameters - GSM module selection) Time and Date is set correctly in the Gateway

Call routing - Changes in call routing in firmware 1.20+ compared to earlier versions on 2N BRI Lite and BRI Enterprise

In firmware 1.20 the way call routing was configured has been changed. In this FAQ you are going to find out what is different from previous firmware versions. On 2N BRI Lite and BRI Enterprise following changes have been done: In Gateway configuration there is no longer option to select port modes, where you were able to select how calls incoming from one port should be routed (basically allowing you to route calls from BRI to GSM or VoIP). This setting has been merged into LCR table offering an easier configuration. LCR table has been redone. New LCR table allows you to have a complete control over where an incoming call (from VoIP, GSM or BRI interface) should be routed to. On pictures bellow you can see examples of differences between the new LCR table and the old one. 1) Explanation of new LCR table Records in LCR table are read from top to bellow. When a record that matches all conditions is found than the call is going to be sent to outgoing destination specified in that record. Therefore it is important to pay attention to the order in which you have your LCR table records organised! From (channels/groups) - this parameter specifies where outgoing call originates. In case of BRI gateway it can be: all GSM channels specific GSM incoming group (1-2) BRI NT interface all channels BRI NT interface, specific channel (1-2) BRI TE interface, all channels BRI TE interface, specific channel (1-2) VoIP Prefix list - you must specify either one prefixlist, that the outgoing call number must match, or you can select option All prefixlists, where any outgoing call number that matches at least one prefixlist, will be routed by channel specified under Groups/Tariffs Groups/Tariffs - this parameter specifies if outgoing call should go through a specific GSM outgoing group, VoIP or BRI interface (NT/TE) This way you have a better control over how outgoing and incoming calls are handled and routed. Plus it is possible to route incoming calls from GSM back to GSM which was not possible in older firmware version. 2) Default LCR table settings Firmware 1.20 Firmware 1.19 and older In default there are 6 records which match the default setting of Port modes and LCR table from firmware 1.19 and older You needed to setup both Port modes and LCR table. 3) Routing outgoing calls from BRI NT interface and VoIP based on prefix lists (2 outgoing GSM groups with 2 prefix lists), incoming calls are left in default Firmware 1.20 Firmware 1.19 and older Calls coming from BRI NT interface (lines 2-4) are routed based on prefix lists. if there is a match in prefix list 1, the call is sent over GSM outgoing group 1 if there is a match in prefix list 2, the call is sent over GSM outgoing group 2 if dialled number does not match prefix list 1 or 2, or there are no free channels in GSM outgoing group 1 or 2, the call is sent to BRI TE interface Calls coming from VoIP (lines 6-8) are routed based on prefix lists: if there is a match in prefix list 1, the call is sent over GSM outgoing group 1 if there is a match in prefix list 2, the call is sent over GSM outgoing group 2 if dialled number does not match prefix list 1 or 2, or there are no free channels in GSM outgoing group 1 or 2, the call is sent to BRI TE interface First you needed to change Port modes to match your desired scenario (top picture above) and than you needed to create 2 rules in your LCR table to match your scenario. 4) Incoming call from GSM group 2 (matching prefix list 2) will be routed back to GSM through GSM outgoing group 1. Every other incoming call from GSM will be sent to BRI TE interface. Everything else is left in default. Firmware 1.20 Firmware 1.19 and older Sending incoming calls from GSM back to GSM was not possible On picture above you can see how to set a scenario where all incoming calls from GSM incoming group 2should be sent back to GSM through GSM outgoing group 1 (if dialled number will match Prefix list 2) Sending incoming calls from GSM back to GSM was not possible Sending incoming calls from GSM back to GSM was not possible On the picture above you can see how to set described scenario. All calls from GSM incoming group 2 (matching prefix list 2) are sent back to GSM.All other calls from GSM are sent to BRI TE interface. Sending incoming calls from GSM back to GSM was not possible

Can I use 2N BRI Lite or 2N BRI Enterprise with my PBB?

If the PBU has an ISDN port with Euro DSS1 signaling according to Q.931, then you can use 2N BRI gateways without any problems.

Dial plan - How to adjust the number of outgoing call?

In firmware version 1.20 we have changed the way how call routing is set up. This FAQ is going to show you how to adjust the number of outgoing call in firmware 1.20+ . If you are using an older version of BRI gateway (metallic case) to configure this function go here: older BRI gateway When I make an outgoing call, the PBX sends number in the following format: 07 1234 5678. I need to dial to GSM 0044 7 1234 5678. Is that possible with 2N® BRI Lite or 2N® BRI Enterprise? Gateway 2N® BRI Enterprise supports modification of dialled prefix. This may be done in the section: Gateway Configuration – Prefixes– Table of Replaced Prefixes How exactly does it work? All numbers starting with 0 are matched in Prefix list 1 and the 0 is automatically replaced by 0044. Then the rest of the digits after 0 (which means number 7 1234 5678) received from PBX is compared in the Table of accepted prefixes. If there is a match, the call continues to the LCR section where an appropriate SIM card is assigned to this call.

Do 2N BRI Lite and 2N BRI Enterprise support data transfers?

2N BRI gateways support voice calls, send/receive SMS messages, but do not support data transmission.

Event reporting on 2N BRI Lite and 2N BRI Enterprise

Please send all the following information A detailed description of the given problem and its origin in verbal form to facilitate replication. The configuration file downloaded from the given BRI gateway. The version of the configuration tool that was used to configure the given BRI gateway List of AT commands ati3 and ati4 entered in the Terminal menu of the configuration tool or hyperterminal Full Trace of the given problem if possible to log the problem All this information will help us quickly diagnose and find a solution to your problem. Thank you for your understanding

Factory reset - How to make a factory reset of 2N BRI Lite/Enterprise

If you need to setup your device to the factory values, please proceed following instructions. This action is irreversible. The factory values and credentials are listed at the end of this document. Factory reset via web interface: Go to the section Management In the right column, click on the Configuration reset Select parameters which will be set to default values Save settings Reset to factory settings using a button: To reset the factory values, press the Reset button until the LED indicators start flashing red. Note: If you forget the password or set the IP interface incorrectly, you can press the RESET button right to the BRI ISDN connector for a long time. Doing so, you reset all the factory configuration values for all the parameters including those related to the Ethernet interface and access data. Default Settings: IPv4 address 192.168.1.2 IP mask 255.255.255.0 Gateway 192.168.1.1 User name Admin User password 2n

Firmware Upgrade - How to make a firmware upgrade on 2N BRI Lite and 2N BRI Enterprise?

Visit our website www.2n.com and download FW for 2N BRI Lite or BRI Enterprise Open web interface of your GW and go to the section Management->Firmware update. Select the FW file you downloaded in the previous step and upload it to the GW. GW will reboot, after reboot you can check in the same section whether the update was successful as you can see the FW version there.

How many simultaneous calls can be made at once through one 2N BRI Lite or 2N BRI Enterprise?

The number of simultaneous calls is equal to the number of SIM cards in the gateway. One 2N® BRI gateway can contain a maximum of 2 SIM cards.

How to edit the called number from PBX on 2N BRI Lite and 2N BRI Enterprise?

2N BRI gateways support calling number modification. You can find this setting in the section Configuration – List of prefixes – Tab. of replaced prefixes (see figure) How exactly does it work? All numbers starting with 0 are "matched" in Prefix List 1 and the digit 0 is automatically replaced by the number 00420. Then the rest of the digits after the replaced digit 0 (ie the number 7 1234 5678) are compared in the Prefix Table. If I successfully match the rest of the number here as well, the call continues to the LCR table, where the SIM card is assigned to make the call.

ISDN trunk interconnection Alcatel

2N BRI Gateway settings Set BRI gateway as NT device. Then set the mode. If you are using DDI, then set PTP (Point to Point). If you are using MSN numbers, then set PtMP (Point to Multipoint). If you don't know, which mode should be selected, in 95% cases is correct Point to Point. (Optional) To avoid synchronisation issue is recommended to use 2N BRI Enterprise and connect second ISDN port of gateway to UA (Universal Alcatel) via S0 Adapter EU. Then assign to the UA some extension number to provide clock to the gateway and set TE Mode to External Sync in gateway's ISDN Parameters. Alcatel OXO settings Create a new DSS1 trunk at External Lines → List Of AccessesChoose DSS1 Protocol type and setup the number of channels At list External Lines → List Of Trunk Groups menu assign the trunk to trunk group Create a numbering plan at menu Numbering → Numbering Plans Setup Least Cost Routing table at menu Numbering → Automatic Routing Selection →Automatic Routing: Prefixes At menu Numbering → Automatic Routing Selection → Trunk Groups Lists assign index with trunk group

ISDN trunk interconnection Siemens

2N BRI Gateway settings Set BRI gateway as NT device. Then set the mode. If you are using DDI, then set PTP. If you are using MSN numbers, then set PtMP. If you don't know, which mode should be selected, in 95% cases is correct Point to Point. Siemens 3000 series settings In Siemens go to trunk settings. Select the line with the ISDN port connected to gateway and double-click in Param. column cell. Screenshot is showing example of 4 ISDN ports. 2 of them are set as trunk and the other 2 as Extension. Gateway will be connected as Trunk. After you double-click in Param. column, you will get following window In Protocol Description select S0: Euro CO PP for Point to Point (in 95%) or S0: Euro CO PMP for Point to Multipoint. That is all. Optionally you may deny to take clock from the gateway. Otherwise, if the PBX goes down, once the PBX is up again it may choose synchronisation from gateway and cause trouble to other ISDN ports. Following settings prevent this. Just select the port with gateway in table at bottom left, column Denied nos. list.

Network Trace - How to get Wireshark network trace and network trace from 2N BRI Lite / Enterprise?

Network trace contains whole communication between IP devices over LAN. In order to analyse what this communication between devices contains, a network trace can be requested. If network trace is requested, please note there are two possible network traces available. Gateway can provide network tracing with limited size on its side, for unlimited network trace of IP communication, external device (usually laptop or PC) equipped with network capture software needs to be used. This article explains how to perform both network trace in such software called Wireshark as well as network trace directly from gateway. How to get Wireshark network trace? How to get network trace from 2N BRI Lite/Enterprise? How to get Wireshark network trace? Program Wireshark is used for tracing the communication between devices interconnected by LAN. The devices (e.g. PBX connected with a GSM gateway via LAN) send to each other packets which are captured by the above mentioned program. Wireshark is distributed under the Open source licence (http://www.wireshark.org/download.html). Before starting network capture Before Wireshark (or in general, any packet capture tool) is used, careful consideration should be given to where in the network packets are to be captured. In order to capture all the packets which are sent via particular LAN, the devices have to be part of the same network segment (they have to be connected via HUB). If you do not have a hub you can use a switch which supports so called port mirroring (http://en.wikipedia.org/wiki/Port_mirroring). Download Wireshark Obtain a Wireshark package or installer for the operating system running on the system which is to be used for packet capture.Download a binary or installer from http://www.wireshark.org. With installers, ensure all product components are selected for installation. Start Wireshark On a Linux or Unix environment, select the Wireshark or Ethereal entry in the desktop environment's menu, or run "wireshark" (or "ethereal") from a root shell in a terminal emulator. In a Microsoft Windows environment, launch wireshark.exe from program installation folder. Note that on Unix systems, a non-GUI version of Wireshark called "tshark" (or "tethereal") may be available as well, but its use is beyond the scope of this article. Use Wireshark (capture network communication) After starting Wireshark, do the following: Select Capture | Interfaces Select the interface on which packets need to be captured. Now click the Start button to start the capture. Recreate the issue. The capture dialog should show the number of packets increasing. If packets are not being captured, try removing any filters that have been defined. Important: In order to provide us with detailed information about the possible problem with the device, please do not apply any filter and simply capture all the communication during the test (call/smpp/email2sms,etc...). Once the issue which is to be analysed has been reproduced, click on Stop. It might take a few seconds for Wireshark to display the packets captured. Save the packet trace in following format: „File->Save As->Wireshark/tcpdump/… -libpcap(*.pcap;*.cap) .Just click on the File menu option and select Save As.By default Wireshark will save the packet trace in libpcap format. This is a filename with a.pcap extension. Please send saved file to us for analysis. How to get network trace from 2N BRI Lite / Enterprise ? Network trace from gateway can be run via menu Utils -> Network capture. The web interface can store up to 4096kB long trace. Network trace can be started by clicking on button START. You will be notified by message "Running..." in capturing status. The Buffer utilisation and Packets captured should show the number of packets increasing. If not, then restart the capture. If Buffer utilisation is on value 4096kB (same as Buffer size), please restart the trace and tests from beginning. Recreate the issue. Once the issue which is to be analysed has been reproduced, click on Stop. Once trace is stopped, you can save it to your computer by clicking on the diskette icon located in bottom right corner of web interface Please send saved file to us for analysis.

Remote control - How to setup and use Remote Control over GSM?

What do you need to have? GSM modem - the easiest is to use a mobile phone as a GSM modem Active licence for GSM Remote Control - licence is active in case when you can see parameter TUN next to DSS1 in the active protocols on the bottom line of the configuration tool. If you do not have it, please contact your sales person and order 50208920E - Licence for remote control over GSM BRI LITE or BRI Enterprise with firmware 2.xx.16 or newer Step by step procedure: During installation of the GW set up login user name and password, you may do that also by using AT command at%x80=login/passw, for example at%x80=brie/testThe same login data will be required from now on for Remote Control and Local Control over USB Connect your GSM modem (mobile phone) to your PC. Go to Settings - Communication Settings and choose the Modem Connected to your PC as seen below In the configuration tool go to Gateway - Gateway list - click on Add Fill in information such as: Name of Installation place Login data Phone number of SIM card installed in the GW In case you have BRI Enterprise with Ethernet interface, fill in IP address of the Ethernet Interface For more details check the picture below To establish the connection with Remote gateway go to Gateway List, choose the right gateway and click on Connect button. You shall see a window like this To disconnect the session click on the Icon "Disconnect Gateway" or in "Gateway Control" choose the same thing.

SIM card usage - How to use both SIM cards equally?

You must set in the chart "GSM basic parameters" the parameter "GSM module selection" to "SMART (by free minutes)" In LCR table set for the prefixes from your Network List (Prefix List) the option "Any Module"

SMS at no answer - How to setup "SMS at no answer"?

Definition of SMS´s text and ringing period First condition is to define text for "SMS at no answer" (red box on the following picture). You also need to setup time period in seconds. This means for how long a GSM station have to be in ringing mode (blue box on following picture). This time period is counted from the moment BRI gateway gets an ALERTING message. Calling party identification There has to be calling party identification in incoming SETUP message to 2N® BRI Gateway (CGN element cannot be empty in the SETUP message).

SMS messages - How to send and receive messages? - SMS gateway integration

Our GSM/UMTS gateways can be used for calls and text messaging at the same time. This page introduces several ways how to send and receive text messages and how you can integrate our gateway with your system. Please note that 2N gateways do not support MMS messages sending/receiving. This FAQ applies for following gateways: 2N BRI Lite, 2N BRI Enterprise (2 channels) 2N VoiceBlue Next (2 or 4 channels) 2N VoiceBlue MAX (4 channels) 2N BlueTower (2 to 8 channels), 2N StarGate (2 to 32 channels). SMS parameters: Sending speed - approx. 10 SMS/minute/GSM module (the speed depends on the local conditions of the specific GSM operator, there is no limitation from 2N side) Support of long SMS (over 160 characters), UTF-8/UTF-16 coding and special characters (Chinese, Arabic, Hebrew...) Delivery report (DLR) Flash SMS End user can send/receive messages via: Gateway's web interface Email client (for ex.: Microsoft Outlook, Mozilla Thunderbird, Opera Mail, Windows Live Mail etc.) - additionally licensed feature SMPP (Short Message Peer-to-Peer) Client/Server (for ex.: Diafaan SMS Server, ActiveXperts SMS Server, Inetlab.SMPP, Logica OpenSMPP etc.) - additionally licensed feature Application developed by you which uses one of the integration options (see below). Integration is possible via: Email conversion to SMS and SMS conversion to email through POP3 and SMTP protocol - additionally licensed feature (up to 200 email users; "SMSE" and "SMSUx" license keys needed) SMPP protocol version 3.3 or 3.4 for SMS transmission over IP - additionally licensed feature (up to 200 SMPP users; "SMSS" and "SMSUx" license keys needed)2N GSM/UMTS gateway can behave as SMPP Client (ESME - External Short Messaging Entity) or SMPP Server (SMSC - Short Message Service Center). Gateway's AT commands through Telnet protocol GSM/UMTS module's AT commands through Telnet protocol (if this access is used, the gateway can not be used for calling) 3rd party software which can provide an additional interface 1) Email to SMS and SMS to email details You can use any common Email client which supports SMTP protocol (for SMS sending) and POP3 protocol (for SMS reading) with basic authentication. Email conversion to SMS:From: user@domain (optionally can be included in SMS)To: number@domain (up to 100 recipients)Subject: Text (optionally can be included in SMS)Body: Message text (always included)The domain selects among the group of GSM/UMTS modules (SIMs). A free module sends a message. The user has a right to send a message into the own domain. Up to 4 different domains can be set. SMS conversion to email:From: number@domainTo: user@domainSubject: Text (Different values can be included: number, time of SMS reception, SIM ID)Body: Message text Example: SMS messages - How to configure Email2SMS and SMS2Email features with Microsoft Outlook for VBN?. 2) SMPP protocol details The SMPP protocol is a standard protocol intended for the transmission of SMS messages over IP between SMS peer entities such as SMS Center (SMSC - usually 2N GSM/UMTS gateway) and Client (ESME - usually your SMPP software). There are a few different versions of the SMPP protocol, 2N GSM/UMTS gateways support the most common versions 3.3 and 3.4. This protocol has been developed as a worldwide standard for the SMS messages exchange in the core networks of GSM operators and therefore is very suitable for heavy SMS messaging applications where you need to get the best possible messaging speed performance. You can use one of various existing commercial SMPP applications such as Diafaan SMS Server (FAQ: SMPP connection - How to connect Diafaan SMPP server ), ActiveXperts SMS Server (FAQ: SMPP connection - How to connect ActiveXperts SMPP server ), Inetlab.SMPP or Logica OpenSMPP (FAQ: smpp-connection-how-to-connect-logica-smpp-server ). Alternatively you can implement it by your own to your own proprietary application. Detailed specifications of the SMPP protocol ver. 3.4 are available for ex. here if needed. SMPP v 3.4 is without the specifaction of default character set. If you keep the default value then please use ASCII encoding. 3) Gateway's AT commands details When you connect to the gateway using terminal via Telnet, you will be able to send the SMS message directly over any available GSM module.First of all start the low-level controlling for SMS by the AT command AT!G=A6. Then use following command syntax:Command: AT^SM=xx,yy,PDU,zzExample: AT^SM=0,18,001100098137491318F60000FF05F0B79C2E03,B4Description:xx = number of the GSM module gxxyy = length of the SMS's PDU (Number of symbols in PDU divided by 2 and minus 1; it equals 18 in the case of PDU from this example)PDU = beginning with 0011 - without confirmation, 0031 – with confirmation. For the translation use please any PDU converter (for ex. here).zz = control sum (Sum hexa Bytes just like their are without transformation to dec - pairs 00+11+00+09+...etc., then you got a result – in this case its 5B4. Control sum is last two digits from the end – in this case it is B4). All necessary AT commands are described in the user manual, see the SMS Control section in the online version here: 4.2 Configuration Commands 4) GSM/UMTS module's AT commands details You can connect to the gateway using terminal via Telnet and send the SMS a very similar way as in the previous example, however now you will use the proprietary AT commands from the manufacturer of the GSM modules installed in 2N gateway.By these AT commands has to be each module controlled separately by sending them directly to the specific GSM module. Use following syntax: at&gxx=AT_command where xx is the number of desired module (00-31) and AT_command is the specific command of the module. Please note that the GSM modules can be used for SMS messaging only when the direct module access is being used. This SMS messaging way is completely at your own risk without any 2N support. All necessary AT commands are described in the AT commands set manual of the specific manufacturer. These manuals have to be usually obtained directly at the manufacturer. 2N gateways can be equipped by following GSM/UMTS modules: Cinterion MC55i-w, Telit GE910, Telit HE910-EUR. 5) 3rd party software details A 3rd party software compatible with 2N gateway can be easily used. So far we have successfully tested the SMS Tool Server 3 application which uses the direct access to the GSM modules (as referred in 4) GSM/UMTS module AT commands details). The 2N gateway behaves from the point of view of the SMS Server Tool 3 as a regular GSM modem. This application allows you to input the SMS messages from a source database file, this database can be filled manually or from a web interface (using a PHP script you will write by your own). Please note that the GSM modules can be used for SMS messaging only when the direct module access by a 3rd party SW is being used. This SMS messaging way is completely at your own risk without any 2N support. The freeware SMS Server Tool 3 application can be downloaded here.

Static IP address - How to set up static IP address on 2N BRI Lite/Enterprise

If you need to set a static IP address for your device, please proceed following instructions. Keep in mind that for further access to the web interface you will need to be in the same network range. The basic values and credentials are listed at the end of this document. How to setup a static IP address: Go to the section Gateway In the right column, click on the Gateway configuration / Ethernet configuration Unselect: Use DHCP Type an IP address, Subnet mask, Default gateway and at DNS server(s). Save settings Default Settings for Static IP Address: IPv4 address 192.168.1.2 IP mask 255.255.255.0 Gateway 192.168.1.1 User name Admin User password 2n

Trace - How to get internal trace from 2N BRI Lite / 2N BRI Enterprise?

Web interface - short trace, just few calls The internal trace can be run via menu Utils -> Report capture. Check in Gateway -> Gateway configuration -> Report configuration that all fields are enabled. Online view for the internal trace is shown in menu Gateway -> Gateway control -> Online report. Telnet client - long trace, "unlimited" The web interface can store up to 512kB long trace. Telnet client allows to use your computer as a storage for a longer trace. Bellow you can find instructions for application Putty. You can also use other telnet capable applications. Putty (www.putty.org) Download and run Putty. Choose Telnet in Connection type and fill in 2N BRI Lite / 2N BRI Enterprise's IP address. In Menu Session -> Logging, select Session logging: All session output and choose a file where the trace capture will be saved to. Establish connection with your gateway and fill login. 10. Now you can make test calls and other needed tests. 11. Pack the created trace file and send it to us via email with following information: the description of numbers you tried to dial / send sms to reported issues desired scenario details (what do you need to achieve - such as routing specific numbers to different modules/SIM cards, etc...). In BRI Configuration tool (for older M114 and M115 CPU) Connect with BRI configuration tool to the gateway (over serial communication or LAN) Go to Gateway control -> Tracing Set details of the tracing: select all check boxes (it will set the level of trace) select tracing: FULL tracing choose Layers 2,3,4 Click on the button choosing (creating) the file to which the trace will be saved Click the button Start. When trace is done, press Stop and text of the trace will be saved in file which you set above.

Virtual Ring Tone - How to upload Virtual Ring Tone Message without configuration tool?

For uploading Virtual Ring Tone Message you have to follow these steps: check your FW version. You need to have FW 2.04.16 or higher for BRI Enterprise, FW 2.05.01 or higher for BRI LITE There are two spaces for Virtual Ring Tone messages, because each GSM channel has its own (they may of course be the same or different) You have to upload them now over Hyperterminal via this procedure: use command at!m1=erase (to delete any previous message) use command at!m1=write go to Transfer - Send file - choose Xmodem and select file with the Virtual Ring Tone - details of the sound file are listed below if the upload of the message fails, delete the message with at!m1=erase and upload it again for uploading of a message for 2nd GSM channel do the same procedure, but use at!m2 commands voice message must have the following characteristics: codec: CCITT-Alaw, Mono, sample-rate 8000, bitrate 8, 64 kbps max. duration of the file = 8 sec (64 kB) when you hear the Virtual Ring Tone during the call setup, then you have to set in the configuration tool in Gateway configuration - GSM out. groups - enable check box "Send Alerting message after dial to GSM" for both GSM channels save the configuration to the gateway and make an outgoing call to test the Virtual Ring Tone

What are the methods of sending and receiving SMS messages using 2N BRI Lite and 2N BRI Enterprise?

There are two options for sending or receiving SMS messages via the 2N BRI gateway: Using the SMS Server application - this is an application that every employee in your company can use on their computer. It will enable your entire company, or just selected employees, to conveniently send/receive SMS messages, using only one GSM gateway. This application also supports sending batch SMS messages, e.g. for marketing use. You can find more information about the SMS Server on the 2N website. The mentioned software solution is licensed. 2N BRI gateways also support custom commands for working with SMS messages. The mentioned commands can be found in the manual of the gateway and their use is free. However, this use assumes that you program the entire application for sending and receiving SMS messages yourself.