Port blocking

[Zido]

Hello! please tell me why ports are selectively blocked? What are these ports responsible for?​

​

Some undergone testing ports were removed from the text in order to reduce the number of characters.​

resolving 'stun-eu.3cx.com'... done

• resolving 'stun2.3cx.com'... done
• resolving 'stun3.3cx.com'... done
• resolving 'sip-alg-detector.3cx.com'... done
• testing 3CX SIP Server... done
  • stopping service... done
  • detecting SIP ALG... not detected
  • testing port 5060... done
  • starting service... done
• testing 3CX Tunneling Proxy... done
  • stopping service... done
  • testing port 5090... done
  • starting service... done
• testing 3CX Media Server... failed (How to resolve?)
  • stopping service... done
  • testing ports [9000..9398]... failed (How to resolve?)
    • testing port 9112... full cone test failed (How to resolve?)
    • testing port 9114... done
    • testing port 9116... done
    • testing port 9118... done
    • testing port 9120... full cone test failed (How to resolve?)
    • testing port 9122... full cone test failed (How to resolve?)
    • testing port 9124... done
    • testing port 9126... full cone test failed (How to resolve?)
    • testing port 9128... full cone test failed (How to resolve?)
    • testing port 9130... full cone test failed (How to resolve?)
    • testing port 9132... full cone test failed (How to resolve?)
    • testing port 9134... full cone test failed (How to resolve?)
    • testing port 9136... full cone test failed (How to resolve?)
    • testing port 9138... full cone test failed (How to resolve?)
    • testing port 9140... full cone test failed (How to resolve?)
    • testing port 9142... done
    • testing port 9144... done
    • testing port 9146... done
    • testing port 9256... full cone test failed (How to resolve?)
    • testing port 9258... done
    • testing port 9260... done
    • testing port 9262... done
    • testing port 9264... done
    • testing port 9266... full cone test failed (How to resolve?)
    • testing port 9268... full cone test failed (How to resolve?)
    • testing port 9270... done
    • testing port 9272... full cone test failed (How to resolve?)
    • testing port 9274... full cone test failed (How to resolve?)
    • testing port 9276... done
    • testing port 9278... full cone test failed (How to resolve?)
    • testing port 9280... done
    • testing port 9282... full cone test failed (How to resolve?)
    • testing port 9284... full cone test failed (How to resolve?)
    • testing port 9286... done
    • testing port 9398... done
  • testing ports [10600..10998]... failed (How to resolve?)
    • testing port 10600... done
    • testing port 10602... done
    • testing port 10604... done
    • testing port 10606... done
    • testing port 10608... full cone test failed (How to resolve?)
    • testing port 10610... full cone test failed (How to resolve?)
    • testing port 10612... done
    • testing port 10614... full cone test failed (How to resolve?)
    • testing port 10616... done
    • testing port 10728... full cone test failed (How to resolve?)
    • testing port 10730... full cone test failed (How to resolve?)
    • testing port 10732... full cone test failed (How to resolve?)
    • testing port 10734... done
    • testing port 10736... done
    • testing port 10738... done
    • testing port 10740... full cone test failed (How to resolve?)
    • testing port 10742... full cone test failed (How to resolve?)
    • testing port 10744... done
    • testing port 10746... done
    • testing port 10748... done
    • testing port 10750... full cone test failed (How to resolve?)
    • testing port 10752... done
    • testing port 10754... done
    • testing port 10756... full cone test failed (How to resolve?)
    • testing port 10758... full cone test failed (How to resolve?)
    • testing port 10760... full cone test failed (How to resolve?)
    • testing port 10762... full cone test failed (How to resolve?)
    • testing port 10872... full cone test failed (How to resolve?)
    • testing port 10874... full cone test failed (How to resolve?)
    • testing port 10876... done
    • testing port 10878... full cone test failed (How to resolve?)
    • testing port 10880... done
    • testing port 10882... full cone test failed (How to resolve?)
    • testing port 10884... done
    • testing port 10886... done
    • testing port 10888... full cone test failed (How to resolve?)
    • testing port 10890... done
    • testing port 10892... done
    • testing port 10894... full cone test failed (How to resolve?)
    • testing port 10900... full cone test failed (How to resolve?)
    • testing port 10990... full cone test failed (How to resolve?)
    • testing port 10992... full cone test failed (How to resolve?)
    • testing port 10994... full cone test failed (How to resolve?)
    • testing port 10996... full cone test failed (How to resolve?)
    • testing port 10998... full cone test failed (How to resolve?)
  • starting service... done

 

[ChrisC_3CX]

Just to clarify, the 3CX Firewall checker runs a series of tests by contacting our STUN servers and then merely presents the results depending on the traffic returned to it. That said, the 3CX PBX is not actively blocking any ports or traffic, all that matters are the nodes in between which, in most cases, is just the firewall on the 3CX PBX's site. The OS firewall is automatically configured upon 3CX Installation provided of course that 3CX has been installed as per our guides.

You can find a more detailed explanation on how the 3CX Firewall Checker works here: https://www.3cx.com/docs/firewall-checker/

What are these ports responsible for?

The ports that seem to be failing are the ports used for RTP traffic which is essentially the traffic for audio.

I'd first recommend taking a quick look at our firewall configuration guide here and check whether you are using one of the firewalls listed to also go through the corresponding guide and check it against your own firewall configuration.