Thanks to those that responded... i had waited several hours/days without the node appearing active and do not have a second client running simultaneously within my network. The later responses indicated the search for my node failed to find a match, but that was because the wrong callsign was used. See below.
cruiser*CLI> echolink dbget c N9JPG-L
960818|N9JPG-L|71.194.253.53
>> Below that is my
echolink.conf file for reference. Note the servers listed - 1,5,3.
I used these in my conf file as it noticed that was what my echolink client was using.
server1=
nawest.echolink.org
server2=
nasouth.echolink.orgserver3=
servers.echolink.org>>Make
sure you point the echolink ports in your router to your allstar server
and as was mentioned you can only run one echolink node per public IP
address.
As noted earlier, that is all set as suggested on the howto page for allstar to do echolink.
Any other ideas?