NAT Inside Interface to OutSide Interface

Hi,

please your firewall rule.

Your firewall should look like any - internal network -> any - > external network-> service port 5001 -> allow -> log

You will not need MASQ.

Ian

Updated Protected Server

Updated Protected Server

This one saveid

This one saved I added ICMP as well but cannot ping it from inside

These are more ports currently

Hi Stephen,

I think you are trying too hard to confuse yourself?

Your 3CX is a VoIP PABX inside your firewall. Nobody can connect to it unless it establishes a connection.So providing a protected server firewall rule will not have any traffic through it.

The 3CX needs to setup and tell your ISP that it is online ready to receive calls. The calls will all be managed by your outgoing firewall rule contrail/SPI functions of the firewall.

Ian

Ok so I need to switch to the other rule

Here is what I changed it to

The other goal is to use their cloud provided url of 

• https://provideddomain.tx.3cx.us:5001/webclient

This maps back from there end to my public ip

Do I need to do anything else besides the rule above?

Do you think you and I can connect and I can show you?

Hi Stephen,

I think is getting to convoluted.

What I would like to see to help clarify things is

1/. a simple network drawing of your desired setup

2/. a call flow description

like 3CX is powered on - > sets up connection to VoIP provider - > outgoing call -> incoming call.

I am trying to understand what the URL you added to a post does?

Ian

Sorry here is a better explanation, its not anything for the URL, what I am wanting to then do is to configure my 3cx app so that I can be inside or outside of my network and be able to use my internal PBX externally.  Does this help?