[Asterisk-Dev] Callingcard (again, sorry!)

[Luis Mata]

Jeremy :

             I think the questions will ne how big they want to scale 
the system. A lot of people have ask me how to acomplish a well 
redundant asterisk prepaid system. My answer based on experience is that 
you need different servers. People think that just because CPU got 
faster and memory got cheaper they can build this monster to handle 
thouthands of calls... Well software sometimes doesn't do magic. And 
Asterisk is not the eception. So again the quesiton how big you want to 
scale.

       FROM  T1 to VOIP prepaid system. ( One T1 ).
                  If you are doing a calling card platform with a T1 you 
can easily use AGI (any flavor is find ) and mate your box with a RDMS.

       If you need to grow bigger then don't lie to your self and design 
a fully redundant system, well if you have already the database or 
billing platform remotely you can attach multiple asterisk servers to 
query the same db.

        If you have incoming clients from SIP to T1 , then use multiple 
servers and use DNS load balancers. Since you are doing the 
authentication in a centralize DB doesnt matter to what Asterisk server 
your customers land.

         This will be not the best , but one way to do an scalable system..

Just my half a cent....

Jeremy McNamara wrote:

> Apollon Koutlides wrote:
>
>> I'm developing a prepaid platform myself on asterisk (will be in a
>> release-able state soon enough, I hope) and encountered the
>> charge-on-termination dilemma myself. Initially I tried to go for the
>> hangup extension, but ended up using the CDRs which I would have to
>> consult anyway. I am currently checking two different approaches: a) use
>> csv CDRs, open the file in pipe mode, capture new records, charge
>> customer and store charging record to database. b) use postgres CDRs and
>> triggers to implement charging. The second approach has some extra
>> merit, since you can host the charging engine outside the asterisk box.
>> I intend to experiment with the radius application too, at some point in
>> time. I am also using pretty complex tariffs, and have created a daemon
>> to do tariff lookups - this helps a whole lote to improve redundancy and
>> offload the * box.
>
>
>
> Both solutions do not scale.  Trying to process CSV's are completely 
> wrong and triggers are going to be a loosing battle for CPU time as 
> your volume increases.
>
> AGI and/or RADIUS are not the solution either. Use the power of 
> Asterisk, don't side step it.
>
> Jeremy McNamara
>
>
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>