Grandstream Reliability Tip

Quote:

---

Originally Posted by 1bird2

Setting a static IP does not seem to work for me.

I log in as Tim mentions. Set IP address to a private IP in my network (NAT'd behind a FW), set subnet, default route and add two public DNS server addresses (my ISP DNS servers)

I update this info, select "Update". Message returned that values are saved, reboot to take affect. I reboot device remotely. Wait 30 secs and login again.

THe static IP is set (as I login with the new IP address in the browser), but the DNS entries are gone and all set to 0.0.0.0. I also notice I have lost dial tone and LED on GS is now flashing on / off with red color.

Log back in to GS. Reset to Dynamic (note, I have reserved an IP for the GS by MAC address), save configuration, reboot GS. Everything works after I do this (i.e. get dial tone, can make call, phone rings when I call a Virtual number I have assinged to the GS -- as I am waiting for my port to complete).

Thoughts anyone?

Thanks

1bird2

---

Are we talking about the 286 or the 502?

I tried to set the 286 I have and found the same problem. DNS is back to 0.0.0.0 and no joy.

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.

chpalmer I was testing, but I guess I should put in a ticket. I also have my router providing the IP via MAC address like you. So, once I put it back to "my way" I again have joy. I read what 1bird2 had said and was testing and confirming for myself. I would imagine Tim would read this and look into it.

FYI - the IP address stayed only the DNS changed.

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

Quote:

---

Originally Posted by 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

---

Glad to hear. The 502 does work for 99% of customers out of the box with no tweaking usually. Overall, it's a great device.

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.

Quote:

---

Originally Posted by 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.

---

Sounds like maybe it might have been related to this?

Quote:

---

Originally Posted by VOIPoTim

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.

---