Google Voice accounts that fail to login (after they have been registered) will be removed on a somewhat regular basis. Basically, when I see statistics that show several accounts failing login, I’ll run the script to prune out those accounts. Accounts usually fail in this manner because the user changes his or her Google Voice password without coming back here to delete the GVGW registration first.
If you no longer want your Google Voice Gateway registration, please come back here and delete your account using the form.
The cause of this error can be hard to determine, because what we get back from Google is simply “not-authorized.” That doesn’t say much, and it could mean anything from entering the wrong credentials to account locked-out.
If you are certain that your username, domain, and password are correct, try following the advice on this page from Google. Today we were troubleshooting a problem with one user not being able to sign up. Others were signing up just fine, and this user could connect to GMail and other services with the account. Following the “Display Unlock Captcha” procedure listed on that page freed the account and he was then able to sign in.
The Google Voice gateway has been upgraded, seamlessly migrated to a new server with extra capacity. I also have a method for building out a gateway cluster, should the need arise. Who knows? This service has been very well-received.
The statement at the top of the registration form previously read, “Free during trial period,” and now reads “This service is donation-supported.” Thanks to everyone who helped me squash bugs and who made suggestions for improvement throughout the trial. Operation of the gateway will continue to be supported by the donations of those who use and enjoy the Google Voice Gateway.
Actually, that would be an understatement! Response has been overwhelmingly positive and the gateway is currently at capacity, so I have to disable new registrations for the moment. Existing users, please keep using and enjoying the service. Prospective users, your patience is appreciated while I build out additional capacity. I may occasionally open the registration in the meantime and let a few new users in as there is availability. Please check the blog for more information or follow my Twitter feed.
Existing users can retrieve their SIP credentials by filling out the form and choosing GetRegistration, or delete their registration the usual way.
Voxilla recently reviewed the Google Voice Gateway, highlighting its ease of use and concluding, “Simon Telephonics Google Voice Gateway is an excellent home solution for all but the heaviest users of Google Voice services.” You can read the review here.
Thanks to Hans for a quick note on how simple it is to set up the Linksys PAP2 with Simon Telephonics’ Google Voice Gateway.
Start by returning the adapter to factory defaults.
Referring to the settings page that appears when you have successfully registered your Google Voice Gateway, configure the PAP2 as follows:
Line1 on Linksys PAP2
Proxy and Registration
Display Name: Your name
User ID: Username
Use Auth ID: Yes
Auth ID: Username
Make sure that the Info page shows the line1 status/registration state as “ONLINE.”
I believe that the IT consultant who will be hired again and again is the one who acts dispensable–as if every day is his last day on the job or project, and someone else will be taking over. In other words, he or she documents everything thoroughly, ties up loose ends, makes code and scripts discoverable, provides links to guides and tutorials, and even shows the customer how to do the work himself. The only thing to be gained by the IT consultant who holds valuable information back is a reputation of shadiness.
Simon Telephonics’ Google Voice Gateway works with VoIP PBXes, such as Asterisk; stand-alone SIP phones, such as those from Polycom and Linksys; and mobile phones with SIP stacks, such as the Nokia n810. Asterisk users are abandoning the native gtalk driver, finding that incoming calls won’t connect, logins time out, and as of Asterisk 10.1, the gtalk audio path is broken. The gateway will get you reconnected using a standard SIP trunk.
TIP: Having trouble with the sign-up process? Make sure you can log in to Google Talk with your Google Voice-affiliated account using a third-party chat client before e-mailing for support.
This weekend, simonics.com got a fresh new look and a blog. Check back here for updates on the Google Voice Gateway and other news.