Tim (and all),

OK on rpt.conf. CCing this to the forum.

I think my confusion was between the xipar and acid Allstar versions. Apparently the xipar version uses the echolink/sl0 stanza setting.

Also I will be adding echolink call lookup to lsnodes for those that have echolink enabled.

Can anyone can explain the third parameter (shown as 1 below) for 'echolink dbget' ? It seems that it does not matter what it is but it has to be there.

WA3DSP_Allstar*CLI> echolink dbget 1 147090
147090|WA3DSP-L|50.191.8.33

WA3DSP_Allstar*CLI> echolink dbget
Usage: echolink dbget <nodename|callsign|ipaddr> <lookup-data>
Looks up echolink db entry

73 Doug
WA3DSP
http://www.crompton.com/hamradio

From: tim.sawyer@mac.com
Subject: Re: Echolink database
Date: Sat, 18 Jan 2014 07:55:52 -0800
To: doug@crompton.com

Sorry I didn't read your note thoroughly. Yes, zap/pseudo is the way to do it with no radio. Just add another node to your system and point echolink at it.

--

Tim

:wq

On Jan 17, 2014, at 10:55 PM, Doug Crompton <doug@crompton.com> wrote:

Tim,

What is the proper way to install echolink in rpt.conf ?

I tried -

rxchannel=echolink/el0

and on restart it failed - would not enter cli.

This is the way it is shown in the examples.

When I use -

rxchannel=Zap/pseudo

It works. In both cases the echolink.conf points to this stanza.

I want to have a node just for echolink. No radio. I will connect to radio node as desired.

Echolink seems to work with the pseudo channel, someone connected to me and we communicated.

73 Doug
WA3DSP
http://www.crompton.com/hamradio