Can't make or receive calls using GVoice since this morning
SteveInWA:
Quote from: glenviewjeff on May 07, 2018, 07:10:27 pm
Quote from: SteveInWA on May 07, 2018, 03:37:38 pm
Quote from: glenviewjeff on May 07, 2018, 03:21:47 pm
I'm getting a "Registration Not Required" status after following these steps. Has anyone seen this?
Thanks,
Jeff
Just ignore that message. If the service isn't working, try rebooting the device (key in ***9 then 1 to reboot).
Thanks, just tried rebooting, same message. Can't place calls either. Other thoughts?
You might as well try following the steps I outlined previously on Saturday afternoon to start all over.
tpayne03:
@Steve -- ha... told you so, when Grasshopper stopped forward to Google Voice after working for five years. What a cluster. Hopefully the OBI's work again with Google Voice someday...
CO_Steve:
I have no sound either way on incoming calls. I followed your reset guide with no results. Any other ideas? It worked two days ago.
edit: It works now. I went to double check the legacy page for chat, not there. I then found there were two identical entries for my device. Apparently when I deleted and re-added it a second entry was created without removing the first. Deleting one fixed the problem.
SteveInWA:
Quote from: tpayne03 on May 07, 2018, 08:11:14 pm
@Steve -- ha... told you so, when Grasshopper stopped forward to Google Voice after working for five years. What a cluster. Hopefully the OBI's work again with Google Voice someday...
Did you pull that post out of your ass? What does Grasshopper have to do with this? And no "cluster", ALL current OBiTALK products support Google Voice NOW, not someday.
tpayne03:
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?
Navigation
[0] Message Index
[#] Next page
[*] Previous page