No devices registered in Vpanel

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

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

Same for me - just had to reboot the ATA.

Quote:

---

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.

Quote:

---

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.

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?? :rolleyes:

Quote:

---

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?? :rolleyes:

---

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

Superb. Thanks. ;)

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.

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.....

For those of you that were experiencing this issue, check the latest reply to your tickets and reboot.

Here is what was sent out earlier to those with tickets in:

-----
We've been monitoring the logs closely throughout the night for a handful of customers reporting this issue. While it's not a widespread issue, we were finally able identify a similarity with the 15 or so customers seeing their registrations drop and have applied a fix for you.

It appears that in some cases, small amounts of network latency (delay) were causing the device's periodic re-registration to fail. The device was waiting for a response and "timed out" before it got the response back. We've made an adjustment to the device so that it will wait longer for a response before giving up, so it should be more resilient in the case of any network delays either on our end or on the path between our network and your ISP. The device should now be waiting plenty of time for this and not timing out prematurely.

Please reboot your adapter so it can pick up this change and establish a new connection with us.

This should resolve the issue for you. Please update us next week and let us know if you continue to see any issues or if things are stable for you after this change. We apologize for any inconvenience this has caused and appreciate your patience.
-----

I'm going to sleep now, but will explain more later this weekend. This is not a system-wide change since most users aren't experiencing the issue.

If you experience a registration loss, just open a ticket and this can be applied to your account as well.

What about us BYODer's having registration issues ? A reboot won't pick up the changes. At least I use a PAP2T so I can apply the changes myself, hopefully.

Quote:

---

Originally Posted by Montano

What about us BYODer's having registration issues ? A reboot won't pick up the changes. At least I use a PAP2T so I can apply the changes myself, hopefully.

---

Same here. Would be nice to know the changes as they are incorporated.

Quote:

---

Originally Posted by burris

Same here. Would be nice to know the changes as they are incorporated.

---

uhm, I'm wondering why you guys (your linksys/sipura ATAs) having registration issues...
Besides a brief outage (which the ATA recovered without any intervention), my SPA-1001 has experienced no problem.
I do not think I did anything special while configuring it to work with VOIPo
BTW, the linksys/sipura ATAs seem to offer better audio quality, particularly on the first few seconds of outbound calls whereas the GS ones suffer minor clicks and pops. this probably due to the way the linksys ATAs handle the SLIC/codec interface with hardware instead of the GSs, DSP code

I forgot to mention that my ATA is configured register at 1hr interval

Quote:

---

Originally Posted by voxabox

uhm, I'm wondering why you guys (your linksys/sipura ATAs) having registration issues...
Besides a brief outage (which the ATA recovered without any intervention), my SPA-1001 has experienced no problem.
I do not think I did anything special while configuring it to work with VOIPo
BTW, the linksys/sipura ATAs seem to offer better audio quality, particularly on the first few seconds of outbound calls whereas the GS ones suffer minor clicks and pops. this probably due to the way the linksys ATAs handle the SLIC/codec interface with hardware instead of the GSs, DSP code

---

As I mentioned, I had no problem with my SPA during the beta as well as running it for some time thereafter, due to working out the kinks with the 286 and such.
I never had a problem with the SPA then.

I did have a few kinks with the 502 and I have left it on provisioning when I use it.

Yesterday, I turned up my SPA again in order to see if there were any issues with the new servers or with the clone process.
Thus far, with the exception of the *codes, which are quite irrelevant for the most part for me, service has been rock solid and I do believe the quality is better and I do hear the the first few seconds you mentioned only with the 286/502. I did refer to this during the beta testing days, but again, I'm not sure how many users would even be aware or care about this.
I'm a nut, so I look for and generally find these kinds of quirks because my main interest is to have my phone talk and listen reliably and clearly...and that it does.
Insofar as wanting to know what tweaks are being done at the system level, I suppose that comes with the territory.:p

Besides that, I will always feel a need to pay attention to all aspects in order to offer any feedback that might be helpful to Tim.

Quote:

---

Originally Posted by burris

As I mentioned, I had no problem with my SPA during the beta as well as running it for some time thereafter, due to working out the kinks with the 286 and such.
I never had a problem with the SPA then.

I did have a few kinks with the 502 and I have left it on provisioning when I use it.

Yesterday, I turned up my SPA again in order to see if there were any issues with the new servers or with the clone process.
Thus far, with the exception of the *codes, which are quite irrelevant for the most part for me, service has been rock solid and I do believe the quality is better and I do hear the the first few seconds you mentioned only with the 286/502. I did refer to this during the beta testing days, but again, I'm not sure how many users would even be aware or care about this.
I'm a nut, so I look for and generally find these kinds of quirks because my main interest is to have my phone talk and listen reliably and clearly...and that it does.
Insofar as wanting to know what tweaks are being done at the system level, I suppose that comes with the territory.:p

