Grandstream GXW-4104 via SBC for Cloud 3CX?

Status
Not open for further replies.

AGidi

Gold Partner
Basic Certified
Joined
Jun 30, 2017
Messages
96
Reaction score
20
Hello quick question.

Will a gateway Grandstream GXW-4104 on site, on the LAN with the phones work via the local SBC to reach a cloud based 3CX instance?

We have never used an FXO gateway behind NAT or double NAT. Phones work fine with SBCs. but gateways?

all comments are welcomed
thanks
 
I just order a Patton SN4114-JO which I plan to use in a similar manner for a client, but I am not sure it will work.

The 3CX instance is in the AWS and an SBC on premises with about 10 phones and have a couple of PSTN lines that I plan to connect to the patton and route it though the SBC to AWS.

If that doesn't work, then I may just have to convert that local SBC into a slave PBX and add the patton to it and create a bridge between the two PBXs, so that calls from the AWS PBX can be routed through the bridge and out the patton.
 
Anyone from the 3CX that can chime in? FXO gateways over SBC? Go, no Go?
 
Hello @AGidi

Please note that Gateways and ATA devices are only supported for local provisioning. SBC or STUN gateway devices are not supported. I would recommend using a VPN that will allow you to add the gateway as a local device.
 
I concur with what @YiannisH_3CX has said as far as supported is concerned however I can confirm I have had this setup work fine across the SBC using both Patton and beroNet supported FXO FXS and ISDN gateways.

All that is required is to generate the config as you would do locally but instead change the registrar address (3CX's local IP) to that of the SBC. It should then funnel all traffic down it to the remote end.

Again this is an un-supported configuration and if VPN is available use this.
 
I concur with what @YiannisH_3CX has said as far as supported is concerned however I can confirm I have had this setup work fine across the SBC using both Patton and beroNet supported FXO FXS and ISDN gateways.

All that is required is to generate the config as you would do locally but instead change the registrar address (3CX's local IP) to that of the SBC. It should then funnel all traffic down it to the remote end.

Again this is an un-supported configuration and if VPN is available use this.

Well this is Great news and I will be trying this same setup in a few days, so i'll be sure to post if I have the same luck.
 
Yeah should be fine I have done this scenario plenty of times.

Post up if you hit any snags however.
 
Status
Not open for further replies.