Obi w/ Google Voice: calls dropping w/ "no service"

[JLJomatic]

Using my OBi 100 (latest available firmware installed) with a Google Voice account and everything works fine except for a new phenomenon: calls are being dropped (or timed out) after approx 5 mins, at which point the "phone" LED (right) on the OBi goes dark and trying to connect a call results in a "there is no service available" message. Resetting the OBi by dis / reconnecting the power supply solves this, but it keep recurring. Anyone experiencing this and have any ideas on a cause and solution? It's a major annoyance.

Any other tech details provided as needed.

PS: Just saw and applied the "full-duplex" setting and we'll see. Meantime any other hints and allegations appreciated. ;-)

[SteveInWA]

This sounds like a flaky home broadband service issue, or perhaps a hardware problem with your home network devices (cable or DSL modem, router, switch).

[JLJomatic]

This sounds like a flaky home broadband service issue, or perhaps a hardware problem with your home network devices (cable or DSL modem, router, switch).

Always possible, though all other functions/connections to/from the router are working normally. Barring a hardware failure with the OBi itself, hopefully it's the duplexing setting. I wish there was a free test call line I could dial and leave open for 10-15 minutes, since there are so few people I actually want to talk to for that long, to test it... 

[avenger49]

Don't think it's a hardware problem since I have the same issue. I works for a while, then the light on the right goes out and I have to power cycle the box in order for it to come back on. I've had success removing the device from the dashboard and then re-adding it and that seems to fix the issue for a time, but the problem always keeps coming back whether it's hours, days, or sometimes weeks later. If I had to guess, they are probably rejecting the device after a time because they want that extra $10 a year for support.

[Lavarock7]

Anytime I see a symptom described as "about every 5 minutes" I start thinking about timers.

5 minutes could be a timer of 300 (60 *5) or a magic number of 256.

It may be something completely different but seemingly consistant outages could be some timer being triggered. Perhaps revalidation, DHCP, refresh, etc. Ramdom hardware issues aren't as consistant.

[SteveInWA]

If I had to guess, they are probably rejecting the device after a time because they want that extra $10 a year for support.

B.S.  No such thing is happening.