Mera MVTS Configuration Sample for ArrowBilling
Friday, 20 April 2007
This document provides a sample about how to configure Mera Systems VoIP Transit softswitch (MVTS) to work with DataTechLabs ArrowBilling.

Operational Modes

Three major AAA operational modes are available:
  • Accounting only mode
  • Authorization and Accounting mode
  • Authorization, Accounting  and Routing mode (available with ArrowBilling 1.5.0 or later, BSDRadius versions only)
 

Accounting Only Mode

In this mode Authorization is provided locally in MVTS with entries in user.cfg file. Only Accounting messages are sent to Arrow Billing: 
-------------------
file: meraproxy.cfg
-------------------

[Radius]
local_address=*
auth_enable= 0
acct_enable= 1
acct_type=1
acct_leg_type=4
secret=<sharedsecret>
acct_address=<billing server ip>
acct_port=1813
auth_address=<billing server ip>
auth_port=1812
local_auth_port=1812
local_acct_port=1813
suppress_Q931_cause=1
q931_h323_disconnect_cause=1
use_h323_ivr_in=0

--------------
file: user.cfg
--------------

[default]
user=default
acct_enable=1
auth_enable=0
 

Authorization and Accounting Mode

In this mode Authorization and Accounting requests both are sent to Arrow Billing. It is not necessary to create entries in user.cfg file. 
-------------------
file: meraproxy.cfg
-------------------

[Radius]
local_address=*
auth_enable= 1
acct_enable= 1
acct_type=1
acct_leg_type=4
secret=<sharedsecret>
acct_address=<billing server ip>
acct_port=1813
auth_address=<billing server ip>
auth_port=1812
local_auth_port=1812
local_acct_port=1813
suppress_Q931_cause=1
q931_h323_disconnect_cause=1
use_h323_ivr_in=0

--------------
file: user.cfg
--------------

[default]
user=default
acct_enable=1
auth_enable=1

Authorization, Accounting  and Routing mode

Routing is available starting with ArrowBilling version 1.5.0 which has BSDRadius server enabled. To enable Routing for H.323 on MVTS, please add following entries:

gateway.cfg
-----------
[H323]
address=1.1.1.1
mask=0.0.0.0

dialpeer.cfg
------------
[goout]
gateway = EXTERNAL
dst_pattern = [0-9]*

 

For routing to SIP gateways, entry in gateway.cfg should be following:

gateway.cfg
-----------
[SIP]
address=1.1.1.1
mask=0.0.0.0
 

Working with SIP-HIT module

To enable SIP-HIT module, add following entry into user.cfg file under [default] section: 
converter=SIP
 
 
SIP clients will be authenticated and accounted in same way as H.323 clients.


Setting up Arrow Billing for Mera MVTS

Adding Data Source

To enable receiving AAA requests from MVTS, follow these steps:
  1. Click Tools > Data Sources.
  2. Click on the link Add Data Source.


  3. In "Add Data Source" screen provide following information:
    • Source Name - any descriptive name for this device, example "Mera1"
    • NAS IP Address - IP address of this device
    • Radius Client IP Address - leave this checkbox checked if Radius packets will be received from same IP, otherwise uncheck it and enter IP Address which will send Radius requests
    • Shared Secret - secret used between device and Arrow Billing Radius server
    • Parent Source - select NAS from list which will receive traffic from this device if it is also Data Soucre for this Arrow Billing
    • Source Type - choose Mera MVTS
    • Enabled - check this box to make the data source enabled.
  4. Submit Entry by pressing the button Create.
 

Common Issues and FAQ

Is it possible to provide DID for my SIP endpoints registered to MVTS and allow calling between them?

Yes, it is supported. First, make sure your endpoints register properly on MVTS. During Authentication phase Arrow Billing returns special attribute required by MVTS to assign phone numbers to endpoints. The format of the message is following: 
xpgk-ep-number="xpgk-ep-number=123456"

I have a setup where my endpoints register to GnuGK gatekeeper and then call is passed to MVTS for Routing. How to avoid duplicate CDR generation from both devides?

You can simply create separate entry for GnuGK in MVTS fateway.cfg and disable accounting for it. Example:

[gnugk1]
address = 10.1.1.94
port = 1720
auth_enable=0
acct_enable=0

 

This ensures that endpoint is assigned number 123456. Other callers, including calls from outside, will reach this endpoint by calling number 123456. Account must have authentication type H323ID/Username, and there should be rate table associated with it so others are allowed to call it (even if calls are free).




Digg!Del.icio.us!Slashdot!Technorati!Free social bookmarking plugins and extensions for Joomla! websites! title=
 
[ Back ]