November 2011 - App_rpt-users - lists.keekles.org

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

23 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 22 Nov '11

22 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

Macros
by Matt Roberts 17 Nov '11

17 Nov '11

Do macros have to be just two digits? Is there a limit to the number of digits a macro can contain? IF I want to create a macro that tells my repeater to connect to my remote base, and control it, do I need to include the password as part of the macro? Matt Roberts n9gmr(a)me.com

1 0

Re: [App_rpt-users] Zaptel & newer Kernels.
by Jim Duuuude 17 Nov '11

17 Nov '11

like i dunno... even the latest DAHDI has ioctl's in it... Date: Thu, 17 Nov 2011 11:02:55 +1000 From: vk4akp(a)yahoo.com.au To: telesistant(a)hotmail.com Subject: Re: [App_rpt-users] Zaptel & newer Kernels. Apparently the newer kernels no long support IOCTL and the Zaptel stuff requires that to compile? I honestly don't know much about it. We've just done a major system update here and have pretty much 99% of everything running again. But the Asterisk is giving us headaches still. LOL It's just the Zaptel, radio interfaces, & TDM card we can't get happening at this point. The rest of your All_Star specific Asterisk install seems to be working OK. I know Dahdi is no good for us but we are using that currently to just get the system online so the conference can be used and so on until we can get past this zaptel problem. The Scottish Gentoo guy we have looking at the current issues will hopefully have more time this weekend to look at it further. I asked about going backwards to an older kernel but he said that's not preferable. Tell you what it's damn hot here too now. 35 deg C! Also see your Pres is over here visiting. Interesting stuff. ~Ken .-.-. On 11/17/2011 9:59 AM, Jim Duuuude wrote: what do you mean by "dont have the ioctl() stuff?" ?? JIM > Date: Thu, 17 Nov 2011 09:30:49 +1000 > From: vk4akp(a)yahoo.com.au > To: app_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] Zaptel & newer Kernels. > > Hi Guys, > > Well another week rolls by and although the Asterisk is running here the > TDM card and all DMK URI interfaces still remain offline basically > making us uncontactable this end. > > I am wondering if there are any plans to update Zaptel to work with the > newer kernels that don't have the IOCTL stuff? > > Or perhaps fix the Dahdi bugs? > > > Regards, > Ken - vk4akp > .-.-. > > >> ------------------------------ > >> > >> Message: 2 > >> Date: Mon, 14 Nov 2011 06:51:59 -0600 > >> From: "Jeremy R. Geeo [KD?EAV]"<kd0eav(a)gmail.com> > >> To: app_rpt-users(a)ohnosec.org > >> Subject: Re: [App_rpt-users] Install fails at zaptel on Gentoo system > >> Message-ID:<4EC10EEF.2060102(a)gmail.com> > >> Content-Type: text/plain; charset=UTF-8; format=flowed > >> > >> Hey Ken, > >> > >> Glad to see a fellow Gentoo(er) on the list. > >> > >> I don't know if you require such a new kernel; but 3.1.0 is very new > >> (especially for Zaptel). > >> > >> Last I knew, (but this may have since been patched) the zaptel modules > >> won't compile as-is on any kernel before 2.6.28 (ish - I may be off a > >> version or two, don't remember). I've only succeeded in making it work > >> up to 2.6.35 (becuase I DID need a newer kernel for hardware support). > >> In 2.6.36 they drop support for the ioctl call > >> (http://lwn.net/Articles/119652/) > >> > >> I haven't followed (or caught up) on changes since about 2.6.36, so I > >> don't know what has changed going into 3.0 and beyond. > >> > >> While trying to refresh my memory, I did find this zaptel patch (which > >> is actually for openWRT) which may be a step in the right direction for > >> the 2.6.36 barrier... > >> https://dev.openwrt.org/browser/packages/libs/zaptel-1.4.x/patches/370-2.6.… > >> > >> I've also found it handy to go into the config on zaptel and disable > >> many/most of the modules - I specifically only need ztdummy (and it's > >> dependencies). In your case, I assume you don't need support for > >> pciradio. Probably no sense troubleshooting that module if you're not > >> going to use it. > >> > >> > >> > >> 73 > >> > >> - Jeremy, KD0EAV > >> > >> > > > > ------------------------------ > > > > Message: 2 > > Date: Mon, 14 Nov 2011 17:53:49 -0800 > > From: Jim Duuuude<telesistant(a)hotmail.com> > > To:<vk4akp(a)yahoo.com.au>, app_rpt mailing list > > <app_rpt-users(a)ohnosec.org> > > Subject: Re: [App_rpt-users] How2 get radio stuff working with > > Dahdi??? > > Message-ID:<BLU155-W2488C2DBD79A3C7A0B3B3BB1C10(a)phx.gbl> > > Content-Type: text/plain; charset="iso-8859-1" > > > > > > well, thats just all well and wonderful except that DAHDI DOESNT WORK! > > Yes, it *STILL* has the *SAME* *STUPID* bugs in it that I had to fix > > in Zaptel. It isnt going to work for a radio project stock. > > > > JIM WB6NIL > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

GPS Reporting - Sending Reports Every 30 Seconds
by Kent Ochs 17 Nov '11

17 Nov '11

I recently turned on the GPS Reporting. There is no physically connected GPS, just a hardcoded coordinates. It is sending reports every 30 seconds. Is there anyway to increase the time between reports to something more reasonable, like every 10 minutes? Thanks. Kent

2 2

Re: [App_rpt-users] Zaptel & newer Kernels.
by Ken Page 16 Nov '11

16 Nov '11

Hi Guys, Well another week rolls by and although the Asterisk is running here the TDM card and all DMK URI interfaces still remain offline basically making us uncontactable this end. I am wondering if there are any plans to update Zaptel to work with the newer kernels that don't have the IOCTL stuff? Or perhaps fix the Dahdi bugs? Regards, Ken - vk4akp .-.-. >> ------------------------------ >> >> Message: 2 >> Date: Mon, 14 Nov 2011 06:51:59 -0600 >> From: "Jeremy R. Geeo [KD?EAV]"<kd0eav(a)gmail.com> >> To: app_rpt-users(a)ohnosec.org >> Subject: Re: [App_rpt-users] Install fails at zaptel on Gentoo system >> Message-ID:<4EC10EEF.2060102(a)gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> Hey Ken, >> >> Glad to see a fellow Gentoo(er) on the list. >> >> I don't know if you require such a new kernel; but 3.1.0 is very new >> (especially for Zaptel). >> >> Last I knew, (but this may have since been patched) the zaptel modules >> won't compile as-is on any kernel before 2.6.28 (ish - I may be off a >> version or two, don't remember). I've only succeeded in making it work >> up to 2.6.35 (becuase I DID need a newer kernel for hardware support). >> In 2.6.36 they drop support for the ioctl call >> (http://lwn.net/Articles/119652/) >> >> I haven't followed (or caught up) on changes since about 2.6.36, so I >> don't know what has changed going into 3.0 and beyond. >> >> While trying to refresh my memory, I did find this zaptel patch (which >> is actually for openWRT) which may be a step in the right direction for >> the 2.6.36 barrier... >> https://dev.openwrt.org/browser/packages/libs/zaptel-1.4.x/patches/370-2.6.… >> >> I've also found it handy to go into the config on zaptel and disable >> many/most of the modules - I specifically only need ztdummy (and it's >> dependencies). In your case, I assume you don't need support for >> pciradio. Probably no sense troubleshooting that module if you're not >> going to use it. >> >> >> >> 73 >> >> - Jeremy, KD0EAV >> >> > > ------------------------------ > > Message: 2 > Date: Mon, 14 Nov 2011 17:53:49 -0800 > From: Jim Duuuude<telesistant(a)hotmail.com> > To:<vk4akp(a)yahoo.com.au>, app_rpt mailing list > <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] How2 get radio stuff working with > Dahdi??? > Message-ID:<BLU155-W2488C2DBD79A3C7A0B3B3BB1C10(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > > well, thats just all well and wonderful except that DAHDI DOESNT WORK! > Yes, it *STILL* has the *SAME* *STUPID* bugs in it that I had to fix > in Zaptel. It isnt going to work for a radio project stock. > > JIM WB6NIL >

2 1