Besides that, I will always feel a need to pay attention to all aspects in order to offer any feedback that might be helpful to Tim.

---

ic, I should have paid more attention - my wife always tells me so;)

I have not read the many replies before this and I am about to reboot my ATA but my phone has been messed up all day.

I tried calling home this morning and it went to a busy tone every time I called. I then called my land line and it was busy so I pieced together that all my calls are going to the fail over number (it was busy because my son was on the land line and I dont pay for call waiting anymore because I dont need it with VOIPo right lol). I sent a message about it to support from work.

It is now 3:40PM. I am off work and at home and I can dial out but all calls are still going to the fail over. About to reboot my ATA. I did read Tim's previous reply but I thought I would post it here anyway because I did not get a response to my ticket. [#GNN-128511]. Hopefully the before mentioned fix will resolve the issue. I have monitored my internet connection and I am positive I have not lost connection since I last rebooted my router.

EDIT after rereading Tim's response I have to wonder if this fix was applied to me or not. By the post it sounds like only the affected people were so I might need it applied. Have rebooted and I can get calls again.

Quote:

---

Originally Posted by Xponder1

I have not read the many replies before this and I am about to reboot my ATA but my phone has been messed up all day.

I tried calling home this morning and it went to a busy tone every time I called. I then called my land line and it was busy so I pieced together that all my calls are going to the fail over number (it was busy because my son was on the land line and I dont pay for call waiting anymore because I dont need it with VOIPo right lol). I sent a message about it to support from work.

It is now 3:40PM. I am off work and at home and I can dial out but all calls are still going to the fail over. About to reboot my ATA. I did read Tim's previous reply but I thought I would post it here anyway because I did not get a response to my ticket. [#GNN-128511]. Hopefully the before mentioned fix will resolve the issue. I have monitored my internet connection and I am positive I have not lost connection since I last rebooted my router.

EDIT after rereading Tim's response I have to wonder if this fix was applied to me or not. By the post it sounds like only the affected people were so I might need it applied.

---

If you didn't get a reply to the ticket, you wouldn't have had this fix applied. I just applied it for you and replied, so once you reboot you'll be able to pick it up.

Quote:

---

Originally Posted by VOIPoTim

If you didn't get a reply to the ticket, you wouldn't have had this fix applied. I just applied it for you and replied, so once you reboot you'll be able to pick it up.

---

Thanks Tim rebooted as requested.

Quote:

---

Originally Posted by Montano

What about us BYODer's having registration issues ? A reboot won't pick up the changes. At least I use a PAP2T so I can apply the changes myself, hopefully.

---

The key with the Grandstream fix was increasing the registration "T Values" which are related to how long it waits for a registration transaction to "complete". If there's any latency or delay in response, a higher value will allow the device to wait longer for it to accommodate that.

I don't know the specific values for it in the PAP2T personally but can get those for you next week.

With the PAP2Ts set to register every minute, I don't think we've had any other reports of drops since even if something like that did cause it to timeout, it would pick back up the next minute.

Interesting Tim. I got the generic response to my ticket that everyone else got and assumed a fix had been found for all. Now it makes me feel as if I was lumped in with everyone else, and no one really looked at my issues. I was quite clear in my ticket that I use a PAP2T.

Here is the initial ticket entry:
"It seems like every 2 or 3 days my PAP2T looses registration over night. It's down this morning and a reboot did not seem to help. I'm on central02."

Quote:

---

Originally Posted by Montano

Interesting Tim. I got the generic response to my ticket that everyone else got and assumed a fix had been found for all. Now it makes me feel as if I was lumped in with everyone else, and no one really looked at my issues. I was quite clear in my ticket that I use a PAP2T.

Here is the initial ticket entry:
"It seems like every 2 or 3 days my PAP2T looses registration over night. It's down this morning and a reboot did not seem to help. I'm on central02."

---

Sorry about that. It was likely because it was BYOD. They should have responded directly, but we've been stressing that we do not provide BYOD support internally to our team a lot lately since it was making up the bulk of our time spent on support calls slowing all the other response times down, so that's likely why. They should have still replied mentioning BYOD though vs a reply with no real useful info for your situation.

The T values and 1 minute registration interval should help you get to a point of being problem-free again.

Thanks for the info Tim. Hopefully BYODers are entitled to support when they are experiencing the same loss-of-registration issues as non-BYODers. I can totally understand not supporting configuration, etc... but when a service works perfectly for 2 1/2 years with no changes to a device, then all of a sudden it won't register on repeated occasions and others are experiencing the same issues, I would hope support would be given.

Edit: Not saying I haven't been given great support, just wondering where you are going to draw that fine line. :)

Well i haven't gone this full thread specially the last 1 week. I started seeing the problem devices not registered on my HT502 since sometime after 8:00pm on 2/13 and till now. Outgoing seems to be working fine. Incoming goes to failover i.e voicemail right now.
I just logged in to HT502 and it show the below.
System Up Time: 23:50:37 up 3 days

