Rings But Cannot Answer
timandheike:
Hi Steve, I deleted the permissions to it and the problem still exists. I still think that something was done when I tied the home to use my GV number.
Perhaps like the ObiHai devices they're using the Google Chat option for outbound VOIP calling through the Home, but since Home only supports outbound calling at this time, they change some internal setting in the GV account related to that Google Chat option when you elect to display your own GV number rather than having an unidentified number.
As mentioned, if I setup another Google Voice account not associated with the Google Home device then it works. Also, removing the oAuth permission might not necessarily undo the change they made to the GV chat option.
This is all hypothetical and I might be wrong, but I'm trying to make sense of it. :-) Thank you for your help!
Driv3l:
I have the exact same problem, and it about the same time voice calling became enabled on the google home.
I am almost 100% certain it's related to Google enabling voice calling on the home (and if you use the same google voice on the Obi).
I tried all options to get it working viz. different phone ports on the Obi, different phone, unlinking the google voice account from the Google Home etc. Nothing works.
I also completely factory reset my Obi202 (after deleting it from the Obitalk account), updated the firmware, and completely reconfigured everything... problem is still there.
It seems the issues are related on the Google side once the account is enabled for voice called for the Google Home.
sunqx:
I am also having the same issue. It came right after I linked my Google Home with my Google Voice number. I switched back to using an unidentified number but the problem still exists. I used all of the solutions that Steve suggested but no success.
sunqx:
I removed the affected google voice account from my OBitalk account and set up with a different google voice number, which has never been associated with my Google Home. Then incoming calls work fine and I can answer. So I am pretty sure this issue is related to Google Home's voice call.
drgeoff:
Another instance http://www.obitalk.com/forum/index.php?topic=12911.0.
5 people reporting this may not be concrete proof that Google Home is implicated but surely there is a prima facie case for SteveInWA to bring this to the attention of his contacts at GV.
Navigation
[0] Message Index
[#] Next page
[*] Previous page