GW Config

TOPEX multiACCESS/QUTEX/EONES/multiSwitch - Operations,
Administration, and Maintenance - CONSIDERATIONS
1. Destination
- TOPEX multiACCESS/QUTEX/EONES/multiswitch may be configured and
administered by the software "Topex multiACCESS/QUTEX - Operations,
Administration, and Maintenance" through serial port or through Ethernet
interface.
- The installation CD-ROM coming with the equipment includes the operation,
administration and maintenance program (OAM). The program may run on any
desktop PC or laptop that fulfills the following minimal requirements:
-Operating system Windows 95 or later versions
-Minimum processor 486
-Recommended minimum 1GB free space on HDD
-Minimum 64 MB RAM
-CD-ROM unit
-One free serial port or one Ethernet interface
-Graphics resolution 1024 by 768 pixels - colors High Color (16bit) or
True Color (32bit)
- Through the OAM program you can configure and manage maximum 50
different TOPEX multiACCESS/QUTEX or 50 different EONES systems. From
the same OAM application you can't operate on both kind of equipments multiACCESS/QUTEX, EONES or multiswitch. Each of the systems has a
associated directory folder (in the same place with the executable application
"gwconfig.exe"). Also there are subdirectories for each types of files: for
alarms - Alarms, for billing - Billing, for activity - Activity, for log files - Log
and for viewing text files - Viewer.
- You can access all remote TOPEX systems in order to configure and maintain
them. You may download files from remote systems into the appropriate
subdirectory on the local HDD, or upload edited configuration files to the Topex
gateways.
2. Installation
To install the OAM program on a desktop PC or notebook please follow these
steps:
- Insert the Topex CD-ROM into the drive.
- The program features auto-run, it should begin installation by itself:
- The installation screen shows up: the Topex logo, the name of the program
being installed and the equipment for which the program is intended, and in
the right bottom corner the progress indicator for the Setup program. You just
wait for the OAM program to be installed on your computer.
- Then the Welcome screen appears, mentioning which version of the program
is currently installing. In the last picture for example the displayed version is
"2.3". The actual software version may be different from the one shown in
"Welcome" window, so after finishing installation, you should use "About"
command to see the OAM version currently running on your computer.
- Then the window "Choose Destination Location" appears, asking you to
specify the folder where the "gwconfig" application will be installed. The
default value is a folder named "TOPEX" in the "Program Files" system folder.
Select "Next" to continue or "Browse" if you want to specify another folder for
the installation. Usually, you do not need to change the default location.
- The "Select Program Folder" window comes next. Here you must specify the
name of the Programs folder were the startup icon for the OAM will be
installed. The setup program will create in Programs a folder called "TOPEX
GATEWAY - OAM". Again, you should not change this default value.
- Now the effective installation begins, you will see a progress bar showing the
progress of the installation:
- When the setup is successfully ended, the window "Setup Complete" will
show up. It asks you if you want to see the README file and if you want to
launch the OAM program immediately.
- To end the installation, click the button "Finish".
- Now the OAM program is fully installed on your system.

- To launch it, go to the Start menu, select "Programs" and then click "TOPEX
GATEWAY - OAM".
Note 1: If the "autorun" feature for CD's is not enabled on your computer,
then you must launch the Setup program manually. Go to "My Computer" and
click on your CD drive. You will see the contents of the Topex installation disk.
Double click the "Setup" icon to launch the installation program.
Note 2: You may want to remove the OAM program from your computer.
- From the Start menu, go to "Settings" and select "Control Panel".
- From Control Panel, double click the icon "Add or Remove Programs". Search
in the list of currently installed program the application "Topex Gateway OAM" and click the "Change/Remove" button if you want to uninstall the
program.
- A window called "Confirm File Deletion" shows up, asking you to confirm that
you want to remove the OAM program. Press YES to continue.
Now the un-installation of the program begins. You will see onscreen a
progress indicator.
- The OAM program is removed from your computer, but the TOPEX folder
won't be deleted. Consequently, if you had configuration, billing or monitoring
files in this folder, the files will be kept. Also, when you re-install the OAM
program over a previous installation, the configuration and log files won't be
overwritten, so you may keep your settings, activity and billing records.
Note 3: on Topex CD-ROM there is also a folder named "OAM". It contains all
files which are necessary for the OAM application to run in case that you need
to copy them manually to a folder you want to use.
Note 4: if you have checked the box "I like to launch TOPEX GATEWAY - OAM"
or when you go to "Start - Programs- TOPEX GATEWAY - OAM", the OAM
program will start up.
3. Menu description
Systems
Through the OAM program you can configure and manage

maximum 50 different TOPEX multiACCESS/QUTEX gateways.
- Add
Adds a system in the arborescent structure
- Remove
Removes a system
Facilities
- Font
Chooses the font type for the text in the "Modify Configuration" and
"View Configuration" windows.
Shows the significance of colors used in "Modify Configuration" and

- Color
"View Configuration" windows in the representation of cards and
signification
ports. The user is allowed to modify the colors at his own choice.
Opens a window in which you may see the text files in which other
- View print
text files or data information have been printed using the button
files
"Print" (or icon "Print").
Opens a dialog box in which expert users may enter direct
Commands commands to the connected system
About
Shows the software version
Help
Opens the help window
Exit
Exit from the OAM program
4. Icons description
- The toolbar including button icons is a dynamic bar which is changing
according to certain actions performed by the user. Some buttons are
equivalent to options from the Menu or from System.
- Definition of the button icons:
Equivalent to System > Add
Equivalent to System > Eliminate
Save Current Configuration of remote
connected Topex System
Downloading Configuration (for TOPEX
equipments with redundancy - with two
processor cards)
Upload Configuration (for TOPEX
equipments with redundancy - with two
processor cards)
Upload Configuration to remote connected
Topex System
Defines gateway parameters
Defines directions (trunk groups) name

Defines classes of directions for incoming
and outgoing calls (direction definition)
Defines table for the routing of the call
Defines LCR table
Defines restriction classes for calls
Defines table with indexes for SIM usage
Defines table with holidays
Defines callback table
Defines circuit groups for SS7 configuration
Defines signaling points for SS7
configuration
Defines parameters for the VoIP card
Displays a window that allows the file
transfer from the system to the program
Shows a window which permits
automatically transfer of files from system
to OAM computer
Clean HDD Space
Displays a window for file editing
Downloads the output of a previous LINUXlike command that has been sent from
"Facilities - Commands" to the connected
Topex system.
In a state of connection between
"gwconfig" program and a gateway,
launches directly the "putty" application.
"Putty" will connect on port 22 the same IP
address to which "gwconfig" software is
connected. The username will be sent
automatically (it is taken from the name
used for logging into the gateway).
Sets the gateway system time with the
time of the computer on which the OAM
program is running
GSM Reprogramming
Defines parameters for alerting
Defines and programs test calls

