System information

2: Peak
3: Offpeak
4: Weekday
5: Weekend
6: Offpeak and weekend
7: Evening
8: Night
9: Holiday
10: All times
11: Other Times (Rest)
example: v_getprice '1','36301234567',6555,'003615555555','150',666,-1,4,2,99,99,4,11,41,500
The v_getprice stored procedure will return the following fields:
tb_billentries.currency,tb_billingtimes.isdiff,tb_billingtimes.origprice,tb_billingtimes.price, tb_billentries.billingstep,
tb_billentries.minammount,tb_billentries.freeammount,tb_billentries.freeafter,tb_billentries.vatincluded, tb_billentries.vatvalue,
tb_billentries.converttonative,tb_billentries.converttovat
According to returned billing settings, the price is calculated accordingly.
If there are no price defined, than default price are loaded. (if set)
If there are no sales price defined, than will be loaded from user setting (commission)
For enduser prices, the discounts and userreductions are applied if set so. Then the user credit is updated.
If there are any error with the billing process, than the default prices are applied if exists.
Billing verification:
List the required CDR records with “Show minute price option”
You can find the billing logs if you search for the called number in the server logs.
Copy the required v_getprice log in the direct query form.
Check if the returned values are as expected.
4.5.8. Invoice and payment storage
Invoices and payments are stored in tb_invoices in the database. So the invoices can be searched, recreated and storno invoice can be built based on
existing invoices (conforming to Hungarian laws).
The last invoice number are loaded from database before every new invoice and incremented. Thus the invoice number increment is guaranteed the by
database engine transactional behavior.