This could happen when using system time and changing the time after startup. It's one of the reasons we don't use system time by default. Similar issues happen with dst when using system time, and it can break accurate cdr details when time changes happen
Sent from my iPadI did not knew FreeSWITCH is that old but looks interesting .. on an old version where enable-use-system-time is enabled for some testing.freeswitch@internal> statusUP 93 years, 92 days, 0 hours, 46 minutes, 41 seconds, 34 milliseconds, 220 microsecondsFreeSWITCH (Version 1.4.26 64bit) is ready0 session(s) since startup0 session(s) - peak 0, last 5min 00 session(s) per Sec out of max 30, peak 0, last 5min 01000 session(s) maxmin idle cpu 0.00/97.93Current Stack Size/Max 240K/8192K
--
Sent with Airmail__________________________________________________________________________________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org