2N BRI Lite Enterprise User Manual v1.3

Download

www.2n.czFirmware

Version

2N BRI Lite/Enterprise

BRI-VoIP-GSM/UMTS Gateway

User Manual

1.3

1.5.0

The 2N TELEKOMUNIKACE joint-stock company is a Czech manufacturer and supplier of telecommunications equipment.

The product family developed by 2N TELEKOMUNIKACE a.s. includes GSM gateways, private branch exchanges (PBX), and door and lift communicators. 2N TELEKOMUNIKACE a.s. has been ranked among the Czech top companies for years and represented a symbol of stability and prosperity on the telecommunications market for almost two decades. At present, we export our products into over 120 countries worldwide and have exclusive distributors on all continents.

2N is a registered trademark of 2N TELEKOMUNIKACE a.s.. Any product and/or other

names mentioned herein are registered trademarks and/or trademarks or brands protected by law.

2N TELEKOMUNIKACE administers the FAQ database to help you quickly find information and to answer your questions about 2N products and services. On www.faq.2n.cz you can find information regarding products adjustment and instructions for optimum use and procedures „What to do if...“.

Declaration of Conformity

2N TELEKOMUNIKACE hereby declares that the 2N BRI Lite/Enterprise product complies

with all basic requirements and other relevant provisions of the 1999/5/EC directive. For the full wording of the Declaration of Conformity see the CD-ROM enclosed and at www.2n.cz.

The 2N TELEKOMUNIKACE company is the holder of the ISO 9001:2009 certificate. All development, production and distribution processes of the company are managed by this standard and guarantee a high quality, technical level and professional aspect of all our

Content

1. Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4 Terms and Symbols Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2. Description and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2 Brief Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.3 Available ISDN BRI Extension Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4 IP Voice Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.5 Types of 2N® BRI Enterprise Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3. Making Calls via BRI Gateway . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1 Supported 2N BRI Gateway Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.2 Call Routing Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4. First Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1 Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.2 Licence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3 Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.4 Factory Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4.5 Basic Configuration – Step by Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5. Introduction to Configuration Interface . . . . . . . . . . . . . . . . 44

5.1 Configuration Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6. Configuration Via Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.1 LAN Communication Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.2 GSM Gateway Behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

6.3 List of Terminal AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.4 Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.5 LOG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

