[App_rpt-users] Echolink node

[Bryan D. Boyle]

Same here, Tim.  Keeps the drive-bys and other low-info Echolink types occupied and the networked systems free of clutter so the rf and allstar users are able/free to use them without an issue.

--
Bryan
Sent from my iPad

> On Jan 16, 2014, at 3:05 PM, Tim Sawyer <tim.sawyer at mac.com> wrote:
> 
> Right, the Echolink node can be any existing node in your system. I have a node dedicated to Echolink with no radio attached. That way I can completely dis/connect Echolink as needed.
> --
> Tim
> :wq
> 
>> On Jan 16, 2014, at 9:14 AM, Mike/W5JR <w5jr.lists at att.net> wrote:
>> 
>> Tim, thanks. I think I get it. The echolink.conf points to a defined node. If I set up a node as non-radio (hub) or even private, then that can be the "Echolink" node. 
>> 
>> tnx
>> Mike / W5JR
>> Milton GA
>> 
>>> On Jan 16, 2014, at 10:48 AM, Tim Sawyer <tim.sawyer at mac.com> wrote:
>>> 
>>> There is nothing to set in rpt.conf other than the two level adjustments and the (not required) announcement setting.
>>> 
>>> Here’s my echolink.conf from a working node. Note the Allstar node is set here, not in rpt.conf and must point to an active node on your server.
>>> 
>>> [el0]
>>> confmode=no
>>> call=WD6AWP-L        ; Change this!
>>> pwd=xxxxxx        ; Change this!
>>> name=Tim        ; Change this to your real name!
>>> qth=HB RACES [Allstar 2534]    ; Change this to your actual QTH!
>>> email=xxxxxxx at gmail.com ; Change this!
>>> maxstns=20
>>> rtcptimeout=10
>>> node=520439        ; Change this!
>>> recfile=/tmp/recorded.gsm
>>> astnode=2534        ; Change this to your active Allstar node number!
>>> context=radio-secure
>>> server1=server1.echolink.org
>>> server2=server5.echolink.org
>>> server3=server3.echolink.org
>>> ;naeast.echolink.org
>>> ;nasouth.echolink.org
>>> ;servers.echolink.org
>>> ;backup.echolink.org
>>> freq=145.140
>>> tone=110.9
>>> lat=33.677793
>>> lon=-118.000978
>>> power=10
>>> height=50
>>> gain=6
>>> dir=0
>>> 
>>> 
>>> --
>>> Tim
>>> :wq
>>> 
>>>> On Jan 15, 2014, at 10:36 PM, Mike/W5JR <w5jr.lists at att.net> wrote:
>>>> 
>>>> Need some direction here. I have added the echolink.conf file and the Echolink server is listing the callsign as available. This is the extent of the Echolink help that I've found on the ohnosec site. 
>>>> 
>>>> What I've not be able to locate is what (proper) entries need to be made in the rpt.conf file to support a given AllStar node as an Echolink node. I found the old "announcement" proclaiming Echolink support but following the detail for rpt.conf has not resulted in a working node nor the AllStar node showing active in the web listing. Loading my modified rpt.conf file kills one of my repeater nodes while another and two hubs continue to work. 
>>>> 
>>>> Any examples or pointing me to additional on-line help would be much appreciated. 
>>>> 
>>>> This is an ACID installation. 
>>>> 
>>>> tnx
>>>> Mike / W5JR
>>>> Milton GA
>>>> _______________________________________________
>>>> App_rpt-users mailing list
>>>> App_rpt-users at ohnosec.org
>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users