<div>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..... :-(</div>
<div>l.</div><div><br></div><div><br></div><div> <br></div><div><br></div><div class="gmail_quote">2010/8/8 Nasir Iqbal <span dir="ltr"><<a href="mailto:nasir@ictinnovations.com">nasir@ictinnovations.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<div><br></div><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">Confusing!</span> you are not alone here. Actually there is no unified development approach exist in Asterisk, every module, application introduce a new way to handle same things!! And the "monitoring" is most difficult part! you have to write different parsing algos to get each bit of information, and unfortunately you have to rewrite most of your code for every new release!</div>
<div><br></div><div>And regarding your question, I recommend you to use AGI for monitoring here is some tips for you</div><div><ul><li>in originate command use extension as destination.</li><li>create "failed" extension in same context.</li>
<li>you can include some variables in originate command which can be used later in dialplan.</li><li>use AGI scripts in "destination" and "failed" extensions to get and save call status in database.</li>
</ul>Regards</div></blockquote></div><br clear="all"><br>-- <br>Loway - home of QueueMetrics - <a href="http://queuemetrics.com">http://queuemetrics.com</a><br><br>