Can't make or receive calls using GVoice since this morning
jacek_:
Again, thank you so much for all those directions, Steve!!
Yesterday, I got a new GV account with a new number, and tried to add it to my account. It didn't work, it was giving me the exact same problems. Frustrated, I left that new number connected. I ordered a new device (assuming that OAuth token is stored on device, and that part of Flash is busted).
Today, I got an email from Poly stating that everything works! Magic!!! Well, I didn't change anything. I tried to call, and the new GV account was working fine. OBi device was in GV Account part. I switched back to my old GV account / number, and voila, everything is working fine!!
There was no change on my side (whether OBi device or OBi / Google accounts. My take is that if that was on Google side, potentially more people (e.g., GV clients) / services (e.g., YT using OAuth) would be affected. That makes me thing that OBi services required a reboot. Although, this is the first time for me in a really long time (I mentioned 2015, but actually that was when I purchased a second device for my relatives).
Steve, Thank you again! Jacek
SteveInWA:
Quote from: jacek_ on April 21, 2021, 04:20:01 pm
Again, thank you so much for all those directions, Steve!!
Yesterday, I got a new GV account with a new number, and tried to add it to my account. It didn't work, it was giving me the exact same problems. Frustrated, I left that new number connected. I ordered a new device (assuming that OAuth token is stored on device, and that part of Flash is busted).
Today, I got an email from Poly stating that everything works! Magic!!! Well, I didn't change anything. I tried to call, and the new GV account was working fine. OBi device was in GV Account part. I switched back to my old GV account / number, and voila, everything is working fine!!
There was no change on my side (whether OBi device or OBi / Google accounts. My take is that if that was on Google side, potentially more people (e.g., GV clients) / services (e.g., YT using OAuth) would be affected. That makes me thing that OBi services required a reboot. Although, this is the first time for me in a really long time (I mentioned 2015, but actually that was when I purchased a second device for my relatives).
Steve, Thank you again! Jacek
I'm glad it worked, but you didn't follow my instructions to transfer the number, which would likely have fixed it.
Also, your assumptions about OAUTH are incorrect. Google Voice is one of the very few remaining Google services still using that authentication method. You'll never know what Poly did, but there was likely a problem with your OBiTALK preventing the token exchange. This wasn't caused by Google.
jacek_:
No, I didn't follow your instructions to do a full xfr. There were two reasons for me to not do it. First, the new GV account with a new number behave exactly as my old one (there was no OBi device added to GV Account page). The second, I wanted to keep my call history / names from the old account. I didn't know whether that will be xfred with the number, or will be destroyed for 'security' reasons.
Again, I did try to reconfigure that SP1 several times yesterday. I got a new browser to get a clean Google account there, and nothing was moving fwd. Today, after the email from Poly, all of the sudden, everything started to work, both new and old account. So, my take is that it had to be something outside of my control (device, portal, G/GV settings).
Also, your statement that my assumptions about OAuth are wrong are a bit harsh. I have never stated that Google does only OAuth. Also, you stated that there are still _few_ services that are using it. My take is that we were both correct. However, whether that is the case or not, my point about OAuth was just how it works between OBi (in general - portal/device) and G/GV.
I guess, we can close this chapter, as we are splitting hairs right now.
Although, I replied to Poly, asking them to improve error reporting (through portal, syslog). Maybe it would be good to have a separate thread that would start listing errors that people have, and explanations / fixes. This way, maybe it would be more visible to OBi, that it could help if they do it.
jacek_:
Well, guess what. There is right now "Connect Failed: 403 Forbidden;Token Error" in OBi's portal.
Again, it started to work by itself (although, kind of surprisingly right after Poly's delayed by two days email). Right now, it went down again by itself (OBi's maintenance or we are back to square one???).
drgeoff:
Quote from: jacek_ on April 21, 2021, 07:20:44 pm
Well, guess what. There is right now "Connect Failed: 403 Forbidden;Token Error" in OBi's portal.
Again, it started to work by itself (although, kind of surprisingly right after Poly's delayed by two days email). Right now, it went down again by itself (OBi's maintenance or we are back to square one???).
FYI. Once your device has been successfully configured for GV, Obihai's servers play no further part in keeping it so configured, nor in making nor receiving GV calls.
The portal can see and report to you the state that your OBi is in vis-a-vis GV (or any other ITSP).
If when the GV connection is back up and working you go into your device's on-board configuration interface and disable Obitalk Provisioning then you can be sure that any subsequent going down of GV is not caused by Obihai servers sending bad instructions to your device.
Navigation
[0] Message Index
[#] Next page
[*] Previous page