Receive E-Mail?

**carlquist** · 02-22-2009 08:10 PM

Received it here. Thanks for the update.

**Xponder1** · 02-22-2009 08:14 PM

Tim,

Just a thought. The IVR command ***999 reboots the ATA. For some folks it may be easier than unplugging it.

Thanks again,

**Xponder1** · 02-22-2009 08:33 PM

Tim if this fixes the issue are you going try setting them back so they do not hammer your servers every minute? All those adapters connecting every minute sounds like a big DDOS attack bandwidth wise.

**scott2020** · 02-22-2009 08:36 PM

I also received the email. I haven't been using the 502 though so I am probably no help!

**VOIPoTim** · 02-22-2009 08:41 PM

Originally Posted by Xponder1

Tim if this fixes the issue are you going try setting them back so they do not hammer your servers every minute? All those adapters connecting every minute sounds like a big DDOS attack bandwidth wise.

No immediately changes with it. Right now the bandwidth/load from it isn't really anything we're worried about.

**Brian** · 02-22-2009 08:47 PM

Originally Posted by VOIPoTim

No immediately changes with it. Right now the bandwidth/load from it isn't really anything we're worried about.

I guess my question, from a customer standpoint, is would I be more at-risk this way? As you said, the GS has issues when there is any network latency for registration - if the interval was set to 30 minutes (or something longer than 1 minute), would the connection be less prone to network lag, since it wouldn't be attempting to register as often? Or will this all be a non-issue if DNS was the culprit?

**Xponder1** · 02-22-2009 08:49 PM

Originally Posted by Brian

I guess my question, from a customer standpoint, is would I be more at-risk this way? As you said, the GS has issues when there is any network latency for registration - if the interval was set to 30 minutes (or something longer than 1 minute), would the connection be less prone to network lag, since it wouldn't be attempting to register as often? Or will this all be a non-issue if DNS was the culprit?

Kind of why I asked. Maybe I am misunderstanding but it sounded to me like Tim thinks they finally figured out what was causing the GS units to act up. If thats the case 1 minute should not be needed.

You can always test it on my line I do not mind being a test subject if I know its coming

**fisamo** · 02-22-2009 09:04 PM

Also got the note. Glad to hear/read that you found a 'significant issue' and hope that it's the root cause.

**bdyelton** · 02-23-2009 02:06 PM

Originally Posted by Xponder1

Tim,

Just a thought. The IVR command ***999 reboots the ATA. For some folks it may be easier than unplugging it.

Thanks again,

Thanks for that

**fisamo** · 02-23-2009 02:25 PM

Originally Posted by Xponder1

Tim,

Just a thought. The IVR command ***999 reboots the ATA. For some folks it may be easier than unplugging it.

Thanks again,

One other point--this code only works for the Grandstream ATA. I don't know if the reboot command on the PAP2 is disabled by provisioning (or password protected--not sure why it would be), but if it's not restricted, the reboot sequence on the PAP2 is to dial **** (to access the IVR menu) and then type in "Reboot" (732668#). That works well if you don't want to mess with wires.