Caller ID Time

Posts: 62 · Full Forum Member Joined: Mar 04, 2006 Posts: 62

Hi,

I have a Pansonic DECT 6.0 phone that gets its time from caller ID. You set the time manually at first, and then after that it sets the time based on caller ID. I've noticed that the time coming from caller ID is around 7 minutes fast. I just set the time correctly and called my phone. It changed the time to be 7 minutes fast. Anyone else seen this? By the way my Vonage adapter is an RTP300.

Thanks

Posts: 62 · Full Forum Member Joined: Mar 04, 2006 Posts: 62

Just an update. The same issue happens on my other Vonage line that has a Uniden phone connected to it. This phone does not get its time from caller ID, but the caller ID log does show the times of the calls to be 7 minutes fast.

Posts: 628 · Posted: Tue Jan 06, 2009 3:02 pm Post subject:

I have confirmed that the Vonage time servers are returning the correct and accurate time. All Vonage devices use time.vonage.net for NTP and upon an incoming calls, the device will query time.vonage.net.

Here is a packet capture of a test call I just placed to myself at approximately 2:55 PM EST. NOTE that the time servers will return results in GMT and your device will convert to your time zone that is set in it's profile.

All the way at the bottom you will see Receive Time Stamp and Transmit Time Stamp. This is what it is getting from the NTP server and what your device will display for the call.

This might be a stupid question but are you sure all your clocks aren't 7 minutes slow?

Frame 4 (90 bytes on wire, 90 bytes captured)
Arrival Time: Jan 6, 2009 14:54:49.585978000
[Time delta from previous captured frame: 0.076198000 seconds]
[Time delta from previous displayed frame: 0.076198000 seconds]
[Time since reference or first frame: 0.156284000 seconds]
Frame Number: 4
Frame Length: 90 bytes
Capture Length: 90 bytes
[Frame is marked: False]
[Protocols in frame: eth:ip:udp:ntp]
Ethernet II, Src: Dell_ba:3c:f2 (00:11:43:ba:3c:f2), Dst: Cisco_af:19:20 (00:0d:28:af:19:20)
Destination: Cisco_af:19:20 (00:0d:28:af:19:20)
Address: Cisco_af:19:20 (00:0d:28:af:19:20)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
Source: Dell_ba:3c:f2 (00:11:43:ba:3c:f2)
Address: Dell_ba:3c:f2 (00:11:43:ba:3c:f2)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
Type: IP (0x0800)
Internet Protocol, Src: 216.115.31.140 (216.115.31.140), Dst: 192.168.0.45 (192.168.0.45)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 76
Identification: 0x0000 (0)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 55
Protocol: UDP (0x11)
Header checksum: 0x8acc [correct]
[Good: True]
[Bad : False]
Source: 216.115.31.140 (216.115.31.140)
Destination: 192.168.0.45 (192.168.0.45)
User Datagram Protocol, Src Port: ntp (123), Dst Port: 12166 (12166)
Source port: ntp (123)
Destination port: 12166 (12166)
Length: 56
Checksum: 0x29da [correct]
[Good Checksum: True]
[Bad Checksum: False]
Network Time Protocol
Flags: 0x24
00.. .... = Leap Indicator: no warning (0)
..10 0... = Version number: NTP Version 4 (4)
.... .100 = Mode: server (4)
Peer Clock Stratum: secondary reference (3)
Peer Polling Interval: 4 (16 sec)
Peer Clock Precision: 0.000001 sec
Root Delay: 0.0755 sec
Root Dispersion: 0.1772 sec
Reference Clock ID: 216.115.30.79
Reference Clock Update Time: Jan 6, 2009 19:53:00.7016 UTC
Originate Time Stamp: Sep 8, 1926 08:45:34.1922 UTC
Receive Time Stamp: Jan 6, 2009 19:54:49.4826 UTC
Transmit Time Stamp: Jan 6, 2009 19:54:49.4826 UTC

Posts: 62 · Full Forum Member Joined: Mar 04, 2006 Posts: 62

I have 2 clocks and a watch that all get their time from the atomic clock in Colorado. Also both my computers have the same time as well. So I don't believe it is an issue with my time. Could it be the RTP300?

Posts: 628 · Posted: Tue Jan 06, 2009 3:21 pm Post subject:

I do not see how it can be the device since it will only pass the time value it receives in the NTP lookup as I just showed you in the NTP packet. It does not store time or have an internal clock. It uses NTP for all time queries.

Posts: 113 · Posted: Tue Jan 06, 2009 4:26 pm Post subject: Re: Caller ID Time

NEWCASTLE wrote:

Hi,

I have a Pansonic DECT 6.0 phone that gets its time from caller ID. You set the time manually at first, and then after that it sets the time based on caller ID. I've noticed that the time coming from caller ID is around 7 minutes fast. I just set the time correctly and called my phone. It changed the time to be 7 minutes fast. Anyone else seen this? By the way my Vonage adapter is an RTP300.

Thanks

Hi NEWCASTLE,

I recently bought a Panasonic DECT 6.0 phone, and in mine there's a setting to change from automatic time adjustment to manual. I don't know which unit you have, but in mine you can do the following:

MENU > Set Date & Time > Time Adjustment > Manual > Save

The other option in Time Adjustment is Caller ID [auto], which I believe yours is on right now. If your phone has a similar setting to change to manual, you might try that to see if that does the trick.

Posts: 62 · Full Forum Member Joined: Mar 04, 2006 Posts: 62

I fixed the issue by unplugging the power from the RTP300 and then reconnecting it. The RTP300 had not been restarted in probably a year. I keep it on UPS, and it never loses power. After restarting it I called my phone and the correct time appeared.