In a2billing terms items 2 and 3 are "init block" and "billing block", i.e. minimum call duration to bill and billing increment after "init block" seconds (in your case you want billing block to be 1 second). Sure these essential billing features are missed in mod_nibblebill. Here are 4 "must have" billing parameters for mod_nibblebill: 1. Connection fee 2. sell rate 3. init block 4. billing increment If call duration is less than "init block" seconds, then call should be charged for "init block" seconds, otherwise for actual call length taking into account "billing increment" value. On Friday 26 March 2010, Jean-Yves F. Barbier wrote:

Le Fri, 26 Mar 2010 17:29:57 -0500, Anthony Minessale <anthony.minessale@gmail.com> a écrit :

Ok, thanks, I read the mod_nibblebill page and What I'd like to ask is to have some more features:

* Connection fee

* Time-credit (from french term "crédit-temps", means when you make a call you're first invoiced a minimum of X seconds - sometimes along a connection fee:(

* A per second invoicing instead of per minute, but without a DB call every second, just one call at hangup.

...

you can post ideas here for discussion. if you want something specific you can open a jira incident at http://jira.freeswitch.org under "improvement" category.

Le Fri, 26 Mar 2010 19:55:11 -0400, Sergey Okhapkin <sos@sokhapkin.dyndns.org> a écrit :

Here is lua code I use instead of mod_nibblebill:

if(ANSWEREDTIME<=initblock) then CHARGETIME=initblock else incrs=math.floor((ANSWEREDTIME- initblock+billingblock-1)/billingblock); CHARGETIME=initblock+incrs*billingblock; end sessionbill=(CHARGETIME*calledrate)/60 + connfee;

I realise 2 things: 1- FS is even more powerful than all I read about it, 2- It's gonna take me "some" time to fully understand it... -- Dogs just don't seem to be able to tell the difference between important people and the rest of us.

I used asterisk for years (and still use it for voice mail and access numbers and call back), but switched regular outgoing calls to FS. And I don't want to look back at asterisk. * doesn't have the flexibility FS offers and I need. On Friday 26 March 2010, Jean-Yves F. Barbier wrote:

Le Fri, 26 Mar 2010 19:55:11 -0400,

Sergey Okhapkin <sos@sokhapkin.dyndns.org> a écrit :

...

Here is lua code I use instead of mod_nibblebill:

if(ANSWEREDTIME<=initblock) then CHARGETIME=initblock else incrs=math.floor((ANSWEREDTIME- initblock+billingblock-1)/billingblock); CHARGETIME=initblock+incrs*billingblock; end sessionbill=(CHARGETIME*calledrate)/60 + connfee;

I realise 2 things: 1- FS is even more powerful than all I read about it, 2- It's gonna take me "some" time to fully understand it...

sell_rate you can get as a user_rate from mod_lcr or do your own separate query if you don't want lcr info too. billing increment, I've seen a patch that implements this. I was gonna port that forward to current rev. If Darren or someone else doesn't get it first I'll get to it eventually. init_block - would implement at same time as billing_increment. connection_fee - again, like init_block. In fact, you *could* get all the values you need via the version of mod_lcr that is sitting locally since you can query/set arbitrary channel vars via custom sql. You can decide how these fields relate to your lcr tables (they may not, it is up to you based on the sql you craft). You also mentioned you don't want to bill in real-time but only at end of call. This you can do today by turning off the heartbeat. I think this is already discussed on the wiki. As always, a bounty goes a long way. One of the devs might jump on it sooner if there is money in it. I'm swamped for the next week at least so... won't have a chance to even look at this until then. Not to mention I want to finish cleaning up my limit stuff. On Fri, Mar 26, 2010 at 6:12 PM, Jean-Yves F. Barbier <12ukwn@gmail.com>wrote:

Le Fri, 26 Mar 2010 17:29:57 -0500, Anthony Minessale <anthony.minessale@gmail.com> a écrit :

Ok, thanks, I read the mod_nibblebill page and What I'd like to ask is to have some more features:

* Connection fee

* Time-credit (from french term "crédit-temps", means when you make a call you're first invoiced a minimum of X seconds - sometimes along a connection fee:(

* A per second invoicing instead of per minute, but without a DB call every second, just one call at hangup.

...

you can post ideas here for discussion. if you want something specific you can open a jira incident at http://jira.freeswitch.org under "improvement" category.

-- Conscious is when you are aware of something and conscience is when you wish you weren't.

_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

-- -Rupa

You can see an (older) version of my work-in-progress along with some discussion of how it works at: http://jira.freeswitch.org/browse/MODAPP-340 <http://jira.freeswitch.org/browse/MODAPP-340>I haven't updated the patch since the version in my tree also depends on my limit work. But the discussion should give you a better idea of how this will work. On Fri, Mar 26, 2010 at 7:13 PM, Sergey Okhapkin <sos@sokhapkin.dyndns.org>wrote:

Could you give more info about "since you can query/set arbitrary channel vars via custom sql"? How can I set a channel variable using mod_lcr with custom sql query?

On Friday 26 March 2010, Rupa Schomaker wrote:

...

sell_rate you can get as a user_rate from mod_lcr or do your own separate query if you don't want lcr info too.

billing increment, I've seen a patch that implements this. I was gonna port that forward to current rev. If Darren or someone else doesn't get it first I'll get to it eventually.

init_block - would implement at same time as billing_increment.

connection_fee - again, like init_block.

In fact, you *could* get all the values you need via the version of mod_lcr that is sitting locally since you can query/set arbitrary channel vars via custom sql. You can decide how these fields relate to your lcr tables (they may not, it is up to you based on the sql you craft).

You also mentioned you don't want to bill in real-time but only at end of call. This you can do today by turning off the heartbeat. I think this is already discussed on the wiki.

As always, a bounty goes a long way. One of the devs might jump on it sooner if there is money in it. I'm swamped for the next week at least so... won't have a chance to even look at this until then. Not to mention I want to finish cleaning up my limit stuff.

On Fri, Mar 26, 2010 at 6:12 PM, Jean-Yves F. Barbier <12ukwn@gmail.com>wrote:

...

Le Fri, 26 Mar 2010 17:29:57 -0500, Anthony Minessale <anthony.minessale@gmail.com> a écrit :

Ok, thanks, I read the mod_nibblebill page and What I'd like to ask is to have some more features:

* Connection fee

* Time-credit (from french term "crédit-temps", means when you make a call you're first invoiced a minimum of X seconds - sometimes along a connection fee:(

* A per second invoicing instead of per minute, but without a DB call every second, just one call at hangup.

...

you can post ideas here for discussion. if you want something specific you can open a jira incident at http://jira.freeswitch.org under "improvement" category.

-- Conscious is when you are aware of something and conscience is when you wish you weren't.

_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

-- -Rupa