- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Echolink
by Tim Sawyer 24 Nov '11

24 Nov '11

You'll need to add it to the node stanza of rpt.conf. -- Tim :wq On Nov 24, 2011, at 2:29 AM, Lu Vencl wrote: > Tim, > Thanks for the info.. Which conf file will I find this in? I looked in rpt > and could not find it. > Thanks > > -----Original Message----- > From: Tim Sawyer [mailto:tim.sawyer@me.com] > Sent: Wednesday, November 23, 2011 10:06 AM > To: Lu Vencl > Cc: App_rpt-users(a)ohnosec.org list > Subject: Re: [App_rpt-users] Echolink > > Sure. Take a look at this link. http://ohnosec.org/drupal/node/103 > > -- > Tim > :wq > > On Nov 23, 2011, at 3:17 AM, Lu Vencl wrote: > >> Hey Tim, >> Did not know about this "timed telemetry". Can you tell me more about it? >> How do I set it up? >> Thanks >> Lu >> KA4EPS >> >> -----Original Message----- >> From: app_rpt-users-bounces(a)ohnosec.org >> [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Tim Sawyer >> Sent: Monday, November 21, 2011 9:32 PM >> To: Matt Roberts >> Cc: App_rpt-users(a)ohnosec.org >> Subject: Re: [App_rpt-users] Echolink >> >> Timed telemetry will announce when you initiate a connection and for a > short >> time thereafter. Incoming connections are not announced except when one >> happens to come in during the timeout period. >> -- >> Tim >> :wq >> >> On Nov 21, 2011, at 11:40 AM, Matt Roberts wrote: >> >>> If I don't want to have all Echolink incoming connections announced, is >> there a way to have outgoing connections announced? If I set Echolink >> telemetry to timed, how does that work? >>> >>> Matt Roberts >>> n9gmr(a)me.com >>> >>> Sent from my iPhone >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >

1 0

Zaptel modified for newer kernels & IOCTL issues.
by Ken Page 24 Nov '11

24 Nov '11

I've had some of the Zaptel code re-written to cope with the newer kernels and IOCTL issues and also some udev stuff. If anyone is interested in having a play with it you can get the patch off my server here. http://shazam.zapto.org/temp/zaptel.patch As per the normal warnings. Use at your own risk. However I'd be interested to hear how people go with it. I found this quiet a hurdle when updating our server here to the latest Gentoo Linux distro. Ken - vk4akp .-.-.

1 0

Re: [App_rpt-users] Echolink
by Tim Sawyer 23 Nov '11

23 Nov '11

Sure. Take a look at this link. http://ohnosec.org/drupal/node/103 -- Tim :wq On Nov 23, 2011, at 3:17 AM, Lu Vencl wrote: > Hey Tim, > Did not know about this "timed telemetry". Can you tell me more about it? > How do I set it up? > Thanks > Lu > KA4EPS > > -----Original Message----- > From: app_rpt-users-bounces(a)ohnosec.org > [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Tim Sawyer > Sent: Monday, November 21, 2011 9:32 PM > To: Matt Roberts > Cc: App_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] Echolink > > Timed telemetry will announce when you initiate a connection and for a short > time thereafter. Incoming connections are not announced except when one > happens to come in during the timeout period. > -- > Tim > :wq > > On Nov 21, 2011, at 11:40 AM, Matt Roberts wrote: > >> If I don't want to have all Echolink incoming connections announced, is > there a way to have outgoing connections announced? If I set Echolink > telemetry to timed, how does that work? >> >> Matt Roberts >> n9gmr(a)me.com >> >> Sent from my iPhone >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >

1 0

Re: [App_rpt-users] SVN app_rpt compile fails
by Dwaine Garden VE3GIF 23 Nov '11

23 Nov '11

