Obi/Google Voice disconnecting overnight
restamp:
This likely has nothing to do with the problem being talked about here, but for completeness, this morning, I discovered that when calling out on my primary GV line (which I pressed into regular telco service via an Asterisk server long before the terms OBiHAI and OATH2.0 ever entered our collective vocabularies) the audio was consistently one-way: I could hear the party I called, but they could not hear me. I switched over to GV line 2, which uses OATH2.0 on my OBi-202 and all was well. (Both GV1 and GV2 terminate on my OBi-202 although, to the OBi, GV1 is just a SIP connection to Asterisk.) After concluding the calls, I examined the OBi's Status page and everything looked good but test calls continued to fail. I then (1) rebooted Asterisk and the problem persisted, and finally (2) rebooted the 202 and the problem resolved itself.
I don't recall having a problem with 1-way communications in the past, at least not since acquiring the OBi. As I said, my problem today may be coincidental, or it may be another indication of some overarching GV problem. Guess it will be interesting to see if it recurs.
SteveInWA:
This has absolutely, positively nothing whatsoever, not at all, in no way, uh-uh, to do with Google "pulling the plug". Google has no idea what model of OBi you are using, nor how long you've been using it, nor do they care, as long as your device is using OAUTH 2.0 authentication.
If it had been one user reporting this, then it would have been the now-tiresome answer: your OBi hasn't been updated in years, it's still using the old, pre-OAUTH authentication, and you need to upgrade firmware, reset the device and re-configure Google Voice on a SPx.
However, this is apparently happening to 100/110 models that are running current firmware and are using OAUTH authentication.
It looks like there's a problem with the OAUTH keys that are being generated for these models (a Obihai problem), and nothing more. I'm going to see what I can find out, but if any of you have a device under warranty, please open a ticket and point to this thread.
SteveInWA:
I reached out to my contacts at Obihai, and they're looking into this now.
LetsTalk:
Steve, I also have an ancient obi110 that has worked very well for years, and it suddenly stopped this afternoon, no calls in or out possible; I followed your instructions as per the link below
http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460
and although Obitalk let me delete the SP1 GV configuration (SP2 is an anveo account just for 911), I couldn't reconfigure SP1 - entered a circular hell where I keep clicking on the right buttons to go thru reconfiguration, but it just always brings me back to the Obitalk device config page, with the $10 message and completely unresponsive buttons (I've always set this up myself, this is driving me crazy).
Even if this is a glitch, when it's fixed I'll still be without phone service with my deleted SP1 and no apparent way to get it working again. Can you suggest anything else to get my GV set up again?
Thank you in advance - your messages and instructions on this forum have solved most of my Obi problems in years past!
SteveInWA:
Last night, I took my old 110 out of storage and set it up with two Google Voice test accounts, which worked fine.
Today, the two accounts are still working, but the portal no longer allows me to configure the device at all. Clicking the SP1 or SP2 links just circles back to the yellow message about needing a firmware upgrade, which is not the case.
We will just have to wait and see what Obihai says about it. Speculation at this point would just be gossip.
Navigation
[0] Message Index
[#] Next page
[*] Previous page