Buy Obihai OBi200 VoIP Telephone Adapter with Google Voice & SIP with fast shipping and top-rated customer service. Newegg shopping upgraded ™.
Here is a way to get SIP account by register your Google Voice account on 'Simon Telephonics' server.1) Create Google Voice accountYou need a permanent US Google Voice number so people can call you on that number. The registration requires US IP (you can use ) and US phone number for verification.a) There are many ways to have free US phone number. Don't use the same US phone number to verify multiple Google Voice (Google won't allow it).
OK, perhaps I should clarify: I'm looking for a standalone ATA, not a service which acts as a SIP/SDP/RTP gateway, or a MagicJack-like dongle that plugs into a USB port.The Simon Telephonics Google Voice Gateway has one of the same problems as Obi, that you're giving your credentials to a third party, so if they're compromised, they have at least the auth tokens to use that part of your Google account. (BTW.do I see that right? The service has no recurring charges, just the setup fee?) Plus, what about latency? I already forward GV to Callcentric, and anytime a VOIP or cellular part is added (basically, anything digital so that it must buffer audio to some extent) I think there is extra delay.
But maybe with Simon it's minimal, or it's not even proxied through them; dunno, haven't tried it and would like your opinions/experiences.It would be a subscription service (ongoing cost), but PBXes.org also offers what they call Google Voice Peering. They're a neat Asterisk-in-the-cloud service, free with some limitations (mostly only so many GB of traffic per month) for most SIP/RTP stuff.I also don't have Windows, only Linux, so a GVMate is not practical. I'm also not looking to run another computer continuously (I already have 3 of those, don't need to add another continuous 60 watts or so.looking for maybe 5 or 10 at most). Said by:I also don't have Windows, only Linux, so a GVMate is not practical. I'm also not looking to run another computer continuously (I already have 3 of those, don't need to add another continuous 60 watts or so.looking for maybe 5 or 10 at most)AFAICT, it certainly is very impractical to use a computer as a VoIP system and/or as a VoIP server for personal usage. Not only it is clunky to take up more spaces and will consume a lot of power, but it will also generate more heat and noise to pollute its surrounding environment.AFAICT, there are at least two inexpensive approaches one can implement to enjoy Google Voice free services for personal usage, namely:1.
A PBX system on a small device (consumes no more than 5 Watts of electricity), i.e. (under US $10 and can run with thousands of packages including, etc.), etc., + any inexpensive standard ATA devices and/or IP Phones as the extensions.2. Any inexpensive pre-paid Android smartphones, i.e. (under US $10), etc., with a WiFi connection. Since we know WiFi is not a duplex connection, this approach may and/or may not be desirable.I have implemented both the above approaches using a PogoPlug Pro 02 as a multi-purpose server to host my digital PBX system and some inexpensive pre-paid Android smartphones through a WiFi connection as other extensions to my PBX. Said by:The Simon Telephonics Google Voice Gateway has one of the same problems as Obi, that you're giving your credentials to a third party, so if they're compromised, they have at least the auth tokens to use that part of your Google account. (BTW.do I see that right?
The service has no recurring charges, just the setup fee?) Plus, what about latency?Authorization given to the Google Voice Gateway only permits login to the Google XMPP service and can be revoked at any time from the GW itself or from Google's account management page.The service has been running in the singular setup fee mode for a little over a year now. Previously it was funded by user donations.Media is proxied through the gateway because direct media is not possible (Jingle RTP differs from standard SIP RTP). Latency from the gateways to Google Voice is about 13ms. So if you are in the eastern US where our gateways are, your latency should be pretty low, likely lower than your forwarding through CallCentric. From elsewhere, maybe not.
Ping gvgw.simonics.com to see. Add 13ms to your results. Said by:The Obihai devices seem fairly popular. You'd figure with a community with the kind of size it has, there'd be at least ONE company making a competing product.Well, unfortunately there is not 'at least ONE company making a competing product'.Paranoia aside, the Simon Telephonics Google Voice Gateway (GVGW) referenced by others is the easiest solution. Rather than looking at more complex (and possibly unworkable) PBX or Asterisk options.I have two quite inexpensive accounts.
One-time up front payment, no ongoing charges. With Bill Simon's GVGW. Each GoogleVoice DID is registered to the gvgw.simonics.com server. And has been used by me at various times on my PAP2T and SPA8000 ATAs, my iPhone (with BRIA), my Android device (with Grandstream's Wave app), and an ExpressTalk softphone on my laptop. Said by:Latency from the gateways to Google Voice is about 13ms. So if you are in the eastern US where our gateways are, your latency should be pretty lowIndeed I am, in the Buffalo area. Because you're not contacting Google directly, you are going through a gateway.
Protocols like SIP and SDP, and possibly the Jingle extensions to XMPP which GV uses, embed IP addresses within the protocol, so NAT is not handled well at all. That is the reason a gateway must be used. Virtually everyone is behind some form of NAT these days. It's also possible GV does not support ICE to compensate for NAT.
The RTP which is used to carry the audio likely has to go to and come from whatever sets up the call, which is the gateway, then the gateway will proxy the RTP (the audio) for you, which adds some delay as it goes first to the gateway and then to Google (and the reverse, audio from Google going first to the gateway and then relayed to you). Said by cptobvious.a better expierience.Indeed - it looks like Obi users are having a wonderful time lately. Their better experience includes being disconnected from Google, firmware confusion, and surprise requests for $10 support upcharge.More to the topic, the issue of support is that there were a few solutions (including ours and Obihai) that relied on username/password login to connect to GVoice. That login method is deprecated in favor of oauth2, which Google supports because it is far more secure. Both Obihai and GVGW (and modified Asterisk) use oauth2 now.
Said by:Indeed - it looks like Obi users are having a wonderful time lately. Their better experience includes being disconnected from Google, firmware confusion, and surprise requests for $10 support upcharge.If you already own an Obi ATA I would think that the $10 is better spent using simonics GV service, considering you still get to use all the Obi dial plans without the curves thrown at you if you go through the OBiTalk service to maintain your GV account. This is the way to cut the cord with OBihai servers without loosing your GV service. Google Fiber Phone GFPB100 VS OBi 200If you need any proof that the Google Fiber phone service is basically just using a re-branded OBI 200 take a look at this picture. I'm pretty sure the Google Fiber Phone service is using Google voice at it's core also as Google Voice has been a big beta test. And with Fiber, they can just prioritize the traffic on it's own VLAN like AT&T does with Uverse VOIP to avoid NAT issues and guarantee QoS. That is probably why there is such a tie in with the OBi products and not much else that functions like it with Google Voice.