- App_rpt-users - lists.keekles.org

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 16 Nov '11

16 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 16 Nov '11

16 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

File Formats
by Matt Roberts 15 Nov '11

15 Nov '11

If I want to record voice files for my repeater, what can I use. I see in some places it says you can use WAV, or GSM. It lists one more format, but can't remember which one. WAV files are the easiest for me to create. CAn I use them? Matt Roberts n9gmr(a)me.com

5 7

How2 get radio stuff working with Dahdi???
by Ken Page 14 Nov '11

14 Nov '11

Hi Jeremy, Yep, love Gentoo. It's the best! hihi! Thanks for all the good info. It can take ages to Google and muddle your way through all this stuff sometimes and there's no point in trying to re-invent the wheel when others have already traveled these roads and know the answers. So, we've commented out a few things and emerged the dahdi stuff and the "make install_usbradio" now works and Asterisk is up again. In terms of Asterisk, we basically did this... 1. install dahdi, dahdi-tools and libpri using Portage 2. stop your Asterisk package from building libpri and zaptel 3. prevent building some Asterisk modules that needed extra deps or didn't like the new gcc 4. remove the ztcfg line from the init.d script because it's not needed 5. set the dahdi init.d scripts to start on boot However our next problem is that the TDM card is not working even though it's detected and started correctly. And none of the DMK URI radio dongles are flashing or working. So I need a shove in the right direction again sorry. Are there some lines in some of the configs that need changing to point stuff at Dahdi instead of Zaptel perhaps? Regards, Ken - vk4akp .-.-. On 11/15/2011 3:00 AM, app_rpt-users-request(a)ohnosec.org wrote: > > ------------------------------ > > 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 > >

3 2

Install fails at zaptel on Gentoo system
by Ken Page 14 Nov '11

14 Nov '11

OK, Here's my latest hurdle. The installer fails at the zaptel section. We've just updated the box to the latest Gentoo Linux OS and now I'm trying to get the Asterisk radio stuff up again. On the old Gentoo system it compiled and installed fine without over writing any configs. The log tail of the failure is below. If anyhow has any advice I'd appreciate it. Regards, Ken - vk4akp .-.-. . . configure: *** Zaptel build successfully configured *** (MAKELEVEL=0; make -C zaptel); # Why does MAKELEVEL need to be 0 for zaptel to build correctly? make: Entering directory `/usr/src/asterisk/trunk/zaptel' make[1]: Entering directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[2]: Entering directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[2]: `menuselect' is up to date. make[2]: Leaving directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[1]: Leaving directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[1]: Entering directory `/usr/src/asterisk/trunk/zaptel' make[2]: Entering directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[3]: Entering directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[3]: `menuselect' is up to date. make[3]: Leaving directory `/usr/src/asterisk/trunk/zaptel/menuselect' make[2]: Leaving directory `/usr/src/asterisk/trunk/zaptel/menuselect' make -C /lib/modules/3.1.0-gentoo/build ARCH=i386 SUBDIRS=/usr/src/asterisk/trunk/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o wcfxo.o wct1xxp.o wctdm.o wcte11xp.o zaptel.o ztd-eth.o ztd-loc.o ztdummy.o ztdynamic.o zttranscode.o wctdm24xxp/" modules make[2]: Entering directory `/usr/src/linux-3.1.0-gentoo' CC [M] /usr/src/asterisk/trunk/zaptel/kernel/pciradio.o In file included from /usr/src/asterisk/trunk/zaptel/kernel/zaptel.h:39:0, from /usr/src/asterisk/trunk/zaptel/kernel/pciradio.c:56: /usr/src/asterisk/trunk/zaptel/kernel/zconfig.h:26:28: fatal error: linux/autoconf.h: No such file or directory compilation terminated. make[3]: *** [/usr/src/asterisk/trunk/zaptel/kernel/pciradio.o] Error 1 make[2]: *** [_module_/usr/src/asterisk/trunk/zaptel/kernel] Error 2 make[2]: Leaving directory `/usr/src/linux-3.1.0-gentoo' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/asterisk/trunk/zaptel' make: *** [all] Error 2 make: Leaving directory `/usr/src/asterisk/trunk/zaptel' make: *** [llastate/zaptel-built] Error 2

2 1

RANGER network
by Bryan D. Boyle 13 Nov '11

13 Nov '11

