Router/GS502 Help!

[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.

[digger16309]

Thanks Tim - I'm going to submit a ticket anyway. My 502 took the hard-coded DNS server just fine (thanks for that fix) but either that or the config glitch, caused it to be cycling unmercifully at 5 am this morning.

It took me almost 30 minutes to get it to play nice again, with about 50 reboots, even after I had it set to a static IP address.

It may be fixed but I'd kind of like to try another 502 and see if it has the same behavior.

One question, the VOIPo servers seem to renew SIP registration on my ATA once an hour - or that's what it looks like on my end. I don't know enough about it. Is there a reason for that re-lease in a short timeframe?

-----------------------

edited for correct term

[voxabox]

Thanks Tim - I'm going to submit a ticket anyway. My 502 took the hard-coded DNS server just fine (thanks for that fix) but either that or the config glitch, caused it to be cycling unmercifully at 5 am this morning.

It took me almost 30 minutes to get it to play nice again, with about 50 reboots, even after I had it set to a static IP address.

It may be fixed but I'd kind of like to try another 502 and see if it has the same behavior.

One question, the VOIPo servers seem to renew the lease on my ATA once an hour - or that's what it looks like on my end. I don't know enough about it. Is there a reason for that re-lease in a short timeframe?

digger16309,
are you sure it's the DHCP lease time not the ATA SIP register expiration?

[digger16309]

digger16309,
are you sure it's the DHCP lease time not the ATA SIP register expiration?

That's what I meant - the ATA SIP register expiration.

Why is that set at 1 hour intervals?

Mostly, I'm just curious about it.

[voxabox]

That's what I meant - the ATA SIP register expiration.

Why is that set at 1 hour intervals?

Mostly, I'm just curious about it.

3600 secs is the default value specified by most ATA/SIP phone manufacturer
I do not recall if there is a specific value recommended by any RFCs
since you're curious, you can consult my library, and let us know

[digger16309]

This problem is now fixed for me.

No more crazy cycling. And I'm not crazy, nor is my network. I feel better now.

Thanks to everyone who provided suggestions that might help, and also to Tim and especially to Ray.