Forum Discussion
Is it just "Call History" that doesn't work?
Are you able to get to "Voice Tools"?
Can you expand "Address Book"?
- MasterMyDomain2 years agoContributor
It's jut call history. I was able to edit an entry in my Address Book and look at Settings. I'll be gone most of today.
- CurtB2 years agoValued Contributor II
If you had a corrupted contact, it could cause Call History to fail. The view you see (when it works) is the result of joining a calls table of your incoming and outgoing calls to a contacts table that you maintain. Since you're able to expand Address Book, I don't think you have a corrupted contact. But you could still test contacts individually by selecting each one and clicking "Edit Contact". At least check the last contact you added before Call History stopped working, if you know which one it was.
If you don't have a corrupted contact, you probably have corrupted calls data. You should get another email account, even if you only use it to communicate with cox.help@cox.com. Contact them and ask for your ticket number. Ask them to verify with the "Phone Tools Team" that they've checked your call history for corrupted data. When Social Media Support updates your ticket, it should trigger a fresh look at your issue and a status update.
- MasterMyDomain2 years agoContributor
In a response to Becky 19 days ago I pointed out the possibility that corrupted data in a contact record or the call record could be causing the problem. Especially because the Call History problem started immediately after they fixed the buffering problem that prevented us from getting into voice tools. In a phone call from them I provided my Login ID and Password. Why haven't they written a utility program to validate all my data records? Why haven't they made a copy of their call history program to run offline using my data? They could put in some checkpoints that say "So far so good at line xxxx of the code?" They could change their error messages to say "Invalid Special Character in Last Name" instead of "We are experiencing technical difficulties." I wrote and modified database programs 30 years ago. I wasn't good at it but fixing problems like this wasn't that difficult. Thanks for not giving up on this.