This is the command for HALT the gateway
This is the command for REBOOT the
gateway
Status monitoring - command for online
display of the port status
Cell, Level and Channel Info monitoring
Calls monitoring - command for online
display of current calls
Prints the files, to the printer or in a text
file
Defines text to find
Find next text
Configuration list
Starts protocol message monitoring
Stops protocol message monitoring
Starts / stops password working mode
Allows definition of users for "gwconfig"
software
Starts the automatic interrogation
procedure for all installed system finding
the alarms and (or) the ASR ("Answer
Seizure Ratio") values
Equivalent to About from the main menu
Equivalent to Help from the menu
Equivalent to Exit from the menu
Note: There are two additionals icons used in a particular situation when
TOPEX equipment is supplied with 2 processor cards (one active and one
backup) - this can be the case of redundancy for softswitch or EONES boxes.
Download configuration files from one of
the selected processor cards.
Upload configuration files in selected
processor card. This operation can be also
performed in the same time on both

selected processors.
- The toolbar including button icons is a dynamic bar which changes according
to certain actions performed by the user. The OAM software can be in one of
the following states:
- one
system
connected
- viewing
files for a
system
- none of
the above
situations
5.Tree options
- The OAM program for TOPEX multiACCESS/QUTEX gateway is using a tree

structure of files and folders.
- Since the OAM program can configure and manage up to maximum 50
different multiACCESS/QUTEX, each of them uses a different folder for its files.
- Description of the tree structure
Identifier of the system:
- "cfg_" are configurations of remote gateways where the
cfg_<Name> program is connected
viz_<Name> - "viz_" identifies local configurations, saved on the HDD for
editing and later uploading

Connect
Initiates a connection to the system
Disconnect
Disconnect, breaks the existing connection to the system
Parameters
Displays the parameters of the connection to the system
Last
Displays the configuration received at the latest status inquiry to
configuration the system
Alarms
Displays the alarm files
Billing
Displays the billing files
Loading
Displays call statistics on ports and directions
Activity
Displays the monitor files
ASR
Displays the ASR ("Answer Seizure Ratio") files. These files

contain ASR values, average time, total number of calls and
answered calls, total seized time and total connected time.
SMS
Displays the SMS and CALLS files (both SMS and CALLS are
supposed to be sent from internet)
Viewer
You can view text files with every kind of extension
Log
Displays the log and lch files
6. Language option
- On the icon buttons bar there is also a listbox which allows changing the
language that is used in all menus, dialog boxes, windows and messages. The
default language is English, shown by the corresponding flag.
- English language
- French language
- Romanian language
7. Status bar
- The status bar is divided into six columns.
- The first three columns (starting from the left side) are displaying indicators
for supervising a connection. These three fields are filled in only in connection
state between the "gwconfig" software and a TOPEX gateway. Exception: if
using automatic interrogation procedure then first column displays the time
remaining until a new interrogation procedure is scheduled.
- First column "
" is indicating the number of commands
that will be sent to the gateway. Each modification (changes in configuration
files or on gateway ports) or data request that is performed on the gateway is
translated into commands. These commands are send to the equipment.
- The second column and the third column are showing protocol messages,
protocol which is running between "gwconfig" software and the connected
gateway.
- The fourth column displays the date and time of the system. (the format is
dd-mm-yyyy hh-mm-ss("
"). Also, this column may
contain information about the time limit for the Topex licence. It can be shown
here either that no licence limitation is present on your system ("no limit
licence") or that a time limit is present for the licence ("30 licence days"). The
number shows how many days you have left for the limited licence. After the
specified period, the application running on the gateway will stop processing
the calls. Then you must contact Topex to get a serial (character string)
which will allow further operation of the gateway.
By clicking with the mouse over this column, a window will pop up, showing
the licence features which are currently granted to your gateway. In the list of
features, each granted features will be shown as an enabled checkbox).
Following the list of features, the version of the gateway application will be
shown as x.z.y. In the last example, this is "Ver 4.1.158".
- The fifth column is an indicator for the occupied HDD space on the target:
the percent value is displayed. The color used is light blue if the available HDD
space is under the 90% and red otherwise. This value is shown only in
connection state.
- The sixth and rightmost column is an indicator for the connection: light blue
if the program is connected to a system ("
") or red if the program is NOT
connected to a TOPEX system ("
")
Note: if the TOPEX equipment is supplied with 2 processor cards (for
redundancy purposes) then in the bottom area of the OAM main window will
be two status bars. Each status bar corresponds to a processor card. In this
case the first column will contains the IP address of the processor card.
The fourth column contains the licence information for each processor card.
Date and time is displayed just for the second status bar.
Last column will contains also the information about the active processor - the
information is "ACTIV".
8. Display issues
- The panel located on the right side of the tree window is used by two kind of
windows.
- First type of window is called "Modify Configuration" and it is displayed
during a state of connection between the "gwconfig" software and a TOPEX
gateway; also the same type of window is used for "View Configuration"
window, window which is displayed when "Last configuration" command is
selected.
- In "Modify Configuration" window the right mouse button is used for adding
/removing cards; if you click the right mouse button over the status bar a
message ("Do you wish to disconnect?") will be displayed, asking you if you
want to disconnect the connection. The same message is displayed if you click
the button to close the window or if you choose the corresponding tree
command option "Disconnect".
- For the second case when "View Configuration" window is displayed the right
mouse button is used to hide the window. The confirmation message that is
used is "Do you wish to hide last configuration?". The same message is
displayed if you click the button to close the window or if you choose the
corresponding tree command option "Disconnect".
- The second kind of window is the one used to display different kind of files as
a result of actions over tree options: "Billing", "Alarms", ASR", "SMS",
"Activity","Log" and "Viewer". In this situation the title of the window includes
the words "Local Viewer" and the system name. An action with the right mouse
click will cause the message "Do you wish to hide?" to be displayed. For
"Billing","ASR","SMS" and "Activity" an appropriate filter can be applied for
viewing the records, then the window which contains the list of the files will be
automatically hidden. For the other options the data will be displayed in the
same "Local Viewer" window.
- The content of that second window can be updated with other data simply by
selecting another option from the tree structure.
Note 1): if "Last Configuration" command is used while "Local Viewer" window
is displayed, then the "View Configuration" window will be displayed over the
previous "Local Viewer" window.
Note 2): if "Local Viewer" command is used while "Modify Configuration" or
"View Configuration" window is displayed then the "Local Viewer" window will
be displayed over the other window. The user must hide (using the right
mouse button) the "Local Viewer" window to see again the "Modify
Configuration" or "View Configuration" window.
Note 3): Just above the status bar there is an icon "
" which allows the
printing of the screen. This icon is used also in all windows that are displayed
by the "gwconfig.exe". This way you can have immediately a hard copy of all
settings of the windows you want.
9. Files
- Files used: the OAM program uses several types of files: for alarms, events,
billing information, etc. Most of the files are text type, so they can be easily
viewed and also modified using a standard text file editor such as Notepad for
Windows.
- The files have different extension, in order to be quickly identified: '.alr' for
files with the alarms, '.tax' for billing (taxation) files, '.mon' for monitor
(supervision) files that include detailed information about each call, '.asr' for
calls statistics, '.sms' for sms files, '.log' files for recording the events, '.lch' for
the files that record the changes made to the system. The name of these files
is given by the field "name" (option "Gateway Parameters") concatenated with
the current day and the extension.
10. Password mode

- The "gwconfig" software includes a multiple (hierarchical) password
protection implementation.
- Password protection mode is useful when several users are working with
"gwconfig" software and certain actions on gateway(s) must be performed
carefully. Different users may have different rights. The implementation
assumes that one user is the administrator of the "gwconfig" software and
the first step is to create such a privileged user.
- The definition of the administrator is achieved by the option "Users
definition".
- If you go to password protected mode without defining an administrator,
following error message will appear:
- For defining an administrator you must choose the option "User definition" ("
"). After entering the password "topex" in the access password window, the
next image will inform you that you must enter the identification data for the
administrator:
- After pressing "OK" button:
- To add a user to the list you must select "Add" button:
- In case of definition for the administrator account all possible rights are
already selected: "Changes allowed" and "Transfer allowed".
For each new user two fields must be always filled in: "Name" and "Password".
An additional window is used to confirm name and password.
- Only the administrator can define new users.

- He can add, edit and delete other users. As a safety rule the administrator
account cannot be deleted.
- Once the definition of an administrator is done, the subsequent access to the
icon "Users definition" (" ") will require administrator name and password:
- Also, to enter into password protected mode (when icon option "Password
mode" is selected (" ")) it is required the administrator's name and password.
Protected mode is shown on the title bar of the "gwconfig" software by the
words "protected mode" at the end.
- When protected mode is launched then another action on the icon "Password
mode" will end this mode.
- When protected mode is started then all access connections to the
gateway(s) will be protected by additionally user identifications.
- A user without any of the two rights (changing data and transfering files) will
be able only to connect to gateway(s) and see current status and settings
without the possibility to change data and transfer files.
- A user who has the right to transfer files will be able moreover to transfer
files from the gateway but not to change data.
Finally a user with all rights will have full control of the gateway(s).
TOPEX multiACCESS/QUTEX/EONES/multiswitch - Operations,

Administration, and Maintenance - SYSTEMS
1. Add
- If you select "System > Add" the following window will appear, asking you to
add another TOPEX multiACCESS/QUTEX system to the arborescent structure.
Directory - enter a name for the folder in where the files downloaded from
the TOPEX multiACCESS/QUTEX system will be stored.On HDD it will be made
a directory in the following shape "cfg_xxxxxxx" where directory is the name
typed in the "Directory" field. The folder will be created on HDD in the
directory where the executable 'gwconfig.exe' is located.
Name - enter a name for the connection to the system. This names is
concatenated at "cfg_" and this it will be the text used in tree structure for
identifying the system.
Serial communication / IP communication - is specified link type between
OAM computer and E1/30 GSM equipment. This are the two exclusive options
for the communication with a TOPEX gateway equipment.
IP Parameters:
IP address - enter the IP address of the system. It can be a numeric IP

address or a text address (in that case a dns request will be made by
software).
IP Port num - enter the number of the port through which the
communication with the system is achieved. The default value is 9009. This
value is established also into the gateway system and should not be modified.
DialUp Connection - in case of IP communication this setting allows if is
checked, a dialup connection to be established. The Dialup Connection must be
create from Windows (from "Dial-Up Networking") and the connection name
must not contained character space inside the text.
Option "Use PPP address" is used to indicate the "gwconfig" software to
connect to the dialup server address after a successfully connection. If this
option is not validated, then the "gwconfig" software will try to connect to the
address specified in the "IP address" field.
If this parameter is checked you may choose a dialup connection from "DialUp
connection name". You must enter a "DialUp Number" which override the
number used at the creation of the Dialup Connection. Also by pressing "Edit"
button you can override the "User" and "Password" used in process of
authentication.
You must note that if changes are made to "User" or "Password", those
changes are made also in the Windows registry.
The field "Connection Timeout" is the time in seconds wait from the moment of
starting the DialUp connection and the obtaining the connection state.
Serial Communication:
Serial Port num - enter the serial port used in case of serial communication
with the gateway. The default value is COM1. This value must be in range
COM1-COM12.
There is a text limit of 19 characters for the "Directory" and "Name" fields and
2 characters for the "Serial Port num".

A value check is performed for the serial port value. If the value is not in the
range 1 - 12, an error message will be displayed and the incorrect field will be
colored in red.
Also, value check is performed for the "Directory" and "Name" fields. If one of
this values is not filled or is the same as an already existent "Directory" or
"Name" (are used for another system), an error message will be displayed and
the incorrect field will be colored in red, as shown in the following image:
Save - saves the setting and adds in the tree structure a system with the
modified settings
Cancel - closes the window without saving the settings.
Note: in case of reduncancy when two processor card are used the "Add
system on position..." window will be different:
In this last window - you can notice one IP address, one port number and one
serial port number for each processor card.
2. Remove
- If you select "System > Remove" then you will see the next window:
- To remove a TOPEX multiACCESS/QUTEX system from the structure, select it

and then click on 'Save' button: the selected system will be deleted from the
tree structure; the folder (directory) on your hard disk drive won't be deleted,
you must erase it manually. If you select Cancel the window will be closed.
Note: There is also a tree command for changing systems parameters: Name,
communication type, IP Address, IP port number, DialUp parameters and serial
port number.

Administration, and Maintenance - FACILITIES
1. Font
If you select "Facilities > Font" the following window will appear:
In this window you can select according to your preferences the font, the style
and size of characters. The changes will only affect the windows called: "View
Configuration" and "Modify Configuration".
2. Colors signification
The significance of the colors used in the "View Configuration" and "Modify
Configuration" windows is here described, as explained below:
- Dark blue - that position is available (free)
- Red - that position is in alarm
- White - that position is already used (busy)
- Light blue - that position is not installed (the checkbox "Installed" from the
window for configuring the settings of the port has not been installed).
The colors which are here presented are the default settings.
There are also shown the colors used for "TextColor", "BackColor" and
"TreeColor".
All these colors can be modified according to users preferences by clicking on
it.
You can select the color you want, either from the predefined "Basic" colors,
either from the detailed zone of custom colors.
- The "Default" button is used to restore color settings to the original color set.
- The text column at the right of "Color signification" window explains the
meaning of values shown for a GSM port in alarm. When a user selects the
icon "Status monitoring" in a connected state, additional information will be
provided for GSM ports. If the GSM module is displayed in red color (therefore
no SIM registered) then after the port position and a line character a value is
shown, describing the cause of the error.
- example of a GSM module in alarm displayed in red color. Here the
cause of error "2" - "no physical SIM".
Possible error causes are:
0 - GSM module in initialisation phase (programming)
1 - no GSM network available ("at+creg?" phase)
2 - no physical SIM
3 - no logical SIM. This value may be obtained in the following situations:
- when the "SIM index" rule is used for changing the SIM cards for the GSM
module but for the current time moment no SIM value is specified in the "SIM
index".
- If "LOAD BALANCING" algorithm is selected to change the SIM on the GSM
module and the "Load Sim" value (the usage time of the SIM) is over the SIM
maximum time to use ("Max").
4 - GSM module error - the module is not responding at "AT" commands
5 - the GSM module is requesting PUK code
3. View print files
- This command is a facility for viewing text files located in "FORMAT" folder.
These files can be made by printing data into files from different locations from
program. To see a file, select its name from the list and click the 'View' button.
A window for viewing/editing the file will appear.
- You can also perform searches by using the buttons marked 'FIND' and
'NEXT' or you can send to the printer a listing of the file.
4.Commands
Use this option for entering direct commands for the system. This part of the
OAM program is "expert level only". You may resize or move the window
"Configuration manager on the screen as you wish. The windows position and
dimensions will be saved in a file on HDD in order to be preserved for future
use.
"Log Section" - if the option "LogFile" is checked, then a log file will be
generated. This file allows the user to analyse later the commands sent to the
gateway and the responses from the gateway. The logfile is always named
"command.txt". The option "Reset" is used to clear the file used for saving the
log.
The commands to be issued to the TOPEX gateway are filled in "OAM" edit
field, at the top of the window. A command is sent to the gateway after
pressing the <ENTER> key.
The command window is useful for several purposes. For instance it allows a
direct conversation with a GSM module (by using AT commands). The user can
also set PIN codes, start debugging, display the number of calls, etc.
"AT commands": if you want a GSM module to accept AT commands you
must put the associated port into a monitoring state (that port must belong to
an installed GSM board).
Therefore the first command sent for putting the GSM module into AT
commands accepting mode is "set moni xxx", where "xxx" is the GSM port
number (as it appears on the "gwconfig" panel). The gateway must send back
the confirmation message "moni xxx", where 'xxx' is the GSM port position. If
the GSM port can't be placed into the monitoring state the following warning
message is received: "res moni" (in the "Exchange response zone" section).
This message is received if the GSM port is busy or initialisations are
performed on that module. If that is the case the user must type first "res
moni' and then "set moni xxx".
When the confirmation from the gateway is received, several AT commands
can be sent to the gateway:
AT Command
Purpose
Response
AT
Allows the user to

check the
functionallity of the
GSM module
AT+CPIN?
-ERROR - there is no
The GSM module is SIM installed or there
interrogating about is another error
pin code. This is a
-READY - if no PIN
useful method to
code is required
check if a SIM card is -SIM PIN - the SIM is
plugged in a GSM
waiting for PIN code
module.
-SIM PUK - the SIM is
waiting for PUK code
This AT command is
used to check if the
module is registered
Should be "OK" in
case of success
The response is:

+CREG:<n>,
<stat>,"xxxx","xxxx"
where <stat> can be:
- stat = 0 - the
module is not
registered and does
not try to register to
a GSM operator
- stat = 1- the
within a GSM network
AT+CREG?
within the GSM

network.
- stat = 2- the
module is not
registered but is
trying to register to a
GSM operator
- stat = 3- the
registration is not
allowed
- stat = 4- unknown
- stat = 5- the
and he has roaming
AT+CLIR=<n>
where n=0 for
default,
where n=1 for
not sending the
identity and
n=2 to allow
the sending the
identity
The module is
responding with "OK"
with a delay that
This command is
depends upon the
used to enable or
loading of the GSM
disable the sending
network. Until the
of the identity (caller
response is waiting an
ID)
additional AT
command must not be
sent to the module
AT+CLIR?
+CLIR:1,4 - the
identity is not send
To check the setting +CLIR:2,4 - the
of identity
identity is send
+CLIR:0,4 - default
value
AT+CLIP=<n>
where n=0 for
not displaying To display or to not
the identity of display the identity
the calling part of the calling part in The module is
case of a call through responding with "OK"
and n=1 to
allow displaying the monitored GSM
port
of the calling
part identity
The response can be:
OK - the destination
part has answered

ATD<number>;
NO CARRIER - the
This is an useful
Where
destination part does
method to make a
<number> is
not respond or it is
call test directly from
the number to
not in the covered
the GSM module
be dialed
area
BUSY - the
destination part is
busy
Is used for
responding to an
incoming call. When
incoming call is
routed through a
GSM module which is
in monitoring state,
the "RING" word will The GSM module is
ATA
appear at each 5
seconds. If CLIP is
activated then a
message with the
calling number will
be displayed:
+CLIP:"calling
number",xxx
ATH
The command is used The GSM module is

to end a call
AT+COPS=?
This command will

detect and display all
active GSM operators
in the gateway area
AT+COPS?
This command will

display the operator's
name to which the
GSM module has
registered
First Command:
- AT+CMGF=<n>
where <n> is 1 for
text format and 0 for

PDU format. The
value to be used is 1.
The module will
respond with "OK".
AT+CMGS="number"
This command is
used to complete the
destination phone
Sending a SMS number.
The module will
respond with ">".
- @send <text
message>
This command will
send the SMS
- the response for
confirmation is:
+CMGS: <message
reference> OK
- the response for
error is:
+CMS ERROR:
<error>
AT+SIM=
<n>,n=0,1,2,3
(Note: here the
values for
identifying the
SIM card are
from 0 to 3
(instead of 1 to
4))
This is an useful
method to check if
the GSM module is
working properly:
the command is used
to set a new active
SIM (this is not a AT
command: it is a
command interpreted
by the controller of
the GSM card)
These settings are
made directly with
the GSM module.
The confirmation
response is "OKSIMn"
where "n" is 0,1,2 or
3 if that SIM was
selected
To release a GSM module from the monitoring state the command "res moni"
must be typed.
There are also additional commands that are interpreted by the gateway
application. The command "help" must be sent to see the list of available
commands:
set pin sim sss pppp
used to set the pin codes for GSM modules at

module "sss". The pin code is "pppp";
set pin range sss sss pppp
used to set the pin codes for GSM modules in

range "sss" to "sss". The pin code is "pppp";
set/res moni ppp
used to put / extract a GSM port from

monitoring state
send gsm at.......
(used to dial a number)
set debug ppp ppp
used to start debugging on a port. The port

for debugging purposes is completed in "ppp"
section: for example to activate debug for
port 1 the command is "set debug 1 2"
set view ppp
must be sent to port "ppp" after the

command "start debug ppp ppp" in order to
activate the debugging facility
res debug ppp ppp
used to stop debugging on port "ppp". The

port is completed in "ppp" section: to stop
the debugging for port "1" the command is
"res debug 1 2"
res view ppp

command "res debug ppp ppp" in order to
deactivate the debugging facility
set tmax sss sss ttt
allows you to define a time interval ('ttt') after

which a SIM will be blocked. sss is the sim
coresponding value. You may specify a range
of SIM cards values. Value of 'sss' may be
computed as follows: number of card (shown
in "Port status) * 8 + number of sim (0,1,2 or
3) for the first GSM module or number of card
(shown in "Port status) * 8 + 4 + number of
sim (0,1,2 or 3) for the second GSM module.
set tsim sss ttt
allows setting the time counter (loading time):

'sss' is the sim coresponding value and 'ttt' is
the value in seconds.
set calls
it is used for displaying the total number of

call attempts ("TCalls"), answered calls ("T
spech"), total duration of calls ("Dcalls"), total
duration of speaking ("Dspech) and the
number of calls released from "A" side
("Arelease") and from "B" side ("Brelease")
set calls off
this command is used to reset the previous

values
set block ppp ppp
command used to send block message on

SS7 signaling to channels in range ppp ppp
res block ppp ppp
command used to send unblock message on

set loop ppp ppp
command used to send loop message on SS7

signaling to channels in range ppp ppp
res loop ppp ppp
command used to send unloop message on

set tchange 1800/3600
speaking time period in seconds following

which the active SIM is changed
kill call port
this command disconnect an active call on a

GSM module. The position of the GSM module
is specified by the "port" parameter
test callbqack id
this command is used for making tests over

the quality of voice. In this chapter this
command is detailed presented
The following commands are used for settings concerning the second SIM
selection algorithm, called LOAD BALANCING. If you select the "equal load"
mode of work for the algorithm, each SIM on a GSM module will be used for a
certain period of speaking time, then the system will go to select the next SIM
card with the lowest load.
The commands are:
"set tchange 1800/3600" - speaking time period in seconds following which
the active SIM is changed (the gateway looks for the SIM card with the lowest
load for the same GSM module). Usual values are 1800 or 3600 seconds. This
parameter is the same for all GSM modules and can be viewed and changed in
any GSM settings window.
"set tsim sss ttt" - allows setting the time counter (loading time): 'sss' is the
sim coresponding value and 'ttt' is the value in seconds. Value of 'sss' may be
computed as follows: number of card (shown in "Port status) * 8 + number of
sim (0,1,2 or 3) for the first GSM module or number of card (shown in "Port
status) * 8 + 4 + number of sim (0,1,2 or 3) for the second GSM module.
Execute AT commands
In "Configuration manager" window the user is also able to execute AT
commands on all GSM modules.
The execution of these commands is based on a script file which is given as
command parameter. This file must be placed in the same folder with
"gwconfig" application. In this file the user can enter a batch of AT commands
to be executed over the GSM modules. The file must include the AT commands
you want to be to be executed over the GSM modules, the expected response,
the time delay to wait the appropriate response and the the option to save the
responses into a file.
The command to start this process is "execute -f xxxxx.txt" for all GSM
modules (where "xxxxx.txt" is the script file), or "execute -f xxxxx.txt -d GSM"
to start the process just for the modules belonging to the "GSM" direction. AT
commands are read from the "xxxxx.txt" file.
A window called "AT Commands Confirmation" is displayed for monitoring
the process.
In order to clarify this facility, here is shown a commented example of a script
file:
at+gsn
OK
10
1
at+cimi
OK
10
1
Each command is grouped as four lines:
1. AT command to be sent to GSM modules; (in the example above these
commands are "at+gsn" for IMEI code and "at+cimi" for IMSI code).
2. response wanted for the AT command; (in both cases the expected response
is OK; the expected value is included in responses before the "OK" text).
3. time to wait for the expected response; the next field is a value (0,1 or 2)
that has two meanings: the first significance (for a value of 0 or 1) is the time
delay to wait for the response at an AT command. If the response comes in the
specified interval then the process continues immediately. The second
significance, if the value read from the file is 2, is this: the application waits all
the specified delay and the last message received from the GSM module is
saved into a file.
4. an option about the saving of the response into a file; a 0 value means no
savings are done into a file, while a value 1 means responses will be saved in
"atresp.txt" file. If the value for the option is 2 then the last message received
during the waiting time will be saved in "atresp.txt". The option value of 2 can
be used to verify the credit for prepaid SIMs.
Notes:
- before sending any AT commands the application starts the monitoring
process (the same as selecting "Status monitoring"). This is done because the
application needs to know which cards are in alarm, which ports are in alarm
or in a call.
- this interrogation is performed just for the SIM cards currently registered.
Because AT commands can't pe sent to GSM modules which are in alarm, those
modules will be skipped in the process. For GSM modules where a conversation
is running, the commands are sent after the call is dropped. When the current
interrogation for a module has reached the last port, then the process will be
restarted for the skipped modules. The total number of restart cycles is 2.
- after a new interrogation process is started (after an "execute" command is
performed) the file "atresp.txt" will be deleted.
The first column representing the port
position. The second column displays
the current "Status" of executing AT
commands over that port. Possible
values are:
- WAITING - AT commands are not
yet sent to the port; (light blue colour
background)
- FINISHED - AT commands have been
succesfully sent to the port; (dark
blue background)
- CONNECTED the port was found in
a call at the time when it was
supposed to be placed under the
process of executing AT commands;
(red background). Call is dropped. AT
commands are sent.
- PORT ERROR- the port was found in
alarm at the time when it was
(red background). The port will be
interrogated in the next cycle.
- TIMEOUT- there was a timeout for
receiving responses for an AT
command; (red background). The port
will be interrogated in the next cycle
- CARD ERROR- the card to which the
port belongs was in alarm when the
application was tried to execute AT
commands for that port; (red
background). This port will NOT not be
- UNINSTALLED- the port is not
placed on any direction or the INST
category is not given; (grey
background). The uninstallled port will
NOT not be interrogated in the next
cycle.
- The third (rightmost) column shows
the number of interrogation cycles.
The maximum number of restart
cycles is 2.
Voice Quality Tests - In the same "Configuration manager" window the user
can to perform tests over the quality of voice on two GSM modules. In order to
make those tests, the user must first define the ports on which he wants to
make the tests.
This selection is done in the "Callback Table":
<identity (number) to test quality of voice> 1 <code 1> <code 2>
The first field of the line is an arbitrary number used to start the test of the
quality of voice. The second field must be "1" (callback functionality). The last
two fields are containing the prefix used in routing table, the GSM port
number and the number to call.
<code1>=<prefix>+032+0744000001 (GSM port position - 032, number to
call -0744000001 )
call -0744000002 )
The Topex gateway will call the GSM module on first port, and following its
answer, it will connect the two, allowing you to check the quality of voice for
the respective connection.
For example:
9999 1 720320720000000 720330740000000 - the identity used for test is
"9999". The prefix used in routing table for the test service is "72". First GSM
port is 32 and the second is 33. First number to be called is "0720000000" and
the second one is "0740000000".
In routing table must exist a record to route "72" (the test prefix) to SERV
("Action" = SERV) and destination "11".
The command to start the voice test is performed from "Configuration
manager":
test callbqack 9999
When the last command is executed, the gateway calls the first number
0720000000 from port 32. When the calls is answered at destination, the
second part of the test is done. The phone number 0740000000 is dialed and
the two are connected.
This way you can connect two by two all of the GSM ports of the gateway and
test the quality of the voice on the respective connections.
Linux commands
Also you can type in the "Configuration manager" LINUX-like commands that
will be sent to the connected gateway. The syntax must always begin with
"system" characters. After a separation character (space character) a LINUX
command may follow. By pressing ">" character after a command the software
automatically adds the destination file for the command output. This
destination is by default "/mnt/app/out/out". After such a command the user
may analyse the output file by selecting the "Output File" icon command (" ")
from the toolbar.
5. Licence
This last option of Facilities menu is used to send a license message to the
Topex gateway.
The purpose of the "license" feature is to implement control over the timelimited application running on the gateway. This limited application will serve
incoming calls only for a specific number of days. After the expiration of this
period, the application will no longer process the calls. A license message is
sent by Topex company, message that is unique for each gateway (it can't be
used with another gateway).
Licenses can enable the control over some of the gateway's features. The
available features are:
- Basic
- SS7
- VoIP
- Callback
- Portability
- Tax - Pulses calculation
The license-enabling message consists of several lines. This message can be
received by the customer as an e-mail message. The user copies the message
into the "License" window and it send to the gateway.
The gateway should answer with the confirmation message: "LICENCE
ACCEPTED". If the license message is not valid, the answer will be "LICENCE
REJECTED". If the license is accepted then the number of working day is
displayed in the status bar.

Administration, and Maintenance - ABOUT
If you select "About" the window shown below will appear in order to tell you
what version of application software you have installed. Select OK to close this
windows.

Administration, and Maintenance - HELP
This is the command for showing this electronic manual.
The left pane of the help window shows an index of pre-defined keywords
where you can search for the item (Icon command, menu command, Tree
command, general considerations) you want to learn about.
The right pane offers detailed pages structured as "Menu description"
(Systems, Facilities and so on) and respectively "Tree Commands" (Connect,
Disconnect, Alarms, Billing etc) and "Icon Commands" ("Gateway Parameters",
"Directions Names", "Call Directions", "Routing Table", "LCR Table" and so on).
The left pane of the help screen also include the search facilities. You click on
the "Search" tab and enter the word or the expression you want to look for,
for example <<billing files>>, then click "List Topics" to start the search: The
help program will display all the occurences it has found, together with the
name of the help page where they are located and and the rank (1,2, 3 etc).
Please note that, according to the general rules for text search, if you enter
several words in the "Search field", the help program will look for occurences
of EITHER word. This is like telling the help program <<search for 'billing" OR
for 'files">>.
If you want to be more specific, you should select the boolean operator AND
instead of OR. For instance, if you want to know about the billing files, you
must search for "billing files", using quotes. In this case, the help program will
display only the occurences where ALL the words inside the quotes are found
together.
You select one of the occurences and click "Display" to show the respective
help page in the right pane. The words or expressions you look for will be
highlighted (marked with reverse video). If you want to search further inside
the help page, press Ctrl F and a "Find" window will show up. You type the
expression to search in the field "Find what", You may select additional
options: "Match whole word only" and "Match case" if you want to narrow the
search. You must specify the direction of the search inside the page, Up or
Down. "Find Next" shows the following occurence of the word you want to
search.
The Search function of the help program remembers the words you entered,
even if you close down the help. When you run "Help" next time the same
word or expression will be displayed.

The window of each command now has a "Help" button of its own. This means
that you no longer need to issue the "Help" command and then search or the
item of interest. When you run a command, for instance "Add System", you
just click its "Help" button and the respective help window will be displayed,
showing you information about that particular command.

Administration, and Maintenance - CONNECT...
1. Connecting steps
First click on the Connect property and wait until the connection with the
remote TOPEX system is established.
A dialog window will appear after the connection was successfully established.
The login procedure on the remote equipment will follow.
A dialog box will appear and in case of connection successfully established the
OAM program tries to download the configuration information, as follows:
File with information about the installed cards ("card.cfg");
File with information about the port settings ("port.cfg");
. File with information about directions name ("dirname.cfg");
File with information about established directions ("dir.cfg");
File with information about the SIM modification table ("simindex.cfg");
File with information about restrictions established ("restr.bin");
File with information about pin codes on GSM/UMTS interfaces ("pin.cfg");
File with information about loading on GSM/UMTS interfaces ("loadsim.bin");
File with information about maximum usage time on GSM interfaces
("tmaxsim.bin");
File with information about the LCR table ("lcr.cfg" - LCR is an abbreviation to
Least Cost Routing);
File with information about the CALLBACK table ("callback.cfg");
Files with information for defining the parameters for alerting and
programming of the test calls ("trafic.cfg");
File with information concerning the parameters used for communication

between a Topex gateway and the "gwconfig" application, and the parameters
used for debug purposes ("exec.cfg");
File that contains the IP settings of the gateway ("network.cfg");
Files with information about the signaling point allocation ("mtpcfg") and CIC
(circuit identification codes) allocation to gateway ports ("isup.cfg"), files used
in case of SS7 card presence;
- Files used for VOIP-H323/SIP configuration: "voip.cfg" and "h323.cfg" and
"sip_pbx.cfg".
There are progress indicators for all of these files. All these files create a
gateway configuration. The "gwconfig" application allows the user to save a
gateway configuration into a separate location (directory). Then you can edit
(modify) this configuration and later upload it to one or more TOPEX gateways.
There are a few situations that can occurr while attempting to connect:
1.The OAM program tries up to four times to connect to a system. If it can't
connect at the fourth retry it displays the following error message: "Passing
Connection Retry Error".
2. In the case of passing fourth attempts for login the following error message
will appear: "Passing Authentication Retry Error". User will not be able to
view or modify system configuration.
3. If the program does not receive from the system one or more of the
configuration files, it displays the following error message:
"Downloading Configuration Failed". User will not be able to view or modify
system configuration.
4. If the dialog process between system and OAM computer falls (up to a
number of consecutive errors) a "Passing LAPD Retry Error" message
occurs.
5. If connection breaks down (because of IP) during the configuration
downloading process or during the connected state, a "Connection Lost"
message appears.
You can only connect to one TOPEX system at a time. So if you want to
connect to another system, you must first disconnect from the previous one.
Please note that there are two types of windows used by the program. There is
one window displaying the content of the files and another window for viewing
and changing the configuration (settings) of the Topex systems. When you
work with files content you will be able to operate upon the commands from
the tree-like structure for the equipment you want and with the right mouse
button you will be able to hide the window. If you work (change or view) with
a certain configuration, this can be hidden using the right mouse button. If the
OAM program is in the state of connection to one of the systems, by clicking
with the right mouse button over the status bar, you will make pop up a
window with the option of disconnecting from the current system.
Note:
- In order to allow additional facilities, the application may also be launched
together with the following parameters:
1) The OAM software includes a protection against starting more then one
instance. If it is necessary to start the software more then one time, you
should use the following command to start the software: "gwconfig.exe -d"
or "gwconfig.exe -D".
The D parameter allows simultaneous administration of several Topex
gateways.
2) Parameter "-c" or "-C" allows automated connection of the administration
program to a TOPEX gateway. The c parameter must be followed by a space
delimiter and the three following fields: identification name for the remote
system, user name and password (to allow automated log-in).
For example: "gwconfig.exe -c TEST,<username>,<password>".
In case of redundancy when the password is not explicity requested - this
parameter ("-c") must be used to provide the username/password to connect
to each processor card.
3) Parameter "-s" or "-S" allows saving of several types of date. The
information saved concerns the status of activation of monitoring, live
monitoring and interrogation about mobile network information (cell IDs and
signal levels).
For instance "gwconfig.exe -s" or "gwconfig.exe -S"
4) There are situations in which the configuration contains files with large
dimensions and the process of downloading is taking too much time. In such a
situation the "z" parameter must be used in order to compress and transfer
from and to proccesor card the compressed files.
All these parameters can be combined and added to the command line.
Note: if another user is connected at the same time with the "gwconfig"
software from another PC, when you try to access the Topex gateway you get
the following error message:
This message indicates the IP address from which the connection to that
gateway has already been accepted.
5) in case of TOPEX equipment with redundancy (multiswitch or EONES) - the
application is connecting to each processor card but the configuration is not
automatically downloaded like in a normal case. During the system setup - the
user connects to each processor card and downloads the current system
configuration - - Downloading Configuration. Every change made from OAM
will be done on both processors in the same time. If one processor card is
changed - then the current configuration can be send through the upload icon:
- Upload Configuration
2. Configuration modifier
Once the configuration files are downloaded, in the right side a "Modify
Configuration" window will be displayed. In this window you can view and
change the current configuration (settings) of the equipment.
In the previous image (valid for multiACCESS/QUTEX equipments) you will

notice:
- a menu bar with names such as "Systems", "Facilities", "About", "Help" and
"Exit";
- underneath, a toolbar with different buttons marked with icons;
- to the left, the tree-like structure of installed gateways;
- the right panel, blue, which is the main window;
- in the upper corner, the flags for selecting the language;
The previous image is different for an EONES equipment. The EONES system
can contains up to 11 digital boards. On the OAM pane the EONES structure is
divided on succesive screens, with three slots each. Every slot may hold a 2E1
trunk or a VoIP card. The main difference between multiACCESS/QUTEX OAM

panel and the EONES panel are the navigation arrows that allows you to go
from one configuration screen to another - arrows which are located on the
bottom right zone of the OAM pane.
Note: there is also a situation when an TOPEX EONES is slave of another
TOPEX - case in which there will be 22 E1 or VoIP slots. For example you can
have a multiswitch master with
an EONES slave.
At the bottom of the screen (bottom left corner) there
are left and right navigation arrows. These arrows allows
you to go from one group of three slots to the next
one or to go back
.
Types of boards:
Analogue
Subscriber board
multiACCESS/QUTEX
8 ports (FXS
card)
GSM/UMTS/CDMA
modules board 2 multiACCESS/QUTEX
ports
PBX junctions
board 8 ports
(FXO card)
multiACCESS/QUTEX
E&M junctions
board 4 ports
multiACCESS/QUTEX
BL phones board
multiACCESS/QUTEX
8 ports
Radio board 4
ports
multiACCESS/QUTEX
NT/TE
ISDN-BRI board
with 4 ports
multiACCESS/QUTEX
E1R2 board (32

channels)
multiACCESS/QUTEX/EONES
E1ISDN-PRI
board (32
channels)
E1SS7 board (32

channels)
E1R1 board (32

channels)
VOIP card - with

H323 or SIP
protocol (8,16,32
or 64 channels)
RG
For multiACCESS/QUTEX systems, the configuration window is divided into

three distinct areas:
- Port status: the analog boards ports (subscriber (FXS), GSM, PBX (FXO),
E&M and BL) are viewed;
- Trunk status: the E1 trunks or VOIP channels are viewed;
- Card status: the boards inserted in the system rack are viewed;
For EONES/multiswitch systems, the configuration window is divided into two
distinct areas:
- the area with SLOTs - on each succesive screen - the OAM pane displays
hree slots. Every slot may hold a 2E1 trunk or a VoIP card; The middle of the
screen shows groups of three slots each, numbered 0,1,2 , 2,4,5 and so on,
up to 9,10,11. You may install up to 11 (eleven) digital boards (2E1 or VoIP)
in an EONES system, so the last slot, no 11, will be always empty.
For the case of an EONES slave - the total number of slots will be 22.
For the multiswitch system - if RTP proxy is needed - for example in case of
SIP users behind NAT - then a VoIP card will be declared (but not physically
present). Otherwise - the configuration can be empty. If transcoding is needed
then a TOPEX multiaccess or QUTEX equipped with a VoIP card will be declared
as slave to the softswitch configuration.
If a SS7 card is present into the gateway configuration then another zone will
show up on the panel: "Remote SP accessibility".
2.1. PORT STATUS (multiACCESS/QUTEX)

- In the Port Status area each column represents an analog board physically
installed in the rack of the equipment. You can have maximum 16 boards for
multiACCESS equipment (128 ports) or 5 boards for QUTEX equipment (40
ports). Each port is shown as a small rectangle marked with a letter
(character) followed by a three digit number. The letter is an identifier for the
type of board (Ex. the GSM modules boards feature the letter G"). The
number that follows the letter is the port position. Each rectangle also includes
under the port value a text which corresponds to the direction name to which
the port is allocated (this text is limited to 6 characters).
- Port representation is from right to left and on a card from up to down
(position on a card from 0 to 7).
- For a GSM/UMTS/CDMA board the number which follows the "G" character is
calculated by multiplying the card number (the number which is written under
the rectangle with the card representation) with 8 and adding the position on
the board. For example GSM module "G040" is located on card 5 at first
position (5*8+0=40). Module "G041" is located on card 5 at second position
(5*8+1=41). The rule applied is number of card * 8 + position on the board.
- The port representation is changing when the user selects the icon "Status
monitoring" in a connecting state. Then the color used to display each port is
changing according to the port status: used port- white color, port in alarm red color, invalid position -light blue (invalid position means "Installed" field
not set or card error) and available port - dark blue. A detailed explanation
will be presented later in this chapter ("Monitoring"). For a GSM module it will
be presented in case of a registered SIM, the active SIM card (in the next
example is the first SIM).
- example of a GSM module displayed in dark blue color which is placed
on direction "GSM". The active SIM card on the "032" module is "1".
If the GSM module is displayed in red color (therefore no SIM registered) then
after the port position and a line character it is presented a value from 0 to 5
which describes the cause of not having a registered SIM on that position.
- example of a GSM module displayed in red color with the cause of error
"2" meaning "no physical SIM".
- Each port from each card can be individually configured by clicking with left
mouse button on corresponding port.
- Depending on port type different parameters may be set:
Port type
Category Direction Number Restriction
Hunting
Group
Pickup
Group
Target
SIM
Index
S
YES
(Subscriber)
YES
YES
YES
YES
YES
YES (for "BC"

settled)
NO
G (GSM)
YES
YES
NO
NO
NO
NO
NO
YES
P (JPABX)
YES
YES
NO
NO
NO
NO
YES
NO
E (E&M)
YES
YES
NO
NO
NO
NO
YES
NO
B (BL)
YES
YES
YES
YES
NO
NO
YES
NO
2.2. TRUNK STATUS (multiACCESS/QUTEX)

- By default, only one digital card (2E1 or VOIP) can be used in a TOPEX
multiACCESS or QUTEX gateway.
For a multiACCESS system: it must be inserted on position to the right of the
PG (Processor Card); According, in the "Trunk Status" window only two Trunk
rectangles can be filled with channels (if they were declared), the other two
will be empty (like in the next image); Upon customer's request, the backplane
of the multiACCESS gateway can be modified to accomodate two digital cards
(2E1 or VOIP); for example you can have two 2E1 cards ore one 2E1 card and
one VOIP card. They will be inserted on positions to the left and to the right of
PG. In this case, on the screen in the "Trunk Status" area all four rectangles
can be filled with channels. Older versions of the multiACCESS used 1E1 cards,
that is the E1 board had a single E1 interface. Consequently, on older TOPEX

gateways you may use by default only one E1 trunk - placed on position to the
right of PG. If you replace the old 1E1 card with a 2E1 card, you may have two
E1 interfaces. The maximum number of E1 interfaces which can be installed in
a TOPEX multiACCESS is four and this is the reason why in "Trunk Status"
zone the representation contains four E1 trunks.
For a QUTEX system: QUTEX allows you to use up to 3 cards of 2E1. the
number of 2E1 cards that can be used in the front side of the equipment is
configured only by the manufacturer.
- if you use 3 cards of 2E1 is important to know that the equipment cannot be
equipped with VoIP cards or other subscriber cards. In this case the maximum
number of E1 interfaces which can be installed in a TOPEX QUTEX is sixth and
this is the reason why in "Trunk Status" zone the representation contains sixth
E1 trunks.
- If you use only a single 2E1 card - you can install it on the back side of
QUTEX equipment (near the processor card). The other 5 cards positions can
be filled with FXS, FXO, GSM or ISDN-BRI cards.
- If you use two 2E1 cards, one will be installed on the back side and the other
on the front side on the first slot from the base. The other 4 cards positions
can be filled with FXS, FXO, GSM or ISDN-BRI cards.
- If you use three 2E1 cards, one will be installed on the back side, and the
others on the front side on the first slot and on the last slot
- If you are using a VoIP card - the VoIP card will be always fixed between the
power supply card and the processor card. Additional 2E1 card can be installed
on the front side of the QUTEX equipment.
- for a QUTEX system - the user must be aware about the number of available
card positions (for FXS, FXO, GSM and ISDN-BRI)- positions from 0 to 4 can be
available in case when just a 2E1 card or a VoIP card is installed. If another
2E1 card is used then just positions from 0 to 3 are available.
2.3. SLOT STATUS (EONES/multiswitch)

You can have maximum 11 digital boards on an EONES equipment. Every slot
may hold a 2E1 trunk or a VoIP card. The middle of the screen shows groups of
three slots each, numbered 0,1,2 , 2,4,5 and so on, up to 9,10,11. You
may install up to 11 (eleven) digital boards (2E1 or VoIP) in an EONES
system, so the last slot, no 11, will be always empty.
The alarms for the respective E1 boards are also shown as rectangles with
corresponding names: LIS, AIS, LFA, RJA, BER, etc. The color of these
rectangles turns to red in case of emergence of an alarm.
2.4.1. E1 card
- The E1 representation of an E1 trunk features on the first two rows the
channels. For each channel, the type of the E1 interface is shown as a small
rectangle marked with a letter, followed by a two-figure number - the number
of the channel. The third row includes representation of the alarm buttons.
Each alarm button is marked with an abbreviation for the type of alarm it
represents, as described in the table below:
LIS Loss of Incoming Signal
AIS Alarm of Indication Signal
LFA Loss of Frame Alignment
RJA Remote of Junction Alarm
LMA
Loss of Multiframe Alignment (not for

an IDSN or SS7 interface)
RSA
Remote of Signaling Alarm (not for an

IDSN or SS7 interface)
BER Bit error rate
- Code representation used on drawing the E1 channels:

D
E1R2 trunk channel (32

positions on a E1 trunk)
E1ISDN trunk channel ISDN

(32 positions)
T E1SS7 (32 positions)

R E1R1 (32 positions)
- Each channel from each E1 interface can be individually configured by

clicking with left mouse button on the corresponding channel. For each
channel the "Category" and the "Direction" parameters can be settled.
-Up to four E1 trunks can be represented.
-In the following picture an E1 - SS7 interface (letter "T") and an E1 - ISDN
interface (letter "I") are displayed.
- The indication "SC" is used to highlight the signaling channel.

- In the previous representation with the E1 trunks, the card number is
displayed in the right side of each trunk. The trunks can be placed on card 16
(trunk 2), 17 (trunk 3), 32 (trunk 6) and 33 (trunk 7).
- In case of a 2E1 card, the position on the right side of the processor card is
32 (this means that the first E1 interface is located on position 32 and the
next interface is located on position 33). The position on the left side of the
processor card is 16 (this means that the first E1 interface is located on
position 16 and the next interface is located on position 17).
- In case of a E1 card, the position on the right side of the processor card is 32
and the position on the left side of the processor card is 33.
2.4.2. VOIP card

- The VOIP card representation features four rows, each with 16 channels.
The total number of channels is 64 (compressed voice channels). For each
channel, the type of the VOIP card is shown as a small rectangle marked with
a letter, followed by a two-figure number - the number of the channel.
Depending on customer needs, the VoIP card can be delivered with 8,16,32 or
64 channels.
- letter 'V' is used for code representation for drawing the VOIP channels:
- A VOIP card is used instead of a 2E1 board; it can be inserted in the rack of
the gateway on card positions 16 or 32. The protocols supported are H232 and
SIP. The codecs used are G711, G723, G728, G729. Please note that the first
two channels on the VoIP card ("V00" and "V01") can't be used as valid voice
channels.
2.5. CARD STATUS
In the area "Card status" of the window, the first row is a representation of the
status of the boards installed in the cabinet of the equipment. Each board is
shown as a small rectangle marked with the number of the card in the 19"
rack.(from right to left). The current status of the board is shown by its color.
The second row shows the status of the E1 trunk board: cards 16,17, 32 and
33.
2.6. LinkStatus & REMOTE SP ACCESSIBILITY
This zone is displayed only if a SS7 card is present into the gateway
multiACCESS/QUTEX/EONES configuration. This zone is a representation of
the accessibility of the remote (adjacent or non-adjacent) signaling points.
The TOPEX gateway can handle connections to maximum 32 signaling points
(SP) which are represented by boxes with values from 00 to 31. Values from 0
to 11 are used for adjacent signaling points and values from 4 to 31 for non-
adjacent signaling points.

The used colors in displaying the "Remote SP accessibility" bar are:
- connection to a SP not installed - light blue
- connection to a SP installed - dark blue. The information regarding the
installed SP connections is reading from the "MTP Configuration" file (" ") the enabled routes (option "Route x" where x is from 0 to 31).
- connection error (alarm) to a SP installed - red. This information is reread at
each 60 seconds.
On the EONES system - the "LinkStatus & Remote SP Accessibility" zone is
displayed on the last OAM pane screen - the screen which contains the last
three EONES slots (9,10 and 11)
2.7. EONES - structure of slots

For EONES equipment - the type of each slot is declared in the bottom side of
the screen using the " " icon. As you can notice in the next picture, there is
a list with all slots (named "PG"), slots starting from 0 to 11. The "Type" of
each slot is 'E1' for E1 cards, 'VoIP' for VoIP card and 'Not Used' for slot
unused.
For softswitch and for configuration with EONES slave - the ">>" button will
be used to navigate to slots 12-23.
The "IP Remote" and "Port Remote" are not used in EONES configuration - are
used in master-slave configuration. The "Rez1" and "Rez2" fields are keeped
for further developments.
The "IP Private VoIP" and "IP Public VoIP" fields are used for EONES and
represent the VoIP private IP - the VoIP IP card and VoIP public IP. For VoIP
slots a new line must be filled - the corresponding "VoIPx" line. For example
the next line corresponds to slot 0 and contents the processor card address 192.168.161.3, the MSPD port - 9677 (for the next VoIP card it will be used
9675, 9673, 9671 and so on). It follows the gateway MAC behind which the
EONES is located (it is the same for all EONES VoIP card) and the VoIP MAC
card.
voip 0 2 192.168.161.3 9677 fork /mnt/app/bin/mspd -p 9677 --trace-cmd -v
--mem 16 --gw-mac 00:48:54:1A:D2:8D -m 00:52:C2:40:3E:40
192.168.244.150 --log /mnt/app/out/%d-%m-%y_mspd.log -
Please notice that in case of EONES - the VoIP configuration is performed here
on "PG configuration" - slot configuration. On "VOIP Configuration" window the "PG Card IP Address", "VoIP Card IP Address", "Public IP Address", "VoIP
Card MAC" and "IP GATEWAY MAC" will be empty.
The "RTP_IP" button is used to fill the IP used in RTP packets. This value can
be different if the TOPOX equipment has more then one ethernet interfaces.
3. Changes available by icons

3.1. Downloading Configuration
This option (icon) is available in case of a TOPEX EONES or multiswitch
equipped with redundancy. The first step is to select the processor card from
which the configuration is downloading:
The configuration is downloaded from the selected processor card.
When the configuration is downloaded - the next window appears asking for
taking over the new configuration. If the answer is yes - then the
configuration will be displayed in the OAM panel.
I
3.2. Uploading Configuration
equipped with redundancy. The first step is to select the processor/processor
cars to which the configuration will be uploaded:
Once the processor card is selected the uploading process is started.
The confirmation message for succesfully uploaded is "The new configuration

has been uploaded!". If an error occurs the message will be "Uploading
configuration Failed".
3.3. Save Current Configuration
A configuration is the collection of files which are downloaded from a gateway

during the connection progress. These files describe the mode of working for a
TOPEX gateway. The "Save Current Configuration" (icon " ") may be use only
in a state of connection between the "gwconfig" application and a gateway.
The next image is displayed allowing the user to type the "Configuration
Name":
After the validation of button "Save" a new item will appear in the tree window
located in the left side of the application panel. The name which was typed in
the "Enter Configuration Name" will be presented together with characters
"viz".
Note:the gateways to which the user is able to make connections will have
characters "cfg" before the gateway identification name.
There are two possible options for a saved configuration:

- "Edit" - this option will display the saved configuration in the same manner
as for a connected gateway. The user is able to make changes. All settings are
preserved when the user choose the "Close" option.
- "Close" - this is the option to close the "Edit" configuration mode. Click "OK"
to hide the configuration window.
3.4. Upload Edited Configuration

This option is used in a state of connection between "gwconfig" application and
a gateway. The icon " " is used to launch the uploading process. First step is
to select in "Uploading CONFIGURATIONS" the desired configuration to be

upload. All available configurations are displayed in a list. The user must select
a configuration then press the button "Loading".
The uploading process is started. The progress of gateway uploading may be

followed in the "Uploading configuration" window.
A confirmation message is displayed when the uploading process has ended.
The "gwconfig" software will display on the screen the new configuration. The
configuration is used also by the gateway main application.
3.5. Gateway Parameters

By clicking the "Gateway Parameters" icon (" ") a window for editing several
gateway parameters is shown. These parameters are regarding IP address,
firewall, serial connectivity and IP connectivity with "gwconfig" software,
debug, syslog and SNMP messages to be generated by Topex gateway.
Network settings - this zone allows the user to change the IP address of the
gateway (in the image the record started by "IPADDR"). Also the user may
change the netmask (line started by "NETMASK") and the gateway address
(line started by "GATEWAY"). A line which is started with "#" character will be
not taken into account. The gateway must be restarted after one parameter
from the "Network settings" was changed. The icon used for restarting the
gateway is " ".
Connection zone: these settings are related to the serial connectivity and IP
connectivity of the TOPEX equipment with the "gwconfig" software. The
command "Parameters" located in the "gwconfig" software is related to the PC
communication parameters. The parameters set for the gateway must
correspond to those established for the OAM program.
Serial Speed - the value is used for serial communication between OAM
program and the software of the gateway. Allowed values are 0 (it means
unused port and must be set when you want to install a dialup server on the
gateway), 4800, 9600, 19200, 38400, 57600 and 115200 (default value);
Serial Port num - specifies the number of the serial port on the gateway to be
used for serial connection with OAM software. Allowed values are 1 or 2 and
the default is 1 (COM1);
IP Port num - the port used for IP connectivity; the default value is 9009. If
this value is changed from OAM software, then the connection will be
immediately lost. You must have the same port number established both in the
OAM program and in the software running on the TOPEX gateway. After
performing a reset, the OAM software will be able to connect to the gateway
using the new value of IP Port.
Firewall - in this edit zone - user can add incoming firewall rules. Each line
from the edit zone must contain three fields.
- first field is the connection type ("tcp" or "udp");
- next the IP address follows - it represents the IP address from which the
connection to the port specified in the third field is allowed.
- third field represents the port on which the connection is accepted.
For example "tcp 192.168.1.6 22" means that a TCP connection is accepted on
port 22 (SSH port) from "192.168.1.6" address.
To enable firewall protection you must uncomment some lines of the
configuration file.
For this, remove the "#" character from the beginning of these lines:
"LAN=ppp0",
"WAN=eth0"
"USE_FIREWALL=yes"
After this operation is done, you must reboot the gateway for the new
settings to take effect.
Attention!
Be careful when you use the embedded firewall. If the firewall protection
is started without the of presence of valid lines in the "Firewall settings", then
the Topex gateway will be no longer reachable from IP. In that case, the only
solution for accessing the gateway is to use the serial connection via the COM2
port of the PG card. Use this serial connection to fix the firewall settings, then
you will be able again to access the gateway via IP.
Debug
Activate 'log' file - when the option is checked the debug messages will be
generated in the debug log of the TOPEX gateway. These debug files have
extension "log" and the name corresponding to the current day (format daymonth-year: dd-mm-yy).
db_alarms - when the option is checked the alarm messages will be shown in
the debug log of the TOPEX gateway.
db_cfg - when the option is checked any changes on gateway configuration will
be shown in the gateway debug log.
- the option sets the debug mask that establishes for which subjects will be
generated debug logs. The items that may be recorded in the logs are: "Port
Activity", "ComCCS", "SOmes", "comUNIX" and "comOAM". To edit the "Debug
Mask" field, the button "..." must be pressed. Then the "Computing Debug
Options" window will be displayed.
- "Port Activity" option is used to generate debug records for all ports of the
TOPEX gateway;
- "ComCCS" is used to generate debug records for communication with the
ISDN and SS7 applications;
- "SOmes" is used to debug the main application which is running on the
TOPEX gateway;
- "comUNIX" is used to debug the commands which are received from the web
server;
- "comOAM" is used to debug the communication with OAM software.
Here you just check the boxes for the options you need to generate debug
information.
Samples of messages from a debug log of a TOPEX gateway:
If option "db_alarms" was set then messages preceeded by "RUN" will appear
in the debug file:
RUN Com Err cd f cat 43 (this is an alarm message on card 'f' which is card
number 15 from the gateway)
RUN Com Err cd 10 cat 4003 (this is an alarm message on card '10' which is
card number 16 from the gateway)
RUN NLIS 4 (LIS error on card 32)
RUN NLFA 4 (LFA error on card 32)
RUN NAIS 4 (AIS error on card 32)
RUN NRJA 4 (RJA error on card 32)
If option "db_cfg" was set then messages preceeded by "CFG" will appear in
the debug file:
CFG Open for read ../cfg/trafic.cfg
CFG Alarm run 0 ASRalarm 80 timeasr 12(min) nr min calls 1 alarmmask 0
timetest 0
CFG Save ASR at 30 min
CFG Debug 1 Pstart 0 Pstop 320 SaveFile 1
CFG Trafic run 0
CFG Trafic idle time 5
CFG Trafic seize time 30
CFG GEN TRAFFIC CALL 0 1234567891108 120 port 257 mod 0. These
messages contains operations performed over the configuration files.
If option "Port Activity" is validated in the creation of debug file then messages
starting with "OAM" will appear in the debug file:
00257 7235150 pid 1 E1CCSidle ACTIV channel 1
00257 7235150 Digits 1234567891108 Ident 120
00257 7235200 Route N 123456 ... NT 123456 ... RxT 9000
00257 7235200 Dialdig M_CALL len 30
00258 7235200 pid 2 E1CCSidle CALL mod 1 mycat 540f b_pid 1 prtb 101
param 0
00258 7235200 Digits Ident 120
00257 7235250 Dialdig ACK_CALL->Dialdest
00257 7250250 Dialdest TimeOut
00258 7250250 E1CCSackout TimeOut|CANCEL ->BUSY. In this case
messages were generated for ports 257 and 258.
If option "SOmes" was validated in the creation of debug mask then messages
starting with "GEN" will appear in the debug file:
GEN COADA 6 TRI 145 TRA 5 CPS 508 CPL 256 DTMF 0 R2 0 CH 0 CMD 0
GEN Local Time Wday 03 Mday 07 Date 07-04-04 Hour 11:19:10 SysDay 2
GEN Run60sec 6872131 us Tcalls 15 Tspech 0 Dcalls 1 Dspech 0 Arelease

1,Brelease 0
1,Brelease 0
If option "comOAM" is validated in the creation of debug mask then messages
OAM ADD CARD 16 CAT 4003 (this is a message which indicates that the card
16 was added to the gateway. Value "4003" is a category which describes the
type of card.)
Syslog - if you activate this option (by checking the box "Activate") the debug
messages can be sent to a selected IP address. This Syslog is an UNIX-like file
feature that allows logging of debug messages and sending them to a remote
machine. The destination IP address is written on target in the file
"/etc/syslog.conf". All logged messages will contain the identification of the
gateway (you enter the identification in the field "Equipment IP").
The type of syslog messages is chosen from the "Facility" list: "LOG_USER",
"LOG_LOCAL0", "LOG_LOCAL1", "LOG_LOCAL2", "LOG_LOCAL3",
"LOG_LOCAL4", "LOG_LOCAL5", "LOG_LOCAL6" and "LOG_LOCAL7".
syslog_alarms - when the option is checked the alarm messages are sent to
the syslog destination;
syslog_cfg - when the option is checked then any changes made upon gateway
configuration will be also sent to the syslog destination;
Syslog mask - is similar to debug mask. This option establishes for which item
("Port Activity", "ComCCS", "SOmes", "comUNIX" and "comOAM") the syslog
message will be generated. Click on "..." button and the next window shows
up, allowing you to select the items which will be included in the syslog.
SNMP - if you activate this option (by checking the box "Activate") alarms can
be sent as traps to a selected IP address ("IP destination"). The user can
choose the type of the trap (default value is 6 - "Entreprise Specific"), the
community name (default value is "public"). For an alarm appearance - the
value sent is 0, and for an alarm disappearance is 1. You can allow that
together with the trap containing the 0 / 1 value, a second trap with the alarm
text specification to be sent. The OID of traps are derived from the specified
OID ("1.3.6.1.4.1.x")
Name - this field is used as a prefix for the names of different files (alarm,
billing, activity, log and ASR) created by the gateway's application. If you
leave this field empty, then the name of these files is given by the current day
and an extension (for example "12-01-05.tax" is the billing file created on the
12th January 2005). If the "Name" field is filled then the names of these files
will be given by the name you have typed, concatenated with the current day
and the extension. For example if you type "Topex", the billing file created on
12-01-05 will be named "Topex12-01-05.tax".
3.6. Direction - Editing directions names

By clicking the "Directions names " icon (" ") a window for editing directions
name will be shown listing the directions name. Depending of the gateway
main application there is a maximum of 20 OR 250 directions.
The Directions are groups of inbound or outbound trunks that have common
routing characteristics. To ensure adequate routing of calls, you must assign
one or more trunks to each direction.
To edit a direction name, you select the name of the direction you want to edit
and double click the name. The following window "Edit direction name" will be
shown:
The direction name must be a unique identifier - an alphanumeric text

(digits/letters) of maximum 19 characters long. The first character must not be
a digit. The direction name must not contain inside the character space " ".
Otherwise an error message will be shown:
3.7. Calls direction - Defining the directions table

Click on the icon button "Calls direction" (" ")to open up the window for
defining the table with call directions. There is a maximum of 20 or 250
directions (trunk groups).
At the bottom of this window - there are two buttons named "DIR IP In
Settings..." and "DIR IP Out Settings". The first one is used to control the
incoming access into the TOPEX equipment. The second one is used to
establish the VoIP outgoing destinations.
To edit a direction parameters double click on it and the next window "Edit call
directions parameters" will show up:
For several fields a text length limitations is used: for "Insert" and "Insert_Id"
fields a maximum of 16 digits, for "Signaling" 4 characters and for "Signaling2"
8 characters.
Name - the name of the direction (cannot be edited here);
Type - can be PORT or DIR and specifies how that direction is addressed. The
associated list contains two strings "PORT" and "DIR". A value of "255"
indicates that the direction is ignored; when the "255" value is assigned to a
direction - then the entire line will be displayedin white color. The name of the
direction which has "255" assigned to "Type" field will be displayed in red color
in the list used to assign a direction for each kind of port and also in all places
in which the destination will be a direction name.
Overflow -overflow direction for the current direction. The calls will be rerouted to this overflow direction when the current direction is unavailable
(completely busy or out of service); you choose a name of a defined direction
from the corresponding list.
Overflow 2 - second overflow direction for the current direction. The calls will
be re-routed to this second overflow direction when the first overflow direction
becomes unavailable; you choose a name of a defined direction from the
corresponding list.
Restriction - the class of restriction applied to that direction; from the list a
number from 0 to 19 can be selected.
Ignore - specifies how many digits are ignored from the numbers received on
that direction; the first x digits of the received number will be ignored. The list
contains a range of values from 0 to 20 digits.
Insert - specifies the digits to be inserted in the number received on that
direction; The maximum allowed is 16 digits. If you don't want any digit to be
inserted you must enter "---" for this field.
Note: First the ignoring operation is performed and then the insertion
operation.
Max_d - maximum number of digits that may be dialed on that direction.
When the maximum number is reached the system will automatically send out
the call to routing analysis, without waiting to see if the caller part still sends
digits. This option is especially useful when you define directions for which the
number of figures to be dialed is well known (for example the numbers for
certain GSM networks). The list contains a range of values from 0 to 20 digits.
Ignore_id - Ignores from the identity of the caller (Caller ID) the number of
digits you have specified; The maximum allowed is 20 figures. The Ignore
command is performed before the Insert command. The list contains a range of
values from 0 to 20 digits.
Insert_id - Adds to the Caller ID the specified figures; The maximum allowed
is 16 digits.
Max_id - The maximum number of digits from the Caller ID to be sent to the
subscriber who has been called. The list contains a range of values from 0 to
20 digits.
Signaling - contains 4 digits with shape 'xyzw' with the following significance:
Digits
Purpose
Bit (from right to left)
Interpretation
bit 0 (mask 0x1000)
DIRCHECKCALLBACK
- when this bit is set
then for an incoming
call on this direction
the callback table will
be analysed with the
received identity
(caller identity)
bit 3 (mask 0x8000)
DIRMODULECDMA when this bit is set all

GSM ports placed on
the selected direction
will be treated as
CDMA modules
Interpretation
bit 0 (mask 0x0100)
DIRTESTNET (used in
case of a direction
which contains GSM
modules) - when this
bit is 1 one then the
outgoing GSM module
will be tested if it is
registered
x (digit 1)
DIRGOODASR - when
this bit is set then a
bit 1 (mask 0x0200)
RELEASE message is
sent on ISDN with a
delay of 5 seconds
when a congestion
situation is
encountered on GSM
part. The call will wait
on the specified time
a free GSM resource.
y (digit 2)
z (digit 3)
w (digit 4)
bit 2 (mask 0x0400)
DIRCATCALL - when
this bit is set then all
calls will be cut
(stopped) on the GSM
modules for which a
reprogramming is
necessary (for
example when a SIM
must be changed
because of an used
algorithm)
bit 3 (mask 0x0800)
verify CLIR - when

this bit is set then the
CLIR setting is verified
each time after the
CLIR setting is sent
to a GSM module
audio level (in range 0-7 dBm for the directions with
GSM interfaces) where '0' is the biggest level value
and '7' the lowest value
Interpretation
bit 0 (mask 0x0001)
- when is set identity

is received on selected
direction
bit 1 (mask 0x0002)

is sent on selected
direction
bit 2 (mask 0x0004)
- establish the
algorithm for
changing SIM on GSM
interfaces (when not
set, the algorithm for
minimal cost is used
(SIM selection by time
periods). When the
bit is set, the "load
balancing algorithm" is
used (equal usage
time for each SIM)
- by setting it, you
allow coupling of ring-
bit 3 (mask 0x0008)
back tone while dialing

on the next link,
before the called party
answers
By pressing button "..." a window for setting "Signaling" field will appear:
Signaling2 - contains 8 digits which will be fully used in further development.

One bit called "Transit Q.850" is used to transfer the Q.850 termination code
from the GSM link back on the E1-ISDN link. These Q.850 codes are available
only for the Siemens GSM modules. For Voxson modules and when the
"Transit Q.850" option is not checked the main application is sending a
congestion message for NO DIALTONE message and for a NO CARRIER
received under 2 seconds. The BUSY message is also received from GSM
network and it is sent as it is. A NO CARRIER message received for a value
greather than 2 seconds will be treated as a release from the GSM network.
A second bit called "Load balancing algorithm on SIM index" is used to enable
the load-balancing algorithm ("equal load") on the SIMs that are already
selected by SIM index algorithm.
"Calculate Tax Pulses" - for each direction (group of trunks) for incoming calls,
you can establish the calculating (and sending) of the tax pulses. The tax
pulses will be generated according to rules you specify and will accumulate in
the billing files. In any case, the calculated tax pulses are saved in the files. In
the case of an ISDN connection (E1-ISDN trunk) these pulses are also sent
out, using ISDN - AOC messages. You must remember that the mask must be
applied to the direction to which E1-ISDN channels belong.
Note: You can establish the prefixes that will be charged with billing pulses in
Routing Table.
The "Search UP" and "Search Down" fields are used for establish a rule in
which channels are selected - for example for a SS7 E1 trunk - the order in
which channels are selected in very important - if the trunk is used in both
direction then one side will choose channels from the first one - and the other
side from the last one.
The "Priority" field is useful in order to implement routes with the same prefix
to have different priorities. For example - when a TOPEX softswitch is used to
route calls to several TOPEX gateways - then each outgoing direction will have
assigned a priority. The customer can assign higher priority to the machines
with higher traffic capabilities and performances. The lowest priority is 0 and
the higher is 9.
Signaling3,Signaling4,Signaling5 and Signaling6 - each one contain 8
digits which will be fully used in further development.
Verifications are made for the fields that are involving insertion operation:
"Insert" and "Insert_id". The allowed characters are digits from 0 to 9, "*",
"#", "f" and "F". Characters "\","/","-" and "." are ingored in saving process. An
error message is displayed in case of an error.
By pressing "OK" you validate the settings for the "Signaling" field.
Note: If the field "Signaling" for a direction (for a record with type "DIR" ) is
changed by modifying "Receive identity","Send identity" or "Audio Level", then
all the GSM modules belonging to that direction will be re-programmed (reset)
in order to properly activate the sending and the receiving of the identity. Also
the audio level will be re-programmed. A confirmation message will be
displayed as follows:
3.7.1. DIR IP Settings

a) DIRIPIN section - this section is used to perform direction settings for VoIP
incoming calls.
By clicking the "DIR IP In Settings..." button in "Define calls direction" window
the following configuration window will show up:
You can Add or remove (Del) records about incoming VoIP calls.
Here the user must allocate to each pair <protocol, IP range> a direction and
a maximum number of incoming calls. The name of the direction can be one of
the already defined directions, so it can be MYVOIP - the generic
direction used for group the VoIP channels or another direction if you
want to use ignore / insert features. If you use the generic MYVOIP name, all
VoIp calls will be treated in the same way, but if you use speciffic direction
names, you can define different rules for different incoming IPs. This allows
you to perform operations such ignoring / inserting digits on the incoming
number or identity (see "Calls direction") like for ordinary calls.
Examples:
SIP 0.0.0.0/0 MYVOIP 100 0 0 100 100 p 0 0 0- for SIP protocol calls are
allowed from all IPs, and maximum 60 calls are allowed
H323 0.0.0.0/0 MYVOIP 100 0 0 100 100 p 0 0 0- for H323 protocol also calls
are allowed from all Ips, and maximum 60 calls are allowed
Note1: in the "IP field" you can complete either a single IP (such as
192.168.144.57) or a range of IP values (for example "192.168.1.0/24");
If you use an IP without specifying the range, then calls are accepted just from
that IP. It is the same as using range /32.
For example if you use 192.168.1.0/24 then IPs allowed are 192.168.1.x;
For example if you use 192.168.0.0/16 then IPs allowed are 192.168.x.x;
For example if you use 192.0.0.0/8 then IPs allowed are 192.x.x.x;
For example if you use 0.0.0.0/0 then IPs allowed are x.x.x.x (calls are
allowed from all IPs!);
Note2: The maximum number of incoming calls controls the number of
simultaneosly calls accepted from the specified IP. If you enter 0 (zero) in the
field Max Calls, this means no restrictions are placed upon the number of
incoming calls. The equipment will accept any number of calls.
The default value is 100.
Proxy - must be enabled if the source IP is behind a NAT.
Transcoding - must be enabled when the source and the destination have
different codecs. This feature works only on the equipments supplied with a
VoIP card (or there is a TOPEX slave machine with VoIP card).
Congrate - this is the congestion rate. It should not be 0. The default value is
1000.
Maxrate - this parameter represents the total number of setup calls on a
second. It should not be 0. The default value is 1000.
Prefix - this parameter was added in case when calls are coming with different
prefixes from the same IP source. In case of two such prefixes - the user can
assign two different directions for the same IP source.
Maxcost - this parameter will be used in further developments.
Nrdig - with this parameter - you can control the number of expected digits for
each call coming from the specified IP.
Endcause - this field is the release code used when the received number has a
different number of digits then the expected ones - "NrDig" value. The default
value is 34.
b) DIRIPOUT section - this section is used to perform settings for outgoing
VoIP calls.
Here the software application feature a possibility to allow overflow over an IP

direction. The user defines for each direction name a protocol (SIP or H323), a
destination IP, a port used for signaling for example 1720 for H323 and 5060
for SIP), the maximum number of outgoing calls.
In order to route a call on VoIP to a destination IP address - there are two
possibilities of setting in "Routing Table".
- if you use "DIRIP" in "action" field then you can provide a VoIP protocol
(SIP/H323) but just one IP.
- if you use "DIR" in "action" field then you can provide a direction name (you
don't have any VoIP channel assign to that direction - because all VoIP
channels are assigned to "MYVOIP" direction). Here in "DIR IP OUT" section
you'll make the relation to an IP address and a VoIP protocol (SIP/H323).

- RTPProxy - must be enabled if the destination IP is behind a NAT.
- Transcoding - must be enabled when the source and the destination has
different codecs. The codec may be changed if, for instance if the destination
IP does know just one codec, so we must perform a transcoding;
- Priority - this parameter represents the priority of the direction. This
parameter can be also set in "Signaling2" field in the direction definition
("Define calls direction");
3.8. Routing table

Click on the icon button "Routing table" (" ") to open the window with the
routing table. You can define a maximum of 128 routing rules (also there are
situations in which the TOPEX machine can handle more routing records such
as 1024 or 4000 records). The user can consult the current settings of the
TOPEX machine regarding the number of directions and routing records in the
licence window);
To add a routing rule to the table click the "Add" button. A new record will be
added at the bottom of the list (the new line will have an empty "Prefix" field).
To insert a new record over the selected record from the table the "Insert"
button can be used (the new line will have an empty "Prefix" field).
To delete a rule for routing select it from the list and then click the "Del"
button (the deleted line will have an empty "Prefix" field).
You can have the same prefix more then once - case in which you can use
"Move" buttons to change the prefix order - for the same prefix - the upper
line will have a greater priority than the lower one.
To edit a routing rule double click it and the editing window will show up:
For several fields a text length limitations is used: for "Prefix","Insert" and
"Insert_Id" fields a maximum of 16 digits, for "IP" 15 characters and 4 for
"Signaling", "Tax" and "Port" fields.
Incoming direction - this parameter is used in case of using several routing
records with the same prefix in order to make the difference between incoming
source. It have to be interpreted here as incoming source direction. A
"DEFAULT" value means that there is not rule to be applied.
Prefix - the routing digits (the first digits which are necessary to route a call)
- if you leave empty the field the respective routing rule will Not be taken into
account at saving action; The maximum allowed is 16 digits;
- inside a prefix string the value 'f' can be used to indicate any digit from '0' to
'9'. For example "1f2" means all prefixes from "102", "112" until "192". This
feature is very useful because it allows to reduce the number of records in the
routing table.
Action - the action to be taken: (there is a list with six strings: "PORT", "DIR",
"SERV","HUNT", "DIRIP" and "LCR".
- PORT- the call will get out through the port specified in the 'Dest' list
- DIR - the call will get out by the direction specified in the 'Dest' list
- SERV - the call will get out through the service that was specified in the
'Dest' list
- HUNT - the call will get out through the hunting group that was specified in
the 'Dest' list;
- DIRIP - in such a case the "Dest" field will be interpreted as VoIP protocol SIP or H323. The user must provide destinations IP address and port (in case
when the default values of 1720 for H323 and 5060 for SIP are not used).
- LCR - the call will get out by analising the LCR table for the index specifyed
in the "Dest" field. This field can take a value from 0 to 6. Each value
represents a rule to be applied in order to find a direction at the specified
moment.
Dest - the destination may be:
- a port number (in range 0-127)
- a direction name specified in "Define directions names" (from the list)
- a service number (from 0 to 19)
- a number of a group of hunting (from 0 to 19);
- an index to the LCR table
Ignore - the number of digits that will be ignored (omitted) from the digits
(numbering) sent out through 'Dest'. There is a list with values from 0 to 20;
Insert - Adds to the number sent out through 'Dest' the specified digits; The
maximum allowed is 16 digits;
Ignore _Id - the number of digits that will be ignored from the Caller ID sent
out through 'Dest'. There is a list with values from 0 to 20;
Insert_id - Adds to the Caller ID sent out through 'Dest' the specified digits;
The maximum allowed is 16 digits
IP - is used in the situation when "DIRIP" is used to fill the action field. It is
the remote IP address used to establish voice over IP connection.
Port - is the number of port used in voice over IP signaling. It is used when
"DIRIP" is specified in the action field.
Signaling - contains 4 digits 'xyzw' with the following significance :
Digits
Bit (from
Interpretation
right to left)
Alloc BSS - this option is used in the
situations when the ring-back tone
x (digit 1)
must be identified in order to declare

the call as answered. This option is
bit 3 (mask useful in cases when the gateway
application must make the difference
0x8000)
between a call answered without
ring-back tone and a call answered
after a ring-back tone. Additional
software must be installed on the
gateway.
Simulate Tax - is used in case of FXO
junction - in which the answer at
destination can't be recognized. In
bit 1 (mask
such a situation this option has to be
2000)
validated. The call is considered as
answered as soon as the call is made
on output link.
Retry Attempt - when this bit is 1
one retry attempt will be made in
bit 0 (mask
case of a first failure on this
0x1000)
direction; when this bit is 0 no retry
attempts will be made
Check Operator (mask 0x0800) - is used when
portability facility is desired. For each call, a
database interrogation is performed. The portability
database can be located on the same gateway or on
another PC. Additional software must be installed
on the gateway.
y (digit 2)
Restrict ID (mask 0x0400) - is used for SS7
direction in order to indicate that the identity is
restricted.
The identity can be hidden if in the routing record the ignore identity field is put to maximum digit
allowed - 20.
z (digit 3)
enable to set the number of digits which are waiting

to take the action specified in the field "Action"
w digit 4)
enable to set the number of seconds in which digits