Quote:

---

Originally Posted by myvoip07

Well i haven't gone this full thread specially the last 1 week. I started seeing the problem devices not registered on my HT502 since sometime after 8:00pm on 2/13 and till now. Outgoing seems to be working fine. Incoming goes to failover i.e voicemail right now.
I just logged in to HT502 and it show the below.
System Up Time: 23:50:37 up 3 days

---

I just applied the mentioned change to your account. Reboot and it should pick it up. Should be smooth sailing after that.

Tim, Thanks. Rebooted the HT502 as requested and now it shows 1 line registered in devices option in Vpanel.

Quote:

---

Originally Posted by myvoip07

Tim, Thanks. Rebooted the HT502 as requested and now it shows 1 line registered in devices option in Vpanel.

---

Yeah. Both lines are registered though. Your 2nd line is now a real clone though and not just two registrations, so you'll only see 1 in vPanel. Both will work though.

It seems that I don't have any devices currently registered. I'll reboot in a few, but wanted to post this first.

Both my lines are registered. Been that way for 3 days straight now :)

Quote:

---

Originally Posted by Montano

Both my lines are registered. Been that way for 3 days straight now :)

---

Not to gloat, but mine have been flawless for a while now! (I love the GS HT502!)

Although the HT502 worked O.K., The PAP2T just seems to be more solid.

To be fair, maybe the registration issues coincided with my assessment of the 502 at the time, but I will exchange them from time to time to offer some comparisons, if there are any practical differences.

Meanwhile, the service is rock solid and the WAF is 100% positive, and I can stand up straight again.;)

Quote:

---

Originally Posted by usa2k

Not to gloat, but mine have been flawless for a while now! (I love the GS HT502!)

---

FWIW, this is what I'm using :)

I just lost registration after 7 days. Vpanel says no registration. But the GS adapter says its registered. I started ethereal and put the ata on a hub. There was no data for 5-10 minutes from the ATA. It is supposed to send registration every minute. Just rebooted and its registered in the Vpanel and I can see SIP traffic on ethereal. I really think there is some problem with the new firmware.

I had DHCP before. I set static IP address for the ATA and will monitor to see how it works

Quote:

---

Originally Posted by sr98user

I just lost registration after 7 days. Vpanel says no registration. But the GS adapter says its registered. I started ethereal and put the ata on a hub. There was no data for 5-10 minutes from the ATA. It is supposed to send registration every minute. Just rebooted and its registered in the Vpanel and I can see SIP traffic on ethereal. I really think there is some problem with the new firmware.

I had DHCP before. I set static IP address for the ATA and will monitor to see how it works

---

Hmm, I've been up & running w/o problem for a number of days as well, but I checked just now and vPanel shows no device registered. Incoming calls go straight to voicemail. A PAP2T is supposed to be arriving soon, so perhaps that will address the problem.

I am having much better luck (staying registered) with the PAP2T vs the 502. Haven't dropped yet! (Hope I didn't just jinx myself ;) )

Quote:

---

Originally Posted by sr98user

I just lost registration after 7 days. Vpanel says no registration. But the GS adapter says its registered. I started ethereal and put the ata on a hub. There was no data for 5-10 minutes from the ATA. It is supposed to send registration every minute. Just rebooted and its registered in the Vpanel and I can see SIP traffic on ethereal. I really think there is some problem with the new firmware.

I had DHCP before. I set static IP address for the ATA and will monitor to see how it works

---

Out of curiosity, did your DHCP issue IPs for 7 days and maybe it renewed?

Quote:

---

Originally Posted by VOIPoTim

Out of curiosity, did your DHCP issue IPs for 7 days and maybe it renewed?

---

Actually, see this:

http://forums.voipo.com/showthread.php?t=1180

Quote:

---

Originally Posted by VOIPoTim

Actually, see this:

http://forums.voipo.com/showthread.php?t=1180

---

Reboot put me back online. Thx.

Quote:

---

Originally Posted by VOIPoTim

Out of curiosity, did your DHCP issue IPs for 7 days and maybe it renewed?

---

I have a static DHCP binding in my router for the ATA. My router says that the lease expiration is Infinite because of the static binding. But my default lease is 7 days for other devices. But the ATA has been up for more than 7 days, close to 8 days. Also, I am able to get to the WEB interface of the ATA. So it has an IP and and it is responding to HTTP requests.

I also noticed in my router logs that in the past 7 days the ATA port status went down/up about 3 times. Usually comes back within 10 seconds. I am not sure why the ATA is doing it. None of my other ports go down. But when I lost registration, the ports status was up.

I just got it again. No devices registered to the servers... I re-opened the ticket and hoping to get the GS swapped out for a Linksys... A reboot to the device corrected the problem.