Google Voice back as Approved Service Provider!?
SteveInWA:
Quote from: lezleeann on September 12, 2014, 08:06:52 am
I am having trouble getting Google Voice working on SP2. I have Vestalink setup and working fine on SP1. My Google Voice on SP2 keeps saying configuring after going through the setup as directed. I do have 2-step verification turned on for the Google account I am using for this. Would that cause it not to work?
Obihai's old instructions for this scenario say to do the following:
If you have enabled Google 2-step verification for Gmail, please follow the following instructions so that you will be able to use your OBi and Google Voice.
Sign in to your Google account settings.
Select the, Authorizing applications & sites link.
Create an application specific password for Google Voice.
Use this password when you configure Google Voice as a service on your OBi device.
However, Obi has now changed the process and I have no way to use an application specific password once I generate one in my Google account.
Any ideas?
This is the one scenario that nobody has yet gone through in detail. I believe that the "approved service provider" method of setting up Vestalink (or Anveo or PhonePower) locks down some aspects of the OBi's configuration. I suggest opening a ticket with Obihai to get the "official" answer and help from them in understanding their recommended way of "peacefully coexisting" with a managed configuration of Vestalink. The alternative is to configure Vestalink manually, but I suggest starting with Obihai support.
RE: two-step verification, you do NOT need to disable it, and whether or not you are using it is unrelated to any issue with the OBi GV setup. Under the new GV setup process, you independently log onto your GV account by yourself, in one open tab on your web browser, using your GV user name, password, and if applicable, your two-step verification method. You then log into the OBiTALK portal in another browser tab of the same browser, and configure your OBi for GV. The configuration process will "see" your logged on Google session, and ask it permission to access your Google account in the future. You'll see a pop-up window on your Google account asking for you to permit this. Once you do so, Obihai and Google exchange secure "access tokens", and there will be no future need for the OBi to know your password at all.
Spidey:
@SteveinWA, thanks for all of the information and an honest 3rd party prospective on GoogleVoice, XMPP and Obihai. I had boxed up my Obihai-202 some time ago until I received an e-mail this week from Obihai indicating that GoogleVoice was supported again in Obihai products. So I fired up the device and configured it for my GV account. It's working great! For now anyway! :)
Crow550:
Quote from: Crow550 on September 12, 2014, 03:09:21 pm
Do you still need the Google Talk option under Phones in the Google Voice settings or can you remove it now?
Anyone test this?
Appears this is still needed:
So now that Google has officially supported the Obi Devices and Voice is slowly merging to Hangouts....
In order to use G-Voice with an Obi you need to have Google Chat under your Forwarding Phones. (If you removed it you have to go into Gmail and select old chat if you're using Hangouts and click the Phone icon and it will re-appear in your Forwarding Phones. No plugins needed, just open the Google Chat Dialer to have it re-added.)
So I think they should rename it Google Hangouts and not Google Talk under Forwarding Phones and remove the option to remove it. Or name it Hangouts for Calling Devices....
Also on a another yet similar topic using the Google Voice Chrome extension when clicking a number to dial there is no Hangouts option (even though you can pick a number at the Google Voice site and select it to dial through Hangouts) and Google Talk does nothing.... (Well it will ring your Obi Device.)
I assume the Google Voice Chrome Extension will be phased out and that functionally be added to Hangouts too. Needs an option to select one of the Forwarding Numbers or VOIP line (Hangouts/ Obi Device).
Course instead of merging and removing the Google Voice extension and site. I hope they keep them and just copy the functionally to Hangouts and have the Google Voice and Hangouts site and extensions sync with each other.
So those who enjoy Google Voice and not Hangouts can still enjoy it and those who love Hangouts can use all the Google Voice stuff within it. ;)
Like some businesses that are using Google Voice may not need what Hangouts offers.
Just some kinks that need to be worked out....
lezleeann:
Quote from: SteveInWA on September 12, 2014, 07:00:41 pm
Quote from: lezleeann on September 12, 2014, 08:06:52 am
I am having trouble getting Google Voice working on SP2. I have Vestalink setup and working fine on SP1. My Google Voice on SP2 keeps saying configuring after going through the setup as directed. I do have 2-step verification turned on for the Google account I am using for this. Would that cause it not to work?
Obihai's old instructions for this scenario say to do the following:
If you have enabled Google 2-step verification for Gmail, please follow the following instructions so that you will be able to use your OBi and Google Voice.
Sign in to your Google account settings.
Select the, Authorizing applications & sites link.
Create an application specific password for Google Voice.
Use this password when you configure Google Voice as a service on your OBi device.
However, Obi has now changed the process and I have no way to use an application specific password once I generate one in my Google account.
Any ideas?
This is the one scenario that nobody has yet gone through in detail. I believe that the "approved service provider" method of setting up Vestalink (or Anveo or PhonePower) locks down some aspects of the OBi's configuration. I suggest opening a ticket with Obihai to get the "official" answer and help from them in understanding their recommended way of "peacefully coexisting" with a managed configuration of Vestalink. The alternative is to configure Vestalink manually, but I suggest starting with Obihai support.
RE: two-step verification, you do NOT need to disable it, and whether or not you are using it is unrelated to any issue with the OBi GV setup. Under the new GV setup process, you independently log onto your GV account by yourself, in one open tab on your web browser, using your GV user name, password, and if applicable, your two-step verification method. You then log into the OBiTALK portal in another browser tab of the same browser, and configure your OBi for GV. The configuration process will "see" your logged on Google session, and ask it permission to access your Google account in the future. You'll see a pop-up window on your Google account asking for you to permit this. Once you do so, Obihai and Google exchange secure "access tokens", and there will be no future need for the OBi to know your user name or password at all.
I got it working by deleting my Obi100 from my dashboard, doing a reset on the Obi, then re-adding it to my dashboard and then going through Obi's process of adding Google Voice to SP1. Then for Vestalink, I added it to SP2 manually. Even though Vestalink doesn't recommend this method, I won't be renewing with them anyway now that Google Voice is officially back. Thanks for all the help detailing how to get it working! These forums are a fantastic.
dfresh:
I updated to the new Google Voice authorization and setup, failed to update over wifi on my 202 several times but finally went through. Setup was way easier and smooth.
HOWEVER! Since about March or April, any direct Google Voice incoming call to my Obi202 rings about three short double rings and the rings sound weak and interrupted each time. Goes to voicemail too fast.
The very best way to stop this was to forward GV to free IPComms DID which rings iIMMEDIATELY and strong long ring 4 or 5 times before voicemail.
I thought the update and new "approved GV" would let me eliminate the IPComms but it is the same. I also have free DID's from Callcentric, ipKall and Anveo but IPComms gives quickest and longest rings and time to get to phone before voicemail.
I have Anveo setup for 911.
OH!!! I have GV at this time on sp2. It did same feeble rings and quick voicemail on sp1. The IpComms DID is Detroit and I am in Oklahoma City
Google Voice was perfect the whole year or so of the original setup on its own. It is a good setup now but I have heard IPComms free DID comes and goes so I was a litte concerned to get GV standalone wih my 202 again?????!!!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page