Apologies Reza,

the distinction between logger and cdr escaped me in my helpful enthusiasm! :-)

However, while I'm not suggesting that those are great CDR tools, I thought you might be able to adapt the flatfile -> SQL scripts to your advantage. The process would be identical to CDR, just a different schema. IIRC they are not very complex and could be adapted to suit your needs.

regards,

Drew


Reza - Asterisk Consultant wrote:
Hello Drew:

Please refer back to my original post. The logs generated from logger.conf file is what I am referring to. Not CDRs.

Asterisk-Stat in our case has proved to be hopeless considering what we are doing.

We custom develop all logging and analysis tools for our internal use. We have what we want... but now we want it REAL TIME. Once again, please note - my query is specifically with regards to log files generated from logger.conf, nothing to do with CDRs.

Kind regards,
Reza.


On Tue, Feb 9, 2010 at 8:42 AM, Drew Gibson <[email protected] <mailto:[email protected]>> wrote:

    Hi Reza,

    these two utilities have scripts and howtos to do just that
    (assuming you can live with their db schema)...

    Asterisk-Stat
    
<http://areski.net/areski/index.php?option=com_content&task=view&id=22&Itemid=54
    
<http://areski.net/areski/index.php?option=com_content&task=view&id=22&Itemid=54>>

    Asterisk Queue/CDR Analyzer
    <http://www.micpc.com/qloganalyzer/>

    IIRC the Queue Analyzer has a script to import all your backlog of
    CDR data.

    regards,

    Drew


    Reza - Asterisk Consultant wrote:

        I have an urgent need to parse log files generated through the
        logger.conf
        into mysql.    I run a cron job to parse the logs created into
        mysql every
        5:00 AM.  However the time has come to get this info real
        time.  Suggestions
        &  ideas are appreciated.

        Thanks and regards,
        Reza.





--
Toronto based VoIP / Asterisk Trainer,
I.T. Consultant and Hosted PBX Solutions Provider.
+1-647-476-2067.
http://www.linkedin.com/in/seminar

Reply via email to