No argc is used in the subroutine not the calling arguments which are all contain in argv with size argc. I finally looked at the code which I should have done to begin with. The argument is 'n' ,'c', or 'i' for node, call, or IP. The reason anything seemed to work is because 'n' is default an I was entering the node. static int el_do_dbget(int fd, int argc, char *argv[]) { char c; struct eldb *mynode; if (argc != 4) return RESULT_SHOWUSAGE; c = tolower(*argv[2]); ast_mutex_lock(&el_db_lock); if (c == 'i') mynode = el_db_find_ipaddr(argv[3]); else if (c == 'c') mynode = el_db_find_callsign(argv[3]); else mynode = el_db_find_nodenum(argv[3]); ast_mutex_unlock(&el_db_lock); if (!mynode) { ast_cli(fd,"Error: Entry for %s not found!\n",argv[3]); return RESULT_FAILURE; } ast_cli(fd,"%s|%s|%s\n",mynode->nodenum,mynode->callsign,mynode->ipaddr); return RESULT_SUCCESS; } 73 Doug WA3DSP http://www.crompton.com/hamradio From: kk6ecm@gmail.com To: doug@crompton.com CC: app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Echolink database Date: Sat, 18 Jan 2014 13:57:21 -0800 The “1” is the argument count.. an integer number of arguments passed to the routine. It is a C and C++ thing. In this case, the node number is a single argument being passed to the routine that returns the nodename|callsign|IP address. See code below. Bob kk6ecm +* CLI extensions+*/++/* Debug mode */+static int el_do_debug(int fd, int argc, char *argv[]);+static int el_do_dbdump(int fd, int argc, char *argv[]);+static int el_do_dbget(int fd, int argc, char *argv[]); argc (“argument count”) ++static char debug_usage[] =+"Usage: echolink debug level {0-7}\n"+" Enables debug messages in app_rpt\n";++static char dbdump_usage[] =+"Usage: echolink dbdump [nodename|callsign|ipaddr]\n"+" Dumps entire echolink db\n";++static char dbget_usage[] =+"Usage: echolink dbget <nodename|callsign|ipaddr> <lookup-data>\n"+" Looks up echolink db entry\n"; From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Doug Crompton Sent: Saturday, January 18, 2014 10:17 AM To: Tim Sawyer Cc: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink database 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