OBi + GV + Inbound Private Callers = Dead air
SteveInWA:
Let's get this out of the way: this has nothing to do with your OBi device. If you want to pursue it further, I recommend starting a new discussion over on the Google Voice Help Forum.
Regarding Hangouts: Hangouts uses some different technology than the old Chat/XMPP protocol used by OBi devices, so it's not unusual that the symptoms would be different.
If this is the only inbound calling party that exhibits this symptom, then the best course of action would be for that party to troubleshoot it as a failed outbound call with their carrier. That carrier should be able to see where, in the convoluted call path, the call fails.
AClab:
First, huge thank you to RFC3261! I really appreciated your PM.
Quote from: SteveInWA on July 26, 2015, 12:57:05 pm
Let's get this out of the way: this has nothing to do with your OBi device.
Thanks for the reply, Steve!
But it certainly IS a possibility it's connected to the OBi in some fashion. Ruling that out definitively and absolutely is a bit foolhardy IMNSHO.
Quote from: SteveInWA on July 26, 2015, 12:57:05 pm
If you want to pursue it further, I recommend starting a new discussion over on the Google Voice Help Forum.
That's probably the next stop, at least that was our plan. Thank you for that.
We figured I would try here first because many of the members are quite helpful and knowledgeable. Yourself included! (even if you don't acknowledge the possibility this could be a conjunction of issues between GV and the OBi)
Quote from: SteveInWA on July 26, 2015, 12:57:05 pm
Regarding Hangouts: Hangouts uses some different technology than the old Chat/XMPP protocol used by OBi devices, so it's not unusual that the symptoms would be different.
Yes. We're familiar with this. We're original GrandCentral users, so we've been using this technology and the newer variants for a long time now!
We still disagree that that item alone in and of itself clearly distinguishes itself and dictates it must be a GV problem alone.
Quote from: SteveInWA on July 26, 2015, 12:57:05 pm
If this is the only inbound calling party that exhibits this symptom, then the best course of action would be for that party to troubleshoot it as a failed outbound call with their carrier. That carrier should be able to see where, in the convoluted call path, the call fails.
I wish that were an option. Believe me. Unfortunately, it isn't. :(
SteveInWA:
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.
All the evidence you have posted so far (after edits) 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.
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. For example, if this is from a correctional institution (prison, jail, halfway house), or some other non-standard telephone service provider, that could easily account for the problem.
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.
AClab:
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? :D
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.
LTN1:
Alcab...you write like you have graduate level education and are in a profession where details and word parsing are important. If I'm incorrect, let me know...for all I know, you could also be a mechanic with a Mensa level IQ. You give praise with one phrase as a prelude to criticizing with another. I recognize that type of writing because I am guilty of that on more occasions than I would like; and when I read myself in others, I find that to be quite annoying. So thanks for reminding me of what I should and shouldn't do on a non-academic forum.
But besides thanking you for pointing out my own issues, I would have to confirm that Steve, though not perfect, is the leading GV expert, not only on this forum, but also on the GV forum.
Navigation
[0] Message Index
[#] Next page
[*] Previous page