Caller ID stopped working

Posts: 18 · Posted: Tue Jan 25, 2005 9:52 am Post subject: Caller ID stopped working

My caller ID was working fine with my Uniden 5.8GHZ cordless phone system. I have lots of calls in the caller ID list up until January 23rd. Then on the 24th it stopped working. When I get an incoming call, it shows "Incoming Call" instead of caller ID info. The caller's information is viewable on the website, but is not received by the phone.

Interestingly enough, Call Waiting Caller ID is working fine, but not normal Caller ID. Any suggestions?

Thanks.

Posts: 86 · Posted: Tue Jan 25, 2005 10:20 am Post subject:

Which device do you have? PAP2, RT?

Posts: 18 · Posted: Tue Jan 25, 2005 10:45 am Post subject:

It's a Motorola VT1005V.

Posts: 86 · Posted: Tue Jan 25, 2005 10:49 am Post subject:

Did you try the infmaous reboot? Or shutdown of all devices then start up one by one, cable modem first?

Posts: 18 · Posted: Tue Jan 25, 2005 10:53 am Post subject:

Nope, haven't tried either rebooting or the power-down/power-up, but I will and I'll report back with results.

Posts: 86 · Posted: Tue Jan 25, 2005 11:00 am Post subject:

Do you have the MTA behind or infront of a router?

Posts: 18 · Posted: Tue Jan 25, 2005 11:03 am Post subject:

Ok, the reboot seems to have fixed it. Thanks for the input. The part of me that hates the way Windows has trained us all to reboot every device in sight to fix problems is wondering why the caller id would suddenly drop off and then come back, but I guess I'll leave well enough alone.

Thanks again

Posts: 86 · Posted: Tue Jan 25, 2005 11:10 am Post subject:

The internet is a whacky place and sending anything across it, doesn't necessarily mean it will all get there in one piece on the other side. Sad

Posts: 3198 · Posted: Tue Jan 25, 2005 11:21 am Post subject:

a reboot has nothing to do with "it" getting there "in one piece". it's either getting there or it's not, and none of it is reliant on the mta. how the mta handles the info is a different story, and apparently the mta got messed up somehow.
when I first looked for a solution, I noticed this post:
http://www.dslreports.com/forum/remark,9637111~mode=flat
but didn't think it was applicable since call waiting caller id still worked. obviously it's an issue with the mta. fortunately a simple reboot fixes it (compared to the multiple ta's some people have to get for noise issues, port disconnects, etc etc)