As for as I know, FreeSWITCH maintains its own clock. When you start freeswitch for the first time, it takes the system time and from there on, it uses its own clock to update the time. So After starting freeswitch, if you change the system time, then freeswitch time and system time will be different. You can sync the system time by using "fsctl sync_clock". Check whether the 9 seconds it due to this behaviour.... On Wed, Aug 31, 2011 at 7:26 PM, Glaucio Vaz de Mello <gvmello@yx.cl> wrote:
Hello,
I noticed a difference between FreeSWITCH time and system clock time. Is this a standard behaviour? or something is wrong in my system?
More details of the issue: Inside FreeSWITCH I look for current epoch time using this function: time_t now = switch_epoch_time_now(NULL);
Then I look for system clock current time using: #include <time.h> time_t now = time(NULL);
Between both results I noticed a difference of 9 seconds.
This can also be viewed using Unix commands.
Unix date command from console: # date +%s 1314741992
Then, I start a call and make a DB query: # sqlite3 /var/freeswitch/db/core.db "SELECT call_created_epoch FROM calls;" 1314742000
Then I repeat unix date command: # date +%s 1314741994
Any comments are welcome. Regards, Glaucio
_______________________________________________ Join us at ClueCon 2011, Aug 9-11, Chicago http://www.cluecon.com 877-7-4ACLUE
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org