<div>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 :)<br></div>
<div>l.</div><div><br></div><br><div class="gmail_quote">2010/8/9 Motiejus Jakštys <span dir="ltr"><<a href="mailto:desired.mta@gmail.com">desired.mta@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Mon, Aug 9, 2010 at 12:08 PM, Lenz Emilitri <<a href="mailto:lenz.loway@gmail.com">lenz.loway@gmail.com</a>> wrote:<br>
> BTW, using the most common Asterisk distros out there that happen to sport a<br>
> very complex dialplan, we see a lot of lost events, so that tracking calls<br>
> on the basis of AMI observation alone becomes practically impossible.....<br>
> :-(<br>
> l.<br>
<br>
</div>You can filter AMI. If you know PERL, you can start with my script<br>
that works with callbacks:<br>
<br>
$callbacks{'Newstate'} = \&newstate_callback;<br>
$callbacks{'Dial'} = \&dial_callback;<br>
<br>
And create appropriate functions for storing desired values to the<br>
database. We catch Dial, Answer, Ringing, Hangup events and store that<br>
info to database with very accurate timestamps :-)<br>
<br>
<a href="http://github.com/Motiejus/Asterisk-perl-AMI/blob/master/asterisk_ami.pl" target="_blank">http://github.com/Motiejus/Asterisk-perl-AMI/blob/master/asterisk_ami.pl</a><br>
<br>
Regards,<br>
Motiejus Jakštys<br>
</blockquote></div><br clear="all"><br>-- <br>Loway - home of QueueMetrics - <a href="http://queuemetrics.com">http://queuemetrics.com</a><br><br>