![]() If outgoing calls are a must, they’re worth considering. Not too expensive, but definitely far from free. They all range from $35-40/year w/ unlimited incoming calls and ~300 minutes for outgoing calls. Since the main selling point of the OBiTalk devices was Google Voice being free, Obihai has recommended the following 2 VoIP services: That May 15th date is approaching and I’ve spent some time researching the alternatives. Google Voice has announced they’ll be ending XMPP support on May 15th which basically prevents any of the current VoIP devices/services from using it. But it looks like that party is coming to an end. ![]() Back then, I was using a Linksys PAP2 instead of my current OBi110. Instead, they’ve adopted OAuth (similar to how you can use Facebook or Twitter to log into random websites).įor the past 5 years I’ve been enjoying free VoIP calling via Google Voice, starting back when they were known as GrandCentral. Tada! That’s it! You’re no longer require to provide OBiTalk with your Google credentials. Once the firmware update completes, enter your area code and link it up with your Google Voice account.If this is your first time setting up with new Google Voice, it should prompt you to update your firmware which should take 1-2 minutes.Click on the new Google Voice Set-Up button above your service provider list.Setting up your Obihai device with Google Voice is simpler than before: Not sure if that’s purely a coincidence or the integration has opened up some access point that Obihai can now connect to. Today, Obihai announces that they’re officially supporting Google Voice again. Yesterday, Google announced they’ve integrated Google Voice into Google Hangouts. Though that hasn’t stopped me from finding a new solution while we wait for the inevitable. XMPP access was suppose to be disabled back in May, but I don’t think Google has actually pulled the plug yet. ![]() Google had announced they were disabling XMPP support awhile back, causing Obihai and other VoIP device manufacturers who were piggybacking on Google Voice to scramble for a new free/cheap solution. Otherwise I think oauth2-secured Asterisk connections, in the same way as Obihai’s, are acceptable.Obihai just sent out an email to all their users announcing that once again Google Voice is now officially supported on OBi VoIP devices. If Google wants to give an official word, I’m sure everyone would appreciate it. The spokespeople for Google Voice stop short of saying that Google approves of Obihai but does accept it because it switched to the secured login method. Someone asked about an “official” Obihai-Google relationship on the Google Voice forum. It is understood that Jingle is published but not ratified as standard so it could change at any time, thus the possibility of something breaking down. That said, I believe that Obihai, GVGW, and Asterisk users that adapt chan_motif to use the secure OAUTH2 are in the clear to connect to Google Voice this way. Whether that constitutes “reverse engineering” is unclear to me. There is/was trivial figuring-out of various necessary configuration parameters. There is no reverse engineering of protocols involved. Our connections to the Google Voice service are a combination of published protocols: OAUTH2 for authentication, XMPP for signaling, and Jingle for media. When making SIP connections, what is the “official API”? It is RFC 3261 and others that make up the suite of SIP-related protocols. ![]() I think we are mostly on the same page, James.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |