System information

You can generate random prepaid codes here.
Prepaid account can be charged over the website or by ivr:
Website operation:
-user authentication (tb_users.username and password)
-check if pincard is valid (tb_prepaidcodes)
-increase credit for the user (tb_users.credit)
IVR operation:
-automatic user authentication based on sip registration or require entering the phone number to be charged
-require pincode
-check if pincard is valid (tb_prepaidcodes)
-increase credit for the user (tb_users.credit)
-goodbye message
4.5.7. The billing process
Every cdr record are handled by the billing module. Prices are determined by the v_getprice stored parameters.
v_getprice parameters:
@type tinyint: type of the billing. 1=enduser cost, 2= provider cost, 3=sales cost, 4 = company profit, 5 = other cost
@callednorm varchar(26): normalized callednumber. example: 36301111111 (B number)
@callerid int: database id of the caller user
@callernum varchar(26): caller number (A number)
@techprefix varchar(4): 3 digit tech prefix if exists
@calledid int: database id of the called user
@calledpacket int: simpacket if exists
@timetype1 tinyint: time period
@timetype2 tinyint: time period
@timetype3 tinyint: time period
@timetype4 tinyint: time period
@currday smallint: weekday number (Monday is 1)
@currhour smallint: call midtime hour
@currmin smallint: call midtime minute
@parentid int = 1: database id for the parent of the caller user
timetypes are considered when you doesn’t set a concrete start-end period in the price list, and you choose from a predefined pattern (peak, offpeak,
weekend, weekday, holiday,evening, night). the following timetypes are defined:
0: Disabled
1: Start-End Time