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:
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.