How to get OBi202 to reconnect to network after network outage ends?
Mango:
Since you have DD-WRT, we have some more troubleshooting tools at our disposal.
If my guess was wrong and X_ProxyServerRedundancy does not solve the problem, I suggest you check /proc/net/ip_conntrack to see if a NAT connection is corrupted.
While the problem is happening, navigate to Administration >> Commands. Run the following commands one at a time, and post the results. If your public IP address appears, you can mask the last two octets with X to protect your privacy.
nvram show | grep ct_udp_timeout
grep obi.ip.address /proc/net/ip_conntrack
Obviously, replace obi.ip.address with its actual IP address.
That will give us the information we need to adjust your timeouts. However, I'm optimistic that X_ProxyServerRedundancy will work. This will cause the OBi to register to sip.ca.anveo.com if a corrupted NAT connection prevents it from reaching sip.anveo.com, and vice-versa.
Keep us posted.
xsgbloom:
Okay, I have more information...
When I pull the plug on the network (without power cycling the OBi202), all of my lines appear on OBiTALK as "Service not configured" with my Anveo line showing:
Retrying Register (server=67.212.84.21:5010
Eventually, the Anveo service registers, but my other services are not registering/no longer configured.
After a reboot of the OBi202, the situation remains the same; the OBi seems to have lost the configuration for my family's Google Voice accounts.
I suspect that troubleshooting the networking issue I've had for a long time is now being hampered by a new issue/OBi change in how it's working with Google Voice, so let me sort out voice before retesting. The fact that the connection to Anveo automatically re-established is a distinct positive.
xsgbloom:
Coolness. Google Voice is configured and the OBi device reconnected following a brief network drop. Loops like the configuration adjustment did the trick!
It looks like the Google Voice reconfigurations were the result of OBi changes (from ClientLogin to using OAuth) that I must have missed somewhere along the way. Anyway, problem seems to be solved.
Thank you Mango! Sorry we didn't get to delve into my DD-WRT issues!
Navigation
[0] Message Index
[*] Previous page