No devices registered in Vpanel

**VOIPoTim** · 02-14-2009 03:32 AM

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.

**Montano** · 02-14-2009 08:26 AM

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.

**burris** · 02-14-2009 10:02 AM

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.

**voxabox** · 02-14-2009 11:55 AM

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

**burris** · 02-14-2009 12:17 PM

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.

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.

**voxabox** · 02-14-2009 12:30 PM

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.

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

**Xponder1** · 02-14-2009 03:46 PM

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.

**VOIPoTim** · 02-14-2009 03:50 PM

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.

**Xponder1** · 02-14-2009 03:52 PM

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.

**VOIPoTim** · 02-14-2009 05:48 PM

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.