are waiting to take the action specified in the field
"Action"
Value of 'z' can take values in range '0' to 'f' (where 'f' means 15 digits). When
a bigger number of digits is required, the value of 'y' may be used. A group of
'yz' with values '10' means 16 digits.
By pressing button "..." when action="DIR" or "DIRIP", a window for setting
"Signaling" field will appear:
The field called "Number of Seconds" can be filled with values from 0 to 15 and
the field "Number of Digits" with values from 0 to 20. A message error is
shown when a bad value is inserted into the specified fields.
Note: there are situations when the "Computing Signaling Field"
window will look different.
When "Action" field is "SERV" and "Dest" field is "FLASHING", the window will
look like in the next image:
When the two specified fields have these values ("SERV", respectively "4"), the
incoming calls will be forwarded to a "FLASING" tone. With the "Signaling"
field you can specify actions about the tones heard by the incoming user:
- "Connect To Music" - the gateway flashing tonality is provided to the
incoming call;
- "Connect To DSP" - the tonality will be obtained from a DSP (with possible
values from 0 to 63);
- "Loop" - the "Tx" and "Rx" sense are looped together;
- "Quiet" - no tonality will be provided to the incoming call; the user will not
hear anything;
The "Timer" field is used as follows: if a "0" value is used then the tonality will
be heard continously; otherwise the value will specify the amount of time on
which the tonality will be played to the incoming call.
When "Action" field is "SERV" and "Dest" field is "PLAY_RELEASE", the window
will look like in the next image:
The release cause for the prefix specified in routing table with action = "SERV"
and destination = "PLAY_RELEASE" will be released with the cause specified in
"Release Cause". A message to be played on such a situation can be also
recorded and stored on the TOPEX equipment.
The pair of settings "SERV" and "Dest=SELECT PORT" is used for testing the
quality of voice through the two GSM modules from the gateway (as explained
in "Facilities-Commands" chapter).
The pair of settings "SERV" and "Dest=DISA" is used for DISA operation on
ISDN channels. For example a record could be:
"Prefix = 8"
"Action = SERV"
"Destination = DISA"
"Ignore =1"
"Signaling = 0000"
The meaning of this record is: calls are coming from ISDN with the prefix (first
digit) '8'. This digit is deleted (because the value in the field "Ignore" is 1).
DISA tone is provided. All those new digits, which are collected in DTMF tone,
will be analyzed according to the routing table. If you want to be sure that all
the digits from the original number are deleted you can use instead "Ignore =
20".
If you want to force the call to be outputted only on a GSM direction, you can
have in the list starting with '8' the "Insert" field filled with the first digit of a
mobile call. For example "Insert = 0". Then, in the record for prefix "0" in the
routing table you must set "Ignore =1" so one digit is deleted.
Note: for a GSM port, DISA tone is provided from the GSM port by selecting
the appropriate setting in the "Category" zone.
Tax - type of billing. You can establish the prefixes that will be charged with
billing pulses in Routing Table. To can handle charging issues you must
change the field Tax.
Prefix Action Dest. IP
Port Ign Ins Ign_id Ins_id Signaling Tax
DIR
GSM
00a4
110a
There are three methods (rules) for configuring calculation of tax pulse. The
first digit (the leftmost of the four) of Tax field is used to differentiate
between those methods. Allowed values for the method are: 0 no method, 1
method 1, 2 method 2 and 3 method 3.
Method 1)
1xyy upon answering the call is charged with x pulses. During the state
of conversation the call is charged with one pulses every yy seconds. So if
you select 1 you must specify the number of pulses at response (10 in the
example below) and the time period for pulse generation (20 seconds in the
example below).
Method 2)
200x the calls are charged according to several zones and tariffs. The
zones are geographical areas where the tariff is the same. This kind of
taxation is performed by several fixed telephony (PSTN) operators. If you
select Method 2 you may change only the Tariff Index value.
The list of all zones and tariffs is defined in the next window, Pulse calculation
based on Zones that is displayed by pressing button.
You can easily handle zones and tariffs.

A maximum number of ten zones and four tariffs can be defined.
In the image above you can notice the tariff allocation on each day of the
week.
First, you have the day-tariff assignment. day=>1,0 means that the tariff 0
is applied on each Monday. The days of the week are allocated beginning
with Monday 1 up to Sunday 7. There is also an 8th day of the week, the
holidays the first value is 8. These special days that begin with 8 are defined in
Define Holidays
After day tariff allocation the tariff zone correspondence follows:

- each line starts with a triplet tariff=x,yy,zz, where x is the number of the
tariff and yy-zz is the time interval when the settings that follow are applied.
- After the characters tariff=x,yy,zz come the ten columns, the zones
showing time period when a pulse is generated. The temporization values are
in msec, so if a value is 60000 this means 60 seconds
Method 3)
3xxx the calls are charged according with a tariff. This is an extension
(refinement) of Method1. Besides the number of pulses upon answering and
the period for generating pulses, now you can specify also a period without tax
pulses and the number of pulses per taxing period. This kind of billing is used
by several mobile telephony carriers. If you select method 3, you may change
only the Tariff Index value.
There are maximum 10 tariffs, so values for Tariff Index can be value from 0
to 9.
The list of all tariffs is defined in the window Pulse Calculation based on
Tariffs, which is displayed by pressing the button .
In the picture above, Tariff1 is defined as follows:

- one pulse is sent upon answering
- then follows a one minute pause, for 60 seconds no pulses are sent
- after 60 seconds one pulse is sent every 10 seconds.
Note. In the Tax field, there is also a facility for limiting the maximum
duration of a call limit. For this, you select 4 for the value of the field
Method. This is NOT really a method for calculating the charge for a call!
With this, you may impose a time limit for the call. The value for Time is in
minutes, so the example above means that no calls longer that one hour will
be allowed.
SecondSign - here the user can specify in case of a SS7 route some
translations parameters as follows:
The first zone is related to "Nature of Address" information. We offer the

posibillity to override the "Called Party" nature of address and "Calling Party"
nature of address.
The "Called Party" nature of address is changed by enabling the first two
options "Check Called Party NAI" and "Override Called Party NAI".
The original "Called Party NAI" - Subscriber,Unknown,National,International
and UK Specific - can be changed to "Override Called Party NAI" which
contains the same list as the first one.
Moreover the "Calling Party NAI" can be override by selecting a value from
"Override Calling Party NAI" and enabling the "Override Calling Party NAI"
option.
The second zone named "Type of Media Required" - the route will be available
just for the specified type of media.
Possible values are "speech", "64k_unrestr" and "3K1Hz_audio".
The "Translation Occured" is to indicate for SS7 that a translation of number
has occured
Ctime - this parameter establish the maximum call duration (in minutes). It is
similar to "Tax" method 4. If this value is set here (not 0) the "Tax" method 4
will be ignored.
Search Mode - this parameter is used for routing in case of using routes with
the same prefix. In such a case a method for overflowing and dividing the
traffic between several routes must be provided. Each routes from such a
group must have "Retry Atempt" option in "Signaling field" (0x1000).
Overflow is performed if one of the following situations occurs:
- when the call is routed on VoIP - the main application is checking if the
number of simultaneously calls is greater then the maximum number of output
calls established in diripout settings (see DIRIPOUT section).
- when the call is dropped from the remote side with a release cause which is
set for rerouting in "trafic.cfg". For example to reroute on congestion message
the line "rerouteoncause 34 1" must be added in "trafic.cfg".
We assume this premise in the following explanations. This parameter is used
in conjunction with "Search Param" parameters:
Search Search
Significance
Mode Param
ASR
not
used
the route will be choosen

based on ASR value
ACD
not
used

based on ACD value
Priority
not
used
The call will be routed

based on direction priority
(direction specified in
"dest" field).
Calls from the routing
group (with the same
prefix) will go mostly on
the direction with the
highest priority. If the
maximum number of calls
is reached (for example
for a direction specified in
"DIR IP OUT" settings
when "Max Calls Out"
value is passed
from the first to the last
Down
not
used
one. Depending on the

position in routing table
the first route from the
group will have the
highest priority.
Up
not
used

from the last to the first
the last route from the
group will have the
highest priority.
Circular
not
used

circulary.
Calls will be routed based

on percentage. The
"Search Parameters"
specifies represents in this case
Percent the
the percentage value. The
percent application running on
TOPEX machine knows the
number of calls on each
machine.
Sign1 - contains 8 digits which will be fully used in further development.

Sign2 - is used for a SS7 route for translating purposes: the "IN Category" can
be override. The Computing Translation Parameters (for SS7 route) is
displayed by pressing the button.
To override the incoming category - the "Check IN Category" and "Override IN

Category" must be selected. In the "IN Catgory" list - you select the incoming
category which will be replaced with "Override IN Category". The possible
values are:
"unknown"
"op_french"
"op_english"
"op_german"
"op_russian"
"op_spain"
"op_rsrv1"
"op_rsrv2"
"op_rsrv3"
"notused"
"ord_subscr"
"prio_subscr"
"data_call"
"test_call"
"payphone"
"uk_oper_call"
"uk_admin_diverted"
3.9. LCR Table

If you click the appropriate icon the "LCR index table" (" ") window will
appear, where the table with the 8 indexes of LCR rules is displayed. Each
index includes information about the selected direction for specified time
intervals on each day of the week and even the days that were declared
national holidays (non-working days).
To edit a certain LCR index, double click on that index and the next window
will be displayed on the screen:
Note: when the dialog window for "Table modification" appears the information
is displayed by default for "Monday".
For each day of the week, a list shows up with the time periods (intervals) that
specify the direction to be used. In the image above , for 00:00 until 24:00
the direction "LOCAL" will be used. The periods are structured as hours and
minutes separated by character ":".
When the user modifies the selection in the list, the fields which are located at
the bottom of the window are filled with the line information: period "From" to
"Until" and the current direction. Those values can be modify and validate by
option "Mod". If you select"the Add" option, a new line will be added in the list.
The "Del" option is used to delete a record from the list.
The periods are checked before adding or modifing operation. An error
message is generated if the character ":" is not preserved or the values used
are wrong (hours or minutes).
The lines that are containing "255" instead of a declared name direction are
not saved in the "LCR" file. The format of the "LCR" file is compacted in order
to have a smaller size. An example of LCR file content is as follows:
#---LCR INDEX FILE--#Day type Mon=0x01 Tue=0x02 Wen=0x04 Thu=0x08 Fri=0x10 Sat=0x20
Sun=0x40 Holyday=0x80
#s index_lcr day_type_bitmap(%x) start_hour:min end_hour:min dir(%x)
l 00 1 00:00 24:00 0
l 00 1e 00:00 24:00 1
l 00 20 00:00 00:01 f
l 00 20 00:01 12:01 11
l 00 20 12:01 14:01 13
l 00 20 14:01 23:01 a
l 00 20 23:01 24:01 9
l 07 13 00:00 24:00 1
l 07 4 00:00 11:45 1
l 07 4 11:45 12:23 8
l 07 4 12:23 12:31 1
l 07 4 12:31 18:50 8
Each line is containing a letter 'l', a LCR index number (for example 00 and
07), a mask (each day of the week has an identifier constant (Mon=0x01
Tue=0x02 Wen=0x04 Thu=0x08 Fri=0x10 Sat=0x20 Sun=0x40
Holyday=0x80), periods used to define an interval and finally an index to
specify the direction used. This is the index in the "Directions Names" table (a
value from 0 to 19).
Note: if the same periods and the same direction are used on different days
(but for the same LCR index) then instead of two records in the file will be
written only one record with the field "mask" completed by an OR operation
between those days. For example "1e" is used to identify Tuesday, Wednesday,
Thursday and Friday.
3.10. Classes of restrictions

If you select "Restriction Classes" from the icon (" ") then the window
"Restriction Classes" will show, allowing you to define certain classes of
restrictions for the calls.
The window "Restriction Classes" includes 20 classes with 20 restrictions each.

To edit (change) the restrictions from a class, double click on that class. A new
window will appear, called "Edit restriction classes", as shown below. Using this
window you can establish up to 20 restrictions for each class.
Rules for establishing restrictions:

- each restriction has 8 characters
The characters can be any figure or the letters 'a' or 'f'
- 'a' represents the figure 0 (zero). For instance a subscriber with the
restriction aa000000 won't be able to make calls started with digits "00"
(international phone calls).
- 'f' represents "any figure". For example, if you define the restriction
f0000000 for a certain port it won't be able to call any number - it will be able
only to receive phone calls.
- '0' signifies the end of the restriction rule. If in a restriction field there are
eight "0" figures this means that no restriction has been defined for that field.
- a class can inherit one or more restriction classes. For instance, if in a class
we have the restriction 000000xx, where xx is the hexadecimal value
corresponding to another class of restrictions, then our class will inherit all the
restrictions that have been defined in the xx class, to which there will be
added the restrictions defined in the current class.
3.11. Table with indexes for selection of active SIM cards

If you click the appropriate icon (" ") the "SIM card index table" window will
appear, where a table with the 4 indexes of SIM cards is displayed. Each index
includes information about the SIM selected for each hour interval of each day
of the week and even the days that were declared national holidays (nonworking days)
To edit a SIM index double click on that index and the next window will be
displayed on the screen:
Note: when the dialog window for "Table modification" appears, by default the
information is displayed for "Monday".
A list is displayed with the periods (intervals) when the SIM card (1,2,3 or 4)
can be used. The periods are structured in hours and minutes separated by ":"
character.
When the user changes the selection in the list, the fields which are located at
the bottom of the window are automatically filled with the line information:
period "From" to "Until" and the active SIM card. These values can be modified
and validated by option "Mod". If user selects "Add" option a new line will be
added in the list.The "Del" option is used to delete a record from the list.
The lines that are containing "255" instead of an active SIM card are not saved
in the "simindex" file. The format of the "simindex" file is compacted in order
to have a smaller size.
An example of simindex file content is as follows:
#---SIM INDEX FILE--#Day type Mon=0x01 Tue=0x02 Wen=0x04 Thu=0x08 Fri=0x10 Sat=0x20
#s index_sim day_type_bitmap(%x) start_hour:min end_hour:min sim(%x)
#---HOLYDAYS--#h holydayday holydaymon
s 00 1f 00:00 06:00 2
s 00 17 06:00 20:00 0
s 00 1f 20:00 21:30 3
s 00 1f 21:30 24:00 0
s 00 8 06:00 20:00 1
s 00 60 00:00 24:00 0
s 00 80 00:00 12:00 0
s 00 80 12:00 24:00 1
s 01 ff 00:00 06:00 0
s 01 ff 06:00 12:00 1
s 01 ff 12:00 18:00 2
s 01 ff 18:00 24:00 3
s 02 ff 00:00 24:00 1
s 03 ff 00:00 24:00 0
h 01 01
h 01 01
h 25 12
h 08 01
Each line that specifies a sim index begins with the letter 's', then follows a
SIM index number (00, 01, 02 and 03), a mask (each week day has an
identifier constant (Mon=0x01 Tue=0x02 Wen=0x04 Thu=0x08 Fri=0x10
Sat=0x20 Sun=0x40 Holyday=0x80), periods used to define an interval and a
SIM card value. In the file the active sim card is written from 0 to 3. In all
locations in the "gwconfig" software values from 1 to 4 are used for SIM cards
(on GSM holders values 1,2,3 and 4 are shown).

Note: if the same time periods and the same active SIM card is used on
different days (for the same SIM index) then instead of two records in the file
will be written only one record with the field "mask" completed by an OR
operation between those days. For example "1f" is used to identify Monday,
Tuesday, Wednesday, Thursday and Friday.
Note: the records starting with 'h' character are used for holidays definition.
3.12. Defining the holidays

In order to define the non-working days with special GSM tariffs, click on the
appropriate icon (" ") to show the window named "Holidays Changing". This
window shows a default list with the national holidays and you can edit the
list, add or remove non-working dates.
To add a holiday in the list click the "Add" button. Once a record has been
added you have to double click on it in order to be available for editing, as
shown in the window below.
To delete a holiday from the list, select the date from the list and click the
"Del" button.
3.13. Callback Table

If you click the appropriate icon (" ") the "Callback table" window will appear:
Callback services assure lower costs for the mobile subscribers: from a mobile
phone you just call the Topex gateway and hang up. The software checks
identity on incoming calls and if the telephone numbers are in its database
calls them back. You don't have to pay anything for the connection! This is
very useful for mobile users in the field that have prepaid cards, which feature
an expensive tariff. They can ring the Topex gateway located at headquarters,
and the equipment will call them back, put them into connection with other
mobile subscriber or allow them to send e-mail messages via SMS.
Callback table is containing the following fields: "Identity", "Action",
"Callback", "CallTo" and "MailTo".
Callback has several implementations (depending on the "Action" field which
can take the values "CALLBACK", "CALLBACKONSMS", "SMSTOMAIL" and
"DISA"):
- if the caller identity of an incoming call is found in the "Callback table" and
the field action contains the mask "CALLBACK" then the caller party will be
called back. The back call is sent to the phone number specified in "Callback"
field (can be the same number with the number specified in the "Identity" field
or a different number). If "CallTo" field is filled with a phone number, then the
caller will be called and put into connection with this phone number;
- if the caller identity of an incoming SMS is found in the "Callback table" and
the field action contains the mask "CALLBACKONSMS" then the caller party
will be called back. The callback is sent to the phone number specified in
"Callback" field (can be the same number with the number specified in the
"Identity" field or a different number). If "CallTo" field is filled with a phone
number then the caller will be called and put into connection with this phone
number;
the field action contains the mask "SMSTOMAIL" then the text content of the
SMS will be sent to the IP address which is specified in the field "MailTo";
the field action contains the mask "DISA" then a "DISA" tone will be provided
to the caller part; The subscriber who ringed to the TOPEX gateway is called
back and receives DISA tone (if the field "CallTo" does not contain another
phone number). "Direct Inward Services Access' allows the mobile subscriber
to get access to private telephonic facilities (he can dial numbering).
To edit the "Action" field the button "..." must be pressed. The following
options are available "CALLBACK", "CALLBACKONSMS", "SMSTOMAIL" and
"DISA".
Note: Callback calls are recorded in the SMS files.
3.14. MTP Configuration

If you click the appropriate icon (" ") the "MTP Configuration" window will
appear:
In this window the signaling point (SP) definitions are performed:

- "SP definition (own codes)" - this is the zone where the own (gateway)
signaling points are defined. Each "SP" is enabled by marking it in the
appropriate checkbox. For each SP the "Code" and "Flag" must be set. For
"Flag" a value of "1" is indicating that this node is an STP (signaling transfer
point).
- "Adjacent SP definition (LinkSet)"- this is the zone where the adjacent
signaling points are defined. Each "Linkset" is enabled by marking it in the
appropriate checkbox. For each linkset the associated "SP" and the "Code"
must be set. The SP list is filled with the SP values enabled in "SP definition
(own codes)" zone.
- "Destinations" - this is the zone where the destinations are defined. Each
"Destination (Connection ID)" is defined by enabling the appropriate checkbox
"Dest" field. The first four destinations are filled based on "Linkset" definitions
- "SP" and "Code" fields are completed directly if the correspondance "Linkset"
is defined. User can define indirect routes using the "Priority" fields. For each
priority, the linkset is set as follows: there are three priorities - represented as
three columns: "Priority 1", "Priority 2" and "Priority 3". Priority 0 is reserved
for the direct route between the own SP and the destination. For each priority
and for each destination, user can select one of the enabled linksets (the
linkset list is filled with the linkset values enabled in "Adjacent SP definition
(LinkSet)" zone). For each destination (with a number greater than 3) the
associate "SP","Code", "Priority" and "Linkset" can be set. The SP list is filled
with the SP values enabled in "SP definition (own codes)" zone.
Note: the own SP code, the adjacent SP code and the nonadjacent SP code
must have the same "NI" field.
Note: the ">>" button is used for destinations from 16 to 31.
Note: the zone "Code value" is used to automatically convert a hex code used
to define a signaling point to the other known formats: "Code 2-3-8-3" and
"Code NI-SP". The user must point with the mouse inside a "Code" edit field.
The fields from the "Code value" zone will be filled with values . The option
"Apply" is used to fill back the original "Code" edit field (an <ENTER" action on
one of the fields from the "Code value" zone will cause a recalculation to be
performed).
Examples:
1) to declare an own SP0 code "8b38", non-STP - check "SP0" in the "SP
definition (own codes)" zone and then click the mouse on the edit field located
in the right side of the "SP0" checkbox - you can directly complete the point
code or you can edit the code value in the "Code value" computing zone. Here
you can input the code in different formats. When you finish you press
<ENTER> key and "Apply" button. You select "0" in the "Flags" field.
2) to declare an adjacent destination code (code "8103") - to the SP0 using
linkset 0- check "Linkset 0", select '0' in "SP" list and fill the point code value
with "8103".
3) to declare a non-adjacent destination code (code "8547") - to the SP0 using
linkset 0 on Connection ID 4. Select "Dest 4" checkbox, select "0" from "SP"
list, complete code field and select linkset on the highest priority available box.
4) to declare an indirect route (linkset 1) to an adjacent destination code
"8103" (linkset 0) - select linkset 1 in the highest priority available - on the
row starting with "Dest 0".
3.15. ISUP Configuration

If you click the appropriate icon (" ") the "ISUP Configuration" window will
appear:
The "ISUP Configuration" window allows the allocation of the circuit groups (in
range from 0 to 7).
- each circuit group is enabled by the option "Group x", where "x" is from 0 to
6.
- "Connection ID" can take values from 0 to 31. The " Connection ID" fields are
completed in "MTP Configuration" window displayed after the user selects " "
icon.
- "First Port" contains the first port from a SS7 card.
- "First CIC" (Circuit Identification Codes (CIC)) and "Range" are used to define
all CIC values.
The SS7 trunks can be placed on card 16 (trunk 2), 17 (trunk 3), 32 (trunk 6)
and 33 (trunk 7). Ports for card 16 are in range 128-159, for card 17 in range
160-191, for card 32 in range 256-287 and for card 33 in range 288-319. For
example the field "First Port" must be filled with the value 256 for an SS7 card
installed on card 32. The range is establishing the total number of channels
from the field "First Port". For a single SS7 card the range field will be 32. If
two consecutive SS7 cards are used (for example 32 and 33) the range can
take the value "64".
3.16. VoIP Configuration

If you click the appropriate icon (" "), the "VOIP Configuration" window will
appear:
The "VOIP Configuration" window contains two zones: "VOIP" and "H323". The
type of protocol (H323 or SIP) is choosed from the "Protocol Type" field. When
the "OK" option is clicked - the OAM application will load the settings from
VoIP zone and depending upon "Protocol Type" selection - the settings from
H323 or SIP zone will be saved.
For the VoIP zone you can change the following settings:
- Version: with or without RTP transcoding. Transcoding means that our
equipment performs conversion of codecs, that is the codecs used on the
output are different from the ones used on the incoming call. For an incoming
call from VoIP that goes out also through VoIP, the RTP channel is processed
by the multiACCESS/QUTEX/EONES equipment and transcoding may be
performed. No transcoding means that the equipment performs VoIP signaling,
but does not process the RTP channel, it goes directly from source IP to
destination without going through the Topex equipment. In this case
transcoding cannot be performed.
The conversion of codecs may be required if the caller uses codec g711, but
the destination supports only g728, so the Topex equipment must perfom
transcodig. But if the called party also supports g711, no transcondig is
required, and the RTP channel from the caller may be connected directly to
destination.
- "PG Card IP Address" - the IP address of the processor card (PG card).This
field is supposed to be filled with the same value as the ones you have
specified in the "Network settings - IPADDR" (icon "Gateway Parameters").
- "VoIP Card IP Address" - the IP address of the VoIP card.
There are two situations concerning the PG Card IP address and respectively
the VoIP card IP address.
1) when the VoIP gateway is installed in a LAN, then both addresses must be
in the range IP addresses of that LAN. In this case the following ports must be
opened if a firewall is used: the ports declared for RTP when the VoIP card was
installed (for example 3000-3063; to see the range of ports assigned for RTP,
go to window "H323 Settings" - window which is described on the bottom of
the window in the area called "IP Card Settings"). RTP ports are UDP and must
be forwarded to the IP address of the VoIP card.The ports 1718, 1719 and
1720 are TCP and they must be forwarded to the IP address of the processor
card (PG).
2) when the PG card is using a public IP address then the VoIP card must also
use a public IP address.
- "VoIP Card MAC" - this value represent the MAC address assigned to the
VoIP card. This value is preset or is given by TOPEX.
- "Public IP Address" - when the TOPEX gateway is used inside a LAN and
when the H323 signaling is performed with a machine from the internet, then
in this field you enter the external IP address of the LAN gateway. When H323
signaling is performed with a machine located inside the same LAN, then in
this field you enter the same value as in the "VoIP Card IP Address" field.
- "IP GATEWAY MAC" - this field is filled in case of making RTP connections
to a machine which is NOT in the same address range. This field will disappear
in future developments (the MAC address will be obtained automatically in all
cases, so you no longer need to fill in the value for the remote MAC).
1) when the VoIP gateway is installed in the same LAN, then a program
(MSPD) running on the Topex equipment automatically detects and fills the
MAC of the target gateway. You will enter in the field MSPD Parameters the
command --no-gw. This means no outside access is required.
2) when the remote VoIP gateway is on the the public IP address, then you
must first use an utility (MSPD executable) to search and find out the MAC of
the target gateway, then you must type this MAC address in the field IP
Gateway MAC.
- Audio Codecs: a list of pairs <codec no><packetization time>, which are

NOT delimited by commas. This is the list of codecs to be used by the RTP
protocol. VoIP uses several different codecs, having different parameters (bit
rate and complexity).The codecs used by Topex EONES are coded with one or
two digit numbers, such as 0 for g711u, 4 for g723.1, 8 for g711 or g711a, 15
for g728 and 18 for g729.
The packetization time is usually 20 (milliseconds), but it may be as long as 30
msec or as short as 10 msec. For a specified codec, like g729, the number of
channels supported depends of the packetization time. Increasing the
packetization time reduces the packetization overhead, so when going form 20
msec to 10 msec the number of voice channels goes down form 60 to only 40.
- "Enable VAD" - this checkbox option allows the "Voice Activity Detection"
facility to be used.
Typical voice conversations can contain up to 35 to 50 percent silence. On
VoIP networks, both conversation and silence is packetized. VAD sends out RTP
packets only when voice is detected, thus decreasing bandwidth by 30-50 %.
This way the Topex EONES will send voice packets only when it has voice
input. When it detects silence on RTP, it will send to the other side a silence
packet that use less bandwidth and allows to be interpreted for generating
comfort noise.
- LOG on MSPD enables logging on MSPD. The name of the log file will be
day-month-year_mspd.log,
such as 08-03-06_mspd.log
- "Port MSPD" - MSPD is a program that controls the VoIP, in this field you
can enter the number of the port to be used by MSPD, such as 9677 that is the
default.
- RTCP RTP Control Protocol - This checkbox establishes if the equipment
uses or not the control protocol for RTP.
The control protocol for RTP, RTCP is used for control and diagnostic on RTP
sessions. Like RTP, RTCP typically runs on top of UDP and is defined in the
IETF RFC1889. RTCP is a companion protocol to RTP that is used to maintain
Quality of Service . RTP nodes analyze network conditions and periodically
send each other RTCP packets that report on network congestion.
DTMF
This configuration area establishes the means of sending out DTMF in the RTP
packets. There are two methods, transmission of DTMF out of band in RTP
packets, or sending out INFO messages (as telephone-events). In SIP protocol,
the INFO method would be used for the carrying of mid-call signaling
information along the session signaling path (for example to send the DTMF
digits generated during a SIP session)

