OBi + GV + Inbound Private Callers = Dead air
AClab:
Hello OBi Friends! Long time reader, infrequent commenter.
We just recently started experiencing a sporadic issue with our OBi202 in conjunction with Google Voice, and I'm hoping some here could steer us down the right path. We've been troubleshooting this issue on our own for almost 3 weeks now.
We've traced the origin of the issue to around the same time of a known Google issue that SteveInWA mentioned.
We don't know if our issue is related to that or not. But the timing has us thinking it isn't coincidental. But it could be.
Here's the issue:
We receive regular calls from a "Private Caller" a few times a month. I suppose I would characterize the calls as from an anonymous number? There's no Caller ID. The OBi reports no name or number inside the Caller ID parenthetical info. These are all calls from one "caller" who we know and WANT to receive calls from, but that has no control over how their outbound calls or Caller ID are handled.
Until July 5 or July 6, we didn't have an issue receiving this calls using OBi202 + GV. Hardware version 1.4, currently running 3.0.1.4738 Firmware.
Now, the calls ring through to our device, but we are never connected. If we answer (even on the first ring) it's simply dead air.
Prior to the issue, the OBi call status and history would normally show these calls listed as:
From GT2()
Or the like, depending on the SP slot. Now, they are labeled:
From GT2(a)
I assume this is somehow being flagged as anonymous call. The only settings I know of in the OBi Service Provider configuration for inbound calling is the AnonymousCallBlockEnable feature, and it is presently set to "unchecked".
If we remove the OBi202 from the equation, and instead use Hangouts on an Android device to receive these calls, the calls do seem to work. Though, the way the calls come in are slightly odd. The inbound calls will ring, we'll answer, and dead air again. Sometimes even without hanging up, another inbound call will come through, and THAT call seems to work.
All other calls to and from the OBi using GV in these SP slots work fine.
I have combed through all the GV settings on the Google side to ensure that the Ring Schedule is set to Always for both Weekdays and Weekends, Call Screening is off, Global Spam Filtering is set to UNCHECKED, and the Anonymous Callers Group/Circle is set to ring Google Talk, with the Call Screening set manually to Off.
Help?
Any advice? Something obvious we are missing? Or maybe even something advanced configuration wise we can change or augment?
We would really appreciate any help. Thanks!
SteveInWA:
Hi:
The issue in the post you referenced was resolved.
What makes you think these are legitimate telephone calls at all? Is this someone you actually want to talk to, and their calls don't work? It could just be some malformed or corrupted caller ID from a spam caller. Furthermore, if you've shown that you get the same dead-air and blank caller ID symptom when using Hangouts, this has nothing to do with your OBi.
Google does try to squash the large majority of junk calls, but sometimes, crud like this gets through.
AClab:
Hi Steve! Thanks for the reply.
Quote from: SteveInWA on July 25, 2015, 08:44:48 pm
The issue in the post you referenced was resolved.
Yes, I read the thread.
And many others over the GV Support Group. I haven't seen any one else really describing our particular problem.
Quote from: SteveInWA on July 25, 2015, 08:44:48 pm
What makes you think these are legitimate telephone calls at all? Is this someone you actually want to talk to, and their calls don't work?
I should have made that more clear. These are calls from ONE particular "caller".
Yes. We do want to receive the calls. If we didn't, hell, why would we worry about someone we don't even know that's can't get through? :D
But I should have made that more clear. My apologies!
Also, that caller has absolutely no control over how their outgoing calls or Caller ID are handled.
Quote from: SteveInWA on July 25, 2015, 08:44:48 pm
It could just be some malformed or corrupted caller ID from a spam caller. Furthermore, if you've shown that you get the same dead-air and blank caller ID symptom when using Hangouts, this has nothing to do with your OBi.
Actually, no. It DOES work with Hangouts. It just works in a very odd and particular way. It rings through, tries to connect, dead air, and sometimes while we are still on the line, it rings again, and we CAN connect.
We don't ever get that same experience with the OBi.
I edited the OP to reflect that we want to receive these calls, and that they are originated from an entity known to us.
It's also completely possible this is an intended feature by Google. I fully understand that.
But we do want to receive these calls. And I'm hoping someone can shed some light on what setting may be wrong, or how we might go about this differently. As I mentioned, this has worked for us in the past with this same caller all the way up until July 5 or 6. The 6th was the first day we actually saw a "live" call with this issue.
Our only other option would be to move to something like Anveo, which has worked for us in the past for this particular caller. Which we may in fact have to do, and that's okay. But this isn't just an issue for us in particular. There's another family member who also receives calls from this caller, and they are having the same issue. If we can keep using Google Voice, that would work best for them. I hate to see them have to pay out of pocket for this, so we are trying our best to figure this out on our own.
We just need a little help doing so. We've exhausted all our ideas and are looking for new ones.
RFC3261:
Quote from: AClab on July 25, 2015, 09:40:31 pm
Also, that caller has absolutely no control over how their outgoing calls or Caller ID are handled.
Unless they are incarcerated (or live in particular suppressible regimes), or residing in places like Antarctica, they likely have some control, although their control could be limited by what they wish to pay, or the technologies they wish to use. The fact that they come in strangely suggests that the source is "special" in some way. You are likely going to have to provide more details regarding the specific source(s), and other limitations, to see if others in similar situations can provide better suggestions.
AClab:
Quote from: RFC3261 on July 26, 2015, 08:54:51 am
Quote from: AClab on July 25, 2015, 09:40:31 pm
Also, that caller has absolutely no control over how their outgoing calls or Caller ID are handled.
Unless they are incarcerated (or live in particular suppressible regimes), or residing in places like Antarctica, they likely have some control, although their control could be limited by what they wish to pay, or the technologies they wish to use. The fact that they come in strangely suggests that the source is "special" in some way. You are likely going to have to provide more details regarding the specific source(s), and other limitations, to see if others in similar situations can provide better suggestions.
Thanks for the reply! Sent you a PM with more details.
The "come in strangely" is a totally new development, FYI. They never did that prior.
And this (again) all started exactly around the time of the GV issue that appears to have been resolved that I mentioned in the OP.
Prior to that date, everything worked swimmingly.
Navigation
[0] Message Index
[#] Next page