| Caller ID problems Apparently my phone adjusts it clock based on incoming calls. My guess is Caller ID data -- I don't know how else to explain it.
I have reset the clock on my phone several times and each time I get a call, the time jumps ahead about 90 hours. I have only noticed this today. Not a huge deal, but a bit of an annoyance since I am using the answering machine built into my phone and this makes the time stamp incorrect.
Is the time transmitted along with Caller ID? I'm guessing yes since it is causing the clock on the phone to change.
Is anyone else experiencing this problem? |
|
| It is transmitted, I know, and it keeps good time for me on a Bell South caller ID box and on a Panasonic phone with caller ID. |
|
 leiboldPremium,MVM
join:2002-07-09
Sunnyvale, CA
kudos:2
 ·SONIC.NET
·Pacific Bell - SBC
| reply to SonicSF
90 hours = 4 days and 4 hours ?
I just tried it by calling my Fusion number from the cell phone and the caller id date/time was correct.
--
Got some spare cpu cycles ? Join Team Helix or Team Starfire! |
|
| reply to SonicSF
I have a Panasonic cordless phone.
I manually set the correct time in my phone just now, 2135 on Jan 2. I called myself with my cell phone and the clock then changed to 1135 Jan 5. Not quite 90 hours, but that is roughly 62 hours.
I first noticed this about 1830 on Dec 29 and the my clock was being changed to 0830 Jan 2. Not quite 90 hours, but it wasn't far off either. |
|
leiboldPremium,MVM
join:2002-07-09
Sunnyvale, CA
kudos:2 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| I also have a Panasonic cordless phone with Caller Id (a fairly old model). I didn't think my phone's time was being set from Caller Id and to test that I intentionally set it to a wrong date (a day ahead). When I called it from my cell phone the Caller Id list showed the correct date and time of the call despite the phone date being wrong (it was still wrong after the call).
--
Got some spare cpu cycles ? Join Team Helix or Team Starfire! |
|
|
|
| reply to SonicSF
Or maybe it was 2 days and change like I am experiencing now. I don't really remember now.
Perhaps this clock is local to my CO, SNFCCA14. |
|
 DaneJasperSonic.NetPremium,VIP
join:2001-08-20
Santa Rosa, CA
kudos:7 | said by SonicSF :Or maybe it was 2 days and change like I am experiencing now. I don't really remember now.
Perhaps this clock is local to my CO, SNFCCA14.
Very odd. Caller ID does set the clock on most phones, though some have an option to enable to disable this. I find it quite convenient when DST rolls around, it resets on the next call to the accurate time.
-Dane |
|
DaneJasperSonic.NetPremium,VIP
join:2001-08-20
Santa Rosa, CA
kudos:7 | reply to SonicSF
said by SonicSF :Perhaps this clock is local to my CO, SNFCCA14.
We gave this DSLAM a look, and you were right - the system control module was replaced recently and the network time sync settings did not carry over. Good catch, thanks!
-Dane |
|
| I don't know what DSLAM I am on but my time is off on my phone but only by a few minutes. It is like three minutes slow... do they have a way to fix that remotely? |
|
| Zeonis, if you can provide the area code and prefix (first 3 digits) of your phone number, or something else I can use to identify your serving CO, I can see if there is any time sync problems that could be causing this. |
|
| Area code is 510 and the prefix is 483... |
|
| Zeonis, I've checked our DSLAM configuration and verified that it is set to the exact correct time, and updates every 30 minutes via NTP. If you are seeing a 3 minute drift on your phone, the problem appears to be external to Sonic's network. |
|
| Strange because the incoming calls set the time so I wonder else could be causing it? Oh well... technology... sometimes it works sometimes it doesn't... thanks for checking though. |
|