SIP INFO method can be used by SIP network elements to transmit DTMF
tones out-of-band in a reliable manner independent of the media stream. It
has advantages of reliabilty (the tones are not affected by low-rate codecs), of
Provides DTMF tone generation for SIP requests and for Enables transport of
DTMF digits along the signaling path.
The options available are:
- DTMF-RTP: if you chek this options, you must also complete the Parameters
field to the right
- DTMF INFO: you select to send out DTMF tones as INFO messages
- None : the sending of dual-tone multifrequency signals is not treated by
the Topex equipment.
Example for DTMF-RTP option: dtmfRTP 101 100 1
The syntax is :
- payload type for DTMF in RTP (according to RFC 2833)
- payload type for DTMF in RTP redundancy
- redundancy scheme: 0 or 1, where 0=IETF and 1=AAL2
For the H323 zone the user can change:

- enable "Gatekeeper" - enabling this option will allow using a gatekeeper.
Type the IP address of the gatekeeper in the "Gatekeeper" field. The H323
negociation will be performed by connecting at the specified gatekeeper IP
address. If you check the "Gatekeeper" option, the fields "User", "Password"
and "ID" must also be filled in. They will be used in the login procedure.
- "Prefixes" - is used to inform the gatekeeper about the digits routed by the
gateway on that link. This value is the same with the "prefix" establshed in
"Routing Table" to route the call on the VoIP card.
- "Trace H323" - allows the generating of an H323 log file, which will be
saved on the HDD of the Topex gateway The name of the file is given by
current day.
- enabling "Fast Start" - this option determines the method used for codecs
and voice activity detection negotiations. If the options is enabled, then both
codecs and VAD will be negociated on call setup or on response by using
additional parameters. When this option is disabled, then the negociation is
performed after response by using the standar H245 protocol. This negociation
will delay the start of the media session. If you enable "Fast Start, the
starting of the session will be faster.
Examples:
1) TOPEX gateway with VoIP installed in a LAN and making VoIP calls
with a machine from the same LAN.
Input data: the address of the PG card is 192.168.244.70, the address of the
VoIP card is 192.168.244.123 (MAC address 00:52:C2:40:3A:12).
Outgoing calls beginning with the prefix 0 will be routed through the VOIP
direction to address 192.168.244.76 as shown in the next image.
PG Card IP Address 192.168

VoIP Card IP Address
192.168.244.123
Public IP Address 192.168.24

(because H323 signaling is per
with an IP address from the sa
range, here is filled the same a
like in the Voip CARD IP addre
MSPD Parameters - -v -no

mem 16. The log option is fix
log file is /mnt/app/out/mspd
Because the other machine is i
same LAN the option "--no-gw
used.
Port use for communication be

H323 and gateway main applic
9010.
Codecs g729b,g729
VAD disabled
Fast Start enabled
Gatekeeper - not used
Trace H323 log on H323 ena
Routing table: the gateway will route calls starting with "5" and "6" to the
VOIP direction and H323 signaling will be started by connecting to
192.168.244.76 (remote machine).
with a machine from internet.
The difference regards the Public IP Address which will be set with the LAN
gateway external address. The firewall of the LAN gateway must allow port
forwarding for the ports which were already presented in this document.
3) TOPEX gateway with one external IP for PG card and another
external IP for VoIP card.
In this case the Voip Card IP Address and Public IP address will be filled
with the same value - meaning the external IP address of the VoIP card.
external IP for VoIP card. In this case a gatekeeper is used (option
gatekeeper enabled and an IP address specified).
In this case the Voip Card IP Address and Public IP address will be the
same. The H323 signaling will be initiated for a call with the gatekeeper
(instead of the IP address taken from the routing table). For login (identifing)
to the gatekeeper field Users, Password or ID are used. If in routing table
the prefix for routing calls on VoIP is 0 the in Prefixes field you must set
also 0.
3.17. Alerts
This option (" ") establishes sending out the alerts, recording of ASR values
and enables several debug and testing functions. Alerts are used in case of
alarms or if ASR values fall below a selectable level.
In case of occurrence of different pre-programmed events, the TOPEX system
can issue warnings (alerts) and also send out a description of the events. The
alarms may be sent to the administrator of the equipment in three ways:
- by e-mail (a warning message that has attached the alarm files)
- by SMS
- as a call on the mobile phone of the operator (several beeps)
The "Alerts" command shows the window for setting up the parameters for the
alerts:
The zone called "Alert zone" which is used to activate (enable) the
transmission of the alerts. For activate the alerts the option ("Alert activated")
must be checked.
The field "ASR alert limit" is used to set a level for activating ASR alert
transmission when ASR value falls below the specified value. The ASR value is
read at time interval specified in "Time period for checking". To validate the
ASR alert a minimum number of calls must be set. Of course, if during the
specified time period you have only one call, and it is not connected, this won't
be relevant for ASR, so it is not taken into account.
There is the possibility to validate the type of alarms for which alerts are
transmitted: "CCS-ISDN", "ASR" and "ALL".
For testing alerts purposes you can use the field "Timer for testing alerts". For
a "0" value in this field the alerts will be sent only in real situations. For
testing purposes a non-zero value (specyfing the number of minutes) must be
used.
"DIAL alert" is used if you want the alerts to be sent via phone calls. You must
enter the phone number to be called upon alert. You may also set the number
of beeps (1,2,3 etc) to be sent out in case of alert. By means of this variable
number of beeps an operator can determine from which TOPEX system the
alert is coming from: gateway A sends one beep, gateway B send two beeps
and so on.
"SMS alert" is used in case of alerts by sending a SMS message to a mobile
phone. You must enter the phone number to be alerted by SMS. You can also
change the content text of the SMS alert message. This SMS alert message
can be edited in a edit type window by pressing "File..." option to the right of
the "SMS alert" area.
"MAIL alert" is used in case of sending e-mail alert messages to an email
address. In case of activation of this kind of alert the following e-mail related
parameters must be set: "Gateway address", "MailFrom", "MailTo", "Subject",
"Server" and "Port".
You also have the facility to send the alert message with the current alarm file
for the TOPEX gateway as an attachment. The text of the e-mail alert message
can be edited in a edit type window by clicking "File..." option to the right of
the "MAIL alert" area. The following fields must not contain spaces inside the
value: "Gateway address", "MailFrom", "MailTo", "Subject" and "Server";
"SMS2MAIL" - this option is used to forward all incoming SMS to an email
address. This option is placed here because it is working together with the
settings estabished in "MAIL alert" zone. The SMS content is sent to the
address specified in "MailTo" field.
The "ASR Reading Parameters" zone is for establishing the ASR reading
procedure. First, to activate the ASR reading process the option "Validate ASR
reading" must be checked. Then the interval (in minutes) for reading and
saving ASR values is set in "ASR read period" field. Please note that this value
must be the same with the value entered above in the field "Time period for
checking" used for ASR alerts.

The "Debug Parameters" zone is used for the debugging process. This facility is
intended to help debugging the TOPEX system: log files for the equipment are
created and respectively displayed. If the "Validate Debug" box is checked then
all activities on ports specified in range "From" and "To" is displayed. If
"Validate Saving" is also checked, this information will be saved in log files on
target.
The "GSM" zone is used for:
1)- "CELL, LEVEL and Channel" interrogation. The GSM scanning is launched
by checking the option "Validate Cell Interrogation". The "GSMScan" value is
the value in seconds at which each GSM module is searched upon cell, level
and channel. If a call is passing through a GSM module and if the "GSMScan"
value is reached, the interrogation upon the mentioned values will be done
after the call ending.
2)- the reset of the "Load Sim" values - the user can enable the option
"Validate Reset of Load Sim values" and specify the "Day and Time" at which
those time of SIM using values are resetting. User will fill the time moment in
"hour minut day" format. These values are separated by space character. The
"Load Sim" values can be reset in each day at the specified time "hour minut"
if the "day" is filled with "0". The "Load Sim" values can be reset on each
month at the specified time "hour minut" if the "day" is filled with the desired
day. If one of the values "hour" and "minut" are wrong then the reset will not
occur.
There are the following text limits at the fields: "ASR alert limit", "ASR read
period", first port and last port - 3, "Time period for checking" - 4, "Minimum
calls number" - 4, "Timer for testing alerts" - 3,"Beep Number Identifier" - 2,
"Gateway address","Mail From", "Mail To", "Subject" and "Server" - 40.
"Simserver zone" - is used in case of a multiACCESS/QUTEX equipment which
is working with GSM cards simserver ready. The "simserver" zone contains an
activation checkbox "Activate", the IP of the simserver and the port to connect
to (default value is 13001). Finally the "Name" is the gateway identification
name, name which is also set in simserver to recognize the gateway client.
3.18. Test calls

For enabling test calls you can use the icon"Test calls" (icon " "):
In "TESTING calls" window is enabled to define call tests which can be

performed by the gateway. Test calls must be first enabled with the option
"run 1" (to disable test calls a line with option "run 0" must be used). For each
test call two parameters will be used: "pause xx" and "con yy" which represent
the time period between two attempts (xx) and the time to keep the call (yy).
After the record preceded by "#nr" the test calls definition follows: each line
will contains the number to be dialed, the identity of the call, the caller port
and a value of 0 or 1. With value '0' in a record the number will be first
analyzed with the definition of the direction (the direction that contains the
specified port) and after that will be analyzed according to the routing table.
With a value of '1' in a record, the number will be sent out directly from the
port.
For example a test record can be "12345 101 257 1". It means an outgoing
call with number '12345" and identity "101' is sent on port 257.
Note1) a good method for testing calls and to analyse the routing process is to
add a subscriber card and to add a record in the "TESTING calls" window with
an installed port from the subscriber card (that port must have also the option
of making calls). For example if the card 15 is a subscriber card then a record
for port "120" will be:
"0700000000 120 120 0"
Note2) for making test calls on E1 trunks or GSM cards an example was giving
before:
"12345 101 257 1",

For sending the number digit by digit a value "0000" must be used to fill the
"Signaling" field for the direction that contains the test port.
Note3) test calls are very useful in finding the available number of GSM
channels. Test calls are simultaneously generated towards the vocal
messaging. After the test calls sequence is started, the number of connected
calls can be observed by using "Live monitoring" facility.
Moreover a new method can be use to generate non-simultaneously calls - the
time delay between attempts and the time for keeping the calls connected was
the same for all test calls from the list. This new method allows the user to
create a list of test calls in order to have variable time delays between them.
Also, not all calls from the list are launched at the same time.
This new method includes the following parameters: (the lines beginning with
"#" are comments, used just to show you the structure of commands for test
calls):
#traffic_run 1/0 nr_simultaneous_calls(max 4 calls) call_type
traffic_run 0 1 test
#traffic_idle t_idle(seconds of idle time betwen calls) rand_add(random added
seconds)
traffic_idle 10 5
#traffic_sel t_sel(seconds of selection time for each call) rand_add(random
added seconds)
traffic_sel 5 3
#traffic_con t_con(seconds of connection time for each call) rand_add(random
added seconds)
traffic_con 1 2
#traffic_call nr id
#traffic_call 5113 100
traffic_call 5112 100
You must notice that each line contains the prefix "traffic_" concatenated with
"run", "idle", "sel" ,"con and "call". In order for this new method to work, the
user must create a direction with the name "SENDCALL" (icon "Directions
Names"). The "Type" field must be completed with "DIR" in "Calls directions".
All those test calls are generated from this fictive direction "SENDCALL".
- "traffic_run 0 1 test" to disable this second method for launching calls: you
can type "0" after "traffic_run". To enable the method you must type "1".
The second number specified in this line is the number of test calls that can be
generated at the same time (in the example above it is "1"). The list with the
test calls is described by the lines beginning with "trafic_call".

The "test" word is used to specify the tonality heard by the called part (in this
case a flashing tone).
- "traffic_idle 10 5" specifies the time to wait before to launch a new test
call. The first digit (in this case 10) means the number of seconds to wait. To
this value you may add the next value (it can be present or not ) which means
a range for a random value. The random number can be between zero and
that value. In the above example, the random range of five means that the
random value is between 0 and 5. Consequently, the waiting time will get
random values between 10 (10+0) and 15 (10+5).
- "traffic_sel 5 3 " specifies the value used to simulate the selection time for
test calls. Here also the first digit (in this case 5) means the starting number
of seconds to simulate the selection time. To this start value may be added the
next digit (which can be or not present) for randomizing. In this example,
three means a random value between 0 and 3. Thus the number used to
simulate the selection time for test calls will have get random values between
5 (5+0) and 8 (5+3).
- "traffic_con 1 2" specifies the value used to simulate the conversation time
for test calls. The first digit (in this case 1) means the starting number of
seconds to simulate the conversation time. To this start value may be added
the next digit (which can be or not present) for randomizing. In this example,
two means a random value between 0 and 2. Hence, the value used to
simulate the duration of the test calls will take random values between 1
(1+0) and 3 (1+2)
- "traffic_call nr id" specifies the number("nr") to be dialed and the identify
("id")
3.19. Transferring files

You can transfer files from and into the TOPEX gateway.
By choosing the associated icon (" ") , a window for file exchange will be
displayed.
The left panel ("Gateway Files - current") shows up the structure of files and
folders from the system associated directory.
You will see directories named "Alarms","Billing","Activity","Log" and "Viewer".
You can change between those directories and the root directory of the
connected system.
The right panel of the window ("Gateway files") shows the files and folders
structure located on the TOPEX multiACCESS/QUTEX gateway that is
connected to the PC. Directory content ("bin" directory) of gateway files is
automatic downloaded. On the gateway you can consult three directories "bin"
(where is located the telephony application), "cfg" (where the configuration
files are stored) and "out" (where system makes files for alarms, billing and
monitoring (activity)). You may navigate through these directories of the right
panel by double clicking.
When you want to download a file from gateway you enter in the directory
from which you want to make download. You choose a file. The file is
downloaded (you have a progress indication) on to the OAM computer.
It is mandatory to download files to appropriate destination: alarms (*.alr
format) and asr (*.asr format) in "Alarms", billing (*.tax format) in "Billing"
and activity (*.mon format) in "Activity". If you want to view a text file you
can download it to "Viewer" folder. Options from tree commands "Alarms",
"Billing" and "Activity" are working with files with the previous extensions.
Automatic file transfer is allowed in connection state. You click on the "Auto
Downloading Files" icon button (" ") to show the window called "Download
Files From Gateway".
The purpose of the automatc file transfer is to generate automatically requests

for billing, alarms, activity, ASR and SMS files on the selected time interval.
The finalization mode for each downloaded file will be either "ERROR" or "OK".
The files are automatically saved in directories according to their type. The
default value for the time interval is the current day.
The option "Download Billing Records (for today) starting with hour: " is used
to download the records which are started with the specified hour from the
billing current day file. The specified hour may be changed.
The option "Download Billing Records (for today) last: 100 (records)" is used to
download last 100 records from the billing current day file. The number of last
records to be downloaded may be changed.
For one of these last two options (which cannot be set in the same time) the
resulted billing records will be automatically displayed.
3.20. Clean HDD Space

This option (" ") allows you to delete files from the TOPEX system. This can be
needed if the equipment has been in use for a long time and has stored many
large files on the hard disk. You may want to delete the older or not important
files to make room for new files.
You must choose the associated icon ("Clean HDD Space").
The window "Deleting Files From Gateway" allows you to choose a time period
and the type of files to be deleted. The type of files can be:
- billing files (extension "*.tax")
- alarms files (extension "*.alr")
- activity files (extension "*.mon")
- ASR files (extension "*.asr")
- SMS files (extension "*.sms")
- log files (extension "*.log"); these files are created by the gateway
application when "Validate Debug" and "Validate Saving to File" are checked in
"Parameters for ALERTING" window (icon option " "). Informations that are
saved in this kind of files is about the port activity for all ports in range "From"
until "To", values which are specified in the same window for defining alerts.
- status files (extension "*.sta"); these files are used to store the state for all
ports (by state of a port we are meaning uninstalled, free, busy or alarm).
These files are used by the web application.
By pressing "OK" option the requests for deleting files are sent to the gateway.
The process of deleting the files can be observed in a listbox which is displayed
in the "Deleting Files From Gateway". At the end of deleting process a request
for reading HDD occupied space is sent to the gateway. The indicator of the
HDD space from the status bar will be changed if the occupied HDD space was
changed on the gateway.
3.21. File Editor

This option (" ") allows you to edit the configuration (.txt) files that can be
loaded later into the TOPEX system. You must choose the associated icon ("File
Editor").
The first window "File Editor Selection" allows you to navigate through the
subdirectories structure in the system root folder.
From this window you choose the text file to edit, then a new dialog window
will show up, with the content of the file. The selection is done by double
clicking on the name of the file, so there is no need for an "OK" button - this
window has only a "Cancel" button at the bottom.
There is a limit for the size of files to be edited, they should not be over
65,535 bytes in length.
File content is saved by "Save" option.
3.22. Loading hour

You can upload the time into the TOPEX system. When you click on the icon ("
") for loading hour a dialog box will appear in which you can change also the
computer time. Loading hour is very important because you modify the
gateway clock: time and date. So this action is protected by password. This
password is always "topex".
The default value shown is the date and time that are set on the computer
where the OAM program is running. Before sending the time to the system,
the program performs a validity check, so if you enter for the time and date
values that are not valid you will receive an error message: 'Error in changing
hour'.
3.23. Automatic download of alarms and ASR

Allows auto-download of alarms and ASR info from all of the TOPEX systems
that are connected (with IP communication). The icon command (" ") is
"Automatic Requests". When you click it, the OAM program will automatically
launch (at pre-established time intervals) interrogation requests for the
installed TOPEX systems. The requests may be about alarmed modules and
about ASR value (both general and instantaneous). This is very useful when
you have several TOPEX gateways, because you no longer need to manually
connect to each one and ask it for the alarms and ASR information.
You must set a "Period" (in seconds) for the interrogation cycle of all TOPEX
systems that are connected. The values must be greater or at least equal to 60
seconds.
Then you select a threshold for the ASR value: when the general or
instantaneous value is under the established level, the value is shown in a
window (called "ASR"). By double-clicking with left mouse button a statistic is
shown with the last 24 values for general and instantaneous ASR (for the
system which is currently in process of automatic interrogation).
The "ALARMS Alert " panel of the Automatic Requests window allows you to
select different kind of alarms. When these alarms occur in the TOPEX system,
they will be shown and stored.
When the interrogation process is not started the text "STOPPED" is shown in
the dialog window title, as you see in the first image. After you have selected
the types of alarms, you may press either "Start" or "Cancel". The start of the
automatic interrogation process is allowed by choosing "Start" option. The
interrogation period and ASR alert value may be changed at any moment by
selecting "Change" value.
When interrogation process is not started the text "STOPPED" is shown in the
dialog window title. Valid options are "Start" and "Cancel". The start of the
interrogation period and ASR alert value may be changed whenever by
choosing "Change" value. When automatic interrogation process is started on
the status bar in the first box (leftmost) the following text will appear: "AUTO
REQUEST ACTIVATED in xxx !!!" where "xxx" is the number of seconds until
the interrogation request will be made.
When interrogation process is started the text "STARTED" is shown in the

dialog box title. Valid options are "Stop" for canceling the interrogation
procedure, "Change" for changing parameters and "Cancel". There is also
"View" option for displaying a statistics with the last 24 values for
instantaneous ASR (for the TOPEX systems which are in process of automatic
interrogation).
When the specified period expires the request for system interrogation will be
launched. On status bar will be displayed the text "AUTO REQUEST IN
PROGRESS !!!". In the next box to the right side all messages will be enclosed
by the system name (connection name).(For example "cfg_GSM")
During the automatic interrogation procedure it is allowed to connect to a
system only if the OAM software is in a pause between two interrogations. In
the contrary case it is allowed to stop the automatic procedure which is in
process (when in the status bar is written "AUTO REQUEST IN PROGRESS !!!")
by selecting the "Disconnect" command from any of the systems. Then the
OAM program will again wait for the established time period before issuing
automatic requests for interrogation.
Notes:
- normally if you have connected to a TOPEX system you can perform
"Disconnect" only from that system. But when in automatic request mode, the
"Disconnect" command may be sent from any system!
- If the connection is broken with "Disconnect" command, only the ASR and
alarms that have already been scanned will be downloaded.
3.24. GSM Reprogramming
This reset command (" ") is useful in situations when there is need to refresh
the settings for all the GSM modules.
This GSM refresh must be issued to allow the proper setting of the receiving or
sending of the identity through GSM modules and also the setting of the audio
level.
There is a confirmation message which is requested to the user, before to start

the reprogramming procedure.
3.25. Halt and Reboot commands

Those two commands are similar to the LINUX commands. First command
HALTS (" ")(stops) the machine and the second REBOOT (" ") the machine.
After HALT command, the TOPEX system may be safely disconnect from the
power supply. Incorrect shut down of the equipment may cause damage of the
file system and other problems such as a large delay in startup due to the file
system check.
3.26. Visualization List

The icon " " display a visualization window with the settings of all ports
(rights, number, target, direction, SIM index regarding type of port).
The list is build in physical order of ports starting with 000.
In the picture above it can be seen GSM positions for which are given the
following settings: 'Installed', 'IN', 'OUT',direction, SIM index, target, Pin1,
Pin2, Pin3 and Pin4 values. Also it can be seen ISDN channels settings:
'Installed', 'IN', 'OUT' and direction.
By using the 'FIND' and 'NEXT' buttons you may search for a text string in this
window.
4. Print options
In all situations involving a print command a dialog box will appear. It will
contains two options:
- print to printer (a printer must be installed into system)
- print to file (in this situation a file name will be given for saving data)
5. NOTE
There are two types of windows used. There is a window for viewing files
content and another window for viewing or modifying system configuration.
When we are working with files content we can operate on the tree commands
for the chosen system and when we are finishing we press the right button and
hide the window. If we are working viewing a configuration we can hide it by

pressing right button. If you are connected and the configuration window is
above by pressing right button you are questioning if you want to disconnect.
At the right side of the status bar there is an indicator for connection: it is blue
when we are connected to a system and it is red when we are not connected to
any system.

Administration, and Maintenance - DISCONNECT...
Disconnect, breaks the connection to a connected system. We cannot
disconnect a different system other that the connected system.

Administration, and Maintenance - Modify parameters
- If you select "Parameters" the following window pops up:
Is permitted to modify System name, IP address and IP port number, serial

port (in range COM1-COM12) and the link type "Serial communication/IP
communication". Also the "DialUp" parameters can be changed: "Use PPP
address", "DialUp connection name", "DialUp Number", user name and
password used for authentication and "Connection Timeout".
There is a text limit of 19 characters for the "Name" field and 2 characters for
the "Serial Port num".
colored in red.
Also, value check is performed for the "Name" field. If this values is not filled
or is the same as an already existent "Name" (used for another system), an
error message will be displayed and the incorrect field will be colored in red, as
shown in the following image:
Is permitted to activate automatic requests for reading ASR and alarms.

Note: in case of reduncancy when two processor card are used the "Modifing
system parameters" window will be different:

Administration, and Maintenance - LAST CONFIGURATION
With this option we can see last downloaded and eventually modified
configuration for chosen system. If you select this option the "View
configuration" window will be displayed. You will be able to view offline last
configuration: ports setting, route table, calls directions, sim table, holydays
settings ("Ok" button in all windows will be hidden).

Administration, and Maintenance - ALARMS
The alarm files are named <current date>.alr and they include the following
fields:
Field
Interpretation
Current date
dd-mm-yy
Current time
xx:xx:xx
SET - blocked (appearance of alarm)
Alarm status
RES - unblocked (disappearance of an alarm)
PROCUP - the processor is started. This is an event, it

works only with SET, not set/reset
PROCDN - the processor is stopped. This is an event, it
works only with SET, not set/reset.
ALIM val - Supply indicator
JONBLOCK - junction alarm
APFALS - local subscriber alarm
CARDERR - board alarm
LIS - Loss of Incoming Signal (is an alarm that indicates that
there is no signal on the E1 trunk input)
LFA - Loss of Frame Alignment (is an alarm that indicates
that the frame alignment is not detected)
LMA - Loss of Multiframe Alignment (is an alarm that
indicates that the multiframe alignment is not detected)
AIS - Alarm Indication Signal (the alarm is send by a
transmission equipment to indicate the lost of the input
signal on the E1 trunk )
Type of alarm
RSA - Remote Signaling Alarm (is an alarm which is

transmitted by the gateway when one of the following
alarms is detected: LIS, LFA or AIS)
RJA - Remote Junction Alarm (is an alarm which is
transmitted by the gateway when LMA alarm is detected)
CCS - Common Channel Signaling Alarm. Warns about the
data link for the ISDN E1 trunk.
SLIP - This alarm event is caused by non-synchronous
operation of the two equipment (TOPEX system and PBX or
VoIP gateway).
BER val - Bit Error Rate; val is a number from zero to three
that shows the error rate as follows: 0 = 10-6, 1 = 10-5, 2
= 10-4, 3 = 10-3.
ASR - alarm of ASR - value calculated on gateway - alarm

which is generated if the ASR is below a threshold. The ASR
value is calculated if "Validate ASR reading" is enabled in
"Alerts" window. The ASR value is recomputed at each "ASR
read period" seconds.
The ASR alert is generated if the ASR value is below "ASR
alert limit" and if "Alert activated" checkbox is enabled (see
"Alert Zone" - "Parameters"); also the "ASR" checkbox must
be enabled in "ALARMS for alerting" area.
Port
Number of the alarmed port
Card
Number of the alarmed card
All these fields are separated in file by "," character (comma character).
By choosing "Alarms" - tree command for a system, all alarm files from the
folder "Alarms" of the system directory we'll be shown.
It is possible to select the alarm file you want. Double click with the left mouse
button, then a dialog box for making an alarm filter we'll be seen. The alarm
filter indicates how to check options and values for searching inside the
"Alarms" directory.
The field "Period" indicates by default the time period corresponding to the
name of the alarm file that was selected. This period can be changed in order
to extend the time interval that is analyzed. The software will look for records
in the alarm files name whose name falls inside the selected time period.
There is an option to view only certain types of alarms and to specify the card
and the port number for them.
You can select only alarms appearances / disappearances or both.
The maximum size of the fields is 8 for the periods and 3 for the fields that are
specifying a card or a position number.
The correctness of the period definition is checked before the filter validation.
By pressing "OK" button all alarms corresponding to the filtering criteria will
be displayed in the "Local Viewer" window.
Each record contains the moment of the appearance (with "SET") or the
disappearance (with "RES") of the alarm and a description (text) of the alarm.
Regarding the error type the next two fields are important (sense): position
and card.

Administration, and Maintenance - BILLING FILES (CDR)
The billing files are named <current date>.tax and include the information
required for detailed billing (taxation) of the calls.
During the development period, the information which is saved in the
billing file was increased by adding columns. In the following
explanations is described the basic billing file structure; at the end of
this short description, the table which contains the billing fields will
present also the new added columns.
The following example - for a multiACCESS - GSM equipment (with an
answered call) contains a test call from port "120" with the phone number
dialed "81712345678". The identity of the call is "120".
TLI,00120,120 ,81712345678 ,10-0304,14:30:43,000004,00001,00,00008,BOK , 16,222222222222222,
10,abcd,GSM
Note 1): an incoming call can be made either from a subscriber or from an
incoming direction (containing E1 trunks or GSM modules);
Note 2): the number and the identity can be subject to modifications by the
multiACCESS/QUTEX gateway. Changes are caused by applying the rules
about the ignore and insert operations and the maximum expected digits from
the "Define Calls directions". Also, if a route exist for the dialed number,
changes can be made by the ignore and insert operations from "Routing table".
But in the billing files the phone number and the identity will always be the
original ones;
Note 3): the total number of digits that can be treated correctly by "gwconfig"
software is 20, both for identity field and for the number field;
Note 4): the number, the identity and the IMSI values used here are for
example purposes only;
The next example (with an answered call) contains a test call made from E1SS7 or VoIP ports on an EONES equipment.
Example1: the fist example with an answered call contains a test call received
on port 32 (E1 port). The received number was 5235. The output port was a
VoIP port (258) located on SS71 direction. The call was released from the
called party side (see BOK). The duration of the call was two seconds, and
selection duration was 11 seconds.
The IP fields are filled with space and the port fields with 00000, because the
incoming port was not a VoIP port.

TLI,00032,100 ,5235 ,10-03-06,11:11:03,000002,00001,00,00258,BOK , 16,
, 11,0000, MYVOIP , ,00000, ,00000, ,00000, ,00000
Example2: another example, also with an answered call, in which the call is
coming from VoIP port 258 with number 5235 and identity 258. The call
was coming from 192.168.1.152 signaling port 37380 and RTP port
49172. The destination IP was 192.168.104.20 (EONES processor address
in this case) with signaling port 5060 and VoIP IP address 192.168.104.21
(voip ip address of the EONES) with RTP port 10516. The output port was 259
located on MYVOIP direction.
TJI,00258,258 ,5235 ,10-03-06,11:21:29,000003,00001,00,00259,BOK , 16,
, 2,0000, MYVOIP ,192.168.1.152 ,37380,192.168.1.152
,49172,192.168.104.20,05060,192.168.104.21 ,10516
Note 1: an incoming call can be made from a an incoming direction (containing
either E1 trunks or VoIP channels);
Note 2: the IP fields together with signaling and RTP ports are written into
billing files when Add IP fields is established in Gateway Parameters.
Billing records can be aslo send to an external MYSQL database for storage and
further processing.
Note 3: the number and the identity can be subject to modifications by the
EONES. The changes are caused by applying the rules about the ignore and
insert operations and the maximum expected digits from the "Define Calls
directions". Also, in addition, if a route exist for the dialed number, then
changes can be made by the Ignore and Insert operations from "Routing
table". But in the billing files the phone number and the identity will always be
the original (initial) ones;
Note 4: the total number of digits that can be processed by the "gwconfig"
software is twenty (20), both for the field identity and for the field number;
A billing file has the following fields:
Field
Description
Call type
TJI or TLI (the call source is a junction respectively a subscriber)
xxxxx - physical position of the source port (5 digits). This value

Source Port
This value can be 65535 in case of a multiswitch.

Source
identity
subscriber number or caller identity (20 digits)
CallDigits
(Call
Number)
call number (20 digits)
Day and
Time
Day and Time of the call in the following shape dd-mm-yy,hh:mm
Connected
Duration
xxxxxx - speaking duration of the call in seconds (6 digits)

