Jun 11

GVGW node addition

A new node, 162.243.210.200, 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.

Feb 09

GVGW node update

A new proxy node is being added to the cluster and will appear in the DNS SRV and round-robin A records shortly.

If you have firewall rules or ACLs restricting access to your SIP equipment, please add 162.243.107.101.

The rest of the list:

$ dig +short gvgw.simonics.com. a
45.55.163.124
198.199.84.66
104.236.102.59
Oct 15

New GVGW node added

A new proxy node has been added to the Google Voice Gateway (GVGW) cluster and is starting to appear in the A-record and SRV records. If you permitted specific IPs in your firewall or ACL, please note the addition:

198.199.84.66

The current list:

$ dig +short gvgw.simonics.com. a
45.55.163.124
198.199.84.66
104.236.102.5
Aug 21

Caller ID format

Google Voice Gateway was previously stripping the + symbol but leaving the leading 1 on caller ID sent for US/Canada calls. This was non-standard behavior and has been fixed.

Incoming calls from US/Canada will show a ten-digit “national format” caller ID, with name (CNAM) if available.

Incoming calls from other locations will show a full-format caller ID including the + symbol and country code. Name information is not available for international calls.

May 11

New Gateway feature: two-way SIP authentication

Starting today, the Google Voice Gateway is able to send SIP calls to your PBX with authentication. If the gateway receives a SIP 401 Unauthorized challenge to an INVITE, it will authenticate using the same username and password your equipment used to register.

This update allows those who are connecting to the Google Voice Gateway with a PBX to tighten their security, allowing calls only from known sources identified by IP address or authentication.

The new feature may be especially of interest to Asterisk users who have had to “allowguest=yes” and handle incoming GVGW calls as if they were anonymous due to Asterisk not being able to properly match peers using SRV or round-robin A records.

In short, to make use of this with Asterisk, set “allowguest=no” and “match_auth_username=yes” in sip.conf, then define your GVGW SIP peer as “type=friend” with the section name matching your GVGW account name. A more detailed tutorial will be available soon in the knowledge base.

Apr 19

Try Digital Ocean for your virtual server needs

I have several providers in my virtual hosting toolbox. One of my new favorites is Digital Ocean, a virtual server hosting company that uses KVM as their virtualization platform and has some great cloud-like features such as snapshotting and deployment from snapshot.

Digital Ocean is my pick for low-latency, high-throughput network and disk (SSD) I/O at a very good price. With VoIP applications, network quality is among the most important concerns. You get a public IPv4 and IPv6 address standard, so there’s no NAT to work around.

Use this link for $10 credit on Digital Ocean and add them to your own virtual hosting toolbox.

Apr 17

GVGW issues today

We are seeing a significant number of disconnects affecting GVGW users today and are actively investigating the problem.

Thank you for your patience.

UPDATE: I will be upgrading some infrastructure on Saturday early morning (midnight+) to resolve issues seen today. Expect brief outages during the Saturday early morning hours.

Maintenance to the databases was completed and gateways working at 2:00am.