Steve, again. Thank you for your reply! I meant to ask a while ago, but where in WA?
We've lived in parts of the PNW before. Have a family member up there right now in WA selling a house a matter of fact!
Quote from: SteveInWA on July 26, 2015, 03:33:50 PM
I don't want to get into a pissing match with you, over you assessment of me being "foolhardy", but I will say, with confidence, that I am the leading expert here on Google Voice, having worked directly with Google engineering for several years diagnosing and solving issues.
So, you can't possibly be incorrect about this? Right?
That's one the major reasons I don't post here. I post on many, many, many other support forums, not looking to solve our issues (because we generally do that on our own), but to help others. I don't really come here because there is, among a rare few, a real case of hyper-elitism. I'm not singling you out here - it's among a few users, and you aren't nearly as bad as some.
If this were a medical diagnostic, using the rule out method with the one very small fact you have would be extremely foolhardy. There's no corroboration. And I've seen plenty of cases where the Google Voice forum regulars have maintained, "This is a GV issue and/or feature. Nothing you can do. Live with it." and it turned out tweaking a setting here or there solved the issue.
I'm not saying your opinion here is wrong. It's valid. But to say it is the ONLY valid one - and then to use the hyper-elitist mantra of, "I've been doing this for XX years, I can't be wrong" excuse - absolutely IS foolhardy. And I won't mince words over that. Sorry.
If we want to compare experience levels, DH and I have been working in IT since the 70's. Collectively, we have far more knowledge than many combined on this forum. Than many combined on a lot of forums, honestly. Including quite a bit of VoIP and PBX experience. But that doesn't address the problem or its solution, so to me, it's pretty useless. I don't see the need to bring it up except as a comparative measurement in the urination department?
Quote from: SteveInWA on July 26, 2015, 03:33:50 PM
All the evidence you have posted so far (after edits)
I've edited to ADD things and clarify things, not take things away. I wrote the OP pretty late and wasn't as focused as I should have been.
Uhhh.... sorry? I try to fix the mistakes or oversights when I catch them.
Quote from: SteveInWA on July 26, 2015, 03:33:50 PM
...indicates that this has absolutely, positively nothing whatsoever to do with any setting or other issue with your OBi device. The fact that it behaves somewhat differently when you attempt to answer the call on Hangouts vs. OBi doesn't change anything. It's simply a different manifestation of the same root cause of the failure.
It very well may be a GV issue. It very well may be a caller provider issue from the other end.
But it ALSO could very well be something can be tweaked in the OBi to solve/fix it (not a problem with the OBi per se, but one that it can address. Savvy?).
We don't know. That's why we're here. To get more ideas on what it could be, and other things to check.
Not to be in a pissing contest, as you so eloquently put it.
Quote from: SteveInWA on July 26, 2015, 03:33:50 PM
There is something unique about this caller's telephone service, which you have hinted at, but have been unwilling to disclose, that is causing the symptom with regard to GV's ability to correctly answer the inbound call.
That absolutely is a possibility. There's no ruling that out for now.
Quote from: SteveInWA on July 26, 2015, 03:33:50 PM
As long as you don't have multiple examples of callers who cannot reach your inbound GV number, or whose calls result in some abnormal behavior, then there is nothing to fix or no setting to change, on the OBi or GV side, to change the behavior of this one caller's number.
We don't use this inbound number or number(s) for many other calls. From the limited tests we've done (from our own phones, services, test services, etc), these numbers appear to function the way they are intended. But again, that doesn't rule out something we could have possibly overlooked.