For the next few days I will be testing a new feature on gvgw3: Google Voice (Talk) logins will follow a user’s SIP login. That is, Google Talk will only be logged in while your SIP device is registered (logged in). Until now, when you set up a Google Voice Gateway account, your Google Talk account would be logged in full-time until you deleted that gateway account. This change allows better use of resources on the gateway and allows the end-user some control over the Google Talk login if he/she wishes.
During the test I will be monitoring resource usage and stability of gvgw3. If the system proves to be stable then this arrangement will remain in place and a more formal announcement will be made. Additionally, I will be upgrading gvgw1 and gvgw2 to the current feature set of gvgw3 including this new login scheme.
Due to some shuffling at the provider hosting gvgw3.simonics.com, this gateway will have some brief downtime TODAY (2 January 2013) sometime between 4:00 and 7:00 PM EST. The IP address will change as well, so if you hard-code the IP rather than use the DNS name, you will need to update your configuration.
We will go through the same routine again next week when the server lands at its long-term home.
UPDATE: The maintenance of 2 January 2013 is complete. The IP address of gvgw3.simonics.com has changed; if you are unable to register your SIP device, you may need to reset it so that it gets the new IP address.
A Sunday afternoon project: XMPP chat and SIP instant messaging (“SIMPLE” or SIP MESSAGE). Here I started a chat with a Google account logged into the Google Voice Gateway. The gateway translated the XMPP chat message to SIP MESSAGE and sent it to the connected SIP client–in this case, Jitsi softphone (a full-featured softphone which I highly recommend). From the softphone, I responded to the chat message that popped up, sending a SIP message back to the gateway which then relayed it to the Google Chat contact.
This new feature is now standard on the Google Voice Gateway for all new registrations. Not so useful with softphones, but if you have a desktop or mobile IP phone that supports SIP SIMPLE/MESSAGE, you might find it to be a cool feature.
Registration is open once again for the Google Voice Gateway.
Along with this reopening of registration, I am pleased to announce a few new often-requested features:
- Alternate port 5070: You may need to use this port if your ISP blocks SIP on 5060.
- SIP over TCP: Users connecting with wireless devices (smart phones, tablets) may want to use the TCP transport to extend battery life. Unless you need this, however, UDP is still the preferred transport. Ports 5060 and 5070 are both available over TCP.
- XMPP priority 127: Previously, all GVGW accounts were set at standard priority 20, which allowed other Google Talk/Chat programs to “override” the login and intercept incoming calls. (For example, if you opened GMail chat on the same account as your Google Voice number registered on the GVGW, incoming calls would ring on GMail chat and not on the gateway.) Having received a lot of feedback on this, I’ve set the default priority to 127 (highest) for all new registrations. With that, all Google Voice calls should hit the gateway, even if you open other Google Talk clients on the same account.
- Multiple SIP registrations: The gateway permits only one SIP registration per set of SIP credentials. Donors to the project may request additional SIP accounts to be affiliated with a Google Voice number registered on the gateway. This setup allows you to receive incoming calls to any registered SIP device and place calls over your GV line from any of your registered SIP devices.
These features are enabled for new registrations only. If you are currently registered on gvgw1 or gvgw2 and want to enable the new features, please migrate your registration to a new gateway by deleting and re-adding your account.
This web site will be offline tonight from 11:00p.m. to 3:00a.m. EDT while the server is migrated to a new datacenter.
The Google Voice Gateway and Google Voice Fax by E-mail services will not be affected by the web site downtime.
Last week, Simon Telephonics released its first paid service, Google Voice Fax by E-mail. This extremely affordable service provides unlimited sending and receiving of faxes using a Google Voice number that you provide, and you can set up a traditional dedicated fax line or an on-demand fax line that you can use for both voice and fax calls. There is a two-day trial period during which you can test out the service. So, if you want to see how it works, sign up through the Members page and if you are not satisfied, you can cancel before the paid subscription begins.
Google Voice Gateway is out of service at the moment due to network connectivity problems at the hosting site. Follow phonesimon on Twitter for updates.
Update: Resolved at 17:45EDT.
Google Talk is currently experiencing an outage. This affects Google Voice through the gateway–no calls can be placed or received through the GVGW at this time. Until the outage is resolved, you may want to forward your Google Voice number to a mobile phone or other alternative.
For current information: Google Talk status page
Update: Google Talk service was restored at 11:00EDT and the Google Voice Gateway is operating normally again.
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.