Google Voice - still working - and its 16 May 2014
KCChris:
Back when the cut-off date for GV arrived I put my Obi100 aside and kind of wrote it off. I pulled it out again today to see if I could find a use for it and when I plugged it in it I was surprised to see it was still working through GV.
When I was mucking around in the Obi Dashboard I clicked on the GV provider option and got a prompt that my device needed new firmware to support GV. I proceeded with the update and everything continues to work fine. I can't find any real details on the firmware and what it provided.
So to my question - is there some magic in this new firmware to make my Obi Google Hangouts friendly or was this just a normal process when configuring GV and I'm still at the mercy of Google shutting off XMPP whenever they choose?
Thanks!
MikePA:
Quote from: KCChris on September 05, 2014, 10:01:53 pm
So to my question - is there some magic in this new firmware to make my Obi Google Hangouts friendly or was this just a normal process when configuring GV and I'm still at the mercy of Google shutting off XMPP whenever they choose?
No, there's no 'magic' to make it work with Google Hangouts. If it did, Google Hangouts would be shown as an Approved Service Provider, not Google Voice.
Yes, XMPP could disappear.
There are plenty of posts by SteveinWA that go into more detail.
SteveInWA:
Quote from: MikePA on September 06, 2014, 01:27:39 am
Quote from: KCChris on September 05, 2014, 10:01:53 pm
So to my question - is there some magic in this new firmware to make my Obi Google Hangouts friendly or was this just a normal process when configuring GV and I'm still at the mercy of Google shutting off XMPP whenever they choose?
No, there's no 'magic' to make it work with Google Hangouts. If it did, Google Hangouts would be shown as an Approved Service Provider, not Google Voice.
Yes, XMPP could disappear.
There are plenty of posts by SteveinWA that go into more detail.
Right; thanks, Mike. I specifically answered that question already. The firmware update only changed the way that the OBi devices authenticate to the user's Google account. It removes the old method, which used the user's Google account user name and password, to simulate the user directly logging into the Google Chat system. Instead, it now uses Google's OAUTH 2.0 authentication method to ask the user to permit OBi to have secure access to their account, and then exchanges access tokens to enable it. The user name and password are never stored by Obihai. You can tell that you have the new firmware, if you hear the female voice prompts on your OBi device, instead of the former male voice.
This doesn't change the continued, actual use, by OBi devices, of XMPP protocol for call setup and call management. You will not find any reliable, official information on Google's continued support of XMPP, nor any public commitment by Obihai or Google to support OBi devices on Hangouts, going forward, unless or until such support actually changes. Google never comments publicly on specific future product features.
ramjet73:
Quote from: SteveInWA on September 06, 2014, 07:21:47 pm
This doesn't change the continued, actual use, by OBi devices, of XMPP protocol for call setup and call management. You will not find any reliable, official information on Google's continued support of XMPP, nor any public commitment by Obihai or Google to support OBi devices on Hangouts, going forward, unless or until such support actually changes. Google never comments publicly on specific future product features.
@SteveInWA I've seen your posts in the Google Voice group so I know your information is pretty accurate, and apparently you are also an Obihai beta tester.
Without getting into Google or Obihai future plans, is there some explanation for why Google Voice is now featured at the top of the list of approved providers (see attached screenshot) and Obihai has bothered to change its authentication method for a service that is presumably dead and Obihai users were expecting to be cutoff "any day now". It seems like if the authentication method needed to be changed for compatibility that would have been a perfect opportunity to officially drop support for Google Voice. ???
I'm not asking for futures, just an explanation of these changes that have already occurred. ;)
dircom:
Steve does not work for Obi, so how would he or anyone (expect for an Obi employee), know why Obi does what it does?
your question makes no sense
Navigation
[0] Message Index
[#] Next page
[*] Previous page