Google Voice representatives have published a note stating that XMPP connectivity to Google Voice — the method we are currently using — will be shut down on June 18. Read the short announcement here.
We are beta testing an updated Google Voice Gateway that will work with Google Voice’s new SIP interop. After testing, if successful, this update will be rolled out to all GVGW users without any intervention necessary, on or before June 18.
Besides allowing us to continue service beyond the XMPP shutdown date, this should alleviate some of the connectivity problems a number of users have reported.
There is the chance that the beta test will bring to light a show-stopping issue. If we are not able to use the new SIP interop with Google Voice, the gateway service will not be able to continue beyond June 18.
Further updates will be posted here as we continue testing and planning.
Google recently announced a beta test of a Google Voice Wi-Fi Calling feature: https://support.google.com/voice/forum/AAAAjq5-_rMaI7m1PrV21Y/?hl=en
The announcement notes that this feature disables compability with Obihai devices. Please note that it also disables compatibility with GVGW. It appears that enabling the Wi-Fi calling feature as described in this Google support article will permanently disable your ability to use that Google Voice account with GVGW. If this changes or any workaround becomes available, this post will be updated with new information.
I am setting the minimum accepted registration expiration on GVGW to 120 seconds as a trial. The gateway’s default minimum of 60 seconds had been in place since launch.
It is recommended that users set their minimum value to at least 120 seconds. UAs attempting to register with a shorter interval will get a SIP 423 “Interval too brief” response and are expected to send another registration that conforms to the server’s minimum.
This is standard SIP but not every UA implements the standard correctly. Also there could be some misconfigurations where users have set a maximum interval lower than 120 which would prevent them from registering.
A 60-second registration timer causes the client to refresh at 30 seconds, which is grossly excessive considering that the majority of devices doing this haven’t changed their IP addresses in weeks or longer. Even as a keep-alive mechanism, a 30 second refresh is unnecessary. UAs needing NAT keepalive should use the appropriate option and not abuse SIP REGISTER for that purpose.
Two more proxies were added to the GVGW cluster. Setting strict ACLs is not recommended due to the nature of our cloud-based service. Nonetheless, here are the new IPs for your reference:
126.96.36.199 has been added to the Google Voice Gateway proxy list.
$ dig @188.8.131.52 +short gvgw.simonics.com. a
To handle recent growth, a new GVGW node has been added: 184.108.40.206.
If you are using strict firewall or ACL rules, be sure to update your configuration for this new proxy.
A seventh gateway proxy was recently added: 220.127.116.11. Here is the full list.
$ dig +short gvgw.simonics.com. a
A new node, 18.104.22.168, was added to the GVGW proxy group today.
A new node, 22.214.171.124, is being added to the Google Voice Gateway proxy list today. If you have a restrictive firewall configuration or specific ACLs, be sure to add the new node to your list.
Our DNS provider suffered a major DNS outage from about 11:30 EDT to 14:30 EDT. During this time, this web site and Google Voice Gateway services were unavailable.