Firewall Check Fails After Upgrade to v16

[Frank86]

Just upgraded from v15.5 SP6 to v16.
All good, except that the firewall check fails, even though nothing has changed on the Firewall side.
The firewall is a Meraki, which does not use SIP ALG.
All the same ports as v15.5 are set up in the firewall.
Ran the test twice, with the same result (the 2nd test also added the mapping issue between port 9192 and 9194
Am I missing something?

 

[AWS2P]

Hi ,
others 3cx users related same problem with V16 FWC, is the FWC giving you some bad different ports each time you run it ?
If it was good in v15.5 ,that's the same for V16

 

[Frank86]

Yes, it shows random bad ports every time I run it.
Thank you.

 

[Alphabetic]

Have you rebooted the firewall to clear out routing and such? Sometimes that can resolve this issue.

 

[AWS2P]

Done , change nothing on my side

 

[Alphabetic]

is this a Windows instance? if so, have you checked windows firewall

 

[AWS2P]

Windows on premise, FWC green in v15.5 and red in V16, same PC, no ports change on FW rules nor in computer side.

 

[Matt Waechter]

We have also seen this issue with multiple upgrades. On a couple if you run the FWC a couple times it shows good, we do have one that has yet to pass but everything seems fine. All issues have been Windows hosts.

 

[Alphabetic]

And what happens if you turn off Windows Firewall and run the test?

Your Windows Firewall might be set to exclude ports 1234 for 3cxapp.exe.

V16 might have installed 3cxappv1.exe, you'd have to look in Advanced Windows Firewall at the rule maybe.

 

[AWS2P]

i will try this tonight out of office hours and will let you know if it was the point.

 

[SussekNick]

My windows firewall is off, the check still fails for me too.

 

[YiannisH_3CX]

Please note that we have identified an issue with the Firewall checker on V16 which could cause some RTP ports to be flagged with the mapping does not match error.
If you are failing random ports every time with the same error then just ignore it for now until we can get this resolved. Your firewall configuration should be fine.

 

[YiannisH_3CX]

So, it may not have been necessary to add the extra OPN Sense firewall config?

It depends on what error you were getting back from the firewall checker. If the issue was the one described above then your firewall was probably setup correctly. If the guide helped you overcome the issues though then i would assume you were facing a different issue.