-
...><div class="content"><font class="modules-title">[[Modules#Billing Module|Billing Module]]</font></div>
8 KB (1,086 words) - 09:08, 31 July 2018
-
* ''billing'' (default false) emits messages needed to bill conference participants
$m->params["billing"] = "true";
6 KB (936 words) - 10:35, 4 November 2013
-
...egory:Subscribe]] [[Category:Call counters]] [[Category:Users]] [[Category:Billing]]
14 KB (2,155 words) - 10:47, 11 January 2014
-
;billid : will hold the billing ID
2 KB (321 words) - 10:37, 21 January 2013
-
...me tips you can use when writing call logs. You use this modules to obtain billing information.
9 KB (1,376 words) - 10:01, 27 October 2017
-
==Billing Modules==
Billing in a database
12 KB (1,662 words) - 13:25, 1 October 2019
-
...dule adds support for RADIUS in Yate to bill calls using well known RADIUS billing mechanism.
The h323-conf-id is the billing id used by YATE.
7 KB (947 words) - 10:30, 4 November 2013
-
:*'''billid'''=true ( will hold the billing ID. Billid is created from stitching the value of runid with the value cdri
10 KB (1,558 words) - 13:22, 13 January 2014
-
* ${billid} - billing record id
==== Set CDR billing====
6 KB (754 words) - 13:14, 11 January 2014
-
...k when a particular set of records has been either billed, or exported for billing.
7 KB (1,094 words) - 12:55, 11 January 2014
-
;billing
...lse) set to true to generate "chan.startup" and "chan.hangup" messages for billing purposes
2 KB (300 words) - 20:57, 15 February 2014
-
: billing ID of the incoming call that triggered the resource location request
746 B (116 words) - 15:23, 21 January 2013
-
^800$ = conf/sampleroom;lonely=true;billing=true;maxusers=200
$m->params["billing"] = "true";
3 KB (468 words) - 09:42, 20 May 2013
-
===Billing from database===
There are two types of billing:
5 KB (887 words) - 14:05, 31 October 2013
