[asterisk-users] Billing/Call Control engine : AGI scripts/ AstMan API
moises.silva at gmail.com
Wed Nov 28 09:09:09 CST 2007
I have found out that executing AGI thru the AMI interface fill better
my needs of control. Take a look
Ignore the bug description and read the first note entry, that might
be a better way to get things done.
On Nov 27, 2007 10:27 PM, Benjamin Jacob <benjamin.jacob at mgl.com> wrote:
> Hello ppl,
> Have implemented a really nice Billing engine using AGI scripts. So far
> it works fine, tho haven't yet put it in the torture cell.
> The AGI scripts have been written in PHP, using MySQL for the billing
> and profile information.
> The major disadvantages I see using AGI scripts :
> 1. A new process(invocation of PHP scripts) on every new call.
> 2. MySQL connections on every instance of the PHP AGI script. (I am not
> too sure, if connections can be maintained across processes, am no PHP
> guru. I think, if I write in C/C++ can use shared memory for maintaining
> the connection).
> So, to overcome these issues, I was thinking of using AstMan APIs along
> with astmanproxy, with the setup being something like this :
> Asterisk <---------> astmanproxy <-----------------> Billing
> Has anyone ever tried this?
> The one seriously big work with this approach would be to have an FSM
> built into my billing engine, maintaining call states, etc. That seems
> to be quite a daunting task to be done in a short time.
> Any ideas anyone?or any similar experiences, in terms of performance,
> scalability, etc. w.r.t both AGI scripts and AstMan API?
> - Benjamin Jacob.
> EMAIL DISCLAIMER : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised distribution or copying is strictly prohibited. If you receive this transmission in error, please notify the sender by reply email and then destroy the message. Opinions, conclusions and other information in this message that do not relate to official business of Mascon shall be understood to be neither given nor endorsed by Mascon. Any information contained in this email, when addressed to Mascon clients is subject to the terms and conditions in governing client contract.
> Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we can not guarantee that any email or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. Mascon grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused.
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
"Within C++, there is a much smaller and cleaner language struggling
to get out."
More information about the asterisk-users