FOOD FOR THOUGHT Replacing Simonics with GVSIP Gateways

[wardmundy]

Bill Simon has indicated that he plans to shut down his Simonics-GoogleVoice gateway whenever Google pulls the plug on XMPP. Some trunks already are not working properly at least for us.

It occurs to me that we really need an independent way for folks to set up their own Google Voice gateways using the new GVSIP technology. Now that we have a $1/month cloud-based offering from HiFormance that anyone can sign up to use, we plan to begin documenting the Asterisk setup process to interconnect remote VoIP servers to take advantage of either shared or dedicated GVSIP trunks on the HiFormance platform. Anyone could host dozens of Google Voice trunks at a monthly cost of only one dollar. This will make it easy for folks with VitalPBX, Issabel, Wazo, FreePBX Distro, AsteriskNOW, and 3CX servers to add Google Voice functionality until GVSIP is independently available on those platforms.

We hope to start rolling out setup instructions for the various platforms in the next few days. If anyone thinks of platforms we've missed, please post a comment.

NOTE: The choice of a hosting provider is obviously your call. We've only mentioned HiFormance because of the pricing and the ease with which you can set up an Incredible PBX server. We receive no compensation from HiFormance.

 

[wardmundy]

The following setup should work with an Incredible PBX GVSIP server platform as GVSIP-Host and a FreePBX Remote Server of any flavor. It could be an Incredible PBX server without independent GVSIP functionality or an Issabel, FreePBX Distro, or AsteriskNOW server. VitalPBX setup is slightly different and will be covered in the next post.

UPDATE: Just a heads up that, if you plan to implement this, we strongly recommend hosting the GVSIP server on a public IP address. And we also recommend using NeoRouter VPN or some other VPN solution for ALL of your interconnected servers. This not only provides encryption, it also eliminates firewall, router, port forwarding, and NAT issues between the various servers. It also avoids having to whitelist IP addresses in Travelin' Man 3 on all of your servers.

The setup below assumes that GVSIP1 is being hosted on GVSIP-Host server for use by a FreePBX Remote Server that lacks GVSIP capabilities. Incoming calls to the GVSIP1 number will be routed to the FreePBX Remote Server and then to the destination specified in the Inbound Route Destination (ext. 701 in this example). Outgoing 10-digit calls from extensions on the FreePBX Remote Server will be routed to the GVSIP-Host because of the Outbound Route's Dial Pattern and Trunk Sequence. When the call hits the GVSIP-Host, it will be treated just as if it were made from a local extension because of the from-internal context designation. Based upon the 10-digit dial pattern, it then will be sent to the GVSIP1 outbound route.

Interconnecting GVSIP-Host server with a FreePBX Remote Server (where FreePBX Remote Server is lacking GVSIP capability)

Trunk setup on GVSIP-Host where 10.0.0.29 is NeoRouter IP address of FreePBX Remote server (no registration on Host side!)

Outbound Route setup on GVSIP-Host for Outbound GVSIP1 Calls

Inbound Route setup on GVSIP-Host for GVSIP1 Calls Destined for FreePBX Remote Server

=============================================================

Trunk setup on FreePBX Remote Server where 10.0.0.3 is NeoRouter IP address of GVSIP-Host server (registration goes in Incoming tab)

Outbound Route setup on FreePBX Remote Server for Outbound GVSIP1 Calls

Inbound Route setup on FreePBX Remote Server for Arriving GVSIP1 Calls

 

[wardmundy]

The setups below assume that GVSIP1 is being hosted on GVSIP-Host server (10.0.0.3) for use by a VitalPBX Remote Server (10.0.0.28) that lacks GVSIP capabilities. Incoming calls to the GVSIP1 number will be routed to the VitalPBX Remote Server and then to the destination specified in the Inbound Route Destination (ext. 501 in this example). Outgoing 10-digit and 11-digit calls from extensions on the VitalPBX Remote Server will be routed to the GVSIP-Host because of the Outbound Route's Dial Pattern and Trunk selection. When the Outbound Call hits the GVSIP-Host, it will be treated just as if it were made from a local extension because of the from-internal context designation. Based upon the dial pattern, it then will be sent to the GVSIP1 outbound route.

Two different setups are provided: With IP Authentication and With Registration

Interconnecting GVSIP-Host server with a VitalPBX Remote Server Using IP Authentication

Trunk setup on GVSIP-Host with IP Authentication where 10.0.0.28 is NeoRouter IP address of FreePBX Remote server and 10.0.0.3 is IP address of GVSIP-Host

Outbound Route setup on GVSIP-Host for Outbound GVSIP1 Calls

same as GVSIP-Host Outbound Route Setup on FreePBX platform above

Inbound Route setup on GVSIP-Host for GVSIP1 Calls Destined for VitalPBX Remote Server

same as GVSIP-Host Inbound Route Setup on FreePBX platform above except Trunk Destination: vitalpbx

=============================================================

Trunk setup on VitalPBX Remote Server with IP Authentication where 10.0.0.3 is NeoRouter IP address of GVSIP-Host server and 10.0.0.28 is VitalPBX IP address

Outbound Route setup on VitalPBX Remote Server for Outbound GVSIP1 Calls

Inbound Route setup on VitalPBX Remote Server for Arriving GVSIP1 Calls (being routed to VitalPBX extension 501)

=============================================================

Interconnecting GVSIP-Host server with a VitalPBX Remote Server Using Username:Password Registration

Trunk setup on GVSIP-Host with Registration where 10.0.0.28 is NeoRouter IP address of FreePBX Remote server and 10.0.0.3 is IP address of GVSIP-Host

Outbound Route setup on GVSIP-Host for Outbound GVSIP1 Calls

same as GVSIP-Host Outbound Route Setup on FreePBX platform above

Inbound Route setup on GVSIP-Host for GVSIP1 Calls Destined for VitalPBX Remote Server

same as GVSIP-Host Inbound Route Setup on FreePBX platform above except Trunk Destination: vitalpbx

=============================================================

Trunk setup on VitalPBX Remote Server with Registration where 10.0.0.3 is NeoRouter IP address of GVSIP-Host server and 10.0.0.28 is VitalPBX IP address

Outbound Route setup on VitalPBX Remote Server for Outbound GVSIP1 Calls

Inbound Route setup on VitalPBX Remote Server for Arriving GVSIP1 Calls (being routed to VitalPBX extension 501)

 

[wardmundy]

This would be a LOT simpler if the Trunk name instead of GVSIP1 were the actual GV number. It seems to be not too well thought out!

Feel free to name your trunks however you like. It's merely an example based upon the naming scheme adopted for the new GVSIP rollout.