Outbound dialing - one ring then silence
Soulcommander:
Quote from: FormerYooper on April 26, 2018, 03:13:52 pm
Last couple of days, I've had an issue with incoming calls on my OBi200 They can hear me, but I can't hear them. I most certainly have "chat" checked in GV settings. I have changed nothing. Worked perfectly for years until a few days ago. The issue will persist for a few calls, then it magically disappears. Then reappears again. Me thinks Google is fooling around with GV a bit. ::)
Go Here and read the posts and then give them calling info https://productforums.google.com/d/topic/voice/Unn7jCk1JUA/discussion
Taoman:
Quote from: GPz1100 on April 26, 2018, 10:47:56 am
Still ongoing here. So far I see several trends.
Call initiated on obi - If the recipient lets the call ring a bit (2 rings?), then there's full audio, otherwise they can hear me but I can't hear them.
Call initiated on softphone through simonics gateway. Full audio present when call is answered immediately.
Call initiated through pbx - same issue as calling through the obi. Sometimes waiting for 2-3 rings doesn't help either.
Interesting. I've been repeatedly testing my two GV lines trying to duplicate what you (and others) have been experiencing. So far, no "luck." One number is configured on my OBi via OBitalk with a direct connection to Google. The other line uses Simonics GVGW. Both lines continue to work as expected with no audio issues.
Just curious: were the GV number(s) in question supplied by Google or did you port them in? Mine were not ported in.
GPz1100:
I've experienced the issue on both, ported and google supplied numbers.
Same number that experiences the issue on the pbx (motif), has no issues when tunneled through simonics.
Another oddity, calling the obi gv number (or other gv #) sometimes I get ringback tones, sometimes not.
SteveInWA:
Thanks for the reports. If you haven't come to the conclusion already, this is a Google Voice infrastructure bug. They have an open ticket on it, and they accept that it's serious. The engineer I spoke with invites y'll to post specific examples, as many have done already. It's not universal, for some unknown-at-this-time reason.
There are a lot of "balls in the air" at this time, in GV-land, with some infrastructure changes related to the GV VoIP beta, etc. It's making things difficult to isolate, and they have a pretty small staff to distribute work on bugs.
If/when I have any further details, I'll be happy to share, but that's all I know this afternoon.
Again, please post over on the thread here:
https://productforums.google.com/d/topic/voice/Unn7jCk1JUA/discussion
SteveInWA:
Google Voice engineering found the issue and has implemented a fix. Please feel free to test it yourself, and report any problems with this specific issue, not general problems to the linked Google Voice forum thread.
Navigation
[0] Message Index
[#] Next page
[*] Previous page