mgazza, short post but really good detective work and solution. I bet many people's problem would be solved by simply switching the ntp server. Here is my story:
I have been using OBi110 for the last 6 months in the hope of slowly transitioning the family away from a POTS line. The OBi works well most of the time, but there have been time when an outbound call could not be made through google voice. At those time the LED with the phone icon was off and the Obi would should offline in OBiTalk. The OBi would not show in the DHCP lease table of my router. Based on this I switched to a static IP.
The static IP worked well but the device would often enter a state where the network light would flicker fast without a connection and would show as offline in ObiTalk. However, when calling ***1, the static IP was read back properly. Restarting the device with ***9 would work but only for a few hours.
Many folks said that support asked them to switch the router. I had a spare new N-router at hand of different make and model, which I tested with the same result. This pretty much told me that the router is not the issue and that this is a firmware bug.
Stumbling at mgazza's hint of ntp dns queries, I changed the ntp server to
time.nist.gov, which I typically use, and all has been well since then.
I have had trouble with
ntp.pool.org on my firewall server as well and those problems went away with the same ntp server change.
Thanks again for the debug help. I was never able to get wireshark to spit out the network traffic from the Obi hardwired connection, so this hint was greatly appreciated!
Cheers,
rev
