Firewall Check Error

[Heath]

I'm getting errors in the firewall check that says 'Full Cone Test Failed'... I went as much as to disable the firewall, and still getting the error...Help

 

[ChrisC_3CX]

I'm getting errors in the firewall check that says 'Full Cone Test Failed'

Have you made sure that all required ports have been configured on the firewall? The fact that you're receiving this message indicates that some of the tests are failing, may for instance be that the expected responses are never reaching the PBX. Make sure you don't have any outbound restrictions, geolocation restrictions, Destination/Source restrictions or anything lese that might be affecting the test.

I went as much as to disable the firewall,

Which firewall are you referring to, the OS firewall?

Also, could you please let us know where the PBX is hosted, what the OS and Hypervisor is(if applies), and what version of 3CX you are running?

 

[Heath]

the firewall on the OS is deactivated as I disabled the firewall on the router. As far as I can see. No restrictions

 

[ChrisC_3CX]

the firewall on the OS is deactivated as I disabled the firewall on the router. As far as I can see. No restrictions

In that case you might need to dig a bit deeper and perhaps perform two packet captures one on the Firewall's LAN interface and one on the Firewall's WAN interface to compare the traffic between them when running the firewall checker to hopefully help you narrow down where the issue might be.

If the firewall holds logs taking a look at them might not be a bad idea either as you may be able to determine if in fact packets in either direction are being dropped.

I do also recommend going over our document explaining how the 3CX Firewall checker works: https://www.3cx.com/docs/firewall-checker/

 

[Heath]

How would I run packet captures. I did look at the firewall checker. Much I didn’t under. Unfortunately when it comes to firewall I’m really not saavy in that

 

[ChrisC_3CX]

How would I run packet captures.

How to go about this will depend on the firewall being used and it's capabilities.

I would highly recommend considering contacting one of our Partners who have experience in these kinds of situations and more effective ways to troubleshoot as this will definitely need a more in depth investigation.

 

[Heath]

I tried 2 partners and they wouldn’t help me because I didn’t buy the license through them

 

[ChrisC_3CX]

Well, I do not know with whom you spoke and what was said, but, I would assume that, for receiving any kind of services from any of our partners you would have to first reach some kind of agreement.

In any case, what you could also do which now that I think of it might actually be the next best step, is contact whoever configured or manages that specific firewall so that they can make the necessary configuration adjustments as not passing the firewall checker rarely has to do with anything else other than the firewall configuration.

The documentation I provided earlier regarding the firewall checker and how it works should be all the information required for configuring the firewall correctly in regards to 3CX: https://www.3cx.com/docs/firewall-checker/

 

[Evolute IT]

I tried 2 partners and they wouldn’t help me because I didn’t buy the license through them

DM me. We do break/fix support without you having to buy a license from us.

 

[SweetAction]

What type of Firewall do you have? Even a picture of the box will help here.

 

[jed]

It could be caused by a dublicate MAC address on your network?

 

[Evolute IT]

It could be caused by a dublicate MAC address on your network?

IP address, not MAC. MAC is almost impossible to have twice on a network unless you use fake MACs.

 

[jed]

Yep, but installing several 3CX Debian Instances on Hyper-V (Server 2012 R2) - I managed to create an new virtual Debian server with an duplicated MAC
We are are using several servers, replicating / moving Instances from time to time, which might have caused the issue in my case. However it is quite easy to find this issue in the Eventlog, Warning Event ID 16945.