[smackman]

Has anyone else had problems with caller ID locking up 622 causing it to reboot on its own? I have not had any unwanted reboots since I disabled the caller ID on 622.
This problem happened on 2 different 622 receivers. I have 2 DSL filters in series so I know my DSL is not causing it. I am wondering if this is a "local" isSue with my caller ID or a software problem.

 

[ChuckA]

Never had a reboot caused by CID. Been running my 622 since Feb. 2006 with CID enabled.

 

[mdewitt]

take a look at this

http://www.dbstalk.com/showthread.php?t=68862&highlight=caller+id

 

[ChuckA]

take a look at this

http://www.dbstalk.com/showthread.php?t=68862&highlight=caller+id

Same user, same problem, just a new thread.

 

[Ron Barry]

I have CID enabled on both my boxes and I have not had any reboots related to getting a call.

 

[Rovingbar]

No problems for me. It is very reliable and we have Vonage. It used to be problematic, but Dish and Vonage seem to have worked out the compatability issues.

 

[invaliduser88]

I've had one hang that seemed to be caused by Caller ID a few weeks back. Fortunately, it hasn't happened again yet.

 

[mchaney]

No reboots, but now with 365, caller ID doesn't work worth poop! It displays the little popup box only about 1 out of every 4 calls. Worked every time before 365. I'm on a regular 'ol analog phone line.

Mike

 

[richbogrow]

Has anyone else had problems with caller ID locking up 622 causing it to reboot on its own? I have not had any unwanted reboots since I disabled the caller ID on 622.
This problem happened on 2 different 622 receivers. I have 2 DSL filters in series so I know my DSL is not causing it. I am wondering if this is a "local" isSue with my caller ID or a software problem.

I have the caller ID lock up the 622 once. Other than that it is pretty reliable.