Ask a question
For the latest on our response to Coronavirus (COVID-19), click here.
Wed, Feb 5, 2020 3:32 PM
Initially, I set the time and have to reset it because, after a while, it is wrong.
2 months ago
ACE - Master
On what and what service?
CL82407 cordless phone
Can’t determine what to do without more info, like the device you are referencing. Most time can be set to automatic through the settings.
CL82407 cordless phone........jumps ahead one hour.
What service is it on? Traditional landline, digital U-verse, wireless home phone? Is AT&T the carrier? Did it ever work? Do you have it set manually or set to get time and date off the caller ID? Hard to answer your question until all information is known.
Thr AT&T cordless phone that is experiencing the problem is a recent replacement for my older AT&T phone.
See page 19 and 26 of the manual found here. Says the time setting being derived from CID default is set to on. So your service is sending you the incorrect time for your location. I don't know enough about magic jack to know if you can set time zone or not and I'm not going to look that information up. You can set your phone manually instead of using the time off CID.
@spoom2 Thanks for the details on what to try. I turned off CID time sync (page 26) and then reset the time (page 19). Now it's a wait and see to determine if this solves the problem. However, even it does, I'm wondering why the default is CID time sync "on"?............is there advantage to having it "on" or a disadvantage to having it "off"?
I will return tomorrow to let you know if the fix was or was not successful.
The advantage to have it get it's information off the CID is the time will always be correct, unless your supplier is sending it wrong, like in your case. Manually set it will depend on how accurate the internal clock is. If accurate it should be no problem you'll just have to reset on DST and back when the time changes, if you're in a area where it's used.
Thanks for the explanation.
The time is still correct as of today, so the fix appears to be working. I appreciate your help.