Firewall Test Failing

[kriley87]

I have a fresh V16 install up and running and my firewall test results are attached.

I've got all of the required ports open in my Watchguard (see attached). I've got 3 extensions registered for testing and internal and external calls work fine with audio both ways. I can access the web GUI as well so it appears that my port forwards are working..

However if I direct my test DID to a digital receptionist, I see the call establish but I have no audio when the recording is playing.

What's weird is I have another 3CX install behind the same firewall that works just fine -- the only difference is the public IP addresses of them are on two different IP blocks.

Anyone have any idea of what I should be looking for?

 

[AWS2P]

If you do an internal call to IVR number from an extension do you have audio?

 

[kriley87]

Actually, I just resolved the no audio IVR issue by implementing a 1 to 1 NAT rule on my firewall but the 3CX firewall test still fails. I guess if there's no problems then the firewall test doesn't really matter?

 

[JohnS_3CX]

Hi @kriley87

You have opened the ports but not in Full Cone NAT (I think Watchguard calls it a Static NAT)

Take a look here: https://www.3cx.com/docs/watchguard-xtm-firewall/

The test fails because it say sends a packet from 5060 but the 3CX STUN server receives it from a different port than originally stated by your PBX (your firewall is remapping the ports).
This may or may not lead to issues since the firewall is doing something other than what what the PBX expects and can cause issues when the firewall throws a wrench in the works when you least expect it.