Bryan, I understand, having run many Echolink nodes, EchoIRLP nodes, etc. for years…. However, the good news is you can limit who can connect! You can lock it down to certain callsigns, good for RACES group, etc… Unfortunately, despite several replies, I have the same config in echolink.conf as everyone sent me and it never shows up on Echolink. Maybe someone can catch my typo: [el0] confmode=no call=*CONFNAME* ; Change this! pwd=password ; Change this! name=Allstar 27408 ; Change this to your real name! qth=Allstar 27408 ; Change this to your actual QTH! email=kb8zgl@kb8zgl.net ; Change this! maxstns=5 rtcptimeout=10 node=8248 ; Change this! (Could this be my issue? Maybe I need to pad the zeros like Allstar does?) recfile=/tmp/recorded.gsm astnode=27408 ; Change this to your active Allstar node number! context=radio-secure server1=naeast.echolink.org server2=nasouth.echolink.org server3=servers.echolink.org freq=1 ; Freq in MHz tone=0 ; CTCSS Tone (0 for none) lat=0 ; Latitude in decimal degrees lon=-0 ; Longitude in decimal degrees power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) gain=0 ; Gain in db (0-9) dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction) From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Bryan D. Boyle Sent: Thursday, August 30, 2012 5:52 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink setup are you really sure you want to? serious question...i'm a lot happier and less agravated by the brain-damaged echolink boneheads since I set it up into a non connected pseudo node. connect to me...and it goes nowhere else. there is nothing you can do with echolink that you can't do with the web transceiver; and the barrier to entry is a bit higher, too. i realize this sounds unwelcoming and not in the spirit of ham radio...neither is the continuous kerchunking, dead key timeouts, and lack of understanding about the environment you are connected to. i prefer to shift the surfers off into a virtual dummy load. -- Bryan Sent from my iPhone please forgive misspellings... On Aug 30, 2012, at 13:21, "Mike Wolthuis" <wolthuis@gmail.com> wrote: I am trying to setup the echolink portion of an allstar node. I followed the instructions for echolink.conf. I don’t see any errors, I know chan_echolink is built in… Is there any way to check logs or what is happening? It doesn’t show up on Echolink. FYI, this is a conference (ie. *confname*). I am hoping that works ok? Any suggestions how I can troubleshoot this? Mike Kb8zgl _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users