Grandstream Reliability Tip

[chpalmer]

Put in a ticket and tell them that provisioning keeps blanking out your static settings. They have to fix that on their end.

Ive set up my routers to statically assign my equipment their addresses and have no problems this way. ymmv.

[1bird2]

286. I have since moved to the 502 due to other issues. The 502 is much more reliable. As for this issue/tip, I have not made any changes on the 502. Everything is working well and I am inclined to not make any changes at this time with the DNS settings (static) as per the original post of this thread. I subscribe to the "if it ain't broke, don't fix it...."

-bird

[digger16309]

Here's a tip for any of you that want to improve speed on your Grandstreams and make things work a little better. Assign the adapter a static IP and static DNS settings on your network.

While this is not completely necessary, it does speed up booting and wiill improve reliability by eliminating the need to ever change the IP.

I have my GS-502 ATA behind my router.

I just had some sort of glitch where it appeared the ATA had a valid IP address from my router and it showed up in the Vpanel. But the ATA kept resetting itself over and over again about every 10-15 seconds. That caused me to have no phone service basically.

After rebooting everything, no change.

I put the ATA in front of the router, no change.

I put the ATA back behind the router, and all was well again. It stopped rebooting itself.

Now that it is working again, I hesitate to fuss with it. But I can't explain what made it go south all of a sudden late Saturday night and all day Sunday. To my knowledge it's the first time this has happened in the 3 weeks I've had the 502.

If I just make the changes in the ATA, is that all I need to do? Or do I also need to make changes in my router to affect this?

[arth]

I had my UPS fail last night - my local network was down, GS286 lost power as well as DSL modem and router. I restarted everything without the UPS and all came back up except for the GS286. Used Wireshark to take a look and it appeared the GS286 was hung up on trying to get STUN to bind. It had a static IP address on my local network, I repower it several time, no help. I then reconfigured the GS286 for a dynamic IP and it immediately registered and is operational. Not sure what is happening, as some time ago the same happened when the GS286 was configured with a dynamic IP and setting it to static allowed it to become active.

[digger16309]

I had my UPS fail last night - my local network was down, GS286 lost power as well as DSL modem and router. I restarted everything without the UPS and all came back up except for the GS286. Used Wireshark to take a look and it appeared the GS286 was hung up on trying to get STUN to bind. It had a static IP address on my local network, I repower it several time, no help. I then reconfigured the GS286 for a dynamic IP and it immediately registered and is operational. Not sure what is happening, as some time ago the same happened when the GS286 was configured with a dynamic IP and setting it to static allowed it to become active.

Sounds like maybe it might have been related to this?

I believe this is resolved for everyone now.

We had a flood of tickets tonight about this and finally discovered a big issue on our end resulting from a change we just made today.

Basically, we made some final changes to the provisioning servers today and there was an error in the test where the config file being passed to the 502s was not fully correct. When an IP renewed or you rebooted a 502 this evening, it would resync with our provisioning servers and download the bad config. Since it was a bad config, it didn't know what to do with it and just cycled.

We've corrected this now and I think it'll resolve the issue for everyone.

So far in all tickets where we've gotten a response back and in all our internal testing, it's been resolved.

I apologize for the inconvenience and am am going to sit down and discuss our dev to production procedures tomorrow to make sure we're all on the same page and clear that everything is to be tested before being pushed out.

If anyone is still seeing the cycling, please turn your ATA off for a few minutes then reconnect it. Once it syncs back up with us (make take a minute or so), it should pull a valid config file and will likely reboot 1 time.

If you're still having issues, please e-mail support@voipo.com and let us know.