Obihai Google Voice XMPP Solutions
gderf:
Quote from: simpleAnswers on January 12, 2014, 02:37:26 pm
My guess is there is a rush to ship as many of the Obi devices before all consumers catch on.
All the big sellers including Amazon and Newegg clearly state that Google Voice is not supported past May 15 2014. TigerDirect's adds don't even mention usability with Google Voice anymore. But if you buy stuff without doing any research or don't bother reading the adds, then you are likely to be disappointed.
As to the information about transitions from GV being "confusing or little" I suggest you read more and get a basic understanding of the device, the associated protocols, VoIP services in general, and try looking around some more. This topic has been beaten to death beginning the day someone associated with Google hinted at the end of XMPP.
drgeoff:
Quote from: giqcass on January 12, 2014, 04:31:16 pm
You can also run an Asterisk server that does the same thing as Sipsorcery.
I have experimented with GV on both an Asterisk PBX (Raspbx on RaspberryPi) and Sipsorcery and had both working successfully.
I am 99% sure that the current Asterisk GV implementation uses XMPP. https://wiki.asterisk.org/wiki/display/AST/Calling+using+Google contains the following sentence:
"Asterisk communicates with Google Voice and Google Talk using the chan_motif Channel Driver and the res_xmpp Resource module."
If correct, it will cease to work after 14 May.
swh2:
I have been using GV since before it was GV (grand Central) I have been using the Obi for at least 2.5 yrs. I guess the stupid and obvious question is why does Obi not work with google to come to a solution before May 1 or figure out what std gv is using after May 1 (not XMPP; not sure what the new std will be) and come out with a new obi box that supports the new service with similar functionality. Is that not a way to sell a lot of new boxes and keep obi going? I heard that Obi was a company run by a bunch of engineers not marketing people. If that the case well act like engineers and solve the problem. Dont make us solve it for you. Thats why I bought your device.
People always say well dont rely on free services to stay free and do what you want. Well Obi was not free and I give my data to google to sift thru and put up with their ads so they can make money off me. Also if google offered a paid work around to use Obi at a decent cost I would use it. But google is keeping everything hush hush as usual and offering customers no options. Everything with google is sort of a take it or leave it option.
I know this might be another thread but here is another issue: "Additionally, judges selected Daniel Klein and Dean Jackson from Google for the Robocall Challenge Technology Achievement Award." Google emp get an award for software that stops robo calling. No implementation of this in GV or Hangouts? Amazing. Of course the "phone" (land and mobile) cos are no better as they are not implementing nomorobo.com as I guess they can see naked phone service to robo collers and make a few bucks. Come on t mobile act like the "un carrier" you claim to be and fix spam calls
giqcass:
Quote from: drgeoff on January 13, 2014, 03:40:14 am
I have experimented with GV on both an Asterisk PBX (Raspbx on RaspberryPi) and Sipsorcery and had both working successfully.
I am 99% sure that the current Asterisk GV implementation uses XMPP. https://wiki.asterisk.org/wiki/display/AST/Calling+using+Google contains the following sentence:
"Asterisk communicates with Google Voice and Google Talk using the chan_motif Channel Driver and the res_xmpp Resource module."
If correct, it will cease to work after 14 May.
You are correct about the current method Asterisk uses but there was an old method that is similar to what Sipsorcery uses. You could run an old version of Asterisk before XMPP support was introduced or wait for the new version to switch to the old method. PBX in a flash may not do future GV support but other Asterisk implementations are sure to add it.
Quote from: swh2 on January 13, 2014, 09:23:11 am
I guess the stupid and obvious question is why does Obi not work with google to come to a solution before May 1
Short answer Google was never working with Obi. They made it clear they don't want their service to be used this way. Obi has a legitimate business beyond Google Voice integration to protect.
Quote from: swh2 on January 13, 2014, 09:23:11 am
I know this might be another thread but here is another issue: "Additionally, judges selected Daniel Klein and Dean Jackson from Google for the Robocall Challenge Technology Achievement Award." Google emp get an award for software that stops robo calling. No implementation of this in GV or Hangouts?
That is the question killing me as well. Callcentric is offering their own version free of charge and almost no carrier supports nomorobo. Fios is one of the few I know that supports it.
swh2:
Quote from: giqcass on January 13, 2014, 10:51:47 am
Short answer Google was never working with Obi. They made it clear they don't want their service to be used this way. Obi has a legitimate business beyond Google Voice integration to protect.
ok I get that but why doesn't Obi try to work with them now on a gv specific box. Again Obi is run by engineers like google. I think there is a engineering solution but I think google does not want to play with others, sort of like Apple and MS. I think google wants to force everyone onto the "Hangouts platform" (on all devices) and not offer an Obi off platform solution as they cant force ads and other things on you that way. Google is still obsessed with facebook which is now dying for the under 20 crowd. Next I expect google to make up some sort of an NSA excuse to rid their world of Obi
Navigation
[0] Message Index
[#] Next page
[*] Previous page