Can’t reach a 3CX Patton Smartnode From Your Computer?

Home/3CX, Denton Business Solutions Blog/Can’t reach a 3CX Patton Smartnode From Your Computer?

Did you just push a new 3CX config file over to your Patton Smartnode only to find that you can’t reach the Smartnode over the web since it rebooted?

The same thing happened to me this week.  After I rebooted the Smartnode it took a few minutes for the SIP trunk to re-register to 3CX but I still couldn’t access the Smartnode from my computer any more, even though calls were going in and out.

The problem?

Once I lost connectivity from my computer, I grabbed my console cable and headed into the phone closet.  I logged into the Patton Smartnode (default login is administrator with no password), and sure enough – I could ping both 3CX (192.168.101.28) and the default gateway of the voice subnet (192.168.101.1):


192.168.101.253#ping 192.168.101.28
Sending 5, 56 bytes, ICMP echo requests to 192.168.101.28:
56 bytes from 192.168.101.28: Time <10ms
56 bytes from 192.168.101.28: Time <10ms
56 bytes from 192.168.101.28: Time <10ms
56 bytes from 192.168.101.28: Time <10ms
56 bytes from 192.168.101.28: Time <10ms
Ping statistics for 192.168.101.28:
Packets: Sent 5, Received 5, Lost 0 (0% loss),
RTT: Minimum <10ms, Maximum <10ms, Average <10ms

192.168.101.253#ping 192.168.101.1
Sending 5, 56 bytes, ICMP echo requests to 192.168.101.1:
56 bytes from 192.168.101.1: Time <10ms
56 bytes from 192.168.101.1: Time <10ms
56 bytes from 192.168.101.1: Time <10ms
56 bytes from 192.168.101.1: Time <10ms
56 bytes from 192.168.101.1: Time <10ms
Ping statistics for 192.168.101.1:
Packets: Sent 5, Received 5, Lost 0 (0% loss),
RTT: Minimum <10ms, Maximum <10ms, Average <10ms

Next I tested whether or not I could ping my computer from within the voice subnet but of course I couldn’t.  If that’s the case I thought perhaps there was something wrong with the routes on the Patton Smartnode so I checked the routing table:


192.168.101.253#show ip route
Route Table of IP context 'router':
Validity state (V): * valid, (*) duplicate, (-) down
Flags: U up, H host, G Gateway, L local, D default
-------------------------------------------------------------------------------
V Destination Traffic Cl. Interface (Next Hop) Protocol Met. Flags
-------------------------------------------------------------------------------
* 192.168.101.253/32 loopback Local 0 ULH
* 127.0.0.1/32 loopback Local 0 ULH
* 192.168.101.0/24 IF_IP_LAN Local 1 UL
* 127.0.0.0/8 loopback Local 1 UL
-------------------------------------------------------------------------------

The Solution

Sure enough – there’s no default gateway specified!  The auto-generated configuration file from 3CX must have overwritten that setting (since it was working before).  I had to add a new default route to the Smartnode’s routing table:


192.168.101.253#configure
192.168.101.253(cfg)#context ip router
192.168.101.253(ctx-ip)[router]#route 0.0.0.0 0.0.0.0 192.168.101.1
192.168.101.253(ctx-ip)[router]#end

Then I saved the configuration.


192.168.101.253#copy running-config startup-config

And tested:


192.168.101.253#ping 192.168.10.171
Sending 5, 56 bytes, ICMP echo requests to 192.168.10.171:
Request timed out.
Request timed out.
Request timed out.
56 bytes from 192.168.10.171: Time 190ms
56 bytes from 192.168.10.171: Time 830ms
Ping statistics for 192.168.10.171:
Packets: Sent 5, Received 2, Lost 3 (60% loss),
RTT: Minimum 190ms, Maximum 830ms, Average 510ms

192.168.101.253#ping 192.168.10.19
Sending 5, 56 bytes, ICMP echo requests to 192.168.10.19:
56 bytes from 192.168.10.19: Time 10ms
56 bytes from 192.168.10.19: Time <10ms
56 bytes from 192.168.10.19: Time <10ms
56 bytes from 192.168.10.19: Time <10ms
56 bytes from 192.168.10.19: Time <10ms
Ping statistics for 192.168.10.19:
Packets: Sent 5, Received 5, Lost 0 (0% loss),
RTT: Minimum <10ms, Maximum 10ms, Average <10ms

As you can see, now my Patton Smartnode is able to reach devices in other subnets. This took me a little while to figure out but I hope this article will save other engineers some time in troubleshooting. Having separate voice and data subnets is definitely a best practice network design for VoIP networks so I really wish 3CX’s Patton Smartnode configuration accounted for this. Until then I will try not to make any changes to my Smartnodes that require me to push another config file over!

About the Author:

Phil is the President and founder of Denton Business Solutions. He's had a fascination with technology for as long as he can remember. Phil uses that fascination to guide manufacturers to technology solutions for enhancing their plant safety, cybersecurity, and productivity. Outside the office, Phil enjoys cooking, spending time with his wife and son, and reading up on the latest manufacturing news. You can connect with Phil on Facebook, Twitter, and LinkedIn!

Leave A Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.