I am ready to pull my hair out. I cannot seem to get the Polycoms to read the time properly. Regardless of the server they are pointed to our the offset, i am getting the correct time, but 24 hours ahead. So for today it is showing Friday April 28 but with the correct time. Any clues? Kerry Garrison Director of Technical Services Tech Data Pros - Orange County's Mobile IT Service Provider (949) 502-7819 x200 - <mailto:kerryg@techdatapros.com> kerryg@techdatapros.com <http://www.techdatapros.com/> http://www.techdatapros.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060427/5caef03d/attachment.htm
What Polycom phone model? What firmware version? What bootROM version? Older versions of Polycom phones only worked with SNTP time servers not NTP. MATT--- On 4/27/06, Kerry Garrison <support@techdatapros.com> wrote:> > I am ready to pull my hair out. I cannot seem to get the Polycoms to read > the time properly. Regardless of the server they are pointed to our the > offset, i am getting the correct time, but 24 hours ahead. So for today it > is showing Friday April 28 but with the correct time. Any clues? > > Kerry Garrison > Director of Technical Services > Tech Data Pros - Orange County's Mobile IT Service Provider > (949) 502-7819 x200 - kerryg@techdatapros.com > http://www.techdatapros.com > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > >
Hello Kerry, you has some NTP server installed in its system? Which distribution uses? I wait to have helped. Greetings Josu? 2006/4/27, Kerry Garrison <support@techdatapros.com>:> > I am ready to pull my hair out. I cannot seem to get the Polycoms to read > the time properly. Regardless of the server they are pointed to our the > offset, i am getting the correct time, but 24 hours ahead. So for today it > is showing Friday April 28 but with the correct time. Any clues? > > Kerry Garrison > Director of Technical Services > *Tech Data Pros - Orange County's Mobile IT Service Provider > *(949) 502-7819 x200 - *kerryg@techdatapros.com* <kerryg@techdatapros.com> > *http://www.techdatapros.com* <http://www.techdatapros.com/> > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com <http://easynews.com/>-- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060427/7145c473/attachment.htm
What dns server are you running? On Thu, 27 Apr 2006, Kerry Garrison wrote:> I am ready to pull my hair out. I cannot seem to get the Polycoms to read > the time properly. Regardless of the server they are pointed to our the > offset, i am getting the correct time, but 24 hours ahead. So for today it > is showing Friday April 28 but with the correct time. Any clues? > > Kerry Garrison > Director of Technical Services > Tech Data Pros - Orange County's Mobile IT Service Provider > (949) 502-7819 x200 - <mailto:kerryg@techdatapros.com> > kerryg@techdatapros.com > <http://www.techdatapros.com/> http://www.techdatapros.com > >-- Aaron Daniel Computer Systems Technician Sam Houston State University amdtech@shsu.edu (936) 294-4198
Kerry Garrison wrote:> I am ready to pull my hair out. I cannot seem to get the Polycoms to > read the time properly. Regardless of the server they are pointed to > our the offset, i am getting the correct time, but 24 hours ahead. So > for today it is showing Friday April 28 but with the correct time. Any > clues? >Yep, I've had a lot of experience with this issue. First, the NTP server offered by the DHCP server overrides any other setting. One problem I found was a Cable Modem offering an NTP server that could not be reached. Find out from the log file what NTP server is being referenced. Also, the NTP server must be synchronized before it can be used as a timing - try ntpq -p to see if there is an asterisk besides a real ntp server. -- Chris Mason NetConcepts (264) 497-5670 Fax: (264) 497-8463 Int: (305) 704-7249 Fax: (815)301-9759 UK 44.207.183.0271 Cell: 264-235-5670 Yahoo IM: netconcepts_anguilla@yahoo.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060427/0b57eed6/attachment.htm
Kerry Garrison wrote:> I am ready to pull my hair out. I cannot seem to get the Polycoms to > read the time properly. Regardless of the server they are pointed to our > the offset, i am getting the correct time, but 24 hours ahead. So for > today it is showing Friday April 28 but with the correct time. Any clues?This is a copy/paste of the exact statements used on a IP600 phone: <SNTP tcpIpApp.sntp.resyncPeriod="86400" tcpIpApp.sntp.address="134.84.84.84" tcpIpApp.sntp.gmtOffset="-21600" tcpIpApp.sntp.daylightSavings.enable="1" tcpIpApp.sntp.daylightSavings.fixedDayEnable="0" tcpIpApp.sntp.daylightSavings.start.month="4" tcpIpApp.sntp.daylightSavings.start.date="1" tcpIpApp.sntp.daylightSavings.start.time="2" tcpIpApp.sntp.daylightSavings.start.dayOfWeek="1" tcpIpApp.sntp.daylightSavings.start.dayOfWeek.lastInMonth="0" tcpIpApp.sntp.daylightSavings.stop.month="10" tcpIpApp.sntp.daylightSavings.stop.date="1" tcpIpApp.sntp.daylightSavings.stop.time="2" tcpIpApp.sntp.daylightSavings.stop.dayOfWeek="1" tcpIpApp.sntp.daylightSavings.stop.dayOfWeek.lastInMonth="1" Are you sure you are setting the gmtOffset to the proper number? The above example is for CST, which is -6 hours (or -21600 seconds) from GMT. It is also config'ed with resyncPeriod = 24 hours, meaning the clock is only sync'ed once per day. What are you using for the above?
Are you passing the Offset through the DHCP server as well? On a linux
DHCP server this would be:
option time-offset -18000; # Eastern Standard Time
option ntp-servers 192.168.x.x
The fact that the date is wrong, but the time is correct, seems a little
strange to me. Are you sure your Windows server is set to the correct
date?
What happens if you set the time on the phone to a different time and
date, will it pull the date back of the NTP server?
Also, try and run some network sniffing tools to verify that it is
getting a valid response.
________________________________
I am ready to pull my hair out. I cannot seem to get the Polycoms to
read the time properly. Regardless of the server they are pointed to our
the offset, i am getting the correct time, but 24 hours ahead. So for
today it is showing Friday April 28 but with the correct time. Any
clues?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060427/51eb0420/attachment.htm
Kerry Garrison wrote:> I am ready to pull my hair out. I cannot seem to get the Polycoms to > read the time properly. Regardless of the server they are pointed to our > the offset, i am getting the correct time, but 24 hours ahead. So for > today it is showing Friday April 28 but with the correct time. Any clues?Kerry, Don't know if this will help, but I'm using a Windows Server 2003 DHCP server for my Polycom 501. In the config I use: 002 Time Offset (UTC offset in seconds): 0xffff8f80 004 Time Server (Array of time server addresses, by preference): my list of servers (note my list is some of the external standard ntp servers out there). p --------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2?/min with Yahoo! Messenger with Voice. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060427/603b7945/attachment.htm