provided by Star2Billing S.L.

There are many times my customer are being charged because the dialing rules in the a2billing can not be easily or properly configured. For instance if I have 1 set as a rate card and one of my customers dials 1502-222 and pushes the #, a2billing will attempt to connect to 1502-222 and charge the caller for that call even though it was an invalid number. If I were charging per minute this would not be much of a problem but since I am charging some customers 45 cents per call this really adds up for those customers. Even for customers paying perminute they will not be happy about being charged for call that didn

Did you find a solution for this?

Hey Samuel,
I am kind of surprise by your post as A2Billing doesnt bill the calls that aren't answered.
Rgds, Areski

Yes and No,, Some VOIP resellers don

HI Areski

If I am not mistaking when I send a call to my Voip provider using A2billing I believe A2billing bills for that call unless i get something back from my Voip provider stating that call was not connected. Some very cheap Voip providers who use several other VOIP providers because of least cost call routing, sometimes don

what a long post

Well the thing is that the lenght of phonenumber is variable from a country to an other.
Any ideas what are min and max....

Rgds, Areski

Areski,

I've encountered this on other platforms, and I'll tell you what their solution is. They have in their rates - 2 extra fields ... min digits, max digits. Some countries have fixed digits such as USA, others have different digit lengths depending on location. The application I'm very familiar with takes a quick look after the first 6 digits (no international number less than 6) - to hopefully find the proper rate record. This will allow it to know the min/max digits and if it finds for example that the first 6 matches prefix of destination with min=7 max=8, then after 8 digits, it gets it and goes .... doesn't need to wait for # or timeout. I know that might be a pain in the butt to program that way, just is how I know another app manages it. I'd think alternatively - just have the min max check after the # or timeout ... that should be a relatively easy implementation.

Oh - and of course, those who don't want to fill that info in (most don't) - just default min to the min possible (7 I think) and max to like 15.

This happen sometimes, I wish a new feature for the billing, and it is free billing, like first 5 secs are free for customers, if the call is ok and get connected after 5 secs then it will be billed normally.

Hi, Doolph

The function is there, please check a2billing.conf on below:

; this is the minimum duration in seconds of a call in order to be billed
; any call with a length less than min_duration_2bill will have a 0 cost
; useful not to charge callers for system errors when a call was answered but it actually didn't connect
min_duration_2bill=0

oops yeah i was blind lol