[asterisk-bugs] [Asterisk 0014142]: Registration uses hwclock and sysclock to retrieve time

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14142 
====================================================================== 
Reported By:                CGMChris
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14142
Category:                   Channels/chan_sip/Registration
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-12-26 17:44 CST
Last Modified:              2009-04-23 12:23 CDT
====================================================================== 
Summary:                    Registration uses hwclock and sysclock to retrieve
time
Description: 
It looks like different areas of the SIP registration code retrieve the
date/time differently. Under *most* conditions the time is pulled from the
sysclock, however, under some rare conditions the time appears to be pulled
from the hwclock.

My system had the hardware clock set 4 hours ahead of the sysclock (it's a
new system and I had never ran /sbin/hwclock --systohc).

Once every day or so, my service would go out, and "sip show registry"
would report a registration time in the future.  Asterisk was showing me as
connected with a registration time 4 hours into the future, but my provider
was timing me out.

I tried the following settings (with no luck)
sip.conf:
[general]
...
registerattempts=0
registertimeout=60
defaultexpiry=120

Granted it's my fault that I did not set the hwclock, but I think Asterisk
should also be more consistent on how it pulls the date/time -- hwclock or
sysclock, one or the other.
====================================================================== 

---------------------------------------------------------------------- 
 (0103699) qwell (administrator) - 2009-04-23 12:23
 http://bugs.digium.com/view.php?id=14142#c103699 
---------------------------------------------------------------------- 
Putting Asterisk issues into the AsteriskNOW project is the wrong thing to
do.  They will never be looked at.

AsteriskNOW is unpatched Asterisk on a standard CentOS install.  There is
nothing magical added. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-23 12:23 qwell          Note Added: 0103699                          
======================================================================