Outage - 1AM Central

**VOIPoTim** · 03-04-2009 02:48 AM

Since network blips, etc will always occur with a service that uses the public internet, it's critical that we get the remaining Grandstream adapters used behind a NAT to ALL be re-registering consistently.

Again, we're now shipping PAP2s out by default and only sending the HT502s out by request so in the future this would not come up.

We're evaluating options for dealing with the 10% of so of our HT502s that are still not re-registering. We've considered possible replacing them all with PAP2s but are working with Grandstream to try to exhaust other options before doing this. They've asked us to give them a week and they're going through logs. We're going to let them work on it and will continue to evaluate all options for dealing with them.

Again virtual all PAP2 users and Grandstream HT502 users NOT behind a router will automatically re-register and these outages will be self-correcting.

It's the Grandstream HT502s behind a router that still have about 10% not doing it.

**burris** · 03-04-2009 04:51 AM

Yep..

Just got up and found both my PAP2s online as you described, with no problems.

**Xponder1** · 03-04-2009 06:01 AM

Thank you for the heads up. I am one of the few it seems.
"You do not currently have any devices registered to our servers! "

Thanks Tim,

**NY Tel Guy** · 03-04-2009 09:42 AM

Originally Posted by VOIPoTim

.......Again virtual all PAP2 users and Grandstream HT502 users NOT behind a router will automatically re-register and these outages will be self-correcting.

It's the Grandstream HT502s behind a router that still have about 10% not doing it.

I am also a member of the great "502 unwashed" whose adpater is not registering in a NAT environment.
I am not home now so I cannot re-boot it but I guess if I am not home, I can't miss the calls that I would not have been home for.....

**dcshobby** · 03-04-2009 12:23 PM

We are also behind a NAT with the 502 and we lost registration again. This is really getting sickening and if the only way to fix it is to move to a PAP2, count us in because we are sick of restarting the 502 all the time. If new firmware can fix the 502 though, we would gladly hold onto it.

**GTOJim** · 03-04-2009 12:56 PM

I have missed all of the fun.

My GS-502 hasn't missed a beat, have not had any registration issues that I'm aware of.

I have one of the first GS-502's still using the original firmware it shipped with. My 502 is behind a router, static IP setup for it with port forwarding. Everything has been working beautifully with one exception. It didn't update to a newer firmware which might be a good thing.

**VOIPoTim** · 03-04-2009 01:16 PM

Originally Posted by GTOJim

I have missed all of the fun.

My GS-502 hasn't missed a beat, have not had any registration issues that I'm aware of.

I have one of the first GS-502's still using the original firmware it shipped with. My 502 is behind a router, static IP setup for it with port forwarding. Everything has been working beautifully with one exception. It didn't update to a newer firmware which might be a good thing.

The other big thing too is that you only have 1 line configured, so the HT502 has nothing to get confused with.

**wagnerb** · 03-04-2009 04:17 PM

PAP2T behind a router. With the exception of inbound call disconnects around 3:30 this afternoon all seems back in order now.

**stason99** · 03-04-2009 06:24 PM

I am on HT502 connected directly to a modem. No Router. But I lost registration anyway. I think these problems will never end….. Unbelievable. VOIPo should give a refund for every day on outage.