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

Custom NodeNames
by W0OTM 18 Aug '15

18 Aug '15

I have written a shell script to create custom node names to replace the announcing of nodes by their node number to the "callsign" configured for each node on the system. Its 2 parts. First uses a php script to download all the AllStar Node data and saves as txt file called nodenames. I save mine as 'getnodes.php'. The code can be found here: http://pastebin.com/cSCuAZnS After this runs, I run the second script: I save mine as 'nodenames.sh'. The code can be found here: http://pastebin.com/AWtPpYjY This script looks up the node number and finds the callsign, it then creates a .ulaw file using the letters and digits found in the AllStar systems. No TTS! It saves all the ####.ulaw files in /var/lib/asterisk/sounds/rpt/nodenames. Now when a node connects or disconnects, its announces a callsign instead of a node number. -- Marshall Dias .-- ----- --- - -- Ottumwa, IA EN31ta 4SQRP #310

3 5

Re: [App_rpt-users] Custom NodeNames
by Doug Crompton 18 Aug '15

18 Aug '15

Marshall, I certainly was not criticizing your work, just making a few suggestions. If you are using the RPi2 (or BBB) then the astdb.txt file is located in /var/log/asterisk updated by a cron entry daily. You could simply read it from there. You do not have to create another copy of astdb.php. Also I was looking for your comments on the ffmpeg. Why is that needed? Are the file types different that you are combining? You could just cat them together if they are all one type and just play them. gsm files will play as well as ulaw. You could also use sox to adjust the volume. There are examples of that in the scripts on the RPi2. I think this would be a worthwhile script to maybe include in the RPi2/BBB image. It just needs a little refinement. 73 Doug WA3DSP http://www.crompton.com/hamradio From: w0otm(a)w0otm.com Subject: Re: [App_rpt-users] Custom NodeNames Date: Mon, 17 Aug 2015 22:29:34 -0500 To: doug(a)crompton.com Everyone has an opinion, you are certainly entitled to yours. In the AllStar raspberry pi image I downloaded, it didn't contain a solution for what I was trying to solve. What I made works well for me and I'm happy with it. Maybe others will see value in it as well. Best regardsmd Sent from my iPhone On Aug 17, 2015, at 8:03 PM, Doug Crompton <doug(a)crompton.com> wrote: Marshall, Looks interesting. On systems that have either lsnodes or allmon the astdb.txt file should already exist and is updated daily. It might be better to use that file for the second script if it exists. That would avoid unnecessary reads from the database and having yet another astdb.php file on the system. The astdb.php file has changed recently also and has better error detection, retry support, and it sorts. Just a suggestion. Also I have a simple combine script I include in the BBB and RPi2 release that simply combines the gsm files with like this cat file1.gsm file2.gsm file3.gsm > node.gsm As long as all files type are the same there is no need to do any conversion. So maybe ffmpeg is not needed? 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Mon, 17 Aug 2015 16:08:06 -0500 From: w0otm(a)w0otm.com To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Custom NodeNames I have written a shell script to create custom node names to replace the announcing of nodes by their node number to the "callsign" configured for each node on the system. Its 2 parts. First uses a php script to download all the AllStar Node data and saves as txt file called nodenames. I save mine as 'getnodes.php'. The code can be found here: http://pastebin.com/cSCuAZnS After this runs, I run the second script: I save mine as 'nodenames.sh'. The code can be found here: http://pastebin.com/AWtPpYjY This script looks up the node number and finds the callsign, it then creates a .ulaw file using the letters and digits found in the AllStar systems. No TTS! It saves all the ####.ulaw files in /var/lib/asterisk/sounds/rpt/nodenames. Now when a node connects or disconnects, its announces a callsign instead of a node number. -- Marshall Dias .-- ----- --- - -- Ottumwa, IA EN31ta 4SQRP #310 _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

2 1

Compiling/running the AllStarLink "trunk" on, a 3.x+ Linux kernel system
by Steve Zingman 17 Aug '15

17 Aug '15

