No devices registered in Vpanel

**scott2020** · 02-13-2009 03:02 PM

Last night I had another registration problem. The ATA showed both lines registered, but all calls were going straight to failover (voicemail). Vpanel showed no devices registered. Reboot of the ATA cleared it up. It seems to happen a lot ever since the latest firmware. I have had my ATA behind my WRT54G running Tomato since October and have not had issues until the past few weeks.

For the time being, I am going back to use my Asterisk box and see how things go with that. I am using a Cisco ATA-186 with Asterisk and a couple of provider trunks and things seem good.
Scott

**KenH** · 02-13-2009 04:39 PM

My calls are now going to failover too. Submitting a ticket.

**Brian** · 02-13-2009 04:42 PM

Same for me - just had to reboot the ATA.

**Xponder1** · 02-13-2009 09:04 PM

Originally Posted by VOIPoTim

Would you be interested in swapping it out with a Linksys device?

If you think thats what is best I will gladly ship you this ATA back (and another that is broke has a major audio problem) and you can ship the Linksys but from the following posts I do not think I am the only one who has had a problem in say the last 24 - 36 hours.

Your call. I will also gladly watch it and see if I continue to have a problem and then we can make a decision. I do not want over react.

Lots of possible reasons for the problems. I am positive this ATA will not function in a normal fashion in front of my router. When I had it doing PPPoE connections my connection speed dropped by over half. It is just not a very good router.

Thanks Tim.

**VOIPoTim** · 02-13-2009 09:13 PM

Originally Posted by Xponder1

If you think thats what is best I will gladly ship you this ATA back (and another that is broke has a major audio problem) and you can ship the Linksys but from the following posts I do not think I am the only one who has had a problem in say the last 24 - 36 hours.

Your call. I will also gladly watch it and see if I continue to have a problem and then we can make a decision. I do not want over react.

Yeah definitely not the only one. We're up to 12 reports now, so I agree it is odd for them to all happen around the same time. It's just hard to diagnose a bigger issue since 12 out of thousands really isn't that much.

We're continuing to monitor it in case anything more does come up.

**Vumes** · 02-13-2009 10:28 PM

Count me in as well. I got calls going to my failover and I looked in vPanel and it did not show anything registered. Can I get a Linksys as well??

**VOIPoTim** · 02-13-2009 10:35 PM

Originally Posted by Vumes

Count me in as well. I got calls going to my failover and I looked in vPanel and it did not show anything registered. Can I get a Linksys as well??

Just open up a ticket about it and we'll take care of it.

**Vumes** · 02-13-2009 10:36 PM

Superb. Thanks.

**buckethead** · 02-14-2009 12:18 AM

Just to add I had same problem today as well again although a powercycle fixed it. I did not know when it lost registration or how long I was down though. Did not open new ticket though as I continued to use a ticket from day before on losing registration as well.

**christcorp** · 02-14-2009 12:55 AM

Concerning the simring question. VoipO is set up that you CAN call your VoipO line FROM the phone (In my case the cell phone) which happens to be your simring. I do it all the time. My cell phone IS my simring AS WELL AS my Failover. I call FROM it to my house all the time without problems. Unless of course if VoipO isn't registered or is down. In that case, I would INSTANTLY get me cell phone voice mail because Failover kicks in, but I am talking from the cell phone which happens to be the failover. but for simring; if all is working well, I can call FROM the simring device to the voipo device. Oh, and for what it's worth; after rebooting that one time early this morning; I haven't had any issues. I've been on the road a lot today. I've called back home to the voipo line and it has gone through without problems. later... mike.....