I don't have a polycomm manual handy, but I think I'd change the
overrideDHCP parameter to "1" and test. You are apparently in the PST
timezone?
If that doesn't do it, my next step would be to use ethereal to capture
one of the ntp request/response pkts and analyze the content. If that
looks okay, then something in the phone isn't right.
Kerry Garrison wrote:
Here is the sip.cfg file
<SNTP tcpIpApp.sntp.resyncPeriod="86400"
tcpIpApp.sntp.address="192.168.10.50"
tcpIpApp.sntp.address.overrideDHCP="0"
tcpIpApp.sntp.gmtOffset="-25200"
tcpIpApp.sntp.gmtOffset.overrideDHCP="0"
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"/>
Using the same IP for the server on a Linksys SPA-941 everything is correct,
using this configuration on the 501 shows 24 hours ahead.
-Kerry
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Rich Adamson
Sent: Thursday, April 27, 2006 11:59 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Polycom NTP issue
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?
_______________________________________________
--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
_______________________________________________
--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
_______________________________________________
--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
