[asterisk-users] Time difference in CSV CDR's and MySQL CDR's

Zhang Shukun bitzsk at gmail.com
Thu Apr 22 01:06:04 CDT 2010


the time in the file cdr is right, as mysql. calldate is the time when
the record insert into mysql.

2010/4/22 Alejandro Recarey <alexrecarey at gmail.com>:
> Hi all,
>
> I am having a curious problem. I use two cdr backends, csv and MySQL.
> These are my settings:
>
> Call Detail Record (CDR) settings
> ----------------------------------
>  Logging:                    Enabled
>  Mode:                       Batch
>  Log unanswered calls:       Yes
>
> * Batch Mode Settings
>  -------------------
>  Safe shutdown:              Enabled
>  Threading model:            Scheduler plus separate threads
>  Current batch size:         0 records
>  Maximum batch size:         25 records
>  Maximum batch time:         10 seconds
>  Next batch processing time: 7 seconds
>
> * Registered Backends
>  -------------------
>    csv
>    mysql
>    cdr-custom
>
>
> I am finding that the calldate field varies between 3 seconds and 3
> minutes between the MySQL database and the CSV files! Is this expected
> behaviour? I thought they should both use the same timestamp. Is is
> very difficult to match CDR's this way, and I am finding it hard to
> trust the results, as I wanted to make sure that my database was
> behaving correctly and not "losing" any CDR's along the way.
>
> Which one of the two CDR's is correct?
>
> Should this be posted as a bug?
>
> Regards,
>
> Alex
>
> --
> _____________________________________________________________________
> -- 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
>



-- 
Best regards,
Sucan



More information about the asterisk-users mailing list