On Mon, Apr 18, 2011 at 8:18 AM, A J Stiles <[email protected]>wrote:
> If all the details you need to compile your reports can be found in > existing > databases (Asterisk's CDR database stores the details of calls; you may > need > to get user login/out events from a separate database), Logging the queue_log to MySQL and then setting up a trigger that inserts/updates data to other tables (such as something like agent_status and call_status), along with the CDR, will allow the OP to get pretty much everything they want. (*OP, if you need something substantially more than the stats I mentioned in my earlier post, definitely feel free to email me with details. That way, not only can I help you, but I can make the open source statistics solution I'm working on even better)* > A hint: Do the whole thing -- or as much of it as it takes to prove to > yourself that you're on the right track -- "by hand" first, entering all > the > queries yourself in the mysql prompt (or phpmyadmin), *before* you try to > write a program to do it. You will save yourself much heartache that way. > > AJ, truer words have not been oft spoken! I'd also add that creating views helps if you have complex queries (just to shorten the query that has to be issued from the end program that gets written).
-- _____________________________________________________________________ -- 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
