Now that the SQL driver plugin has been implemented, the path forward should take us onto making the GK write the CDRs into the Database (failing which, CDR to CSV file - not as in trace CDR messages of FileAcct). The GK can also update another temporary table with calls in progress data - to avoid very frequent updation - let a timestamp of last updation be a field in the target table from where any dB client can compute the actual seconds = (time elapsed + current time - lastupdationdatetime). This way we eliminate the need for external monitoring software for CDR capture. Regards, Ap.Muthu ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
