This morning I made an outbound call, proving everything was OK with OBi110 plus Google Voice. But this afternoon when looking over at it, only the power LED was lit, meaning one of the services lost connectivity. (It's supposed to have power plus the one with the telephone/handset logo lit.) Looking into the device, it said authentication failed on SP1, and it was backing off. I will also note that since Obihai wants to store my admin password, I normally disable the ObiTALK service and the Obi autoprovisioning, and do any updates locally (not through the ObiTALK portal). Of course, with the new OAUTH2 requirements and Obihai's chosen implementation, it is REQUIRED to provision Google Voice through ObiTALK, but once (presumably) the OAUTH2 yummy bits are placed on the device (secret? token? refresh token? I don't know what exactly is needed, just that it's a PITB), if I'm not mistaken, you can shut off communication with Obihai. It was clear back to yesterday that I did anything security related with my Google account (revoking some apps' access, but certainly nothing Obihai related), and I didn't change my password, or turn on two factor auth, or anything like that. In theory, whatever the OBi110 had should have continued working. I reenabled the ObiTALK service, reenabled Obi autoprovisioning, logged into the ObiTALK portal, presumably got an updated token put on my ATA, and it seems to operate.
A few things seem troublesome though.
A couple weeks ago, when things were operating just fine, as a matter of periodic maintenance, I logged into the device and created a config backup. Because ObiTALK messed up my customised digit maps, call routing, etc., I restored that config from 07-May. But that caused GV not to auth properly again. I would hope any config dump wouldn't contain the credentials (at least not passwords), but apparently it does.
Where was the breakdown? I am reasonably sure I didn't change anything Obi related on the Google side, yet it failed something like 18 hours after the last Google account change.
I don't like that auth tokens for Google go through Obihai, but I guess 'dems the breaks; at this point, it's either accept it or don't use GV with an ATA
Altering things other than the credentials (like putting in my name instead of leaving it, I think, blank) also caused GV not to auth.
On the positive side, I have Callcentric provisioned on SP2, which seems relatively unaffected. I was expecting Obihai to wipe out all my local changes. It seemed anything I changed locally after the OAUTH2 firmware update would be countermanded by the ObiTALK portal, sort of like resetting it to factory, and rebooting it. (Storing my password is horrid enough, but the other detestable thing is the reboot after EVERY ObiTALK Expert change. At least with local changes, I can make a whole batch of them on several pages and THEN reboot.) So to stop that from happening, as mentioned, I turn off Obi autoprovisioning and the Obitalk service in an attempt to keep it from phoning home (oh the irony, or something, in that statement).
So, am I virtuallly the only one to which this happened? Anything I can do differently to prevent this from happening again?
--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.
Jeopardy! replies and randomcaps REALLY suck!
↧