Hello folks,
my company has experience in setting up single asterisk setup, but
recently one of our customers asked us to set up an asterisk cluster,
that must be High Availability and Load Balanced.
So I wrote here to have some hint or advice about the configuration we thought.
First of
Compile without SRTP support
Hint: ./configure --without-srtp
~
Andrew lathama Latham
lath...@gmail.com
* Learn more about OSS http://en.wikipedia.org/wiki/Open-source_software
* Learn more about Linux http://en.wikipedia.org/wiki/Linux
* Learn more about Tux http://en.wikipedia.org/wiki/Tux
Tarek,
I already tested this feature with a2billing.
This is difficult to extract the working code from a2billing.
Also we are developing billing system so this is not a good idea
to deploy another billing system in parallel.
Any idea or link might help full.
On Fri, Sep 24, 2010 at 9:30
if you are deploying your own system.. then you can build a small application
(AGI) that would do the math for you .. will devide the call duration into the
stages you want .. and does the calculation.. i think MYSQL already can do
that.. but a PHP script will do it faster and easier.. or like
Yes. you are right. I was thinking to avoid reinventing the wheel.
Will write AGIs. Trick is how to charge at 3min 59 sec or 4 min 01 sec
during live call.
We can monitor channel variables over AMI. But this will be a CPU overhead
(say for 100 or 200 calls) if we monitor channel variables on
the way i see it can be done.. is using ${CDR(billsec)} into a dial plan or
your AGI, A2billing is a script that runs and waits till the call ends then
exists with status 0. it doesn't listen to AMI (as i expect) it pulls the
variables after the channel is hungup and then does the calculation
(Caution-top posting. Delete Before Reading if that's a problem for you.)
As I see it, real-time billing is only necessary if you have multiple people
making simultaneous calls against a prepaid balance or limited credit limit.
In other situations, you can simply make a determination at
