Read the forum guidelines
This has been going on for at least a day now in the Cleveland Ohio area. The wrong time is being sent from COX in the Caller Id data. Currently it is 11:30 PM but COX is sending 9:30 AM as the time.
This has been reported by others on the DSL Reports forums too: www.dslreports.com/.../r32206313-FL-COX-Voice-sending-incorrect-time
Have you tried rebooting the phone modem?
Rebooting of the phone modem made no difference. I even unplugged the phone modem, removed the internal battery, and let it sit for a couple minutes before reseating the battery and plugging in the power cord. Time is still completely hosed.
Time is correct on the Cox Website and Cox Connect Phone Tools Android App but it is wrong on the actual phones.
Call listed at 10:40 AM, but physical phones show 8:40 PM.
Other thing noticed is all Distinctive Ring settings are wiped out. Special ring did not happen when using my cell phone to call, that has been configured for distinctive ring for years now.
Another new realization is the phone settings now have "simultaneous ring" available. This was not available a month ago. I'm guessing when the phone system was upgraded by Cox (backend) that someone forgot to usethe correct time settings somewhere.
Phones have been reprogrammed multiple times, but each time a call comes in, Cox sends incorrect time and date (or timezone) so the phones are wrong from there on out. Phones are AT&T DECT wireless and AT&T wired wall mounted incase of power outages.
Like now, Cox reset all phones to 2:20 AM 02/18 instead of 4:20 PM 02/17.
Problem still exist, not fixed, even though someone called at 7:33 PM 02/19 according to the phone's Caller Id data saying its fixed.
Its only 5:45 PM 02/19. So that would mean they called at 9:33 AM real time.
The phones timestamps worked fine earlier last week, but after COX's upgrade it is off by 10 hours. The logical conclusion is something with the COX upgrade broke it.
I noticed the wrong time showing very late on Friday. Did COX do a system upgrade on Friday? If so, that's when it broke.