Billing: Difference between revisions

From VoIPmonitor.org
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Billing feature overview =  
== Billing Feature Overview ==


* CDR contains two price types - customer price and operator price. The purpose is to know how you are selling and what it costs watching expense to various operators etc.  
* Two price types in CDR: Customer and operator (for comparing operators).
* multiple billing tables - for each of your operator and for each customer  
* Multiple billing tables: For each operator and customer.
* billing watchdog rule quota - per hour / day / week / month aggregated per src IP or per tel. number  
* Billing watchdog rules: Quotas per hour/day/week/month aggregated by src IP or tel. number.
* billing watchdog rule expensive destination
* Billing watchdog rules: For expensive destinations.


= Settings -> Billing configuration =
== Settings > Billing Configuration ==


== billing type / rules ==
Sections: Billing type/rules, state holidays, operator assignment, customer assignment, exclude, aggregation, currency, settings.


Here you need to create at least one billing table which will be used to bill customer and operator price. If you do not need to have customer price but only operator price, just create one billing table for each operator (if you have different pricing for each operator) and do not check "Default customer billing" checkbox.
=== Billing Type / Rules ===


* Name: name of the billing table
Create at least one billing table for customer/operator prices. For operator-only, create per operator and assign in "operator assignment" without "Default customer billing".
* State holidays: choose holidays table which will be used if peak is enabled
* Default price: is price per minute (offpeak if peak/offpeak enabled)
* Enable peak / offpeak: enable billing based on peak / offpeak
* Default price peak: is price per minute for peak period (and offpeak if peak/offpeak enabled)
* Default T1: number of seconds for the first impulse.
* Default T2: lenght of period. For example call was 30 seconds length and T1 is 10 and T2 is 6 the number of seconds to bill will be 10 + 4*6 = 34 seconds.
* Default customer billing: if checked all customer prices who are not assigned in "customer assignment" will be billed based on this billing table


After creating billing table you need to add billing rules: (you can export / import them via CSV)  
* Name: Billing table name.
* State holidays: Assign holidays table for peak/offpeak.
* Default price: Per-minute (offpeak if peak/offpeak enabled).
* Enable peak/offpeak: For time-based billing.
* Default price peak: Peak per-minute.
* Default T1: First impulse seconds.
* Default T2: Period length (e.g., 30s call, T1=10, T2=6: Bill 10 + 4*6 = 34s).
* Default customer billing: Applies to unassigned customers.


* name: of the billing rule
Add billing rules (CSV export/import):
* prefix number: rule will match based on the same prefix 
* fixed number:  rule will match based on the same exact number
* price: price for the destination (offpeak if peak/offpeak enabled)
* price peak: price for the destination in peak period (if peak/offpeak enabled)
* override default peak offpeak: change the default peak/offpeak
* t1: set custom T1 timer
* t2: set custom T2 timer


== state holidays ==
* Name: Rule name.
* Prefix number: Match prefix.
* Fixed number: Match exact.
* Price: Destination (offpeak if enabled).
* Price peak: Peak destination.
* Override default peak/offpeak: Custom times.
* T1: Custom first impulse.
* T2: Custom period.


Table of state holidays which you can assign in billing table. Those days will be treated as offpeak. You need to define this only in case your billing are based on peak/offpeak.
=== State Holidays ===


== operator assignment ==
Holidays table for offpeak treatment. Define only for peak/offpeak billing.


To be able to bill CDR based on to what operator call is going through you need to create rule for each of operator and select billing table. If you create and assign the table customer price will be not calculated if call is coming from operator. This way the system knows that it should bill only outgoing calls. If you would like to have customer and operator price in CDR you need to create at least two billing tables and the customer one set as "default customer billing" and assign the operator billing table in this section to the operator IPs.
=== Operator Assignment ===


== customer assignment ==
Rules per operator with billing table. Excludes customer price for operator calls (bills outgoing only). For both prices: One default customer table, assign operator tables here.