xxxxx - billing Units for the call (5 digits)
Billing Units
for the call
This field is usually filled with 0 for non-answered calls and with 1
However if tax pulses calculation is set on incoming direction (see
Direction") then this value will be filled according with the numbe
bases (see "Tax" field in "Routing Table").
Destination
When the destination port is a GSM port (multiACCESS or QUTEX
SIM Number
Destination
Port
- physical position of the destination port (5 digits) (when the ca

in this field (5 digits)
In case of a TOPEX multiswitch - calls terminated with success wil
Possible values are AOK, BOK, ARELS, BRELS, AINEX, BINEX, ACO
ANANS, BNANS, ABUSY, BBUSY,
ATOUT,BTOUT,AERRAUTH,ANOCRED,AFINCRED,AVMAIL,BVMAIL,N
It indicates the mode of ending the call:

- first character indicates who has released the call: A=caller part
- next characters are keywords detailing how the call was ended:
OK - ANSWER (response in the destination part)
RELS - RELEASE (release in other situation then ring-back tone or
INEX - INEX (non-existent from equipment point of view - no defin
CONG - CONG (congestion from equipment point of view - no ava
SERR - SERR (Signaling error)
NERR - NERR (Network error)
Finalization
call mode
NANS - NO ANSWER (release on ring-back tone)

BUSY - BUSY (release on busy situation)
TOUT - TIMEOUT (timer expiration)
AERRAUTH - when the ANI or prepaid user is not authenticated on
ANOCRED - when the ANI or prepaid user has no credit available
AFINCRED - for ANI or prepaid user when the credit expires durin
AVMAIL BVMAIL - when a call is finished on vocal message box - cause of
NOVOIPCH - when no VoIP channel is available
CODECERR - when the source codec is not in the list of supported
NOLICENCE - indicates two situations: 1) that the LICENCE had ex
for the requested protocol - for example VoIP or SS7. The LICENC
ACLREJECT - indicates for an incoming VoIP call that the IP is not
different then the expected value or the number of incoming calls
are set in
DIRIPIN section.
Finalization
Possible values are either ' 31' (normal call) for non ISDN calls or
call mode on
release codes
ISDN calls
IMSI
International Mobile Subscriber Identity (multiACCESS or QUTEX
Selection
Duration
xxx- three digits - total time (in seconds), cumulated value of both
CELL
For a call routed through a GSM port (multiACCESS or QUTEX) it

where the SIM was registered.
The direction to which the destination port is belonging (it is the o

Direction
In case of TOPEX software versions released after 2006 - this field

This direction can be a direction to which ports are belonging (for
a direction used for incoming VoIP calls - which is the generic "MY
ports) used just to allow inserting/ignoring digits from number or
The IP source and destination address and the RTP source and des
This info includes the Signaling IP and Signaling Port for the sourc
followed by Signaling IP and Signaling Port for the destination, an
IP address
destination.
and RTP port
For the VoIP incoming calls, the destination signaling IP is the one
destination RTP is the IP of the VoIP card. In case of VoIP outgoing
VoIP card of the Topex (multiACCESS/QUTEX/EONES) equipment,
Session_id
remote VoIP card that made the call.

This is an unique identifier of a call inside the equipment software
equipment log files.
Jitter
Jitter is a variation in packet transit delay caused by queuing, con

through the network.
Packet Loss
VoIP packet loss occurs when a large amount of traffic on the netw
dropped conversations, a delay in receiving the voice communicat
Client_id
Direction output
direction
This direction is the output direction and can be a direction to whi

FXO,FXS,GSM or E1 - ISDN/SS7) or a direction used for outgoing
"MYVOIP" direction or a virtual direction (without ports) used just
destination IP (see DIRIPOUT section).
Proto in
protocol used on incoming side - H323/SIP (VoIP), CAS (FXS,FXO,
Proto out
protocol used on outgoing side - H323/SIP (VoIP), CAS (FXS,FXO,
the value of codec:

G729 - 18
Payload Type G723 - 4
G711, G711a - 8
G711u - 0
The Packetization Time is the length of the digital voice segment t

Packetization
millisecond packets. Selecting 10 millisecond packets enhances th
Time
to packet loss, but doubles the load on the network traffic.
If you select "Billing" - tree command for a system, then all billing files from
the folder "Billing" of the selected system directory will be seen.
You go to the billing file you want to see, and by double clicking the left mouse
button a dialog window will pop up, allowing you to build a filter for selective
display of the billing information. This filter for billing (taxation) files permits
the setting of options and values for searching records inside the subdirectory
for billing.
The first field, "Period", indicates the time period corresponding by default to
the name of the billing that you have selected. You may change this default
period to extend the time interval that is analyzed. For each of the "From"
and "Until" limits, subfields are "Day" and "Hour". The program will look for
records in the billing files whose name falls inside the selected time period.
From the source point of view you may specify these options:
- physical position of the source port
- port number (for an exchange subscriber call) or caller identity
- a direction - a name of a direction defined in "Directions Names"
- the source port type: local or junction (trunk)
From the call destination (called part) point of view you may specify these
options:
- digits from the destination digits. You can choose to select only records with
the number of destination digits less, equal or greater than the value typed.
- physical position of destination port
- a direction- a name of a direction defined in "Directions Names"
- a value for SIM card (1,2,3,4 or 255)(when the destination port is a GSM
port)
- a value for IMSI code
- a value for CELL code
The section "IP and Port Filter" contains several options to select from the
incoming call side:
- signaling IP
- signaling port
- RTP IP
- RTP port
From the ougoing call side:
- signaling IP
- signaling port
- RTP IP
- RTP port
You may specify a filter on the finalization call mode. All calls and also the
billing records have a caller and a called party. For an incoming call on E1
trunk the source party will be a channel on the trunk and the call will be
routed over a GSM interface (the destination port). Caller party will be
represented by 'A' and called party by 'B' (field "Release Side"). Depending
by the side which ends the call a letter ( 'A' or 'B') will be shown and the
finalization mode will contain one of the following strings: OK - ANSWER, RELS
- RELEASE, INEX - INEX, CONG - CONG, SERR - SERR, NERR - NERR, NANS NO ANSWER, BUSY - BUSY, TOUT - TIMEOUT. "Call Type" lets you to specify
the mode of ending of the call.
Note: physical port position on a E1 trunk is computed in the following
procedure: for E1 trunk installed on card 32 (trunk 6) the port will be 256 +
channel number on E1 trunk, for E1 trunk installed on card 33 (trunk 7) the
port will be 288 + channel number on E1 trunk, for E1 trunk installed on card
16 (trunk 2) the port will be 128 + channel number on E1 trunk and for E1
trunk installed on card 17 (trunk 3) the port will be 160 + channel number on
E1 trunk.
You may set a value for "ISDN EndType" which represents call release code
for ISDN calls. Other types of calls will display a value of ' 31' in the billing
records.
You may also set the option to select the records with the conversation
duration and the selection duration (in seconds) less, equal or greater than
the value typed.
The maximum size of the fields is 8 for the periods (date and hour), 2 for the
number of digits, 3 for the source port position, sim index and ISDN EndType,
5 for destination port position, 6 for duration, 3 for selection duration, 16 for
specifying IMSI code and 20 for specifying destination digits.
Certain values from the billing filter are checked before validation (by pressing
the button "OK"). The program checks correctness of the following:
- period definition (day and hour - day less or equal to 31, month less or equal
to 12, year less or equal to 36, hour less or equal to 23, minute less or equal
to 59 and second less or equal to 59);
- port position of the call source (in range 0 to 319);
- sim index (in range 1 to 4 or 255);
- destination port position (65535 or a value in the range from 0 to 319);
- duration and selection duration (a value greater or equal to zero);
- number of digits (a value greater or equal to zero);
- ISDN EndType (a value greater or equal to zero);
If something is wrong, an error message will be shown to the user and the
field that has caused the error will be colored in red (while the text color
becomes white). When the user goes back to the incorrect field in order to
correct the wrong data, then the red color will disappear. In the following
example an error message "Wrong port value" is displayed because of an error
field on port position (a value "342" which is greater than the maximum
number of 319).
Finally, you can set the option for viewing only the totals of the recording
(option "Display only the total without the records") that corresponds to
the selected criteria or you can choose to display the values without totals
(option "Display only the records without a total").
The option "Display only the records without a total" is useful for filtering out
the records in a certain time interval for the purpose of post-processing of the
stored billing information (post-processing is done for cost analysis). For these
applications, you need a text file with values only (that may be imported into a
spreadsheet like Excel) but without totals interspread in it.
The option "Report Definition" is used to define the columns to be displayed
in the "Billing Report". These columns will be explained later in this chapter.
The information regarding the billing columns to be displayed is stored in the
file "tax_rep.dat" on the harddisk in the same directory from where "gwconfig"
software is running. In this file it is also saved the information about the size
of the columns presented in the billing report.
By pressing "OK" button all Billing records corresponding to the filter criteria
will be seen.
In the dialog window that shows up you can see a total for each day (from the
selected interval) and time intervals that include: total number of attempts
(field "Attempts"), total number of connected calls (field "Connected"),
ASR (field "ASR"), total duration of calls (conversation part-field
"Duration"), associated billing units (field "TaxUnits"), and at the end a total
for all of the intervals - total number of attempts, total number of connected
calls, ASR, total duration and billing units.
Note1: All the recordings, together with the totals, are saved in the "Viewer"
subdirectory for the chosen system in a file with the "tot" extension and the
name corresponding to the selected time interval. This way you may get both
the total of calls for several days and also a general total.
Note2: Once you have defined a filter for the billing files, some of its settings
will be saved, so you can apply the same filter to several billing files. The
settings established in the billing filter are saved in the file "tax_fl.dat" on the
harddisk in the directory where "gwconfig" software is running. These settings
are:"Port Type" (section "Call Source") - subscriber part and junction part,
"Release Side" ("A Side" or "B Side"), "Call Type" ("ANSWER", "RELEASE",
"INEX", "CONG", "SERR", "NERR", "NO ANSWER", "BUSY" and "TIMEOUT") and
the options regarding the viewing of totals and billing records ("Display only the
total without the records" and "Display only the records without a total"). These
settings are loaded before the showing of the billing filter in order to be preestablished.
Note3: a sorting operation can be performed on all fields (except "Type" field).
The sorting operation is activated by clicking the desired column. The first
operation on a field is an ascending sort. The indication will be the character
"^" which is added to the column name.
A second click on the same field will give an descending sort. The indication will
be the character "v" which is added to the column name.
An example of sorting the column "Ident" is provided for both ascending and
descending sort.
Depending of the number of records the sorting operation can take a significant
amount of time.

Administration, and Maintenance - ACTIVITY
The monitoring (activity) files are very detailed activity files, that record
everything about the calls. They are generated to detail the mode of call setup
and follow up the calls from and towards the ports that have checked the field
"Monitoring".
Activity files are named <current date>.mon and they include for each
routed call four activity recordings. For a call not routed the file contains only
two recordings representing just the calling part.
The first following example (with an answered call) contains a test call from
port "120" with the number dialed "81712345678". The identity of the call is
"120". Port "120" is allocated to the direction called "LOCAL". First line which
is starting with "TLI,00120" contains the original number and the original
identity. The rules (regarding the ignore and insert operations and the
maximum expecting digits) which are defined in the section "Define Calls
directions" are first applied to the number and to the identity. The line
preceded by "IN,00120" contains the modified number and the modified
identity according to the settings belonging to the "LOCAL" direction from
"Define Calls directions" table. The rules were "Ignore = 2" (ignore two digits)
and "Insert = '0'" (insert the digit '0') for the number, so the number was
changed from "81712345678" to "0712345678". The rules were "Ignore_id =
1" (ignore one digit) and "Insert_id = '33'" (insert the digits '33') for the
identity so the identity was changed from "120" to "3320". After the rules
established in "Define Calls directions" table are applied for the incoming part,
the call is routed by applying the "Route table" definition. In this table a record
with "Prefix = 0" is defined. In this case the fields "Ignore","Ignore_id","Insert"
and "Insert_id" are not specified.The third and fourth line represent the
outgoing part of the call routed through a GSM port "00008". Caller id sent
through this port is "3320" and number is "0712345678".
Note 1): an incoming call can be made from a subscriber or from a incoming
direction (containing E1 trunks or GSM modules);
Note 2): the fields that are specifying the modified number and the modified
identity are the same in the second and in the third line ("0712345678" for
the number and "3320" for the identity). Identity will appear modified or not
by fields "Ignore_id" and "Insert_id" from the "Define Calls direction" window
and by fields "Ignore_id" and "Insert_id" from the "Routing table" window.
Number will appear modified or not by fields "Ignore" and "Insert" from the
"Define Calls direction" window and by fields "Ignore" and "Insert" from the
"Routing table" window;
Note 3): the fourth line does not contain any information about the number
and the identity;
Note 4): the number and the identity can be also affected by the field
"Max_d", and respectively by "Max_id" from the "Define Calls direction"
window;
Note 5): the total number of digits that are well treated by "gwconfig" software
is 20 for identity field and number field;
Note 6): in the billing files the number and the identity will not appear
changed.
Note 7): the number, the identity and the IMSI values used above are for
testing purposes only;
TLI,00120,120 ,81712345678 ,10-0304,14:30:43,000004,00001,00,00008,BOK ,16,222222222222222,
17,abcd,GSM
IN ,00120,3320 ,0712345678 ,TD008,TSEL009,MODfe,0001,ff
TJO,00008,3320 ,0712345678 ,10-0304,14:30:43,000004,00001,ff,00120,BOK , 16, , 17,0000,
OUT,00008, , ,TD008,TSEL009,MOD01,0001,00
The second example (also with an answered call) contains a test call from port
"120" with the number dialed "81712345678". The identity of the call is "120".
Port "120" is allocated to the direction called "LOCAL". First line which is
starting with "TLI,00120" contains the original number and the original
maximum expecting digits) defined in the section "Define Calls directions" are
first applied to the number and to the identity. The line preceded by
"IN,00120" contains the modified number and the modified identity according
to the settings belonging to the "LOCAL" direction from "Define Calls directions"
table. The rules were "Ignore = 2" (ignore two digits) and "Insert = '51'"
(insert the digits '51') for the number, so the number was changed from
"81712345678" to "51712345678". The rules were "Ignore_id = 1" (ignore
one digit) and "Insert_id = '33'" (insert the digits '33') for the identity so the
identity was changed from "120" to "3320". After the rules established in
"Define Calls directions" table are applied for the incoming call, the call is
routed by applying the "Route table" definition. In this table a record with
"Prefix = 5" is defined. In this case the fields "Ignore=2" (ignore two digits)
and "Insert='0'" (insert the digit '0') (the fields "Ignore_id" and "Insert_id" are
not specified).The number "51712345678" will become "0712345678". The
third and fourth line represent the outgoing part of the call routed through a
GSM port "00008". Caller id sent through this port is "3320" and number is
"0712345678".
TLI,00120,120 ,81712345678 ,10-0304,15:08:44,000004,00001,00,00008,AOK ,16,222222222222222,

19,abcd,GSM
TJO,00008,3320 ,0712345678 ,10-0304,15:08:44,000005,00001,ff,00120,AOK , 16, ,19,0000
OUT,00008, , ,TD007,TSEL012,MOD01,0000,00
Note that there are two kind of records: first record like in lines 1 and 3 from
the previous example and the second record like in lines 2 and 4 (containing
"IN" and "OUT").
The first recording includes the fields:
RECORD
1
Field
Significance
Unfinished Incoming call: - MJI or MLI
(the call source is a junction respectively a
subscriber) or Finished (answered)
incoming call- TJI or TLI (the call source
is a junction respectively a subscriber)
Call Type
Unfinished Outgoing call: - MJO or MLO
outgoing call- TJO or TLO (the call source
Source Port
xxxxx - physical position of the source port

(5 digits);
Source
identity
subscriber number or source identity (20

digits). For outgoing records identity
("Ident") will appear modified or not by
fields "Ignore_id" and "Insert_id" from
the "Define calls direction" window and
by fields "Ignore_id" and "Insert_id"
from the "Routing table" window;
call number (20 digits).For outgoing
records this field will appear modified or
CallDigits
(Call
Number)
not by fields "Ignore" and "Insert" from

by fields "Ignore" and "Insert" from the
Day and
Time
Day and Time of the call in the following

format dd-mm-yy,hh:mm:ss ;
Connected xxxxxx - duration of the conversation in

Duration
seconds (6 digits);
Billing Units
xxxxx - billing Units for the call (5 digits);
for the call
Destination When the destination port is a GSM port
SIM
(multiACCESS or QUTEX) it specifies a
Number
value for SIM card (1,2,3,4 or ff);
- physical position of the destination port
Destination (5 digits) (when the call is unfinished a
Port
value of 65535 will be found in this field (5
digits);
Possible values are AOK, BOK, ARELS,
BRELS, AINEX, BINEX, ACONG, BCONG,
Finalization
ASERR, BSERR, ANERR, BNERR, ANANS,
call mode
BNANS, ABUSY, BBUSY, ATOUT and
BTOUT;
Finalization
Possible values are ' 31' (normal call) for
call mode
non ISDN calls or values corresponding to
on ISDN
ISDN standard for call release codes;
calls
IMSI
International Mobile Subscriber Identity (is

filled for incoming records routed through a
GSM port (multiACCESS or QUTEX))
Selection
Duration
xxx- three digits - cumulated selection

time in seconds. It cumulates both "Dial
time" (time in seconds for dialing the
number) and "Selection time" (time in
seconds while the response is waited for).
CELL
The GSM CELL (four digits - alphanumeric

code) where the SIM used for the call is
registered ("Destination SIM Number" on
the "Destination Port") (multiACCESS or
QUTEX). The cell info is useful to search
which cells from the network have

generated better ASR values.
Direction
The direction to which the destination port

is belonging (it is the output direction)
The second record contains:

RECORD
2
Field
Significance
IN (incoming call)
Call type
OUT (outgoing call)
Source Port
xxxxx - physical position of the source port (5 digits). This is the

destination port from the preceding record;
Source
Identity
Represents the source identity. For incoming records (preceded

by "IN") the identity may be modified by fields "Ignore_id" and
"Insert_id" established in direction definition and by fields
"Ignore_id" and "Insert_id" from "Routing table" window; for
records preceded by "OUT" this field is empty;
CallDigits
(Call
Number)
Number dialed (20 digits). For incoming records (preceded by

"IN") the number may be modified by fields "Ignore" and
"Insert" established in direction definition window and by fields
"Ignore" and"Insert" from "Routing table" window; for records
preceded by "OUT" this field is empty;
Dial time
TDxxx-time in seconds for dial;
Selection
time
TSELxxx-time in seconds when the response is waiting;
Call Type
MODxx -specified call type (0-incoming call, 1-outgoing call). This

field is used for further developments;
Finalization
mode
Possible value are 0000-AOK, 0001-BOK, 0002-ARELS, 0003BRELS, 0004-AINEX, 0005-BINEX, 0006-ACONG, 0007-BCONG,
0008-ASERR, 0009-BSERR, 000a-ANERR, 000b-BNERR, 000cANANS, 000d-BNANS, 000e-ABUSY, 000f-BBUSY, 0010-ATOUT,
0011-BTOUT(4 digits);
SIM
information
For calls routed to destination through a GSM module it

represents the active SIM card. Possible values are 1,2,3,4 or ff
(xx- 2 digits);
NOTE: The activity records are processed before viewing into a more simple
format by grouping two records (record 1 and 2) into a single one (chapter
"ACTIVITY").
By choosing "Activity" - tree command for a system, all activity (monitoring)
files from the subdirectory "Activity" of the selected system directory we'll be
displayed.
By double clicking with left mouse button on a file, a dialog window for activity
filter will be displayed. This filter allows setting several options for searching
the data from the "Activity" filter.
The "Period" area indicates (by default) the period which corresponds to the
selected Activity file name. This period can be changed in order to increase the
time interval to be analyzed. This software searches for "Activity" files having
assigned a name corresponding to this period. A time period can be also set (in
"Hour" area).
To specify filtering from the point of view of the source of calls you have the
following options:
- a direction (all source port on that direction will be searched)
- the source port type: local subscriber or junction
The following options for the call destination (called part) are available:
the number of destination digits less, greater or equal that the value typed.
- a direction (all destination port on that direction will be searched)
- the value of the SIM card (1,2,3,4 or 255)(when the destination port is a
GSM port)
activity records have a caller and a called party. For an incoming call on E1
represented by 'A' and called party by 'B'. Depending by the side which ends
the call a letter ( 'A' or 'B') will be shown and the finalization mode will contain
one of the following strings:
OK - ANSWER (call answered, response in the destination part)
RELS - RELEASE (release in other situation then ring-back tone or busy)
INEX - INEX (non-existent from equipment point of view - no defined route)
CONG - CONG (congestion from equipment point of view - no available
resources)
E1 trunk.
You can set a value for "ISDN EndType" which represent call release code for
ISDN calls. For other calls in billing records a value of ' 31' will be displayed.
You may set also the option to select the records with the conversation
duration (in seconds) less, greater or equal than the value typed.
You may set also the option to select the records with the selection duration
(in seconds) less, greater or equal than the value typed.
specifying IMSI code 16 and 20 for specifying destination digits.
Certain values from the monitoring filter are checked before the validation (by
pressing the button "OK"). The correctness of the period definition ( - (day and
hour - day less or equal then 31, month less or equal then 12, year less or
equal then 36, hour less or equal then 23, minute less or equal then 59 and
second less or equal then 59)), port position of the call source (in range 0 to
319), sim index (in range 1 to 4 or 255), destination port position (65535 or a
value in the range from 0 to 319), duration and selection duration (a value
greater or equal than zero), number of digits (a value greater or equal than
zero), ISDN EndType (a value greater or equal than zero); A message error
will be shown to the user and the field that was causing the error will be
colored in red (and the text color will become white). When the user gives
back the focus to the error field in order to correct the wrong data, then the
red color will disappear. In the following example an error message "Wrong
port value" is displayed because of an error field on port position (a value
"342" which is greater than the maximum number of 319).

in the "Activity Report". Those columns will be presented later in this chapter.
The information regarding the activity columns to be displayed is stored in the
file "mon_rep.dat" on the harddisk in the same directory from where
"gwconfig" software is running. In this file it is saved also the information
regarding the size of the columns presented in the activity report.
By pressing "OK" button (in the "Activity Filter" window) all activity records
complying with the filter criteria will be shown.
All these records will be saved in "Viewer" folder for the chosen system in a
file named "moni.tmp".
An activity record will contain (when all fields are selected to be presented in
the "Activity Record Definition" window) the following fields:
Field
Significance
Unfinished Incoming call: - MJI or MLI (the call source is a junction respectively a subscriber)
or Finished incoming call- TJI or TLI (the call source is a junction respectively a subscriber)
Type (Call type)
Unfinished Outgoing call: - MJO or MLO (the call source is a junction respectively a
subscriber) or Finished outgoing call- TJO or TLO (the call source is a junction respectively a
subscriber)
PortS (Source
Port)
xxxxx - physical position of the source port (5 digits);
Ident (Source
Identity)
subscriber number or caller identity (20 digits) (this field may be modified for outgoing
records by "Ignore_id" and "Insert_id" fields from "Define calls direction" and by fields
"Ignore_id" and "Insert_id" from "Routing table" window);
Ident Changed
(Source Identity
This field is filled only for incoming records and contains the changed source identity which
can be modified by "Ignore_id" and 'Insert_id" fields from directions definition window
and by fields "Ignore_id" and "Insert_id" from "Routing table" window; In the previous
Changed)
CallDigits (Call
Number)
picture it can be seen on the first record (an incoming call) in the field "Ident" the value
"120" modified in the field "Ident changed" to "3320" (like in the examples);
call number (20 digits)(this field may be modified for outgoing records by "Ignore"and
"Insert" fields from "Define calls direction" window and by fields "Ignore"and "Insert"
from "Routing table" window);
This field is filled only for incoming calls and contains the changed call number which can be
CallDigits
modified by "Ignore" and "Insert" fields from directions definition window and by
Changed(Call
"Ignore" and "Insert" by "Routing table" window; In the previous picture it can be seen
Number Modified) on the first record (an incoming call) in the field "CallDigits" the value "81712345678"
modified in the field "CallDigits changed" to "0712345678" (like in the examples);
Day and Time
(Day and Time of
the call)
Day and Time of the call in the following shape dd-mm-yy,hh:mm:ss
Selection
(Duration of the
selection and dial
phases)
xxx - selection duration of the call in seconds (3 digits); this time is calculated by adding the
values "Dial time" and "Selection time"
Connected
Duration
(Duration of the
call)
xxxxxx - connected duration of the call in seconds (6 digits)
TUnits (Billing
xxxxx - Billing Units for the call (5 digits)
Units for the call)
SIM1 (Destination When the destination port is a GSM port (multiACCESS or QUTEX) it specify a value for SIM
SIM Number)
card (1,2,3,4 or ff)
PortD (Destination - physical position of the destination port (5 digits) (when the call is unfinished a value of
Port)
65535 will be found in this field (5 digits)
End (Finalization
call mode)
Possible values are AOK, BOK, ARELS, BRELS, AINEX, BINEX, ACONG, BCONG, ASERR,
BSERR, ANERR, BNERR, ANANS, BNANS, ABUSY, BBUSY, ATOUT and BTOUT
End 2(Finalization
Possible values are ' 31' (normal call) for non ISDN calls or values from ISDN standard for
call mode on
release code
ISDN calls)
Dial (Dial time)
xxx-dial time in seconds
Sel (Selection
time)
xxx-selection time in seconds
Call (Call type)
xx-specify call type (0-incoming call, 1-outgoing call). This field will be used for further
purposes.
SIM2 (Source SIM When the source port is a GSM port (multiACCESS or QUTEX) it specify a value for SIM card
Number)
(1,2,3,4 or ff)
IMSI
International Mobile Subscriber Identity (is filled for incoming calls routed through a GSM
port (multiACCESS or QUTEX))
CELL
The GSM CELL where the SIM used for the call ("Destination SIM Number" on the
"Destination Port") is registered.(multiACCESS or QUTEX)
Direction
The direction to which the destination port is belonging (it is the output direction)
Note1: several settings established in the monitoring filter are saved in the file
"moni_fl.dat" on the harddisk in the directory where "gwconfig" software is
running. These settings are:"Port Type" (section "Call Source") - subscriber
part and junction part, "Release Side" ("A Side" or "B Side") and "Call Type"
("ANSWER", "RELEASE", "INEX", "CONG", "SERR", "NERR", "NO ANSWER",
"BUSY" and "TIMEOUT"). These settings are loaded before the showing of the
monitoring filter in order to be pre-established.
An example of sorting the column "Day and Time" is provided for both
ascending and descending sort.
amount of time.

Administration, and Maintenance - VIEWER FILES
In this section we can view all files from "Viewer" directory in the selected
system directory.
We make left double click with mouse on a file and view content of the file.
Files are viewed in text mode.
There are several extensions which are directly interpreted and viewed in a
non-text mode. Those extensions are "tot" for billing records, "mes" for sms
records and "moni.tmp" for activity records. For those extensions the display
mode is the same like for billing files, sms files and activity files.

Administration, and Maintenance - ASR
Answer seizure ratio (ASR) is an important parameter because it gives a very
good indication of how well the equipment (in this case multiACCESS/QUTEX)
performs. ASR shows the relationship between the number of seizures that
result in an answer signal and the total number of seizures. Thus, ASR is a
direct measure of the effectiveness (how many of the attempted calls were
completed) of the service performed. ASR is defined as the ratio between the
number of "seizures" that result in an answer signal and the total number of
seizures, in a specified period of time.
In order to calculate the several ASR instant and average values, the ASR files
store parameters such as number of answered calls, total number of calls, total
connected time and total seized time.
The asr files are named <current date>.asr.
The saving of the ASR values in files is determined by the parameter "Validate
ASR reading". This parameter together with the time delay between savings
can be edit by choosing icon option "Alerts" (" ").
The lines of the file are grouping two by two, one line contains general data
(average and totals) and the next line instantaneous data. The general values
are the cumulated values from the beginning of the ASR saving and the
instantaneous values are the values stored at specified delay periods.
Note: For a line all the values are calculated for the specified period.
The fields of the asr files are shown below:
Field
ASR value
Average time (in
seconds)
Total number of calls
Total number of
answered calls
from 'A' part (calling
party)
from 'B' part (called

party)
Total Seized Time (in
seconds)
Total Connected Time
(in seconds)
By choosing "ASR" - tree command for a system, all ASR (statistics) files from
the folder "Alarms" of the selected system directory we'll be seen.
Double click with the left mouse button, then a dialog box for making an ASR
filter we'll be seen. ASR filter indicates how to check options and values for
searching inside the alarms directory.
By default the "Period" area indicates the time interval which correspond to
the name of the selected ASR file. This period can be changed in order to
increase the time frame. This software is searching for ASR files having
assigned a name corresponding to this period. The maximum size of the fields
is 8 for the periods (date). The correctness of the period definition is checked
before the validation of the "Asr Filter" (day less or equal then 31, month less
or equal then 12 and year less or equal then 36). An error message is shown if
period is not correct chosen.
There is an option for viewing ASR results (records) in graphical mode or text
mode. For the text representation it is allowed to set also the option 'Only
Total" for displaying only the total, not all the ASR records.
Graphical representation allows the following statistics:
Note: instantaneous values from the "ASR" files are used in the statistics
representation. The statistics are done on hour periods. For a single day for
"ASR" statistics and "Average Time" statistics, an additional average
calculation is performed on an hour period if the number of recordings on that
hour is greater than one. For calls and time statistics a SUM calculation is
performed on an hour period if the number of recordings on that hour is
greater than one. This method of calculation is extended in case of selecting
more then one day.
1. ASR Statistics
When the number of calls on a hour period is zero, the ASR value is undefined
so the graphic will be represented by a dotted line. On the right side there are
displayed ASR values for each time period.
2. Average Time Statistics
The image shows the evolution of average time value. On the right side are
displayed average time values for each period (in seconds).
3. Calls Statistics
You may see the evolution of number of total calls ("Total Calls"), total calls
ending with response ("Connected"), total calls released from the calling party
("ARELS") and total calls released from the called party ("BRELS"). The values
for total calls released from "A" or "B" part are containing all possible
situations for ending a call. On the right side are displayed those values for
each hour period and colors used for each type of values (blue, red, grey and
white).
4. Total seized time and connected time statistics
In the image above it can be observed the evolution of total seized time
("TIME") and connected time ("TIMECON"). In the right side the values in
seconds for each hour period are shown.
To switch from one statistic to another you must use the buttons located on
the upper side of the dialog box.
All these graphics can be printed by choosing option "Print" (if a printer is
installed);
Text representation - when selected, it displays all records from the ASR
files as text only. As shown below, the records are grouped two by two, with
general and instantaneous ASR values.
- Lines beginning with character 'G' or 'I' show if the record is general or
instantaneous. ASR value is following, "MT" characters, the average time of
speaking (in seconds), record time, total number of calls ("CALLS"), total
number of connected calls ("CONN"), total number of calling part release calls
("ARELS"), total number of called part release calls ("BRELS"). Next is total
seized time ("TIME") and connected time ("TCON") both of them in seconds.
- If you have several files to be shown, they will be displayed one after
another. Then, at the end, a general (overall) total will be shown for
instantaneous records. The general total is computed like this:
- for ASR and average times, a mean is computed over the number of records
in the selected period of time;
- for other values, a SUM is performed (values are added);
- At the end, there is a general total for instantaneous records and on time
periods: ASR and average time, number of calls and time values.

Administration, and Maintenance - SMS FILES
These files are used to keep information regarding the sending of short text
messages (SMS) and about the calls made from an internet browser. SMS's
can be sent and CALLS can be made from any internet browser by accessing
the TOPEX gateway. The "SMS" files are named <current date>.sms. The SMS
files are also containing the CALLBACK actions.
1) To send a SMS just connect to the gateway to the "txsms.html" page (to
reach this page, you must first type into the browser's address bar the IP
address of the TOPEX gateway).
For accessing the TOPEX gateway, you must add its IP address to the section
"Trusted sites" for your browser. The format of the record to be added is
"http://xxx.xxx.xxx.xxx" where "xxx.xxx.xxx.xxx" is the IP address of the
TOPEX gateway. The authentication of clients is performed using "Digest
Authentication" algorithm.
Accessing TOPEX gateway from an Internet browser is password protected. You
must logon with your name and password.
The default password is "topex".

After going over the password protection, a new page will appear asking the
user to enter the SMS destination phone number (field "Phone Number") and
the SMS message (field "SMS text"). The SMS will be sent by clicking the
"SendSms" option. The SMS can't be sent if direction named "SENDSMS" does
not exist on the target.The SMS number will be parsed with all the rules which
are included in the definition of the "SENDSMS" direction and the routing
table.
A successful message will appear to inform the user that the SMS has been
sent ("OK Your SMS was sent OK! Thank you!").
Example of SMS records in a SMS file:
SMS ,WWW ,192.168.1.152 ,0700000000 ,12-0304,07:24:50,000005,00004,00,00008,BOK , 16,222222222222222
SMS ,WWW ,192.168.1.152 ,0700000000 ,12-0304,07:26:12,000000,00000,ff,65535,ASERR, 16,
SMS ,WWW ,192.168.1.152 ,0700000000 ,12-0304,07:27:02,000000,00000,ff,65535,AINEX, 16,
- first record is containing a SMS message from the address "192.168.1.152"
to the number "0700000000". The SMS was sent successfully ("BOK");
- second record contains a SMS message from the address "192.168.1.152" to
the number "0700000000". The SMS was not sent successfully because the
direction called "SENDSMS" was not existent on the target ("ASERR");
- the third record is containing a SMS message from the address
"192.168.1.152" to the number "0700000000". The SMS was not sent
successfully because no route to destination was found ("AINEX");
Note 1): the total number of digits that can be processed by "gwconfig"
software is 20;
Note 2): the number, the identity and the IMSI values which are used are only
for testing purposes;
Note 3): the code "WWW" is used only to indicate the origin of the SMS
("WWW");
There is also another page called "txsmsgrp.html" which is used to send a SMS
to a group of mobile phones. These groups can be defined on the gateway in

the file "/mnt/app/cfg/sms_groups". The structure of this file is as following:
grup test
0740000001
0740000002
The "Group Name" in the previous picture will be filled in with the group
name: in the displayed example the group name is "test" (the word which
follows the key word "grup". The SMS will be sent to the phone numbers that
follow the line with "grup" keyword. The numbers are searched until an empty
line is found or until another line starting with "grup" is found.
sent ("Your SMS has been sent OK! Sent to 2 numbers"). The number of
mobile phone destinations is also displayed.
2) A call can be sent in the same way by accessing the page "txcall.html". To
allow sending a CALL from an Internet browser the direction called
"SENDCALL" must exist on the target. The call will pass all the rules which are
included in the definition of the "SENDCALL" direction and the routing table.
The user must enter the CALL destination phone number (field "Phone
Number") and further options (field "Call Options" - not yet implemented).
A successful message will appear to inform the user that the CALL will be made
Example of records regarding making CALLS from a SMS file:
CALL,WWW ,192.168.1.152 ,0700000000,12-0304,07:45:49,000000,00000,ff,65535,AINEX, 16,
CALL,WWW ,192.168.1.152 ,0700000000,12-0304,07:47:10,000000,00000,ff,65535,ASERR, 16,
CALL,WWW ,192.168.1.152 ,0700000000,12-0304,07:48:10,000040,00004,00,00008,BOK , 16,222222222222222
- first record is containing a CALL test made from the address "192.168.1.152"
to the number "0700000000". The CALL wasn't made ("AINEX") because no
route to destination was found;
- second record is containing a CALL test from the address "192.168.1.152" to
the number "0700000000". The CALL was not made because the direction
called "SENDCALL" was not existent on the target ("ASERR");
- the third record is containing a CALL test from the address "192.168.1.152"
to the number "0700000000". The CALL was made successfully ("BOK"); the
called part was answered;
Note 1): The total number of digits that can be processed by "gwconfig"
software is 20;
Note 3): the code "WWW" is used only to indicate the origin of the CALL
("WWW");
3) SMS ALERT indication. When a SMS alert is sent, the current SMS file
contains the number and the moment of sending and the following fields:
"Type" -> "SMS", "Source" -> "ALARM" and "IP" -> 127.0.0.1.
SMS ,ALARM,127.0.0.1 0700000000 ,08-1004,16:44:11,000599,00010,00,00033,BOK , 16,226019451004927
4) CALLBACK records
CALL,CBACK,0700000000 ,0700000000 ,13-04-
04,11:25:33,000001,00000,00,00008,AOK , 16,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:32:32,000013,00000,ff,00008,BBUSY, 17,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:33:14,000007,00000,00,00008,BRELS, 16,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:36:07,000001,00000,00,00008,AOK , 16,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:40:22,000012,00000,00,00008,BBUSY, 17,226019451004927
CALL,CBACK,0700000000 ,0700000001 ,13-0404,12:03:40,000001,00000,00,00009,AOK , 16,226019451004922
A record is generated into a SMS file for each back call. Callback table contains
the following fields: "Identity", "Action", "Callback", "CallTo" and "MailTo". A
CALLBACK record contains the identity (in the example it is the field
"0700000000" - the identity is one of the "Identity" from the Callback table)
and the number dialed in the callback action. The number dialed can be the
same number like the identity number or can be another one (if the field
"Callback" is filled with another number then the identity number).
In the billing file, the number dialed by the called party of the back call action
will be saved. If the "CallTo" field is filled in the callback table then that
number will be saved in the billing file.
A SMS file has the following fields:
Field
Description
Record
type
SMS or CALL (the record is a SMS

respectively a CALL test)
Source
Port
WWW (for SMS and CALLS made from the

internet),CBACK and ALARM
IP or
identity
the IP address of the client from where the

SMS was sent or the CALL was launched
(20 digits) or the identity of the call in case
of a CALLBACK record
CallDigits
(Call
SMS destination number or CALL test

number (20 digits) or the number called in
Number)
a CALLBACK record
Day and
Time

shape dd-mm-yy,hh:mm:ss (ending time)
Call
Duration
xxxxxx - duration of the call in seconds (6

digits). Is different from a zero value in
case of a successful sending of a SMS or
making a CALL test and indicates the
amount of time from the moment of
accepting the request and the moment of
the successful ending;
Length
xxxxx - the length of SMS message and the