6.6 Call Data Records (CDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

6.7 Statistics - Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

7. Technical Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8. Supplementary Information . . . . . . . . . . . . . . . . . . . . . . . . . . 93

8.1 Directives, Laws and Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

8.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

8.3 List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

8.4 General Instructions and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

1. Product Overview

In this section, we introduce the product, outline its2N BRI Lite / Enterprise

application options and highlight the advantages following from its use. Here is what you can find in this section:

1.1 Product Description

1.2 Safety Precautions

1.3 Upgrade

1.4 Terms and Symbols Used

52N TELEKOMUNIKACE a.s., www.2n.cz

1.1 Product Description

The GSM gateway provides direct interconnection of the2N Enterprise / BRI Lite

ISDN with GSM networks. It can also be used for direct interconnection of an ISDN PBX with a GSM network, ISDN telephone set and, via a terminal adapter, with an analogue apparatus or coin machine. The voice mode, i.e. outgoing and incoming calls, is the basic function of the gateway. Moreover, the BRI gateway provides connection to the VoIP–SIP networks. The gateway is equipped with all functions necessary for this mode

and is very user–friendly. In addition, allows you to 2N BRI Enterprise / BRI Lite

send and receive SMS messages. No additional devices (an external telephone, e.g.) are required for normal operation. All gateway parameters can be set using a configuration program (on an enclosed CD), or using the AT commands. Programmable parameters are pre–set to make it possible to make calls as soon as the supply cable, antenna a SIM cards are connected.

2N® BRI Enterprise / 2N® BRI Lite Differences

The and gateways are based on one and the2N® BRI Enterprise 2N® BRI Lite same type of hardware and apply identical firmware and control (configuration) software. The only difference lies in the count of BRI ISDN interfaces:

Interface

2N®BRI Lite 2N®BRI Enterprise

BRI ISDN 1 (NT/TE) 2 (1 TE ; 1 NT)

Ethernet YES* YES*

*The VoIP–SIP support depends on Part No. (subject to licence).

Telephone Cost Cuts

Having connected to your ISDN PBX, you can2N® BRI Enterprise / BRI Lite make calls to the mobile network directly. This saves your PSTN – GSM

.connection costs You do not pay for barred calls. You can set groups of barred numbers in the gateway. A flexible setting of the Least Cost Router helps you call GSM numbers at

.minimum operational costs You can route calls to alternative providers' networks via the VoIP/SIP interface. As all gateway user calls are added up for billing purposes, you are advised to use the most advantageous tariff offered by your provider.

62N TELEKOMUNIKACE a.s., www.2n.cz

2N BRI Enterprise / 2N® BRI Lite Basic Features

Integration of the best features of two communication technologies: ISDN and GSM

VoIP–SIP telephony support with G.711a/u and G.729ab codecs

Intelligent routing of incoming and outgoing calls Web interface for gateway configuration and SMS sending/receiving Automatic no answer SMS sending for GSM networks Automatic missed call SMS in the GSM network Simple recording of a welcome note, DISA voice message Automatic recording of call data and detailed statistics (CDR) ENBLOCK/OVERLAP ISDN dialling switch option Monitoring of ISDN BRI line statuses and alarm SMS sending option Automatic sending of Alive SMS in user–defined intervals Easy firmware upgrade via a configuration program External synchronising source connection option (BRI Enterprise)

Mobility Extension support.

[1]

Depending on the licence

[2]

Will be available in early 2013

DialThru (2N® BRI Enterprise)

The difference between and lies in the DialThru2N BRI Enterprise

2N BRI Lite

functionality. DialThru enables the gateway to be connected between the PBX and the voice service provider line, i.e. PSTN. The GSM gateway in the DialThru mode routes, based on the LCR, calls into the PSTN or GSM/UMTS networks.

Refer to the figure below for a schematic diagram of the connecti2N BRI Enterprise

on.

The gateway works as a dial–through router (using both the TE and NT ports in the DialThru

72N TELEKOMUNIKACE a.s., www.2n.cz

mode) for calls to a mobile network, and a monitoring system, which, with the appropriate licence, sends SMS to the provider (in the case of line unavailability, e.g.).

The GSM gateway contains just one ISDN BRI port and thus cannot2N BRI Lite

work in the DialThru mode. It can be connected to a PBX on a trunk line or extension and route calls to the GSM/UMTS networks only – see the figure below.

82N TELEKOMUNIKACE a.s., www.2n.cz

1.2 Safety Precautions

It is prohibited to use any transmitters, including the GSM/UMTS gateways, in areas where explosives are used, such as quarries.

It is prohibited to use the GSM gateways at petrol2N BRI Enterprise / BRI Lite

stations where mobile telephones are also prohibited. GSM phones may affect sensitive life–saving devices in medical centres. Therefore, it is forbidden to use GSM/UMTS devices, including the GSM gateways, in such facilities. In general, any prohibition regarding mobile phones based on RF energy radiation applies to GSM/UMTS devices too. If necessary, the GSM gateways may be installed at a safe distance from the prohibited area and connected with the original place through an Ethernet cable. Although GSM gateways are not intended for cars or aeroplanes, all relevant prohibitions and regulations regarding mobile phones apply to them too.

92N TELEKOMUNIKACE a.s., www.2n.cz

1.3 Upgrade

The manufacturer reserves the right to modify the product in order to improve its qualities. In response to the customers' requirements, the manufacturer constantly improves the

software contained in the product (firmware). For the latest 2N BRI Enterprise /

firmware version and the User Manual refer to the 2N .2N® BRI Lite web sites

Refer to the , , for a detailed description of the S. 2 Description and Installation 2N

firmware upgrade.BRI Enterprise / 2N® BRI Lite

Manual

Version

Changes

1.0

The User Manual relates to the 2N BRI Enterprise / BRI Lite

firmware version .1.5.0

102N TELEKOMUNIKACE a.s., www.2n.cz

1.4 Terms and Symbols Used

Manual Symbols

Safety

Always abide by this information to prevent persons from

injury.

Warning

Always abide by this information to prevent damage to the

device.

Caution

Important information for system functionality.

Tip

Useful information for quick and efficient functionality.

Note

Routines or advice for efficient use of the device.

Future Functions, Innovations

The in this document designates the functions that are undergrey-marked text preparation or development at present.

112N TELEKOMUNIKACE a.s., www.2n.cz

2. Description and Installation

This section describes the product and its2N BRI Enterprise /®2N BRI Lite

installation. Here is what you can find in this section:

2.1 Before You Start

2.2 Brief Installation Guide

2.3 Available ISDN BRI Extension Configurations

2.4 IP Voice Transmission

2.5 Types of 2N® BRI Enterprise Connection

122N TELEKOMUNIKACE a.s., www.2n.cz

2.1 Before You Start

Caution

Make sure that you are equipped with all system components necessary for putting in operation2N® BRI Enterprise / Lite (SIM card, ISDN phone and/or duly configured ISDN BRI line of your PBX or PSTN, an available Ethernet/USB socket and a PC for initial gateway configuration).

Product Completeness Check

Before installing this product, check whether the gateway delivery complies 2N BRI

with the following packing list:

Package BRI Lite BRI Enterprise

2N BRI Enterprise / Lite

1 1

Power supply adapter 1 1

Long antenna 1 – 2* 1 – 2*

Ethernet cable 1 1

BRI ISDN cable 1 2

Wall mounting set 1 1

*depends on the Part No.

Connector Lay–Out – Lower Side

The following connectors are available on the BRI gateway bottom:

Connector type BRI Lite BRI Enterprise

DC Jack 2.1mm supply connector YES YES

10/100BaseT Ethernet connector YES YES

ISDN BRI TE interface NO YES

ISDN BRI NT interface NO YES

ISDN BRI NT/TE interface YES NO

132N TELEKOMUNIKACE a.s., www.2n.cz

Caution

2N® has two RJ45 connectors, which, however, areBRI Lite

cross–connected into one ISDN BRI. Be sure to connect just one ISDN BRI line to make the system work properly. Which of the RJ45 connectors will be used depends on the type of the equipment to be connected (NT/TE) and the interconnecting cable (cross/straight).

Connector Lay–Out – Upper Side

There are SMA female antenna connectors to each GSM/UMTS module on the 2N BRI

upper side.Enterprise / Lite

Status LED Indicators – 2N® BRI Lite

The status is indicated by five LEDs on the front side. BRI 1 and BRI 22N BRI Lite

indicate the status of ISDN BRI B–channels and CH 1 and CH 2 indicate the status of each GSM/UMTS module. Refer to the table below for the statuses

142N TELEKOMUNIKACE a.s., www.2n.cz

LED Indicators

Power supply

green light – mains powered

– device switched offno light

GSM/UMTS network

green light – call in progress

errorred light –

network registration, SMSgreen flashing –

module restartred flashing –

– signal intensity indicationRed/green flashing

ISDN port

green light – 2 calls in progress

– ISDN synchronisation/active callgreen flashing

– ISDN disconnectedred light

– synchronisation of lower ISDN layersred flashing

Ethernet port

green light – disconnected+ no orange light

100BaseT connected, ingreen light + orange flashing – operation no green light + orange light – 10baseT connected, no operation green flashing + orange flashing – 10BaseT connection, in operation

Signal intensity

Signal intensity indication:one segment = less than –109dbmtwo segments = more than –95dbmthree segments = more than –81dbmfour segments = more than –65dbm

*If the devices have been interconnected, the layers will not be connected until the first call.

Status LED Indicators – 2N® BRI Enterprise

The status is indicated by five LEDs on the front side. BRI 1 and2N BRI Enterprise

BRI 2 indicate the status of ISDN BRIs and CH 1 and CH 2 indicate the status of each GSM/UMTS module. Refer to the table below for the statuses.

152N TELEKOMUNIKACE a.s., www.2n.cz

LED Indicators

Power supply

green light – mains powered

– device switched offno light

GSM/UMTS network

green light – call in progress

errorred light –

network registration, SMSgreen flashing –

module restartred flashing –

– signal intensity indicationRed/green flashing

ISDN port

green light – 2 calls in progress

– ISDN synchronisation/active callgreen flashing

– ISDN disconnectedred light

– synchronisation of lower ISDN layersred flashing

Ethernet port

green light – disconnected+ no orange light

Signal intensity

Signal intensity indication:one segment = less than –109dbmtwo segments = more than –95dbmthree segments = more than –81dbmfour segments = more than –65dbm

* If the devices have been interconnected, the layers will not be connected until the first call.

**Remember to set the signal intensity indication in the gateway configuration menu.

Potential GSM/UMTS Troubles

All gateways work reliably under a long–time full load. The following2N GSM

problems may be caused by GSM/UMTS networks:

The GSM/UMTS module(s) cannot log in, log in slowly, or log out occasionally. This problem may be caused by any of the following situations:

The GSM/UMTS signal is low. The minimum signal level should be approximately . If lower, change the antenna position or type!–80dBm The GSM/UMTS cell (BTS) to which the GSM/UMTS modules are trying to log in is overloaded. Change the antenna position or reduce the count of

the logged–in GSM/UMTS modules. One of the GSM/UMTS modules is permanently logged–out or fails to make outgoing calls:

The problem indicates a GSM/UMTS network overload on the installation

site. To eliminate the problem, set the parameter to Relax delay 2

. If the GSM module fails to log in or rejects to make outgoingseconds GSM calls even after the gateway restart, consult your GSM provider for your SIM card/GSM module availability.

The manufacturer shall not be held liable for any SIM card or provider service unavailability in the case of a breach of the provider's SIM terms and conditions for the SIM card use.

162N TELEKOMUNIKACE a.s., www.2n.cz

2.2 Brief Installation Guide

Installation Conditions

The following installation conditions have to be met for a proper installation:

2N BRI Enterprise / BRI Lite® is to be installed on a site with enough free

space.

2N BRI Enterprise / BRI Lite® is to be mounted on a suitable vertical surface.

For this purpose, a hanger is included in the gateway delivery, which is fitted to the wall using dowels and screws and used for gateway hanging.

It is possible to operate the gateway in another working position too, e.g. on a desk, for a short time for servicing and testing purposes, for example.

Any excess of the allowed working temperature may not affect the 2N BRI

function immediately but may result in faster ageing andEnterprise / BRI Lite lower reliability. For the allowed working temperature and humidity ranges refer to .S. 7

2N BRI Enterprise / BRI Lite® is not designed for high–vibration

environments such as means of transport, machine rooms, and similar.

2N BRI Enterprise / BRI Lite® is not designed for dusty environments or

places exposed to high humidity and temperature changes.

2N BRI Enterprise / BRI Lite® may not be exposed to aggressive gases, acid

and solvent vapours (during cover cleaning, e.g.).

2N BRI Enterprise / BRI Lite® is intended for indoor use. It may not be

exposed to rain, flowing water, condensing moisture, fog, and so on.

2N BRI Enterprise / BRI Lite® may never be exposed to direct sunshine or

placed close to heat sources (radiators). A sufficient clearance must be kept over and under 2N BRI Enterprise / BRI

for cabling and air flow to carry off the heat.Lite

A sufficient GSM/UMTS signal intensity has to be provided for 2N BRI

.Enterprise / BRI Lite

172N TELEKOMUNIKACE a.s., www.2n.cz

An adequate capacity of the GSM/UMTS network has to be ensured (no BTS overload). Remember that multiple GSM gateways used in one location may overload the base transceiver station (BTS) you are currently logged in to. This may lead to a permanent or occasional rejection of GSM/UMTS calls!

No strong electromagnetic radiation is allowed on the 2N BRI Enterprise /

installation site.BRI Lite

No strong electromagnetic reflections are allowed on the 2N BRI Enterprise /

antenna installation site.BRI Lite

An inappropriate location of or its antenna2N BRI Enterprise / BRI Lite

close to television, broadcasting and/or other rf–sensitive sets may impair the function of these sets.

Being a source of radio frequency emissions, the 2N BRI Enterprise / BRI

antenna should not occur in the close vicinity of the human body. The healthLite hazard is higher than with mobile phones as, generally, gateways shared by multiple users show a very high traffic. It is recommended that the power supply adapter should be connected to a network with a UPS back–up and due overvoltage protection.

SIM Card Inserting/Removing

Insert the SIM card in the bottom as shown in the2N BRI Enterprise / BRI Lite

figure. As the SIM slots are of the Push/Pull type, just slide the card in and push it into position. Push the SIM gently to slide it out of the slot.

182N TELEKOMUNIKACE a.s., www.2n.cz

Caution

Be sure to such provider/SIM card services as callset forwarding, call barring, preferred networks, SMS centre, etc. in

your mobile phone into before inserting the SIM card 2N

. BRI Enterprise / BRI Lite If two SIM cards are used, make sure that both the SIM cards have or .one and the same PIN PIN code request disable

Having inserted the SIM card, restart 2N BRI Enterprise

to make the SIM card log in./ BRI Lite Remember to the service beforedisable Another call on line using the SIM cards!

Antenna Connection

2N BRI Enterprise / BRI Lite® is equipped with a SMA female antenna connector for

all the GSM/UMTS modules. The external antenna should always be installed vertically on a site with a good wireless signal.

Warning

Tighten the antenna connector gently with your hand – never

!use a wrench

Being a source of radio frequency emissions, the 2N BRI

antenna should not be very close to theEnterprise / BRI Lite human body. The is higher than with mobilehealth hazard phones as, in general, gateways shared by multiple users show a very high traffic.

192N TELEKOMUNIKACE a.s., www.2n.cz

Note

The antenna has a sufficient gain for a trouble–free operation under normal conditions. If the signal is poor or you want to

place your antenna away from 2N BRI Enterprise / BRI Lite

, you can use an antenna with an SMA–connector terminated cable. The antenna should be mounted vertically. Refer to , , for the antenna S.7 Technical Parameters parameters.

Power Supply Connection

Use only the power supply adapter included in the delivery. Make sure that the electric distribution network voltage is in compliance with the data on the supply adapter plate before plugging the adapter and that the antenna is connected properly. If you connect the power supply without having connected the antenna, the GSM module transmitter may get damaged. Plug the supply adapter into the mains socket and only then connect the adapter connector to the gateway. Refer to the status indicators.

Warning

Connecting a defective or inappropriate power supply adapter may lead to a temporary or permanent 2N BRI Enterprise /

error!BRI Lite Check whether the antenna is connected before plugging the adapter. Feeding the device without antenna connection

may result in the GSM module transmitter damage.

202N TELEKOMUNIKACE a.s., www.2n.cz

Ethernet Cable Connection

To connect into the Ethernet network, use a standard2N BRI Enterprise/Lite

straight cable terminated with RJ–45 connectors (included in the package). The GSM gateway supports the 10BaseT and 100BaseT standards, the Ethernet connection status is indicated by the status LED indicators located on the RJ–45 connector (refer to for details). S. 2.1

Caution

The Ethernet interface is used for remote supervision and configuration only, i.e. does not contain the VoIP interface. With a proper licence, the device provides the VoIP–SIP support.

RJ–45 LAN Connector

NT and TE Connectors

1 not used2 not used3 Tx4 Rx5 Rx6 Tx7 not used8 not usedISDN devices are connected to the NT/TE connectors depending on the configuration of your telecommunications equipment. They are connected via a 4–wire passive bus with the aid of RJ–45 connectors. Refer to the figure below for the NT/TE connector pin lay–out.

212N TELEKOMUNIKACE a.s., www.2n.cz

TE connector The figure below shows connected as2N BRI Enterprise / BRI Lite

network termination (NT) – extension for your ISDN PBX or ISDN phone, i.e. your own equipment.

The figure below shows connected as terminal2N BRI Enterprise / BRI Lite

equipment (TE) – extension from the ISDN (PSTN), i.e. from your service provider.

An example of the connection in the ISDN mode follows. 2N BRI Enterprise

222N TELEKOMUNIKACE a.s., www.2n.cz

Caution

2N BRI Lite® is equipped with just one ISDN BRI. Hence, two

independent devices cannot be connected at the same time!

232N TELEKOMUNIKACE a.s., www.2n.cz

2.3 Available ISDN BRI Extension Configurations

You have to know the way of connection of your ISDN devices in order to configure your GSM gateway correctly. For information on your2N BRI Enterprise / BRI Lite

ISDN type, check your ISDN extension provider's registration form or contact your telephone network administrator.

Point–to–Point Configuration

The Point–to–Point (EuroISDN with DDI) configuration interconnects directly one ISDN terminal (TE) and a network terminal (NT) (see the figure below). This type is applied mainly where PBXs are connected to the ISDN.

Point–to–Multipoint Configuration

Point–to–Multipoint (EuroISDN with MSN) is another type of ISDN terminal interconnection. Here the network terminal (NT) is interconnected with up to eight ISDN terminals through a 4–wire passive bus as shown in the figure below.

242N TELEKOMUNIKACE a.s., www.2n.cz

2.4 IP Voice Transmission

Speech Encoding Methods

Voice transmission is strictly separated from signalling in VoIP networks. Modern VoIP networks mostly use the RTP (Realtime Transport Protocol) for voice transmission. The purpose of the RTP is only to transmit data (voice) from a source to a destination at real time. Codecs are used to save the channel data capacity. Codecs process the voice signal using variable algorithms to minimise the volume of user data. The degree of compression used by the codec affects the quality of voice transmission. Thus, the better voice transmission is required, the wider data range (the higher transmission rate) is needed. The MOS (Mean Opinion Score) scale is used for rating voice transmission quality, where 1 means the worst and 5 the best quality. For a survey of

the codecs supported by gateway refer to the table below.2N BRI

Codecs supported

Standard Algorithm

Transmission rate [kbps]

MOS

G.711a PCM 64 4.1

G.711u PCM 64 4.1

G.729 is an optional part of the system.

CS–ACELP 8 3.92

For gateway, quadruple the above mentioned rates (two fully duplex calls) 2N BRI

and add the TCP and IP header transmission rate to the result to get the resultant transmission rate. It is important to keep both a stable appropriate transmission rate during connection and a small and identical transmission time per data packet in order to maintain a high–quality voice transmission.

G.711 – this codec is used in digital telephone networks. The PCM (Pulse Code Modulation) is used for voice signal encoding. The sampled signal is encoded in 12 bits and then compressed using a non–linear scheme into the resultant 8 bits. Europe uses the A–law compression system while North America and Japan obey the µ–law. The resultant data flow is 64 kbps. G.729 – this codec uses the CS–ACELP (Conjugate–Structure Algebraic–Code–Excited Linear–Prediction) algorithm with the resultant transmission rate of 8 kbps. The speech signal is split into blocks of 10 ms each. The parameters of these blocks are then inserted in frames of the size of 10 bytes. 2–byte frames are generated for noise transmission.

During call set–up, a codec is selected automatically for voice transmission. g2N BRI

ateway supports the codecs included in the table above. The type of codec to be used depends on your VoIP network (individual devices) and your gateway2N BRI

configuration. gateway is designed primarily for VoIP corporate networks and2N BRI

tries to meet the opponent's codec requirements. If a codec is requested that is incompatible with , the call will be rejected.2N BRI Enterprise

The SIP and ITU–T H.323 recommended protocols are mostly used for connection establishing, maintaining and cancelling. gateway uses the (Session2N BRI

SIP

Initiation Protocol) signalling.

252N TELEKOMUNIKACE a.s., www.2n.cz

Tip

In the case of separated direct connection of your SIP Proxy and

, use the G.711 codec to achieve a high2N VoiceBlue Next

voice quality.

SIP Components

The following components are involved in the SIP message exchange:

UAC (User Agent Client) – the terminal device client, which initiates SIP signalling. UAS (User Agent Server) – the terminal device server, which responds to SIP signalling from the UAC. UA (User Agent) – a SIP network terminal (SIP phones, gateways to other networks, etc.), which contains the UAC and UAS. Proxy server – receives connection requests from the UA and transfers them to the next Proxy server if the given station is not under it administration. Redirect server – receives connection requests, but, instead of sending them to the called line, sends them back to the requesting device asking for where to route the request. Location server – receives registration requests from the UA and updates the terminal database accordingly.

All the server components (Proxy, Redirect, Location) are mostly on one physical device called Proxy server, which is responsible for keeping a client database and connection establishing, maintaining and terminating, as well as call routing.

The gateway VoIP–GSM gateway acts as a UA in any case (has the same2N BRI

functions as a VoIP phone), i.e. receives call set–up requirements and, on the basis of its inner LCR table, routes calls to GSM networks.

None of the SIP–defined server components are integrated in the gateway2N BRI

gateway.

SIP Signalling Messages

Below is a list of messages sent via the SIP:

INVITE – connection set–up request; ACK – INVITE confirmation by the final message addressee; BYE – connection termination; CANCEL – failed connection cancellation; REGISTER – UA registration with the SIP Proxy; OPTIONS – server capability query.

The answers to the SIP messages are numerically coded as the case is with the http protocol. Below are the most important ones:

1XX – information messages (100 – trying, 180 – ringing, 183 – progress); 2XX – successful request completion (200 – OK); 3XX – request forwarding needed (302 – temporarily moved, 305 – use Proxy); 4XX – error (403 – forbidden, 486 – busy here); 5XX – server error (500 – Server Internal Error, 501 – not implemented); 6XX – global failure (606 – not acceptable).

262N TELEKOMUNIKACE a.s., www.2n.cz

272N TELEKOMUNIKACE a.s., www.2n.cz

2.5 Types of 2N® BRI Enterprise Connection

This subsection deals with the types of connection of the gatewa2N BRI Enterprise

y to the main ISDN BRI extension.

ISDN TE – 2N BRI Enterprise Connection

The connection type shown in the figure below provides communication via a GSM/UMTS gateway without PSTN connection. The ISDN telephone sets are connected to the NT port of the GSM gateway, while a mains adapter simulating power supply from the PSTN is connected to the TE port. The adapter is available under Part No.

5020002.

2N BRI Enterprise Point–to–Point Connection

This type of connection is especially suitable for direct calls from an ISDN branch network to a GSM/UMTS network.

Another possible connection type is NT, where gateway synchronisation is derived from the PSTN BRI extension.

282N TELEKOMUNIKACE a.s., www.2n.cz

With multiple GSM gateways, the connection lay–out is as follows:

2N BRI Enterprise Connection as DialThru Router

This type of connection saves one BRI port to the PBX. Incoming PSTN calls are treated by the GSM/UMTS gateway in the DialThru mode while outgoing calls are routed according to the LCR table. The figure below shows the gateway as a DialThru router for the Point–to–Multipoint extension. Calls are routed automatically into GSM, UMTS or ISDN based on the internal LCR rules.

292N TELEKOMUNIKACE a.s., www.2n.cz

302N TELEKOMUNIKACE a.s., www.2n.cz

3. Making Calls via BRI Gateway

This section describes the call routing techniques via an ISDN BRI GSM gateway. The purpose of the settings is to improve your call efficiency and cut your call costs. Here is what you can find in this section:

3.1 Supported 2N BRI Gateway Functions

3.2 Call Routing Principles

312N TELEKOMUNIKACE a.s., www.2n.cz

3.1 Supported 2N BRI Gateway Functions

Time/destination based call routing B–channel based call routing Intelligent incoming CLIP routing (based on Calling Line Identification Presentation) Auto CLIP routing (automatic incoming call routing to a line stored in the AutoCLIP table) Time LCR (Least Cost Router) based outgoing call routing DISA (tone dialling) DISA into GSM (tone DID from ISDN ports to GSM networks) CallBacks to GSM SMS sending/receiving SMS at no answer Configuration via web interface Access password for configuration on all ports CLIP and CLIR for incoming GSM calls ENBLOCK/OVERLAP dialling transmission to ISDN Generation/retransmission from GSM of AoC pulses Table of allowed/barred numbers calling from GSM ISDN BRI monitoring with Alert SMS option Alive SMS in user defined intervals

2N Mobility Extension® feature

322N TELEKOMUNIKACE a.s., www.2n.cz

3.2 Call Routing Principles

2N BRI Lite

The gateway is equipped with one BRI ISDN and one VoIP–SIP ports. You can select one of the following incoming call processing modes for each of the ports via the web interface:

Use LCR table – in this case, calls with be routed as set in the LCR table; Reject calls – all incoming calls will be rejected; Route to port – all calls will be routed to the selected port without change.

If your BRI gateway is connected to a PBX subscriber line, you can activate DTMF. If you do so, the GSM gateway automatically answers any incoming call from BRI ISDN and offers the caller dialtone for another DTMF dialling. The call will then be routed to the GSM/UMTS modules. Incoming GSM/UMTS calls can be either DTMF–processed or automatically routed to the ISDN BRI / VoIP–SIP interface according to the active intelligent GSM gateway rules functions (Auto CLIP, CLIP routing). They are routed to the ISDN NT or ISDN TE interface depending on the GSM gateway configuration. Incoming GSM/UMTS calls can also be rejected and, with the aid of CLIP, used for CallBack. The LCR algorithm routes outgoing calls on the basis of the call type, current time tariff, day in a week and, if available, free minutes of GSM providers.

2N BRI Enterprise

The gateway is equipped with two BRI ISDN and one VoIP–SIP ports. You can select one of the following incoming call processing modes for each of the ISDN ports via the web interface

If your BRI gateway is connected to a PBX subscriber line, you can activate DTMF. If you do so, the GSM gateway automatically answers any incoming call from BRI ISDN and offers the caller dialtone for another DTMF dialling. The call will then be routed to the GSM/UMTS modules. Incoming GSM/UMTS calls can be either DTMF–processed or automatically routed to the ISDN BRI interface according to the active intelligent GSM gateway rules functions (Auto CLIP, CLIP routing). They are routed to the ISDN NT, or ISDN TE interface depending on the GSM gateway configuration. Incoming GSM/UMTS calls can also be rejected and, with the aid of CLIP, used for CallBack. The LCR algorithm routes outgoing calls on the basis of the call type, current time tariff, day in a week and, if necessary, free minutes of GSM providers.

332N TELEKOMUNIKACE a.s., www.2n.cz

Tip

2N BRI Enterprise / BRI Lite® can also route outgoing calls

into the GSM/UMTS networks according to the B–channel used. In that case, the GSM/UMTS module is paired with a specific B–channel of the ISDN BRI line.

LCR Table

The LCR (Least Cost Routing) table is the key telephone cost cutting factor. It helps you set call routing rules according to the CLIP, daytime and day in a week. By entering state (bank) holidays into the LCR table you achieve even more remarkable cuts. To make the prefix–based call routing to external ports and the LCR table work properly, select the module for the call in the parameter whileOutgoing destination creating the LCR record. The gateway also allows you to route outgoing GSM calls on the basis of the SIM card position. Such outgoing calls are not routed according to the GSM provider's number but through the defined GSM module. In addition, the ISDN ports can work in the DialThru mode. This means that all calls are routed to the respective port without any check. Namely, from TE to NT and vice versa.

Outgoing GSM Call Routing from Internal ISDN

If the GSM/UMTS gateway is connected to a subscriber line of your PBX, you are advised to enable the DISA function to GSM to make your GSM gateway answer every call routed to it by the PBX and wait for further dialling to GSM networks. The GSM/UMTS gateway routes outgoing calls to GSM as follows:

The calling subscriber dials a user number. If the user dialling is evaluated as , the gateway barredAccess to GSM gateway number table is searched through and, if a match is found, the call setup request is rejected. With an outgoing call, the gateway waits for further digits to be dialled. This timeout results in a certain delay between the subscriber's dialling and the subsequent dialling by the GSM gateway. Therefore, select the Count of dialled

for the called destinations while configuring your gateway. Then, thedigits gateway initiates the outgoing call processing algorithm on receiving the last digit The dialling prefix is first checked against the prefixes included in the first row of the LCR table. If no match is found, the following row is used for check and so on. In case the prefix and call time comply with the routing rules, the call is routed according to the first LCR rule to the module corresponding to the particular

included in the list.Outgoing GSM group Outgoing destinations If the selected GSM module is busy or has a low credit, the preceding step is repeated and the next LCR row is checked. In case the selected GSM module is free and has a sufficiently high credit, the GSM gateway starts dialling the GSM number. If the calling subscriber number has an unknown prefix or all routes are busy, the GSM gateway rejects the call setup request.

342N TELEKOMUNIKACE a.s., www.2n.cz

An outgoing call is not billed until the called party answers the call. The GSM network signals the off–hook and the GSM gateway transfers this information to the PBX. The gateway is able to generate the AoC tariff pulses during an outgoing call, which, if the GSM gateway is connected to the PBX, allows for call cost logging per user.

Incoming GSM Call Routing

Incoming GSM calls are routed by the algorithm described in the following steps and shown in the figure below: Incoming calls are processed according to the parameter in the Mode Incoming GSM

table. The following options are available:calls

Reject/Ignore incoming calls – incoming calls are not routed to extensions. The call setup request can either be rejected or ignored on the GSM side (the calling party hears the check ringing tone). Report to PC – information on an incoming call is sent to a PC equipped with the management software. The calling subscriber gets a voice message or the check ringing tone. The management software then completes the call routing procedure. CallBack – this function helps establish connection on the account of the SIM card inserted in the gateway. The incoming call is either ignored or rejected. After the calling subscriber hangs up, the GSM gateway sets up connection to the defined extension. When the extension answers, the GSM gateway replays the CallBack message to the extension while establishing connection to the previously calling GSM/UMTS subscriber. After the CallBack message, the GSM gateway interconnects the call. If CallBack with incoming call ignoring is enabled and the calling party fails to hang up within a defined timeout (default=10s), the CallBack function is disabled for this call and the subscriber can go on dialling the extension number. Set the CallBack function in the CLIP routing table. If none of the above mentioned options is selected, the AutoCLIP routing table is checked. If the calling number is found, the call is routed to the extension whose number is assigned to the calling number in the table. In case the calling number is not included in the AutoCLIP routing table, or the AutoCLIP routing function is disabled, the gateway receives the incoming call and either replays a voice message or transmits the dialtone to the calling subscriber. Then the gateway awaits the count of digits necessary for call setup. Define the minimum and maximum counts of DTMF digits in the Incoming GSM calls menu. If the gateway does not receive the minimum count of digits and no other digit comes from the GSM network within the timeout defined in the DTMF dialling

, the call is rerouted to the extension included in the .delay List of extensions

If call forwarding to extension is inactive, the incoming call is rejected.

352N TELEKOMUNIKACE a.s., www.2n.cz

DISA Message

With DISA activated and DISA welcome note recorded, the message is played to every incoming call whose CLIP is not included in the AutoCLIP table. After playing, the gateway waits for the first DTMF digit for the time period defined in the Incoming GSM

table. Having received the count of digits defined in the calls – DTMF dial timeout Inco

parameter, the gateway activates connection toming GSM calls – Minimum DTMF digits the SIP proxy or telephone via the port included in the table with theISDN parameters DTMF–received number. You can upload the DISA message using the GSM gateway web interface. Or, you can record the message using your PC as and load it into the gatewaydisa.wav using the configuration program via the web interface.

DISA Recording via PC and Web Interface

The DISA voice message parameters for PC recording are as listed below: maximum duration of 65s, compression according to ISDN A–law, mono, sampling frequency of 8kHz. Name the file Disa.wav and load it via the weGateway control – Voice messages b interface into the gateway.

DISA voice message parameters

Sound format: WAV

Sampling frequency: 8 kHz

Channels: 1 mono

Codec: ISDN A–law

362N TELEKOMUNIKACE a.s., www.2n.cz

4. First Launch

Having completed the physical installation, get acquainted with the factory settings and operation of the gateway. 2N® BRI Enterprise / BRI Lite Here is what you can find in this section:

4.1 Ethernet Interface

4.2 Licence

4.3 Firmware Version

4.4 Factory Reset

4.5 Basic Configuration – Step by Step

372N TELEKOMUNIKACE a.s., www.2n.cz

4.1 Ethernet Interface

The BRI gateway can be fully configured via the web interface at

. Make sure that a device equipped with a web browser (PC,http://IP_gateway_address NB, Tablet, etc.) has been connected for successful connection to the BRI gateway configuration interface. The device also supports configuration via an extended AT command set on the Telnet interface (IP port 23).

Tip

The device also supports configuration via an extended AT command set on the Telnet interface (IP port 23). Refer to Subs.

, page for details.6

The BRI gateway supports DHCP (client). By default, the DHCP support is disabled.

Tip

If DHCP is active, use specialised detection software (for LANs only) to identify the assigned IP address. Refer to the

web sites, BRI Gateways (IP Scanner) for thewww.2n.cz

software.

Use the web configuration interface in the Gateway configuration – Ethernet

section to set the Ethernet interface.configuration

Ethernet Interface Factory Settings

IPv4 address 192.168.1.2

IP mask 255.255.255.0

User name Admin

User password 2n

Caution

Change the user name and password during your gatewayfirst

configuration to avoid unauthorised access to your gateway configuration! Refer to page for details!

Tip

In the event of data loss or configuration interface unavailability, perform the factory reset to retrieve the data. Doing so, however, you reset all the default values in your gateway. Refer to , p. for details.Subs. 4.4

MAC Address

The BRI gateway has a unique, factory–set MAC (Media Access Control) address. Refer to the rear side label of your device or the gateway web interface for the MAC address.

382N TELEKOMUNIKACE a.s., www.2n.cz

The MAC address can be user–changed.

Tip

If you use DHCP, you are advised to set permanent assignment of one and the same IPv4 address to the defined MAC address to avoid unexpected change of the gateway IPv4 address and subsequent VoIP–SIP setting errors.

392N TELEKOMUNIKACE a.s., www.2n.cz

4.2 Licence

The BRI gateway can contain different licence keys depending on the Part No. Refer to the section via the web interface for the currentGateway control – Firmware/Licence licence key status.

Use this section to download a new licence key into your gateway in order to change the current software licence status.

Caution

The gateway can contain2N® BRI Enterprise / BRI Lite time–limited software licences (for SIP signalling, Mobility Extension, etc.). Such licences are limited to a certain period of time (hours) during which the gateway provides its services. Every GSM gateway restart adds one hour to the internal licence counter value!

A gateway with an expired licence processes no2N BRI

incoming or outgoing calls! Ask your dealer for licence term prolongation or an unlimited licence in due time.

Restricted Use in GSM / UMTS Networks

Some types of BRI gateways may be locked for use in specified GSM/UMTS networks only. This means that you will not be able to use such gateways in networks other than the recommended GSM/UMTS networks. This state is signalled by a red LED in the given GSM/UMTS module and a 'netw–err' cause in the diagnostics. Contact your dealer please for more information.

Tip

Contact your dealer please for more information.

402N TELEKOMUNIKACE a.s., www.2n.cz

4.3 Firmware Version

Upgrade your gateway with the latest firmware 2N® BRI Enterprise / BRI Lite version available for this GSM gateway type before installation. Refer to forwww.2N.cz the latest firmware version.

Warning

Use the for this GSM gateway type only tofirmware certified avoid to your system!irreversible damage

Download the new firmware version comfortably using the gateway configuration interface as follows:

Connect the PC and gateway to the Ethernet. Open the web browser (MS Internet Explorer 9 and higher or Mozzila Firefox v. 4 and higher are recommended). Log in to the GSM gateway web interface by entering http://IP_gateway_address

Click on , then on and select the new firmware file.Update Browse

Click on the icon in the bottom part of the web site.Download firmware

The BRI gateway will perform upgrade automatically.

412N TELEKOMUNIKACE a.s., www.2n.cz

4.4 Factory Reset

Should you forget your password or set the IP interface incorrectly, you can reset the factory values. Press the button right to the BRI ISDN connector for a ratherReset long time to reset the default values. Doing so, you reset all the factory configuration values for all the parameters including those related to the Ethernet interface and access data.

Caution

By resetting the default configuration values, you change the Ethernet interface settings and have to reconfigure the gateway subsequently.

Note

Press the button for a short time (0.5 s) to restart theReset GSM gateway.

422N TELEKOMUNIKACE a.s., www.2n.cz

4.5 Basic Configuration – Step by Step

This subsection helps you put your BRI gateway in operation for the first time. Refer to the paragraphs of for more detailed settings.S. 3

Install the GSM gateway as instructed in . Remove the SIM cards orSubs. 2.2 insert the PIN–disabled SIM cards before the first launch. Connect the GSM gateway to the Ethernet to be able to get connected to the address mentioned in , page from the web interface. If the default IP Subs. 4.1 address of your gateway is not suitable for your Ethernet installation, change the IP address setting as follows:

Disconnect the configuration terminal from the Ethernet. Disconnect the GSM gateway from the Ethernet. Get an Ethernet switch or an Ethernet crossed cable. With the crossed cable, interconnect the configuration terminal directly with the GSM gateway. With the Ethernet switch, connect the configuration terminal and GSM gateway to the switch. We do not recommend you to connect any other device. Change the IPv4 setting in your configuration terminal Ethernet settings to, e.g.: IP=192.168.1.200, Net mask: 255.255.255.0 Open your web browser and enter the IP address of your GSM gateway. Complete the factory login data. Change the required settings in the Gateway configuration – Ethernet

section and save the changes into the GSM gateway.configuration Connect the GSM gateway to a standard Ethernet. Rechange the IP settings of the configuration terminal and reconnect the terminal to a standard Ethernet.

Enter the new IP address of your GSM gateway to get connected to the web interface. Set the current time and date for the GSM gateway in the Gateway control –

menu.Date/Time

Check the for 'unlocked' in the Licence status Gateway control –

menu. If the status is not unlocked, your GSM gateway is notFirmware/Licence equipped with the proper licence (refer to ). Contact your dealer for theSubs 4.2 licence key. Set the correct PIN code value in the Gateway configuration – System

menu to meet the PIN code of the SIM cards used.parameters Set new login data in the menu.Gateway configuration – Login configuration Switch off the GSM gateway and insert the SIM cards. Connect the antenna to the GSM gateway and switch the gateway on. The GSM gateway factory configuration allows you to make outgoing calls without any additional programming. All you have to do is set the correct values for the BRI ISDN and VoIP interfaces.

Should you have problems with the gateway functions, follows the instructions below please:

Read the User Manual carefully and check all the parameters. Find answers to your questions at (Frequently Asked Questions).http://faq.2n.cz Contact your servicing centre.

It is recommended that you should attend certified training courses at 2N to be able to install the whole system successfully.

432N TELEKOMUNIKACE a.s., www.2n.cz

5. Introduction to Configuration Interface

This section introduces the configuration interface of the 2N BRI Enterprise / BRI

product. Lite

Here is what you can find in this section:

5.1 Configuration Web Interface

Gateway control Gateway configuration Others

442N TELEKOMUNIKACE a.s., www.2n.cz

5.1 Configuration Web Interface

Essential Data

The web interface supports the following web2N BRI Enterprise / BRI Lite

browsers:

MS Internet Explorer v9

Mozilla Firefox v4 and higher

Any other web browsers may cause troubles. The recommended screen resolution is 1280x1024 and colour quality 32bit and higher. The configuration interface is available in the English language version only at present.

Tip

Use the F11 key to display the full–screen mode.

Enter the server IP address into your web browser to log in to the web configuration interface of your BRI gateway. The following login dialogue will get displayed.

Just one user may be logged in at one time. Refer to , page for access dataSubs. 4.1 default values.

Tip

The one–user limitation applies to the web interface access only. If Telnet is used, ten users may be logged in at the same time.

A time limit is defined for login, which is renewed automatically when thefive–minute

452N TELEKOMUNIKACE a.s., www.2n.cz

user keeps active on the web interface. When this time interval expires, the user is logged out automatically. Click on to restore the maximum time limit.Refresh

Caution

You are recommended to change these default login data upon the first login to increase security of your system significantly.

Web Icons

Caution

Remember to press the button to save theSave settings changes in order to avoid of new data after leaving theloss current configuration window!

[4]

Set the time limit value in the section.Gateway – Web configuration – Auto logout

462N TELEKOMUNIKACE a.s., www.2n.cz

Home Page

Upon login, you get onto the home page (see the figure below) of the section.Gateway There is a menu to the left, divided into the and Gateway control Gateway

items. You can see the current login time counter status and the configuration

button for time limit refreshing in the right–hand upper corner.Refresh The button on the home page is used for user logout. You will be notified ofLogout every successful logout to avoid reuse of your login data. The following sections are located in the upper menu too:

SMS – helps you receive/send SMS messages via the web interface. Utils – contains extended system utensils (Ethernet and internal tracing). Update – helps you download the latest firmware. Restart – helps you execute the software restart of the GSM gateway.

The main window also provides information on the gateway licence status, firmware and bootware versions and BRI gateway Ethernet interface MAC address. You can download a new licence here too.

472N TELEKOMUNIKACE a.s., www.2n.cz

Gateway control

Gateway control helps you:

Monitor the current state of each GSM gateway parts; Check and set the GSM gateway licence; View and save the LOG file and CDR.

Firmware / Licence

Use this window to display information on the gateway licence status, firmware and bootware versions and Ethernet interface MAC address. You can enter a new licence code here.

Firmware version – displays the current firmware version for the GSM gateway connected. Bootware version – displays the current bootware version for the GSM gateway connected. MAC address – shows the MAC address of the GSM gateway Ethernet interface. CPU serial number – shows the GSM gateway serial number in the M203–xxxxxxxxxx.bin format. Active – protocols allowed by the licence:

SIP – SIP support; MExx – Mobility Extension support, where 'xx' means the maximum count of users; G729 – G.729ab voice codec support; DSS1 – ISDN BRI DSS1 protocol support;

TUN – GSM–CSD remote supervision support.

Gateway limitation – displays the gateway operation limit (or licence limitation). Licence status – displays the current licence status (unlocked/locked).

Caution

When the licence code expires, the licence–based protocols will be locked!

Networks – displays the list of allowed/disallowed GSM/UMTS networks.

Tip

Upon the dealer's request, the gateway may be locked against certain types of GSM/UMTS networks. This state is signalled by a red LED Ch 1/Ch 2 and a 'netw–err' cause in the GSM module diagnostic window. Contact your dealer please for more information.

Licence key for gateway – helps you insert a new GSM gateway connection licence.

Caution

By inserting a new licence code you restart the GSM gateway and discontinue all the currently made calls!

482N TELEKOMUNIKACE a.s., www.2n.cz

Date / Time

Use this window to set the current date and time for your gateway. Tick Synchronise

to set the time a date items automatically according to your PC data.with local PC

Caution

The internal power source keeps the internal clock source running for a few hours only! Therefore, check the current gateway date and time after long BRI gateway disconnection!

LOG file

The LOG file helps you read out the gateway LOG file. There are LOG file saving and LOG listing updating icons in the lower part of the window.

Refer to , page for details on LOG records.Subs.7

CDR file

The CDR file helps you read out the gateway Call Data Records (CDR). There are CDR file saving and CDR listing updating icons in the lower part of the window. Refer to

, page for details on the CDR format.Subs 6.6

Caution

The maximum CDR capacity is 962 records. When this value is reached, the oldest records will be deleted automatically!

Module status

The window displays the current status of each GSM/UMTS channel. Refer to ,Subs. 6.4 page for more details.

492N TELEKOMUNIKACE a.s., www.2n.cz

Module control

The window helps you control the selected GSM/UMTS module manually.

Statistics

The window displays the current statistic data on calls. There are LOG file saving and LOG listing updating icons in the lower part of the window. Refer to , page forSubs. 6.7 the statistic data format details.

Current call info

The window displays the currently made calls. There are LOG file saving and listing updating icons in the lower part of the window.

Connection state

The window shows the state of all available configuration sessions. There are LOG file saving and listing updating icons in the lower part of the window.

AutoCLIP routing table

The window displays the current state of the AutoCLIP table. There are LOG file saving and listing updating icons in the lower part of the window.

SIP registration

The window displays the current state of the gateway SIP registration.

ISDN lines

The window shows the state of each ISDN BRI interface of the gateway.

Online report

The window provides online GSM gateway tracing.

502N TELEKOMUNIKACE a.s., www.2n.cz

Gateway configuration

System parameters

General

Saving call data (CDR) – define the call types for which the GSM gateway shall store information in the CDR.

Gateway ID – provides gateway with a numerical code in the CDR in2N BRI

case multiple devices generate CDRs in the network. Number for remote control.

Summer / winter time

Automatically move to summer/winter time – enable automatic GSM gateway system time change for winter/summer time format transition. Date of move to winter time [dd.mm] – specify the day and month for the change. Date of move to summer time [dd.mm] – specify the day and month for the change.

Mobility Extension (DTMF settings)

Start dialling (quick call forwarding) – set the DTMF code for quick call forwarding start. End dialling (quick call forwarding) – set the DTMF code for quick call forwarding end. Hold call – set the DTMF code for the current call holding. Hang up call – set the DTMF code for the current call termination. 'Follow me' activation – activate the function to make the GSMFollow me gateway start routing calls to the defined GSM/UMTS user number. The default value is *55. 'Follow me' deactivation – deactivate the function. The default valueFollow me is #55. 'SMS at no answer' activation – activate the function for aSMS at no answer registered user. The default value is *33. 'SMS at no answer' deactivation – deactivate the function forSMS at no answer a registered user. The default value is #33.

Tip

Activate/deactivate the and SMS at no answer Follow me functions by dialling the above mentioned DTMF access codes into the GSM gateway from a registered mobile user number. You can change the function values via the configuration interface too (see below).

Others

PIN – set the PIN code for the PIN–secured SIM cards.

512N TELEKOMUNIKACE a.s., www.2n.cz

Caution

A PIN–active SIM card with a PIN value other than that set in the GSM gateway configuration will be blocked by the gateway with the 'pin–err' cause. Enter the correct PIN on your mobile phone to unlock the SIM card!

End of dialling (empty=off) – set the DTMF code for DTMF dialling end for DISA incoming calls. The default value is „#".

List of emergency numbers

The window displays a list of emergency numbers, which are normally routed to the BRI interface. If the BRI line is disconnected, the emergency numbers are dialled automatically via any GSM/UMTS module according to the following rules:

Search of a logged–in GSM/UMTS module (regardless of free minutes); Search of a blocked or network searching GSM/UMTS module.

The table includes an exact format of the number to be called (112,911, etc.). The 'x p' laceholder stands for any digit in the number to be called. The ' }'_ placeholder means{ the rest of the number. For example:

Format Allowed numbers

123 123 only

14x0 1400,1410,1420,…1490

999_ All numbers starting with 999

VoIP parameters

VoIP functions

Day of deleting statistics on VoIP (every month) – set the day for automatic deletion of call statistics via the VoIP interface. None = statistics will not be deleted automatically.

SIP protocol settings

Use CLIP from INVITE field – define that CLIP from the 'Contact' or 'From' field shall be used for call routing to GSM/UMTS. Send 180 ringing instead of 183 session progress. Send 200 OK instead of 180/183. Send 200 OK and BYE when rejected from GSM.

Send 200 OK on REGISTER request – virtual registration of device in 2N BRI

gateway (for registration requiring equipment). Replace CLIP from GSM with Caller ID. Deny DTMF according to RFC2833. Forward DTMF for ME.

522N TELEKOMUNIKACE a.s., www.2n.cz

SIP registration

Registration expires [s] – set the expiration time for the gateway2N BRI

registration data with SIP proxy. Reattempt registration [s] – set the time interval after which the request shall be resent. Registration domain (realm). Caller ID. Username – registration data with SIP proxy. Password – registration data with SIP proxy.

Voice parameters

First RTP port (even: 1024 – 65524) – set the number of the first RTP port. The RTP port number must be even according to the recommendation. Last RTP port (even: first RTP+10 – 65534) – set the number of the last RTP port. The RTP port number must be even according to the recommendation. The recommended minimum RTP port range is 10.

Codecs settings

Set details for the G.711a/u or G.729 codecs.

Codecs priority

Set the types of the speech codecs to be preferred.

Priority 1 Priority 2 Priority 3

IP addresses

SIP proxy (IP–>GSM) the SIP proxy IP address from which gateway– 2N BRI

awaits the GSM outgoing call requests.

Tip

If you keep the default values (0.0.0.0), gateway will2N BRI

receive requests from any IP address.

SIP proxy (GSM–>IP) – the SIP proxy IP address to which gateway2N BRI

turns in the case of GSM incoming calls. SIP registrar – SIP registration server IP address. NAT firewall – NAT firewall IP address. STUN server – STUN server IP address (Simple Traversal of UDP through NATs (Network Address Translation)) for obtaining the public IP address with which 2N

gateway operates in the Internet. You are recommended to complete this BRI

field if gateway is installed in a private network separated from the2N BRI

Internet via NAT or firewall. The pre–set port for sending requests to STUN is

3478. Next STUN request (60–6553, 0=off) [s] – update of information on the 2N

gateway public IP address. Use this parameter to configure the frequency of BRI

queries routed to the STUN server.

532N TELEKOMUNIKACE a.s., www.2n.cz

Note

In case the GSM gateway is installed behind the NAT, make proper routing settings in the NAT router for the relevant ports (SIP, RTP, STUN). Integrated firewalls can also affect VoIP calls!

Tip

Should you have call troubles (such as unilateral audibility, connection errors), make sure that all the active elements on the VoIP call route have been set properly. For easy troubleshooting, try the point–to–point connection with the software IP phone (SJ phone, e.g.) in your PC and, at the same time, apply network analyzer tracing (WireShark –

).www.wireshark.org

Refer to for easy tracing by the BRI gateway.Subs 5.1

Tones generated to VoIP

Ring tone to VoIP – enable generation of a user ring tone or transfer of the real ring tone from the GSM/UMTS networks.

ISDN parameters

Use this window to set the BRI ISDN port parameters. The appearance and count of the parameters may be different in and due to 2N BRI Lite

2N BRI Enterprise

different counts of ISDN BRI ports.

BRI mode selection

Mode – set the BRI1 and BRI2 (for only) ports.2N BRI Enterprise

BRI1 and BRI2

TEI Address – set a fixed TEI address for connection of port(s) in the Point–to–Point mode. MTP – activate assignment of the dynamic TEI address (Point–to–Multipoint mode).

Progress indicator value – set the value for each progress element for call setup. Please respect the PBX and PSTN settings to avoid wrong evaluation of messages sent by the BRI gateway and, subsequently, call setup errors. Refer to the table for the decimal numbers to be assigned to the progress messages.

542N TELEKOMUNIKACE a.s., www.2n.cz

Number Meaning

OFF Progress element is not sent in the message

Connection is not end–to–end ISDN, following progress messages will be sent in the speech band

2 Call destination address is not ISDN

3 Call initiator address is not ISDN

4 Call is returning to ISDN

Communication between interconnected systems has lead to a change of the telecommunication service (for end–to–end ISDN connection only)

10 Delay due to speech interface

BRI functions

Day of deleting statistics on BRI (every month) – set this item to '0' to disable periodical (monthly) deleting of statistics. Set this value to 'x' other than '0' to enable deletion of statistic data on x–th day of a month. Digits count in SETUP (en–block) – set the count of outgoing dialling digits to be sent by the gateway in the SETUP message in the ENBLOCK format. The remaining digits will be sent in the OVERLAP format, i.e. in the information element following the SETUP message. The OVERLAP mode is used in analogue networks.

Example:

SETUP digit count: 7, user number: 601234567

Call setup messages:

SETUP (601234567) INFO (6) INFO (7)

Receive dial number from Subaddress – use this parameter to receive dialling from the subaddress element instead of standard CDN. Don't send Connect ACK on TE – use this parameter to enable/disable sending of the CONNECT ACK message to the TE port.

Tone signalling for calls from ISDN

Dial tone to BRI1 with empty SETUP – set the dial tone type to be generated by the BRI gateway. Ring tone – set the ring tone type to be generated by the BRI gateway. Generate busy tone to BRI1 – set the busy tone type to be generated by the BRI gateway into the BRI 1 interface. Generate busy tone to BRI2 – set the busy tone type to be generated by the BRI gateway into the BRI 2 interface.

Numbering plan settings

CDN, CGN – use these parameters to set the for the called (CDN) andNumbering plan calling (CGN) numbers.

552N TELEKOMUNIKACE a.s., www.2n.cz

Binary value Decimal value Description

0000 0 Unknown numbering plan

0001 1 ISDN/Telephony numbering plan

0011 3 Sata numbering plan

0100 4 Telex numbering plan

1000 8 National standard numbering plan

1001 9 Private numbering plan

1111 15 Reserved for Extension

Port modes

This item helps you set each of your gateway ports. The settings are based on the LCR table including relevant routing/rejecting rules for all incoming and outgoing calls.

GSM basic parameters

Number of digits dialled from VoIP

Minimum numbers from VoIP – set the minimum count of digits to be dialled into the GSM network. Maximum numbers from VoIP – set the maximum count of digits to be dialled into the GSM network.

Wait for next digit [s] – set the timeout for gateway to wait for the2N BRI

next digit dialled from VoIP to GSM.

Calls

Relax timeout [s] – set the timeout between the end of the last call and beginning of the next call made via one and the same GSM module (incoming and outgoing calls are rejected during this timeout). The recommended relax value is 2 seconds – please do not change this setting unless absolutely necessary.

Holiday list

List of days on which calls will be routed like on weekends in the LCR.

DTMF settings

Minimum delay between two identical DTMF characters [s/100] received.

Tone detector settings

The GSM gateway can automatically detect user defined tones transmitted by GSM/UMTS for setting up outgoing calls to the GSM/UMTS networks. In general, they are tones of a transferred number. For the purpose of such detection, the GSM gateway automatically terminates the call and tries to set it up via another available outgoing group (if defined in the LCR).

Frequency 1;2;3;4 – define the frequencies for the tone to be detected. Sequence list – set the sequence of the tones to be detected.

562N TELEKOMUNIKACE a.s., www.2n.cz

Voice parameters of GSM modules

Set the voice level in the gateway GSM modules.

Audio level DSP

Set the voice level for calls in the gateway signal processor.

Caution

An extremely high voice level may lead to poor voice quality (distortion, echo, etc.) and wrong DTMF detection!

Tone generated for incoming calls from GSM/UMTS

Dial tone – set the dial tone for incoming calls from GSM/UMTS. Ring tone – set the ring tone for incoming calls from GSM/UMTS. Generate busy tone to GSM/UMTS – enable busy tone generation for call termination.

Caution

If the function is enabled, the duration ofGenerate busy tone outgoing calls billed by the GSM/UMTS provider will be extended!

Error GSM/UMTS causes

Set the ISDN release cause for each of the below mentioned statuses. Every call that meets any of the below mentioned requirements, will be rejected with a user defined cause (the ISDN cause number will be translated to VoIP as a SIP code as defined below).

Lack of digits in OVERLAP mode – any call that fails to meet the minimum

digits count requirement will be rejected.

Restricted number prefix – any call whose prefix is not included in any of

the prefix lists will be rejected.

Selected module / GSM group is not ready – a call will be rejected in case

there is no available GSM module in the selected (by LCR) outgoing GSM

group.

Selected module / GSM groups are not ready – a call will be rejected in

case there is no available GSM module in the selected (by LCR) outgoing

GSM groups.

Cause translation

The release cause received from GSM/UMTS can be converted into another ISDN release cause. The resultant ISDN cause number will be converted into a SIP code according to the table below:

Conversion table:

572N TELEKOMUNIKACE a.s., www.2n.cz

ISDN cause

value

Description

SIP

code

Description

1 Unallocated number 410 Gone

3 No route to destination 404 Not found

6 Channel unacceptable 503 Service unavailable

16 Normal call clearing BYE

17 User busy 486 Busy here

18 No user responding 480

Temporarily unavailable

19 No answer from user 480

Temporarily unavailable

21 Call rejected 603 Decline

22 Number changed 410 Gone

27 Destination out of order 404 Not found

28 Address incomplete 484 Address incomplete

29 Facility rejected 501 Not implemented

31 Normal, unspecified BYE

34 No circuit available 503 Service unavailable

38 Network out of order 503 Service unavailable

41 Temporary failure 503 Service unavailable

Switching equipment congestion

503 Service unavailable

Requested facility not subscribed

503 Service unavailable

47 Resource unavailable 503 Service unavailable

Requested facility not subscribed

503 Service unavailable

Incoming class barred within CVG

603 Decline

57 Bearer capability not authorised 501 Not implemented

Bearer cap, unavailable at present

501 Not implemented

63 Service or option unavailable 503 Service unavailable

65 Bearer cap, not implemented 501 Not implemented

Service or option not implemented

501 Not implemented

87 User not member of CVG 603 Decline

88 Incompatible destination 400 Bad request

98 Invalid message 400 Bad request

102 Recover on timer expiry 408 Request timeout

XXX Other received CAU from netw. 500 Internal server error

582N TELEKOMUNIKACE a.s., www.2n.cz

Others

Text of SMS at no answer – edit the text of the SMS to be sent to the calling party in case of no answer (if the function is active). The %N string will insert the CLIP received from VoIP in the SMS text. Text of SMS for all calls – complete this parameter to make the GSM gateway send SMS to every called party regardless of whether or not the call was successfully connected. The %N string will insert the CLIP received from VoIP in the SMS text. Save received SMS to – select the storage for received SMS messages. SIM card identification – set the SIM Id (IMSI/SCID) to be entered in the CDR. Disable CLIP from GSM/UMTS to VoIP – enable/disable resending of the CLIP from GSM to VoIP. Reject call with CHLD – enable rejection of incoming calls from GSM/UMTS via AT+CHLD (subscriber busy) instead of standard ATH.

GSM group assignment

Here you can assign the GSM/UMTS modules to groups. You can assign incoming and outgoing calls separately using the parameters below.

GSM outgoing groups

2N BRI® gateway allows you to work with two groups of outgoing calls. You can set

different values (call setup, called minutes and sent SMS per period, etc.) for each of them.

General settings

Delay for CONNECT [s] – set the delay between receiving a GSM call and sending the CONNECT message. Minimum ring duration to send SMS at no answer [s] – set the minimum ringing timeout for sending the SMS at no answer.

Note

The INVITE message must contain the called and calling numbers in order that the function maySMS at no answer work properly.

Delay for ALERTING [a] – set the delay before sending the ALERTING message. Minute parameter – define whether the GSM gateway shall consider call duration or count while limiting outgoing calls. Day of deleting statistics in group (every month) – set a day on which statistic data on disconnected calls shall be deleted. Generate virtual ring tone – enable/disable generation of the virtual ringing tone into the VoIP interface. Call length counting – define whether call minutes or seconds shall be counted. BTS lock – identify the BTS to which the GSM modules shall log in. Restart the selected GSM modules to execute the changes.

592N TELEKOMUNIKACE a.s., www.2n.cz

Caution

The BTS lock service work with specific GSM modules only (Q55)! If you set a wrong BTS lock, the selected GSM module(s) will not log in to GSM.

After call relax delay – set the time between the end of the current call and start of the next call via one and the same GSM/UMTS module. The recommended value for heavy–traffic installations is 2 seconds! Add random time – use this auxiliary parameter to add random time in seconds. Thus, the resultant time is the sum of the two above mentioned parameters.

Disconnect call

Set the reasons for immediate discontinuation of an outgoing call to GSM/UMTS.

Send CLIP from VoIP to GSM/UMTS

Transfer CLIP to GSM/UMTS – enable/disable the function. Separating char – define the CDN/CLIP separating character. Modify (‘–’ remove one digit) – change the CLIP. The ‘–’ character is used for deleting one character from the left.

Caution

The service must be supportedSend CLIP from VoIP to GSM by the GSM/UMTS provider's network. Otherwise, the call may be rejected by GSM/UMTS!

Basic settings

Roaming enabled for network code – international code for the roaming enabled network. The code consists of the following two numbers:

MCC – Mobile Country Code – national code (Czech Republic – 230, e.g.)

MNC – Mobile Network Code – GSM network code (T–Mobile 01, O202,

Vodafone 03, e.g.)

Hence, the T–Mobile CZ international code is 23001. Leave the field empty to disable roaming.

String Note

<empty> Roaming disabled

2300 Roaming disabled (five digits at least)

23002 Roaming enabled for the 23002 (MCC+MNC) network

230XX Roaming enabled for the 23000 – 23099 (MCC+MNC) network

XX001 Roaming enabled for the 00001 – 99001 (MCC+MNC) network

XXXXX Roaming enabled for any network

602N TELEKOMUNIKACE a.s., www.2n.cz

Note

Before enabling roaming, please use your mobile phone to make sure that the GSM/UMTS searching priorities have been set properly on the SIM card.

Caution

Calls via a roaming network may increase your telephone call costs!

CLIR – enable/disable presentation of the SIM CLI on the called party's telephone. CLIR is recommended for the SIM card inserted in the GSM module to avoid CallBack problems.

Caution

The and Temporary CLIP enable Temporary CLIR enable services must be supported by the GSM/UMTS provider's network. Otherwise, the call may be rejected by GSM/UMTS!

Maximum number of called minutes – define the maximum count of minutes to be called within a month via the selected SIM card. SMS messages number – define the maximum count of SMS messages to be sent within a month via the selected SIM card. Day of restoring call limit and delete statistics – select a day in a month on which the and statistics shallMax count of called minutes Count of SMS messages be deleted. First count – set the length of the first pulse after which the pulse counting change starts as defined in the parameter.Next count Next count – set the length of one pulse in seconds after the time defined in the

parameter elapses.First count

Note

Set the two parameters above ( , )First count Next count properly to count free minutes on SIM cards correctly. These parameters are used for limiting outgoing calls depending on free minutes. The CDRs contain real data.

Day limit of called minutes – set the maximum count of minutes to be called within a day via the selected SIM card.

Time limits

There are two SIM use time limits in a GSM group.

612N TELEKOMUNIKACE a.s., www.2n.cz

Call tariffs

Use this function to assign up to four independent free minute counters to a group of GSM modules (SIM cards), e.g.:

free minutes for calls to own GSM/UMTS network;Tariff 1 = free minutes for calls to other GSM/UMTS networks;Tariff 2 = free minutes for calls to fixed network;Tariff 3 =

free minutes for calls within a closed user group (VPN).Tariff 4 = Complete the LCR table (assign prefixes to tariffs) properly to make full use of this function. If routing to a tariff is not used, the global free minutes function will be used in the LCR table.

Free minutes Set the free minutes for the tariff offered by the provider. Transferred minutes Set the maximum count of free minutes to be transferred

to the next period. Day of restoring free minutes Set a day on which the free minute counters will be reset automatically. Select every 24 hours, a day in a month, or a day in a week. Week of restoring free minutes Set a week in which the freein month minute counters will be reset automatically. Set the week number only if the restoration takes place in a month, e.g., or keep forevery other Friday Every the other cases.

Caution

The recommended free minute counter value is X–5, where X is the number of free minutes obtained from the GSM/UMTS provider. Thus, you can avoid exceeding limits. The manufacturer is not responsible for additional call costs incurred as a result of exceeding your GSM/UMTS provider's free minute/SMS limit.

GSM incoming groups

2N BRI® gateway allows you to work with two groups of incoming calls. You can set

different values for each of them.

622N TELEKOMUNIKACE a.s., www.2n.cz

General settings

Mode – set how the gateway shall process incoming calls from the GSM network.

Reject incoming calls – all incoming calls from the GSM network are rejected automatically. Ignore incoming calls – all incoming calls from the GSM network are ignored. The calling party hears the check ring tone. Accept incoming calls + voice message – incoming GSM calls are accepted by the gateway and, if programmed so, DTMF with a voice message is activated for them. Accept incoming calls + dialtone – incoming GSM calls are accepted by the gateway and, if programmed so, DTMF with a simulated second dialtone is activated for them. CallBack after ring / Reject – CallBack will be made if the CLIP is included in the CallBack table. The other incoming calls will be rejected. CallBack after ring / Ignore – CallBack will be made if the CLIP is included in the CallBack table. The other incoming calls will be ignored. Report to PC + voice message – the GSM gateway sends information on the incoming call to a PC equipped with call routing application. If programmed so, DTMF with a voice message is activated for the incoming call. Report to PC + dialtone – the GSM gateway sends information on the incoming call to a PC equipped with call routing application. If programmed so, DTMF with a simulated second dialtone is activated for the incoming

call. Minimum digits in DTMF – set the minimum count of digits to be requested by the gateway for DTMF. Maximum digits in DTMF – set the maximum count of digits to be accepted by the gateway for DTMF. Timeout for entering DTMF digits [s] – set the timeout for which the GSM gateway shall wait for the first/next DTMF digit. If you select '0', the incoming call will be automatically connected to the numbers included in the List of called

.numbers Day of deleting GSM group statistics – set a day in a month on which the incoming call statistics shall be deleted. Prefix before DISA – set a numerical prefix to precede DTMF. CLIP – use this parameter to modify the incoming CLIP from GSM/UMTS. For international codes, '+' will be removed automatically. Use '–' to remove a digit. Examples (CLIP in GSM: +420600123456):

Parameter

CLIP to VoIP/PRI 1

Note

Null 420261301500 No CLIP change

+ +420261301500 Add + before CLIP

00 00420261301500 Add 00 before CLIP

– 0261301500 First two digits removed from CLIP

–––99 99261301500

First three digits removed from CLIP, prefix 99 added

632N TELEKOMUNIKACE a.s., www.2n.cz

Looping of voice message – set the voice message playing time.

Send CLIP from GSM/UMTS to VoIP

Transfer CLIP from GSM/UMTS – enable/disable the function. Separating char – set the separator for the SIM card CLIP and ID of the extension to be called. Modify – modify the extension ID.

Caution

The service must be supportedSend CLIP from VoIP to GSM by the GSM/UMTS provider's network. Otherwise, the call may be rejected by GSM/UMTS.

Others

Time to keep CLIP in table – set the record keeping time for AutoCLIP routing. Add record only for unconnected call – enable storing of unconnected outgoing calls in the AutoCLIP table only. Delete record for connected answer – enable deletion of an AutoCLIP record in the case of successful CallBack. Skip DTMF for numbers not in CLIP Routing table – enable this option to set DTMF to the incoming calls only whose CLIP is included in the CLIP Routing table. Skip list of called numbers after failed call to wanted number – enable this function to disable forwarding of incoming calls to the numbers included in the

if rejected after DTMF.List of called numbers Auto end to CallBack request – enable that the incoming call whose CLIP meets the CallBack settings will be rejected. If not, the call will be ignored. The CallBack function will be retrieved after call end in both the cases.

List of called numbers

List of numbers to be dialled if DTMF dial–in was not made.

Prefixes

Use this window to adapt the gateway to calling to various GSM providers' networks. Set the call routing rules based on prefixes for up to eight groups.

Prefix list 1–8

Eight prefix groups to be assigned in the LCR table.

Basic settings

GSM network ID – set the prefix list user code for easier orientation in the LCR. Default count of digits – default length of the number to be dialled into the GSM/UMTS networks for routing via the selected prefix list. Use this parameter in case the is not included in the table.Digits count Accepted prefixes

642N TELEKOMUNIKACE a.s., www.2n.cz

Table of replaced prefixes

Use this table to replace the prefix of the received number ('00' with '+', e.g.). You can only add or remove the prefix. This change is made before the prefix is searched for in the prefix table. Be sure to keep the „/" record in the table for a proper function.

Table of accepted prefixes

List of prefixes of called destinations to which the selected prefix list applies.

LCR table

The Least Cost Routing (LCR) table helps you route calls according to the called party number, time and days in a week.

Prefix list – prefixes to be used for a selected LCR row. Time limitation – time validity limitation for a selected LCR row. Weekend usage – enable/disable a row on weekends. Maximum length of call – set the maximum duration (minutes) for an outgoing call to the GSM/UMTS network. Groups – outgoing GSM groups used for the selected LCR row. Tariffs – select the tariff group (free minute counter) to be used for the outgoing call. Refer to the subsection for details.GSM outgoing groups Ignore tone detection in last group – having detected a user defined tone (refer to ), the GSM gateway automatically terminates the call andGSM basic settings seeks for another call setup way. If this parameter is activated, the GSM gateway ignores the tone detection results and sets up a call when this is the only possible call establishing way.

Note

If you use tariff routing, set the tariffs properly in the GSM

subsectionoutgoing groups

CLIP routing table + CallBack

Use the table to set a fixed CLIP assignment of incoming CLIPs from GSM to the numbers of extensions to which incoming calls are routed automatically. Also, set the CLIP list in the GSM network for which CallBack is enabled.

GSM number (CLIP) – user Id in GSM/UMTS. Autodial – enable/disable CLIP routing for the selected CLIP. Dial to VoIP – VoIP destination number for the CLIP routing function. Auto CallBack – enable/disable CallBack routing for the selected CLIP. Limit – set the maximum call duration (minutes).

Note

Remember to activate the CallBack mode in the GSM incoming

for a proper function.groups

Mobility Extension

Use this table to register the Mobility Extension users.

Name – user name for calling to VoIP.

652N TELEKOMUNIKACE a.s., www.2n.cz

User – registration user name for VoIP. Password – registration user password for VoIP. GSM number (CLIP) – user SIM card CLIP. Follow me function – enable/disable call forwarding to the user mobile station (according to CLIP). SMS at no answer function – enable/disable sending of SMS on missed calls.

Ethernet configuration

Use this window to set the gateway Ethernet interface.

Use DHCP – enable/disable the DHCP client function for gateway.2N BRI

IP address – fixed IP address (v4) for the gateway Ethernet interface.2N BRI

Subnet mask – network mask for the gateway Ethernet interface.2N BRI

Default gateway – IP address (v4) of the IP gateway in the Ethernet.

Caution

Saving wrong values, e.g. DHCP enable, may result in making the gateway configuration part inaccessible. In that2N BRI

case, reset the GSM gateway to factory values; refer to

.Subs.4.1

Tip

If the gateway is in the DHCP client mode, the current values obtained from the DHCP server are displayed in the IP address, Subnet mask and Default gateway items.

Use this window to set the access password and name for the gateway web2N BRI

interface. Use the same access data for Telnet connection too.

Caution

Change the user name and password during your gatewayfirst

configuration to avoid unauthorised access to your gateway configuration!

Web configuration

Set additional parameters for web access to the GSM gateway.

Auto logout – set the count of minutes in which the user will be logged out automatically. Enable web session lock – one Admin user may be connected to the GSM gateway at one time. If another duly authorised user tries to log in, the preceding session will be terminated automatically. If you activate this function, no automatic logout will occur and any other access attempts will be blocked. Simple login form – activate this item to change the graphic appearance of the login window into an anonymous look. This function is recommended for direct connection of the GSM gateway to the Internet. Use SMS user for SMS operations on the web – enable/disable a user authorised to send/receive SMS messages only.

662N TELEKOMUNIKACE a.s., www.2n.cz

SMS user name/password – connect a user with the right to receive/send SMS only.

Report configuration

Use the window to set details for automatic tracing generated by the GSM gateway.

672N TELEKOMUNIKACE a.s., www.2n.cz

Others

Configuration backup

Configuration download

Use this window to download the current BRI gateway configuration. The saved file has the following format: CFG–M202–gateway_serial_number–rrrrmmdd–hhmmss.tar

Configuration upload

Use this window to upload new configuration to the BRI gateway. The Ethernet interface values and access data remain unchanged!

Warning

Upload a well–known configuration file intended for the selected GSM gateway to avoid GSM gateway error and subsequent factory restart.

Documentation

Download the User Manual saved in the gateway.

Caution

The User Manual version will not change during the gateway firmware upgrade. Click on the link to for the latestwww.2n.cz User Manual version!

Utils

This section provides extra functions of the GSM gateway. At present, the GSM gateway offers the Ethernet interface tracing (Network trace) and gateway communication tracing functions. These functions help detect gateway installation troubles (SIP communication debugging). The file format is PCAP, which is readable in the Wireshark ( ) program, for example.http://www.wireshark.org/

Update

This section helps you upgrade your GSM gateway firmware. Select the BRI–xx.xx.xx.bin files only. Refer to Subs 4.3

Warning

Use the for this GSM gateway type only tofirmware certified avoid to your system!irreversible damage

When the new firmware file has been uploaded successfully, the GSM gateway will be restarted automatically.

682N TELEKOMUNIKACE a.s., www.2n.cz

Restart

This section provides forced restart of the BRI gateway connected.

692N TELEKOMUNIKACE a.s., www.2n.cz

6. Configuration Via Terminal

Communication with the gateway is via the LAN. This2N BRI Enterprise®/ BRI Lite connection provides uniform gateway configuring by AT commands. Here is what you can find in this section:

6.1 LAN Communication Setting

6.2 GSM Gateway Behaviour

6.3 List of Terminal AT Commands

6.4 Status Messages

6.5 LOG Files

6.6 Call Data Records (CDR)

6.7 Statistics - Description

702N TELEKOMUNIKACE a.s., www.2n.cz

6.1 LAN Communication Setting

First set the IP address to communicate with the gateway via your2N BRI gateway LAN successfully. To do so, configure the Ethernet interface; refer to . Use anySubs.4.1 of the available programs (HyperTerminal, Telnet, Putty, etc.) for communication and configuration with the following data:

IP address:address set by you Port:23 (Telnet)

712N TELEKOMUNIKACE a.s., www.2n.cz

6.2 GSM Gateway Behaviour

The gateway behaves as an ANSI terminal with echo. Commands are entered in the text format. Upon login, the gateway reports itself with . If not, enter the commaOK at nd and press <ENTER>. A correctly connected gateway should answer . In suchOK case, the gateway starts communicating with a dialogue shown in the figure below. Enter the user name, press <ENTER> and, when being asked so, enter the access

.Password

722N TELEKOMUNIKACE a.s., www.2n.cz

6.3 List of Terminal AT Commands

By default, all these commands start with AT. (Note: Some of the AT commands listed below may not be available in the current firmware versions.)

Basic AT Commands

The following command list is intended for all GSM gateways from that are based2N

on the same SW architecture. Some of the AT commands may be inaccessible for the BRI gateways.

A/ ...repeat last command (without AT)

I3 ...copyright & firmware

I4 ...serial number

&FRES ...factory defaults & reset

&V ...view active parameters (system)

&VI ...view active parameters (isdn)

&V0 ...view active parameters (common)

&V# ...view active parameters (modules 1..2)

&V9 ...view active parameters (inc. groups)

&VALL ...view all group parameters

&P ...view pseudo params

&N# ...view network params (net 1..8)

&NALL ...view all network params

&A ...view autorouting table <SPACE...continue>

&R ...view lcr–routing table <SPACE...continue>

&T ...view bris + modules totals

&TMOD ...view all modules totals

&G##=atcommand ...send at command to module 0..1 (ended by OK from gsm)

&G##=xtcommand

...send at command to module 0..1 (ended by <CR> from user)

&G##=cmd

...cmd for module 0..1 (RESET,BLOCK,OFF,DOWN,ON), (ATBAUD)

&GALL=cmd ...cmd for module 0..1 (RESET,BLOCK,OFF,DOWN,ON)

&S ...view aux, bris, modules status

&S## ...view aux, bris, one module status (ax,px,ex,0..1)

&S=info ...view all modules selected info (by at&S##)

&Q## ...view signal quality on module 0..1

&QALL ...view signal quality on all modules

&L ...view logfile from recent <SPACE...continue>

&C ...view buffer (calls) from recent <SPACE...continue>

732N TELEKOMUNIKACE a.s., www.2n.cz

&CR ...read buffer from the oldest <#...erase & continue>

&BSYS=cmd ...cmd for system (RESET)

&XG ...view conn table/gsm (call states)

(&XG## ...view call details for gsm channel)

&M0 ...disable ansi colors

&M1 ...enable ansi colors

&M9 ...start matrix

&U ...view logged users

&I##

...view gsm moninfo (dBm = signal level whn registering with BTS,

RxLEV = minimum signal level required by BTS for registering of GSM module)

Configuration AT Commands

System Settings

%S85=sms ...no answer sms text (max 63 chars)

%S90=mode ...operating mode of GSM module allocation

(0=cyclic mode, 1=locked mode, 2=smart mode – according to already called minutes)

(for 0 and 2 set LCR group = 3 (any))

%S91=buf,id

...cdr mode (b0=outg, b1=inc, b2=failed, b3=moninfo)

unit id (0=off, 1..255)

%S92=rep ...report mode (b0=states, b1=tstamp, b2=smp,

b3=lay2, b4=select)

%S98=pin ...sim pin (max 7 digits)

%S99=dd.mm.yy.w/hh:mm:ss ...set date/time (w=1..7 day of week)

%X10=tsec ...external routing tout in sec/10 (5..60,255)

%X20=mmdd,mmdd

...date of hour+1,hour–1 time change (0=off,0101..1231)

%X22=hh:mm

...0:01..23:59 – time of reset of GSM gateway, 0:00 – no reset

%X80=login/pass ...login name / password (max 15 chars all)

System Control

AT&Gxx=RESET Reset of GSM module No xx

AT&Gxx=BLOCK Block of GSM module No xx

AT&Gxx=DOWN Transfer of GSM module into the sleep mode

AT&Gxx=ON Transfer of GSM module into the idle mode

742N TELEKOMUNIKACE a.s., www.2n.cz

ISDN Settings

%I00=xxx ...pri1 protocol/mode:

NT,TE,NT/S,NTNT (pri2 = TE,NT,SY,NT)

For FW:2_03_15 only NT and NT/S (sync received from TE port)

%I01=tei,mtp tei,mtp = 0..63,0 ….fixed tei,ptp

tei,mtp = 64,0 ….dynamic tei,ptp

tei,mtp = 64,1 ....fixed tei,mtp

%I05=c1,c2,c3,c4 ...cause codes for failed calls

c1=dial timeout (TIMEOUT=120)

c2=dis.prefix (REJECT=21)

c3=req.mod/grp not ready (TEMPFAIL=41)

c4=pref grps not ready (CONGEST=42)

%I06=sack,proc,prog,ale ...prog.elem (0=off,1..8) for isdn message

%I07=opx/npx,... ...list of old/new prefixes (max 47 chars)

%I08=dial,ring,disc

...dial (0 = off,1..255) dialtone to NT on empty SETUP, ring (0=off,1 ..255) ringtone to NT if no PROGRESS from PSTN

– 1=EU (dial = constantly 425Hz,ring = 1000+4000msec 425Hz) – 2=CZ (dial = 300/300/600/1200msec 425Hz,ring = 1000+4000msec 425Hz) – 3=HU (dial = constantly 425Hz,ring = 1000+4000msec 425Hz) – 4=GB (dial = constantly 425Hz,ring = 400+200+400+2000msec 400+450Hz)

disc(0=off,1..255) busy tone to NT interface on DISCONNEECT

%I09=day,bits,enb ...day (0=off,1..31) of clearing pri stat

ctrl bits (b0=not defined, b1=not defined ,b2=subaddr–recv, b4=don't send CONNECT_ACK in TE mode)

enblock digits (0=overlap,1..20)

%I11=xxx ...dial for dig.call from pri1 (max 15 chars)

%I21=xxx ...dial for dig.call from pri2 (max 15 chars)

%I127=msn ...MSN number for TE mode

%i28=pin (max 15chars) ...PIN (password) for TE–>GSM calls

GSM Settings

%G02=mode,atms,afms ...tc35 mode (2,4)

atms/afms gain (+5dB=3,+2.5dB=1,0dB=0,–2.5dB=2,–5dB=4)

752N TELEKOMUNIKACE a.s., www.2n.cz

%G05=delay ...dtmf space delay (1..99 sec/100)

%G06=mmdd,..mmdd ...holiday list (0101=1st jan, 1231=31st dec)

%G07=mmdd,..mmdd ...holiday list2

%G08=delay,min,max,tout ...gsm call delay (0..10 sec), dial min/max (0..20)

dial tout (0..20 sec)

%G09=bits,dial,ring ...bit0=sim card number (0=imsi,1=scid)

bit1=siemens connecting tone,

bit2=don't send CLIP for calls BRI<–GSM

bit3=send AoC for calls BRI–>GSM (functionless for FW>2.03.14 and lower)

dial (0=off,1..255) dialtone to GSM, ring(0=off,1..255) ringtone to GSM if no PROGRESS from PBX

– 1=EU (dial = constantly 425Hz,ring = 1000+4000msec 425Hz) – 2=CZ (dial = 300/300/600/1200msec 425Hz, ring = 1000+4000msec 425Hz) – 3=HU (dial = constantly 425Hz, ring = 1000+4000msec 425Hz) – 4=GB (dial = constantly 425Hz,ring = 400+200+400+2000msec 400+450Hz)

%G101=old/new,... ...gsm causes change table (0..8 causes)

%G#1=netid,clir,min,smsday,sec,sec2,pseudo

...out.module 1..2, sim 1 params

netid (7 chars), clir (0=netw,1=on,2=off)

min (0=0ff,1..65535 minutes), sms (0=off,1..65535)

day (0=off,1..31,32=everyday), sec/2 (1..250)

pseudo (0=off,1..8)

%G#9=ale,conn,disc,day,bits,nasms

...alerting tout (0=off,1=send ALERTING on recieveng +CIEV form GSM network, 2..20sec after recieving PROCEEDING)...alerting tout (0=off,1=send ALERTING on recieveng +CIEV form GSM network,2..20sec after recieving PROCEEDING)

conn delay (0..20sec),

forced disc (bit0=sim limit, bit1=time limit, bit2=noale)

day (0=off,1..31) of clearing group stat,

bits 0..255, b0=(notused), b1=min––>calls, b2=(notused)

b3=(notused),

nasms tout (0=off, 1..20sec)

%G9#=mode,min,max,tout,day,dial,clip

762N TELEKOMUNIKACE a.s., www.2n.cz

...inc.module 1..2 params

mode (0=reject,1=ignore,2=ok–message,3=ok–tone)

mode (4..7=0..3 + autocallback, 6..7= + ext.callback)

min(0..20), max(0..20) tout (0..20 sec) dtmf dial–in

day (0=off,1..31) of clearing inc.group stat

dial prefix (max 15 ch), clip prefix (max 7 ch)

%G9#=xxx,xxx,...xxx

...auto dials (max 63 chars) #=5..8 for inc.groups

1..4

%G99=exp,bits ...dynamic clip expire (0=off,1..240 hours)

bit0=add.conn, bit1=rem.answ

%G19#=mess ...params #=1..4 for inc.groups 1..4

mess duration (0=once, 1..99=repeated) minutes

Network List Parameters

%N#0=opx/npx,... ...list of old/new main–prefixes (max 47 chars)

%N#1=pref/dig,... ...list of prefixes/digits–to–end (max 63 chars)

%N#2=pref/dig,... ...pref. list extension (max 63 chars)

%N#3=pref/dig,... ...pref. list extension (max 63 chars)

%N#4=pref/dig,... ...pref. list extension (max 63 chars)

%N#5=pref/dig,... ...pref. list extension (max 63 chars)

%N#6=pref/dig,... ...pref. list extension (max 63 chars)

%N#7=pref/dig,... ...pref. list extension (max 63 chars)

%N#9=netid,max ...network id (7 chars), default max digits (0..20)

772N TELEKOMUNIKACE a.s., www.2n.cz

Routing Parameters

%A##=clip,dial,limit ...set autorouting item (ix 0..95)

clip (20), dial(20), limit(0=off,1..99 minutes)

%R##=net,hh:mm/hh:mm/w+–,groups,lim ...set lcr–routing item (ix 0..63)

net (1..8), groups = (max 7 chars=1..3,9), 3=any module, 9=bri2

call limit (0=off, 1..99min)

last LCR table line must be empty

; totals

; first m,c,s ...inc. minutes,calls,smses

; second m,c,s ...out. minutes,calls,smses

; ri,ro ...redirected inc,out calls

%TB#=m,c,m,c

...init minutes,calls in bri # (0..65535)

%TBALL=m,c,m,c

...init minutes,calls in all bris (0..65535)

%TG#=m,c,ri,ro

...init minutes,calls,rin,rout in group # (0..65535)

%TGALL=m,c,ri,ro

...init minutes,calls,rin,rout in all groups (0..65535)

%TI#=m,c

...init minutes,calls in inc.group # (0..65535)

%TIALL=m,c

...init minutes,calls in all inc.groups (0..65535)

%T##=1,m,c,s,m,c,s

...init minutes,calls,sms in mod ##, sim 1 (0..65535)

%TALL=1,m,c,s,m,c,s

...init minutes,calls,sms in all mods, sim 1 (0..65535)

Tracing Commands

AT!RE Start tracing of error messages active interface.

AT!Lx

Start tracing of LAN & Telnet on layer xx=2 – Layers IP,TCP,Telnet x=3 – Layers TCP, Telnetx=4 – Layer Telnet

AT!Rx

Start tracing of ISDN BRI & GSM on layer xx=1 – Layers 1,2,3,4x=2 – Layers 2,3,4x=3 – Layers 3,4x=4 – Layer 4

AT!RR Start tracing (AT!R2) to COM1 interface

AT!RX Stop tracing (AT!R2) to COM1 interface

782N TELEKOMUNIKACE a.s., www.2n.cz

SMS Processing

SMS Sending/Receiving Commands

AT!G=A6

Start low–level controlling for SMS (can run only on one port)

AT!G=55 Stop low–level controlling on used port

Control SMS

AT^SX=ch

…(sms listing) request to list all SMS messages and status confirmations saved on SIM card. Possible answers:: *smserr (busy,list) or *smsinc (ix=1..255) for each saved SMS or status SMS messages, end of list or empty SIM card – *smsinc (ix=0).

AT^SR=ch,ix

…(sms read) request to read SMS or status SMS saved in SIM card. Possible answers: *smserr (busy,read) or *smspdu

AT^SD=ch,ix

…(sms delete) request to delete SMS message (or status SMS message). Possible answers: *smserr (busy,delete) or *smsdel

AT^SM=ch,len,pdu,csum

…(sms to module) request to send message via GSM module 0..31 or via any GSM module (ch=32). Possible answers: *smserr (busy,write) or *smsout

AT^SG=grp,len,pdu,csum

…(sms to group) request to send SMS message via GSM group 1..8. Possible answers: *smserr (busy,write) or *smsout

SMS from BRI GSM Gateway

*smsinc: ch,ix,sts

… SMS message was received and saved into SIM card: Ch…GSM module number 0..31 Ix…index number of saved SMS 0..255 Sts…SMS status

*smsrep: ch,ix

…SMS status confirmation was received and saved to SIM card (this message is only for GSM modules TC35 and GM47)

*smsout: ch,ix,ref

…SMS message was sent and was not saved into SIM card: Ref…reference number of sent SMS 0..255 (will be used in SMS status confirmation message)

*smspdu:

ch,ix,sts,len,pdu,csum

…content of SMS message or status confirmation: Len…SMS length (number of bytes in PDU) Pdu…message content in PDU format Csum…Checksum of all PDU bytes (2 hexa digits) calculated without carry

*smsdel: ch,ix

SMS message or status confirmation was deleted from position ix

792N TELEKOMUNIKACE a.s., www.2n.cz

6.4 Status Messages

ISDN Layer 1 Message Status

ID Name Description

0 DEACT Deactivation – no signal received

1 ACTIVE Activation – full synchronisation achieved (frame,multiframe,crc)

2 SIGNAL Signal received – no synchronization

3 SYNC Signal received – only partial synchronization (frame)

ISDN Layer 2 Message Status

ID Name Name acc. to ITU–T Q.921

0 NOTEI TEI Unassigned

1 AWTEI Assigned Awaiting TEI

2 AWTEST Establish Awaiting TEI

3 OKTEI TEI Assigned

4 AWEST Awaiting Establishment

5 AWREL Awaiting Release

6 OKEST Multiple Frame Established

7 TIMREC Timer Recovery

802N TELEKOMUNIKACE a.s., www.2n.cz

ISDN Layer 3 Message Status

ID Name

Name acc. to

Q.931

Description on NT

interface

Description on TE

interface

0 NULL Null

Rest status, ready for call

1 CINIT Call Initiated Call from BRI indicated Call to BRI started

2 OVSEND Overlap Sending

Gradual dialling receiving

Gradual dialling sending

3 OPROC

Outgoing Call Proceeding

Dialling from BRI terminated

Dialling to BRI terminated

4 CDELIV Call Delivered Call from BRI ringing Call to BRI ringing

6 CPRES Call Present Call to BRI started

Call from BRI indicated

7 CRECV Call Received Call to BRI ringing Call from BRI ringing

8 CONREQ Connect Request Call to BRI answered

Call from BRI answered

9 IPROC

Incoming Call Proceeding

Dialling to BRI terminated

Dialling from BRI terminated

10 ACTIVE Active Connected call

11 DISREQ

Disconnect Request

End of call from BRI End of call to BRI

12 DISIND

Disconnect Indication

End of call to BRI End of call from BRI

19 RELREQ Release Request Channel release request

25 OVRECV Overlap Receiving Gradual dialling sending

Gradual dialling receiving

61 RSTREQ Restart Request

Channel restart request sent

62 RSTART Restart

Channel restart request received

Management Message Status

ID Name Description

0 INIT Initialization upon BRI reset

1 IDLE Activation – rest status, necessary for layers 2 and 3

2 DISC Deactivation

812N TELEKOMUNIKACE a.s., www.2n.cz

GSM Layer Statuses

GSM Layer 2 Message Status

ID Name Description Follows

0 INIT GSM module initialization start PINREQ

1 SIM0 Module switch to internal SIM card INIT

2 PINREQ Module PIN request PINSET

3 PINSET PIN value sensing to module INFO

4 BLOCK

Module blocked temporarily or permanently (see Layer 2 information)

INIT

5 SETUP Module configuration running IDLE

6 SLEEP Module sleep running (transition to BLOCK status) BLOCK

7 NWAIT Awaiting GSM log–in SETUP

8 IDLE

Rest status, can start/receive call, execute AT&G command

CALL/CMD

9 CALL Call running (call establishing, connected call, call end) IDLE

10 CMD Communicating with module upon AT&G command IDLE

13 INFO Information loading from module and SIM card NWAIT

GSM Layer 2 BLOCK Message Status

ID Name Description

41 (block)

Blocked by AT&G command, terminated by module, board or system reset

42 Netw–reg

GSM log–in refused (not activated SIM), next attempt in 5..60 minutes

43 Clir–err CLIR activation request refused, next attempt in 2..10 minutes

44 Mod–err

Defective or not connected GSM module, next attempt in 2 minutes

45 Pin–err Wrong PIN, permanently in BLOCK status

46 Sim–err Defective or not inserted SIM card, next attempt in 2 minutes

47 Log–out Temporarily logged–out according to parameter X00

48 Puk–req SIM card requires PUK

(undef) This position of SIM card wasn't checked by gateway

822N TELEKOMUNIKACE a.s., www.2n.cz

GSM Layer 3 Message Status

ID Name Description

0 NULL Rest status, ready for call

1 CINIT Request of call to GSM (from Layer 4)

3 OPROC Call to GSM is connected

4 CDELIV Call to GSM is ringing

6 CPRES Indication of call from GSM (from Layer 2)

7 CRECV Call from GSM is ringing on ISDN interface

9 IPROC Call from GSM is processed by ISDN interface

10 ACTIVE Connected call

11 DISREQ Disconnection request (to Layer 2)

12 DISIND Indication of disconnection (from Layer 2)

19 RELREQ Module release for another call (to Layer 2)

25 OVRECV Reading of DTMF dialling from GSM (from Layer 2)

38 RELIND Indication of module release (from Layer2)

Layer 4 Message Status

ID Name Description

0 NULL Rest status, ready for call

1 MORE

Call request received from GSM or ISDN, awaiting further dialling or timeout

2 SETUP Call request sent to opposite interface

3 PROC Call request confirmed, awaiting call answer

4 ACTIVE Connected call

5 DISC Call disconnection in progress

832N TELEKOMUNIKACE a.s., www.2n.cz

Command Shell Statuses

Command Row Message Status

ID Name Description

0 IDLE Rest status, awaiting AT commands

1 REQUEST

Communication with GSM module upon AT&G command is displayed

2 REPORT Active tracing

3 LOGFILE Content of log file is being written out

4 CALLFILE Content of call file is being written out

5 CALLREAD Call file records are read

6 AUTOFILE Content of incoming call autorouting chart is being written out

7 QUERY (not used so far)

8 SCREEN (not used so far)

9 MATRIX Active matrix screensaver

10 FUNCFILE Content of debug file is being written out

11 LCRFILE (not used so far)

Telnet Message Status

ID Name Description

0 LOGOUT User logged–out

1 LOGIN User is entering name

2 PASSW User is entering password

3 IDLE User logged–in

Records of Events and Calls

Records on Events and Calls

ID Name Description

0 POWER System power on, power off or reset

1 INIT Initialization of EEPROM (configuration) or flash (upgrade)

3 SYSERR System error (memory error, etc.)

8 L1–ERR BRI port layer 1 error (ISDN1)

9 L2–ERR BRI port layer 2 error (ISDN2)

10 L3–ERR BRI port layer 3 error (ISDN3)

12 G2–ERR GSM module layer 2 error (gate2)

13 G3–ERR GSM module layer 3 error (gate3)

14 C4–ERR Link layer error (call4)

842N TELEKOMUNIKACE a.s., www.2n.cz

Types of CDRs

ID Name Description

0 I–FD Not connected incoming call attempt

1 I–OK Connected incoming call

8 O–FD Not connected outgoing call attempt

9 O–OK Connected outgoing call

852N TELEKOMUNIKACE a.s., www.2n.cz

6.5 LOG Files

Table of LOG Events:

Type Text Description

POWER [Power on] System switched on

[Power off] System switched off

[Warm boot] Restart of system, unknown cause

[Watchdog] Restart of system by watchdog

[BKPT code] CPU error: break code detected

[Stack error] CPU error: stock integrity failure

[Divided by zero]

CPU error: dividing by zero

[RETI code] CPU error: illegal using of instruction reti

[NMI intr] CPU error: wrong interrupt

[VOID intr] CPU error: wrong interrupt

[Upgrade reset] Start of upgrade firmware procedure

[Software reset]

Reset by AT commands (at&fres…)

INIT Eeprom Initialisation of eeprom (configuration)

Flash Initialization of flash memory (firmware)

HW–ERR

(##…address of chip, RD…read value/WR…expected value)

Duart #####,RD/WR

Error in initialization of serial controller on GSM board

SYSERR

User stack error!

SW error: stock integrity failure

BRDIN #08 TYP STS the board inserted (number of gsm board, type, status)

BRDOUT #08 TYP STS the board disconnected

BRDRES #08 TYP STS Reset the board by AT command

ALL GSM RESET CMD

Reset of all GSM boards by AT command

SYSTEM RESET CMD

Reset of system by command at&bsys

L1–ERR (reserved)

L2–ERR Error of 2. ISDN layer by Q.921

A: unsol.RX(F) Received packed RR,RNR,REJ with unexpected bit F=1

B: unsol.DM(F) Received packed DM with unexpected bit F=1

C: unsol.UA(F) Received packed UA with unexpected bit F=1

D: unsol.UA(–) Received packed UA with unexpected bit F=0

E: unsol.DM(–) Received packed DM with unexpected bit F=0

862N TELEKOMUNIKACE a.s., www.2n.cz

F: peer re–est Received packed SABME in status OKEST

G: repeated SABME

Repeated unsuccessful send of packet SABME

H: repeated DM Repeated unsuccessful send of packet DM

I: failed (TIMREC)

Unsuccessful breaking–up of status TIMREC

J: N(R) error Received wrong value N(R) – numbering of packets

K: recv.FRMR Received packed FRMR (information about error)

L: undef.frame Received unknown type packed

M: (I field) Received wrong I–packet (numbered packet)

N: frame size Received packed with wrong length

O: N201 error Value N201 was exceeded (max. length of packet)

L3–ERR

tout sts # (p##)

Error of 3. layer isdn: timeout in status # on channel p##

G2–ERR

ATD/ERROR init (g##)

Error of 2. layer isdn: restart of module g## after rejected command ATD by GSM network

GSM Cause 150 (g##)

Error of 2. layer isdn: restart of module g## after cause 150 was received (call barred by GSM network)

G3–ERR

tout sts # (g##)

Error of 3. layer isdn: timeout in status # on module g##

C4–ERR

tout sts # (p##/g##)

Error of 4. connecting layer: timeout in status # on call between channel p## and GSM module g##

872N TELEKOMUNIKACE a.s., www.2n.cz

6.6 Call Data Records (CDR)

18.08.10/15:55:17 O–OK CAU–016 p01/g00 GRP–31 0:17 000:13 00000.00 72015573

1/2300300255266242 1111

Column 1 – **

call date and timeColumn 2 – call statusColumn 3 –

I–FD : failed incoming call I–OK : successfully connected incoming call O–FD : failed outgoing call O–OK : successfully connected outgoing call

Column 4 – release cause sent to ISDN

used B–channel number / used GSM moduleColumn 5 – used GSM group (C=CallBack)Column 6 – connection timeColumn 7 –

– call duration mmm:ss (max. 255:59), or error cause for unconnected callColumn 8

9 – call cost (to be implemented in higher firmware versions) / gateway IDColumn

(optional)

10 – called party number (CDN)Column

– calling party number (CGN)Column 11 Column 12 – SIM card slot number / SIM card IMSI or SCID (Siemens GSM modules only)

882N TELEKOMUNIKACE a.s., www.2n.cz

6.7 Statistics - Description

The GSM gateway automatically generates statistic data on all outgoing and incoming calls. These data can be deleted on the user level or though configuration (automatic deletion on a selected day).

Explanation of columns

PRI/grp – call type

Reset – last restart date

Minutes – count of call minutes

Calls – count of calls

Reject – count of rejected calls (if no GSM module was available, the call will be

rejected with cause 41(42))

Failed – count of failed calls (rejected by GSM)

C.offs – count of unconnected calls (rejected by called user)

Errors – count of errors (wrong request – prefix to be dialled, etc.)

Red.in – count of successful calls (forwarded to this GSM group)

Redout – count of successful calls (forwarded to another GSM group)

Smses – count of sent SMS messages

Statistics of outgoing and incoming groups

[ Total statistics ]

network (reset) minutes hhhh:mm:ss calls reject failed c.offs errors

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

#bri1 inc (0.00) 2 0:02:21 10 4 4 18 0

#bri2 inc ( 0.00) 0 0:00:00 0 0 0 3 0

network (reset) minutes hhhh:mm:ss calls reject failed red.in redout

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

#bri1 out ( 1.12) 0 0:00:07 3 0 0 0 0

#bri2 out ( 1.12) 0 0:00:00 0 4 0 0 0

module (reset) minutes hhhh:mm:ss calls reject failed c.offs smses

892N TELEKOMUNIKACE a.s., www.2n.cz

#mods inc ( 0.00) 0 0:00:07 3 0 0 1 0

#mods out ( 0.00) 2 0:02:32 11 0 4 9 0

[ End of Total statistics ]

Statistics of incoming calls on all GSM modules

[ Module statistics ]

module (reset) minutes hhhh:mm:ss calls reject failed c.offs smses

#g00 i nc ( 0.00) 0 0:00:07 3 0 0 1 0

#g01 i nc ( 0.00) 0 0:00:00 0 0 0 0 0

module (reset) minutes hhhh:mm:ss calls ekor failed c.offs smses

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

#g00 out ( 0.00) 1 0:01:24 6 0 0 4 0

#g01 out ( 0.00) 1 0:01:08 5 0 4 5 0

End of Module statistics ]

902N TELEKOMUNIKACE a.s., www.2n.cz

7. Technical Parameters

In this section, the technical parameters of the / produ2N BRI Enterprise®BRI Lite ct are described.

Wireless

Mobile network type

GSM 850/900/1800/1900MHz, UMTS/3G at 850/900/1800/2100MHZ – according to the module type used

SIM card Plug–in 3V („small")

Transmission power

Max. 2W

Receiver sensitivity

–104 dBm

Antennas

Frequency

850/900/1800/1900/2100 MHz – according to the GSM module type used

Impedance 50 Ω

Maximum output power

2 W

Antenna connector type

SMA (male)

Count of antennas 1 or 2 (depending on the gateway type)

Cable length 3–10 m or no cable

Power Supply

Adapter 110 – 230 V, 50/60 Hz, 12 V DC

DC power supply 12 V DC / 2 A

Supply connector DC jack, 2.1 mm

912N TELEKOMUNIKACE a.s., www.2n.cz

ISDN

ISDN NT connection type

S0, point–to–multipoint S0, point–to–point

ISDN TE connection type

S0, point–to–multipoint S0, point–to–point

ISDN protocol EuroISDN, DSS–1

2N BRI Lite port count + type

1 NT/TE

2N BRI Enterprise port count + type

1 NT + 1 TE

ISDN connector type 2 RJ–45

NT interface supply From external adapter or ISDN

Ethernet

Type Ethernet 10/100BaseT

Connector RJ–45

Protocols Telnet, http, SIP

VoIP signalling SIP (TCP, UDP), DTMF RFC2833

Voice codecs G.711 (A/u–law), G.729ab

Others

Dimensions (w/o connectors) 162 mm x 156 mm x 35 mm

Working temperature 0°C to 45°C

Relative humidity 5 to 95%

922N TELEKOMUNIKACE a.s., www.2n.cz

8. Supplementary Information

This section provides supplementary information on the 2N BRI Enterprise / BRI

product. Lite

Here is what you can find in this section:

8.1 Directives, Laws and Regulations

8.2 Troubleshooting

8.3 List of Abbreviations

8.4 General Instructions and Cautions

932N TELEKOMUNIKACE a.s., www.2n.cz

8.1 Directives, Laws and Regulations

2N BRI Enterprise/Lite® conforms to the following directives and regulations:

Directive 1999/5/EC of the European Parliament and of the Council, of 9 March 1999 – on radio equipment and telecommunications terminal equipment and the mutual recognition of their conformity Directive 2006/95/EC of the European Parliament and of the Council of 12 December 2006 on the harmonization of the laws of the Member States relating to electrical equipment designed for use within certain voltage limits Directive 2004/108/EC of the European Parliament and of the Council of 15 December 2004 on the approximation of the laws of the Member States relating to electromagnetic compatibility and repealing Directive 89/336/EEC Directive 2002/96/EC of the European Parliament and of the Council of 27 January 2003 on waste electrical and electronic equipment Regulation (EC) No 1907/2006 of the European Parliament and of the Council of 18 December 2006 concerning the Registration, Evaluation, Authorization and Restriction of Chemicals (REACH), establishing a European Chemicals Agency, amending Directive 1999/45/EC and repealing Council Regulation (EEC) No 793/93 and Commission Regulation (EC) No 1488/94 as well as Council Directive 76/769/EEC and Commission Directives 91/155/EEC, 93/67/EEC, 93/105/EC and 2000/21/EC

Directive 2011/65/EC of the European Parliament and of the Council of 8 June

2011 on the restriction of the use of certain hazardous substances in electrical and electronic equipment.

942N TELEKOMUNIKACE a.s., www.2n.cz

8.2 Troubleshooting

For the most frequently asked questions refer to .FAQ.2n.cz

No LED is shining on .2N BRI Enterprise / BRI Lite

2N BRI Enterprise / BRI Lite® is disconnected from the power supply.

fails to log in to the GSM network.2N BRI Enterprise / BRI Lite

Check the SIM card. Check the PIN. Check the antenna connection.

Select a place with a good GSM signal. When I make outgoing call thru the GW, the call is rejected by the gateway. What may cause it?

The communication protocol on the line from your PbX to the gateway is

set to Euro ISDN DSS1 according to Q.931

The SIM cards are logged to the network correctly – both LEDs called GSM1

and GSM2 must be off (they are blinking during logging process, but they

go off after they are logged successfully)

You see good signal strength in the Diagnostics (between –60dB and –80

dB)

The SIM cards are active, they have credit, they are not blocked by the

GSM operator

If you are using CLIR function Enabled in the gateway, check if this feature

is enabled in the SIM card by the GSM operator

The dialed number is in correct format, it matches one of the Network Lists

and this Network List is Actively used in the LCR section

If you have set Max. number of called minutes, make sure those minutes

have not been already used up.

The Time limitation of SIM card (which part of the day it shall be used) is

set correctly

Time and Date is set correctly in the Gateway

Call is not disconnected immediately

Call release in GSM network can take up to 2s. If you are experimenting

longer delay it can be caused by gateway or by PBX settings. Usually the

connection stays active because of simulation of analogue line. If call is

disconnected in analogue line you can hear busy tone. This is not typical

anymore in ISDN networks but you can simulate this behaviour and

generate busy tone up to 30s.

On gateway side you can set following:

If call stays up when call is disconnected from GSM side. Go to ISDN parameters and set Busy tone on None. (This is turning off busy tone generation from gateway.) If call stays up when call is disconnected from PBX side. Go to GSM Basic parameters and set Busy tone on None. (This is turning off busy tone generation from gateway). If call is not cut after this settings set this parameter on Disabled. (If PBX requests to keep line active in disconnection message then gateway will ignore this request and the call will be ended)

952N TELEKOMUNIKACE a.s., www.2n.cz

8.3 List of Abbreviations

API (Application Programming Interface) ASR (Answer Seizure Ratio) BIOS (Basic Input–Output System) A basic set of instructions adn functions

necessary for PC launch.

CD (Compact Disc) A portable optical medium for digital data storing. CDR (Call Data Record) CLIP (Calling Line Identification Presentation)

CLIR (Calling Line Identification Restriction)Unknown calling subscriber. COMPC serial port, RS–232. DHCP (Dynamic Host Configuration Protocol) Automatic IP address assignment

protocol. DNS (Domain Name Server) Server responsible for transfer between IP addresses and domain names.

DTMF (Dual Tone Multifrequency)Tone dialling. FW (Firmware)Similar to SW, used for control microprocessor program name. GMT (Greenwich Mean Time)Mean time for time zone calculations. GSM (Group Switched Mobile system)Current digital mobile telephone network

standard. GPRS (General Packet Radio Service)High–speed data transmission with packet commutation in GSM.

HW (Hardware)Electronic equipment, circuit, board and similar components. IMEI (International Mobile Equipment Identity) Unique number assigned by the

GSM module manufacturer. IMSI (International Mobile Subscriber Identity) Unique SIM card number assigned by the GSM provider.

IP Address of the device within a network. LAN (Local Area Network) LED (Light Emited Diod) Electric light–emitting semi–conductor component. NT (Network Termination)

Network terminal for interconnecting a user line from an ISDN telephone with the provider's external network, a PBX gateway or 2N BRI Enterprise / BRI Lite gateway, for example.

PC (Personal Computer)IBM PC compatible personal computer. PCB (Printed Circuit Board) PIN (Personal Identification Number)SIM card code against unauthorised use. BRI (Basic Rate Interface) Type of ISDN connectino with 2 channels with 64

Kbps each. PUK (Personal Unblocking Key)Code for SIM card unblocking after repeated PIN entering error. SIM (Subscriber Identity Module)Modul with a chip for identification in the GSM network. SMS (Short Message Service)Short text message transmitting service in GSM networks. Short text messages.

SSH (Secure Shell) Secured communciation protocol for LANs, program. SW (Software)Program, programové vybavení TCP (Transmission Control Protocol) TE (Terminal Equipment)

Terminal equipment on the user side (such as ISDN telephone, fax, router, etc.),

962N TELEKOMUNIKACE a.s., www.2n.cz

connected to the NT port only.

UCMD Protocol used for gateway firmware upgrade. UDP (User Datagram Protocol) Transport layer protocol with non–guaranteed

packet delivery. UMTS (Universal Mobile Telecommunication System) 3G system of the mobile phone standard, successor to GSM.

UPS (Uninterruptible Power Supply) Source of continuous power supply. USSD (Unstructured Supplementary Service Data) Data transmission standard

using GSM signalling channels.

972N TELEKOMUNIKACE a.s., www.2n.cz

8.4 General Instructions and Cautions

Please read this User Manual carefully before using the product. Follow all instructions and recommendations included herein. Any use of the product that is in contradiction with the instructions provided herein may result in malfunction, damage or destruction of the product. The manufacturer shall not be liable and responsible for any damage incurred as a result of a use of the product other than that included herein, namely undue application and disobedience of the recommendations and warnings in contradiction herewith. Any use or connection of the product other than those included herein shall be considered undue and the manufacturer shall not be liable for any consequences arisen as a result of such misconduct. Moreover, the manufacturer shall not be liable for any damage or destruction of the product incurred as a result of misplacement, incompetent installation and/or undue operation and use of the product in contradiction herewith. The manufacturer assumes no responsibility for any malfunction, damage or destruction of the product caused by incompetent replacement of parts or due to the use of reproduction parts or components. The manufacturer shall not be liable and responsible for any loss or damage incurred as a result of a natural disaster or any other unfavourable natural condition. The manufacturer shall not be held liable for any damage of the product arising during the shipping thereof. The manufacturer shall not make any warrant with regard to data loss or damage. The manufacturer shall not be liable and responsible for any direct or indirect damage incurred as a result of a use of the product in contradiction herewith or a failure of the product due to a use in contradiction herewith. All applicable legal regulations concerning the product installation and use as well as provisions of technical standards on electric installations have to be obeyed. The manufacturer shall not be liable and responsible for damage or destruction of the product or damage incurred by the consumer in case the product is used and handled contrary to the said regulations and provisions. The consumer shall, at its own expense, obtain software protection of the product. The manufacturer shall not be held liable and responsible for any damage incurred as a result of the use of deficient or substandard security software. The consumer shall, without delay, change the access password for the product after installation. The manufacturer shall not be held liable or responsible for any damage incurred by the consumer in connection with the use of the original password. The manufacturer also assumes no responsibility for additional costs incurred by the consumer as a result of making calls using a line with an increased tariff.

982N TELEKOMUNIKACE a.s., www.2n.cz

Electric Waste and Used Battery Pack Handling

Do not place used electric devices and battery packs into municipal waste containers. An undue disposal thereof might impair the environment! Deliver your expired electric appliances and battery packs removed from them to dedicated dumpsites or containers or give them back to the dealer or manufacturer for environmental-friendly disposal. The dealer or manufacturer shall take the product back free of charge and without requiring another purchase. Make sure that the devices to be disposed of are complete. Do not throw battery packs into fire. Battery packs may not be taken into parts or shirt-circuited either.

992N TELEKOMUNIKACE a.s., www.2n.cz

2N TELEKOMUNIKACE a.s.

Modřanská 621, 143 01 Prague 4, Czech Republic

Tel.: +420 261 301 500, Fax: +420 261 301 599

E-mail: sales@2n.cz

Web: www.2n.cz

MG1877v1.3

1002N TELEKOMUNIKACE a.s., www.2n.cz

2N BRI Lite Enterprise User Manual v1.3

Specifications and Main Features

Frequently Asked Questions

User Manual

1. Product Overview

1.1 Product Description

1.2 Safety Precautions

1.3 Upgrade

1.4 Terms and Symbols Used

2. Description and Installation

2.1 Before You Start

2.2 Brief Installation Guide

2.3 Available ISDN BRI Extension Configurations

2.4 IP Voice Transmission

2.5 Types of 2N® BRI Enterprise Connection

3. Making Calls via BRI Gateway

3.1 Supported 2N BRI Gateway Functions

3.2 Call Routing Principles

4. First Launch

4.1 Ethernet Interface

4.2 Licence

4.3 Firmware Version

4.4 Factory Reset

4.5 Basic Configuration – Step by Step

5. Introduction to Configuration Interface

5.1 Configuration Web Interface

Gateway control

Gateway configuration

Others

6. Configuration Via Terminal

6.1 LAN Communication Setting

6.2 GSM Gateway Behaviour

6.3 List of Terminal AT Commands

6.4 Status Messages

6.5 LOG Files

6.6 Call Data Records (CDR)

6.7 Statistics - Description

7. Technical Parameters

8. Supplementary Information

8.1 Directives, Laws and Regulations

8.2 Troubleshooting

8.3 List of Abbreviations

8.4 General Instructions and Cautions