Solved Getting "No Response" Message on phones when dialing on new installation

[kdmolle]

I have completed a new installation of 3CX on a Windows 10 System on a network behind a NAT. The
firewall checker has passed and extensions register on the system, but when I try to dial internal or external I get a message "No Response" displayed on the phones.

I tested the system on a Win 10 Laptop before we moved forward, and the only difference now is a New
Win. 10 Pro computer used as the PBX (install was completed onsite) and the port behind our firewall had to be 5062 instead of 5060 (as this is currently in use). I changed the port with my trunk provider as well. What is baffling me is that the phones will not even call each other but indicate registered on the PBX.

I have included my system info below, any help would be greatly appreciated

• 3CX Version: Pro Annual 16.0.2.910
• OS: Windows 10 (Ver. 10.0.18363)
• The 3CX Server Hosted: Onsite
• IP Phone: Grandstream GPX2135 & GPX2170 (FW Ver. 1.0.11.6)
• Provisioning Method: Local & STUN
• Trunk Provider: Bandwidth.com - IP Based
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[leejor]

Check the 3CX Activity Log, for one of the call attempts. Does one even show? Perhaps the sets are attempting to reach the wrong port?

 

[kdmolle]

No, the attempted calls do not show up in the log. I can receive calls from outside, but the phones cannot call each other or outside the trunk.

 

[leejor]

Have you re-provisioned the phones since changing the port? You may have to use Wireshark to confirm where the sets are attempting to connect. My guess would be that they are still trying to contact the server on port 5060, considering that you are not seeing any call attempts in the logs. The perplexing bit, is that if you are able to receive calls, then that would seem to indicate that the sets are registered, which means that they are contacting the server.

 

[JohnS_3CX]

STUN Phones aside, the local phones should be able to reach each other.

Please recheck the following points:

1. Extensions > Phone Provisioning > Provisioning Method -> LAN
2. Factory reset the phones
3. If the phones ask for user/pass hit cancel (this is due to the STUN RPS entry)
4. Reprovision them via the Phones section

And finally ensure you are not behind a double NAT scenario, the phones should be on the same subnet as the PBX and with no NAT/Firewall between them on the LAN.

 

[kdmolle]

Have you re-provisioned the phones since changing the port? You may have to use Wireshark to confirm where the sets are attempting to connect. My guess would be that they are still trying to contact the server on port 5060, considering that you are not seeing any call atempts in the logs. The perplexing bit, is that if you are able to receive calls, then that would seem to indicate that the sets are registered, which means that they are contacting the server.

Thank you for your reply, I had done that. I finally scrapped the install and started again fresh. The good news is all phones are registering and communicating like they should. I appreciate the help.