[Asterisk-Users] Billing

[trixter http://www.0xdecafbad.com]

Just a note on scaling astcc, you can have a database with server
replication, so that it scales well, and doesnt subtract from the cpu
power of the asterisk boxes.  This is regardless of medium for the voice
calls.

If you then distribute the load across multiple asterisk boxes you build
in a system that is more fault tolerant and can scale better.

While I havent looked specifically at astcc it would need to ensure that
concurrent calls from the same account dont end up going over available
minutes if prepaid.  This can be accomplished by locking rows in the
database, pulling a certain amount of minutes from the database (perhaps
into a temp table incase something breaks) etc.  Then at regular
intervals pull more minutes or drop the call if none are present.  I
dont know how astcc deals with this particular issue.

A scalable solution with redundancy could be implemented with astcc
based on an overview of what it is.  The fact that you have a realtime
database for queries on calls could mean that you can have a easier time
with a web interface than batch processing radius accounting logs later.
It would also offer a prepaid solution, which would be almost impossible
with radius alone.



On Tue, 2005-04-19 at 09:16 -0700, Sathya Weerasooriya wrote:
> Maxim, based on the info in the URL below, you claim to say that completely
> asterisk based solution for calling card application may not scale. You
> suggest that the alternative is to use gnugk just to use its AAA, or Radius.
> In my opinion and experience, I would say by introducing Gnugk and OH323,
> you take more horsepower out of the Server that you are running the "calling
> card application".
> I believe you can do lot better even with an application like ASTCC. Better
> mean you will be able to handle more calls in the same box. I think one of
> the best ways to handle large call volume is to make sure that asterisk do
> the minimum and essential work and build your network around it.  If you can
> set up asterisk to Answer SIP calls, Authenticate the user based on mysql
> database and then route, again using SIP with codec pass through, that will
> be the most minimum and efficient way to use asterisk. This kind of setup
> with a powerful processor based box, can easily handle 100 + concurrent
> calls with millions of minutes. Then you face the situation where, your most
> terminating parties are h.323. At this point is where a Cisco 2600XM come in
> handy. Also, now you want all front end work to be done via web interface,
> which would give customers real time account recharge, cdr etc. For that you
> could have a backup mysql with replication. Your website would be talking to
> this replicated server for real time data. I think this kind of a solution
> can compete with most medium to large calling card systems out there.
> 
> Cheers
> 
> Sathya
> 
> 

-- 
Trixter http://www.0xdecafbad.com
UK +44 870 340 4605   Germany +49 801 777 555 3402
US +1 360 207 0479 or +1 516 687 5200
FreeWorldDialup: 635378
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050419/78b12485/attachment.pgp