Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
SteveInWA:
Quote from: atom on December 05, 2017, 12:54:26 pm
Quote from: billsimon on December 05, 2017, 09:19:06 am
Thanks for assuming I'm cool ;)
To be very clear about the access Google Voice Gateway (and its proprietor) have:
You authorize systems that have our app credentials (specifically, any of the current 7 GVGW VoIP servers) to log in to your Google Chat account ONLY. There is no other access to your Google account, including the Google Voice page, SMSes, or anything else. Audio does pass through our servers, obviously, but it is not monitored (Who has time for that?) nor is it tracked in any way that would make it convenient or easy to do so. Use TLS to hide your signaling for good measure.
Hi Mr. Simon! Thanks for your response and for clearing some things up. To be clear on my end, I really do think you're cool and not the creepy guy listening to our conversations on the weekends :-) After I signed up I was checking out the third party app access in my google account and saw the attached Image below.
It just made me think, who is this guy and what have I done. It says it has access to google hangouts, view and send chat messages. If one has the option turned on to receive google voice texts and voicemail via hangouts I was unsure. I thought I may have just given access to my SMS and voicemail which I really didn't want to give a guy that I don't know. I don't know why, but I feel more comfortable giving a company that sells their products at Bestbuy/Walmart/Newegg etc the same access instead. But seeing your reply here makes me want to trust you more.
I couldn't stop thinking about it, I'm weird like that... Around the same time I get a promo for the obi202 from newegg so I just picked one of those up. Now obi has access to view and send chat messages. :-)
You have made the Google Voice Gateway service very easy to set up/use and a great option for older obi100 devices that now receive the "Backing off" error. I also enjoyed seeing caller ID as well. From the few days that I used it, it worked very well. Thank you for giving us the option for the ridiculously low one time $6 setup fee.
What Bill is discussing is this:
In ye olden days, users would authenticate to their Google accounts by supplying an email address and a password. That gave whoever had those two things complete access to that Google account; a very bad idea. Google implemented a safer alternative, using a secure (digitally signed) token exchange, known as OAUTH 2.0. By using OAUTH, Google can limit access to specific services on your Google account. The party desiring access (Obihai or Simonics) sends a request to Google, which then pops a dialog box or page, asking that Google user if it's ok to allow that third party access to the specific service you want to use with them, and you approve. At no point does the third party ever have your Google password.
So, specific to Google Voice, GVGW is just being granted access, by you, to the telephony stuff, and nothing else.
jmsnyc:
Quote from: SteveInWA on December 04, 2017, 11:16:08 pm
It is six dollars per Google account.
Why not just buy a new OBi 200 and be happy?
I'd rather spend $6 than $60.
Something must have been wrong last night. Now it is working. I am guessing you do not thinking "working " on 110 will be consistent
SteveInWA:
Quote from: jmsnyc on December 05, 2017, 05:21:00 pm
Quote from: SteveInWA on December 04, 2017, 11:16:08 pm
It is six dollars per Google account.
Why not just buy a new OBi 200 and be happy?
I'd rather spend $6 than $60.
Something must have been wrong last night. Now it is working. I am guessing you do not thinking "working " on 110 will be consistent
Right -- you cannot assume that a OBi 110 or 100 will keep working with Google Voice. Eventually, you will need to either upgrade to an OBi 200 series, or use the Simonics GVGW, or not use Google Voice.
JLDP:
We were hit by the same problem yesterday. Googled a lot, fixed it by adding a DNS server.
Came home from work to the same problem, again. No DNS server setting in our box either.
How often do we need to set the DNS server? Is GV erasing it remotely?
Why even the need for DNS entries? If configured properly, the service should work flawlessly, without IT-level intervention in Expert Mode etc. It worked for years. Who broke it?
</rant>
I'll see if I can fix it. Again.
We need our phone line ... you know ... for making phone calls. Daring, right? It's not here only for decoration.
Hoping that there is a more permanent fix than temporary DNS settings.
drgeoff:
Quote from: JLDP on December 06, 2017, 03:41:17 pm
We were hit by the same problem yesterday. Googled a lot, fixed it by adding a DNS server.
Came home from work to the same problem, again. No DNS server setting in our box either.
How often do we need to set the DNS server? Is GV erasing it remotely?
Why even the need for DNS entries? If configured properly, the service should work flawlessly, without IT-level intervention in Expert Mode etc. It worked for years. Who broke it?
</rant>
I'll see if I can fix it. Again.
We need our phone line ... you know ... for making phone calls. Daring, right? It's not here only for decoration.
Hoping that there is a more permanent fix than temporary DNS settings.
There are three permanent fixes. All have been discussed many, many times in these forums.
1. If you have an Obi2xx device or an OBi IP phone it needs a firmware update.
2. If you have an OBi1x0 device then either replace it with an OBi2xx
or
3. Pay the one-time $6 to use the Simonics GV gateway.
Changing DNS is just playing whack-a-mole except that sooner or later your mallet will break - game over.
Navigation
[0] Message Index
[#] Next page
[*] Previous page