Sep 26

IP addresses for gvgw3, 4, 5, 6, 7 have changed

Google Voice Gateway users: If you are connecting to gateway gvgw3, 4, 5, 6, or 7, the IP address for your gateway has changed.

DNS entries were updated on Wednesday, so any new connections to these gateways will use the new IP addresses. If you are connecting with a PBX, IP phone, or other device/software that stays online continually, you may need to reload or restart your device for it to get the new IP from DNS.

Both the old IPs (starting with 64 or 216) and the new IPs (starting with 185) will be active until September 30. After that time, the old IP addresses will cease to work. Therefore, it is important that you reload or restart your SIP client before that time to avoid a disruption.

(If you have directly entered the IP address of a gateway into your SIP client’s configuration for some reason, you will need to look up your assigned gateway in DNS and reconfigure with the new IP address.)

Jun 14

Low-bandwidth GSM codec available on GVGW

Google Voice Gateway donors can select the GSM codec on their devices for significantly lower bandwidth usage at cellular voice quality.

Standard PCMU/G.711u codec

Lower bandwidth usage with GSM codec

The low-bandwidth codec and SIP TCP transport make the Google Voice Gateway a lean, battery-saving option for mobile VoIP.

Jun 11

Wednesday morning (12 June 2013) maintenance for gvgw1 and gvgw2

Between 6:00 a.m. and 8:00 a.m. EDT on Wednesday, 12 June 2013, gvgw1 and gvgw2 will be offline at various times for a code upgrade and feature sync. After this upgrade, these two gateways will match the others, including features mentioned in the following posts:

Please note: If you have been using gvgw1 or gvgw2 for outbound calling only, without SIP registration, you will no longer be able to do so by default. Please open a support ticket if you wish to do this.

In addition to this work, a new feature will be released for all Google Voice Gateways. By popular request, I am enabling a low-bandwidth codec, GSM-FR (typically called simply “GSM”), available to project donors. To use the codec, simply force GSM as the only codec by enabling it and disabling all others in your SIP device/software.

To donate and have this feature available, please visit the Donate page and include your Google Voice number in the text field of the PayPal form.

Feb 15

Did you hear, “Please donate today”?

The popular Google Voice Gateway is donation-supported; your donations cover the costs of hosting, caller-ID service, and ongoing development of the project. At random, you may hear a pleasant voice between the first and second ring of your outgoing call reminding you to “please donate today.” This recording is not delaying your call; it’s being played while the line is ringing. And if the called party picks up before or during the recording, the call will be connected without any delay, as usual.

If you have donated and don’t want to be reminded at random to donate again, e-mail with your GV number and your request to turn off the donation reminders.

New donors: The PayPal donation form now includes an optional field where you can enter your GV number. Do so and the reminders will be turned off for you, also.

Jan 23

Failed accounts to be removed later today on gvgw3

If you have a Google Voice Gateway account on gvgw3 and it is still failing to log in to Google Voice (following the maintenance two weeks ago that triggered “suspicious login” alerts from Google – see previous post), it will be removed later today. If you are reading this notice after the fact, just register again. It’s free!

Jan 09

gvgw3 gateway maintenance complete

Maintenance is complete on Google Voice Gateway gvgw3. If you use this gateway, you may notice that the IP address has changed. This should be the last change in IP for a while.

With this IP change, a number of Google accounts received warnings about blocked login. If your gateway account is not working, please check your e-mail on your Google Voice account and see whether Google has blocked the recent login attempt. If so, allow it and then restart your SIP device to cause the gateway to try logging in your account again.