Doing an ObiTALK portal refresh of my Google credentials helped immediately for me. The unfortunate thing is, after changing OBiTalk Provisioning from "disabled" to "on restart," restarting my OBi100 to get it to download my Google credentials to the device, then putting provisioning back to disabled, some of my stuff was screwed up, like my SP1 and FXS port digit maps, and my FXS port outbound routing. Trying to restore a backup caused my OBi110 not to be able to auth again (I had hoped credentials weren't stored there, but I guess they are somehow). So, going through (presumably) getting the token again, I could get running again. It's just that I had to go into ObiTALK Expert and change the things for SP1 (name, digit map, maybe a few other things). After seeing successful authentication to Google, I turned autoprovisioning off again, and could change other items just fine, I just really DON'T want to touch anything with SP1.
I wish we could eliminate the ObiTALK portal as one more thing that could break, but that may be dicey at best. See, Google's auth system has keys tied to a developer (such as Obihai). Google even warns you not to divulge your keys, or I think they'll suspend/deactivate them. So the alternative could be for Obihai firmware to be able to accept individual's own secret and token, but that would involve the individual properly setting up a Google developer's account and project, and getting all the Googley fiddly details correct for that project. I've done it for google-drive-ocaml-fuse, and it's not particularly straightforward, at least if you've never done it before (took me a few tries to get it right). So there's going through Obihai, which they take care of all the details, or individuals going through a lot of trial and error, especially if they've never set up a Google project before. For Obihai and their support, the unfortunate truth is it's likely a lot easier for them to set up their portal than it is to coach people through seting up their own developer credentials.