Where is NEW_ASTERISK defined? There is no reason why I have it defined. Dwaine ________________________________ From: Dwaine Garden VE3GIF <dwainegarden(a)rogers.com> To: Dwaine Garden VE3GIF <dwainegarden(a)rogers.com> Sent: Wednesday, November 23, 2011 12:03:22 AM Subject: Re: [App_rpt-users] SVN app_rpt compile fails Where is NEW_ASTERISK defined? There is no reason I have it defined. ________________________________ From: Dwaine Garden VE3GIF <dwainegarden(a)rogers.com> To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> Sent: Tuesday, November 22, 2011 9:07:14 PM Subject: [App_rpt-users] SVN app_rpt compile fails I'm getting a compile error when trying to compile SVN. I can compile most of SVN, but it fails on app_rpt. Anyone seen this problem? [root@AsteriskServer asterisk]# make menuselect/menuselect --check-deps menuselect.makeopts Generating embedded module rules ... make[1]: Entering directory `/usr/src/trunk/asterisk/utils' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/utils' make[1]: Entering directory `/usr/src/trunk/asterisk/agi' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/agi' make[1]: Entering directory `/usr/src/trunk/asterisk/res' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/res' make[1]: Entering directory `/usr/src/trunk/asterisk/channels' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/channels' make[1]: Entering directory `/usr/src/trunk/asterisk/pbx' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/pbx' make[1]: Entering directory `/usr/src/trunk/asterisk/apps' [CC] app_rpt.c -> app_rpt.o app_rpt.c:542: error: âCONFIG_FLAG_WITHCOMMENTSâ undeclared here (not in a function) app_rpt.c: In function âuchameleon_pin_initâ: app_rpt.c:2598: error: too many arguments to function âast_config_loadâ app_rpt.c: In function âdo_dtmf_phoneâ: app_rpt.c:4367: error: too many arguments to function âast_senddigitâ app_rpt.c: In function âdo_dtmf_localâ: app_rpt.c:4435: error: too many arguments to function âast_senddigitâ app_rpt.c: In function âsend_usb_txtâ: app_rpt.c:4977: error: request for member âptrâ in something not a structure or union app_rpt.c: In function âsend_link_plâ: app_rpt.c:5000: error: request for member âptrâ in something not a structure or union app_rpt.c: In function ânode_lookupâ: app_rpt.c:5577: error: too many arguments to function âast_config_loadâ app_rpt.c: In function âforward_node_lookupâ: app_rpt.c:5650: error: too many arguments to function âast_config_loadâ app_rpt.c: At top level: app_rpt.c:5790: warning: âstruct ast_tmâ declared inside parameter list app_rpt.c:5790: warning: its scope is only this definition or declaration, which is probably not what you want app_rpt.c: In function ârpt_localtimeâ: app_rpt.c:5796: warning: passing argument 1 of âast_localtimeâ from incompatible pointer type app_rpt.c:5796: warning: passing argument 2 of âast_localtimeâ from incompatible pointer type app_rpt.c: In function âload_rpt_varsâ: app_rpt.c:5858: error: too many arguments to function âast_config_loadâ make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs.... make[1]: *** wait: No child processes. Stop. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs.... make: *** wait: No child processes. Stop. [root@AsteriskServer asterisk]# [root@AsteriskServer asterisk]# [root@AsteriskServer asterisk]# [root@AsteriskServer asterisk]# _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

2 1

SVN app_rpt compile fails
by Dwaine Garden VE3GIF 22 Nov '11

22 Nov '11

