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 iPad
On Aug 5, 2016, at 7:25 AM, Muhammad Naseer Bhatti <nbhatti@gmail.com> wrote:
I 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> status UP 93 years, 92 days, 0 hours, 46 minutes, 41 seconds, 34 milliseconds, 220 microseconds FreeSWITCH (Version 1.4.26 64bit) is ready 0 session(s) since startup 0 session(s) - peak 0, last 5min 0 0 session(s) per Sec out of max 30, peak 0, last 5min 0 1000 session(s) max min idle cpu 0.00/97.93 Current 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