RTP Ports Issue

[TayZaLinZaw]

Hi 3CX team ,
We are facing with this issue on customer site. We already did ports forward in Pfsense firewall.

How Can be solve this ? please help us guys .

 

[Alphabetic]

Hi

does firewall test pass?

 

[TayZaLinZaw]

Firewall checker did not pass.

 

[bitn2]

Did you follow the maual? https://www.3cx.com/docs/pfsense-firewall/

What are you using in front of your pfsense? Maybe another router? Double NAT?

 

[TayZaLinZaw]

Did you follow the maual? https://www.3cx.com/docs/pfsense-firewall/

What are you using in front of your pfsense? Maybe another router? Double NAT?

Yes, I followed that manual .

 

[Rick-Arcus-IT]

Did you create the static outbound mapping rule? Step 2 in the manual. Please show your outbound rules.

 

[TayZaLinZaw]

Did you create the static outbound mapping rule? Step 2 in the manual. Please show your outbound rules.

 

[Rick-Arcus-IT]

Looks correct, do you have a firewall in front of your PfSense? Does PfSense have a public IP as WAN?

 

[TayZaLinZaw]

Looks correct, do you have a firewall in front of your PfSense? Does PfSense have a public IP as WAN?

Yes , We have public IP as Wan.

 

[Rick-Arcus-IT]

Did you Change “NAT Reflection mode for port forwards” to “Pure NAT”, activate the “Enable NAT Reflection for 1:1 NAT” checkbox and activate the “Enable automatic outbound NAT for Reflection” checkbox? These settings are in System -> Advanced

 

[Guillaume Bourgeois]

Do you have set ;

1. Go to System > Advanced
2. Click Firewall & NAT
3. Set ‘Firewall Optimization Options’ to Conservative

 

[kent3]

I have always used "Manual Outbound NAT" for my port preservation but not sure that's what's causing your issue here. There's no web filtering in play here or ISP cloud firewall?

 

[Guillaume Bourgeois]

The question has already been asked, but I am asking again because it could be a likely cause.

Are you on double NAT? For instance, does your internet provider include its own router?

If you connect the network cable that is currently plugged into the PFSense to the WAN port... and instead plug it directly into your computer (bypassing the PFSense), do you get a public IP address directly? Is that correct?

 

[Rick-Arcus-IT]

The question has already been asked, but I am asking again because it could be a likely cause.

Are you on double NAT? For instance, does your internet provider include its own router?

If you connect the network cable that is currently plugged into the PFSense to the WAN port... and instead plug it directly into your computer (bypassing the PFSense), do you get a public IP address directly? Is that correct?

The question has already been answered. He already mentioned the PfSense has a public IP address. I believe the issue is somewhere in the NAT settings of the PfSense.

 

[kent3]

I'm assuming this is an "out of the box" pfsense setup, no additional packages installed, no limiters applied etc?

I do remember a long time ago, when first setting these pfsense boxes up, we had to disabled ipv6 as it caused all sorts of issues, Ive always stuck to that rule

 

[Guillaume Bourgeois]

The question has already been answered. He already mentioned the PfSense has a public IP address. I believe the issue is somewhere in the NAT settings of the PfSense.

Indeed, but I must emphasize the question: if the guide was followed step by step, it should work.If the problem persists despite following all the steps in the guide, a restart of PfSense might be necessary.

Or, PfSense could be located behind another NAT.

What is the version of PfSense?

 

[JohnS_3CX]

@TayZaLinZaw best open a case with 3CX Support for further investigation. The error you posted originally is before the firewall - the PBX itself has run out of ports on the host.

The firewall check failure is another issue by itself which also needs to be resolved after the first one.

 

[kent3]

Did you find a solution to this? Interested to know as we use pfsense a lot, just in case we stumble across a similar issue

 

[TayZaLinZaw]

Did you find a solution to this? Interested to know as we use pfsense a lot, just in case we stumble across a similar issue

The issue is still persist.

 

[bitn2]

The issue is still persist.

Did you open a ticket with 3cx? They could help you as @JohnS_3CX allready said.