Firewall check is failing 100% of ports, and no audio (both sides).

[billsecond]

I have 3CX newly installed on a Hyper-V VM behind my SonicWall router.

I have all of the ports opened up, and I have manually tested some of these ports myself by using a port listener application and an online web tool, but they are open when I do open them.

When I run the firewall checker utility part of the 3CX web application, it says if fails with all port checks. I really don't think it is accurate due to my other test.

When I do go to the server and get a whats-my-IP, I get the correct IP address, so I know the NAT settings on the firewall seems correct.

Please note the Windows Firewall is fully trunned off.

I am also getting no audio (both ways) when making or receiving calls from the outside of my network.

I am using Twilio for my SIP provider.

 

[Saqqara]

Have you seen this document on configuring sonicwalls ? - https://www.3cx.com/docs/sonicwall-firewall-configuration/

 

[billsecond]

Yes, and went through that document twice.

 

[billsecond]

All of a sudden, after a reboot, everything is working, except for the firewall check. Full audio both ways.

 

[billsecond]

But why is the firewall check failing?

 

[leejor]

Could it be something to do with SIP ALG?

 

[billsecond]

Nope, that is disabled.

 

[leejor]

Does your ISP issue you a public IP? I know there are some ISPs that "share" one public IP amongst a number of customers. There is no other hardware between 3CX, the router and the ISP? Do you have another, perhaps more simple router, to test with? If that worked, then you'd know it is a router configuration /option issue.

 

[billsecond]

No, its a dedicated unblocked IP. They are not blocking any ports. Again, the whole system is now working, but the Firewall Checker is not.

 

[leejor]

Does the current Firewall Checker "failure" look the same as the one you posted previously?

 

[YiannisH_3CX]

Hello @billsecond

The following guide explains how the firewall checker works and how you can troubleshoot it. You will need to run a capture parallel to the firewall checker to verify the results.
https://www.3cx.com/docs/firewall-checker/