That was exactly what I was lamenting - that some common distros do not send
every event, so that AMI ends up being less than reliable. If AMi sends all
events, then it's really trivial to track calls :)
l.
2010/8/9 Motiejus Jakštys <desired....@gmail.com>
> On Mon, Aug 9, 2010 at 12:08 PM, Lenz Emilitri <lenz.lo...@gmail.com>
> wrote:
> > BTW, using the most common Asterisk distros out there that happen to
> sport a
> > very complex dialplan, we see a lot of lost events, so that tracking
> calls
> > on the basis of AMI observation alone becomes practically impossible.....
> > :-(
> > l.
>
> You can filter AMI. If you know PERL, you can start with my script
> that works with callbacks:
>
> $callbacks{'Newstate'} = \&newstate_callback;
> $callbacks{'Dial'} = \&dial_callback;
>
> And create appropriate functions for storing desired values to the
> database. We catch Dial, Answer, Ringing, Hangup events and store that
> info to database with very accurate timestamps :-)
>
> http://github.com/Motiejus/Asterisk-perl-AMI/blob/master/asterisk_ami.pl
>
> Regards,
> Motiejus Jakštys
>
--
Loway - home of QueueMetrics - http://queuemetrics.com
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
