Firewall checker stalls after new firewall install

[BW~Merlin]

We have just changed firewalls so wanted to make sure 3CX was working properly but when I try and run the firewall test it just stalls (has been running for like 20+ minutes with no progress). The detecting SIP ALG is reporting not detected but nothing else (ports 5060, 5090 or 9000+) have progressed at all.

Our new firewall is a Smoothwall S14 and if we set the default rule (any any) to allow the test will go through fine (currently it is set to deny). However even though the firewall test isn't making any progress, 3CX is working (inbound, outbound and internal calls).

Sound I be worried? Does anyone have experience with Smoothwall about any special tricks we may need to do?

 

[Alphabetic]

Is it stopping services? It could be having trouble doing that.

Have you tried restarting the PBX then running the check again?

 

[Rhys Haskell]

I had this issue when the server didnt have access to DNS.

 

[BW~Merlin]

I had this issue when the server didnt have access to DNS.

I have just noticed a heap of these errors with our backup SIP trunk

SIP Server/Call Manager ID: 12293
Registration at OurISP has failed. Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.

This would imply (to me at least) a DNS issue but unsure why as websites etc are resolving correctly.

 

[Rhys Haskell]

I have just noticed a heap of these errors with our backup SIP trunk

SIP Server/Call Manager ID: 12293
Registration at OurISP has failed. Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.

This would imply (to me at least) a DNS issue but unsure why as websites etc are resolving correctly.

What DNS server are you using?

 

[BW~Merlin]

What DNS server are you using?

Our internal DNS servers are our Windows domain controllers.

As of right now the backup trunk is now up and running. A little unsure what fixed it but perhaps a server reboot?

 

[JohnS_3CX]

Hi @BW~Merlin

Although nothing conclusive from the description, sounds like a DNS/network error or firewall issue.

Was the connection healthy at the time of the test? If ALG was not detected then the test was able to run up until that point at least, otherwise it would say "failed"