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.
2010/8/8 Nasir Iqbal <na...@ictinnovations.com> > Hi, > > Confusing! 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! > > And regarding your question, I recommend you to use AGI for monitoring here > is some tips for you > > - in originate command use extension as destination. > - create "failed" extension in same context. > - you can include some variables in originate command which can be used > later in dialplan. > - use AGI scripts in "destination" and "failed" extensions to get and > save call status in database. > > Regards > -- 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
