User Guide For VoiceBlue Next (ENO) (v3.13)
User Guide For VoiceBlue Next (ENO) (v3.13)
User Manual
Firmware 1.26
Version 3.13 www.2n.cz
The 2N TELEKOMUNIKACE a.s. 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 TELEKOMUNIKACE a.s. 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...“.
2N TELEKOMUNIKACE a.s. hereby declares that the 2N® VoiceBlue Next 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 (if enclosed) or our
website at www.2n.cz.
This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions: (1) This device may not cause harmful interference, and (2) this device
must accept any interference received, including interference that may cause undesired
operation.
The 2N TELEKOMUNIKACE a.s. 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
products.
Content
Content
1. Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Terms and Symbols Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.1 Terminal-Based Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.2 AT Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.3 LOGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.4 CDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.5 SDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.6 Available Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.7 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.8 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.9 External SMS Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
In this section, we introduce the 2N® VoiceBlue Next product, outline its application
options and highlight the advantages following from its use. This section also includes
safety instructions.
[2]
Depending on the part number
For a detailed description of the 2N® VoiceBlue Next firmware upgrade see the
section devoted to the system installation.
Manual
Upgrade
Version
1.1 The User Manual relates to the 2N® VoiceBlue Next firmware version
01.00.02.
2.0 The User Manual relates to the 2N® VoiceBlue Next firmware version
01.00.04.
3.0 New four–channel 2N® VoiceBlue Next version.
3.2 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.14.0.
The User Manual relates to the 2N® VoiceBlue Next firmware version
3.3
1.14.0. Text correction.
3.4 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.16.5.
3.5 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.17.0.
3.6 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.18.1.
3.7 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.19.1.
3.8 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.22.0.
3.9 The User Manual relates to the 2N® VoiceBlue Next firmware version
1.22.0. Text correction.
The User Manual relates to the 2N® VoiceBlue Next firmware version
3.10
1.23.0.
The User Manual relates to the 2N® VoiceBlue Next firmware version
3.11
1.24.0.
The User Manual relates to the 2N® VoiceBlue Next firmware version
3.12
1.25.0.
The User Manual relates to the 2N® VoiceBlue Next firmware version
3.13
1.26.1.
Symbols in Manual
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.
This section describes the proper 2N® VoiceBlue Next product installation and
connection.
Licences
2N® VoiceBlue Next may contain time-limited software licences (SIP signalling,
Mobility Extension, e.g.) that render services for limited hours only. Every gateway
restart adds one hour to the internal licence counter. To check the current licence
status, use the web interface of the gateway (refer to Subs. 3.4), or the AT interface of
the Telnet protocol (refer to S. 4).
Caution
A GSM gateway with an expired licence cannot process any incoming
and/or outgoing calls! To avoid this, ask your dealer for licence
prolongation or an unlimited licence!
Tip
Contact your dealer please for more information.
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 −80dBm. If lower, change the antenna position or type!
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 Relax delay parameter to 2
seconds (refer to the GSM Basic Parameters subsection). If the GSM
module fails to log in or rejects to make outgoing 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.
IP address: 192.168.1.2
IP mask: 255.255.255.0
IP gateway: 192.168.1.1
Username: Admin
Password: 2n
Caution
Remember to change the username and password during the first
gateway configuration to avoid unauthorised access!
Caution
Make sure that the GSM gateway is off before inserting and removing SIM
cards to avoid the GSM/UMTS module damage.
Installation Conditions
The following installation conditions have to be met for proper installation:
1. Drill two screws into the wall in a relative distance matching the wall mounting
holes in the 2N® VoiceBlue Next rear. The maximum screw head – wall
distance is 5mm.
2. Hang the 2N® VoiceBlue Next unit onto the pre-drilled screws.
Caution
Do not open the GSM gateway during wall mounting to avoid product
damage and subsequent warranty invalidation!
The screw head – wall distance must allow for simple handling such as
removing from the wall.
1. Put the GSM gateway carefully on a stable horizontal support with its bottom side
up.
2. Stick the rubber feet into the corners as shown below.
3. Place the device on a stable horizontal support.
Caution
Refer to the Proper Location subsection for correct placing!
Components Pieces
Short wing 2
Long wing 1
Rear connecting plate 1
Upper connecting plate 1
Mounting screws 12
Rack screws 4
Single Mounting
Follow the instructions below to mount a single unit into a system rack:
1.
2. Having screwed the wings, place the GSM gateway into a free 1U place of the
system rack fitting it with four rack screws (included in the package).
Pair Mounting
Follow the instructions below to rack mount two GSM gateways into one 1U place:
1. Put the GSM gateways next to each other making their sides touch each other.
Fit the short wings (included in the package) onto the free gateway ends with the
screws enclosed.
2. Insert the connecting plates (BE CAREFUL! The rear and upper connecting plates
have different drilled holes – the upper plate holes are larger and without
threading) in the upper and rear holes of one GSM gateway first. Then connect
the other unit.
Caution
The rear and upper connecting plates have different holes – the upper
plate holes are larger and without threading.
Make sure that the plate does not get into the device to avoid electric
short-circuit inside the GSM gateway.
Leave 2 cm free space at least over and under the GSM gateway for
better ventilation (airflow)!
Warning
Connecting a defective or inappropriate power supply adapter may lead to
a temporary or permanent 2N® VoiceBlue Next error!
Never connect 2N® VoiceBlue Next using the PoE and a local adapter at
the same time to avoid permanent 2N® VoiceBlue Next malfunction!
Check whether the antenna is connected before plugging the adapter.
Feeding the device without antenna connection may result in the
GSM module transmitter damage.
Warning
Tighten the antenna connector gently with your hand – never use a
wrench!
Being a source of radio frequency emissions, the 2N® VoiceBlue Next
antenna should not occur in the close vicinity of the human body. The
health hazard is higher than with mobile phones as, generally, gateways
shared by multiple users show a very high traffic.
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
separately from 2N® VoiceBlue Next, you can use an antenna with an
SMA-connector terminated cable. The antenna should be mounted
vertically.
Refer to the Technical Parameters section for the antenna and cable
parameters.
For the Ethernet interface factory settings for 2N® VoiceBlue Next refer to Subs. 2.2.
Caution
Resetting factory values results in a change of the 2N® VoiceBlue Next
Ethernet interface configuration!
Using a defective Ethernet cable may lead to a high packet loss rate in the
Ethernet network and subsequent instability and poor quality of all
GSM/UMTS calls!
Antenna Splitter
The antenna splitter is a passive component that combines multiple GSM/UMTS
channels into one antenna. In 2N® VoiceBlue Next, it combines two/four antennae
into one. The antenna splitter is placed in the installation box. It is a passive element –
it has a characteristic signal attenuation value that the antenna connected must
compensate. No antenna splitter is used for one-channel 2N® VoiceBlue Next gatewa
ys.
Licence Restrictions
2N® VoiceBlue Next may contain time limited software licences. See p. for more
information.
Firmware Upgrade
Please upgrade the 2N® VoiceBlue Next firmware before installing the system. Check
the www.2N.cz web sites for the latest firmware for this gateway type.
Warning
Use the firmware certified for this gateway type only! Any other
firmware type may damage 2N® VoiceBlue Next irreversibly!
Follow the instructions below to download firmware easily using the gateway web
interface:
For 2N® VoiceBlue Next, quadruple the above mentioned rates (two fully duplex
calls) and add the TCP and IP header transmission rate to the result to get the
resultant transmission rate.
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. 2N®
VoiceBlue Next supports the codecs included in the table above. The type of codec to
be used depends on your VoIP network (individual devices) and your 2N® VoiceBlue
Next configuration. 2N® VoiceBlue Next is designed primarily for VoIP corporate
networks and tries to meet the opponent's codec requirements. If a codec is requested
that is incompatible with 2N® VoiceBlue Next, the call will be rejected.
The SIP and ITU-T H.323 recommended protocols are mostly used for connection
establishing, maintaining and cancelling. 2N® VoiceBlue Next uses the SIP (Session
Initiation Protocol) signalling.
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 2N® VoiceBlue Next VoIP-GSM gateway acts as a UA in any case (has the same
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 2N® VoiceBlue Next
gateway.
Point-to-Point Configuration
2N® VoiceBlue Next can communicate with just one SIP VoIP phone or device (a
VoIP gateway, e.g.) in the PTP (Point-to-Point) mode. The IP address of the opposite
party is always selected as the Proxy server IP address in 2N® VoiceBlue Next for
this mode.
The 2N® VoiceBlue Next PTP configuration is often used for testing purposes before
implementation into the VoIP network. Refer to the figure below for the PTP scheme.
Tip
If you set the incoming SIP Proxy IP address to '0.0.0.0' in the 2N®
VoiceBlue Next configuration, the GSM gateway will receive calls from
any VoIP device.
Point-to-Multipoint Configuration
Point-to-Multipoint is a classical scheme of a distributed VoIP network with one or more
SIP Proxy servers (VoIP gateway). The SIP Proxy server is a software PBX (or a
standard PBX extended with VoIP services), which is responsible for all VoIP signalling.
Multiple source devices (VoIP phones, e.g.) and multiple target devices (2N®
VoiceBlue Next, e.g.) can be used in this mode. An internal routing algorithm (Least
Cost Router, LCR) of your SIP Proxy is used for routing outgoing GSM and other calls in
this mode. Calls to GSM networks can be routed via the 2N® VoiceBlue Next gateway
s. All SIP signalling is governed by the SIP Proxy server and the subsequent voice
stream is based on the Point-to-Point RTP.
Doing this, you restore the factory default configuration values for all parameters,
including the Ethernet interface parameters and access data. Refer to Subs. 2.2 for
factory settings.
Caution
Resetting the factory configuration values results in changes of the
Ethernet settings and subsequent necessity to reconfigure the gateway.
Note
To reset the factory values, press the Reset button until the LED
indicators start flashing red.
Note
Push the RESET button for a short time (0.5 s) to restart the GSM
gateway.
Install the GSM gateway as instructed in Subs. 2.3. Before the first start, remove
the SIM cards, or insert the SIM cards with the PIN request disable.
Connect the GSM gateway to the Ethernet network to enable connection to the
address mentioned in Subs. 2.2 from the configuration terminal. If the gateway
default IP address is not suitable for your Ethernet installation, reset the IP
address as follows:
Disconnect the configuration terminal from the Ethernet network.
Disconnect the GSM gateway from the Ethernet network.
Prepare the Ethernet switches, or an Ethernet crossed cable.
With the Ethernet crossed cable, interconnect the configuration terminal
with the GSM gateway directly.
With the Ethernet switch, connect the configuration terminal and GSM
gateway to the pre-prepared Ethernet switch. We do not recommend
connecting any other equipment.
Change the Ethernet IP setting in the configuration terminal, e.g.:
IP=192.168.1.200, Net Mask: 255.255.255.0.
Open your web browser and enter the GSM gateway IP address.
Enter the factory login data.
Change the required settings in the Gateway configuration / Ethernet
configuration menu and store the data into the GSM gateway.
Connect the GSM gateway to a standard Ethernet network.
Restore the configuration terminal IP setting and connect the configuration
terminal to a standard Ethernet network.
Enter the new GSM gateway IP address to get connected to the web interface.
Enter the current time and date in the Gateway control / Date / Time menu
for the GSM gateway.
Make sure that the Licence status item is unlocked in the Gateway control /
Firmware/Licence menu. If not, your GSM gateway does not contain the
licence. Contact your dealer for the licence key.
Set the correct PIN value in the Gateway configuration / System parameters
menu. The value must comply with the SIM card PIN value.
Set new login data in the Gateway configuration / Login configuration
menu.
Switch the GSM gateway off and insert the SIM cards. Connect an antenna to the
GSM gateway and switch it on.
The GSM gateway contains the factory configuration settings that enable
outgoing calls without additional settings. Now enter the IP address equal to the
GSM gateway IP address on your SIP Proxy or IP terminal.
From now on, 2N® VoiceBlue Next will be ready to receive VoIP-SIP calls and route
them to GSM/UMTS networks. If all the GSM modules are occupied, or logged out, the
GSM gateway will reject all VoIP-IP and GSM/UMTS calls.
You are recommended to attend a 2N® certified training to improve your installation
chances.
The LCR algorithm identifies the outgoing call type, current time tariff rate, day in a
week, and/or free minutes of GSM providers and routes outgoing calls accordingly.
Incoming calls from GSM networks are routed directly to the defined SIP address, or
the DISA function is activated. Furthermore, calls can be routed according to the CLIP
(caller's telephone number). And the CallBack service is also available.
Advantages:
You never miss any important call as you are available at all times.
You can get information SMS messages on missed calls.
You can control your company PBX call forwarding services from your mobile
phone.
You can make use of a comfortable DTMF code control.
You need not make complicated forwarding actions as the function is fully
automatic.
ME can work with any SIP Proxy PBX.
ME can replace any standard VoIP phone.
Calls to your mobile phone are free of charge or at a moderate cost 4.
You need not integrate a costly DECT system any longer.
Fig. 1 shows routing of calls in the case of absence of a subscriber in the VoIP network.
Subscriber A calls subscriber B, for whom the 2N® Mobility Extension function has
been permitted with the active “Follow me” function. Subscriber B does not answer the
call in the VoIP network and so the call is rerouted to its mobile telephone.
In the case of a missed call in the VoIP network, the 2N® Mobility Extension provide
s sending of an information text announcement. This function is called “SMS at no
answer”. Like with call forwarding, it is possible to use the DTMF option to activate and
deactivate the service of sending text announcements for missed calls.
In addition to rerouting calls in the event of absence, the 2N® Mobility Extension allo
ws calls to be forwarded within a VoIP network, which brings the services of the SIP
Proxy to a mobile telephone. The description of this function is shown in Fig. 3.
Correct ME configuration:
Connect the GSM gateway to your PBX/SIP Proxy.
Check whether the 2N® Mobility Extension licence key has been entered
correctly.
Enter all ME users in the Gateway configuration / Mobility Extension menu.
Enter the prefix matching the ME user mobile number in the Gateway
configuration / prefixes menu.
LCR Table
The LCR (Least Cost Routing) table is the key telephone cost cutting tool. It helps you
select call routes according to the called subscriber’s number, daytime and weekdays.
By adding bank holidays (with routing rules as on Sundays) to the LCR table you
achieve even higher call cost savings.
To make your prefix and LCR routing work properly, enter the prefix of the number to
be called to the GSM/UMTS network into the Table of accepted prefixes in the
Gateway configuration / Prefixes menu. The number to be called may not exceed
the Default count of digits or the higher priority Count of digits setting in the Table
of accepted prefixes. The table is searched from top to bottom starting with the first
match.
Apply the Table of replaced prefixes to modify the number to be called to the
GSM/UMTS network. Every modification is displayed in the "prefix"/"replace with" f
ormat (99/+420, e.g.). The Table of replaced prefixes must always contain one
record at least or the "/" record if no prefix modification is made. The digits removed
from/added to the number in the Table of replaced prefixes are not included in the
Count of digits. The table is searched from top to bottom starting with the first
match.
Make sure that the apriopriate provider's SIM card is inserted in the GSM gateway.
Assign the incoming and outgoing groups in the Gateway configuration / GSM
groups assignment menu.
For a call setup, the LCR table is searched sequentially from top to bottom. Each LCR
table row is assigned a Prefixlist in which the prefix match is searched for. If a match
is found, the call will be routed according to the routing group parameters (Groups in
the LCR table) as set in the Gateway configuration / GSM outgoing groups table.
The call will be connected via the GSM module as assigned to the GSM outgoing
groups in the GSM groups assignment table.
If the selected GSM/UMTS module is busy, the call is routed according to the next
routing rule included in the Groups and defined by the GSM outgoing groups table.
Again, the GSM outgoing group is assigned to a GSM module in the GSM groups
assignment table.
The LCR row is checked in this way until a free GSM/UMTS module is found. If no
available GSM/UMTS module (GSM outgoing groups) is found, the call is rejected.
The calling subscriber dials the subscriber number and the SIP Proxy routes it to
2N® VoiceBlue Next depending on the SIP Proxy settings.
The number prefix is checked against the prefixes in the List of networks tables
in the ascending sequence, i.e. table 1 is searched first, followed by table 2 and
so on.
When a matching prefix is found in a List of networks, the LCR is checked for a
valid row. Again, the LCR is searched upwardly, starting from the first row.
If a List of networks number matches a valid number on the respective row,
the call time is checked against the routing rule. If no match is found, the next
LCR row is checked.
If the List of networks number and call time meet the routing rules, the call is
routed to the module selected in the Assignment to GSM groups table
according to the first routing rule included in the Groups section and given in the
GSM outgoing groups table.
Moreover, call duration limiting timer can be selected for the outgoing call.
If the selected GSM/UMTS module is occupied or has a low credit, the algorithm
returns to the preceding step but considers the next Groups row instead of the
first one. If no record is found in this section, the next LCR row is used.
Reject/ Ignore incoming calls – incoming calls are not routed to the VoIP
network. On the GSM side, the connection request is either rejected or ignored
(the caller hears the check ringing tone).
If the above mentioned option is not selected, the CLIP routing table is checked.
If the calling number is found, it is checked for CallBack first. If the CallBack
function is enabled for this number, 2N® VoiceBlue Next will ignore the
incoming call and set up a CallBack to GSM after the caller hangs up. If the
AutoDial function is enabled for the calling number, the caller will be routed
directly to the extension number entered in the AutoDial item. If both the
CallBack and AutoDial functions are activated, 2N® VoiceBlue Next will ignore
the incoming call and set up a call to GSM after the caller hangs up.
Simultaneously, a call to the VoIP extension will be set up and then the calls will
be connected. If the CallBack function is enabled and the caller fails to hang up
within 10 s, 2N® VoiceBlue Next will try to set up a call according to the
AutoDial settings.
In case the CLIP routing function is disabled or the calling number is not included
in the CLIP routing table, the Dynamic CLIP routing table is checked. If the
calling number is found, the incoming call is routed directly to the corresponding
extension. To set the Dynamic CLIP routing function use the GSM incoming
groups menu.
If the incoming call is still not processed, the gateway will receive the call and
send either a voice message or the dialtone to the caller. After that, 2N®
VoiceBlue Next awaits the required count of digits necessary for connection
set-up. Set the minimum and maximum counts of DTMF digits in the GSM
incoming groups menu.
If 2N® VoiceBlue Next does not receive the minimum count of digits and no
other digit comes within the timeout set in the DTMF dialling timeout
parameter, the call is forwarded to the operator as if the called extension number
were unknown.
If call forwarding to the operator is inactive, the incoming call will be rejected.
Essential Data
The 2N® VoiceBlue Next web interface supports the following web 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 or higher. The configuration interface is available in
the English language version only at present.
Tip
Use the F11 key to activate the full-screen mode for better resolution.
Login
For login to the 2N® VoiceBlue Next web configuration interface, enter the server IP
address into your web browser. The following login dialogue will get displayed.
Just one user may be logged in at a time. Refer to Subs. 2.2 for details on the login
factory settings.
Tip
The user limitation applies to the web interface access only. The access to
the Telnet interface is limited to ten simultaneous users.
Web Icons
Caution
Push the Save settings button to save the changes. Otherwise you will
lose the configuration changes after quitting the current configuration
window!
Home Page
Having logged in, you get to the Gateway home page as shown in the figure below.
There is a menu on the left, which includes the Gateway control and Gateway
configuration items. The right-hand upper corner displays the current state of the login
timer and the Refresh button for automatic time limit refreshing.
The home page also includes the Logout button. You wil be notified of successful
logout after every logout action to avoid re-use of your login data.
There are four more sections in the right-hand upper menu:
Firmware / Licence
This window provides information on the gateway licensing, firmware and bootware
versions and Ethernet interface MAC address. A new licence code can be inserted here.
Caution
The licensed protocols will be blocked when the licence code has expired!
Caution
Auto licence is added via the 2N® SIMStar server.
If the current Licence status is blocked during automatic licensing, 2N®
VoiceBlue Next will be restarted during licence adding.
If the current Licence status is unblocked during automatic licensing,
the Gateway limitation will be prolonged without 2N® VoiceBlue Next
restart.
Tip
Upon the dealer's request, the gateway may contain blocking of certain
GSM/UMTS networks. This state is indicated by a red shining Ch 1 / Ch 2
LED. The GSM module diagnostic window displays the 'netw-err' status.
Contact your dealer for more information please.
Caution
By entering a new licence code you restart the GSM gateway and
discontinue all current calls!
Date/Time
The Date/Time window enables you to set the current date and time for the gateway.
Select the Synchronise with local PC item and the Time and Date items will be set
automatically according to your PC data.
Caution
The internal back-up source is able to back up the internal clock source for
a few hours only! Make sure that the gateway date and time values are
correct after a long disconnection from the power supply!
Voice Messages
This window is used for recording, checking and downloading voice
messages. Supported format is PCM-Alaw, Mono, 8000 Hz, 8 bits.
Note
Voice messages with indexes 30–37 are used for detection of the mobile
provider's voice message played before call connection. If a match is
found of the voice message with any of the voice messages recorded in
the gateway, the call is terminated automatically or established via the
last GSM outgoing group set in the LCR table (on condition that the ITD –
Ignore tone detection in last group parameter is active) in the Gateway
Configuration / LCR table section. Refer to the Gateway
Configuration / GSM basic parameters / Voice message detector
settings for details.
LOG file
The LOG file window helps read out the gateway LOG file. The bottom part of the
window includes icons for saving the LOG file into a file and refreshing the LOG listing
in the web window.
CDR File
The CDR file window helps read out the Call Data Records (CDR) of the gateway. The
bottom part of the window includes icons for saving the CDR into a file and refreshing
the CDR listing in the web window. Refer to Subs. CDR line description for more details
on the CDR format.
Caution
The maximum capacity is 100,000 call records. When this limit is reached,
the oldest record(s) will be deleted automatically!
The latest 1,000 call records are displayed in the web interface.
Downloading of a high amount of CDR may take up to several tens of
seconds.
Caution
The maximum capacity is 100,000 SMS records. When this limit is
reached, the oldest record(s) will be deleted automatically!
The latest 1,000 SMS records are displayed in the web interface.
Downloading of a high amount of SDR may take up to several tens of
seconds.
Module status
This window displays the current status of each GSM/UMTS channel. Refer to Subs. 4.5
for status details.
Module control
This window helps you control the selected GSM/UMTS module manually.
Statistics
The window displays the current statistics on calls. The bottom part of the window
includes icons for saving the LOG file into a file and refreshing the CDR listing in the
web window. Refer to Subs. 4.6 for format information.
Connection state
The window displays the states of all available configuration sessions. The bottom part
of the window includes icons for saving the LOG file into a file and refreshing the listing
in the web window.
SIP registration
The window displays the current SIP registration state of the gateway.
Online report
The window displays on-line gateway tracing.
System parameters
General
Saving call data (CDR) – select the call types on which records are to be saved
into the CDR file.
Gateway ID – identifies 2N® VoiceBlue Next numerically in the CDR in case
multiple devices generate the CDR in the network.
System Restart
Enable system restart – enable/disable the feature.
Time of system restart [hh:mm] – set the time for system restart.
Note
If there are active calls, restart will be executed 10 seconds after the end
of the last call.
Tip
The SMS at no answer and Follow me functions can be
enabled/disabled using the above mentioned DTMF codes by calling the
GSM gateway from a registered mobile user phone. The values of these
functions can be changed using the configuration interface too (see
below).
Others
PIN – PIN code for the SIM cards that request the PIN code.
End of dialling (empty=off) – a selectable DTMF code for DTMF dialling end in
the event of a DISA incoming call. The default value is '#'.
VoIP parameters
VoIP functions
Day of deleting statistics on VoIP (every month) – the day of automatic
deletion of call statistics on the VoIP interface. None = no deletion.
SIP registration
Registration expires [s] – the timeout after which the 2N® VoiceBlue Next
registration data expire at the SIP Proxy.
Reattempt registration [s] – time interval for re-sending the request.
Registration domain (realm).
Caller ID.
Username – registration data for the SIP Proxy.
Password – registration data for the SIP Proxy.
Voice parameters
First RTP port (even: 1024 – 65524) – number of the first RTP port. The
number must be even as recommended.
Last RTP port (even: first RTP+10 – 65534) – number of the last RTP port.
The number must be even as recommended. The recommended minimum range
of RTP ports should be 10.
Codec settings
detailed codec settings (G.711a/u, or G.729).
IP addresses
SIP Proxy (IP / GSM) – IP address of the SIP Proxy from which 2N®
VoiceBlue Next awaits the GSM outgoing call requirements.
Tip
In case you keep the default values (0.0.0.0), 2N® VoiceBlue Next will
receive requests from any IP address.
SIP Proxy (GSM / IP) – IP address of the SIP Proxy to which 2N® VoiceBlue
Next turns in the case of a GSM incoming call.
SIP registrar – IP address of the SIP registration server.
Tip
You can use the domain name Registration domain (realm) for the SIP
proxy (IP / GSM), SIP proxy (GSM / IP) and SIP registrar IP
addresses on condition that you complete the domain name Registration
domain (realm) and set the DNS server address properly in the Web
configuration / Ethernet configuration section.The SIP proxy and
SIP registrar IP addresses must be set to the default value (0.0.0.0).
Note
In case the GSM gateway is located behind the NAT, make sure that the
NAT router routing settings for the appropriate ports (SIP, RTP, STUN) are
made. The integrated firewalls may affect VoIP calls too!
GSM selection
Assignment of GSM-channel
Cyclical
Smart - least used minutes
Smart - most remaining minutes
Linear - always first free module
Caution
The Smart – least used minutes and Smart – most remaining
minutes rules are useful where different limit settings are used for SMS.
Calls
Relax timeout [s] – time interval between the end of the last call and the
beginning of the next call via one and the same GSM module (all incoming and
outgoing calls are rejected during this timeout). The recommended value is 2
seconds. Do not change this setting unless absolutely necessary.
Timeout for ringing to GSM [s] – ringing timeout for outgoing calls to GSM. If
not answered or terminated within this timeout, the call will be terminated
automatically by the gateway when this timeout elapses.
Source interface for CallBack – select the CallBack source interface
for CallBack routing. The LCR table must include the appropriate outgoing traffic
rule: if, for example, a VoIP port is the CallBack source interface, routing
from VoIP to GSM must be defined in the LCR.
Delay for fast CallBack [s] – set the delay between the CallBack request and
outgoing call if Auto end to CallBack request is active.
DTMF settings
The minimum delay between two identical DTMF characters received [s/100].
Warning
The GSM/UMTS codec and noise reduction settings of the above listed
module types may affect the DTMF detection quality. Make sure that the
settings comply with the mobile network used.
Caution
An excessively high volume may deteriorate the voice quality (distortion,
echo, etc.) and wrong DTMF detection!
Caution
If the Generate busy tone function is enabled, the length of the
outgoing calls billed by the GSM/UMTS operator increases
Cause translation
Here you can convert the release cause received from GSM/UMTS into another ISDN
release cause. The resultant ISN cause number will be transformed into a VoIP SIP
code as included in the table below:
Define the GSM failed call causes for the 2N® SIM Star Server. If you enter no record
into the Causes of failed calls table, every non-connected call will be evaluated as a
failed call.
General settings
Delay for CONNECT [s] – define a delay before sending information on the
connected call after receipt from GSM.
Minimum ring duration to send SMS at no answer [s] – set the minimum
ringing time for an outgoing call to GSM/UMTS before the SMS at no answer is
sent.
Note
The SMS at no answer function works properly only if the INVITE
message contains the called and caller numbers.
Delay for ALERTING [a] – define a delay before sending information on ringing
start.
off – no Alerting message will be forwarded.
real – the Alerting message will be forwarded as soon as the gateway
receives Alerting from the wireless network or ring tone detectors detect
the alerting tone (if active).
1–20 – the Alerting message will be automatically sent after a predefined
number of seconds after the call is dialled into wireless network.
Minute parameter – select whether or not the GSM gateway should record the
call length or count for outgoing call restriction.
Day of deleting statistics in group (every month) – define a day on which
statistics on disconnected calls should be deleted.
Network settings
BTS lock – identify the BTS to which the GSM modules shall log in. Restart the
selected GSM modules to execute the changes.
Caution
The BTS lock service work with specific GSM modules only (Q55, Q24,
GE910, HE910)!
If you set a wrong BTS lock, the selected GSM module(s) will not log in to
GSM.
Network operator code (MCC+MNC) – set the local mobile network provider
code manually. If you do not enter a value, the provider will be selected
automatically.
Number of registration attempts – set the count of network registration
attempts if the network rejects to register the +CREG:3 SIM responses.
Delay after registration denied (1-600) [s] – set the registration delay, i.e.
the timeout within which the network may send another response after rejecting
+CREG:3.
Timeout for registration (10-600) [s] – set the maximum timeout for the
module to wait for network login in the NWAIT mode.
Next try for registration (0=off, 1-720) [m] – set the interval between
relogging attempts.
Enable USIM and SIM Application Toolkit – enable/disable the USIM and SIM
Application Toolkit services for the Telit HE/GE 910 modules.
Disconnect Call
Set the rules for automatic disconnection of outgoing calls to a wireless network.
SIM limit exceeded – automatic call disconnection when the active SIM card
call limit is exceeded.
Time limit exceeded – automatic call disconnection when the active SIM card
time of use is exhausted.
No ALERTING before CONNECT – automatic call disconnection when the
gateway receives the call connect message without alerting.
GPRS activation
APN string – define the Access Point Name (APN) for GPRS connectivity.
Basic settings
Roaming enabled for network code – set the international network identifier
for roaming purposes consisting of the following two codes:
MCC – Mobile Country Code – country code (Czech Republic – 230);
MNC – Mobile Network Code – GSM code (T-Mobile – 01, 0202, Vodafone –
03).
Hence, the international identification code for T-Mobile CZ is 23001. Leave this field
empty to disable roaming.
String Note
<empty> Roaming is disabled
2300 Roaming is disabled (5 digits is the minimum count)
23002 Roaming is enabled for networks with MCC+MNC code 23002
230XX Roaming is enabled for networks with MCC+MNC codes 23000 – 23099
XX001 Roaming is enabled for networks with MCC+MNC codes 00001 – 99001
XXXXX Roaming is enabled for any network
Note
Check the GSM/UMTS searching priorities on the SIM card using your
mobile phone before enabling roaming.
Caution
Calls via a roaming network may increase you telephone bill!
CLIR – fill in this parameter to define whether or not the called subscriber should
be displayed the calling SIM card telephone number. It is recommended that the
telephone number of the SIM card inserted in the GSM module should not be
displayed to the called subscriber to avoid problems with CallBack from GSM.
Caution
The Temporary CLIP and Temporary CLIR enable services must be
supported by the GSM/UMTS provider. If not, not, the provider's network
may reject the call!
Note
A correct setting of the First count and Next count parameters
guarantees a correct counting of remaining minutes on SIM cards. These
parameters help limit outgoing calls according to free minutes. The CDR
includes real data.
Day limit of called minutes – set the maximum count of minutes to be called via
the SIM card per day.
Time limits
Define the SIM card use time limits for the GSM group.
Call tariffs – use this function to assign up to four independent free minute counters
to each GSM module (SIM card) group:
Free minutes – Count of free minutes for a specific tariff offered by the
provider.
Transferred minutes – Maximum count of unused free minutes to be
transferred to the next period.
Day of restoring free minutes – Day on which the free minute counters are to
be reset automatically. Choose every 24 hours, a day in a month, or a day in a
week for restoring.
Week of restoring free minutes in month – Define the week in which the free
minute counters are to be reset automatically. This setting is useful when counter
reset takes place on 'every other Friday in month'. Otherwise, leave the 'every'
value.
Caution
We recommend you to set the free minute counter value to X-5, where X
is the count of free minutes obtained from the GSM/UMTS provider to
avoid limit excesses.
The manufacturer is not liable for any additional call costs in case the
GSM/UMTS provider's free minute/SMS limits are exceeded.
Caution
The Send CLIP from VoIP to GSM service must be supported by the
GSM/UMTS provider. If not, not, the provider's network may reject the
call!
Others
Time to keep CLIP in table – set the time for which records are to be kept in
the AutoCLIP routing table.
Add record only for unconnected call – unconnected outdoing calls are stored
in the AutoCLIP table only.
Delete record for connected answer – if the CallBack is successful, the
corresponding AutoCLIP record will be deleted.
Skip DTMF for numbers not in CLIP Routing table – enable this function to
define that only the incoming calls whose CLIPs are stored in the CLIP Routing
table will be able to use DTMF dial-in. Make sure that the called number table
includes one record at least to make the function work.
Skip list of called numbers after failed call to wanted number – enable this
function to define that the incoming call will not be forwarded to the number(s)
included in the List of called numbers in case the call is rejected after the
preceding DMTF dial-in.
Auto end to CallBack request – any incoming call whose CLIP matches the
CallBack setting will be rejected and all the other incoming calls will be ignored.
In either case, the CallBack function will be invoked after the incoming call ends.
Prefixes
The window helps you adapt the gateway to calling to variable GSM networks. You can
set the prefix-based call routing rules here and identify up to sixteen different groups
for routing.
Note
The number to be dialled to the GSM/UMTS network must meet the
Count of digits condition.
For VoIP calls, the count of digits to be dialled must be equal to or higher
than the value set in the Count of digits.
Note
The maximum count of records in the Table of replaced prefixes is 14
for each prefixlist.
The maximum table record size is 9 characters for the prefix and 9
characters for the replaced number.
Note
The maximum count of records in the Table of accepted prefixes is 138
for each prefixlist.
The maximum table record size is 9 characters.
LCR Table
Table of outgoing Least Cost Routing (LCR) rules. Every outgoing call from the source
interface is routed to the destination interface according to this table. For a call, the
gateway checks the lines and if the called number prefix matches the prefix in the
selected network list and the current time value is within time limitation limits, the call
will be routed via the defined GSM group(s) or VoIP interface.
Note
If you use tariff routing, set the tariffs properly in the GSM outgoing
groups subsection.
The maximum count of LCR table records is 64.
The rules are applied to calls sequentially, starting from the first rule. If all
the set rules are met in a row, the call is routed according to the row.
Call routing from VoIP/VoIP is not supported. Such calls will be rejected
by 2N® VoiceBlue Next.
Tip
CallBack detects the CLIP from right to left. Thus, configure 10 rules for all
the incoming CLIPs to make CallBack work properly. Each of the rules
must contain one of the CLIPs: 0,1,2,3,4,5,6,7,8,9.
Note
Remember to activate the CallBack mode in the GSM incoming groups
window for a proper CallBack function.
The maximum count of CLIP routing table records is 96.
Mobility Extension
The table registers the Mobility Extension users.
Note
You are recommended to read the Mobility Extension section on page
carefully before using the Mobility Extension function.
Ethernet configuration
This window helps you configure the Ethernet interface of your gateway.
Use DHCP – enable/disable the DHCP client function in 2N® VoiceBlue Next.
IP address – the fixed IP address (v4) of the 2N® VoiceBlue Next Ethernet
interface.
Subnet mask – the subnet mask for the 2N® VoiceBlue Next Ethernet
interface.
Default gateway – The IP gateway IP address (v4) in the Ethernet network.
DNS server1 – primary DNS server.
DNS server2 – secondary DNS server. Used as a back-up when DNS server 1 is
not functional.
Caution
Incorrect settings, e.g. enabling the DHCP client service, may result in a
denial of access to the 2N® VoiceBlue Next configuration. To avoid this,
restore the GSM gateway default settings. Refer to Subs. 3.1 for details.
Login configuration
The window helps you set the access password and name for the 2N® VoiceBlue
Next web interface. Use the same data for Telnet connection too.
Caution
Remember to change the username and password during the first
gateway configuration to avoid unauthorised access!
Note
The username and password may have up to 30 characters in total.
Web configuration
Set additional parameters for the gateway web interface.
Auto logout – set the count of minutes in which the current user should be
logged out automatically.
Enable web session lock – by default, one Admin user may only be connected
to the GSM gateway at a moment. If another authorised user tries to log in, the
previous session will be aborted automatically. By activating this function you
disable such automatic logout and block any further access attempts.
Simple login form – here you can change the login window graphic lay-out.
Upon activation, the GSM gateway login page will have an anonymous
appearance. This function is recommended for connecting the gateway to the
Internet directly.
Use SMS user for SMS operations on the web – enable/disable the user
authorised for SMS sending/receiving only.
SMS user name/password – the gateway enables independent connection of a
user authorised for SMS receiving/sending only.
Report configuration
This window is used for setting details on automatic tracing generated by the GSM
gateway.
Time Synchronisation
Set the NTP server time synchronisation.
Summer/Winter Time
Automatically switch to summer/winter time - enable/disable automatic
winter/summer time transition.
Switch to summer time - set the summer time transition date and time.
Switch to winter time - set the winter time transition date and time.
Caution
This service is file-licensed. Refer to Management / Licence key for the
current GSM gateway licence details.
Modules Grouping
Global settings
SMS server enabled – enable/disable the SMS server at the GSM gateway
(keep disabled if you select another SMS processing method).
AutoCLIP routing expires [hours] (1–10000, 0=off) – set the maximum
time for keeping of the automatic SMS routing record (response) in the AutoCLIP
table.
Not sent SMS expires in [hours] (1–10000, 0=off) – delete an SMS in case
it was not sent within the timeout.
Received SMS expires in [hours] (1–10000, 0=off) – delete a received SMS
in case it was not delivered to the e-mail / SMPP user within the timeout.
Delivery Report expires in [hours] (1–10000, 0=off) – delete an SMS
waiting for delivery report and make an error record in the SDR table in case no
delivery report arrives within the set period of time.
Caution
0=off means disabled expiry, i.e. records are saved into the AutoCLIP
routing table for an indefinite period of time. Therefore, make sure that
the routing priorities are set properly for incoming SMS. Refer to
Incoming SMS routing for details.
Note
If multiple SMS are sent to one and the same number, delivery reports
are assigned to them according to the sending time, starting from the
oldest one.
Caution
The count of user accounts is file-licensed. Refer to Management /
Licence key for the current GSM gateway licence details.
Users
This section helps you manage the SMS users. Select a communication protocol for
user adding (SMTP/POP3 or SMPP).
Note
You can set the Delivery status required parameter only if the
SMTP/POP3 protocol is used.
With SMPP, the delivery information is active automatically in case the
service is required by the SMPP counterparty or via an incoming SMS
message from the GSM/UMTS network.
The user count is licence-limited. The highest possible count of licensed
users is 200. Refer to Management / Licence key for the current GSM
gateway licence details.
The maximum count of SMPP user accounts is 16. With the Email/Web
user accounts, the maximum count is 200 as specified in the licence.
General settings
Set the basic parameters for SMS sending via SMTP/POP3 or SMPP.
Optional informations
Description – set the User group details.
Identical SMS limit – set the check of identical SMS messages, i.e. sequentially
sent messages with identical SMS PDUs. When the set limit is exceeded, the
excessive SMS messages are discarded without being sent.
E-mail settings
Domain – define the domain name for SMS sending/receiving via SMTP/POP3.
The maximum domain length is 63 characters.
POP3 – Subject of e-mail – set the message subject to be added automatically
to the SMS loaded from the GSM gateway via POP3.
POP3 – Subject of e-mail (delivery acknowledgement) – set the SMS
delivery acknowledging message subject.
POP3 – Subject of e-mail (not delivered) – set the SMS non-delivery
acknowledging message subject.
POP3 – Subject of e-mail (send error) – set the SMS sending failure message
subject.
SMTP – Maximum SMS per e-mail – set the maximum count of SMS messages
to be sent within one Email message. Any characters exceeding the set length
will be ignored.
SMTP – Add "From" to SMS – add 'From' from the Email message to the
outgoing SMS. The sender information will be displayed at the beginning of the
SMS message.
SMTP – Add "Subject" to SMS – add 'Subject' from the Email message to the
outgoing SMS. The subject information will be displayed at the beginning of the
SMS message.
Note
The rules are applied to incoming SMS sequentially, starting from the first
rule. If all the set rules are met in a row, the SMS is routed according to
the row.
Sending SMS depends on the outgoing routing rules set in Messaging /
User group / Outgoing SMS routing and limits defined in Gateway /
Gateway configuration / GSM outgoing group. When the limits get
exhausted, the SMS will be stored in the outgoing SMS database until the
set limits are restored.
Note
The rules are applied to outgoing SMS sequentially, starting from the first
rule. If all the set rules are met in a row, the SMS is routed according to
the row.
Control
This section helps you monitor the system. It includes storage filling information and
AutoCLIP records.
SMS queues
The subsection displays the current SMS storage state.
Caution
The POP3 protocol enables you to set how long a copy of the loaded
message shall be kept in the SMS server. The SMS keeping time depends
on your e-mail client setting. Make sure that you have chosen a correct
time value to avoid database overfilling. When the storage has been filled
up, no new SMS messages will be received!
User table
The table shows the count of incoming and outgoing SMS stored in the
above-mentioned databases from the user's point of view and helps you delete the
SMS stored.
Note
If the GSM network shows a temporary error or unavailability, short SMS
are sent three times and long (multipart) SMS five times. If none of the
SMS sending attempts is successful, the SMS will be deleted from the
outgoing SMS database and an Incoming SMS count - Failed message
is generated by the gateway.
Send SMS
This section includes a web interface for SMS sending via the available user
accounts. Sending SMS depends on the outgoing routing rules set in Messaging /
User group / Outgoing SMS routing and limits defined in Gateway / Gateway
configuration / GSM outgoing group.
Note
The maximum message length is 10 SMS. The message can use 7-bit
encoding (up to 1520 characters) or 16-bit encoding (up to 670
characters).
Figure 1 shows sending/receiving SMS via SMPP. Having created user accounts in 2N
®
VoiceBlue NEXT, the users can send/receive SMS via SMPP. The figure shows an
example with two SMSC accounts created in 2N® VoiceBlue NEXT (to the right).
Another 2N® VoiceBlue NEXT (ESME) gateway and a PC on which the SMPP (ESME)
application is running are connected to these accounts via SMPP. An SMS coming to 2N
® VoiceBlue NEXT via SMPP is routed according to the gateway outgoing routing rules
and sent to GSM. An SMS coming from GSM is routed according to the gateway
incoming routing rules and sent to the destination via SMPP.
Caution
You can send an SMS message of any length to up to 100 users at the
same time from the e-mail client. The maximum SMS count per e-mail is
only limited by the User group / General settings SMTP / Maximum
SMS per e-mail settings.
d.
Figure 1 shows sending/receving SMS via SMTP/POP3. Having created user accounts
in 2N® VoiceBlue NEXT, the users can access the accounts via the e-mail client and
send SMS messages to 2N® VoiceBlue NEXT via SMTP. The gateway receives the
messages and resends them to the GSM users according to the predefined routing
rules. A message coming to 2N® VoiceBlue NEXT from GSM is routed according to
the incoming SMS rules and delivered to the user via POP3.
Caution
You can send an SMS message of any length to up to 100 users at the
same time from the e-mail client. The maximum SMS count per e-mail is
only limited by the User group / General settings SMTP / Maximum
SMS per email settings.
a.
and domain Domain: email.com, then the e-mail address of the user
with the right to access the SMS server will be USER@email.com. The @
character is completed automatically and is not included in the Domain:
field.
4. Create the incoming SMS routing rules in the Messaging / User Group /
General settings / Incoming SMS routing / Add menu:
a. Select the group to receive the SMS via the M essage from SMS group.
b. Select the A ction type to define how to process incoming SMS. Example:
Set Action type: Deliver to user to deliver SMS to selected users.
c. Set Deliver to user to define the SMS receiving user.
5. Create the outgoing SMS routing rules in the Messaging / User Group /
General settings / Outgoing SMS routing / Add menu:
Enable the SMS server in the Messaging / Modules grouping / SMS server
enabled menu.
a. Set the SMS group via which the outgoing SMS will be routed in the
Message to SMS group menu.
b. Select the Action type to define how to process outgoing SMS. Example:
Set Action type: Submit from user to send SMS from selected users.
c. Set Submit from user to define the SMS sending user.
6. Should you get in troubles, follow the steps below please:
Read the User Manual carefully and check all parameters.
Find answers to the frequently asked questions at http://faq.2n.cz.
Consult your servicing partner.
You are recommended to attend a 2N certified training to improve your installation
chances.
Refer to the List of SNMP traps for the list of all SNMP traps sent by 2N® VoiceBlue
NEXT.
Caution
This service is subject to licence! Refer to Management / Licence key
for the current GSM gateway licence state details.
Common Settings
General
Signal level – define the maximum/minimum level of the signal received by the
GSM/UMTS module. The SNMP trap is sent automatically whenever the defined
values are exceeded.
SMS bufer upper limit – define the maximum filling capacity of the SMS
storage. The SNMP trap is sent automatically whenever the defined value is
exceeded.
SNMP
General
Enabled – enable/disable the SNMP service.
Community – SNMP community is a group that owns the device and control
stations on which SNMP is running. Default value = public.
Caution
The SNMP service works properly on condition that:
VoIP
VoIP SIP line is not registered
VoIP SIP line is registered
GSM
First GSM module: ERROR
First GSM module: OK
First GSM module has too strong signal level
First GSM module decreased under level of too strong signal level
First GSM module has weak signal level
First GSM module increased over level of too weak signal level
Second GSM module: ERROR
Second GSM module: OK
Second GSM module has too strong signal level
Second GSM module decreased under level of too strong signal level
Second GSM module has weak signal level
Second GSM module increased over level of too weak signal level
Third GSM module: ERROR
Third GSM module: OK
Third GSM module has too strong signal level
Third GSM module decreased under level of too strong signal level
Third GSM module has weak signal level
Third GSM module increased over level of too weak signal level
Fourth GSM module: ERROR
Fourth GSM module: OK
Fourth GSM module has too strong signal level
Fourth GSM module decreased under level of too strong signal level
Fourth GSM module has weak signal level
Fourth GSM module increased over level of too weak signal level
FXS
FXS line 1 ERR
FXS line 1 OK
FXS line 2 ERR
FXS line 2 OK
FXS line 3 ERR
FXS line 3 OK
FXS line 4 ERR
FXS line 4 OK
SMS buffer
Number of SMS/SMPP messages in memory exceeds defined max level
Number of SMS/SMPP messages in memory decreased under defined max level
Number of SMS/SMPP messages in memory exceeds defined max level
Number of SMS/SMPP messages in memory decreased under defined max level
BTS Lock
This section helps you set the BTS lock if the GSM/UMTS module supports this function.
The BTS ID containing cells are marked blue to indicate that the module supports BTS.
Set the BTS lock manually by selecting a BTS or depending on the BTS signal intensity.
Tip
The USSD menu helps you, for example, obtain SIM credit or other
information from the provider. The USSD menu can contain multiple
levels. Use the semicolon ';' to access the next level. A USSD command
can be as follows, e.g.: *123#;1;2.
Test Call
This section helps you test calls via the gateway interfaces or verify the LCR
settings. Both incoming and outgoing calls to/from all the 2N® VoiceBlue Next interfa
ces can be tested.
Status
Call status Connection channel – display the channel for the selected interface
for outgoing test calls.
NULL – no action.
CPRES – call setup request.
IPROC – call setup initiation.
CRECV – called user ringing.
ACTIVE – active call.
DISREQ – call end request.
OVRECV – call setup request rejection due to non-fulfilment of the LCR
conditions.
Waiting channel – display the test channel for an incoming call via the selected
2N® VoiceBlue Next interface.
Firmware update
In this menu you can store new firmware into the GSM gateway. Select the
VBN–xx.xx.xx.bin files only. Refer to the Firmware Upgrade subsection on page Brief
Installation Guide for more firmware information.
Warning
Use the firmware certified for this gateway type only! Any other
firmware type may damage 2N® VoiceBlue Next irreversibly!
After the new firmware file is stored and sent, the GSM gateway is restarted
automatically.
Licence key
This section helps you upload the licence file/code to 2N® VoiceBlue NEXT and
provides information on the current licence file. Refer to Gateway Control for more
details.
Caution
By inserting a new licence code you restart the GSM gateway and
discontinue all the currently made calls!
Restart
This subsection provides information on a forced restart of 2N® VoiceBlue Next.
Configuration upload
The window helps you upload new configuration settings into 2N® VoiceBlue Next co
nfiguration. The Ethernet interface and login data remain the same!
Warning
Be sure to upload the configuration file intended for the selected GSM
gateway only to avoid malfunction of the GSM gateway and the necessity
to restart the system.
Configuration Reset
This subsection helps you restore the default configuration (except for Ethernet and
login).
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 www.2n.cz for the latest User Manual
version!
SIM Client
This section is displayed for those GSM gateways only that support the 2N® SIM Star
system connection – remote SIM card function.
SMS
This subsection helps you send and receive SMS via the modules.
Tip
You can also use the SMS user account for SMS sending/receiving. Refer
to the Web Configuration subsection for SMS user configuration details.
Note
This menu is inactive if the SMTP/POP3 or SMPP messaging licence is
active. In this case, use the Messaging / Send SMS menu for sending
SMS via the web interface.
This section describes communication with 2N® VoiceBlue Next using a terminal.
Terminal
2N® VoiceBlue Next acts as an ANSI terminal with echo. Text commands are entered
in one of the following formats: AT[command]<CR>, or AT[command]<CR><LF>. The
answer consists of up to several rows, an empty row with <CR><LF> and the reply
type: OK, ERROR, or BUSY. Use A/<CR> to repeat the command.
The gateway requests a password by displaying the Login: and Password: prompts.
It uses an extended set of AT commands for configuration. Refer to Subs.4.2 for the
list of terminal AT commands.
Access Data
2N® VoiceBlue Next receives Telnet requests on port 23. Port 23 can not be
reconfigured.
The access password and name are identical with those of the web interface. The
access data cannot be changed from the gateway Telnet interface (only from the web
interface) for security reasons.
The following list of AT commands is universal and some commands may not be
included in 2N® VoiceBlue Next.
Basic Commands
System Information
ATI3 – Firmware version and copyright
ATI4 – Factory number
Statistics
AT&T – Statistics of calls via PRI interface
AT&TIN – Statistics of incoming calls via GSM modules
AT&TOUT – Statistics of outgoing calls via GSM modules
AT&T## – Statistics of calls via SIM cards of GSM module ##
AT%TPR=mi,ci,mo,co – Setting of statistics via PRI
AT%TG0=mi,ci,0,0 – Setting of statistics of incoming calls via all GSM modules
in GSM group 0
AT%TG#=mi,co,ri,ro – Settings of statistics of GSM group #
AT%TGALL=mo.co,ri,ro – Settings of statistics of all GSM groups
AT%T##=#,mi,ci,si,mo,co,so – Settings of statistics of SIM card # of GSM
module ##
AT%T##=ALL,mi,ci,si,mo,co,so – Settings of statistics of all SIM cards of
GSM module ##
AT%TALL=ALL,mi,ci,si,mo,co,so – Settings of statistics of all SIM cards of all
GSM modules
AT%T##F=#,m,a,m,a,m,a,m,a – Settings of statistics of tariffs for module ##
and SIM card #
AT%T##F=ALL,m,a,m,a,m,a,m,a – Settings of statistics of tariffs for
module ## and all SIM cards
AT%TALLF=ALL,m,a,m,a,m,a,m,a – Settings of statistics of tariffs for all
modules and SIM cards
Description of parameters:
Mi/mo – Minutes of incom./outg
callsCi/co – number of connected incom./outg
callsRi/ro – number of re-routed incom/outg
calls in groupSi/so – number of received/sent SMS messages
m - called minutes of the current period
a - unused minutes of the last period
Caution
When you change these parameters, all the other counters will be reset!
Configuration commands
Status Information
AT&V – Overview of all system settings
AT&VI – Overview of ISDN PRI settings
AT&V0 – Overview of basic GSM settings
AT&V# – Overview of GSM group # settings (#=1–8)
AT&VB - Overview of module assignment to groups
format: B#=grpout, grpin
# is the module number
grpout, grpin - outgoing and incoming groups of module
AT&VALL – Overview of all GSM group settings
AT&VE – Overview of VOIP parameters
AT&N# – Overview of parameters of network list # (#=1–8)
AT&NALL – Overview of parameters of all network lists
AT&R – Overview of LCR lines
Default Reset
AT&FRES – Reset with gateway factory settings
System Control
AT&BSYS=RESET – Reset of PRIGW
AT&Gxx=RESET – Reset of GSM module xx
AT&Gxx=BLOCK – Block of GSM module xx
AT&Gxx=DOWN – Transfer of GSM module into the sleep mode
AT&Gxx=ON – Transfer of GSM module into the idle mode
List of Networks
AT%N#0=op/np,…op/np – List of prefixes replaced by new prefixes
(#-number of netlist; op-old prefix;np-new prefix)
AT%N#1=pr/n,…pr/n – List of prefixes dialled into ISDN (to be used for LCR
table) pr=prefix n=length of number (parameter /n is optional)
AT%N#2..7=pr/n,…pr/n – Other 7 lists of prefixes dialled into ISDN
AT%N#9=net,max – Net-network number, max-default length of number
dialled from ISDN
Test Calls
AT!SGxx=dial – Initiates testing call from AUX interface (xx is the called
interface):
00..31 – GSM module
32 – to GSM via GSM module according to call prefix
AT!WGxx – Connects the following call from interface xx to AUX interface
00..31 – from GSM No.
32 – first incoming calls from GSM
AT!D – Terminates call on AUX interface
Trace
Trace can be activated for only one session at a time.
SMS Control
SMS control can be activated for only one session at a time.
AT!G=#
A6 – activate control via used session
55 – deactivate control via used session
99 – deactivate control on all sessions
AT^MS=ch – Module status ch=0–31
*module: ch,sim,sts3,sts2,phs2,type – Response to AT^MS:
ch – number of wireless engine
sim – number of currently used SIM: 0-none, 1–8-holder 1–8
sts3 – status of layer 3
sts2 – status of layer 2
phs2 – substatus of layer 2
type – type of wireless engine
AT^MI=ch – Module info ch = 0–31
*minfo: ch,sim,netid,"oper",new,cnt – Response to AT^MI
**Date Time Type Cause From/to Groups conn. durat. aoc-info gid CDN CGN
IMSI/SCID
Column 1: **
Column 2: call date and time
Column 3: call status
O-OK – successful outgoing call
O-FD – unsuccessful outgoing call
I-OK – successful incoming call
I-FD – unsuccessful incoming call
OSIM – successful outgoing simulated call
RSIM – successful incoming simulated call
ESIM – unconnected outgoing simulated call
Column 4: GSM release cause
Column 5: used channel number / used GSM module
Column 6: used GSM group (C=CallBack)
Column 7: connection time
Column 8: call duration mmm:ss (max. 255:59), or error cause for
unconnected call
Column 9: call cost (to be implemented in higher firmware versions) / gateway
ID (optional)
Column 10: called party number (CDN)
Column 11: calling party number (CGN)
Column 12: SIM card slot number / SIM card IMSI or SCID
** date time type error usr/gr/mo ssec date time pn/pt gid
Column 1: **
Column 2: date/time – SDR record creation time
Column 3: type of SMS
R-OK – delivered OK – SMS received
S-FD – sending ERROR – SMS sending error
S-OK – send OK – SMS was sent but no SMS delivery receipt was required
S-TO – sending timeout – SMS was not sent within the set timeout
D-ER – delivery ERROR – SMS delivery error
D-OK – delivered OK – SMS delivered
D-TO – delivery timeout – SMS was not delivered within the set timeout
SANS – SMS after successful call
SNOS – SMS at no answer
SWEB – SMS was sent via web interface
SSIM – simulation SMS was sent via 2N® SIMStar server
RSIM – simulation SMS was received 2N® SIMStar server
Column 4: error type
for (D-OK): SMS receipt status (typically E – 000)
for (D-ER): SMS receipt error code
for (S-FD): module +CMS ERROR (typically E – 028)
for (S-FD): internal error (E – 902 = no rule to send)
Column 4: user id/SMS group/GSM module
Column 5: SMS sending time
Column 6: date/time
First row – SMS sending time or total sending time for all parts of a long
SMS
Second row – time of SMS adding to the outgoing/incoming SMS database
Column 8: part number/total
Column 9: gateway id
GSM Layer 2
INIT – GSM module initialisation start (follow PINREQ)
SIM0 – Module switch to internal SIM card (follow INIT)
PINREQ – Module PIN request (follow PINSET)
PINSET – PIN value sending to module (follow INFO)
BLOCK – Module blocked temporarily or permanently (see Layer 2 information)
(follow INIT)
SETUP – Module configuration running (follow IDLE)
SLEEP – Module sleep running (transition to BLOCK status) (follow BLOCK)
NWAIT – Awaiting GSM log-in (follow SETUP)
IDLE – Rest status, can start/receive call, execute AT&G command (follow
CALL/CMD)
CALL – Call running (call establishing, connected call, call end) (follow IDLE)
CMD – Communicating with module upon AT&G command (follow IDLE)
INFO – Information loading from module and SIM card (follow NWAIT)
GSM Layer 3
NULL – Rest status, ready for call
CINIT – Request of call to GSM (from Layer 4)
OPROC – Call to GSM is connected
CDELIV – Call to GSM is ringing
CPRES – Indication of call from GSM (from Layer 2)
CRECV – Call from GSM is ringing on ISDN interface
IPROC – Call from GSM is processed by ISDN interface
ACTIVE – Connected call
DISREQ – Disconnection request (to Layer 2)
DISIND – Indication of disconnection (from Layer 2)
RELREQ – Module release for another call (to Layer 2)
OVRECV – Reading of DTMF dialling from GSM (from Layer 2)
RELIND – Indication of module release (from Layer 2)
Layer 4
NULL – Rest status, ready for call
MORE – Call request received from GSM or ISDN, awaiting further dialling or
timeout
SETUP – Call request sent to opposite interface
PROC – Call request confirmed, awaiting call answer
ACTIVE – Connected call
DISC – Call disconnection in progress
Command Shell
IDLE – Rest status, awaiting AT commands
REQUEST – Communication with GSM module upon AT&G command is displayed
REPORT – Active tracing
LOGFILE – Content of log file is being written out
CALLFILE – Content of call file is being written out
CALLREAD – Call file records are read
AUTOFILE – Content of incoming call auto routing chart is being written out
QUERY – (not used so far)
SCREEN – (not used so far)
MATRIX – Active matrix screensaver
FUNCFILE – Content of debug file is being written out
LCRFILE – (not used so far)
Telnet Layer
LOGOUT – User logged-out
LOGIN – User is entering name
PASSW – User is entering password
IDLE – User logged-in
Explanation of columns
Group/network/module – type of calls
Reset – date of last reset the statistics
Minutes – number of minutes hhhh:mm:ss, same number converted to time
Calls – number of calls
SMS – number of sent SMS messages
Reject – number of unconnected calls (no available free GSM module-call
rejected with cause 41(42))
Failed – number of unconnected calls (rejected by GSM network)
C.offs – number of unconnected calls (terminated by calling party)
Errors – number of unconnected calls (wrong requests – disallowed prefix, etc.)
Red.in – number of connected calls (rerouted to this GSM group)
Redout – number of connected calls (rerouted to another GSM group)
Explanation of rows
#i1 inc – incoming group 1
#g1 out – outgoing group 1
#vi inc – all incoming calls via VoIP
#grpinc – all incoming calls via GSM/UMTS
#vi out – all outgoing calls via VoIP
#grpout – all outgoing calls via GSM/UMTS
#m0 inc – incoming calls via m0 module – local SIM
#m0 out – outgoing calls via m0 module – local SIM
#m0 day – m0 module limit statistics
#m0 fre – m0 module tariff statistics
#m0 rem – remote SIM statistics
-----------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
------------------------------------------------------------------------------ -----------------
Tip
You are advised to synchronise your GSM gateway with the SIP Proxy, or
a PC before tracing.
AT Command
AT%S92=x – Description AT%S92=x Set the tracing details. Refer to the table
below for value X
AT!R2 – Start tracing via the active session
Any character – Terminate tracing
Layer 3 and 4 Timestamp SMP Packet Layer 2 Status LCR
Status Listing Write-Out Write-Out Listing Listing
1 2 4 8 16
The resultant value X is a sum of the required functions (X= timestamps+LCR = 16+2
= 18, e.g.).
SMS Storages
Siemens/Cinterion: 1=SM, 2=ME, 3=ME
Ericsson: 1=SM, 2=ME, 3=ME
Wavecom: 1=SM, 2=ME, 3=SR
Huawei: 1=SM, 2=SM, 3=SM
SierraWir.: 1=SM, 2=ME, 3=SR
Motorola: 1=IM, 2=IM, 3=IM
(SM = SIM card, ME = module, SR = status report memory, IM = inbox memory)
Information Messages
*smsinc: ch,ix,sts,mem – An SMS message was received and saved into the
SMS storage.
*smsrep: ch,ix,sts,mem – An SMS status confirmation was received.
*smsout: ch[/id],ref,req – An SMS message was sent and not saved into the
SMS storage.
*smspdu: ch,ix,sts,len,pdu,csum – Content of SMS message or status
confirmation.
*smsdel: ch,ix – An SMS message or status confirmation was deleted from
position ix.
*smserr: ch[/id],ix,req,err,cms – Response to an error command.
*smssel: ch,cnt – Confirmation of an SMS storage change.
Two-Channel Version
Dimensions
Dimensions (W x H x D): 170x130x45 mm
Power Supply
Type: External power adapter (SELF type) 90–230V,50–60Hz to 12V DC 2A
Power over Ethernet (PoE 802.3af)
Connector: DC Jack 2.1mm
Power input: Up to 20W
Interface
Protocols: TCP,UDP,IP,RTP,TELNET,http,DHCP
Connector: 1x 10/100BaseT Ethernet
Administration: AT commands, web interface
VoIP
Signalling: SIP
DTMF: RFC2833
Count of voice channels: 4
Voice codecs: G.711 PCM at 64 kbpsG.729 Annex AB
PCM companding: A-law/u-Law (optional)
Others
Working temperature: 5°C–45°C
Air humidity: Max 95% at 40°C
Four-Channel Version
Dimensions
Dimensions (W x H x D): 220x45x140 mm
Weight: 945 g
Power Supply
Type: External power adapter (SELF type) 90–230V,50–60Hz to 12V DC 2A
Power over Ethernet (PoE 802.3af)
Connector: DC Jack 2.1mm
Power input: Up to 20W
Interface
Protocols: TCP,UDP,IP,RTP,TELNET,http,DHCP
Connector: 1x 10/100BaseT Ethernet
Administration: AT commands, web interface
VoIP
Signalling: SIP
DTMF: RFC2833
Count of voice channels: 4
Voice codecs: G.711 PCM at 64 kbpsG.729 Annex AB
PCM companding: A-law/u-Law (optional)
Others
Working temperature: 5°C–45°C
Air humidity: Max 95% at 40°C
6.1 Troubleshooting
6.2 List of Abbreviations
6.3 Regulations and Directives
6.4 General Instructions and Cautions
Check the Ethernet cable connection and the Ethernet interface settings in your
PC.
Europe
2N® VoiceBlue Next 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 2011/65/EU 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
Regulation (EC) No. 1907/2006 of the European Parliament and of the Council of 18
December 2006 concerning the Registration, Evaluation, Authorisation 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 2012/19/EC of the European Parliament and of the Council of 4 July 2012 on
waste electrical and electronic equipment.
Industry Canada
This Class A digital apparatus complies with Canadian ICES-003. / Cet appareil
numérique de la classe A est conforme a la norme NMB-003 du Canada.
Changes or modifications not approved by the responsible party could void the user’s
authority to operate the equipment.
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 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.
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
short-circuited either.
PR1561v3.13