length of the option of CALL message (5
digits) or 00000 for a CALLBACK record
Destination
When the destination port is a GSM port it
SIM
specify a value for SIM (1,2,3,4 or ff)
Number
Port
digits)
Finalization BRELS, AINEX, BINEX, ACONG, BCONG,
call mode ASERR, BSERR, ANERR, BNERR, ANANS,
BNANS, ABUSY, BBUSY, ATOUT and BTOUT
Finalization
Possible values are either ' 31' (normal call)
call mode
for non ISDN calls or values corresponding
on ISDN
to ISDN standard for call release codes
calls
IMSI
International Mobile Subscriber Identity
By choosing "SMS" - tree command for a system, all SMS files from the folder
"Billing" of the selected system directory we'll be seen.
You choose the SMS file you want to see, and by double clicking the left mouse
display of the SMS information. This filter for SMS files permits setting the
options and values for searching the records inside the SMS files.
the SMS file that you have selected. Sub-fields are Day and Hour each of
them with "From" and "Until" limits. You may change the default period to
extend the time interval that is analyzed. The program will look for records in
the SMS files whose name fall inside the selected time period.
From the source point of view you may specify the following options:
- IP source;
- you may specify the source value: (this value can be used in further
developments);
- the record type: SMS or CALL;
- the record source: WWW or CBACK or ALARM;
From the call destination (called party) point of view you may specify the
following options:
the number of destination digits less, equal or greater then the value typed.
port)
SMS records have a caller and a called party. For an incoming call on E1 trunk
the source party will be a channel on the trunk and the call will be routed over
a GSM interface (the destination port). Caller party will be represented by 'A'
and called party by 'B' (field "Release Side"). Depending by the side which
ends the call a letter ( 'A' or 'B') will be shown and the finalization mode will
contain one of the following strings: OK - ANSWER, RELS - RELEASE, INEX INEX, CONG - CONG, SERR - SERR, NERR - NERR, NANS - NO ANSWER, BUSY
- BUSY, TOUT - TIMEOUT. "Call Type" lets you to specify the mode of ending
of the call.
You may set a value for "ISDN EndType" which represent call release code
for ISDN calls. Other types of calls will display a value of ' 31' in the SMS
records.
You may set also the option to select the records with the duration (in
seconds) less, equal or greater then the value typed.
number of digits, 3 for the sim index and ISDN EndType, 5 for destination port
position, 6 for duration, 15 for the IP field, and 16 for specifying IMSI code and
20 for specifying destination digits.
Certain values from the SMS filter are checked before the validation (by
pressing the button "OK"). The correctness of the period definition (day and
second less or equal then 59), sim index (in range 1 to 4 or 255), destination
port position (65535 or a value in the range from 0 to 319), duration (a value
back the focus to the error field in order to correct the wrong data, the red
color disappears. In the following example an error message "Wrong sim
index" is displayed because of an error on SIM field (a value "5" which is
greater than the maximum number of a SIM card (4).
(option "Display only the total without the records") that correspond to
the records in a certain time interval for the purpose of post-processing (cost
analysis) of the stored SMS information. For these applications, you need a
text file with values only (that may be imported into a spreadsheet like Excel)
but without totals interspread in it.
in the "SMS Report". These columns will be presented later in this chapter. The
information regarding the SMS columns to be displayed is stored in the file
"sms_rep.dat" on the harddisk in the same home directory from where
"gwconfig" software is running. In this file is also saved the information
regarding the size of the columns presented in the SMS report.
By pressing "OK" button all SMS records corresponding to the filter criteria will
be seen.
(field "Attempts"), total number of SMS successfully sent (field
"Connected") and the percentage of successfully SMS sent- (field "Period")
and in the end a total for all of the intervals - total number of attempts, total
number of connected and the percentage of successfully connections.
subdirectory for the chosen system in a file with the "sms" extension and the
the total of records for several days and also a general total.
Note2: several settings which are established in the SMS filter are saved in the
file "sms_fl.dat" on the harddisk in the home directory where "gwconfig"
software is running. These settings are:"Record Type" (section "Call Source") SMS or CALL,"Record Source" (section "Call Source") - WWW or CBACK or
ALARM, "Release Side" ("A Side" or "B Side"), "Call Type" ("ANSWER",
"RELEASE", "INEX", "CONG", "SERR", "NERR", "NO ANSWER", "BUSY" and
"TIMEOUT") and the options regarding the viewing of totals of SMS records
("Display only the total without the records" and "Display only the records
without a total"). These settings are loaded before the showing of the SMS
filter in order to be pre-established.
If the number of records is large, the sorting operation can take a significant
amount of time.

Administration, and Maintenance - LOG FILES
The log files are named <current date>.log and contain information about
the events that took place: date and time for the making and respectively
breaking of connections concerning the selected TOPEX system, file transfer
and so on.
Field
Description
Date
dd-mm-yy
Hour
xx:xx:xx
Event
Description of the event that was performed
The lch files are named <current date>.lch and include information about the
changes (modifications) made to the TOPEX multiACCESS/QUTEX system.
Field
Description
Date of change
dd-mm-yy
Time of change
xx:xx:xx
Modification
Description of the change that was performed

OK - the change was successfully
Status
ERROR - the change was not successfully
By choosing "Log" (tree command for a system), then all connections log
(extension is *.log) files and changes log (extension is *.lch) files from the
folder "Log" of the system directory we'll be seen.
All these files are located inside folder "Log" of the root system directory.
The "log" files contain information indicating time and date of connection and
disconnection related to the chosen system.
Here are saved all the operations regarding downloading and loading of files.
There are specified directories ("bin", "cfg" or "out" from the remote gateway)
and the file name involved into the transfer operation. Also here are saved the
ASR values and alarms gathered during automatic interrogation process.
In "lch" files there is information related to the time of modifications operated
on the remote gateway.
- In the image above there are some examples: Rights modified for ports,
Adding card, Deleting card, SIM index modification.
- In this type of files also the results of the changes: OK or ERROR are shown.
For all possible changes there are verification made by OAM software and also
by remote gateway. Remote gateway may respond with an ERROR message.
You will get an error, for instance, when you try to allocate the same number
to two different ports.

Administration, and Maintenance - LOADING COMMAND
The "Loading" command provide statistics about billing files, allowing the
user to have data about each SIM, GSM module and directions.
By selecting "Loading" - tree command for a system, all billing files from the
folder "Billing" of the selected system directory will be displayed.
You go to the billing file you want to analyze, and by double clicking with left
mouse button a dialog window will pop up, allowing you to build a filter for
selective display of the statistic information. This "Display Statistics" filter for
billing statistics permits the setting of options and values for highlighting
records.
The first field, "Period", indicates the time period (by default the period
corresponds to the name of the billing file that you have selected). The
program will look for records in the billing files whose name falls inside the
selected time period.
For highlighting you may specify the following options:
- "ASR" (you may define a threshold: the default is an initial value of 70%);
- "Average duration" (a threshold can be defined: the default is 120 seconds);

- "Duration < x seconds" (a threshold can be defined: by default you have an
initial value of 20%); For 'x' a value of 20 seconds is used by default.
There is a text limit of 8 for period files and 3 for the other three fields.
The correctness of the those value is checked: periods (day,month,year),
percentage for "ASR" and "Duration < x seconds" (a value between 0 and 100)
and "Average Duration" (greater than 0). A bad filled value will cause a red
color to fill that field and an error message to appear. The red color will
disappear when the user will give back the focus to the error filled field.
After you select "OK" button, the statistics shown below will appear:
In the above image two panels can be seen: the first one contains "Input" data
and the second "Output" data.
Statistics are provided for each port and include the following columns:
- "Port"
- "Dir" (direction)
- "Type" (GSM, SUBSCRIBER, BC, BL, EM, PABX, E1R2, ISDN, SS7 and R1)
- "SIM" (is filled only for GSM ports and on outgoing calls and it can be 1,2,3
or 4)
- "Attempts" (number of call attempts)
- "Connected" (number of connected calls)
- "ASR"
- "Minutes" (number of spoken minutes)
- "Duration" (average duration of the conversations)
- "Duration<" (percentage of calls with a duration below 20 seconds).
Highlighting is done with red color and can appear on the columns: "ASR",
"Duration" and "Duration<".
The lists in the two panels are filled only with ports that have been active, that
is from which or to which calls where made or routed.
Each list contains at the bottom a total statistic and statistics over directions.
For the "Output" area there is also presented a statistic for each different GSM
Cell.
By pressing a record from the one in the lists an additional image will be
provided, showing graphically details about calls: normal completion, release,
errors.
The image contains three columns: first column from the left contains a
statistic over calls (on that port, on a direction or on total): TOTAL number,
"Completed", "Release", "Inex", "Cong", "Serr", "Nerr", "Nans", "Busy" and
"Tout". The second column contains a statistic over calls ended from the "A"
part and the last column a statistic over calls ended from "B" part.

Administration, and Maintenance - ASR
Answer seizure ratio (ASR) is an important parameter because it gives a very
good indication of how well the equipment (in this case multiACCESS/QUTEX)
performs. ASR shows the relationship between the number of seizures that
result in an answer signal and the total number of seizures. Thus, ASR is a
direct measure of the effectiveness (how many of the attempted calls were
completed) of the service performed. ASR is defined as the ratio between the
number of "seizures" that result in an answer signal and the total number of
seizures, in a specified period of time.
In order to calculate the several ASR instant and average values, the ASR files
store parameters such as number of answered calls, total number of calls, total
connected time and total seized time.
The asr files are named <current date>.asr.
The saving of the ASR values in files is determined by the parameter "Validate
ASR reading". This parameter together with the time delay between savings
can be edit by choosing icon option "Alerts" (" ").
The lines of the file are grouping two by two, one line contains general data
(average and totals) and the next line instantaneous data. The general values
are the cumulated values from the beginning of the ASR saving and the
instantaneous values are the values stored at specified delay periods.
Note: For a line all the values are calculated for the specified period.
The fields of the asr files are shown below:
Field
ASR value
Average time (in
seconds)
Total number of
answered calls
from 'A' part (calling
party)
from 'B' part (called

party)
Total Seized Time (in
seconds)
Total Connected Time
(in seconds)
By choosing "ASR" - tree command for a system, all ASR (statistics) files from
the folder "Alarms" of the selected system directory we'll be seen.
Double click with the left mouse button, then a dialog box for making an ASR
filter we'll be seen. ASR filter indicates how to check options and values for
searching inside the alarms directory.
By default the "Period" area indicates the time interval which correspond to
the name of the selected ASR file. This period can be changed in order to
increase the time frame. This software is searching for ASR files having
assigned a name corresponding to this period. The maximum size of the fields
is 8 for the periods (date). The correctness of the period definition is checked
before the validation of the "Asr Filter" (day less or equal then 31, month less
or equal then 12 and year less or equal then 36). An error message is shown if
period is not correct chosen.
There is an option for viewing ASR results (records) in graphical mode or text
mode. For the text representation it is allowed to set also the option 'Only
Total" for displaying only the total, not all the ASR records.
Graphical representation allows the following statistics:
Note: instantaneous values from the "ASR" files are used in the statistics
representation. The statistics are done on hour periods. For a single day for
"ASR" statistics and "Average Time" statistics, an additional average
calculation is performed on an hour period if the number of recordings on that
hour is greater than one. For calls and time statistics a SUM calculation is
performed on an hour period if the number of recordings on that hour is
greater than one. This method of calculation is extended in case of selecting
more then one day.
1. ASR Statistics
When the number of calls on a hour period is zero, the ASR value is undefined
so the graphic will be represented by a dotted line. On the right side there are
displayed ASR values for each time period.
2. Average Time Statistics
The image shows the evolution of average time value. On the right side are
displayed average time values for each period (in seconds).
3. Calls Statistics
You may see the evolution of number of total calls ("Total Calls"), total calls
ending with response ("Connected"), total calls released from the calling party
("ARELS") and total calls released from the called party ("BRELS"). The values
for total calls released from "A" or "B" part are containing all possible
situations for ending a call. On the right side are displayed those values for
each hour period and colors used for each type of values (blue, red, grey and
white).
4. Total seized time and connected time statistics
In the image above it can be observed the evolution of total seized time
("TIME") and connected time ("TIMECON"). In the right side the values in
seconds for each hour period are shown.
To switch from one statistic to another you must use the buttons located on
the upper side of the dialog box.
All these graphics can be printed by choosing option "Print" (if a printer is
installed);
Text representation - when selected, it displays all records from the ASR
files as text only. As shown below, the records are grouped two by two, with
general and instantaneous ASR values.
- Lines beginning with character 'G' or 'I' show if the record is general or
instantaneous. ASR value is following, "MT" characters, the average time of
speaking (in seconds), record time, total number of calls ("CALLS"), total
number of connected calls ("CONN"), total number of calling part release calls
("ARELS"), total number of called part release calls ("BRELS"). Next is total
seized time ("TIME") and connected time ("TCON") both of them in seconds.
- If you have several files to be shown, they will be displayed one after
another. Then, at the end, a general (overall) total will be shown for
instantaneous records. The general total is computed like this:
- for ASR and average times, a mean is computed over the number of records
in the selected period of time;
- for other values, a SUM is performed (values are added);
- At the end, there is a general total for instantaneous records and on time
periods: ASR and average time, number of calls and time values.

Administration, and Maintenance - SYSTEMS
1. Add
- If you select "System > Add" the following window will appear, asking you to
add another TOPEX multiACCESS/QUTEX system to the arborescent structure.
Directory - enter a name for the folder in where the files downloaded from
the TOPEX multiACCESS/QUTEX system will be stored.On HDD it will be made
a directory in the following shape "cfg_xxxxxxx" where directory is the name
typed in the "Directory" field. The folder will be created on HDD in the
directory where the executable 'gwconfig.exe' is located.
Name - enter a name for the connection to the system. This names is
concatenated at "cfg_" and this it will be the text used in tree structure for
identifying the system.
Serial communication / IP communication - is specified link type between
OAM computer and E1/30 GSM equipment. This are the two exclusive options
for the communication with a TOPEX gateway equipment.
IP Parameters:
IP address - enter the IP address of the system. It can be a numeric IP

address or a text address (in that case a dns request will be made by
software).
IP Port num - enter the number of the port through which the
communication with the system is achieved. The default value is 9009. This
value is established also into the gateway system and should not be modified.
DialUp Connection - in case of IP communication this setting allows if is
checked, a dialup connection to be established. The Dialup Connection must be
create from Windows (from "Dial-Up Networking") and the connection name
must not contained character space inside the text.
Option "Use PPP address" is used to indicate the "gwconfig" software to
connect to the dialup server address after a successfully connection. If this
option is not validated, then the "gwconfig" software will try to connect to the
address specified in the "IP address" field.
If this parameter is checked you may choose a dialup connection from "DialUp
connection name". You must enter a "DialUp Number" which override the
number used at the creation of the Dialup Connection. Also by pressing "Edit"
button you can override the "User" and "Password" used in process of
authentication.
You must note that if changes are made to "User" or "Password", those
changes are made also in the Windows registry.
The field "Connection Timeout" is the time in seconds wait from the moment of
starting the DialUp connection and the obtaining the connection state.
Serial Communication:
Serial Port num - enter the serial port used in case of serial communication
with the gateway. The default value is COM1. This value must be in range
COM1-COM12.
There is a text limit of 19 characters for the "Directory" and "Name" fields and
2 characters for the "Serial Port num".

colored in red.
Also, value check is performed for the "Directory" and "Name" fields. If one of
this values is not filled or is the same as an already existent "Directory" or
"Name" (are used for another system), an error message will be displayed and
the incorrect field will be colored in red, as shown in the following image:
Save - saves the setting and adds in the tree structure a system with the
modified settings
Cancel - closes the window without saving the settings.
Note: in case of reduncancy when two processor card are used the "Add
system on position..." window will be different:
2. Remove
- If you select "System > Remove" then you will see the next window:
- To remove a TOPEX multiACCESS/QUTEX system from the structure, select it

and then click on 'Save' button: the selected system will be deleted from the
tree structure; the folder (directory) on your hard disk drive won't be deleted,
you must erase it manually. If you select Cancel the window will be closed.
Note: There is also a tree command for changing systems parameters: Name,
communication type, IP Address, IP port number, DialUp parameters and serial
port number.

Administration, and Maintenance - FACILITIES
1. Font
If you select "Facilities > Font" the following window will appear:
In this window you can select according to your preferences the font, the style
and size of characters. The changes will only affect the windows called: "View
Configuration" and "Modify Configuration".
2. Colors signification
The significance of the colors used in the "View Configuration" and "Modify
Configuration" windows is here described, as explained below:
- Dark blue - that position is available (free)
- Red - that position is in alarm
- White - that position is already used (busy)
- Light blue - that position is not installed (the checkbox "Installed" from the
window for configuring the settings of the port has not been installed).
The colors which are here presented are the default settings.
There are also shown the colors used for "TextColor", "BackColor" and
"TreeColor".
All these colors can be modified according to users preferences by clicking on
it.
You can select the color you want, either from the predefined "Basic" colors,
either from the detailed zone of custom colors.
- The "Default" button is used to restore color settings to the original color set.
- The text column at the right of "Color signification" window explains the
meaning of values shown for a GSM port in alarm. When a user selects the
icon "Status monitoring" in a connected state, additional information will be
provided for GSM ports. If the GSM module is displayed in red color (therefore
no SIM registered) then after the port position and a line character a value is
shown, describing the cause of the error.
- example of a GSM module in alarm displayed in red color. Here the
cause of error "2" - "no physical SIM".
Possible error causes are:
0 - GSM module in initialisation phase (programming)
1 - no GSM network available ("at+creg?" phase)
2 - no physical SIM
3 - no logical SIM. This value may be obtained in the following situations:
- when the "SIM index" rule is used for changing the SIM cards for the GSM
module but for the current time moment no SIM value is specified in the "SIM
index".
- If "LOAD BALANCING" algorithm is selected to change the SIM on the GSM
module and the "Load Sim" value (the usage time of the SIM) is over the SIM
maximum time to use ("Max").
4 - GSM module error - the module is not responding at "AT" commands
5 - the GSM module is requesting PUK code
3. View print files
- This command is a facility for viewing text files located in "FORMAT" folder.
These files can be made by printing data into files from different locations from
program. To see a file, select its name from the list and click the 'View' button.
A window for viewing/editing the file will appear.
- You can also perform searches by using the buttons marked 'FIND' and
'NEXT' or you can send to the printer a listing of the file.
4.Commands
Use this option for entering direct commands for the system. This part of the
OAM program is "expert level only". You may resize or move the window
"Configuration manager on the screen as you wish. The windows position and
dimensions will be saved in a file on HDD in order to be preserved for future
use.
"Log Section" - if the option "LogFile" is checked, then a log file will be
generated. This file allows the user to analyse later the commands sent to the
gateway and the responses from the gateway. The logfile is always named
"command.txt". The option "Reset" is used to clear the file used for saving the
log.
The commands to be issued to the TOPEX gateway are filled in "OAM" edit
field, at the top of the window. A command is sent to the gateway after
pressing the <ENTER> key.
The command window is useful for several purposes. For instance it allows a
direct conversation with a GSM module (by using AT commands). The user can
also set PIN codes, start debugging, display the number of calls, etc.
"AT commands": if you want a GSM module to accept AT commands you
must put the associated port into a monitoring state (that port must belong to
an installed GSM board).
Therefore the first command sent for putting the GSM module into AT
commands accepting mode is "set moni xxx", where "xxx" is the GSM port
number (as it appears on the "gwconfig" panel). The gateway must send back
the confirmation message "moni xxx", where 'xxx' is the GSM port position. If
the GSM port can't be placed into the monitoring state the following warning
message is received: "res moni" (in the "Exchange response zone" section).
This message is received if the GSM port is busy or initialisations are
performed on that module. If that is the case the user must type first "res
moni' and then "set moni xxx".
When the confirmation from the gateway is received, several AT commands
can be sent to the gateway:
AT Command
Purpose
Response
AT
Allows the user to

check the
functionallity of the
GSM module
AT+CPIN?
-ERROR - there is no
The GSM module is SIM installed or there
interrogating about is another error
pin code. This is a
-READY - if no PIN
useful method to
code is required
check if a SIM card is -SIM PIN - the SIM is
plugged in a GSM
waiting for PIN code
module.
-SIM PUK - the SIM is
waiting for PUK code
This AT command is
used to check if the
Should be "OK" in
case of success
The response is:

+CREG:<n>,
<stat>,"xxxx","xxxx"
where <stat> can be:
- stat = 0 - the
module is not
registered and does
not try to register to
a GSM operator
- stat = 1- the
within a GSM network
AT+CREG?
within the GSM

network.
- stat = 2- the
module is not
registered but is
trying to register to a
GSM operator
- stat = 3- the
registration is not
allowed
- stat = 4- unknown
- stat = 5- the
and he has roaming
AT+CLIR=<n>
where n=0 for
default,
where n=1 for
not sending the
identity and
n=2 to allow
the sending the
identity
The module is
with a delay that
This command is
depends upon the
used to enable or
loading of the GSM
disable the sending
network. Until the
of the identity (caller
response is waiting an
ID)
additional AT
command must not be
sent to the module
AT+CLIR?
+CLIR:1,4 - the
identity is not send
To check the setting +CLIR:2,4 - the
of identity
identity is send
+CLIR:0,4 - default
value
AT+CLIP=<n>
where n=0 for
not displaying To display or to not
the identity of display the identity
the calling part of the calling part in The module is
case of a call through responding with "OK"
and n=1 to
allow displaying the monitored GSM
port
of the calling
part identity
The response can be:
OK - the destination
part has answered

ATD<number>;
NO CARRIER - the
This is an useful
Where
destination part does
method to make a
<number> is
not respond or it is
call test directly from
the number to
not in the covered
the GSM module
be dialed
area
BUSY - the
destination part is
busy
Is used for
responding to an
incoming call. When
incoming call is
routed through a
GSM module which is
in monitoring state,
the "RING" word will The GSM module is
ATA
appear at each 5
seconds. If CLIP is
activated then a
message with the
calling number will
be displayed:
+CLIP:"calling
number",xxx
ATH
The command is used The GSM module is

to end a call
AT+COPS=?
This command will

detect and display all
active GSM operators
in the gateway area
AT+COPS?
This command will

display the operator's
name to which the
GSM module has
registered
First Command:
- AT+CMGF=<n>
where <n> is 1 for
text format and 0 for

PDU format. The
value to be used is 1.
The module will
respond with "OK".
AT+CMGS="number"
This command is
used to complete the
destination phone
Sending a SMS number.
The module will
respond with ">".
- @send <text
message>
This command will
send the SMS
- the response for
confirmation is:
+CMGS: <message
reference> OK
- the response for
error is:
+CMS ERROR:
<error>
AT+SIM=
<n>,n=0,1,2,3
(Note: here the
values for
identifying the
SIM card are
from 0 to 3
(instead of 1 to
4))
This is an useful
method to check if
the GSM module is
working properly:
the command is used
to set a new active
SIM (this is not a AT
command: it is a
command interpreted
by the controller of
the GSM card)
These settings are
made directly with
the GSM module.
The confirmation
response is "OKSIMn"
where "n" is 0,1,2 or
3 if that SIM was
selected
To release a GSM module from the monitoring state the command "res moni"
must be typed.
There are also additional commands that are interpreted by the gateway
application. The command "help" must be sent to see the list of available
commands:
set pin sim sss pppp
used to set the pin codes for GSM modules at

module "sss". The pin code is "pppp";
set pin range sss sss pppp
used to set the pin codes for GSM modules in

range "sss" to "sss". The pin code is "pppp";
set/res moni ppp
used to put / extract a GSM port from

monitoring state
send gsm at.......
(used to dial a number)
set debug ppp ppp
used to start debugging on a port. The port

for debugging purposes is completed in "ppp"
section: for example to activate debug for
port 1 the command is "set debug 1 2"
set view ppp

command "start debug ppp ppp" in order to
activate the debugging facility
res debug ppp ppp
used to stop debugging on port "ppp". The

port is completed in "ppp" section: to stop
the debugging for port "1" the command is
"res debug 1 2"
res view ppp

command "res debug ppp ppp" in order to
deactivate the debugging facility
set tmax sss sss ttt
allows you to define a time interval ('ttt') after

which a SIM will be blocked. sss is the sim
coresponding value. You may specify a range
of SIM cards values. Value of 'sss' may be
computed as follows: number of card (shown
in "Port status) * 8 + number of sim (0,1,2 or
3) for the first GSM module or number of card
(shown in "Port status) * 8 + 4 + number of
sim (0,1,2 or 3) for the second GSM module.
set tsim sss ttt
allows setting the time counter (loading time):

'sss' is the sim coresponding value and 'ttt' is
the value in seconds.
set calls
it is used for displaying the total number of

call attempts ("TCalls"), answered calls ("T
spech"), total duration of calls ("Dcalls"), total
duration of speaking ("Dspech) and the
number of calls released from "A" side
("Arelease") and from "B" side ("Brelease")
set calls off
this command is used to reset the previous

values
set block ppp ppp
command used to send block message on

res block ppp ppp
command used to send unblock message on

set loop ppp ppp
command used to send loop message on SS7

signaling to channels in range ppp ppp
res loop ppp ppp
command used to send unloop message on

set tchange 1800/3600
speaking time period in seconds following

which the active SIM is changed
kill call port
this command disconnect an active call on a

GSM module. The position of the GSM module
is specified by the "port" parameter
test callbqack id
this command is used for making tests over

the quality of voice. In this chapter this
command is detailed presented
The following commands are used for settings concerning the second SIM
selection algorithm, called LOAD BALANCING. If you select the "equal load"
mode of work for the algorithm, each SIM on a GSM module will be used for a
certain period of speaking time, then the system will go to select the next SIM
card with the lowest load.
The commands are:
"set tchange 1800/3600" - speaking time period in seconds following which
the active SIM is changed (the gateway looks for the SIM card with the lowest
load for the same GSM module). Usual values are 1800 or 3600 seconds. This
parameter is the same for all GSM modules and can be viewed and changed in
any GSM settings window.
"set tsim sss ttt" - allows setting the time counter (loading time): 'sss' is the
sim coresponding value and 'ttt' is the value in seconds. Value of 'sss' may be
computed as follows: number of card (shown in "Port status) * 8 + number of
sim (0,1,2 or 3) for the first GSM module or number of card (shown in "Port
status) * 8 + 4 + number of sim (0,1,2 or 3) for the second GSM module.
Execute AT commands
In "Configuration manager" window the user is also able to execute AT
commands on all GSM modules.
The execution of these commands is based on a script file which is given as
command parameter. This file must be placed in the same folder with
"gwconfig" application. In this file the user can enter a batch of AT commands
to be executed over the GSM modules. The file must include the AT commands
you want to be to be executed over the GSM modules, the expected response,
the time delay to wait the appropriate response and the the option to save the
responses into a file.
The command to start this process is "execute -f xxxxx.txt" for all GSM
modules (where "xxxxx.txt" is the script file), or "execute -f xxxxx.txt -d GSM"
to start the process just for the modules belonging to the "GSM" direction. AT
commands are read from the "xxxxx.txt" file.
A window called "AT Commands Confirmation" is displayed for monitoring
the process.
In order to clarify this facility, here is shown a commented example of a script
file:
at+gsn
OK
10
1
at+cimi
OK
10
1
Each command is grouped as four lines:
1. AT command to be sent to GSM modules; (in the example above these
commands are "at+gsn" for IMEI code and "at+cimi" for IMSI code).
2. response wanted for the AT command; (in both cases the expected response
is OK; the expected value is included in responses before the "OK" text).
3. time to wait for the expected response; the next field is a value (0,1 or 2)
that has two meanings: the first significance (for a value of 0 or 1) is the time
delay to wait for the response at an AT command. If the response comes in the
specified interval then the process continues immediately. The second
significance, if the value read from the file is 2, is this: the application waits all
the specified delay and the last message received from the GSM module is
saved into a file.
4. an option about the saving of the response into a file; a 0 value means no
savings are done into a file, while a value 1 means responses will be saved in
"atresp.txt" file. If the value for the option is 2 then the last message received
during the waiting time will be saved in "atresp.txt". The option value of 2 can
be used to verify the credit for prepaid SIMs.
Notes:
- before sending any AT commands the application starts the monitoring
process (the same as selecting "Status monitoring"). This is done because the
application needs to know which cards are in alarm, which ports are in alarm
or in a call.
- this interrogation is performed just for the SIM cards currently registered.
Because AT commands can't pe sent to GSM modules which are in alarm, those
modules will be skipped in the process. For GSM modules where a conversation
is running, the commands are sent after the call is dropped. When the current
interrogation for a module has reached the last port, then the process will be
restarted for the skipped modules. The total number of restart cycles is 2.
- after a new interrogation process is started (after an "execute" command is
performed) the file "atresp.txt" will be deleted.
The first column representing the port
position. The second column displays
the current "Status" of executing AT
commands over that port. Possible
values are:
- WAITING - AT commands are not
yet sent to the port; (light blue colour
background)
- FINISHED - AT commands have been
succesfully sent to the port; (dark
blue background)
- CONNECTED the port was found in
a call at the time when it was
(red background). Call is dropped. AT
commands are sent.
- PORT ERROR- the port was found in
alarm at the time when it was
(red background). The port will be
- TIMEOUT- there was a timeout for
receiving responses for an AT
command; (red background). The port
will be interrogated in the next cycle
- CARD ERROR- the card to which the
port belongs was in alarm when the
application was tried to execute AT
commands for that port; (red
background). This port will NOT not be
- UNINSTALLED- the port is not
placed on any direction or the INST
category is not given; (grey
background). The uninstallled port will
NOT not be interrogated in the next
cycle.
- The third (rightmost) column shows
the number of interrogation cycles.
The maximum number of restart
cycles is 2.
Voice Quality Tests - In the same "Configuration manager" window the user
can to perform tests over the quality of voice on two GSM modules. In order to
make those tests, the user must first define the ports on which he wants to
make the tests.
This selection is done in the "Callback Table":
<identity (number) to test quality of voice> 1 <code 1> <code 2>
The first field of the line is an arbitrary number used to start the test of the
quality of voice. The second field must be "1" (callback functionality). The last
two fields are containing the prefix used in routing table, the GSM port
number and the number to call.
call -0744000001 )
call -0744000002 )
The Topex gateway will call the GSM module on first port, and following its
answer, it will connect the two, allowing you to check the quality of voice for
the respective connection.
For example:
9999 1 720320720000000 720330740000000 - the identity used for test is
"9999". The prefix used in routing table for the test service is "72". First GSM
port is 32 and the second is 33. First number to be called is "0720000000" and
the second one is "0740000000".
In routing table must exist a record to route "72" (the test prefix) to SERV
("Action" = SERV) and destination "11".
The command to start the voice test is performed from "Configuration
manager":
test callbqack 9999
When the last command is executed, the gateway calls the first number
0720000000 from port 32. When the calls is answered at destination, the
second part of the test is done. The phone number 0740000000 is dialed and
the two are connected.
This way you can connect two by two all of the GSM ports of the gateway and
test the quality of the voice on the respective connections.
Linux commands
Also you can type in the "Configuration manager" LINUX-like commands that
will be sent to the connected gateway. The syntax must always begin with
"system" characters. After a separation character (space character) a LINUX
command may follow. By pressing ">" character after a command the software
automatically adds the destination file for the command output. This
destination is by default "/mnt/app/out/out". After such a command the user
may analyse the output file by selecting the "Output File" icon command (" ")
from the toolbar.
5. Licence
This last option of Facilities menu is used to send a license message to the
Topex gateway.
The purpose of the "license" feature is to implement control over the timelimited application running on the gateway. This limited application will serve
incoming calls only for a specific number of days. After the expiration of this
period, the application will no longer process the calls. A license message is
sent by Topex company, message that is unique for each gateway (it can't be
used with another gateway).
Licenses can enable the control over some of the gateway's features. The
available features are:
- Basic
- SS7
- VoIP
- Callback
- Portability
- Tax - Pulses calculation
The license-enabling message consists of several lines. This message can be
received by the customer as an e-mail message. The user copies the message
into the "License" window and it send to the gateway.
The gateway should answer with the confirmation message: "LICENCE
ACCEPTED". If the license message is not valid, the answer will be "LICENCE
REJECTED". If the license is accepted then the number of working day is
displayed in the status bar.

1. Connecting steps
("tmaxsim.bin");

"sip_pbx.cfg".
occurs.
message appears.
Note:
gateways.
signal levels).

notice:
"Exit";

an EONES slave.
one or to go back
.
Types of boards:
Analogue
Subscriber board
multiACCESS/QUTEX
8 ports (FXS
card)
GSM/UMTS/CDMA
ports
PBX junctions
board 8 ports
(FXO card)
multiACCESS/QUTEX
E&M junctions
board 4 ports
multiACCESS/QUTEX
BL phones board
multiACCESS/QUTEX
8 ports
Radio board 4
ports
multiACCESS/QUTEX
NT/TE
ISDN-BRI board
with 4 ports
multiACCESS/QUTEX
E1R2 board (32

channels)
E1ISDN-PRI
board (32
channels)
E1SS7 board (32

channels)
E1R1 board (32

channels)
VOIP card - with

H323 or SIP
protocol (8,16,32
or 64 channels)
RG

distinct areas:

Port type
Hunting
Group
Pickup
Group
Target
SIM
Index
S
YES
(Subscriber)
YES
YES
YES
YES
YES
YES (for "BC"

settled)
NO
G (GSM)
YES
YES
NO
NO
NO
NO
NO
YES
P (JPABX)
YES
YES
NO
NO
NO
NO
YES
NO
E (E&M)
YES
YES
NO
NO
NO
NO
YES
NO
B (BL)
YES
YES
YES
YES
NO
NO
YES
NO


E1 trunks.

2.4.1. E1 card
LMA

RSA

BER Bit error rate

D


(32 positions)



2.4.2. VOIP card

64 channels.
channels.
2.5. CARD STATUS
33.

each 60 seconds.

unused.
card.
--mem 16 --gw-mac 00:48:54:1A:D2:8D -m 00:52:C2:40:3E:40

I


Name":
"viz".





gateway is " ".
configuration file.
"LAN=ppp0",
"WAN=eth0"
"USE_FIREWALL=yes"
Attention!
Debug
TOPEX gateway;
TOPEX gateway;
server;
information.
in the debug file:
the debug file:
timetest 0
CFG Trafic run 0
00257 7235150 Digits 1234567891108 Ident 120
00257 7235200 Route N 123456 ... NT 123456 ... RxT 9000
param 0
00258 7235200 Digits Ident 120

1,Brelease 0
1,Brelease 0
type of card.)
OID ("1.3.6.1.4.1.x")

shown:


8 characters.
corresponding list.
operation.
is 16 digits.
20 digits.
Digits
Purpose
Interpretation
bit 0 (mask 0x1000)
DIRCHECKCALLBACK
received identity
(caller identity)
bit 3 (mask 0x8000)

GSM ports placed on
will be treated as
CDMA modules
Interpretation
bit 0 (mask 0x0100)
DIRTESTNET (used in
case of a direction
which contains GSM
outgoing GSM module
registered
x (digit 1)
DIRGOODASR - when
bit 1 (mask 0x0200)
RELEASE message is
sent on ISDN with a
delay of 5 seconds
when a congestion
situation is
encountered on GSM
y (digit 2)
z (digit 3)
w (digit 4)
bit 2 (mask 0x0400)
DIRCATCALL - when
calls will be cut
modules for which a
reprogramming is
necessary (for
example when a SIM
must be changed
because of an used
algorithm)
bit 3 (mask 0x0800)
verify CLIR - when

each time after the
to a GSM module
Interpretation
bit 0 (mask 0x0001)

direction
bit 1 (mask 0x0002)

is sent on selected
direction
bit 2 (mask 0x0004)
- establish the
algorithm for
changing SIM on GSM
periods). When the
used (equal usage
time for each SIM)
bit 3 (mask 0x0008)

on the next link,
answers

Routing Table.
the higher is 9.

incoming calls.
Examples:
1000.
value is 34.
VoIP calls.


3.8. Routing table

licence window);
routing table.
'Dest' list
the 'Dest' list;
moment.
Digits
Bit (from
Interpretation
right to left)
x (digit 1)

0x8000)
gateway.
bit 1 (mask
2000)
on output link.
bit 0 (mask
0x1000)
on the gateway.
y (digit 2)
restricted.
allowed - 20.
z (digit 3)

w digit 4)

"Action"
incoming call;
hear anything;
"Prefix = 8"
"Action = SERV"
"Ignore =1"
"Signaling = 0000"
20".
DIR
GSM
00a4
110a
Method 1)
example below).
Method 2)

week.
Define Holidays

Method 3)
to 9.

be allowed.

nature of address.
option.
has occured
will be ignored.
Search Search
Significance
Mode Param
ASR
not
used

based on ASR value
ACD
not
used

based on ACD value
Priority
not
used

"dest" field).
value is passed
Down
not
used

group will have the
highest priority.
Up
not
used

group will have the
highest priority.
Circular
not
used

circulary.

on percentage. The
"Search Parameters"
Percent the
machine.


values are:
"unknown"
"op_french"
"op_english"
"op_german"
"op_russian"
"op_spain"
"op_rsrv1"
"op_rsrv2"
"op_rsrv3"
"notused"
"ord_subscr"
"prio_subscr"
"data_call"
"test_call"
"payphone"
"uk_oper_call"
"uk_admin_diverted"
3.9. LCR Table

l 00 1 00:00 24:00 0
l 00 1e 00:00 24:00 1
l 00 20 00:00 00:01 f
l 00 20 00:01 12:01 11
l 00 20 12:01 14:01 13
l 00 20 14:01 23:01 a
l 00 20 23:01 24:01 9
l 07 13 00:00 24:00 1
l 07 4 00:00 11:45 1
l 07 4 11:45 12:23 8
l 07 4 12:23 12:31 1
l 07 4 12:31 18:50 8




character.
s 00 1f 00:00 06:00 2
s 00 17 06:00 20:00 0
s 00 1f 20:00 21:30 3
s 00 1f 21:30 24:00 0
s 00 8 06:00 20:00 1
s 00 60 00:00 24:00 0
s 00 80 00:00 12:00 0
s 00 80 12:00 24:00 1
s 01 ff 00:00 06:00 0
s 01 ff 06:00 12:00 1
s 01 ff 12:00 18:00 2
s 01 ff 18:00 24:00 3
s 02 ff 00:00 24:00 1
s 03 ff 00:00 24:00 0
h 01 01
h 01 01
h 25 12
h 08 01


"Del" button.

"DISA"):
number;
"DISA".

appear:

point).
(own codes)" zone.
performed).
Examples:
with "8103".

appear:
range from 0 to 7).
6.
icon.
all CIC values.

appear:
destination.
card (PG).
Gateway MAC.

comfort noise.
default.
DTMF

field to the right
The syntax is :

current day.
Examples:

192.168.244.123


used.

9010.
Codecs g729b,g729
VAD disabled
Fast Start enabled
also 0.
3.17. Alerts
- by SMS
alerts:
must be checked.
used.
and so on.

target.
occur.
3.18. Test calls


port.
"0700000000 120 120 0"
before:
"12345 101 257 1",

calls):
seconds)
traffic_idle 10 5
added seconds)
traffic_sel 5 3
added seconds)
traffic_con 1 2
#traffic_call nr id

5 (5+0) and 8 (5+3).
(1+0) and 3 (1+2)
("id")

displayed.
connected system.


3.21. File Editor

Editor").
3.22. Loading hour

hour'.

seconds.

interrogation).
Notes:
level.


system check.

window.
4. Print options
5. NOTE

any system.

1. Connecting steps
("tmaxsim.bin");

"sip_pbx.cfg".
occurs.
message appears.
Note:
gateways.
signal levels).

notice:
"Exit";

an EONES slave.
one or to go back
.
Types of boards:
Analogue
Subscriber board
multiACCESS/QUTEX
8 ports (FXS
card)
GSM/UMTS/CDMA
ports
PBX junctions
board 8 ports
(FXO card)
multiACCESS/QUTEX
E&M junctions
board 4 ports
multiACCESS/QUTEX
BL phones board
multiACCESS/QUTEX
8 ports
Radio board 4
ports
multiACCESS/QUTEX
NT/TE
ISDN-BRI board
with 4 ports
multiACCESS/QUTEX
E1R2 board (32

channels)
E1ISDN-PRI
board (32
channels)
E1SS7 board (32

channels)
E1R1 board (32

channels)
VOIP card - with

H323 or SIP
protocol (8,16,32
or 64 channels)
RG

distinct areas:

Port type
Hunting
Group
Pickup
Group
Target
SIM
Index
S
YES
(Subscriber)
YES
YES
YES
YES
YES
YES (for "BC"

settled)
NO
G (GSM)
YES
YES
NO
NO
NO
NO
NO
YES
P (JPABX)
YES
YES
NO
NO
NO
NO
YES
NO
E (E&M)
YES
YES
NO
NO
NO
NO
YES
NO
B (BL)
YES
YES
YES
YES
NO
NO
YES
NO


E1 trunks.

2.4.1. E1 card
LMA

RSA

BER Bit error rate

D


(32 positions)



2.4.2. VOIP card

64 channels.
channels.
2.5. CARD STATUS
33.

each 60 seconds.

unused.
card.
--mem 16 --gw-mac 00:48:54:1A:D2:8D -m 00:52:C2:40:3E:40

I


Name":
"viz".





gateway is " ".
configuration file.
"LAN=ppp0",
"WAN=eth0"
"USE_FIREWALL=yes"
Attention!
Debug
TOPEX gateway;
TOPEX gateway;
server;
information.
in the debug file:
the debug file:
timetest 0
CFG Trafic run 0
00257 7235150 Digits 1234567891108 Ident 120
00257 7235200 Route N 123456 ... NT 123456 ... RxT 9000
param 0
00258 7235200 Digits Ident 120

1,Brelease 0
1,Brelease 0
type of card.)
OID ("1.3.6.1.4.1.x")

shown:


8 characters.
corresponding list.
operation.
is 16 digits.
20 digits.
Digits
Purpose
Interpretation
bit 0 (mask 0x1000)
DIRCHECKCALLBACK
received identity
(caller identity)
bit 3 (mask 0x8000)

GSM ports placed on
will be treated as
CDMA modules
Interpretation
bit 0 (mask 0x0100)
DIRTESTNET (used in
case of a direction
which contains GSM
outgoing GSM module
registered
x (digit 1)
DIRGOODASR - when
bit 1 (mask 0x0200)
RELEASE message is
sent on ISDN with a
delay of 5 seconds
when a congestion
situation is
encountered on GSM
y (digit 2)
z (digit 3)
w (digit 4)
bit 2 (mask 0x0400)
DIRCATCALL - when
calls will be cut
modules for which a
reprogramming is
necessary (for
example when a SIM
must be changed
because of an used
algorithm)
bit 3 (mask 0x0800)
verify CLIR - when

each time after the
to a GSM module
Interpretation
bit 0 (mask 0x0001)

direction
bit 1 (mask 0x0002)

is sent on selected
direction
bit 2 (mask 0x0004)
- establish the
algorithm for
changing SIM on GSM
periods). When the
used (equal usage
time for each SIM)
bit 3 (mask 0x0008)

