Google Voice One Way Audio
GPz1100:
Other than I believe one or two other people with this issue, I don't recall seeing any audio issue reports on here or dslreports in recent weeks.
We have 2 obi's which use 3 different google accounts between them, no audio issues, including calls to/from att wireless devices. In addition, there's another 4 or 5 gv accounts provisioned in a local pbx. No audio issues with those either.
It easy enough to create another google voice account and number to test with. I don't think that will solve your problem though unless the underlying reason has to do with gv/routing for your particular gv number areacode/exchange.
Which specific obi devices you have and which firmware are you using? I have 3.2.1 (Build: 5757EX) on both the 200 and 202 models. There is newer build out there but some have reported issues. We haven't encountered any issues with this build. I see no reason to update.
SteveInWA:
Quote
Calling the Ooma echo test number garners the same results. I can't hear myself echo back like I should. I don't know what to do at this point.
If this is the case, then it proves it is not a Google Voice problem. More likely, your router has SIP ALG enabled, which can cause one-way audio.
As far as Google Voice is concerned, Google will not troubleshoot your problem if it only occurs using an OBi device. If you link a conventional 10-digit US telephone number to your inbound Google Voice number, and, using that setup, inbound and outbound calls through that forwarding number work properly, then again, there's nothing wrong with Google Voice -- it's an OBi problem.
BrianTalk:
I saw you post to my old thread. What you described is exactly the same as what I hit almost 1 month ago. My problem was automatically resolved after several days. I tried almost everything but it did not help.
I was planning to pay $10 for the paid support but I found the problem was resolved magically when I did the last try before I tried to buy the support.
Sorry I cannot be more help but I hope the good luck to you. I also hope someone could figure out the root cause and fix.
BrianTalk:
I also suggested you can try to create a new Google voice account to have try. I did intensive research when I hit the issue and some articles said GV might block Obi talk in some manner on the server side. My problem was self resolved which I think it is more like a server-side issue instead of a client-side issue as I did nothing on the client-side.
Otherwise, I would suggest you buy the Obi paid service to let them troubleshoot. It is still cheaper than you buy a new device.
Quote from: Steve56 on February 26, 2018, 11:03:27 pm
Did perform a factory reset as well and then set-up Google Voice as SP1. Still the same intermittent one-way audio problems. No real opportunity to test with another internet connection but at this point, I'm leaning toward this being a Google Voice issue, especially since I've seen at least one other recent post chronicling the same exact issue I'm encountering. The problem only seems to present when calling AT&T wireless phone numbers. Landlines are mostly unaffected, however the Ooma echo test gives me silence, no echo of what I'm saying. Conversely, calling another echo test service does work just fine!
If anyone has the means to do so, please forward this issue on to the proper people at Google. Yes, it's a free service, that I know, but to say this is immensely frustrating would be an understatement.
SteveInWA:
Quote from: BrianTalk on February 27, 2018, 10:44:17 pm
I did intensive research when I hit the issue and some articles said GV might block Obi talk in some manner on the server side. My problem was self resolved which I think it is more like a server-side issue instead of a client-side issue as I did nothing on the client-side.
That's incorrect. Google does not block the use of OBi devices. In fact, Google has specifically left their otherwise obsolete and useless XMPP servers in place, specifically for OBi users' benefit.
Here are a few pieces of factual information:
When people make or receive calls using Google Voice's old "Google Chat/Talk" infrastructure, the calls first connect to Google's servers (there are hundreds of them, spread around the country), via XMPP, not SIP. From there, the calls can pass through multiple carrier-class connections, including one or more "transit" or intermediate carriers, between your end and the ultimate called party's end.One common cause of one-way audio is a CODEC mismatch or other technical problem between carriers. Often, these problems are discovered and fixed, without any end user action. Sometimes, they go on for months, typically when a particular international destination is being called, which increases the likelihood of some oddball transit carrier having a problem. Furthermore, subsequent calls to a given destination may traverse different transit carriers, thus increasing the intermittent nature of the failures, and making problem determination more difficult.Most consumer-class routers have a largely-useless feature known as a SIP Application Layer Gateway, or ALG. This feature, while having a seemingly useful name, actually interferes with ordinary SIP client to SIP server communications, and it needs to be disabled (turned off). Many routers default this setting to being enabled for typical SIP client use.Google Voice (actually Google Chat) doesn't use SIP, so it is unaffected by the SIP ALG setting. However, the Simonics GVGW is a SIP<-->XMPP gateway. If you are using GVGW instead of a direct XMPP connection to Google, then your OBi is acting as a SIP client, and may be impacted by SIP ALG settings.The best way to determine if the OBi or the user's home network equipment or ISP is at fault, is to test Google Voice calling without using the OBi at all. Instead, make or answer multiple calls using Google Voice with an ordinary land line or mobile phone connection. If no calls fail this way, after multiple tries, then there is nothing wrong with your Google Voice configuration, nor the Google Voice telephony infrastructure; you have an OBi/router/ISP issue.
Navigation
[0] Message Index
[#] Next page
[*] Previous page