Callcentric workaround firmware
VOIPisGreat:
Quote from: lacibaci on November 02, 2012, 06:48:34 am
Quote from: VOIPisGreat on November 01, 2012, 09:30:40 pm
Can you tell me the settings you use to configure callcentric?
Somebody posted these:
ProxyServer = srv.callcentric.com
RegistrarServer = leave blank
UserAgentDomain = leave blank
OutboundProxy = leave blank
X_ProxyServerRedundancy = unchecked
X_DnsSrvAutoPrefix = checked
SPx Service:
X_KeepAliveEnable = enabled
X_KeepAliveExpires = 120
This is what I'm running right know.
I tried both the setting recommended by CC and the above setting. My obi has been resetting roughly every other day, with the firmware fix installed. Has anyone else seen the same issue?
RoyH:
Quote from: VOIPisGreat link=topic=4497.msg29759#msg29759
My obi has been resetting roughly every other day, with the firmware fix installed. Has anyone else seen the same issue?
I don't have the new firmware but I did have an issue with my Obi100 rebooting every 12 hours. When I enabled remote syslog it turned out the the Obi was trying to renew its DHCP address (halfway through the DHCP lease of 24 hours) and my Netgear router was refusing to renew. When that happens the Obi reboots itself, requests a new DHCP address, and everything is fine.
The cause was a bug in my Netgear router firmware when you try to assign a specific IP address to a device via DHCP. If the address is outside the range of the DHCP pool then the router won't renew it.
http://forum1.netgear.com/showthread.php?t=59228
I changed the assigned IP address to be inside the DHCP pool and the rebooting stopped. Not sure if this is your problem but it sounds similar. Ideally the Obi would negotiate a new IP when it receives a DHCP NAK instead of rebooting.
VOIPisGreat:
Quote from: RoyH on November 08, 2012, 05:27:03 pm
Quote from: VOIPisGreat link=topic=4497.msg29759#msg29759
My obi has been resetting roughly every other day, with the firmware fix installed. Has anyone else seen the same issue?
I don't have the new firmware but I did have an issue with my Obi100 rebooting every 12 hours. When I enabled remote syslog it turned out the the Obi was trying to renew its DHCP address (halfway through the DHCP lease of 24 hours) and my Netgear router was refusing to renew. When that happens the Obi reboots itself, requests a new DHCP address, and everything is fine.
The cause was a bug in my Netgear router firmware when you try to assign a specific IP address to a device via DHCP. If the address is outside the range of the DHCP pool then the router won't renew it.
http://forum1.netgear.com/showthread.php?t=59228
I changed the assigned IP address to be inside the DHCP pool and the rebooting stopped. Not sure if this is your problem but it sounds similar. Ideally the Obi would negotiate a new IP when it receives a DHCP NAK instead of rebooting.
Thanks for the tip. I checked the IP address of the obi and it's within the DHCP range, so I suspect this is not the issue. But I reboot the router in case it's in a weird state which is causing the problem.
I read from DSLR that callcentric has fixed their SRV record so potentially people won't even need the firmware fix anymore. I am going to leave the CC setting for 2 more days and see if the reboot issue will go away.
IrwinFamily:
I have assigned a static IP to my OBi. That would stop all DHCP lease issues. For example, if your subnet is 192.168.1.xxx, your router is likely 192.168.1.1 and your DHCP pool begins with 192.168.1.100. If you assign the OBi an address of 192.168.1.50 you should be fine.
Navigation
[0] Message Index
[*] Previous page