GoogleVoice OAUTH + Configure locally
azrobert:
There has been much whining on this forum by users that configure their OBi's locally (including myself) about the new GV OAUTH authentication forcing us to use OBiTalk to configure our OBi devices.
The below procedure will allow us to continue to locally configure the OBi.
Starting with an un-configured OBi:
1. Add the device to OBiTalk.
Auto Firmware Update and OBiTalk Provisioning will be automatically enabled. The latest firmware will be downloaded to the OBi.
2. Define a GV trunk using OBiTalk.
3. Sign into the OBi locally and disable Auto Firmware Update and OBiTalk Provisioning.
4. Configure the OBi locally including changes to the GV trunk. The only settings you can't change are the GV UserID and PW.
If you need to add another GV trunk in the future:
5. Create a Configuration Backup locally in System Management/Device Update.
Check Use OBi Version.
6. In OBiTalk Expert import the backup. Now the OBi and OBiTalk will be in sync.
7. Locally enable OBiTalk Provisioning.
8. In OBiTalk define the GV trunk.
9. Locally disable OBiTalk Provisioning again.
10. Locally make any necessary config changes.
The config backup does not contain any passwords, so when you do the import there aren't any passwords on OBiTalk. When OBiTalk downloads the new config after you define the GV trunk it does NOT overlay the locally defined passwords with blanks.
If you have a configured OBi, start at step 5.
This procedure is acceptable for me. How often do we change GV passwords or add a new GV trunk? However, I still hope OBihai adds OAUTH 2.0 to the local interface.
QBZappy:
+1 Thanks
corporate_gadfly:
Quote from: azrobert on September 23, 2014, 04:55:08 pm
This procedure is acceptable for me. How often do we change GV passwords or add a new GV trunk? However, I still hope OBihai adds OAUTH 2.0 to the local interface.
Thanks for trying this out.
I wasn't too keen on messing with my "production" setup. So kudos for letting us know how it worked out.
Rick:
Seems simple enough, except for:
Define a GV trunk using OBiTalk.
I only use the local configuration options, and have Callcentric on both SP1 and SP2. I have two GV numbers, each of which forwards to a Callcentric number, and then rings the OBi. For about a month, GV has not forwarded calls reliably - GV says it's a CC issue, CC says it's a GV issue. I have little hope it's going to get resolved.
So unless I want to move from GV (which I may), it appears I have to do something like this.
Does this mean that I can keep CC on SP1 and SP2, because the trunk is setup for GV? I really don't understand the trunk concept. Reading OBi's documentation doesn't help. :o
SteveInWA:
"Trunk" is telco jargon, meaning a circuit or, in this case, a ITSP registration, providing a connection from your premises to some telephone company or ITSP.
Substitute the term "service provider configuration" in the context of OBi-speak, and it makes more sense.
You currently have Google Voice set up to forward to Callcentric numbers. That setup is on the Google Voice website, not on your OBi, which has the CC numbers configured. So, you can decide what you want to do with GV, and either enable "Do Not Disturb" on GV settings, or delete your GV number(s) entirely. I'd suggest just placing them into DND and recording a new voicemail greeting directing people to call your CC number(s), for now, until you are darn sure you want to get rid of GV. It's difficult to get a new GV number at the moment, due to dwindling supply.
Since you already have Callcentric defined on SP1 and SP2, if you now decide to use those numbers directly, without using GV, then you don't have to do anything at all on your OBi. IF you also have GV defined on one of your SP slots, then just delete it locally.
TL;DR: in your particular case, since you are not adding GV service, you don't need to use the OBiTALK portal now.
Navigation
[0] Message Index
[#] Next page