If you need to bill some customers differently so the default customer billing table is not enough you can create rules to apply different billing tables to customers based on their source IP or source Tel. numbers. (prefixes or fixed numbers)  
Override international prefixes per operator (see [[#settings]]).


== exclude ==
=== Customer Assignment ===


If you do not want to bill CDR for some IP or numbers you can set rules for them here. Rules allows to choose for what source or destination IP should be excluded as well as for source or destination tel. prefixes / numbers.  
Apply different tables to customers by src IP or tel. numbers/prefixes if default insufficient.


== aggregation ==
Override international prefixes per customer (see [[#settings]]).


Aggregation feature summarize called sum based on ip source or tel. number source for hours days weeks months. This aggregation is used in fraud/alerts in billing over quota rules.
=== Exclude ===


=== settings ===
Rules to exclude billing by src/dst IP or tel. prefixes/numbers.


* enable by addresses: aggregates per source IP address
=== Aggregation ===
* enable by numbers: aggregates per tel. number
* week start
* hours / days / weeks / months / years: set how long should be various date ranges kept in the database.


=== exclude addresses ===
Summarizes costs by src IP/tel. number for hour/day/week/month/year. Used in fraud/alerts for quota rules.
* which IP addresses (src or dst) should be excluded from aggregation. This is usefull to not aggregate operator source IP or your SIP proxy source IP so the aggregation data will have only customers data.  


=== exclude numbers ===
==== Settings ====
* which numbers (src or dst) should be excluded from aggregation. It is always good to set addresses first like your operator sip source ip addresses so your database will be not filled with data you do not want to use.


== currency ==
* Enable by addresses: Per src IP.
* Enable by numbers: Per tel. number.
* Week start.
* Hours/days/weeks/months/years: Retention periods.


You do not need to create currency if you have only one. If you will have more currencies the GUI will recalculate it to the base currency which is set as "Main currency"
==== Exclude Addresses ====


* Code: USD for example
Exclude src/dst IPs (e.g., operators/SIP proxies) for customer-only data.
* Custom code: symbol "$" for example 
* Name: name of the currency
* Country: Select the country
* Main currency: if selected all currencies in CDR view and charts etc. are recalculated to this currency
* Description


= Watchdog =  
==== Exclude Numbers ====


In alerts / anti fraud there is two billing watchdog rules. You have to enable aggregation in billing settings.  
Exclude src/dst numbers. Prioritize addresses to avoid unnecessary data.


=== Currency ===


== Billing over quota ==
Optional for single currency. Multiple: Recalculates to main via Google rates (view-only, not stored).


Billing over quota is checking total billed sum per source IP or souce Tel. number or grouped source IPs / numbers for hour / day / week and month aggregation periods. The purpose of this rule is possibility to be alerted globally or individually if there is any account which has billed sum higher then set threshold during the last hour day etc.  
* Code: e.g., USD.
* Enabled: enable/disable rle* Every N minutes: how often to check the rule* Enable hyperlinks: create hyperlink in email alert to quickly go to the rule * hour / day / week / month: set maximum amount of calling costs to trigger the alert. * summary: if enabled all included caller numbers / ip addresses are summarized and then evaluated instead of taking each IP/tel.num separatly. This is for case where you want to group all customers numbers or ip addresses. * Include / Exclude IP addresses / numbers: allow to filter only calls you want to get the alert. If you do not specify any include/exclude rules the rule will trigger for every IP / tel. number individually.
* Custom code: Symbol, e.g., "$".
== Billing high rate ==
* Name: Currency name.
* Country: Select.
* Main currency: Recalculate all to this.
* Description.


=== Settings ===


The second watchdog rule is to trigger alert if calling to destination with higher cost per minute then set threshold. For example you want to know if someone is calling to destination 0.5USD / minute.  
* International prefixes: Distinguish local/international (default: 00, +).
* Enabled: enable/disable rle* Every N minutes: how often to check the rule* Enable hyperlinks: create hyperlink in email alert to quickly go to the rule * Limit: set the cost / minute which will trigger this alert* Include / Exclude IP addresses / numbers: allow to filter only calls you want to get the alert. If you do not specify any include/exclude rules the rule will trigger for every IP / tel. number individually.
* Min. international length: Treat longer numbers as international if no prefix.
* Local numbers are in: Prefix local numbers with international code for selected country.
 
== Watchdog ==
 
In Alerts/Anti Fraud: Two rules requiring aggregation enabled.
 
=== Billing Over Quota ===
 
Checks billed sums per src IP/tel. number or groups for periods. Alerts on thresholds.
 
* Enabled: On/off.
* Every N minutes: Check frequency.
* Enable hyperlinks: Links in emails.
* Hour/day/week/month: Max costs.
* Summary: Aggregate included callers/IPs.
* Include/Exclude IP/numbers: Filter calls. None: Per individual IP/number.
 
=== Billing High Rate ===
 
Alerts on destinations > cost/minute threshold.
 
* Enabled: On/off.
* Every N minutes: Check frequency.
* Enable hyperlinks: Links in emails.
* Limit: Cost/minute threshold.
* Include/Exclude IP/numbers: Filter calls. None: Per individual IP/number.
 
=== AI Summary for RAG ===
 
'''Summary:''' This article overviews VoIPmonitor's billing features: Price types, tables, watchdog rules for quotas/expensive destinations; configuration sections for types/rules, holidays, assignments, excludes, aggregation, currency, settings; and watchdog details.
 
'''Keywords:''' billing, customer price, operator price, billing tables, peak/offpeak, currency, watchdog, quota, high rate
 
'''Key Questions:'''
* What are the key billing features in VoIPmonitor?
* How to create and configure billing tables/rules?
* What is state holidays for in billing?
* How to exclude calls from billing?
* How to handle multiple currencies?
* What are international prefix settings?
* How do billing watchdog rules function?

Latest revision as of 14:38, 10 November 2025

Billing Feature Overview

  • Two price types in CDR: Customer and operator (for comparing operators).
  • Multiple billing tables: For each operator and customer.
  • Billing watchdog rules: Quotas per hour/day/week/month aggregated by src IP or tel. number.
  • Billing watchdog rules: For expensive destinations.

Settings > Billing Configuration

Sections: Billing type/rules, state holidays, operator assignment, customer assignment, exclude, aggregation, currency, settings.

Billing Type / Rules

Create at least one billing table for customer/operator prices. For operator-only, create per operator and assign in "operator assignment" without "Default customer billing".

  • Name: Billing table name.
  • State holidays: Assign holidays table for peak/offpeak.
  • Default price: Per-minute (offpeak if peak/offpeak enabled).
  • Enable peak/offpeak: For time-based billing.
  • Default price peak: Peak per-minute.
  • Default T1: First impulse seconds.
  • Default T2: Period length (e.g., 30s call, T1=10, T2=6: Bill 10 + 4*6 = 34s).
  • Default customer billing: Applies to unassigned customers.

Add billing rules (CSV export/import):

  • Name: Rule name.
  • Prefix number: Match prefix.
  • Fixed number: Match exact.
  • Price: Destination (offpeak if enabled).
  • Price peak: Peak destination.
  • Override default peak/offpeak: Custom times.
  • T1: Custom first impulse.
  • T2: Custom period.

State Holidays

Holidays table for offpeak treatment. Define only for peak/offpeak billing.

Operator Assignment

Rules per operator with billing table. Excludes customer price for operator calls (bills outgoing only). For both prices: One default customer table, assign operator tables here.

Override international prefixes per operator (see #settings).

Customer Assignment

Apply different tables to customers by src IP or tel. numbers/prefixes if default insufficient.

Override international prefixes per customer (see #settings).

Exclude

Rules to exclude billing by src/dst IP or tel. prefixes/numbers.

Aggregation

Summarizes costs by src IP/tel. number for hour/day/week/month/year. Used in fraud/alerts for quota rules.

Settings

  • Enable by addresses: Per src IP.
  • Enable by numbers: Per tel. number.
  • Week start.
  • Hours/days/weeks/months/years: Retention periods.

Exclude Addresses

Exclude src/dst IPs (e.g., operators/SIP proxies) for customer-only data.

Exclude Numbers

Exclude src/dst numbers. Prioritize addresses to avoid unnecessary data.

Currency

Optional for single currency. Multiple: Recalculates to main via Google rates (view-only, not stored).

  • Code: e.g., USD.
  • Custom code: Symbol, e.g., "$".
  • Name: Currency name.
  • Country: Select.
  • Main currency: Recalculate all to this.
  • Description.

Settings

  • International prefixes: Distinguish local/international (default: 00, +).
  • Min. international length: Treat longer numbers as international if no prefix.
  • Local numbers are in: Prefix local numbers with international code for selected country.

Watchdog

In Alerts/Anti Fraud: Two rules requiring aggregation enabled.

Billing Over Quota

Checks billed sums per src IP/tel. number or groups for periods. Alerts on thresholds.

  • Enabled: On/off.
  • Every N minutes: Check frequency.
  • Enable hyperlinks: Links in emails.
  • Hour/day/week/month: Max costs.
  • Summary: Aggregate included callers/IPs.
  • Include/Exclude IP/numbers: Filter calls. None: Per individual IP/number.

Billing High Rate

Alerts on destinations > cost/minute threshold.

  • Enabled: On/off.
  • Every N minutes: Check frequency.
  • Enable hyperlinks: Links in emails.
  • Limit: Cost/minute threshold.
  • Include/Exclude IP/numbers: Filter calls. None: Per individual IP/number.

AI Summary for RAG

Summary: This article overviews VoIPmonitor's billing features: Price types, tables, watchdog rules for quotas/expensive destinations; configuration sections for types/rules, holidays, assignments, excludes, aggregation, currency, settings; and watchdog details.

Keywords: billing, customer price, operator price, billing tables, peak/offpeak, currency, watchdog, quota, high rate

Key Questions:

  • What are the key billing features in VoIPmonitor?
  • How to create and configure billing tables/rules?
  • What is state holidays for in billing?
  • How to exclude calls from billing?
  • How to handle multiple currencies?
  • What are international prefix settings?
  • How do billing watchdog rules function?
Retrieved from "https://www.voipmonitor.org/doc/index.php?title=Billing&oldid=5740"