on the next link,
answers

Routing Table.
the higher is 9.

incoming calls.
Examples:
1000.
value is 34.
VoIP calls.


3.8. Routing table

licence window);
routing table.
'Dest' list
the 'Dest' list;
moment.
Digits
Bit (from
Interpretation
right to left)
x (digit 1)

0x8000)
gateway.
bit 1 (mask
2000)
on output link.
bit 0 (mask
0x1000)
on the gateway.
y (digit 2)
restricted.
allowed - 20.
z (digit 3)

w digit 4)

"Action"
incoming call;
hear anything;
"Prefix = 8"
"Action = SERV"
"Ignore =1"
"Signaling = 0000"
20".
DIR
GSM
00a4
110a
Method 1)
example below).
Method 2)

week.
Define Holidays

Method 3)
to 9.

be allowed.

nature of address.
option.
has occured
will be ignored.
Search Search
Significance
Mode Param
ASR
not
used

based on ASR value
ACD
not
used

based on ACD value
Priority
not
used

"dest" field).
value is passed
Down
not
used

group will have the
highest priority.
Up
not
used

group will have the
highest priority.
Circular
not
used

circulary.

on percentage. The
"Search Parameters"
Percent the
machine.


values are:
"unknown"
"op_french"
"op_english"
"op_german"
"op_russian"
"op_spain"
"op_rsrv1"
"op_rsrv2"
"op_rsrv3"
"notused"
"ord_subscr"
"prio_subscr"
"data_call"
"test_call"
"payphone"
"uk_oper_call"
"uk_admin_diverted"
3.9. LCR Table

l 00 1 00:00 24:00 0
l 00 1e 00:00 24:00 1
l 00 20 00:00 00:01 f
l 00 20 00:01 12:01 11
l 00 20 12:01 14:01 13
l 00 20 14:01 23:01 a
l 00 20 23:01 24:01 9
l 07 13 00:00 24:00 1
l 07 4 00:00 11:45 1
l 07 4 11:45 12:23 8
l 07 4 12:23 12:31 1
l 07 4 12:31 18:50 8




character.
s 00 1f 00:00 06:00 2
s 00 17 06:00 20:00 0
s 00 1f 20:00 21:30 3
s 00 1f 21:30 24:00 0
s 00 8 06:00 20:00 1
s 00 60 00:00 24:00 0
s 00 80 00:00 12:00 0
s 00 80 12:00 24:00 1
s 01 ff 00:00 06:00 0
s 01 ff 06:00 12:00 1
s 01 ff 12:00 18:00 2
s 01 ff 18:00 24:00 3
s 02 ff 00:00 24:00 1
s 03 ff 00:00 24:00 0
h 01 01
h 01 01
h 25 12
h 08 01


"Del" button.

"DISA"):
number;
"DISA".

appear:

point).
(own codes)" zone.
performed).
Examples:
with "8103".

appear:
range from 0 to 7).
6.
icon.
all CIC values.

appear:
destination.
card (PG).
Gateway MAC.

comfort noise.
default.
DTMF

field to the right
The syntax is :

current day.
Examples:

192.168.244.123


used.

9010.
Codecs g729b,g729
VAD disabled
Fast Start enabled
also 0.
3.17. Alerts
- by SMS
alerts:
must be checked.
used.
and so on.

target.
occur.
3.18. Test calls


port.
"0700000000 120 120 0"
before:
"12345 101 257 1",

calls):
seconds)
traffic_idle 10 5
added seconds)
traffic_sel 5 3
added seconds)
traffic_con 1 2
#traffic_call nr id

5 (5+0) and 8 (5+3).
(1+0) and 3 (1+2)
("id")

displayed.
connected system.


3.21. File Editor

Editor").
3.22. Loading hour

hour'.

seconds.

interrogation).
Notes:
level.


system check.

window.
4. Print options
5. NOTE

any system.
TOPEX multiACCESS/QUTEX/EONES/multiswitch Operations, Administration, and Maintenance - Options

which can be selected to supervise the gateway
functionality
1. Status Monitoring
For viewing online state of the gateway equipment - in the connected state we can choose icon to start monitoring (" ") the system. If the monitoring
process is started then the icon will be displayed in a gray rectangle " ". To
stop the monitoring process, click again the icon " ". A command for state
viewing will be sent to system at regular intervals (5 seconds).The monitoring
process may be stopped by pressing once again the icon. You can see:
- for ports (port status):
------ which port is opened (used) - white color
------ which port is in alarm - red color (for GSM - there is no SIM active and
for subscriber - there is a line in fault). There are two situations for GSM
positions: first situation when no SIM number is shown (a line can be viewed)
and the second situation when the SIM number is displayed. For first situation
there are few possibilities: there is no SIM card physical installed on that GSM
port or PIN code is incorrect or the GSM module is in fault. For the second
situation the cause is that SIM module is not registered into a GSM network:
antennas are not connected or there is congestion in GSM network or SIM card
is inactivated in GSM network or there is a problem in radio frequency section.
------ invalid position -light blue (invalid position means "Installed" field not
set or card error). Card error will appear red in the card status area. Card
error will appear in the absence of an installed card (which is present in
configuration) or when the card is damaged and therefore
cannot be interrogated by the processor card.
------ available port - dark blue
- for trunk you can see alarmed channels and the situations of possible alarms
on trunk: LIS, LFA, LMA, AIS, RSA, RJA, BER
For E1-ISDN trunk the indication "SC" is used to display the status of the
signaling channel: when link is up the dark blue color is used; the red color is
used to indicate that the link is down (LAYER2 alarm); the white color is used
to indicate that a restoration of the link is performing.
- for card status there are shown: dark blue for installed board, light blue for
not installed card and red for alarm on that card
2. CELL, LEVEL and CHANNEL Info

This option is selected in connected state with a gateway from the toolbar by
pressing the icon "CELL, LEVEL and CHANNEL Info". For viewing cell, level
and channel info choose the icon (" "). If the cell, level and channel
monitoring process is started then the icon will be displayed in a gray
rectangle.
The window "CELL, LEVEL and CHANNEL Info" will present for a list of GSM
modules (modules that contain the "Installed" option in the "Category" field
and for which there is no alarm indication) the "Cell", "Level" and "Channel"
information. In the right side of the window is displayed a statistic for each cell
to which GSM modules are registered. For each cell the number of modules
connected "Count" and the average "Level" is presented. The window position
and size will be kept on a file on HDD for a future using.
3. Calls monitoring
For viewing online calls on the gateway equipment - you can choose icon to
start call monitoring (" "). If the call monitoring process is started then the
icon will be displayed in a gray rectangle. The call monitoring can be stopped
at any time by pressing one more time the same icon or the window closing
box. Following the validation of the icon, several types of monitoring windows
can be displayed:
a)- LIVE Monitoring (n), where n may be from 1 to 4
b)- LIVE Monitoring Report on DIRECTIONS

c)- LIVE Monitoring IP signaling
a) The first type of window, LIVE Monitoring (n), is used to see on line the
calls passing all the range of ports of the EONES gateway. The range is defined
from 0 to 1471, for all directions on incoming and outgoing sides. The user has
the posibility to open up to 4 (four) windows of that type. The tooltip displayed
for the live monitoring icon is Calls monitoring new window. When all the
four windows are opened the icon tooltip will show Calls monitoring no
window available.
Through those four windows you have the possibility to filter calls from
different directions on both incoming or outgoing ways.
The digit n shown between the round brackets ( and ) represents the index
of the window - it can be a value from one to four. In this example you see the
window (1):
Each call in progress is displayed with:

- the port source ("PortS")
- number made ("Number")
- identity of the call ("Identity")
- day and time.
- the field "Duration1" is filled with the time of selection.
- the field "Duration2" is filled with the conversation time.
- the status of a call can take the following values:"SETUP",
"PROCEED","ALERTING","CONNECTED" and "RELEASED" (the background color
is different for each type of status).

- the destination port ("PortD") - can take a value of "65535" until the
incoming call is routed through an destination port.
- "End" - finalization call mode - possible values are AOK, BOK, ARELS, BRELS,
AINEX, BINEX, ACONG, BCONG, ASERR, BSERR, ANERR, BNERR, ANANS,
BNANS, ABUSY, BBUSY, ATOUT and BTOUT. It indicates the mode of ending
the call:
- first character indicates who has released the call: A=caller party or B=called
party
- next characters are keywords detailing how the call was ended: OK ANSWER (response in the destination part), RELS - RELEASE (release in other
situation then ring-back tone or busy), INEX - INEX (non-existent from
equipment point of view - no defined route), CONG - CONG (congestion from
equipment point of view - no available resources), SERR - SERR (Signaling
error), NERR - NERR (Network error), NANS - NO ANSWER (release on ringback tone), BUSY - BUSY (release on busy situation) and TOUT - TIMEOUT
(timer expiration)
- "End2" - finalization call mode on ISDN calls - possible values are ' 31'
(normal call) for non ISDN calls or values from ISDN standard for release code
- IP:Port (sign) the IP signaling port filled in case of incoming voip calls
and viewing IN records or in case of outgoing calls and viewing OUT records
(IN, OUT settings are performed through the Filer option).
- IP:Port (RTP) the IP signaling RTP filled in case of incoming voip calls
Note1: the fields "Duration2", "End" and "End2" are filled only when the status
field takes the value "RELEASED".
Note2: Initially the LIVE MONITORING window displays the IN records (the
incoming side of each call; not the output side of the call. This is performed in
order not to have the same call into two records. Because for an incoming call
will have in case of routing succes another correspondent line in which the
source port is the destinaton port from the other record.)
The Filter option displays a window Live Monitoring Filter in which you can
select as you wish the range of ports to be monitorized through the live
monitoring process.
You can select a range of ports for which to display the "LIVE Monitoring". The
format to be used is "xx-yy" for a range of port or simple x for just a port.
The separation character is a comma ,.
The monitoring will be displayed for the selected ports (the cumulation for the
range of ports and ports). The default range which is used is from 0 to 1471.
Also you can select a direction for viewing incoming or outgoing calls
(Direction port source or port destination).
The name of log file is always "livex.txt" (where x is 1,2,3 or 4 depending of
the LIVE Monitoring window rank). The content of the file can be reset with
the option "Reset".
On the bottom of LIVE Monitoring window there is a statistic (which can be
restarted through the Clear button), which contains the live number of total
calls and connected calls, the ASR and ACD values and the time since the
supervision was started.
The Graph button is used to display a statistic on the last 60 minutes upon
the values of ASR and ACD.
In the upper part of the previous picture you can see a statistic on the ACD
(Average call duration). The color which is used for ACD is blue, and for the
average ACD is yellow.
On the bottom half of the last picture there is a statistic on the ASR. The color
which is used for ASR is green, and for the average ACD is yellow.
The calculated values for both ASR and ACD are highlighted in blue color.
Tooltips with the calculated values are displayed if the user put the mouse
over those points.
b) LIVE Monitoring Report on Directions

This live monitoring window show an online statistic on each direction (input
and output) and a total.
Only the directions for which at least a port is installed on the gateway will be
displayed. There is an indication on each direction about the number of
connected calls (displayed with blue color), number of attempted calls
(displayed with red color) and online ASR. By pressing on a column (IN or
OUT) for a direction a new window will be displayed ("Type of call end"
window).
Here you can obtain detalied information regarding the end of a call attempt.
The information is structured in three columns:
- first column "Side A" contains all calls released from caller party.
- second column "Side B" contains all calls released from called party.
- third column "Total" contains all calls.
For each zone, when you clikc over a column, the causes for calls releasing are
detailed as shown:
c) LIVE Monitoring IP Signaling

A single window which provide access to the calls which are passing through
our EONES equipment.
This happens when the EONES gateway is performing just the VoIP signaling
and when the RTP is made without using the resources of EONES VoIP
channels, or in case of incoming VoIP calls. The first type of calls are not using
the VoIP ports of EONES and therefore cannot be displayed in one normal
windows of the LIVE MONITORING feature. Thus you need the IP signaling
window to be able to monitor the calls that are bypassing the EONES
equipment:
Those records are temporary records. For the first type of windows the
records are preserved after disconnection until a new records is coming on the
same input or output port. In this second case the records are deleted after 20
seconds.
To close live monitoring windows you should close down all windows of the
first type.Then Live monitoring windows for directions and IP signaling will be
also closed, automatically.
field is takes the value "RELEASED".
Note2: You can select a range of ports for which to display the "LIVE
Monitoring".
The format to be used is "xx-yy". The calls monitoring will be displayed for the
ports in range from "xx" to "yy". Those two values must be separated by the
minus character "-".
The option "Set" must be used to validate the new port range. The default
range which is used is ports from 0 to 319.
Note3: You can select the option "IN" or "OUT". Those two options are about
the type of the call (from the point of view of the TOPEX EONES): incoming or
outgoing calls. The default option is IN, it is automatically selected at startup
of live monitoring.
Note4: You may also save all online messages regarding the progress of the
calls into a log file The name of this log file is always "live.txt". The content of
the file can be reset with the option "Reset".
TOPEX multiACCESS/QUTEX/EONES/multiswitch Operations, Administration, and Maintenance - Options

which can be selected to supervise the gateway
functionality
1. Status Monitoring
For viewing online state of the gateway equipment - in the connected state we can choose icon to start monitoring (" ") the system. If the monitoring
process is started then the icon will be displayed in a gray rectangle " ". To
stop the monitoring process, click again the icon " ". A command for state
viewing will be sent to system at regular intervals (5 seconds).The monitoring
process may be stopped by pressing once again the icon. You can see:
- for ports (port status):
------ which port is opened (used) - white color
------ which port is in alarm - red color (for GSM - there is no SIM active and
for subscriber - there is a line in fault). There are two situations for GSM
positions: first situation when no SIM number is shown (a line can be viewed)
and the second situation when the SIM number is displayed. For first situation
there are few possibilities: there is no SIM card physical installed on that GSM
port or PIN code is incorrect or the GSM module is in fault. For the second
situation the cause is that SIM module is not registered into a GSM network:
antennas are not connected or there is congestion in GSM network or SIM card
is inactivated in GSM network or there is a problem in radio frequency section.
------ invalid position -light blue (invalid position means "Installed" field not
set or card error). Card error will appear red in the card status area. Card
error will appear in the absence of an installed card (which is present in
configuration) or when the card is damaged and therefore
cannot be interrogated by the processor card.
------ available port - dark blue
- for trunk you can see alarmed channels and the situations of possible alarms
on trunk: LIS, LFA, LMA, AIS, RSA, RJA, BER
For E1-ISDN trunk the indication "SC" is used to display the status of the
signaling channel: when link is up the dark blue color is used; the red color is
used to indicate that the link is down (LAYER2 alarm); the white color is used
to indicate that a restoration of the link is performing.
- for card status there are shown: dark blue for installed board, light blue for
not installed card and red for alarm on that card
2. CELL, LEVEL and CHANNEL Info

This option is selected in connected state with a gateway from the toolbar by
pressing the icon "CELL, LEVEL and CHANNEL Info". For viewing cell, level
and channel info choose the icon (" "). If the cell, level and channel
monitoring process is started then the icon will be displayed in a gray
rectangle.
The window "CELL, LEVEL and CHANNEL Info" will present for a list of GSM
modules (modules that contain the "Installed" option in the "Category" field
and for which there is no alarm indication) the "Cell", "Level" and "Channel"
information. In the right side of the window is displayed a statistic for each cell
to which GSM modules are registered. For each cell the number of modules
connected "Count" and the average "Level" is presented. The window position
and size will be kept on a file on HDD for a future using.
3. Calls monitoring
For viewing online calls on the gateway equipment - you can choose icon to
start call monitoring (" "). If the call monitoring process is started then the
icon will be displayed in a gray rectangle. The call monitoring can be stopped
at any time by pressing one more time the same icon or the window closing
box. Following the validation of the icon, several types of monitoring windows
can be displayed:
a)- LIVE Monitoring (n), where n may be from 1 to 4
b)- LIVE Monitoring Report on DIRECTIONS

c)- LIVE Monitoring IP signaling
a) The first type of window, LIVE Monitoring (n), is used to see on line the
calls passing all the range of ports of the EONES gateway. The range is defined
from 0 to 1471, for all directions on incoming and outgoing sides. The user has
the posibility to open up to 4 (four) windows of that type. The tooltip displayed
for the live monitoring icon is Calls monitoring new window. When all the
four windows are opened the icon tooltip will show Calls monitoring no
window available.
Through those four windows you have the possibility to filter calls from
different directions on both incoming or outgoing ways.
The digit n shown between the round brackets ( and ) represents the index
of the window - it can be a value from one to four. In this example you see the
window (1):
Each call in progress is displayed with:

- the port source ("PortS")
- number made ("Number")
- identity of the call ("Identity")
- day and time.
- the field "Duration1" is filled with the time of selection.
- the field "Duration2" is filled with the conversation time.
- the status of a call can take the following values:"SETUP",
"PROCEED","ALERTING","CONNECTED" and "RELEASED" (the background color
is different for each type of status).

- the destination port ("PortD") - can take a value of "65535" until the
incoming call is routed through an destination port.
- "End" - finalization call mode - possible values are AOK, BOK, ARELS, BRELS,
AINEX, BINEX, ACONG, BCONG, ASERR, BSERR, ANERR, BNERR, ANANS,
BNANS, ABUSY, BBUSY, ATOUT and BTOUT. It indicates the mode of ending
the call:
- first character indicates who has released the call: A=caller party or B=called
party
- next characters are keywords detailing how the call was ended: OK ANSWER (response in the destination part), RELS - RELEASE (release in other
situation then ring-back tone or busy), INEX - INEX (non-existent from
equipment point of view - no defined route), CONG - CONG (congestion from
equipment point of view - no available resources), SERR - SERR (Signaling
error), NERR - NERR (Network error), NANS - NO ANSWER (release on ringback tone), BUSY - BUSY (release on busy situation) and TOUT - TIMEOUT
(timer expiration)
- "End2" - finalization call mode on ISDN calls - possible values are ' 31'
(normal call) for non ISDN calls or values from ISDN standard for release code
- IP:Port (sign) the IP signaling port filled in case of incoming voip calls
- IP:Port (RTP) the IP signaling RTP filled in case of incoming voip calls
field takes the value "RELEASED".
Note2: Initially the LIVE MONITORING window displays the IN records (the
incoming side of each call; not the output side of the call. This is performed in
order not to have the same call into two records. Because for an incoming call
will have in case of routing succes another correspondent line in which the
source port is the destinaton port from the other record.)
The Filter option displays a window Live Monitoring Filter in which you can
select as you wish the range of ports to be monitorized through the live
monitoring process.
You can select a range of ports for which to display the "LIVE Monitoring". The
format to be used is "xx-yy" for a range of port or simple x for just a port.
The separation character is a comma ,.
The monitoring will be displayed for the selected ports (the cumulation for the
range of ports and ports). The default range which is used is from 0 to 1471.
Also you can select a direction for viewing incoming or outgoing calls
(Direction port source or port destination).
The name of log file is always "livex.txt" (where x is 1,2,3 or 4 depending of
the LIVE Monitoring window rank). The content of the file can be reset with
the option "Reset".
On the bottom of LIVE Monitoring window there is a statistic (which can be
restarted through the Clear button), which contains the live number of total
calls and connected calls, the ASR and ACD values and the time since the
supervision was started.
The Graph button is used to display a statistic on the last 60 minutes upon
the values of ASR and ACD.
In the upper part of the previous picture you can see a statistic on the ACD
(Average call duration). The color which is used for ACD is blue, and for the
average ACD is yellow.
On the bottom half of the last picture there is a statistic on the ASR. The color
which is used for ASR is green, and for the average ACD is yellow.
The calculated values for both ASR and ACD are highlighted in blue color.
Tooltips with the calculated values are displayed if the user put the mouse
over those points.
b) LIVE Monitoring Report on Directions

This live monitoring window show an online statistic on each direction (input
and output) and a total.
Only the directions for which at least a port is installed on the gateway will be
displayed. There is an indication on each direction about the number of
connected calls (displayed with blue color), number of attempted calls
(displayed with red color) and online ASR. By pressing on a column (IN or
OUT) for a direction a new window will be displayed ("Type of call end"
window).
Here you can obtain detalied information regarding the end of a call attempt.
The information is structured in three columns:
- first column "Side A" contains all calls released from caller party.
- second column "Side B" contains all calls released from called party.
- third column "Total" contains all calls.
For each zone, when you clikc over a column, the causes for calls releasing are
detailed as shown:
c) LIVE Monitoring IP Signaling

A single window which provide access to the calls which are passing through
our EONES equipment.
This happens when the EONES gateway is performing just the VoIP signaling
and when the RTP is made without using the resources of EONES VoIP
channels, or in case of incoming VoIP calls. The first type of calls are not using
the VoIP ports of EONES and therefore cannot be displayed in one normal
windows of the LIVE MONITORING feature. Thus you need the IP signaling
window to be able to monitor the calls that are bypassing the EONES
equipment:
Those records are temporary records. For the first type of windows the
records are preserved after disconnection until a new records is coming on the
same input or output port. In this second case the records are deleted after 20
seconds.
To close live monitoring windows you should close down all windows of the
first type.Then Live monitoring windows for directions and IP signaling will be
also closed, automatically.
field is takes the value "RELEASED".
Note2: You can select a range of ports for which to display the "LIVE
Monitoring".
The format to be used is "xx-yy". The calls monitoring will be displayed for the
ports in range from "xx" to "yy". Those two values must be separated by the
minus character "-".
The option "Set" must be used to validate the new port range. The default
range which is used is ports from 0 to 319.
Note3: You can select the option "IN" or "OUT". Those two options are about
the type of the call (from the point of view of the TOPEX EONES): incoming or
outgoing calls. The default option is IN, it is automatically selected at startup
of live monitoring.
Note4: You may also save all online messages regarding the progress of the
calls into a log file The name of this log file is always "live.txt". The content of
the file can be reset with the option "Reset".

Administration, and Maintenance - Modify parameters
- If you select "Parameters" the following window pops up:
Is permitted to modify System name, IP address and IP port number, serial

port (in range COM1-COM12) and the link type "Serial communication/IP
communication". Also the "DialUp" parameters can be changed: "Use PPP
address", "DialUp connection name", "DialUp Number", user name and
password used for authentication and "Connection Timeout".
There is a text limit of 19 characters for the "Name" field and 2 characters for
the "Serial Port num".
colored in red.
Also, value check is performed for the "Name" field. If this values is not filled
or is the same as an already existent "Name" (used for another system), an
error message will be displayed and the incorrect field will be colored in red, as
shown in the following image:
Is permitted to activate automatic requests for reading ASR and alarms.

Note: in case of reduncancy when two processor card are used the "Modifing
system parameters" window will be different:

Administration, and Maintenance - ALARMS
The alarm files are named <current date>.alr and they include the following
fields:
Field
Interpretation
Current date
dd-mm-yy
Current time
xx:xx:xx
SET - blocked (appearance of alarm)
Alarm status
RES - unblocked (disappearance of an alarm)
PROCUP - the processor is started. This is an event, it

works only with SET, not set/reset
PROCDN - the processor is stopped. This is an event, it
works only with SET, not set/reset.
ALIM val - Supply indicator
JONBLOCK - junction alarm
APFALS - local subscriber alarm
CARDERR - board alarm
LIS - Loss of Incoming Signal (is an alarm that indicates that
there is no signal on the E1 trunk input)
LFA - Loss of Frame Alignment (is an alarm that indicates
that the frame alignment is not detected)
LMA - Loss of Multiframe Alignment (is an alarm that
indicates that the multiframe alignment is not detected)
AIS - Alarm Indication Signal (the alarm is send by a
transmission equipment to indicate the lost of the input
signal on the E1 trunk )
Type of alarm
RSA - Remote Signaling Alarm (is an alarm which is

transmitted by the gateway when one of the following
alarms is detected: LIS, LFA or AIS)
RJA - Remote Junction Alarm (is an alarm which is
transmitted by the gateway when LMA alarm is detected)
CCS - Common Channel Signaling Alarm. Warns about the
data link for the ISDN E1 trunk.
SLIP - This alarm event is caused by non-synchronous
operation of the two equipment (TOPEX system and PBX or
VoIP gateway).
BER val - Bit Error Rate; val is a number from zero to three
that shows the error rate as follows: 0 = 10-6, 1 = 10-5, 2
= 10-4, 3 = 10-3.
ASR - alarm of ASR - value calculated on gateway - alarm

which is generated if the ASR is below a threshold. The ASR
value is calculated if "Validate ASR reading" is enabled in
"Alerts" window. The ASR value is recomputed at each "ASR
read period" seconds.
The ASR alert is generated if the ASR value is below "ASR
alert limit" and if "Alert activated" checkbox is enabled (see
"Alert Zone" - "Parameters"); also the "ASR" checkbox must
be enabled in "ALARMS for alerting" area.
Port
Number of the alarmed port
Card
Number of the alarmed card
All these fields are separated in file by "," character (comma character).
By choosing "Alarms" - tree command for a system, all alarm files from the
folder "Alarms" of the system directory we'll be shown.
It is possible to select the alarm file you want. Double click with the left mouse
button, then a dialog box for making an alarm filter we'll be seen. The alarm
filter indicates how to check options and values for searching inside the
"Alarms" directory.
The field "Period" indicates by default the time period corresponding to the
name of the alarm file that was selected. This period can be changed in order
to extend the time interval that is analyzed. The software will look for records
in the alarm files name whose name falls inside the selected time period.
There is an option to view only certain types of alarms and to specify the card
and the port number for them.
You can select only alarms appearances / disappearances or both.
The maximum size of the fields is 8 for the periods and 3 for the fields that are
specifying a card or a position number.
The correctness of the period definition is checked before the filter validation.
By pressing "OK" button all alarms corresponding to the filtering criteria will
be displayed in the "Local Viewer" window.
Each record contains the moment of the appearance (with "SET") or the
disappearance (with "RES") of the alarm and a description (text) of the alarm.
Regarding the error type the next two fields are important (sense): position
and card.

Administration, and Maintenance - BILLING FILES (CDR)
The billing files are named <current date>.tax and include the information
required for detailed billing (taxation) of the calls.
During the development period, the information which is saved in the
billing file was increased by adding columns. In the following
explanations is described the basic billing file structure; at the end of
this short description, the table which contains the billing fields will
present also the new added columns.
The following example - for a multiACCESS - GSM equipment (with an
answered call) contains a test call from port "120" with the phone number
dialed "81712345678". The identity of the call is "120".
TLI,00120,120 ,81712345678 ,10-0304,14:30:43,000004,00001,00,00008,BOK , 16,222222222222222,
10,abcd,GSM
Note 1): an incoming call can be made either from a subscriber or from an
incoming direction (containing E1 trunks or GSM modules);
Note 2): the number and the identity can be subject to modifications by the
multiACCESS/QUTEX gateway. Changes are caused by applying the rules
about the ignore and insert operations and the maximum expected digits from
the "Define Calls directions". Also, if a route exist for the dialed number,
changes can be made by the ignore and insert operations from "Routing table".
But in the billing files the phone number and the identity will always be the
original ones;
Note 3): the total number of digits that can be treated correctly by "gwconfig"
software is 20, both for identity field and for the number field;
Note 4): the number, the identity and the IMSI values used here are for
example purposes only;
The next example (with an answered call) contains a test call made from E1SS7 or VoIP ports on an EONES equipment.
Example1: the fist example with an answered call contains a test call received
on port 32 (E1 port). The received number was 5235. The output port was a
VoIP port (258) located on SS71 direction. The call was released from the
called party side (see BOK). The duration of the call was two seconds, and
selection duration was 11 seconds.
The IP fields are filled with space and the port fields with 00000, because the
incoming port was not a VoIP port.

TLI,00032,100 ,5235 ,10-03-06,11:11:03,000002,00001,00,00258,BOK , 16,
, 11,0000, MYVOIP , ,00000, ,00000, ,00000, ,00000
Example2: another example, also with an answered call, in which the call is
coming from VoIP port 258 with number 5235 and identity 258. The call
was coming from 192.168.1.152 signaling port 37380 and RTP port
49172. The destination IP was 192.168.104.20 (EONES processor address
in this case) with signaling port 5060 and VoIP IP address 192.168.104.21
(voip ip address of the EONES) with RTP port 10516. The output port was 259
located on MYVOIP direction.
TJI,00258,258 ,5235 ,10-03-06,11:21:29,000003,00001,00,00259,BOK , 16,
, 2,0000, MYVOIP ,192.168.1.152 ,37380,192.168.1.152
,49172,192.168.104.20,05060,192.168.104.21 ,10516
Note 1: an incoming call can be made from a an incoming direction (containing
either E1 trunks or VoIP channels);
Note 2: the IP fields together with signaling and RTP ports are written into
billing files when Add IP fields is established in Gateway Parameters.
Billing records can be aslo send to an external MYSQL database for storage and
further processing.
Note 3: the number and the identity can be subject to modifications by the
EONES. The changes are caused by applying the rules about the ignore and
insert operations and the maximum expected digits from the "Define Calls
directions". Also, in addition, if a route exist for the dialed number, then
changes can be made by the Ignore and Insert operations from "Routing
table". But in the billing files the phone number and the identity will always be
the original (initial) ones;
Note 4: the total number of digits that can be processed by the "gwconfig"
software is twenty (20), both for the field identity and for the field number;
A billing file has the following fields:
Field
Description
Call type
TJI or TLI (the call source is a junction respectively a subscriber)
xxxxx - physical position of the source port (5 digits). This value

Source Port
This value can be 65535 in case of a multiswitch.

Source
identity
subscriber number or caller identity (20 digits)
CallDigits
(Call
Number)
call number (20 digits)
Day and
Time
Day and Time of the call in the following shape dd-mm-yy,hh:mm
Connected
Duration
xxxxxx - speaking duration of the call in seconds (6 digits)

xxxxx - billing Units for the call (5 digits)
Billing Units
for the call
This field is usually filled with 0 for non-answered calls and with 1
However if tax pulses calculation is set on incoming direction (see
Direction") then this value will be filled according with the numbe
bases (see "Tax" field in "Routing Table").
Destination
When the destination port is a GSM port (multiACCESS or QUTEX
SIM Number
Destination
Port
- physical position of the destination port (5 digits) (when the ca

in this field (5 digits)
In case of a TOPEX multiswitch - calls terminated with success wil
Possible values are AOK, BOK, ARELS, BRELS, AINEX, BINEX, ACO
ANANS, BNANS, ABUSY, BBUSY,
ATOUT,BTOUT,AERRAUTH,ANOCRED,AFINCRED,AVMAIL,BVMAIL,N
It indicates the mode of ending the call:

- first character indicates who has released the call: A=caller part
- next characters are keywords detailing how the call was ended:
OK - ANSWER (response in the destination part)
RELS - RELEASE (release in other situation then ring-back tone or
INEX - INEX (non-existent from equipment point of view - no defin
CONG - CONG (congestion from equipment point of view - no ava
Finalization
call mode

AERRAUTH - when the ANI or prepaid user is not authenticated on
ANOCRED - when the ANI or prepaid user has no credit available
AFINCRED - for ANI or prepaid user when the credit expires durin
AVMAIL BVMAIL - when a call is finished on vocal message box - cause of
NOVOIPCH - when no VoIP channel is available
CODECERR - when the source codec is not in the list of supported
NOLICENCE - indicates two situations: 1) that the LICENCE had ex
for the requested protocol - for example VoIP or SS7. The LICENC
ACLREJECT - indicates for an incoming VoIP call that the IP is not
different then the expected value or the number of incoming calls
are set in
DIRIPIN section.
Finalization
Possible values are either ' 31' (normal call) for non ISDN calls or
call mode on
release codes
ISDN calls
IMSI
International Mobile Subscriber Identity (multiACCESS or QUTEX
Selection
Duration
xxx- three digits - total time (in seconds), cumulated value of both
CELL
For a call routed through a GSM port (multiACCESS or QUTEX) it

where the SIM was registered.
The direction to which the destination port is belonging (it is the o

Direction
In case of TOPEX software versions released after 2006 - this field

This direction can be a direction to which ports are belonging (for
a direction used for incoming VoIP calls - which is the generic "MY
ports) used just to allow inserting/ignoring digits from number or
The IP source and destination address and the RTP source and des
This info includes the Signaling IP and Signaling Port for the sourc
followed by Signaling IP and Signaling Port for the destination, an
IP address
destination.
and RTP port
For the VoIP incoming calls, the destination signaling IP is the one
destination RTP is the IP of the VoIP card. In case of VoIP outgoing
VoIP card of the Topex (multiACCESS/QUTEX/EONES) equipment,
Session_id
remote VoIP card that made the call.

This is an unique identifier of a call inside the equipment software
equipment log files.
Jitter
Jitter is a variation in packet transit delay caused by queuing, con

through the network.
Packet Loss
VoIP packet loss occurs when a large amount of traffic on the netw
dropped conversations, a delay in receiving the voice communicat
Client_id
Direction output
direction
This direction is the output direction and can be a direction to whi

FXO,FXS,GSM or E1 - ISDN/SS7) or a direction used for outgoing
"MYVOIP" direction or a virtual direction (without ports) used just
destination IP (see DIRIPOUT section).
Proto in
protocol used on incoming side - H323/SIP (VoIP), CAS (FXS,FXO,
Proto out
protocol used on outgoing side - H323/SIP (VoIP), CAS (FXS,FXO,
the value of codec:

G729 - 18
Payload Type G723 - 4
G711, G711a - 8
G711u - 0
The Packetization Time is the length of the digital voice segment t

Packetization
millisecond packets. Selecting 10 millisecond packets enhances th
Time
to packet loss, but doubles the load on the network traffic.
If you select "Billing" - tree command for a system, then all billing files from
the folder "Billing" of the selected system directory will be seen.
You go to the billing file you want to see, and by double clicking the left mouse
display of the billing information. This filter for billing (taxation) files permits
the setting of options and values for searching records inside the subdirectory
for billing.
the name of the billing that you have selected. You may change this default
period to extend the time interval that is analyzed. For each of the "From"
and "Until" limits, subfields are "Day" and "Hour". The program will look for
records in the billing files whose name falls inside the selected time period.
From the source point of view you may specify these options:
- a direction - a name of a direction defined in "Directions Names"
- the source port type: local or junction (trunk)
From the call destination (called part) point of view you may specify these
options:
the number of destination digits less, equal or greater than the value typed.
- a direction- a name of a direction defined in "Directions Names"
port)
The section "IP and Port Filter" contains several options to select from the
incoming call side:
- signaling IP
- signaling port
- RTP IP
- RTP port
From the ougoing call side:
- signaling IP
- signaling port
- RTP IP
- RTP port
billing records have a caller and a called party. For an incoming call on E1
represented by 'A' and called party by 'B' (field "Release Side"). Depending
by the side which ends the call a letter ( 'A' or 'B') will be shown and the
finalization mode will contain one of the following strings: OK - ANSWER, RELS
- RELEASE, INEX - INEX, CONG - CONG, SERR - SERR, NERR - NERR, NANS NO ANSWER, BUSY - BUSY, TOUT - TIMEOUT. "Call Type" lets you to specify
the mode of ending of the call.
E1 trunk.
You may set a value for "ISDN EndType" which represents call release code
for ISDN calls. Other types of calls will display a value of ' 31' in the billing
records.
You may also set the option to select the records with the conversation
duration and the selection duration (in seconds) less, equal or greater than
the value typed.
specifying IMSI code and 20 for specifying destination digits.
Certain values from the billing filter are checked before validation (by pressing
the button "OK"). The program checks correctness of the following:
- period definition (day and hour - day less or equal to 31, month less or equal
to 12, year less or equal to 36, hour less or equal to 23, minute less or equal
to 59 and second less or equal to 59);
- port position of the call source (in range 0 to 319);
- sim index (in range 1 to 4 or 255);
- destination port position (65535 or a value in the range from 0 to 319);
- duration and selection duration (a value greater or equal to zero);
- number of digits (a value greater or equal to zero);
- ISDN EndType (a value greater or equal to zero);
If something is wrong, an error message will be shown to the user and the
field that has caused the error will be colored in red (while the text color
becomes white). When the user goes back to the incorrect field in order to
correct the wrong data, then the red color will disappear. In the following
example an error message "Wrong port value" is displayed because of an error
field on port position (a value "342" which is greater than the maximum
number of 319).
(option "Display only the total without the records") that corresponds to
the records in a certain time interval for the purpose of post-processing of the
stored billing information (post-processing is done for cost analysis). For these
applications, you need a text file with values only (that may be imported into a
spreadsheet like Excel) but without totals interspread in it.
in the "Billing Report". These columns will be explained later in this chapter.
The information regarding the billing columns to be displayed is stored in the
file "tax_rep.dat" on the harddisk in the same directory from where "gwconfig"
software is running. In this file it is also saved the information about the size
of the columns presented in the billing report.
By pressing "OK" button all Billing records corresponding to the filter criteria
will be seen.
(field "Attempts"), total number of connected calls (field "Connected"),
ASR (field "ASR"), total duration of calls (conversation part-field
"Duration"), associated billing units (field "TaxUnits"), and at the end a total
for all of the intervals - total number of attempts, total number of connected
calls, ASR, total duration and billing units.
subdirectory for the chosen system in a file with the "tot" extension and the
the total of calls for several days and also a general total.
Note2: Once you have defined a filter for the billing files, some of its settings
will be saved, so you can apply the same filter to several billing files. The
settings established in the billing filter are saved in the file "tax_fl.dat" on the
harddisk in the directory where "gwconfig" software is running. These settings
are:"Port Type" (section "Call Source") - subscriber part and junction part,
"Release Side" ("A Side" or "B Side"), "Call Type" ("ANSWER", "RELEASE",
"INEX", "CONG", "SERR", "NERR", "NO ANSWER", "BUSY" and "TIMEOUT") and
the options regarding the viewing of totals and billing records ("Display only the
total without the records" and "Display only the records without a total"). These
settings are loaded before the showing of the billing filter in order to be preestablished.
An example of sorting the column "Ident" is provided for both ascending and
descending sort.
amount of time.

Administration, and Maintenance - ACTIVITY
The monitoring (activity) files are very detailed activity files, that record
everything about the calls. They are generated to detail the mode of call setup
and follow up the calls from and towards the ports that have checked the field
"Monitoring".
Activity files are named <current date>.mon and they include for each
routed call four activity recordings. For a call not routed the file contains only
two recordings representing just the calling part.
The first following example (with an answered call) contains a test call from
port "120" with the number dialed "81712345678". The identity of the call is
"120". Port "120" is allocated to the direction called "LOCAL". First line which
is starting with "TLI,00120" contains the original number and the original
maximum expecting digits) which are defined in the section "Define Calls
directions" are first applied to the number and to the identity. The line
preceded by "IN,00120" contains the modified number and the modified
identity according to the settings belonging to the "LOCAL" direction from
"Define Calls directions" table. The rules were "Ignore = 2" (ignore two digits)
and "Insert = '0'" (insert the digit '0') for the number, so the number was
changed from "81712345678" to "0712345678". The rules were "Ignore_id =
1" (ignore one digit) and "Insert_id = '33'" (insert the digits '33') for the
identity so the identity was changed from "120" to "3320". After the rules
established in "Define Calls directions" table are applied for the incoming part,
the call is routed by applying the "Route table" definition. In this table a record
with "Prefix = 0" is defined. In this case the fields "Ignore","Ignore_id","Insert"
and "Insert_id" are not specified.The third and fourth line represent the
outgoing part of the call routed through a GSM port "00008". Caller id sent
through this port is "3320" and number is "0712345678".
Note 1): an incoming call can be made from a subscriber or from a incoming
direction (containing E1 trunks or GSM modules);
Note 2): the fields that are specifying the modified number and the modified
identity are the same in the second and in the third line ("0712345678" for
the number and "3320" for the identity). Identity will appear modified or not
by fields "Ignore_id" and "Insert_id" from the "Define Calls direction" window
and by fields "Ignore_id" and "Insert_id" from the "Routing table" window.
Number will appear modified or not by fields "Ignore" and "Insert" from the
"Define Calls direction" window and by fields "Ignore" and "Insert" from the
Note 3): the fourth line does not contain any information about the number
and the identity;
Note 4): the number and the identity can be also affected by the field
"Max_d", and respectively by "Max_id" from the "Define Calls direction"
window;
Note 5): the total number of digits that are well treated by "gwconfig" software
is 20 for identity field and number field;
Note 6): in the billing files the number and the identity will not appear
changed.
Note 7): the number, the identity and the IMSI values used above are for
testing purposes only;
TLI,00120,120 ,81712345678 ,10-0304,14:30:43,000004,00001,00,00008,BOK ,16,222222222222222,
17,abcd,GSM
TJO,00008,3320 ,0712345678 ,10-0304,14:30:43,000004,00001,ff,00120,BOK , 16, , 17,0000,
OUT,00008, , ,TD008,TSEL009,MOD01,0001,00
The second example (also with an answered call) contains a test call from port
"120" with the number dialed "81712345678". The identity of the call is "120".
Port "120" is allocated to the direction called "LOCAL". First line which is
starting with "TLI,00120" contains the original number and the original
maximum expecting digits) defined in the section "Define Calls directions" are
first applied to the number and to the identity. The line preceded by
"IN,00120" contains the modified number and the modified identity according
to the settings belonging to the "LOCAL" direction from "Define Calls directions"
table. The rules were "Ignore = 2" (ignore two digits) and "Insert = '51'"
(insert the digits '51') for the number, so the number was changed from
"81712345678" to "51712345678". The rules were "Ignore_id = 1" (ignore
one digit) and "Insert_id = '33'" (insert the digits '33') for the identity so the
identity was changed from "120" to "3320". After the rules established in
"Define Calls directions" table are applied for the incoming call, the call is
routed by applying the "Route table" definition. In this table a record with
"Prefix = 5" is defined. In this case the fields "Ignore=2" (ignore two digits)
and "Insert='0'" (insert the digit '0') (the fields "Ignore_id" and "Insert_id" are
not specified).The number "51712345678" will become "0712345678". The
third and fourth line represent the outgoing part of the call routed through a
GSM port "00008". Caller id sent through this port is "3320" and number is
"0712345678".
TLI,00120,120 ,81712345678 ,10-0304,15:08:44,000004,00001,00,00008,AOK ,16,222222222222222,

