Mera MVTS Integration Manual

Copyright © 2006-2008 JeraSoft Development

http://jerasoft.net/
1. Description
To be able to collect the calls data from Mera MVTS you can go two ways:
collect the data via the CDR-files or via the RADIUS-server. The differences in
these methods are the following:
● CDR-files import
○ Advantages: high reliability and stability, no calls information
may be lost due to server or client side;
○ Disadvantages: the data is received with delays because files
are copying at the defined periods of time.
● RADIUS-server
○ Advantages: data is received in real-time mode (the call packet
is sent right after the end of the call), call authorization procedure is
possible;
○ Disadvantages: when network or server hardware is unstable,
the loss of data is possible (although, this data can be restored later
with CDR-files).
Of course, if hardware posseses enough capacity, you can combine both
methods.

2. Integration via CDR-files

2.1. BillBery settings

To allow the billing system collect the data from MVTS via CDR-files, you
need to do the following:
1) Create Mera MVTS gateway within BillBery (go to VoIP Gateways
section of User Manual) and enable Files Collector. In gateway's
parameters you must define:
- IP: MVTS server IP adress;
- Collector Type: «CDR/ Mera MVTS (cdr_format=0)»;
- After Parse: define the desired method of collected files processing;
2) Enable the files autodownloader under the Files Downloader tab and
specify appropriate paths where files should be written to and where
they should be downloaded from (check VoIP Gateways section of User
Manual for more info).
3) Make sure, that Task Scheduler section has Files Collector and Files
Downloader processes enabled
2.2. MVTS settings
First thing you need to do, is to create SSH-keys on MVTS server with
next set of commands:
cd /usr/local/billbery/bin
su billbery
./ssh_keys.py root@MVTS_server_IP

Important note: this set of commands needs to be run on BillBery

server.
Also, you can define the period of CDR-files creation. To do this, open the
meraproxy.cfg file and specify the period parameter in [Billing] section. Also,
specify the cdr_format=0 if you have not already done so (make sure that the
format value is equal to the chosen collector in the billing system). Thus, the
[Billing] section may look like this:
[Billing]
period = 01:00:00
file = ../billing/bill
cdr_format = 0
level = 3

3. Integration via RADIUS

3.1. BillBery settings

To allow the billing system collect the data from MVTS via RADIUS-
protocol, you need to do the following:
1) Create Mera MVTS gateway within BillBery (go to VoIP Gateways
section of User Manual) and enable RADIUS Server collector. In
gateway's parameters you must define:
- IP: MVTS server IP adress;
- Radius Server collector type: «RADIUS / Mera MVTS»;
- Secret: random password, that is equal to the password specified in
meraproxy.cfg file (look below for details).
2) Make sure that Task Scheduler section has RADIUS Server process
enabled.
3) Make sure that System Status section has RADIUS Server process
running, and if not – start it.
3.2. MVTS settings

3.2.1. RADIUS accounting and authorization

To allow the correct data collection via RADIUS, open the meraproxy.cfg
file and define next parameters under the [Radius] section:
q931_h323_disconnect_cause=1
use_h323_ivr_in=1
suppress_Q931_cause=0
local_auth_port = 11812
local_acct_port = 11813
local_route_port = 11814
acct_port = 1813
auth_port = 1812
route_port = 1812
secret = --change to your secret in billing--
acct_enable = 1
acct_address = --billing IP-adress--
acct_type = 1
acct_leg_type = 2
acct_stop_only = 1
dst_user_orig_leg=1

Please note, that if you plan to use BillBery's capacity control features
and/or need to monitor active calls in Active Calls section, you will have to
enable start and stop call packets by assigning acct_stop_only parameter
following value:
acct_stop_only = 0

The secret field must contain the password, that will be used in
interconnection of billing system and MVTS. Also, don't forget to specify the
billing server IP adress.
To perform calls authorization, add next rows:
auth_enable = 1
auth_address = --billing IP-adress--

3.2.2. Dynamical Routing setup

To enable the dynamic routing, perform the following:
In gateways.cfg file create next section (names matching is essential):
[BILLBERY_GW]
address= --billing IP-adress--
gateway_mode=3
gateway_type=1
port=1720
proxy_type=1
 And in meraproxy.cfg file add following lines:
route_address = --billing IP-adress--
route_enable = 1

Also, in file dialpeer.cfg, add «gateway=EXTERNAL» line under a route you

want to be routed dynamically via billing system. An example of route section
looks like this (where «dst_pattern=.+» is a definition of route):
[R_BILLBERY]
dst_pattern=.+
gateway=EXTERNAL
hunt_stop=1
priority=100

Important notice: if you need to perform routing and authorization only

via BillBery, without Mera MVTS involvement, you will need to add the
following section into gateways.cfg file:

[public_access]
address=127.0.0.1
mask=0.0.0.0