cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
172
Views
0
Helpful
1
Replies
Enthusiast

CUE 8.6.9 time is incorrect

My C3945 router works great and it keeps time perfectly.  We are on the east coast and we observe daylight savings time. 

TDC_CME_Router#sh clock
17:30:03.061 DST Wed Jul 24 2019
TDC_CME_Router#sh ntp associations

address ref clock st when poll reach delay offset disp
*~192.99.2.8 213.251.128.249 2 3 64 377 128.24 4.585 4.293
~127.127.1.1 .LOCL. 7 7 16 377 0.000 0.000 0.231
192.168.69.41 192.168.69.1 4 223 1024 143 0.773 -2.207 92.053
+~138.68.46.177 90.187.7.5 2 31 64 377 120.49 7.116 5.102
192.168.50.51 192.168.69.1 4 29 1024 355 0.379 -18.572 24.480
+~198.50.238.163 213.251.128.249 2 33 64 377 120.12 -1.435 3.302
+~103.105.51.156 206.55.191.142 2 1304 1024 376 135.31 -1.595 16.936
+~162.221.74.15 185.140.51.3 2 41 64 377 133.29 5.868 6.135
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

I installed an ISM-300 voicemail module and got it working too.  However, the time is incorrect by one hour for the voicemail timestamps.  The phones show the correct time.  I cannot figure out how to get the ISM to recognize DST. I an ping the CME router from within CUE.

TDC-VMAA# sh ntp ser
remote refid st t when poll reach delay offset jitter
==============================================================================
*10.110.0.1 198.50.238.163 3 u 210 256 1 0.336 9.002 1.612
space reject, x falsetick, . excess, - outlyer
+ candidate, # selected, * sys.peer, o pps.peer
TDC-VMAA# ping 10.110.0.1
PING 10.110.0.1 (10.110.0.1) 56(84) bytes of data.
64 bytes from 10.110.0.1: icmp_seq=1 ttl=255 time=0.191 ms
64 bytes from 10.110.0.1: icmp_seq=2 ttl=255 time=0.172 ms
64 bytes from 10.110.0.1: icmp_seq=3 ttl=255 time=0.137 ms
64 bytes from 10.110.0.1: icmp_seq=4 ttl=255 time=0.127 ms
64 bytes from 10.110.0.1: icmp_seq=5 ttl=255 time=0.130 ms

--- 10.110.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.127/0.151/0.191/0.027 ms, ipg/ewma 0.204/0.169 ms
TDC-VMAA# sh clock
16:24:56.161 EST Wed Jul 24 2019
TDC-VMAA# exit

Session closed


[Connection to 10.110.0.1 closed by foreign host]
TDC_CME_Router#sh clock
17:25:00.954 DST Wed Jul 24 2019

 

Everyone's tags (1)
1 REPLY 1
Highlighted
Rising star

Re: CUE 8.6.9 time is incorrect

Hi,

Can you try configuring "clock timezone America/New_York" command on CUE module.

 

Please rate helpful posts and if applicable mark "Accept as a Solution".
Thanks, Vaijanath S.
CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards