Firewall Tester Tests Unnecessary Ports in v15

[jms]

I don't want to have 256 RTP ports when I will never use most of them. If you run the firewall tester, it takes too long and that time is downtime.

I have a v15 site with 100 RTP ports: custom parameter FIRSTEXTPORT is 9000 and LASTEXTPORT is 9099.
When I run the firewall checker, it checks ports 9000 to 9255.

The firewall checker could be finished 60% quicker if it tested the correct port range.

 

[craigreilly]

funnily enough, 3cx says to open 9000-9500.
http://www.3cx.com/docs/3cx-phone-system-v14-ports/
so in that scenario, v15 doesn't test enough ports.

If I recall 9256-9500 was for webRTC.

 

[Sopock]

If you run the firewall tester, it takes too long and that time is downtime.

Maybe they need to modify this tool?

http://www.3cx.com/blog/voip-howto/3cx-firewall-checker-client/

 

[Sopock]

The firewall checker could be finished 60% quicker if it tested the correct port range.

I guess only option is to open all ports and then change it again?

If everything is configured correctly, the tests should take less than a minute. If there are issues with all the ports, the test can take between 4 and 9 minutes. You also have the option to cancel the test.
Dot alignment?

• resolving 'stun.3cx.com'..... done
• resolving 'stun2.3cx.com'... done
• resolving 'stun3.3cx.com'... done
• testing 3CX SIP Server...... done
  • stopping service...... done
  • testing port 5060..... done

 

[eagle2]

Maybe they need to modify this tool?

http://www.3cx.com/blog/voip-howto/3cx-firewall-checker-client/

This a client firewall checking tool, not of the PBX. It is useful for testing remote extensions operation

 

[craigreilly]

it doesn't really matter. my machine fails the firewall checker but we have no issues. every time we run the checker different ports fail in the 9000 range. the same firewall passed in v14.
just open the ports you need.