Can't make or receive calls using GVoice since this morning
SteveInWA:
Quote from: tpayne03 on May 07, 2018, 09:15:57 pm
Yep... definitely working. As my Obi is sitting here blinking and is non-functional and forum is lit up with people saying the same thing. I have $40 of international GVoice credits while I was trying to make a call to China. My Obi really is toasty now. You get awfully testy about a $40/box.... what's the deal, take an xanax or something.
As an embedded engineer, I'm pretty confident most of these problems are very well connected with the Polycom acquisition (which I think, I did mention "out of my ass" a month ago when all these problems started with GVoice). Now why their boxes can't seem to roll-out a firmware update. Well that's a f'ing cluster my friend...
The reality is probably like 0.1% of users "hack" their Obi and somehow aren't accepting automatic updates. The reality is that this is a cluster.
If Steve from WA in a corporate forum is your point person. That's a f'ing cluster for a company owned by Polycom. Seriously, how many billions is Polycom's market cap?
That's the most absurd, incoherent post so far on this subject.
Sadly, being an "embedded engineer" does nothing for your common sense.
daninwa:
Getting back to the original topic, are there any solutions yet
beyond waiting for Polycom/Google to track down and fix the
software issues?
glenviewjeff:
Quote from: SteveInWA on May 07, 2018, 07:39:10 pm
You might as well try following the steps I outlined previously on Saturday afternoon to start all over.
I'll try that, thanks. Just to make sure, is that a typo re: the software version? I'm running 3.2.2 (Build: 5859EX). I'm back to getting "Connect Failed: No Response".
Do I need to downgrade firmware? If so, do I need to disable updates? Thanks for the guidance.
Ohto:
For what it's worth, I'll add one more data point saying my Obi200 is completely useless as well. I'm suddenly getting the "Connect Failed: No Response" for Google Voice's status now. I've deleted the account/device/younameit several times and started over with no luck. I'm on the latest firmware 3.2.2 (Build: 5859EX). It updated by itself, so I didn't force it.
SteveInWA:
Quote from: glenviewjeff on May 08, 2018, 02:41:08 pm
Quote from: SteveInWA on May 07, 2018, 07:39:10 pm
You might as well try following the steps I outlined previously on Saturday afternoon to start all over.
I'll try that, thanks. Just to make sure, is that a typo re: the software version? I'm running 3.2.2 (Build: 5859EX). I'm back to getting "Connect Failed: No Response".
Do I need to downgrade firmware? If so, do I need to disable updates? Thanks for the guidance.
No, you do not need to, (and you must not) downgrade your firmware! It won't work at all. The build you have is current as of today. They've been pushing out new builds over the past few days, as previously undiscovered bugs are found and fixed. So, a) your device and your Google account have been converted to the new VoIP platform, and b) no manual updates are needed to the device firmware.
I would wait until tomorrow and then go through the steps in my post. There are a lot of Google Voice changes all happening at once, between the new OBiTALK support and the new WiFi calling feature, and it's sort of a moving target.
Navigation
[0] Message Index
[#] Next page
[*] Previous page