Stacey, Everything you need to install AllStar Asterisk on Debian is at: github.com/N4IRS/AllStar Works on ARM X86 and X64. Patches for DAHDI, SSL etc. Including scripts to do it all for you. 73, Steve N4IRS On 8/17/2015 12:00 PM, app_rpt-users-request(a)ohnosec.org wrote: > Message: 5 > Date: Mon, 17 Aug 2015 08:50:47 -0700 > From: Stacy<kg7qin(a)arrl.net> > To:app_rpt-users@ohnosec.org > Subject: [App_rpt-users] Compiling/running the AllStarLink "trunk" on > a 3.x+ Linux kernel system > Message-ID:<55D202D7.80101(a)arrl.net> > Content-Type: text/plain; charset=utf-8 > > All- > FYI. I wasn't able to find any information on how to do this, so I took > Friday night/Saturday to hack on the files from the "trunk" branch of > the AllStarLink repository, getting asterisk to compile and successfully > run under a 3.x+ kernel. > > More info here: > https://forums.qrz.com/index.php?threads/allstarlink-on-a-3-x-linux-kernel.… > > Github repository with files I used to do this: > https://github.com/KG7QIN/AllStarLink > > Note that I also provide a patch for the DAHDI 2.10.2+2.10.2 complete > driver for it to work with AllStarLink. > > After setting up my Raspberry PI B+ as an AllStar node, I wanted to run > this on other system for experimentation (I used VK2ACP's Github > repository for this, but I had to port the patch to the newer DAHDI > driver since the one he had wouldn't compile on the version of ArchLinux > I was running due to the IOCTL calls used.). > > I didn't like that I couldn't compile this on a Debian distro running a > 3.x+ kernel using the files provided from the repository. After a bit > of searching, it seems that this was a common problem with not many > people trying to do it (or for those that have done it, having the > information readily accessible on the web -- I was able to mostly find > the images that people have from their work on this). > > I had tried to port the zaptel driver over to the 3.x+ kernel, but with > the changes to the IOCTL calls between kernels, as well as some other > changes, it didn't work. (I even unsuccessfully tried to post a $50 > bounty for someone to do the conversion on bountysource.com, but it went > unclaimed and I ended up killing it). > > After letting this sit for a few months, I decided to try another shot > at it. Since I had some free time on my hands, I decided to try my hand > at "solving" this problem and getting the software to compile and run on > my laptop (running Ubuntu 15.04). > > I installed the necessary build dependencies for asterisk from the > Ubuntu repositories which let me compile most of AllStarLink asterisk, > and proceeded to narrow down why res_crypto wouldn't compile (I was able > to get the system to partially work without this, but it wouldn't accept > calls from the AllStarLink telephone portal due to not being able to > verify the public key used). > > After playing with OpenSSL (I thought the problem lied in how the Ubuntu > folks compiled it), and trying to force res_crypto to compile (causing > asterisk to crash when loaded), I found it came down to the test for > OpenSSL that is used in the configuration script. I did some digging > and found that configure.ac was the main source for this, and I was able > to find the offending lines that created the test condition that would > fail and make the build scripts not compile in res_crypto. > > Since the autobuild scripts seems to be some black magic that I wasn't > steeped in, I decided to see how a newer version of Asterisk handled the > test for OpenSSL and downloaded Asterisk 1.8. Looking at its > configure.ac, I saw the lines that they used for the test and copied > them over, replacing the old ssl2_connect test that was failing. After > running bootstrap.sh to refresh the config scripts and commending out a > check for SED (that makes configure bomb out), I ran a make menuconfig > and saw that res_crypto was no longer X'd out. A quick compile, install > and configuration of the node shows that it works. > > I really like the concept behind the AllStarLink network and think Jim > Dixon (et all) have done a great job with it. Having been exposed to > asterisk through an article in Usenix back in 2005/2006 (and using it > ever since for my own phone system), I never realized what the > pciradio/etc stuff was really for. It wasn't until I got my ham radio > license in January that I really started to learn what the "other stuff" > in asterisk was for. > > Anyways, I'm sharing this with the hope that someone else may use it. > It works for me, but it may not work for you. > > 73s, > Stacy (KG7QIN) -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

