Remote Analogue Extns using Patton SN4114

[PaulCarter]

Hi,

We have a new installation hosted by Google and are looking to deploy a Patton analogue gateway on site. On site currently we have an SBC connecting around 20 IP phones.
I have found old topics regarding this that say using the analogue gateway remotely is not supported however I see there is the option when creating the FXS/DECT gateway to choose the FQDN rather than the local IP within the Google cloud.

I have downloaded the .gwcfg file which has the FQDN in, past documents I have found state it should be pointing to the internal IP of the SBC on site, can someone confirm if this is correct please?

Thanks in advance.

 

[Evolute IT]

Hi,

We have a new installation hosted by Google and are looking to deploy a Patton analogue gateway on site. On site currently we have an SBC connecting around 20 IP phones.
I have found old topics regarding this that say using the analogue gateway remotely is not supported however I see there is the option when creating the FXS/DECT gateway to choose the FQDN rather than the local IP within the Google cloud.

I have downloaded the .gwcfg file which has the FQDN in, past documents I have found state it should be pointing to the internal IP of the SBC on site, can someone confirm if this is correct please?

Thanks in advance.

Normally your gateway would register locally to your PBX since it is the only officially supported way. VPN is included in "locally".

That being said, I know some have successfully connected a gateway via SBC. You would register to the FQDN using the SBC as a proxy.

However, are you trying to install a FXO gateway or FXS?

FXO is for POTS line connections.
FXS is to connect ATAs for analog phones and fax machines.

 

[eddv123]

Completely unsupported but I have done this plenty of times myself. I am only recommending SBC for analogue phones ONLY not FAX, PDQ, door entry or any other type of analogue endpoints.

To do this download the Patton template and change the registrar addresses (should be local IP of the 3CX system) to the address of the SBC instead, it will funnel all the calls through.

If you can setup a VPN however (possible with Google cloud) it is your best option.

 

[PaulCarter]

Hi,

Thanks for your replies. On the 3CX FXS setup we had to set the gateway IP address and mask as the ones we wanted on the remote LAN (IE 192.168.3.220 / 255.255.255.0) and then download the config file then open the config file in notepad and then replace all the entries for customer.3cx.co.uk with the local IP of the SBC on the remote LAN.

This now works fine!