Obi/Google Voice disconnecting overnight
SteveInWA:
Quote from: hapollo on June 14, 2016, 07:16:36 pm
Yeah, my OBI200 went down around noon and 2x OBI110 went down 2 hrs later.
All running Pre-OAuth- OBI200 3.0.1 (Build: 4350) and OBI110 1.3.0 (Build: 2824).
I suspect most OBI200s already running POST 4350 Builds.
Upgraded one OBi110 remotely to 2886 and not crazy about the Obitalk GV Portal so holding off on upgrading the other 2 for now.
Can still receive calls on OBi200 thru Callcentric and calls out through Hangouts for now.
Thinking of going the Simon Telephonics route if I can keep my 2324 and 4350 Builds for them.
Let's sum this up: you created a spam-storm over the OBi 100/110 firmware update issue, which was already documented. Now you are posting about your 200 issue.
You've created your own problem by refusing to use OAuth 2.0 authentication.
hapollo:
Yeah, that spam storm you call was to help you from having to rant and rave how the solution was posted over and over again in various threads and to save a few unsuspecting OBIs from paying the ransomware.
But you know what? Even now 10 hrs later, you're still having to reply to new threads asking about this and posting the same manual upgrade solution to those running OAuth 2.0 I can assure you, my 3 posts saved you from having to cut/paste your "spam" post at least a half dozen times. Majority were those running Post OAuth2-2372 builds, so I didn't create my own problem. The problem arose for ALL users. Pre and Post OAuth!
Instead of seeing as a way to alleviate you having to post that over and over, I posted 3x in sub-forums. That's spam?
One can argue each time you keep posting the same cut/paste solution, it is spam. How many times did you spam your "solution" today. Ever think of that?
Tell you what. I have a life. I'll let you sit in front of your computer all day/night to answers all the questions going forward. I can see why others call you mean Steve and stop posting after a while after your abrasiveness.
Good-bye. Enjoy YOUR forum. You moderator wanna-be ::)
sdda61:
:) - Thanks it worked -- I actually had 2 - 110s - Both stop working over 1 year ago - One came back online after
a couple of days -- And Just today it went dead --- Ran the the manual update and your steps on the one the one that has been dead for 1 year and its back working -- Have not tried the other one yet -- One thing I noticed on the one I got working - It had all the original account info - but the Google Voice setup was missing -- on the device - just readded it and now its working..
B34N:
My 202 stopped working with Google Voice today. My Phone Power seems to be working. Strange thing is that I cannot access the obi through the IP address so I'm not sure if Google Voice is the issue.
I reset power multiple times. No change. I read part of this long thread but am unsure what to do since I have a 202 and they have not been impacted.
SteveInWA:
Quote from: B34N on June 23, 2016, 07:03:37 pm
My 202 stopped working with Google Voice today. My Phone Power seems to be working. Strange thing is that I cannot access the obi through the IP address so I'm not sure if Google Voice is the issue.
I reset power multiple times. No change. I read part of this long thread but am unsure what to do since I have a 202 and they have not been impacted.
Log onto your Google Voice account from a laptop/desktop computer's web browser, and go here: https://www.google.com/voice#phones
Confirm that you see the exact two words, "Your number" on the left side of the web page, and underneath it is, in fact, your inbound Google Voice number. If so, then press Ctrl-T to open a new browser tab, and go to your OBiTALK dashboard page. Click your device. Click the SP that you are using for Google Voice, and delete it completely. Now, click the SP again, and follow the instructions to set up Google Voice again.
Navigation
[0] Message Index
[#] Next page
[*] Previous page