Unable to Connect With 3cx License Server. Check Your Network and Try Again.
The 3CX Firewall Checker tool is used to bank check whether your router or firewall is assuasive network traffic to or from VoIP providers, bridges, external extensions and 3CX tunnel connections.
3CX telephone systems require all necessary ports to be forwarded one-on-one into the LAN toward the 3CX phone system, otherwise the configuration is considered unsupported.
You lot can find a link to download the 3CX Firewall Checker on our downloads page.
Having compatibility issues with onetime phones?
Check out the "PBX Delivers Audio" option.
The following ports need to exist open up for the 3CX Firewall Checker client to work:
- SIP Port UDP: 5091
- RTP Ports UDP: Range: 11000 – 11015
Running the 3CX Firewall Checker
The following ports demand to exist open for the 3CX Firewall Checker client to work:
- SIP Port UDP: 5091
- RTP Ports UDP: Range: 11000 – 11015
- Login to your 3CX Management Console
- Click on "Firewall Check" in the PBX Status section and click "Run".
- Results volition be displayed along with what you can do to troubleshoot the trouble.
Note:
The Firewall Checker will stop all 3CX services and the PBX will not exist bachelor for the elapsing of the test. The examination will by and large take approximately 4 – 9 minutes, and can be cancelled at any time.
If the 3CX Firewall Checker starts reporting issues later on the first few ports have been checked, endeavor disabling the port scan cheque on your firewall while running the examination.
3CX Firewall Checker Tests
The 3CX Firewall Checker will check for connectivity by making requests to the STUN servers.
Internet Reachability Exam
This test checks basic internet connectivity and if the STUN server is reachable.
Failure on this test:
- Ostend your connection to the net through a web browser
- Bank check configuration of firewall – does it allow connections to the internet on the port being checked? View ports used past 3CX hither.
- Is your firewall configured to permit connections to the port being checked on both TCP an UDP?
- Confirm correct STUN server in STUN server settings: "Settings" > "Network" > "Public IP", or choose a unlike STUN server to test.
- Ensure Windows Firewall is allowing connections on ports being checked.
- Ports may exist blocked by your Internet service provider.
Entering Connection Test
This exam checks if a server on the net can connect and communicate with 3CX on the port being checked. It is used to make up one's mind if one-to-one port forwarding is configured (which is required by the 3CX PBX).
If one exam succeeds, merely ii fail:
- Ensure your firewall/ router has static, one-to-one port forwarding configured.
- Some ports require static port mapping for both TCP and UDP. Cheque 3CX ports for more information regarding this.
"Success – Port forwarding is correctly implemented for this port. VoIP can work. This configuration is supported."
All tests have completed and your current configuration is supported.
"STUN server has no second address."
Your STUN server is configured incorrectly, and you will need to use another STUN server to run these tests.
"Failed – No response received or port mapping is closed. Port forwarding not configured correctly. "
Port Forwarding is not configured correctly for the port existence checked. In this case VoIP Providers and Remote extensions Volition NOT WORK. Log in to your router / firewall and configure port forwarding by entering the ports required past 3CX and forwarding them to the IP Address of the 3CX Telephone Organization machine.
"Failed – Firewall check failed. Some errors were detected. Please cheque your firewall configuration and try the test over again."
This bulletin is displayed if some ports pass and others don't, and will require farther investigation as to which ports failed.
Ensure your firewall/ router is not forwarding connections to another IP accost – all ports must be forwarded to the IP address of the 3CX phone arrangement.
"Failed – Malformed response received – (aka Symmetric NAT). Port forwarding not correctly implemented."
This message indicates that you do not accept a one-to-one NAT required for VoIP providers, Bridges and external extensions to work.
"STUN server did not respond or port forwarding is not configured on your firewall."
Possible reasons for this message:
- STUN server is not reachable
- STUN server is downward
- Port forwarding is not correctly configured.
"STUN server accost cannot be resolved ."
The reason for this bulletin could be a DNS issue, or the STUN server is no longer working.
"Failed – Malformed or no response received from configured STUN servers. Cheque your cyberspace connectedness, DNS settings, or alter STUN servers from Settings → Network → External IP Configuration section."
Your firewall may exist blocking packets, ensure port forwarding has been correctly configured.
"Failed – Port is in utilise past another awarding on this estimator." -OR-"SIP port is in employ by procedure {0}. The 3CX Firewall checker requires the SIP port to exist free."
This message displays if the port being checked is currently in use.
To observe out which process is using the port, blazon the following into control prompt (with "0000" replaced with the port number you need to bank check):
netstat -ano | findstr /I /C:"PID" /C:":0000″
This command will give you lot a Process ID (PID), which tin can be used to place the process by running the following command in command prompt (Replace "0" with the PID:
tasklist /fi "pid eq 0"
"STUN servers are not reachable. Cannot perform Firewall cheque. This configuration is not supported"
This message is generally caused by an cyberspace connectivity problem.
- Login to 3CX Management Console
- Navigate to "Settings" > "Network" > "External IP Configuration"
- Modify the STUN servers to i of the following:
- stun.3cx.com
- stun2.3cx.com
- stun3.3cx.com
- stun4.3cx.com
[3cx-clicktotalk id="29505" title="AatroxComms"]
Source: https://aatroxcommunications.com.au/3cx-firewall-checker/
0 Response to "Unable to Connect With 3cx License Server. Check Your Network and Try Again."
Post a Comment