August 2013 - App_rpt-users - lists.keekles.org

URI<>TKR-750 cable
by Jay Urish 06 Feb '15

06 Feb '15

Does anybody have notes on connecting tkr750 to a URI? TIA, W5GM

4 3

Echo-stink
by Johnny Keeker 05 Jan '15

05 Jan '15

I've found the 'permit=w1aw,w5yi,etc' line in the echolink.conf only allows for 29 allowed calls. Any more than 30 entries in the list prevents incoming requests on or not on the list access to the node. Short of checking for typo's, using a backslash\ to continue to the next line, or adding another 'permit= line' hasn't proved any results. ???

6 6

Registration issues
by Randy Ballard 07 Dec '13

07 Dec '13

My nodes 27365 and 27751 both on same server is showing on the status page but not showing in the rpt_extnodes on other nodes im using standard port 4569. we have been seeing this with several nodes in our group over past month or so of coarse if we define in the rpt file we can connect but would be nice if it was registering. sometimes it may show up in a few hours or a day generally a reboot and its gone again Thanks for any help in advance 73 Randy KB3HJC

5 9

Radio Console
by John Locke 20 Nov '13

20 Nov '13

I'm trying to develop a TAXI radio dispatch application. Something like this: http://www.motorolasolutions.com/US-EN/Business+Product+and+Services/Dispat… I have 3 radios (with different private frecuencies) connected to the asterisk with 3 URI interfaces. The basic features of app_rpt and iaxrpt are working OK. Now, the problems... 1) Sometimes i need to talk to 2 or 3 of the radio channels at the same time. With the iaxrpt I can select and talk to only one radio, only one active call. 2) Also, i need to listen to the audio of the 3 calls (base radios), not only the selected call. Sadly, i can't open iaxrpt multiple instances in the same PC... 3) Is there any way i can detect wich taxi is talking to the radio? I'm a programmer, but I'm a newbie in the radio field. It would be great if any of you can sell me some consulting hours to accomplish this project. Thanks in advance John

7 9

Compile Errors
by Robert Garcia 28 Sep '13

28 Sep '13

Guys, I am working on compiling app_rpt for another platform using the sources from svn and following the makefile. It looks like I am going to need some help as I am already stuck at configuring zaptel. lol gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/home/tc/zaptel/menuselect' make[1]: Leaving directory `/home/tc/zaptel/menuselect' *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 I then nuked the menuselect.makeopts per the error and tried again, I get a little further before receiving this error. make -C /lib/modules/3.0.21-tinycore/build ARCH=i386 SUBDIRS=/usr/src/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="zaptel.o ztdummy.o ztdynamic.o zttranscode.o " modules make[2]: Entering directory `/usr/local/src/linux-headers-3.0.21-tinycore' CC [M] /usr/src/zaptel/kernel/zaptel-base.o In file included from /usr/src/zaptel/kernel/zaptel-base.c:37:0: /usr/src/zaptel/kernel/zconfig.h:26:28: fatal error: linux/autoconf.h: No such file or directory compilation terminated. make[3]: *** [/usr/src/zaptel/kernel/zaptel-base.o] Error 1 make[2]: *** [_module_/usr/src/zaptel/kernel] Error 2 make[2]: Leaving directory `/usr/local/src/linux-headers-3.0.21-tinycore' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/zaptel' make: *** [all] Error 2 make: Leaving directory `/usr/src/zaptel' Oddly, the linux/autoconf.h file is there, so I'm not sure what path is the base. I "fixed" that by providing an absolute path to the autoconf.h file. Then I tried again and received this. make -C /lib/modules/3.0.21-tinycore/build ARCH=i386 SUBDIRS=/usr/src/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="zaptel.o ztdummy.o ztdynamic.o zttranscode.o " modules make[2]: Entering directory `/usr/local/src/linux-headers-3.0.21-tinycore' CC [M] /usr/src/zaptel/kernel/zaptel-base.o /usr/src/zaptel/kernel/zaptel-base.c: In function 'zt_rbs_sethook': /usr/src/zaptel/kernel/zaptel-base.c:2160:2: warning: suggest parentheses around operand of '!' or change '&' to '&&' or '!' to '~' [-Wparentheses] /usr/src/zaptel/kernel/zaptel-base.c: At top level: /usr/src/zaptel/kernel/zaptel-base.c:7650:2: error: unknown field 'ioctl' specified in initializer /usr/src/zaptel/kernel/zaptel-base.c:7650:2: warning: initialization from incompatible pointer type [enabled by default] /usr/src/zaptel/kernel/zaptel-base.c:7650:2: warning: (near initialization for 'zt_fops.fsync') [enabled by default] make[3]: *** [/usr/src/zaptel/kernel/zaptel-base.o] Error 1 make[2]: *** [_module_/usr/src/zaptel/kernel] Error 2 make[2]: Leaving directory `/usr/local/src/linux-headers-3.0.21-tinycore' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/zaptel' make: *** [all] Error 2 make: Leaving directory `/usr/src/zaptel' Any ideas on how I can get past this? Robert N5QM

