Time service on a Cisco DHCP

[trietgiang]

I don't know if you are using a Cisco router as a DHCP for ShoreTel phones. We have that in place with this setup:

ip dhcp pool Mypool
network 10.1.1.0 255.255.255.0
default-router 10.1.1.254
option 156 ascii "ftpservers=10.1.1.1"
dns-server 139.130.4.4 61.3.133.192 61.9.134.49
option 4 ip 128.250.36.2 128.250.36.3

Option 4 is where I specified the time servers. But it seemed that they are not working. Those servers are working on my PC. Could someone please tell me why it doesn't work?

Note that I have enabled a permit on the ACL of the dialer0 (outside interface).

Thank you for your time.
Triet

[gberkemeyer]

You should use option 42 (NTP Servers) instead of option 4 (Time Servers)

Gary

[trietgiang]

Thanks Gary, I tried that, still showing the wrong time.

Other suggestions?

[trietgiang]

I checked an old config where the time was right and "option 4" was used.

I tried pinging the NTP server from the phone (using <mute>PING (<mute)7464) and the ping was ok.

[Jason Learmouth]

Option 4 and 42 both work but 4 has been depricated by 42 so that should be the one you setup if you have the choice. Does it work if you use an internal time server? Try the DC on your 10.1.1.x subnet as the NTP server.

[trietgiang]

Thanks all for your help.

I have found out what's wrong: the GMT offset in the Sites configuration was wrongly set. So I think the way the handset works is to request "some" raw time data from the server, then offset it with the GMT settings and give out the time.

[Forum]

Thanks all for your help.

I have found out what's wrong: the GMT offset in the Sites configuration was wrongly set. So I think the way the handset works is to request "some" raw time data from the server, then offset it with the GMT settings and give out the time.

That is correct! If the offset is wrong, it's due to the Shoretel settings, if the entire Date/time is way off, it's the NTP server not responding.