3 2

Compiling/running the AllStarLink "trunk" on a 3.x+ Linux kernel system
by Stacy 17 Aug '15

17 Aug '15

All- FYI. I wasn't able to find any information on how to do this, so I took Friday night/Saturday to hack on the files from the "trunk" branch of the AllStarLink repository, getting asterisk to compile and successfully run under a 3.x+ kernel. More info here: https://forums.qrz.com/index.php?threads/allstarlink-on-a-3-x-linux-kernel.… Github repository with files I used to do this: https://github.com/KG7QIN/AllStarLink Note that I also provide a patch for the DAHDI 2.10.2+2.10.2 complete driver for it to work with AllStarLink. After setting up my Raspberry PI B+ as an AllStar node, I wanted to run this on other system for experimentation (I used VK2ACP's Github repository for this, but I had to port the patch to the newer DAHDI driver since the one he had wouldn't compile on the version of ArchLinux I was running due to the IOCTL calls used.). I didn't like that I couldn't compile this on a Debian distro running a 3.x+ kernel using the files provided from the repository. After a bit of searching, it seems that this was a common problem with not many people trying to do it (or for those that have done it, having the information readily accessible on the web -- I was able to mostly find the images that people have from their work on this). I had tried to port the zaptel driver over to the 3.x+ kernel, but with the changes to the IOCTL calls between kernels, as well as some other changes, it didn't work. (I even unsuccessfully tried to post a $50 bounty for someone to do the conversion on bountysource.com, but it went unclaimed and I ended up killing it). After letting this sit for a few months, I decided to try another shot at it. Since I had some free time on my hands, I decided to try my hand at "solving" this problem and getting the software to compile and run on my laptop (running Ubuntu 15.04). I installed the necessary build dependencies for asterisk from the Ubuntu repositories which let me compile most of AllStarLink asterisk, and proceeded to narrow down why res_crypto wouldn't compile (I was able to get the system to partially work without this, but it wouldn't accept calls from the AllStarLink telephone portal due to not being able to verify the public key used). After playing with OpenSSL (I thought the problem lied in how the Ubuntu folks compiled it), and trying to force res_crypto to compile (causing asterisk to crash when loaded), I found it came down to the test for OpenSSL that is used in the configuration script. I did some digging and found that configure.ac was the main source for this, and I was able to find the offending lines that created the test condition that would fail and make the build scripts not compile in res_crypto. Since the autobuild scripts seems to be some black magic that I wasn't steeped in, I decided to see how a newer version of Asterisk handled the test for OpenSSL and downloaded Asterisk 1.8. Looking at its configure.ac, I saw the lines that they used for the test and copied them over, replacing the old ssl2_connect test that was failing. After running bootstrap.sh to refresh the config scripts and commending out a check for SED (that makes configure bomb out), I ran a make menuconfig and saw that res_crypto was no longer X'd out. A quick compile, install and configuration of the node shows that it works. I really like the concept behind the AllStarLink network and think Jim Dixon (et all) have done a great job with it. Having been exposed to asterisk through an article in Usenix back in 2005/2006 (and using it ever since for my own phone system), I never realized what the pciradio/etc stuff was really for. It wasn't until I got my ham radio license in January that I really started to learn what the "other stuff" in asterisk was for. Anyways, I'm sharing this with the hope that someone else may use it. It works for me, but it may not work for you. 73s, Stacy (KG7QIN)

2 2

PTT Question w/iaxRPT and HT's connected to Node
by John C. Westmoreland, P.E. 17 Aug '15

17 Aug '15

Hello All, I was wondering if any of you have seen this with iaxRPT and app_rpt - but - if I keep all settings the same - and I set invertptt=0 - iaxRPT works fine - audio through that gets copied out and HT's receive just fine - but; when I try to talk with the HT's - audio isn't received - node radio receives but the audio isn't xmitted through. Now, if I set invertptt=1 - then the HT's can xmit and iaxRPT 'hears' it - but now iaxRPT cannot xmit. Has anyone seen this issue? Hopefully just a config issue I have missed. Maybe a weak pull-up or pull-down on PTT is needed? 73's, John AJ6BC