3 7

Re: [App_rpt-users] RXONDELAY not working?
by tom 02 Sep '13

02 Sep '13

The chan_simpleusb.c code clearly has the rxondelay parameter. However, I tested it on a couple of half-duplex nodes and didn't see any effect. A bug? Tom / K5TRA

5 6

Allstar on different distros
by Tony KT9AC 01 Sep '13

01 Sep '13

OK, I'm going to ask if there ongoing efforts to package or provide install schemes for different hardware? I have had a node running for years on an old P4 just fine. For a low-power, fanless box I've gravitated toward the HP Thin clients, which really aren't that bad. 1.0Ghz AMD Geode, 512MB ram and an upgrade to a 44-pin 8GB Compact Flash. I have a need to build and remotely deploy three of these and would like a common install to manage. I do the standard noatime and tmpfs changes to keep the flash quiet and happy. ACID won't install on Thin Clients; XIPAR will install but takes about 3-4 hours and doesn't do MDC1200 or record traffic that I need (acid archives). I can install Debian 7.1 in about 20 minutes and it absolutely flies. Asterisk 1.8 and the current ACID SVN all compile under Debian but I can't get it to work with the URI interface. Dmesg and lspci show the URI but Allstar using the "radio tune" shows the card as "-1". I have a whole weekend in this latest build attempt. It would seem that out in the real world you can install Asterisk on anything, and that is the spirit of open-source. What would be required to get app_rpt and some of the chan stuff to run on "commodity" installs (apt-get install asterisk for example)? A lot of this is over my head, but I'm willing to try. I realize that some builds were customized for a point in time, so that begs the question about modern day attempts (Debian 7.1 runs the 3.2.0-4-686-pae kernel). Thanks Kirk for your script, but I found out late last night it doesn't use the same hardware that I do. Thanks. Tony (27129/27418/27460)

3 3

Cylon Suppression
by David Osborn 01 Sep '13

01 Sep '13

I followed with interest the discussion on accessing command mode with a macro, and the innovative ideas to achieve the desired result. That was very informative and speaks to the flexibility that Jim and others built-in to AllStar (Kudos, guys). I'm looking at a similar project but I keep getting attacked by the Cylons J (http://www.youtube.com/watch?v=0ccKPSVQcFk ) Our hub node (2483) hosts the EchoLink gateway. It has no RF hardware connected to it (then it wouldn't be a hub!). If a user on one of our other nodes wants to make an EchoLink connection, he has to go into command mode to access the hub first, then (after the Cylons have had their say), they enter the command to make the EchoLink connection, and so-on. That works well, but it's a little long-winded. What I would like to do is create a "Speed Dial" for a selected list of EchoLink nodes, and Macros appear to be ideal for this. The idea is that the Macro would accept a 3-digit suffix to connect, and a different 3-digit suffix to disconnect, like this: [functions] 6 = macro [macro] 101 = *42483*33338712# ;Connect echolink 102= ...Next connect macro 201= *42483*13338712# ;Disconnect echolink 202=...Next Disconnect macro This means that, keying *6101 will connect to the first EchoLink node (GD4HOZ, as it happens!), and keying *6201 will disconnect it. It works, except... Because there's no gap in the macro execution, the Cylons stick their galactic oars in ("By Your Command") and it actually comes out of the remote EchoLink node - which would come as a shock to the node owner. What I'm looking for is an approach that will ideally circumvent the Cylon message (even though I do kinda like it) and just get-on with the job of connecting. Perhaps a script, as Brian suggested, would do the job, by adding a delay or two, but that would still give the command message to the local user - which may not be a bad thing. Has anybody else done any EchoLink "Speed Dial" trickery? David

3 3

Re: [App_rpt-users] Webcam on AllStar?
by Geoff Edmonson 31 Aug '13

31 Aug '13

For that matter, why not apt-get gnome-base or which ever GUI you're comfy with?

1 0

Re: [App_rpt-users] Webcam on AllStar?
by Geoff Edmonson 31 Aug '13

31 Aug '13

Can you find the camera in /dev more so, see where its mounted? Without the GUI it'll be hard to tell where its pointed. Seems that you'd have to have a GUI running and access it via remote. On the other hand, why Not run the GUI on a cCentOS install and run it remote, too? As long as you had enuff ram, cpu speed and drive space. Bob Roszkowski <bob(a)w5evh.org> wrote: >_______________________________________________ >App_rpt-users mailing list >App_rpt-users(a)ohnosec.org >http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0