3CX & NAT (Again)

[SteveITS]

@alek AFAIK pfSense doesn't have a SIP ALG "feature." Is there an ISP router upstream that could be doing that? Is the pfSense WAN IP a public IP or NATted from the ISP router? If the latter then the ports need to be forwarded on the ISP router also, or pfSense made its DMZ.

[Alek]

@steveits said in 3CX & NAT (Again):

@alek AFAIK pfSense doesn't have a SIP ALG "feature." Is there an ISP router upstream that could be doing that? Is the pfSense WAN IP a public IP or NATted from the ISP router? If the latter then the ports need to be forwarded on the ISP router also, or pfSense made its DMZ.

I don't think so but will ask our ISP if it's the case.
In the past, they told us that everything is open and unrestricted since it's a business connection.

Yes the pfsense WAN IP is a public IP.

[SteveITS]

@alek do you have some sort of firewall on the VM?

SIP ALG actively modifies the packets in transit.

[Alek]

@steveits
No firewall, it's the 3cx appliance

[Patch]

@alek My rules as similar but not the same

With

and

with

[Alek]

@patch
Thanks for the screenshots, what's PBX_IP_in_SIP in your rules ?

I edited my rules to make them looks like yours except for the PBX IP alias :

Dest. Address is our VIP

NAT Address is our VIP

There is some progress on 3cx firewall checker. Now the SIP ALG passes :

But still the same problem with the ports.

[Patch]

@alek said in 3CX & NAT (Again):

what's PBX_IP_in_SIP in your rules ?

The SIP address of the VoIP suppliers I use. Mostly defined by FQDN but some as small ranges of IP addresses (stored in a separate alias). Using it means I white list the IP addresses which can access my 3CX, decreasing it's attack surface.

Note this must also include the 3CX SIP server IP addresses to enable passing the fire wall testing.
3CX console -> Settings -> Network -> External IP Configuration
plus
sip-alg-detector.3cx.com

@alek said in 3CX & NAT (Again):

But still the same problem with the ports.

I suspect double NAT / CGNAT

[Alek]

@patch
If I put our VIP in source Address for Port Forward and Destination in Outbound I pass the SIP ALG test but I still have a problem with the ports match.
I'm waiting for an answer from our ISP about double NAT / CGNAT...

[Patch]

@alek Have you enabled static port mapping?
pfsense -> Firewall -> Nat -> Outbound -> Mapping -> Edit

[Alek]

@patch Yes it's checked

[Unoptanio]

@Alek

Hello

i have the same problem with pfsense 2.7.2 CE on baremetal (no provider router)

3CX ver20 on premise
IP Server 3CX in the LAN 192.168.1.137

Have you resolved?

I also followed this guide

ENG:
https://www.3cx.com/docs/pfsense-firewall/

ITA:
https://www.3cx.it/doc/configurazione-firewall-pfsense/

System Advanced Firewall & NAT :

[Alek]

@Unoptanio
Hi o/

Yes resolved. Started everything from scratch and it worked.

My outbound rule is :

My inbound rules :

PBX_Ports_WAN contains :

NAT is in Pure Nat too.

Verify the your 3CX server is using the correct WAN if you have multiple WAN/VIP.

[Unoptanio]

@Alek

i have one WAN only

the doors seem the same to me
I'm testing with 3cx version 20 on premise

[SteveITS]

@Unoptanio I don't think pfSense even has SIP ALG, check your ISP router for SIP ALG and disable it there.

[albgen]

The problem in your case is for sure that you have to change some parameters on 3cx.
From the web UI of 3cx go to Advanced->Parameters. Search with the local ip address value. It will find many entries. Change them to the public ip address. There should be only one left with the local ip.
Once you do this it will work and the firewall test will pass but there is still another problem with the port forwarding i think. Forx example i cant chat. Can't change the status on yhr 3cx client..

[Unoptanio]

@albgen

In the meantime I solved it and now everything works correctly.
I disabled pfsense's pfBlockerNG module and now the firewall test has improved significantly:

I discovered that by disabling the Top Spammers GEOIP category the 3CX test of full cone nat ports passes

Digging deeper and leaving the GeoIP Top Spammers category enabled, the entry causing the problem was "France" which I deselected from the list. (I connect from Italy)

more information here:

https://www.3cx.it/community/threads/configurazione-del-firewall-pfsense-con-3cx.116324/#post-429317

Another issue causing the firewall test to fail within 3cx:
having a pool of static public addresses I had reserved a specific one for the 3cx server. This caused the problem because it must be identical to the public address you use to go out on the internet. After setting it equal the test passed.

[SteveITS]

@Unoptanio said in 3CX & NAT (Again):

GeoIP Top Spammers

FWIW, as I recall "top spammers" is simply a horribly named list of entire-country IPs.

It is however valid to run the 3CX firewall test and then block IPs/countries to limit access. We do so on the 3CX servers we host.

[Unoptanio]

@SteveITS

This is my setup that works perfectly:

[Patch]

@Unoptanio I white list the IP address 3CX needs to work. White listing is done by adding an allow rule high up.
Required IP address include some 3CX company address as well as those used by your voip service providers.

[albgen]

@Unoptanio my firewall test is okay and all green. I can call and recieve also calls. Strangly, it is not working perfectly on the android app. I see the following

The only difference from the standard install is that i changed the https port to 5001 and of course added a NAT entry for that.

No idea why it is not working.