multiSwitch – user manual
© TOPEX 2008 38
7.3.2 Data Base activation
The following lines are referring to the process poll activation / deactivation –
establishes the database type. The supported format for data base by TOPEX multiSwitch
are PostGre SQL, My SQL and Microsoft SQL. The value “0” means deactivation and “1”
activation.
pgsql_billing 0/1
mysql_billing 0/1
mssql_billing 0/1
pgsql_prepaid_pool 0/1
pgsql_ani_pool 0/1
pgsql_simserver_pool 0/1
rtptx_pool 0/1
rtprx_pool 0/1
dns_pool 0/1
7.3.3 RADIUS activation
The next lines includes several parameters related to RADIUS AAA (
A
uthentication,
A
uthorized,
A
ccounting).
TOPEX multiSwitch can be interconnected with an external billing system. At this
moment multiSwitch supports 3 billing dictionaries: TOPEX, Quintum and Mind.
radius_billing 1
// “
1
” for activation and “
0
” for deactivation
radius_dictionary 0
// “0=Topex; 1=Quintum; default 0
tx_access_request 1
// sends or not access request for authentication
tx_accounting_start 1
// sends or not accounting_start for billing. The value “
1
”
indicates activation and “
0
” deactivation. You can use billing also without activate
“accounting_start” parameter. You can activate only “accounting_stop”.
radius_auth cli
// establishes the information sent in the “access_request”
packet in the username field for authentication on trunk input calls.
The possible values for radius authentication on trunks are:
cli
= Caller ID, ANI
ip
= IP source of the call
class_name
= source class (direction) of the call
radius_sip_user_auth ip
// establishes the information sent in the
“access_request” package in the username field for authentication on the calls
initiated by the SIP users
The possible values for radius authentication on SIP users are:
cli
= Caller ID, ANI
ip
= IP source of the call
The command below command enables / disables the CDR (Call Detail Records) writing in
Mind format assuring the interconnection with an external billing system developed by Mind.
mind_cdr 1/0