Printable View
Cable Modem --> Router --> 502 --> PhoneQuote:
Originally Posted by VOIPoTim
This worked fine for the 286 and previously a PAP2T. I had no issues with either one.
I did try putting it in front of the router and got the same issue - constant cycling of the 502. Going router to router would not be my first preference.
That might be it.Quote:
Originally Posted by dswartz
It is maddening to deal with because there are less than 10 seconds to make changes each time before it blinks out and I get locked out of the interface until it reboots.
The only way to get it to hold is to switch back to dynamic, then take several chances on restarting, modem, router, ATA in such an order that the ATA likes. It never seems to be the same each time. That's been true since I got it.
I think the suggestion dswartz made may solve a lot of this and also explain why these are problem-free when connected to a modem directly.
I think he's saying the LAN IP range of the GS is conflicting with the router's range so the GS is confused when you hook it up to the LAN port and it gets a WAN IP within its local IP block.
To be completely safe, can you just set the LAN portion of the GS to use an entirely different block like 10.175.1.1 or something that's not remotely in the same block?
I hadn't thought about that much, but it makes sense as to why it would loop sometimes if it's thinking the WAN IP is suddenly in the LAN IP range.
Didn't see this part. In that case it's very possible that it is defective.Quote:
Originally Posted by digger16309
I'm having someone look at the DNS stuff though to see if that could be related.
If that's not the issue and they think it's defective too, then we can overnight a replacement tomorrow.
I hesitate to mess with it right now for fear I will take another 30 minute odyssey of cycling hell.
My Linksys router DHCP range is 192.168.1.101-250
The 502 LAN port is not enabled and is running with different IP address even if it were enabled.
It currently reads as this:
Device Mode: Bridge
NAT maximum ports: 1024 (range: 0 - 4096, default is 1024)
NAT TCP timeout: 3600 (range: 0 - 3600, default is 3600)
NAT UDP timeout: 300 (range: 0 - 3600, default is 300)
Uplink bandwidth: Disabled
Downlink bandwidth: Disabled
Enable UPnP support: No
Reply to ICMP on WAN port: Yes (Unit will not respond to PING from WAN side if set to No)
WAN side HTTP/Telnet access: Yes (WAN side access will be rejected if set to No)
Cloned WAN MAC Addr: (in hex format)
Enable LAN DHCP: No
LAN DHCP Base IP: 192.168.2.1 (base IP for the LAN port, default is 192.168.2.1)
LAN DHCP Start IP: 100 (default is 100)
LAN DHCP End IP: 199 (default is 199)
LAN Subnet Mask: 255.255.255.0 (default is 255.255.255.0)
DHCP IP Lease Time: 120 (in units of hours, default is 120 hours or 5 days)
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.
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
digger16309,Quote:
Originally Posted by 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.Quote:
Originally Posted by voxabox
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 manufacturerQuote:
Originally Posted by digger16309
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:)