19,abcd,GSM
TJO,00008,3320 ,0712345678 ,10-0304,15:08:44,000005,00001,ff,00120,AOK , 16, ,19,0000
OUT,00008, , ,TD007,TSEL012,MOD01,0000,00
Note that there are two kind of records: first record like in lines 1 and 3 from
the previous example and the second record like in lines 2 and 4 (containing
"IN" and "OUT").
The first recording includes the fields:
RECORD
1
Field
Significance
Unfinished Incoming call: - MJI or MLI
incoming call- TJI or TLI (the call source
Call Type
Unfinished Outgoing call: - MJO or MLO
outgoing call- TJO or TLO (the call source
Source Port
xxxxx - physical position of the source port

(5 digits);
Source
identity
subscriber number or source identity (20

digits). For outgoing records identity
("Ident") will appear modified or not by
fields "Ignore_id" and "Insert_id" from
by fields "Ignore_id" and "Insert_id"
from the "Routing table" window;
call number (20 digits).For outgoing
records this field will appear modified or
CallDigits
(Call
Number)
not by fields "Ignore" and "Insert" from

by fields "Ignore" and "Insert" from the
Day and
Time

format dd-mm-yy,hh:mm:ss ;
Connected xxxxxx - duration of the conversation in

Duration
seconds (6 digits);
Billing Units
xxxxx - billing Units for the call (5 digits);
for the call
Destination When the destination port is a GSM port
SIM
(multiACCESS or QUTEX) it specifies a
Number
value for SIM card (1,2,3,4 or ff);
Port
digits);
BRELS, AINEX, BINEX, ACONG, BCONG,
Finalization
ASERR, BSERR, ANERR, BNERR, ANANS,
call mode
BNANS, ABUSY, BBUSY, ATOUT and
BTOUT;
Finalization
Possible values are ' 31' (normal call) for
call mode
non ISDN calls or values corresponding to
on ISDN
ISDN standard for call release codes;
calls
IMSI
International Mobile Subscriber Identity (is

filled for incoming records routed through a
GSM port (multiACCESS or QUTEX))
Selection
Duration
xxx- three digits - cumulated selection

time in seconds. It cumulates both "Dial
time" (time in seconds for dialing the
number) and "Selection time" (time in
seconds while the response is waited for).
CELL
The GSM CELL (four digits - alphanumeric

code) where the SIM used for the call is
registered ("Destination SIM Number" on
the "Destination Port") (multiACCESS or
QUTEX). The cell info is useful to search
which cells from the network have

generated better ASR values.
Direction
The direction to which the destination port

is belonging (it is the output direction)
The second record contains:

RECORD
2
Field
Significance
IN (incoming call)
Call type
OUT (outgoing call)
Source Port
xxxxx - physical position of the source port (5 digits). This is the

destination port from the preceding record;
Source
Identity
Represents the source identity. For incoming records (preceded

by "IN") the identity may be modified by fields "Ignore_id" and
"Insert_id" established in direction definition and by fields
"Ignore_id" and "Insert_id" from "Routing table" window; for
records preceded by "OUT" this field is empty;
CallDigits
(Call
Number)
Number dialed (20 digits). For incoming records (preceded by

"IN") the number may be modified by fields "Ignore" and
"Insert" established in direction definition window and by fields
"Ignore" and"Insert" from "Routing table" window; for records
preceded by "OUT" this field is empty;
Dial time
TDxxx-time in seconds for dial;
Selection
time
TSELxxx-time in seconds when the response is waiting;
Call Type
MODxx -specified call type (0-incoming call, 1-outgoing call). This

field is used for further developments;
Finalization
mode
Possible value are 0000-AOK, 0001-BOK, 0002-ARELS, 0003BRELS, 0004-AINEX, 0005-BINEX, 0006-ACONG, 0007-BCONG,
0008-ASERR, 0009-BSERR, 000a-ANERR, 000b-BNERR, 000cANANS, 000d-BNANS, 000e-ABUSY, 000f-BBUSY, 0010-ATOUT,
0011-BTOUT(4 digits);
SIM
information
For calls routed to destination through a GSM module it

represents the active SIM card. Possible values are 1,2,3,4 or ff
(xx- 2 digits);
NOTE: The activity records are processed before viewing into a more simple
format by grouping two records (record 1 and 2) into a single one (chapter
"ACTIVITY").
By choosing "Activity" - tree command for a system, all activity (monitoring)
files from the subdirectory "Activity" of the selected system directory we'll be
displayed.
By double clicking with left mouse button on a file, a dialog window for activity
filter will be displayed. This filter allows setting several options for searching
the data from the "Activity" filter.
The "Period" area indicates (by default) the period which corresponds to the
selected Activity file name. This period can be changed in order to increase the
time interval to be analyzed. This software searches for "Activity" files having
assigned a name corresponding to this period. A time period can be also set (in
"Hour" area).
To specify filtering from the point of view of the source of calls you have the
following options:
- a direction (all source port on that direction will be searched)
- the source port type: local subscriber or junction
The following options for the call destination (called part) are available:
the number of destination digits less, greater or equal that the value typed.
- a direction (all destination port on that direction will be searched)
- the value of the SIM card (1,2,3,4 or 255)(when the destination port is a
GSM port)
activity records have a caller and a called party. For an incoming call on E1
represented by 'A' and called party by 'B'. Depending by the side which ends
the call a letter ( 'A' or 'B') will be shown and the finalization mode will contain
one of the following strings:
OK - ANSWER (call answered, response in the destination part)
RELS - RELEASE (release in other situation then ring-back tone or busy)
INEX - INEX (non-existent from equipment point of view - no defined route)
CONG - CONG (congestion from equipment point of view - no available
resources)
E1 trunk.
You can set a value for "ISDN EndType" which represent call release code for
ISDN calls. For other calls in billing records a value of ' 31' will be displayed.
You may set also the option to select the records with the conversation
duration (in seconds) less, greater or equal than the value typed.
You may set also the option to select the records with the selection duration
(in seconds) less, greater or equal than the value typed.
specifying IMSI code 16 and 20 for specifying destination digits.
Certain values from the monitoring filter are checked before the validation (by
pressing the button "OK"). The correctness of the period definition ( - (day and
second less or equal then 59)), port position of the call source (in range 0 to
319), sim index (in range 1 to 4 or 255), destination port position (65535 or a
value in the range from 0 to 319), duration and selection duration (a value
back the focus to the error field in order to correct the wrong data, then the
red color will disappear. In the following example an error message "Wrong
port value" is displayed because of an error field on port position (a value
"342" which is greater than the maximum number of 319).

in the "Activity Report". Those columns will be presented later in this chapter.
The information regarding the activity columns to be displayed is stored in the
file "mon_rep.dat" on the harddisk in the same directory from where
"gwconfig" software is running. In this file it is saved also the information
regarding the size of the columns presented in the activity report.
By pressing "OK" button (in the "Activity Filter" window) all activity records
complying with the filter criteria will be shown.
All these records will be saved in "Viewer" folder for the chosen system in a
file named "moni.tmp".
An activity record will contain (when all fields are selected to be presented in
the "Activity Record Definition" window) the following fields:
Field
Significance
Unfinished Incoming call: - MJI or MLI (the call source is a junction respectively a subscriber)
or Finished incoming call- TJI or TLI (the call source is a junction respectively a subscriber)
Type (Call type)
Unfinished Outgoing call: - MJO or MLO (the call source is a junction respectively a
subscriber) or Finished outgoing call- TJO or TLO (the call source is a junction respectively a
subscriber)
PortS (Source
Port)
xxxxx - physical position of the source port (5 digits);
Ident (Source
Identity)
subscriber number or caller identity (20 digits) (this field may be modified for outgoing
records by "Ignore_id" and "Insert_id" fields from "Define calls direction" and by fields
"Ignore_id" and "Insert_id" from "Routing table" window);
Ident Changed
(Source Identity
This field is filled only for incoming records and contains the changed source identity which
can be modified by "Ignore_id" and 'Insert_id" fields from directions definition window
and by fields "Ignore_id" and "Insert_id" from "Routing table" window; In the previous
Changed)
CallDigits (Call
Number)
picture it can be seen on the first record (an incoming call) in the field "Ident" the value
"120" modified in the field "Ident changed" to "3320" (like in the examples);
call number (20 digits)(this field may be modified for outgoing records by "Ignore"and
"Insert" fields from "Define calls direction" window and by fields "Ignore"and "Insert"
from "Routing table" window);
This field is filled only for incoming calls and contains the changed call number which can be
CallDigits
modified by "Ignore" and "Insert" fields from directions definition window and by
Changed(Call
"Ignore" and "Insert" by "Routing table" window; In the previous picture it can be seen
Number Modified) on the first record (an incoming call) in the field "CallDigits" the value "81712345678"
modified in the field "CallDigits changed" to "0712345678" (like in the examples);
Day and Time
(Day and Time of
the call)
Day and Time of the call in the following shape dd-mm-yy,hh:mm:ss
Selection
(Duration of the
selection and dial
phases)
xxx - selection duration of the call in seconds (3 digits); this time is calculated by adding the
values "Dial time" and "Selection time"
Connected
Duration
(Duration of the
call)
xxxxxx - connected duration of the call in seconds (6 digits)
TUnits (Billing
xxxxx - Billing Units for the call (5 digits)
Units for the call)
SIM1 (Destination When the destination port is a GSM port (multiACCESS or QUTEX) it specify a value for SIM
SIM Number)
card (1,2,3,4 or ff)
PortD (Destination - physical position of the destination port (5 digits) (when the call is unfinished a value of
Port)
65535 will be found in this field (5 digits)
End (Finalization
call mode)
Possible values are AOK, BOK, ARELS, BRELS, AINEX, BINEX, ACONG, BCONG, ASERR,
BSERR, ANERR, BNERR, ANANS, BNANS, ABUSY, BBUSY, ATOUT and BTOUT
End 2(Finalization
Possible values are ' 31' (normal call) for non ISDN calls or values from ISDN standard for
call mode on
release code
ISDN calls)
Dial (Dial time)
xxx-dial time in seconds
Sel (Selection
time)
xxx-selection time in seconds
Call (Call type)
xx-specify call type (0-incoming call, 1-outgoing call). This field will be used for further
purposes.
SIM2 (Source SIM When the source port is a GSM port (multiACCESS or QUTEX) it specify a value for SIM card
Number)
(1,2,3,4 or ff)
IMSI
International Mobile Subscriber Identity (is filled for incoming calls routed through a GSM
port (multiACCESS or QUTEX))
CELL
The GSM CELL where the SIM used for the call ("Destination SIM Number" on the
"Destination Port") is registered.(multiACCESS or QUTEX)
Direction
The direction to which the destination port is belonging (it is the output direction)
Note1: several settings established in the monitoring filter are saved in the file
"moni_fl.dat" on the harddisk in the directory where "gwconfig" software is
running. These settings are:"Port Type" (section "Call Source") - subscriber
part and junction part, "Release Side" ("A Side" or "B Side") and "Call Type"
("ANSWER", "RELEASE", "INEX", "CONG", "SERR", "NERR", "NO ANSWER",
"BUSY" and "TIMEOUT"). These settings are loaded before the showing of the
monitoring filter in order to be pre-established.
amount of time.

Administration, and Maintenance - SMS FILES
These files are used to keep information regarding the sending of short text
messages (SMS) and about the calls made from an internet browser. SMS's
can be sent and CALLS can be made from any internet browser by accessing
the TOPEX gateway. The "SMS" files are named <current date>.sms. The SMS
files are also containing the CALLBACK actions.
1) To send a SMS just connect to the gateway to the "txsms.html" page (to
reach this page, you must first type into the browser's address bar the IP
address of the TOPEX gateway).
For accessing the TOPEX gateway, you must add its IP address to the section
"Trusted sites" for your browser. The format of the record to be added is
"http://xxx.xxx.xxx.xxx" where "xxx.xxx.xxx.xxx" is the IP address of the
TOPEX gateway. The authentication of clients is performed using "Digest
Authentication" algorithm.
Accessing TOPEX gateway from an Internet browser is password protected. You
must logon with your name and password.
The default password is "topex".

After going over the password protection, a new page will appear asking the
user to enter the SMS destination phone number (field "Phone Number") and
the SMS message (field "SMS text"). The SMS will be sent by clicking the
"SendSms" option. The SMS can't be sent if direction named "SENDSMS" does
not exist on the target.The SMS number will be parsed with all the rules which
are included in the definition of the "SENDSMS" direction and the routing
table.
sent ("OK Your SMS was sent OK! Thank you!").
Example of SMS records in a SMS file:
SMS ,WWW ,192.168.1.152 ,0700000000 ,12-0304,07:24:50,000005,00004,00,00008,BOK , 16,222222222222222
SMS ,WWW ,192.168.1.152 ,0700000000 ,12-0304,07:26:12,000000,00000,ff,65535,ASERR, 16,
SMS ,WWW ,192.168.1.152 ,0700000000 ,12-0304,07:27:02,000000,00000,ff,65535,AINEX, 16,
- first record is containing a SMS message from the address "192.168.1.152"
to the number "0700000000". The SMS was sent successfully ("BOK");
- second record contains a SMS message from the address "192.168.1.152" to
the number "0700000000". The SMS was not sent successfully because the
direction called "SENDSMS" was not existent on the target ("ASERR");
- the third record is containing a SMS message from the address
"192.168.1.152" to the number "0700000000". The SMS was not sent
successfully because no route to destination was found ("AINEX");
Note 1): the total number of digits that can be processed by "gwconfig"
software is 20;
Note 3): the code "WWW" is used only to indicate the origin of the SMS
("WWW");
There is also another page called "txsmsgrp.html" which is used to send a SMS
to a group of mobile phones. These groups can be defined on the gateway in

the file "/mnt/app/cfg/sms_groups". The structure of this file is as following:
grup test
0740000001
0740000002
The "Group Name" in the previous picture will be filled in with the group
name: in the displayed example the group name is "test" (the word which
follows the key word "grup". The SMS will be sent to the phone numbers that
follow the line with "grup" keyword. The numbers are searched until an empty
line is found or until another line starting with "grup" is found.
sent ("Your SMS has been sent OK! Sent to 2 numbers"). The number of
mobile phone destinations is also displayed.
2) A call can be sent in the same way by accessing the page "txcall.html". To
allow sending a CALL from an Internet browser the direction called
"SENDCALL" must exist on the target. The call will pass all the rules which are
included in the definition of the "SENDCALL" direction and the routing table.
The user must enter the CALL destination phone number (field "Phone
Number") and further options (field "Call Options" - not yet implemented).
A successful message will appear to inform the user that the CALL will be made
Example of records regarding making CALLS from a SMS file:
CALL,WWW ,192.168.1.152 ,0700000000,12-0304,07:45:49,000000,00000,ff,65535,AINEX, 16,
CALL,WWW ,192.168.1.152 ,0700000000,12-0304,07:47:10,000000,00000,ff,65535,ASERR, 16,
CALL,WWW ,192.168.1.152 ,0700000000,12-0304,07:48:10,000040,00004,00,00008,BOK , 16,222222222222222
- first record is containing a CALL test made from the address "192.168.1.152"
to the number "0700000000". The CALL wasn't made ("AINEX") because no
route to destination was found;
- second record is containing a CALL test from the address "192.168.1.152" to
the number "0700000000". The CALL was not made because the direction
called "SENDCALL" was not existent on the target ("ASERR");
- the third record is containing a CALL test from the address "192.168.1.152"
to the number "0700000000". The CALL was made successfully ("BOK"); the
called part was answered;
Note 1): The total number of digits that can be processed by "gwconfig"
software is 20;
Note 3): the code "WWW" is used only to indicate the origin of the CALL
("WWW");
3) SMS ALERT indication. When a SMS alert is sent, the current SMS file
contains the number and the moment of sending and the following fields:
"Type" -> "SMS", "Source" -> "ALARM" and "IP" -> 127.0.0.1.
SMS ,ALARM,127.0.0.1 0700000000 ,08-1004,16:44:11,000599,00010,00,00033,BOK , 16,226019451004927
4) CALLBACK records
CALL,CBACK,0700000000 ,0700000000 ,13-04-
04,11:25:33,000001,00000,00,00008,AOK , 16,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:32:32,000013,00000,ff,00008,BBUSY, 17,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:33:14,000007,00000,00,00008,BRELS, 16,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:36:07,000001,00000,00,00008,AOK , 16,226019451004927
CALL,CBACK,0700000000 ,0700000000 ,13-0404,11:40:22,000012,00000,00,00008,BBUSY, 17,226019451004927
CALL,CBACK,0700000000 ,0700000001 ,13-0404,12:03:40,000001,00000,00,00009,AOK , 16,226019451004922
A record is generated into a SMS file for each back call. Callback table contains
the following fields: "Identity", "Action", "Callback", "CallTo" and "MailTo". A
CALLBACK record contains the identity (in the example it is the field
"0700000000" - the identity is one of the "Identity" from the Callback table)
and the number dialed in the callback action. The number dialed can be the
same number like the identity number or can be another one (if the field
"Callback" is filled with another number then the identity number).
In the billing file, the number dialed by the called party of the back call action
will be saved. If the "CallTo" field is filled in the callback table then that
number will be saved in the billing file.
A SMS file has the following fields:
Field
Description
Record
type
SMS or CALL (the record is a SMS

respectively a CALL test)
Source
Port
WWW (for SMS and CALLS made from the

internet),CBACK and ALARM
IP or
identity
the IP address of the client from where the

SMS was sent or the CALL was launched
(20 digits) or the identity of the call in case
of a CALLBACK record
CallDigits
(Call
SMS destination number or CALL test

number (20 digits) or the number called in
Number)
a CALLBACK record
Day and
Time

shape dd-mm-yy,hh:mm:ss (ending time)
Call
Duration
xxxxxx - duration of the call in seconds (6

digits). Is different from a zero value in
case of a successful sending of a SMS or
making a CALL test and indicates the
amount of time from the moment of
accepting the request and the moment of
the successful ending;
Length
xxxxx - the length of SMS message and the

length of the option of CALL message (5
digits) or 00000 for a CALLBACK record
Destination
When the destination port is a GSM port it
SIM
specify a value for SIM (1,2,3,4 or ff)
Number
Port
digits)
Finalization BRELS, AINEX, BINEX, ACONG, BCONG,
call mode ASERR, BSERR, ANERR, BNERR, ANANS,
BNANS, ABUSY, BBUSY, ATOUT and BTOUT
Finalization
Possible values are either ' 31' (normal call)
call mode
for non ISDN calls or values corresponding
on ISDN
to ISDN standard for call release codes
calls
IMSI
International Mobile Subscriber Identity
By choosing "SMS" - tree command for a system, all SMS files from the folder
"Billing" of the selected system directory we'll be seen.
You choose the SMS file you want to see, and by double clicking the left mouse
display of the SMS information. This filter for SMS files permits setting the
options and values for searching the records inside the SMS files.
the SMS file that you have selected. Sub-fields are Day and Hour each of
them with "From" and "Until" limits. You may change the default period to
extend the time interval that is analyzed. The program will look for records in
the SMS files whose name fall inside the selected time period.
From the source point of view you may specify the following options:
- IP source;
- you may specify the source value: (this value can be used in further
developments);
- the record type: SMS or CALL;
- the record source: WWW or CBACK or ALARM;
From the call destination (called party) point of view you may specify the
following options:
the number of destination digits less, equal or greater then the value typed.
port)
SMS records have a caller and a called party. For an incoming call on E1 trunk
the source party will be a channel on the trunk and the call will be routed over
a GSM interface (the destination port). Caller party will be represented by 'A'
and called party by 'B' (field "Release Side"). Depending by the side which
ends the call a letter ( 'A' or 'B') will be shown and the finalization mode will
contain one of the following strings: OK - ANSWER, RELS - RELEASE, INEX INEX, CONG - CONG, SERR - SERR, NERR - NERR, NANS - NO ANSWER, BUSY
- BUSY, TOUT - TIMEOUT. "Call Type" lets you to specify the mode of ending
of the call.
You may set a value for "ISDN EndType" which represent call release code
for ISDN calls. Other types of calls will display a value of ' 31' in the SMS
records.
You may set also the option to select the records with the duration (in
seconds) less, equal or greater then the value typed.
number of digits, 3 for the sim index and ISDN EndType, 5 for destination port
position, 6 for duration, 15 for the IP field, and 16 for specifying IMSI code and
20 for specifying destination digits.
Certain values from the SMS filter are checked before the validation (by
pressing the button "OK"). The correctness of the period definition (day and
second less or equal then 59), sim index (in range 1 to 4 or 255), destination
port position (65535 or a value in the range from 0 to 319), duration (a value
back the focus to the error field in order to correct the wrong data, the red
color disappears. In the following example an error message "Wrong sim
index" is displayed because of an error on SIM field (a value "5" which is
greater than the maximum number of a SIM card (4).
(option "Display only the total without the records") that correspond to
the records in a certain time interval for the purpose of post-processing (cost
analysis) of the stored SMS information. For these applications, you need a
text file with values only (that may be imported into a spreadsheet like Excel)
but without totals interspread in it.
in the "SMS Report". These columns will be presented later in this chapter. The
information regarding the SMS columns to be displayed is stored in the file
"sms_rep.dat" on the harddisk in the same home directory from where
"gwconfig" software is running. In this file is also saved the information
regarding the size of the columns presented in the SMS report.
By pressing "OK" button all SMS records corresponding to the filter criteria will
be seen.
(field "Attempts"), total number of SMS successfully sent (field
"Connected") and the percentage of successfully SMS sent- (field "Period")
and in the end a total for all of the intervals - total number of attempts, total
number of connected and the percentage of successfully connections.
subdirectory for the chosen system in a file with the "sms" extension and the
the total of records for several days and also a general total.
Note2: several settings which are established in the SMS filter are saved in the
file "sms_fl.dat" on the harddisk in the home directory where "gwconfig"
software is running. These settings are:"Record Type" (section "Call Source") SMS or CALL,"Record Source" (section "Call Source") - WWW or CBACK or
ALARM, "Release Side" ("A Side" or "B Side"), "Call Type" ("ANSWER",
"RELEASE", "INEX", "CONG", "SERR", "NERR", "NO ANSWER", "BUSY" and
"TIMEOUT") and the options regarding the viewing of totals of SMS records
("Display only the total without the records" and "Display only the records
without a total"). These settings are loaded before the showing of the SMS
filter in order to be pre-established.
If the number of records is large, the sorting operation can take a significant
amount of time.

1. Connecting steps
("tmaxsim.bin");

"sip_pbx.cfg".
occurs.
message appears.
Note:
gateways.
signal levels).

notice:
"Exit";

an EONES slave.
one or to go back
.
Types of boards:
Analogue
Subscriber board
multiACCESS/QUTEX
8 ports (FXS
card)
GSM/UMTS/CDMA
ports
PBX junctions
board 8 ports
(FXO card)
multiACCESS/QUTEX
E&M junctions
board 4 ports
multiACCESS/QUTEX
BL phones board
multiACCESS/QUTEX
8 ports
Radio board 4
ports
multiACCESS/QUTEX
NT/TE
ISDN-BRI board
with 4 ports
multiACCESS/QUTEX
E1R2 board (32

channels)
E1ISDN-PRI
board (32
channels)
E1SS7 board (32

channels)
E1R1 board (32

channels)
VOIP card - with

H323 or SIP
protocol (8,16,32
or 64 channels)
RG

distinct areas:

Port type
Hunting
Group
Pickup
Group
Target
SIM
Index
S
YES
(Subscriber)
YES
YES
YES
YES
YES
YES (for "BC"

settled)
NO
G (GSM)
YES
YES
NO
NO
NO
NO
NO
YES
P (JPABX)
YES
YES
NO
NO
NO
NO
YES
NO
E (E&M)
YES
YES
NO
NO
NO
NO
YES
NO
B (BL)
YES
YES
YES
YES
NO
NO
YES
NO


E1 trunks.

2.4.1. E1 card
LMA

RSA

BER Bit error rate

D


(32 positions)



2.4.2. VOIP card

64 channels.
channels.
2.5. CARD STATUS
33.

each 60 seconds.

unused.
card.
--mem 16 --gw-mac 00:48:54:1A:D2:8D -m 00:52:C2:40:3E:40

I


Name":
"viz".





gateway is " ".
configuration file.
"LAN=ppp0",
"WAN=eth0"
"USE_FIREWALL=yes"
Attention!
Debug
TOPEX gateway;
TOPEX gateway;
server;
information.
in the debug file:
the debug file:
timetest 0
CFG Trafic run 0
00257 7235150 Digits 1234567891108 Ident 120
00257 7235200 Route N 123456 ... NT 123456 ... RxT 9000
param 0
00258 7235200 Digits Ident 120

1,Brelease 0
1,Brelease 0
type of card.)
OID ("1.3.6.1.4.1.x")

shown:


8 characters.
corresponding list.
operation.
is 16 digits.
20 digits.
Digits
Purpose
Interpretation
bit 0 (mask 0x1000)
DIRCHECKCALLBACK
received identity
(caller identity)
bit 3 (mask 0x8000)

GSM ports placed on
will be treated as
CDMA modules
Interpretation
bit 0 (mask 0x0100)
DIRTESTNET (used in
case of a direction
which contains GSM
outgoing GSM module
registered
x (digit 1)
DIRGOODASR - when
bit 1 (mask 0x0200)
RELEASE message is
sent on ISDN with a
delay of 5 seconds
when a congestion
situation is
encountered on GSM
y (digit 2)
z (digit 3)
w (digit 4)
bit 2 (mask 0x0400)
DIRCATCALL - when
calls will be cut
modules for which a
reprogramming is
necessary (for
example when a SIM
must be changed
because of an used
algorithm)
bit 3 (mask 0x0800)
verify CLIR - when

each time after the
to a GSM module
Interpretation
bit 0 (mask 0x0001)

direction
bit 1 (mask 0x0002)

is sent on selected
direction
bit 2 (mask 0x0004)
- establish the
algorithm for
changing SIM on GSM
periods). When the
used (equal usage
time for each SIM)
bit 3 (mask 0x0008)

on the next link,
answers

Routing Table.
the higher is 9.

incoming calls.
Examples:
1000.
value is 34.
VoIP calls.


3.8. Routing table

licence window);
routing table.
'Dest' list
the 'Dest' list;
moment.
Digits
Bit (from
Interpretation
right to left)
x (digit 1)

0x8000)
gateway.
bit 1 (mask
2000)
on output link.
bit 0 (mask
0x1000)
on the gateway.
y (digit 2)
restricted.
allowed - 20.
z (digit 3)

w digit 4)

"Action"
incoming call;
hear anything;
"Prefix = 8"
"Action = SERV"
"Ignore =1"
"Signaling = 0000"
20".
DIR
GSM
00a4
110a
Method 1)
example below).
Method 2)

week.
Define Holidays

Method 3)
to 9.

be allowed.

nature of address.
option.
has occured
will be ignored.
Search Search
Significance
Mode Param
ASR
not
used

based on ASR value
ACD
not
used

based on ACD value
Priority
not
used

"dest" field).
value is passed
Down
not
used

group will have the
highest priority.
Up
not
used

group will have the
highest priority.
Circular
not
used

circulary.

on percentage. The
"Search Parameters"
Percent the
machine.


values are:
"unknown"
"op_french"
"op_english"
"op_german"
"op_russian"
"op_spain"
"op_rsrv1"
"op_rsrv2"
"op_rsrv3"
"notused"
"ord_subscr"
"prio_subscr"
"data_call"
"test_call"
"payphone"
"uk_oper_call"
"uk_admin_diverted"
3.9. LCR Table

l 00 1 00:00 24:00 0
l 00 1e 00:00 24:00 1
l 00 20 00:00 00:01 f
l 00 20 00:01 12:01 11
l 00 20 12:01 14:01 13
l 00 20 14:01 23:01 a
l 00 20 23:01 24:01 9
l 07 13 00:00 24:00 1
l 07 4 00:00 11:45 1
l 07 4 11:45 12:23 8
l 07 4 12:23 12:31 1
l 07 4 12:31 18:50 8




character.
s 00 1f 00:00 06:00 2
s 00 17 06:00 20:00 0
s 00 1f 20:00 21:30 3
s 00 1f 21:30 24:00 0
s 00 8 06:00 20:00 1
s 00 60 00:00 24:00 0
s 00 80 00:00 12:00 0
s 00 80 12:00 24:00 1
s 01 ff 00:00 06:00 0
s 01 ff 06:00 12:00 1
s 01 ff 12:00 18:00 2
s 01 ff 18:00 24:00 3
s 02 ff 00:00 24:00 1
s 03 ff 00:00 24:00 0
h 01 01
h 01 01
h 25 12
h 08 01


"Del" button.

"DISA"):
number;
"DISA".

appear:

point).
(own codes)" zone.
performed).
Examples:
with "8103".

appear:
range from 0 to 7).
6.
icon.
all CIC values.

appear:
destination.
card (PG).
Gateway MAC.

comfort noise.
default.
DTMF

field to the right
The syntax is :

current day.
Examples:

192.168.244.123


used.

9010.
Codecs g729b,g729
VAD disabled
Fast Start enabled
also 0.
3.17. Alerts
- by SMS
alerts:
must be checked.
used.
and so on.

target.
occur.
3.18. Test calls


port.
"0700000000 120 120 0"
before:
"12345 101 257 1",

calls):
seconds)
traffic_idle 10 5
added seconds)
traffic_sel 5 3
added seconds)
traffic_con 1 2
#traffic_call nr id

5 (5+0) and 8 (5+3).
(1+0) and 3 (1+2)
("id")

displayed.
connected system.


3.21. File Editor

Editor").
3.22. Loading hour

hour'.

seconds.

interrogation).
Notes:
level.


system check.

window.
4. Print options
5. NOTE

any system.

GW Config

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

GW Config

Diunggah oleh

Hak Cipta:

Format Tersedia

TOPEX multiACCESS/QUTEX/EONES/multiSwitch - Operations,

Administration, and Maintenance - CONSIDERATIONS

- Now the OAM program is fully installed on your system.

Through the OAM program you can configure and manage

Adds a system in the arborescent structure

Shows the significance of colors used in "Modify Configuration" and

Shows the software version

Opens the help window

Exit from the OAM program

Defines directions (trunk groups) name

Defines and programs test calls

performed in the same time on both

- The OAM program for TOPEX multiACCESS/QUTEX gateway is using a tree

editing and later uploading

Initiates a connection to the system

Disconnect, breaks the existing connection to the system

Displays the parameters of the connection to the system

Displays the alarm files

Displays the billing files

Displays call statistics on ports and directions

Displays the monitor files

Displays the ASR ("Answer Seizure Ratio") files. These files

You can view text files with every kind of extension

Displays the log and lch files

10. Password mode

- After pressing "OK" button:

- To add a user to the list you must select "Add" button:

- Only the administrator can define new users.

TOPEX multiACCESS/QUTEX/EONES/multiswitch - Operations,

IP address - enter the IP address of the system. It can be a numeric IP

2 characters for the "Serial Port num".

- To remove a TOPEX multiACCESS/QUTEX system from the structure, select it

TOPEX multiACCESS/QUTEX/EONES/multiswitch - Operations,

3. View print files

Allows the user to

The response is:

within the GSM

part has answered

The command is used The GSM module is

This command will

This command will

text format and 0 for

used to set the pin codes for GSM modules at

set pin range sss sss pppp

used to set the pin codes for GSM modules in

set/res moni ppp

used to put / extract a GSM port from

send gsm at.......

(used to dial a number)

set debug ppp ppp

used to start debugging on a port. The port

set view ppp

must be sent to port "ppp" after the

res debug ppp ppp

used to stop debugging on port "ppp". The

res view ppp

must be sent to port "ppp" after the

set tmax sss sss ttt

allows you to define a time interval ('ttt') after

set tsim sss ttt

allows setting the time counter (loading time):

it is used for displaying the total number of

set calls off