[Freeswitch-dev] Epoch current time difference
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
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
Hi, Thanks for the answer. I made several tests and came to the conclusion that FreeSWITCH clock is always avanced compared to system time. The difference is about 9 seconds per day, just letting FreeSWITCH running, without touching the system clock. Effectively I can sync with system time with "fsctl sync_clock", then the difference comes to zero and start counting again. This can be an issue for billing long duration calls, since the registered call duration will be some seconds more than it really was. If someone need more information, logs or reporting this issue as a bug, just let me know. regards, Glaucio On Tue, Sep 6, 2011 at 1:57 AM, lakshmanan ganapathy <lakindia89@gmail.com>wrote:
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
_______________________________________________ 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
Most likely you are using something like ntp to sync your system clock, if so you should also sync the FS clock when you change the ntp time. FS is keeping it's own time using the monotonic clock in the kernel which is the same mechanism as the system time so your machine probably keeps bad time. On Fri, Sep 9, 2011 at 8:27 AM, Glaucio Vaz de Mello <gvmello@yx.cl> wrote:
Hi,
Thanks for the answer. I made several tests and came to the conclusion that FreeSWITCH clock is always avanced compared to system time. The difference is about 9 seconds per day, just letting FreeSWITCH running, without touching the system clock. Effectively I can sync with system time with "fsctl sync_clock", then the difference comes to zero and start counting again.
This can be an issue for billing long duration calls, since the registered call duration will be some seconds more than it really was. If someone need more information, logs or reporting this issue as a bug, just let me know.
regards, Glaucio
On Tue, Sep 6, 2011 at 1:57 AM, lakshmanan ganapathy <lakindia89@gmail.com> wrote:
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
_______________________________________________ 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
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Yes, that's right. I had ntp enabled. With ntp disabled the problem disappear, FS clock is exactly the same as system clock. Thanks. On Fri, Sep 9, 2011 at 5:19 PM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
Most likely you are using something like ntp to sync your system clock, if so you should also sync the FS clock when you change the ntp time.
FS is keeping it's own time using the monotonic clock in the kernel which is the same mechanism as the system time so your machine probably keeps bad time.
On Fri, Sep 9, 2011 at 8:27 AM, Glaucio Vaz de Mello <gvmello@yx.cl> wrote:
Hi,
Thanks for the answer. I made several tests and came to the conclusion that FreeSWITCH clock is always avanced compared to system time. The difference is about 9 seconds per day, just letting FreeSWITCH running, without touching the system clock. Effectively I can sync with system time with "fsctl sync_clock", then the difference comes to zero and start counting again.
This can be an issue for billing long duration calls, since the registered call duration will be some seconds more than it really was. If someone need more information, logs or reporting this issue as a bug, just let me know.
regards, Glaucio
On Tue, Sep 6, 2011 at 1:57 AM, lakshmanan ganapathy < lakindia89@gmail.com> wrote:
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
_______________________________________________ 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
_______________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ 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
On Mon, Sep 12, 2011 at 7:05 AM, Glaucio Vaz de Mello <gvmello@yx.cl> wrote:
Yes, that's right. I had ntp enabled. With ntp disabled the problem disappear, FS clock is exactly the same as system clock.
I don't know what your environment is like, but if you can get away with keeping NTP running on the server and issue a sync_clock nightly, that might be the best thing. I can think of 3 or 4 other systems that could fail unexpectedly due to time drift like that. At the very least, it makes it so that all of your logs have correct timestamps :) Gabe
-----Original Message----- I don't know what your environment is like, but if you can get away with keeping NTP running on the server and issue a sync_clock nightly, that might be the best thing. I can think of 3 or 4 other systems that could fail unexpectedly due to time drift like that. At the very least, it makes it so that all of your logs have correct timestamps :)
Gabe
Hello, sorry for "hijacking" this thread. Can someone please explain why FS keeps its own time ? As far as I know on vmware machines you can't avoid using NTP if you want to keep your system clock and with automatic daylight changes i've seen a difference of one hour between system time and freeswitch time. :-( Ciao, Claudio Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. -----------------------------------------------------------------------------------------------------
I feel I have explained this many times. Too bad it never makes it to a wiki or faq. Allowing any software to trust the system time is very dangerous. Something that was depending on the system time to calculate a duration etc can be considerably compromised if the time suddenly changes by hours or years in either direction. Things like daylights savings time can break CDR etc. The clock in FS is the onboard monotonic clock and the offset to real time is preserved. If you want FS to sync to system time when desired there are commands to perform this operation. On Wed, Dec 14, 2011 at 10:21 AM, Cavalera Claudio Luigi < Claudio.Cavalera@italtel.it> wrote:
-----Original Message----- I don't know what your environment is like, but if you can get away with keeping NTP running on the server and issue a sync_clock nightly, that might be the best thing. I can think of 3 or 4 other systems that could fail unexpectedly due to time drift like that. At the very least, it makes it so that all of your logs have correct timestamps :)
Gabe
Hello, sorry for "hijacking" this thread. Can someone please explain why FS keeps its own time ? As far as I know on vmware machines you can't avoid using NTP if you want to keep your system clock and with automatic daylight changes i've seen a difference of one hour between system time and freeswitch time. :-(
Ciao, Claudio
Internet Email Confidentiality Footer
----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto.
This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.
-----------------------------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Daylight saving should never modify the time, as for anything like this, one should be using UTC time, or local time with a UTC offset. Any software that computes a duration differently because of DST cannot blame the system: it is very, very, broken. (Although, I'll bet there's more than one company out there with broken CDR software. In fact, I came across such a program and asked the developers about it. They said "not a problem; the system crashes when there's a DST shift, so we never have to deal with those records.") The only reason I can think of for the time values to jump around is if your clock is way out of sync and you force a large NTP jump. But in that case, you're sorta out of luck anyways. -Michael From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Wednesday, December 14, 2011 9:32 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference I feel I have explained this many times. Too bad it never makes it to a wiki or faq. Allowing any software to trust the system time is very dangerous. Something that was depending on the system time to calculate a duration etc can be considerably compromised if the time suddenly changes by hours or years in either direction. Things like daylights savings time can break CDR etc. The clock in FS is the onboard monotonic clock and the offset to real time is preserved. If you want FS to sync to system time when desired there are commands to perform this operation. On Wed, Dec 14, 2011 at 10:21 AM, Cavalera Claudio Luigi <Claudio.Cavalera@italtel.it<mailto:Claudio.Cavalera@italtel.it>> wrote:
-----Original Message----- I don't know what your environment is like, but if you can get away with keeping NTP running on the server and issue a sync_clock nightly, that might be the best thing. I can think of 3 or 4 other systems that could fail unexpectedly due to time drift like that. At the very least, it makes it so that all of your logs have correct timestamps :)
Gabe Hello, sorry for "hijacking" this thread. Can someone please explain why FS keeps its own time ? As far as I know on vmware machines you can't avoid using NTP if you want to keep your system clock and with automatic daylight changes i've seen a difference of one hour between system time and freeswitch time. :-(
Ciao, Claudio Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. ----------------------------------------------------------------------------------------------------- _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto: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 -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com<mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net<http://irc.freenode.net> #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org<mailto:sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
As a caveat, DST being only one example, the other more real reasons include: erroneous commands from sysadmins changing the system time, virtual migrations over VE and many other reasons that went into our decision to lock on to the most accurate time source possible ASAP. On Wed, Dec 14, 2011 at 10:49 AM, Michael Giagnocavo <mgg@giagnocavo.net>wrote:
Daylight saving should never modify the time, as for anything like this, one should be using UTC time, or local time with a UTC offset. Any software that computes a duration differently because of DST cannot blame the system: it is very, very, broken. (Although, I’ll bet there’s more than one company out there with broken CDR software. In fact, I came across such a program and asked the developers about it. They said “not a problem; the system crashes when there’s a DST shift, so we never have to deal with those records.”)****
** **
The only reason I can think of for the time values to jump around is if your clock is way out of sync and you force a large NTP jump. But in that case, you’re sorta out of luck anyways.****
** **
-Michael****
** **
*From:* freeswitch-dev-bounces@lists.freeswitch.org [mailto: freeswitch-dev-bounces@lists.freeswitch.org] *On Behalf Of *Anthony Minessale *Sent:* Wednesday, December 14, 2011 9:32 AM *To:* freeswitch-dev@lists.freeswitch.org *Subject:* Re: [Freeswitch-dev] Epoch current time difference****
** **
I feel I have explained this many times. Too bad it never makes it to a wiki or faq.****
** **
Allowing any software to trust the system time is very dangerous. Something that was depending on the system time to calculate a duration etc can be considerably compromised if the time suddenly changes by hours or years in either direction.****
Things like daylights savings time can break CDR etc.****
** **
The clock in FS is the onboard monotonic clock and the offset to real time is preserved. If you want FS to sync to system time when desired there are commands to perform this operation.****
** **
On Wed, Dec 14, 2011 at 10:21 AM, Cavalera Claudio Luigi < Claudio.Cavalera@italtel.it> wrote:****
-----Original Message----- I don't know what your environment is like, but if you can get away with keeping NTP running on the server and issue a sync_clock nightly, that might be the best thing. I can think of 3 or 4 other systems that could fail unexpectedly due to time drift like that. At the very least, it makes it so that all of your logs have correct timestamps :)
Gabe****
Hello, sorry for "hijacking" this thread. Can someone please explain why FS keeps its own time ? As far as I know on vmware machines you can't avoid using NTP if you want to keep your system clock and with automatic daylight changes i've seen a difference of one hour between system time and freeswitch time. :-(
Ciao, Claudio
Internet Email Confidentiality Footer
----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto.
This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.
-----------------------------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com****
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****
****
** **
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900****
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Hello, I'm trying to clarify this concept in order to add it to create a "clock" entry on the wiki. What does "virtual migrations over VE" mean? Could FS run safely in production on virtual environments (e.g. vmware) or this is a "screwed by design" deployment because of unsolvable timing issues? I've read on the wiki http://wiki.freeswitch.org/wiki/Amazon_EC2 the ML http://old.nabble.com/Announcing-the-FreeSWITCH-Technology-Preview-VMWare-Ap... http://www.mail-archive.com/freeswitch-users@lists.freeswitch.org/msg07704.h... and also some vmware specific docs http://tinyurl.com/bmympov but I'm still unsure. Which of the following are true? 1) It's not safe to run FS on a vmware production environment 2) It's perfectly safe to run FS on a vmware production environment provided that FS does not handle media (i.e. use bypass_media) 3) It's perfectly safe to run FS on a vmware production environment taking advantage of the full FS features set (e.g. potential transcoding, IVR, conferencing). Kind Regards, Claudio From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Wednesday, December 14, 2011 6:16 PM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference As a caveat, DST being only one example, the other more real reasons include: erroneous commands from sysadmins changing the system time, virtual migrations over VE and many other reasons that went into our decision to lock on to the most accurate time source possible ASAP. Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. -----------------------------------------------------------------------------------------------------
FreeSWITCH will only run as good as a VE can perform. It is perfectly safe to use it in production but we WILL NOT support performance issues related to running in a VE because there are too many variables and emulations present to know the root cause of any particular performance issue. Our community conference server is a VE but its openvz which has proven the most reliable VE to run FreeSWITCH under that we have tested. Especially with current FS HEAD, it runs as expected on EC2 assuming you are choosing the correct image with full CPU power and the amazon linux OS. On Mon, Dec 19, 2011 at 9:01 AM, Cavalera Claudio Luigi < Claudio.Cavalera@italtel.it> wrote:
Hello, I'm trying to clarify this concept in order to add it to create a "clock" entry on the wiki.
What does "virtual migrations over VE" mean?
Could FS run safely in production on virtual environments (e.g. vmware) or this is a "screwed by design" deployment because of unsolvable timing issues? I've read on the wiki http://wiki.freeswitch.org/wiki/Amazon_EC2 the ML
http://old.nabble.com/Announcing-the-FreeSWITCH-Technology-Preview-VMWare-Ap...
http://www.mail-archive.com/freeswitch-users@lists.freeswitch.org/msg07704.h... and also some vmware specific docs http://tinyurl.com/bmympov
but I'm still unsure. Which of the following are true? 1) It's not safe to run FS on a vmware production environment 2) It's perfectly safe to run FS on a vmware production environment provided that FS does not handle media (i.e. use bypass_media) 3) It's perfectly safe to run FS on a vmware production environment taking advantage of the full FS features set (e.g. potential transcoding, IVR, conferencing).
Kind Regards, Claudio
From: freeswitch-dev-bounces@lists.freeswitch.org [mailto: freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Wednesday, December 14, 2011 6:16 PM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference
As a caveat, DST being only one example, the other more real reasons include: erroneous commands from sysadmins changing the system time, virtual migrations over VE and many other reasons that went into our decision to lock on to the most accurate time source possible ASAP.
Internet Email Confidentiality Footer
----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto.
This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.
-----------------------------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
I have been using it under LXC containers without issues, as well, but they are like OpenVZ where it runs on bare-metal hardware and not through some full virtualization environment. On Mon, Dec 19, 2011 at 11:41 AM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
FreeSWITCH will only run as good as a VE can perform.
It is perfectly safe to use it in production but we WILL NOT support performance issues related to running in a VE because there are too many variables and emulations present to know the root cause of any particular performance issue.
Our community conference server is a VE but its openvz which has proven the most reliable VE to run FreeSWITCH under that we have tested.
Especially with current FS HEAD, it runs as expected on EC2 assuming you are choosing the correct image with full CPU power and the amazon linux OS.
On Mon, Dec 19, 2011 at 9:01 AM, Cavalera Claudio Luigi < Claudio.Cavalera@italtel.it> wrote:
Hello, I'm trying to clarify this concept in order to add it to create a "clock" entry on the wiki.
What does "virtual migrations over VE" mean?
Could FS run safely in production on virtual environments (e.g. vmware) or this is a "screwed by design" deployment because of unsolvable timing issues? I've read on the wiki http://wiki.freeswitch.org/wiki/Amazon_EC2 the ML
http://old.nabble.com/Announcing-the-FreeSWITCH-Technology-Preview-VMWare-Ap...
http://www.mail-archive.com/freeswitch-users@lists.freeswitch.org/msg07704.h... and also some vmware specific docs http://tinyurl.com/bmympov
but I'm still unsure. Which of the following are true? 1) It's not safe to run FS on a vmware production environment 2) It's perfectly safe to run FS on a vmware production environment provided that FS does not handle media (i.e. use bypass_media) 3) It's perfectly safe to run FS on a vmware production environment taking advantage of the full FS features set (e.g. potential transcoding, IVR, conferencing).
Kind Regards, Claudio
From: freeswitch-dev-bounces@lists.freeswitch.org [mailto: freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Wednesday, December 14, 2011 6:16 PM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference
As a caveat, DST being only one example, the other more real reasons include: erroneous commands from sysadmins changing the system time, virtual migrations over VE and many other reasons that went into our decision to lock on to the most accurate time source possible ASAP.
Internet Email Confidentiality Footer
----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto.
This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.
-----------------------------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Eliot Gable "We do not inherit the Earth from our ancestors: we borrow it from our children." ~David Brower "I decided the words were too conservative for me. We're not borrowing from our children, we're stealing from them--and it's not even considered to be a crime." ~David Brower "Esse oportet ut vivas, non vivere ut edas." (Thou shouldst eat to live; not live to eat.) ~Marcus Tullius Cicero
Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock I hope it can helps everyone which sees sees different between system and FS times. can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime Thanks, Claudio Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. -----------------------------------------------------------------------------------------------------
So the question I have is can I just disable monotonic for CDR reporting? If FS needs it for internal timing and scheduling, that's fine. But my CDRs absolutely need to be based on the actual time. I cannot think of any scenario where I want anything but the closest to "real" time reported. Can we have the best of both worlds? Realtime for CDRs, and monotonic for FS internals? -Michael -----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Cavalera Claudio Luigi Sent: Thursday, December 22, 2011 2:37 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock I hope it can helps everyone which sees sees different between system and FS times. can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime Thanks, Claudio Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. ----------------------------------------------------------------------------------------------------- _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com 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
CDR are the leading reason we have monotonic support. If you change the time in the middle of a call to yesterday, then that call will report it was 1 day long. However, the monotonic clock support is only used in UNIX anyway so if you are in WIN you are not using it. There is a switch for windows to turn it on but I don't know if its the same thing as what we do in unix. On Thu, Dec 22, 2011 at 10:02 AM, Michael Giagnocavo <mgg@giagnocavo.net>wrote:
So the question I have is can I just disable monotonic for CDR reporting? If FS needs it for internal timing and scheduling, that's fine. But my CDRs absolutely need to be based on the actual time. I cannot think of any scenario where I want anything but the closest to "real" time reported.
Can we have the best of both worlds? Realtime for CDRs, and monotonic for FS internals?
-Michael
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto: freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Cavalera Claudio Luigi Sent: Thursday, December 22, 2011 2:37 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference
Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock
I hope it can helps everyone which sees sees different between system and FS times.
can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime
Thanks, Claudio
Internet Email Confidentiality Footer
----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto.
This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.
-----------------------------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
About Windows - yes, it will work as on Unix systems if starting with "-monotonic-clock" - it will use a true monotonic clock. I just submitted a patch for this also, to get usec precision on this on clock, currently its only ms - Jlenk is looking into it :) /Peter ________________________________________ Från: freeswitch-dev-bounces@lists.freeswitch.org [freeswitch-dev-bounces@lists.freeswitch.org] för Anthony Minessale [anthony.minessale@gmail.com] Skickat: den 22 december 2011 18:12 Till: freeswitch-dev@lists.freeswitch.org Ämne: Re: [Freeswitch-dev] Epoch current time difference CDR are the leading reason we have monotonic support. If you change the time in the middle of a call to yesterday, then that call will report it was 1 day long. However, the monotonic clock support is only used in UNIX anyway so if you are in WIN you are not using it. There is a switch for windows to turn it on but I don't know if its the same thing as what we do in unix. On Thu, Dec 22, 2011 at 10:02 AM, Michael Giagnocavo <mgg@giagnocavo.net<mailto:mgg@giagnocavo.net>> wrote: So the question I have is can I just disable monotonic for CDR reporting? If FS needs it for internal timing and scheduling, that's fine. But my CDRs absolutely need to be based on the actual time. I cannot think of any scenario where I want anything but the closest to "real" time reported. Can we have the best of both worlds? Realtime for CDRs, and monotonic for FS internals? -Michael -----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org<mailto:freeswitch-dev-bounces@lists.freeswitch.org> [mailto:freeswitch-dev-bounces@lists.freeswitch.org<mailto:freeswitch-dev-bounces@lists.freeswitch.org>] On Behalf Of Cavalera Claudio Luigi Sent: Thursday, December 22, 2011 2:37 AM To: freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org> Subject: Re: [Freeswitch-dev] Epoch current time difference Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock I hope it can helps everyone which sees sees different between system and FS times. can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime Thanks, Claudio Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. ----------------------------------------------------------------------------------------------------- _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto: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 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto: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 -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com<mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net<http://irc.freenode.net> #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org<mailto:sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900 !DSPAM:4ef3638c32766194317259!
So using realtime clock then won't screw with audio processing? -Michael From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Thursday, December 22, 2011 10:13 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference CDR are the leading reason we have monotonic support. If you change the time in the middle of a call to yesterday, then that call will report it was 1 day long. However, the monotonic clock support is only used in UNIX anyway so if you are in WIN you are not using it. There is a switch for windows to turn it on but I don't know if its the same thing as what we do in unix. On Thu, Dec 22, 2011 at 10:02 AM, Michael Giagnocavo <mgg@giagnocavo.net<mailto:mgg@giagnocavo.net>> wrote: So the question I have is can I just disable monotonic for CDR reporting? If FS needs it for internal timing and scheduling, that's fine. But my CDRs absolutely need to be based on the actual time. I cannot think of any scenario where I want anything but the closest to "real" time reported. Can we have the best of both worlds? Realtime for CDRs, and monotonic for FS internals? -Michael -----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org<mailto:freeswitch-dev-bounces@lists.freeswitch.org> [mailto:freeswitch-dev-bounces@lists.freeswitch.org<mailto:freeswitch-dev-bounces@lists.freeswitch.org>] On Behalf Of Cavalera Claudio Luigi Sent: Thursday, December 22, 2011 2:37 AM To: freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org> Subject: Re: [Freeswitch-dev] Epoch current time difference Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock I hope it can helps everyone which sees sees different between system and FS times. can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime Thanks, Claudio Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. ----------------------------------------------------------------------------------------------------- _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto: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 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto: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 -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com<mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net<http://irc.freenode.net> #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org<mailto:sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Hello Michael, I've added the info on this thread to the wiki: http://wiki.freeswitch.org/wiki/Clock although poorly formatted I'm sure it will be useful to many users. However I don't understand this final question of yours (which got no answers btw). Could you please elaborate on it a bit? With "using realtime clock" do you mean "using the -nort flag"? Thanks, Claudio From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Michael Giagnocavo Sent: Friday, December 23, 2011 3:44 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Epoch current time difference So using realtime clock then won't screw with audio processing? -Michael Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. -----------------------------------------------------------------------------------------------------
-nocal turns off the calibrating clock sequence executed at startup. It does several tests to find the number of microseconds you should sleep to get exactly 1 millisecond. Some systems are off in this respect and the test finds the optimal value, when you specify -nocal it just uses the default of exactly 1000 microseconds. -nort essentially disables clock_nanosleep from being used as a method to sleep small amounts of time. On many systems this function is by far the most accurate but on many others its not. Its harder to test for this so we have to figure it out manually, really its mostly older boxes who need this. On Thu, Dec 22, 2011 at 3:36 AM, Cavalera Claudio Luigi < Claudio.Cavalera@italtel.it> wrote:
Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock
I hope it can helps everyone which sees sees different between system and FS times.
can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime
Thanks, Claudio
Internet Email Confidentiality Footer
----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto.
This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.
-----------------------------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Claudio, Thanks for adding this! We appreciate it when community members take the initiative to add useful information to the wiki. Later in this thread Anthony answers your questions about -nolocal and -nort. If you need assistance adding that information to the wiki just let me know. Thanks again, MC On Thu, Dec 22, 2011 at 1:36 AM, Cavalera Claudio Luigi < Claudio.Cavalera@italtel.it> wrote:
Hello, I've created this entry on the wiki: http://wiki.freeswitch.org/wiki/Clock
I hope it can helps everyone which sees sees different between system and FS times.
can someone elaborate a bit on these options which i believe are clock related? -nocal -- disable clock calibration [NOTE: if you don't want it to try to calibrate the 1ms sleep precision] -nort -- disable clock clock_realtime
Thanks, Claudio
Hi guys, I'm currently working on speaker identification and verification support. However, I don't know how to get the results so I can use them in dialplan conditions. I followed the ASR, the results from SID system are sent via MRCP and stored in SID's internal structure called switch_sid_handle_t (the same as switch_asr_handle_t but modified for SID). In the ASR, the results are sent via the event system. My question is, how can I access the results sent by an event from dialplan ?? I'd like to use the results in the dialplan conditions. Thanks is advance guys ;)
In the places where you set the events, also set channel variables with the same info for the dialplan apps to get to it. On Tue, Sep 13, 2011 at 11:15 AM, Viktor Jamrich <viktor_jamrich@centrum.sk> wrote:
Hi guys, I'm currently working on speaker identification and verification support. However, I don't know how to get the results so I can use them in dialplan conditions.
I followed the ASR, the results from SID system are sent via MRCP and stored in SID's internal structure called switch_sid_handle_t (the same as switch_asr_handle_t but modified for SID). In the ASR, the results are sent via the event system. My question is, how can I access the results sent by an event from dialplan ?? I'd like to use the results in the dialplan conditions.
Thanks is advance guys ;)
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
participants (10)
-
Anthony Minessale
-
Cavalera Claudio Luigi
-
Eliot Gable
-
Gabriel Gunderson
-
Glaucio Vaz de Mello
-
lakshmanan ganapathy
-
Michael Collins
-
Michael Giagnocavo
-
Peter Olsson
-
Viktor Jamrich