Can't make or receive calls using GVoice since this morning
SteveInWA:
Yes, delete the Google Voice app permission, at the point in the procedure I documented. This will force the OAUTH authentication process to be refreshed.
It should go without saying, but have you checked that your Google Voice service hasn't been suspended, or the number reclaimed (taken back by Google)?
Use a desktop web browser (Google Chrome Browser, Microsoft Edge Chromium, Firefox or Safari, production versions only), sign into the correct account that holds your Google Voice number, and go here: https://voice.google.com/
Confirm that your Google Voice phone number is still shown, and make a test call from the browser interface. Also call your Google Voice phone number from some unrelated phone number and confirm that it rings on the browser.
jacek_:
Thank you Steve,
I have deleted GV app permission, while going through the recovery steps. It didn't really help. I still get the "has not received response from SP" error and the "Token Error." In the Google account Security / "Apps with access to your account" the Google Voice entry was regenerated, with 'Access given on:' few minutes ago (two entries: Third-party apps... and Google Account sign-in prompts). Although, GV Settings doesn't have OBi as a second device (only Web is listed).
As OBi was granted permissions (two entries in Google account Security section), that implies that the initial OAuth is working fine. However, I assume that the token is incorectly used when trying to add OBi device to GV account. That may indicate that either Google modified OAuth permissions or I am missing some entry either in Google Security side or GV Settings that gives permission to add a new device. Not sure what else it could be. Actually, I don't know who negotiates that OAuth exchange to add OBi device. Is that done by the OBi Portal, or rather by OBi device. Maybe my device is missing something as it is 2015.
- GV account is not suspended, I can use it from a browser to call or receive calls for the listed number. So, the phone number is also OK, as incoming calls are fine.
- GV account used is correct, as in the Google Security part of that account a new permission is granted, and the phone number is listed at the top of Account section.
Actually, in Google account Security, there is one more settings "Less secure app access on/off." I tried both, but it didn't make a difference. I guess, this is where OBi tries to make a call, not when a new OBi device is being added to the account.
UPDATE: Went through the process second time. Right now for more than an hour OBi status is "Connecting to 216.239.36.145." As there is still no OBi device in GV account, that would imply that:
- Google successfully granted OAuth permissions/token to OBi
- OBi is trying to use that OAuth token to setup my OBi device, but struggles with it
My guess is that the error I saw before "Token error" means that OBi for whatever reason is failing to OAuth handshake based on the granted token. My assumption is that it is OBi portal talking directly to GV account, so my OBi device is for now out of the picture (whether it is good or bad).
SteveInWA:
Well, one thing that comes to mind is that you said you set up the device in 2015. It's possible it is running downlevel firmware.
Pick up the phone, and key in ***0 then 1# and listen to it speak the firmware version. If it is lower than 3.2.2.5921 then you need to upgrade it, using this file:
http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw
The Google Voice authentication is negotiated by the portal, but the token is stored on your device.
jacek_:
Really appreciate your help, Steve!
I got the same number for F/W. Although, I downloaded that F/W, and tried to update my adapter just in case (using embedded portal), and got the message "Previous version identical to the update. F/W not modified." So, good to confirm it, but that's not it. Actually, is there a way to force that update?
As far as OAuth, I think there are three steps:
Negotiating permissions (adding Google Voice to Apps with access to your account in general account settings) - OBi portal to Google account.Adding OBi device to GV settings - OBi portal to GV account (I think this is where I am failing)Storing the token on OBi device to be used to negotiate calls
If those assumptions are correct, than either something changed on OBi portal side, or on G/GV side. As mentioned, I didn't do any changes to either account for quite some time (if ever), and it just stopped working last week. However, at that time I had OBi device in GV Account (was asked to remove it by OBi support). Although, if that would be the case (portal/Google changes), I would not be the only one whining right now.
That means that maybe OBi portal is storing the token right away on the device, and the flash on my device is corrupted, basically giving back a damaged token.
I wish there would be a way to turn on more detailed error logs, either on the OBi portal and/or on device. Actually, on Google side would help as well, as that could tell that the token is missing/bad.
Any other suggestions?
UPDATE
Actually, I used the internal admin page (on OBi device), and enabled syslog (System Management / Device Admin / Syslog). There is some output from OBi device, and one potential SSL error came during GV setup when new config/settings were downloaded, and OBi was asked to reboot:
Code:
2021-04-19T19:28:41.827846-07:00 obihai200.jacek.int BASESSL:verifing:20
2021-04-19T19:28:41.830269-07:00 obihai200.jacek.int BASESSL:connect error:-1:1[4401]
2021-04-19T19:28:41.830544-07:00 obihai200.jacek.int TC[lhttpc]:ssl connection failed
2021-04-19T19:28:41.830696-07:00 obihai200.jacek.int GAPI:connect error
It is hard to tell, whether that is serious, as few lines after that there is just HTTP connection that is successful (not sure whether the same remote host).
After a couple of minutes, OBi again sent the same BASESSL connection error. So, that would suggest that it may be serious, as it is trying to reconnect.
Earlier in the process, there were two hosts indicated: obihai.telephony.goog (one from Google giving token error - SIP proxy) and root.pnn.obihai.com (potentially OBi portal). Not sure if either of those is causing that SSL error.
I have tried to make an outgoing call, but there are no SIP traces, just DTMF detection. Looking at that internal management page for SIP, there is no entry to enable logging, so kind of useless for debugging.
SteveInWA:
Follow these steps:
http://www.obitalk.com/forum/index.php?topic=14643.msg93013#msg93013
Navigation
[0] Message Index
[#] Next page
[*] Previous page