As Google Voice merges with Hangouts, possible impact on Obi support?
dconway:
For those of us who rely on the Google Voice service with our Obi devices, do we have reason to worry about Google removing (or degrading) the service as they migrate their communication apps to Google Hangouts?
Here's an article worth checking out:
http://www.theverge.com/2013/5/19/4346910/google-hangouts-upgrade-removes-host-google-voice-calls-gmail
giqcass:
Interesting article. There were ways to place Google Voice calls prior to xmpp support. If all else fails we can revert to one of those methods. I'm sure once Google has the new system up and running someone will find out how to connect to it. Hopefully OBiHai will implement it in their devices. I believe Google is moving towards web RTC. If that is the case it is meant to be an open platform which should make it easy to integrate into new devices like the OBi. Google will likely depreciate the current services once the new services come out of beta. They are unlikely to shut them off without a significant overlap period. They will also probably release documentation. This is to allow developers the time and resources to update their apps. Of course it's important to remember that sometimes Google works in mysterious ways. If all else fails there are many cheap services that will work with Obi.
FormerYooper:
Quote from: giqcass on May 20, 2013, 07:14:11 pm
Interesting article. There were ways to place Google Voice calls prior to xmpp support. If all else fails we can revert to one of those methods. I'm sure once Google has the new system up and running someone will find out how to connect to it. Hopefully OBiHai will implement it in their devices. I believe Google is moving towards web RTC. If that is the case it is meant to be an open platform which should make it easy to integrate into new devices like the OBi. Google will likely depreciate the current services once the new services come out of beta. They are unlikely to shut them off without a significant overlap period. They will also probably release documentation. This is to allow developers the time and resources to update their apps. Of course it's important to remember that sometimes Google works in mysterious ways. If all else fails there are many cheap services that will work with Obi.
giqcass .... would you care to expound on those ways to use GV prior to xmpp support? Do those ways *exclude" the Obi device? I think it's very interesting that Obihai is disturbingly silent since this announcement regarding the loss of xmpp support. And, if this new "likely" open platform does not integrate with the obi device ... then where are we? Will these other "many cheap services that will work with Obi" allow us to port our GV number over to them?
I'm sure many of us would appreciate some sort of statement from the Obi folks? Please!
dircom:
yes you can port your GV # to somewhere else.
and I would guess that Obi support knows as much about the changes as we do, at this point.
the sky is not falling
giqcass:
First off the beautiful thing about Google Voice is it will forward your calls to other phone numbers. That makes the porting problem less of a concern. I have in fact checked that my Google Voice number would port to Callcentric. There is a tool for this. www.callcentric.com/lnp/ Most companies provide a similar tool. I have been told not all Google Voice numbers will port the same so check your own number.
So far as "other solutions" are concerned. I previously used Sipsorcery. The old way worked similar to XMPP but it used a gateway. The gateway sent an http message to Google Voice on your behalf. That would generate a callback. Then the gateway would receive a sip call and connect it to you sip device. Any Sip device can be used in this way including the Obi. It takes a couple extra seconds for the other persons phone to start ringing on outbound calls but it's hardly noticeable.
Incoming calls just ring normally.
Navigation
[0] Message Index
[#] Next page