I'm getting a compile error when trying to compile SVN. I can compile most of SVN, but it fails on app_rpt. Anyone seen this problem? [root@AsteriskServer asterisk]# make menuselect/menuselect --check-deps menuselect.makeopts Generating embedded module rules ... make[1]: Entering directory `/usr/src/trunk/asterisk/utils' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/utils' make[1]: Entering directory `/usr/src/trunk/asterisk/agi' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/agi' make[1]: Entering directory `/usr/src/trunk/asterisk/res' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/res' make[1]: Entering directory `/usr/src/trunk/asterisk/channels' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/channels' make[1]: Entering directory `/usr/src/trunk/asterisk/pbx' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/trunk/asterisk/pbx' make[1]: Entering directory `/usr/src/trunk/asterisk/apps' [CC] app_rpt.c -> app_rpt.o app_rpt.c:542: error: âCONFIG_FLAG_WITHCOMMENTSâ undeclared here (not in a function) app_rpt.c: In function âuchameleon_pin_initâ: app_rpt.c:2598: error: too many arguments to function âast_config_loadâ app_rpt.c: In function âdo_dtmf_phoneâ: app_rpt.c:4367: error: too many arguments to function âast_senddigitâ app_rpt.c: In function âdo_dtmf_localâ: app_rpt.c:4435: error: too many arguments to function âast_senddigitâ app_rpt.c: In function âsend_usb_txtâ: app_rpt.c:4977: error: request for member âptrâ in something not a structure or union app_rpt.c: In function âsend_link_plâ: app_rpt.c:5000: error: request for member âptrâ in something not a structure or union app_rpt.c: In function ânode_lookupâ: app_rpt.c:5577: error: too many arguments to function âast_config_loadâ app_rpt.c: In function âforward_node_lookupâ: app_rpt.c:5650: error: too many arguments to function âast_config_loadâ app_rpt.c: At top level: app_rpt.c:5790: warning: âstruct ast_tmâ declared inside parameter list app_rpt.c:5790: warning: its scope is only this definition or declaration, which is probably not what you want app_rpt.c: In function ârpt_localtimeâ: app_rpt.c:5796: warning: passing argument 1 of âast_localtimeâ from incompatible pointer type app_rpt.c:5796: warning: passing argument 2 of âast_localtimeâ from incompatible pointer type app_rpt.c: In function âload_rpt_varsâ: app_rpt.c:5858: error: too many arguments to function âast_config_loadâ make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs.... make[1]: *** wait: No child processes. Stop. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs.... make: *** wait: No child processes. Stop. [root@AsteriskServer asterisk]# [root@AsteriskServer asterisk]# [root@AsteriskServer asterisk]# [root@AsteriskServer asterisk]#

2 1

Echolink
by Matt Roberts 21 Nov '11

21 Nov '11

If I don't want to have all Echolink incoming connections announced, is there a way to have outgoing connections announced? If I set Echolink telemetry to timed, how does that work? Matt Roberts n9gmr(a)me.com Sent from my iPhone

2 1

Block a station
by Neal Garbenis 21 Nov '11

21 Nov '11

I know with allstar you cannot block a station persay. I am having a problem with a certain node connecting to my system causing problems. Does anyone have some advice on how to stop this Neal NG8Y Sent from my iPhone

2 1

node list lookups
by George Csahanin 21 Nov '11

21 Nov '11

I have two nodes running here at my house, one is 2360, IP 65.68.232.25, one is an unlisted one, so to speak (1998) on 192.168.0.132 This gets complicated. 65.68.232.25 nats thru the router to 192.168.1.111, the box REAL address. I need to make a connection from 1998 on an inside address to 2360, but the directory address is 65.68.232.25. The inside addresses cannot see that address. Something with the router...and no one has been able to figure it out...it just is that way. However, I put a line in rpt,conf with this line: 2360 = radio(a)192.168.1.111/2360,NONE, this under [nodes] But when I go to connect from 1998 to 2360 it still won't, leading me to think that app_rpt, etc forst looks at the downloaded list and then at [nodes]. Is this correct? If so I'll just have to live with it. But if there is a way to make it look at [nodes] first, then the downloaded directory...etc. Kinda like hosts, bind in /etc/host.conf Any thoughts on this? Thanks everyone. GeorgeC Node 2360/2428 George J Csahanin W2DB Cedar Park, TX

3 4

Cross-Link X reflectors
by Shaun Rudling 19 Nov '11

19 Nov '11

Hi Ramesh, great stuff you are doing with those XRF reflectors. Question, 1- What module on XRF004 should we be connecting to? Are they separate individual modules, or are they all bridged together? 2- Which X reflectors can cross-link from allstar to dstar? XRF004A? XRF005A? XRF044B? Thanks Shaun zr5s

1 0

Port number for online update
by Shaun Rudling 19 Nov '11

19 Nov '11

Hi Jim, What port does the AllStar server use to get it's online configuration file from the AllStar server. I need to forward that port in my router. This is needed when I do the "nodesetup.sh" from the root. Shaun zr5s

3 3