Been working (with Jim...and hope he doesn't mind...) on some mods to the app_rpt module. The genesis for this was a posting on QRZ concerning the lack of consistent monitoring (or even accessiblity) of repeaters across the country, as well as the multiplicity of frequencies in use (note, I'm only talking about the US here...though, I'm sure that other countries have the same issues), PL schemes, etc. So...took this a step further. What if (how all great ideas start): 1. There was one agreed-upon frequency in the 2m band (which is the most popular, and accessible to all (well, except for the grandfathered Novice licenses...) hams. Some folks have bandied about 146.55. Idea is to NOT impinge on .52, satellite, repeaters, weak signals, sideband, etc. 55 is in the simplex range in the current band plan. 2. There was a way of having a transceiver (this is simplex, remember) physically connected via app_rpt/URI/etc to a local machine or linked network (such as the one I participate in here in eastern PA/NJ) that would be listening on 55...waiting for the LiTZ signal (and that's the only gating part...no PL, no processing, just waiting for the long zero...) in which case asterisk would: a. *3 to a targeted node/reflector/network b. using the nodename announce gsm file, announce its presence c. change add an extra 'feature' to the CT sequence to alert to the fact that the emergency node is connected d. be disconnected under the control of a control/sysop on the network after the issue had been resolved. 3. Part 97 says one of our three charters is to provide emergency services in the event we're called upon to do so. I'm taking a broad view and saying that a fellow ham, either themselves, or coming upon an incident, is well within their privileges to offer whatever aid they can. The fact is...driving across country for vacation with my ARRL Repeater Directory at my side...finding a machine that a) had someone listening and b) was accurately listed (freqs, PLs, offsets, locations..) was a hit and miss thing. Mostly probably because of b)...because when I was able to finally connect up with machines during the drive, there was always some OM out there willing to chew the rag. So, it's part of our charter. Besides...if you look at it...other licensed services, such as marine, aviation, heck, even Citizens Band, has defined emergency frequencies...and in the case of CB...an active cadre of folks who are visible presences on the highways (REACT comes to mind...say what you will...at least they make the effort....). Anyway, Jim took the bull by the proverbial horns and coded up the additions to the app_rpt.c code to do just that. At it's minimal implementation, you only need 3 lines in the rpt.conf file to activate the basic functionality, a URI, and an open USB port. So...the current SVN has the code in there to do just that. For what it's worth, I'm using an Alinco DR135, since in data mode, the DB9 connector on the back gives you all the right signals: discriminator audio, COR, audio in, PTT. VERY simple to interface. Just remember to put it into DATA mode... So, there are a few things to consider: 1. Registration of the node. Jim's set aside the 9xxxx sequence of node numbers for this proposal on AllStarLink. Oh, by the by, RANGER stands for Radio Amateur Network (for) General Emergency Response. If you want to participate, register for a node by putting RANGER in the comments field for the registration. You'll need to download the current svn, build, and install the software and build the configs for the additional uri to bring it up. 2. He's registered a domain and set up a web site (www.hamranger.org) with some preliminary information about the whys, wherefores, and such as an introduction. There's also more about the rationale. 3. The AllStarLink nodelist lists the active RANGER nodes in RED. Ranger Red. Not bad...;) Think also of other advantages: 1. You see something (or it happens to you...). The manufacturers see the advantages of putting an 'emergency button' on the faceplate of their newest lines of radios which (or, you programmed one of the hypermemory buttons), when pressed, segue to the defined frequency, you send out the dtmf zero for 4 seconds to get picked up by the closest station that is connected to a network covering, say, Philly to NY to Allentown PA (which is the reach of the PA/NJ Asterisk Net). 2. Someone somewhere answers back. Help disptched or additional aid offered. or 1. You see something (or it happens to you...). You twist the dial to find a repeater. Can't hear anything. So, you call on 52. Same thing. Pull out the repeater handbook and a) try and figure out what county you're in, b) what machines MAY be close to you, and c) dial in the frequency, try to remember which button sequences you need to press to get to the PL settings since you computer loaded the thing and forgot how to operate the front panel apart from on, volume, and channel select... I set up a Facebook group, if anyone on the list is on FB. Search for 'RANGER Emergency Communicatons Network' to join. It's a hope that the discussion will center around not so much "whether" we should do this, but "HOW WE CAN" do this. <soapbox>That we CAN is the important thing, and might just be one more contribution we can make as amateurs to using our skills not to just collect wallpaper...but to provide additional services for our society </soapbox> Also, FWIW, my RANGER node is up, connected to my controller, and initial tests indicate that it responds just fine to the long zero (including transmitting the additional courtesy tones....) and works just fine. I'm sure there will be tweaking. But, that is the nature of running a repeater. Feel free to discuss...flames to /dev/null. -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. Sent from my MacBook Pro.

3 8

How to attach URI to exsisting Cat 300 Controller
by Brian Williams 11 Nov '11

11 Nov '11

I would like to know how to go about hooking up a URI to the link port of the CAT 300 controller. We have a remote site and the computer went down, so I want to put the Cat controller back in place and still have Allstar connection. The problem I have is the link port has to see a COR from the link Device (usually a Radio) . How do I get COR from the URI?? so that port 1 will send transmit signal to Repeater TX??

2 1

REmote Base Access Control
by Matt Roberts 11 Nov '11

11 Nov '11

I have an access question about remote bases. IF I set the node so users can't access my remote base node by phone, using the portal, does that include me as the sysop as well? Is there a way I can have an allow list for this? IF not, how can I have access to my remote base node so I and other users I authorize can control it by phone? I want to use the service provided by Allstar for outgoing autopatch calls for my server. Can I do both, or do I have to choose one? Matt Roberts n9gmr(a)me.com

2 1