1 0

Silencing connected node connection announcements
by kk6ecm 16 Aug '15

16 Aug '15

I've been searching, and have not discovered how to silence connection announcements from a node which I'm connected ("node xxxx disconnected from node xxxx"). A more general question. Where can I find a data dictionary for the terms in the rpt.conf telemetry stanza? thanks, Bob kk6ecm

3 2

Correct Wiring For The URIx Diagnostic Dongle
by John C. Westmoreland, P.E. 16 Aug '15

16 Aug '15

Hello All, Here is the wiring instructions from the FAQ: Pin 1 to Pin 7 Pin 2 to Pin 3 Pin 4 to Pin 8 *Pin 23 to Pin 24* 10K Resistor between Pins 21 and 22 10K Resistor between Pins 21 and *23* For URIx (CM119) only, also include the following connections: Pin 5 to Pin 10 Pin 6 to Pin 11 >From uridiag: Enter your selection:c Special Test Cable Pinout: 25 pin D-shell connector Pin 1 to Pin 7 Pin 2 to Pin 3 Pin 4 to Pin 8 * Pin 11 to Pin 24* 10K Resistor between Pins 21 & 22 10K Resistor between Pins 21 & 23 For URIx (CM119), also include the following: Pin 5 to Pin 10 Pin 6 to Pin* 11* Do *NOT* include these for the standard URI!! So, which one of these do I use? 73's, John AJ6BC

4 8

Re: [App_rpt-users] Pickle SVN Server
by Bob 15 Aug '15

15 Aug '15

Hi Guys There's a few of us down under in Oz that are running pickle on XM's 73 Bob VK6ZGN On 15 August 2015 19:47:01 "John C. Westmoreland, P.E." <john(a)westmorelandengineering.com> wrote: > Hello Robert, > > Well, I have heard at least one other HAM on the air around here and he said > he prefers to use the xM vs. the rest. And there's at least another HAM > that I have talked to via this list that has at least one xM on the air - so > I guess that gets us up to 3 real fast. Hi! > > I thought there'd be enough xM's out there looking for something to do; this > would be a good fit. > > So, is 3 enough to get the source on the repository? Or did it ever live > there? Assume so since the rest are there. > > I see Jim WB6NIL updated uridiag. > > 73's, > John > AJ6BC > > > On Sat, Aug 15, 2015 at 3:15 AM, Robert Newberry <N1XBM(a)amsat.org > <mailto:N1XBM@amsat.org> > wrote: > > > My guess is lack if interest. Most people are playing with the beaglebone > blacks or the rasbperry pi 2. There are people experimenting with the newer > ARM computers too. > > I haven't heard anything about pickle in over a year. You're the most I've > ever heard about it. > > N1XBM > Apparare Scientor > Paratus Communicare > Allstar Node # 27086, 41540, 41812, 42086 > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to > the bottom of the page. Enter your email address and press the "Unsubscribe > or edit options button" > You do not need a password to unsubscribe, you can do it via email > confirmation. If you have trouble unsubscribing, please send a message to > the list detailing the problem. > > >

3 3

Pickle SVN Server
by John C. Westmoreland, P.E. 15 Aug '15

15 Aug '15

Hello All, Just wondering why Pickle is absent from here: http://svn.ohnosec.org/viewvc/projects/allstar/?root=svn 73's, John AJ6BC

2 2

resending request for app info
by Reid Brandon 14 Aug '15

14 Aug '15

Not sure why this wasn't posted before so resending it:After discovering there is no pop-up window during CENT-OS installation to allow selection of a fixed IP address (it installs then looks for DHCP, which isn't there so the installation check crashes, I found I can make a Firewall perform DHCP as it also acts as a router. And I have a licensed FW available so now the person who is setting up the Firewall box asked me a few questions.Keep in mind this is way out of my field of experience! But I need a list of apps that need permission to pass thru the FW. I saw SSH in a non-std software port, SIP (session initiation protocol) What else - any Gurus out there that have btdt?TIA, Reid W6MTF

3 2