Tried deleting and enabling Google Chat. Don't know what to do
How about giving us a bit more information such as:
What OBi model?
Has this ever worked properly? Is this a new set-up or one that has been OK previously and is now not OK.
Can you make outgoing calls OK?
Have you any other service providers configured on your OBi? If yes, any problems with them?
What exactly happens when the phone rings and you take it off-hook? What do you hear?
If the OBi is an ATA (ie not an IP phone) what sort of phone are you using? Is it plugged directly into the OBi, no fax machine, no house wiring, no nothing?
Is it always calls from the same numbers that go to voicemail?
Anything else you think relevant.
No information -> no solution.
Obi 200 has successfully worked for about 6 months. Some calls make it thru. I can call out.
No other service providers ever used. Vtech phone plugged into fax machine, fax direct to Obi. it rings, I answer and hear nothing. I try calling myself from my cell phone, rings, I aqnswer, my cell (any caller) continues to ring and goes to Google VM.
I deleted google chat a second time and enabled and system seems to be working for now..
Having a similar issue with our Obi1062 and Obi202s with Google Voice. Everything has worked fine for months and issues started up this past Monday.
When we pick up, there is no sound and eventually caller goes to VM. It continues to ring other Obi devices (we have both the 1062 and 202 on each Google Voice account), plus continues ringing in our browser/Gmail and forward phones. Answering in the browser or forwarded phones seems to work fine.
It's happening >50% of the time now on all our lines.
Firmware is fully updated on all devices and have tried rebooting
Getting worried as answering these phones is vital for our business
Edit: outgoing calls seem to work totally fine
I am having the exact same issue as queensoffice, came here to look for answers. I have an Obi202 that has worked fine for months, now I have trouble answering calls. The Obi202 is connected to a Panasonic cordless, and I also have GV calling my cell phone. When I answer on the cordless, I just hear dead air, and my cellphone continues to ring. I then end up taking the call on my cell phone before it goes to VM. This happens at least 50-75% of the time. It all started earlier this week, I have never had issues up until now. Maybe a daylight savings issue?
This issue has been reported to Google (by me) today, and they've opened a ticket. I have no information as to when it will be investigated and fixed.
There is nothing you can do about it, and removing and re-adding Google Chat is NOT going to do anything about it.
Same here
Thanks Steve
Quote from: SteveInWA on March 16, 2018, 03:21:48 PM
This issue has been reported to Google (by me) today, and they've opened a ticket. I have no information as to when it will be investigated and fixed.
There is nothing you can do about it, and removing and re-adding Google Chat is NOT going to do anything about it.
Thank you Steve. Let me know if you need some logs, it happens quite frequently.
Very same issue, happening on two Ibi200+GV I own. I upgraded the firmware manually to the "latest" dated January 2018, V.3.2.1 Build 5794EX, but this morning I got the [!] in Obi Dashboard for one of my units for FW update, and I did it - resulting in Build 5757EX. Problem still persists.
I want to add: Ringing goes through, Caller ID is displayed, when receiver is picked up - CONNECT does not get to the SIP server, so GV does not know that receiver is picked up.
I also opened "Request for Service" ticket with Obihai, no response yet.
Seems like a problem is between Obi200 (PBX) and GV Server. The [CONNECT] is either not sent or not always received.
Quote from: simonmiz on March 17, 2018, 08:59:16 AM
Very same issue, happening on two Ibi200+GV I own. I upgraded the firmware manually to the "latest" dated January 2018, V.3.2.1 Build 5794EX, but this morning I got the [!] in Obi Dashboard for one of my units for FW update, and I did it - resulting in Build 5757EX. Problem still persists.
I want to add: Ringing goes through, Caller ID is displayed, when receiver is picked up - CONNECT does not get to the SIP server, so GV does not know that receiver is picked up.
I also opened "Request for Service" ticket with Obihai, no response yet.
Seems like a problem is between Obi200 (PBX) and GV Server. The [CONNECT] is either not sent or not always received.
That several people are reporting the same issue more likely means that problem is at the GV end. In which case there is nothing you or Obihai support can do except wait for GV to fix it.
BTW GV uses XMPP protocol not SIP.
I have two lines in 2 different locations now with this same issue. Obihai 1062 and 1022 both using GV. The 1022 line is also setup to forward to a cell phone which can answer the calls via cell but not the obi. Outgoing calls seem to be working fine.
As I said above: this is already on Google's radar to investigate. I know people like to experiment and speculate on causes and fixes, but there is nothing you can do about this particular issue.
Depending on how long it takes Google to fix this issue the quickest solution might be to get a free DID from Callcentric (or IPComms) and forward your incoming GV calls to that (after configuring the DID as a new Service Provider on your OBi device). Problem solved.
Quote from: Taoman on March 17, 2018, 05:36:05 PM
Depending on how long it takes Google to fix this issue the quickest solution might be to get a free DID from Callcentric (or IPComms) and forward your incoming GV calls to that (after configuring the DID as a new Service Provider on your OBi device). Problem solved.
Can anyone confirm Callcentric can be setup to receive GV calls? The below quote is what is making me question whether or not this is possible:
"Verification calls from third-party services (WhatsApp, Craiglist, etc) are blocked for this product"
If so this seems like a viable interim solution.
Hey Steve, thank you for alerting Google to this issue. Where in Google forum is your posting? Can you give a little more specific link?
It's clear the issue is between Obi and GV. For now - as a temp solution - I linked my cell phone to the GV number, so it rings on both, and if Obi does not pick up - the cell phone picks up OK.
Quote from: cruz878 on March 18, 2018, 07:24:42 AM
"Verification calls from third-party services (WhatsApp, Craiglist, etc) are blocked for this product"
If so this seems like a viable interim solution.
You may find this of interest:
https://www.obitalk.com/forum/index.php?topic=13433.0 (https://www.obitalk.com/forum/index.php?topic=13433.0)
Quote from: cruz878 on March 18, 2018, 07:24:42 AM
Quote from: Taoman on March 17, 2018, 05:36:05 PM
Depending on how long it takes Google to fix this issue the quickest solution might be to get a free DID from Callcentric (or IPComms) and forward your incoming GV calls to that (after configuring the DID as a new Service Provider on your OBi device). Problem solved.
Can anyone confirm Callcentric can be setup to receive GV calls? The below quote is what is making me question whether or not this is possible:
"Verification calls from third-party services (WhatsApp, Craiglist, etc) are blocked for this product"
If so this seems like a viable interim solution.
You misunderstand.
Using a Callcentric (or similar) number as a forwarding number from an existing GV number is a completely different thing from using a number to receive the verification code when setting up a new GV account.
I also have this issue. Occasionally a call gets answered but that is a rarity.
My current solution is to forward to a linked phone number so I can answer calls. My problem with this workaround is that the caller ID is that of the linked line so some outgoing call recipients don't answer fan unknown number.
I hope Google fixes this quickly.
same problem never had before. Tried with and without simonics. Will try callcentric now...
Same problem here since last week, pick up phone that is connected to my OBI200 just get silence, meanwhile my cell phone continues to ring and I can answer the call that way.
Temporary workaround seems to be callcentric.
Quote from: simonmiz on March 18, 2018, 08:19:52 AM
Hey Steve, thank you for alerting Google to this issue. Where in Google forum is your posting? Can you give a little more specific link?
It's clear the issue is between Obi and GV. For now - as a temp solution - I linked my cell phone to the GV number, so it rings on both, and if Obi does not pick up - the cell phone picks up OK.
See: https://productforums.google.com/d/topic/voice/ouSBboXA1zY/discussion (https://productforums.google.com/d/topic/voice/ouSBboXA1zY/discussion)
Just my 2cents:
I do embedded hardware design & firmware, so I pretty much get how these Obi devices are built.
I've been using these devices for a few years for non-enterprises business lines. Great deal -- pretty much free phone lines using Google Voice with a basic QOS router to manage each MAC address.
And than, BAM -- service is broken. Not a little broken, but massive breakdown. Maybe Google decided OBi doesn't get a free pass anymore seeing how they got purchased by Polycom?
I guess you can purchase access to some other providers, but why would you since Google Voice works so well, and is so free?
Right now my OBi isn't receiving any inbound calls correctly with Google Voice at all.
Quote from: tpayne03 on March 20, 2018, 07:48:54 AM
And than, BAM -- service is broken. Not a little broken, but massive breakdown. Maybe Google decided OBi doesn't get a free pass anymore seeing how they got purchased by Polycom?
No conspiracy theories, please. This is a known bug that Google has been made aware of.
Quote
I guess you can purchase access to some other providers, but why would you since Google Voice works so well, and is so free?
You answered your own question. Google Voice is not a free telephone company. It is an inbound call forwarding and message management system. VoIP calling via OBi products is using Google's former "Google Chat" service via XMPP, but it is not the primary role of the service. There is no guaranteed service level. If your business depends on highly-reliable telephone service, then use a SIP VoIP service provider instead.
same problem here with obi 200.
Quote from: AF1E on March 21, 2018, 08:05:39 AM
same problem here with obi 200.
Same problem, same solution as I posted above:
See: https://productforums.google.com/d/msg/voice/ouSBboXA1zY/vRKFyQotBQAJ (https://productforums.google.com/d/msg/voice/ouSBboXA1zY/vRKFyQotBQAJ)
Quote from: SteveInWA on March 21, 2018, 08:32:21 AM
Same problem, same solution as I posted above:
You mean "workaround," not "solution."
Solution would be for Google to fix this problem. Any ETA?
Well, I won't debate semantics.
I can confirm that as of this afternoon, the status is that the problem has been assigned to an engineer. I don't have any more specifics. Without knowing the root cause yet, I can't predict how long it will take to restore service.
I've been working with the GV engineering team this evening. They've got a handle on what caused it, and it should be working now.
Please feel free to bang on it and let me know. I don't know if it matters, but it wouldn't hurt to power-cycle your OBis before testing.
As of March 22 2018 10:46AM EST -
Is everyone still having this problem, as I am?
And was the going to voicemail issue fixed as per the update here via GV engineer(s)?
Is anyone else having this additional issue as I am : (and it still happens on most calls, though many times after 10+ minutes on the call)
During an outgoing call I hear redialing tones at some point, as if someone had pressed redial on their phone. My phone was on a table, not held by me, as I use a corded headset. AND at that point and beyond, the caller tells me the volume of my voice has decreased and it's hard to hear me.
Thanks.
Bob
Quote from: SteveInWA on March 21, 2018, 07:09:10 PM
I've been working with the GV engineering team this evening. They've got a handle on what caused it, and it should be working now.
Please feel free to bang on it and let me know. I don't know if it matters, but it wouldn't hurt to power-cycle your OBis before testing.
Great news, thanks!
Still having all the same problems I mentioned in my post including the redialing sound and lowered volume, as of March 22 2018 at 4:32 EST.
So I unplugged the power connection, waited 30 seconds, reconnected. After that,
it appears ALL calls are going to voicemail - at least the 4-5 I've gotten since then.
Is anyone seeing this fixed?
Does GV have a setting to turn off voicemail? I can't find it.
Bob
PS - I googled how to turn off voicemail, had to go into legacy GV, but my home phone is ringing via Obi 200, and is not a forwarding number..so is there a way to turn off voicemail another way?
Ditto: we have been forwarding calls to cellphones for a week. We tried call forwarding through Google Voice, and the calls are going immediately to voicemail. This is still broken.
Quote from: tpayne03 on March 27, 2018, 08:57:07 AMWe tried call forwarding through Google Voice
There is no such option. What are you trying to say?
Our Cloud PBX forwards calls -> Google Voice -> Obi @ End Number with Analog Phone.
When Cloud PBX Forwards, Google Voice simply hangs up, as Cloud PBX terminates into Voicemail prompt.
Quote from: tpayne03 on March 28, 2018, 08:30:25 AM
Our Cloud PBX forwards calls -> Google Voice -> Obi @ End Number with Analog Phone.
When Cloud PBX Forwards, Google Voice simply hangs up, as Cloud PBX terminates into Voicemail prompt.
That configuration (PBX forwarding TO a Google Voice number) is not supported. It's not expected to work.
Furthermore, the bug that was the subject of this discussion thread was fixed. Any currently-experienced problems are unrelated to this issue. Start a new discussion.
Quote from: SteveInWA on March 28, 2018, 03:06:00 PM
Quote from: tpayne03 on March 28, 2018, 08:30:25 AM
Our Cloud PBX forwards calls -> Google Voice -> Obi @ End Number with Analog Phone.
When Cloud PBX Forwards, Google Voice simply hangs up, as Cloud PBX terminates into Voicemail prompt.
That configuration (PBX forwarding TO a Google Voice number) is not supported. It's not expected to work.
And, this also answers your other post, regarding Grasshopper. It simply won't work reliably, if at all.
http://www.obitalk.com/forum/index.php?topic=13703.msg87892#msg87892 (http://www.obitalk.com/forum/index.php?topic=13703.msg87892#msg87892)
Except this functionality worked for something like 5 years.... and then something changed, and now it's stopped working.
(Your post you suggested for me to look at, is in fact where I am the original poster...).
I'm not really certain why you would think this would not work... why would Google Voice have any issue with forwarding calls like that?
Do you code the platform, that's a very specific claim -- in light of the fact the whole thing has been working for years.... Is there some specific technical document / service statement to support anything like that?
The problem is being caused by trying to forward your PBX inbound calls to the Google Voice number. That is backwards from the design of Google Voice, which is intended to be the single point of contact number, which then forwards calls to linked destination numbers and/or OBis and to Hangouts.
The fact that it used to work is interesting, but irrelevant. Google makes changes to their infrastructure on a regular, ongoing basis, and there is no guarantee that an unsupported configuration will continue to work. In addition, PBX software changes all the time, as do the configurations users make to their PBXs that may or may not work with Google Voice.
No, there is no technical documentation on this. As I mentioned previously, if you need VoIP trunks, then use a vanilla SIP VoIP service provider, not Google Voice.