June 2014 - App_rpt-users - lists.keekles.org

Registration issues
by Thor Wiegman 30 Nov '15

30 Nov '15

Tonight I had a user tell me that one of my nodes wouldn't connect anywhere. Verified, rebooted the server, still nothing. Tried running the rc.updatenodelist script manually and it just sits there. However, after running the following command I do get an update and can now connect to other nodes. /usr/bin/wget -O /var/lib/asterisk/rpt_extnodeshttp://nodes1.allstarlink.org/cgi-bin/nodes.pl When I checked two other nodes they had the same problem and same work-around. I ran that same command for nodes2 and it works. When I run it for nodes3 it times out. Could a problem with nodes3.allstarlink.org be causing the rc.updatenodelist script to choke? And could that have been causing my nodes to not be able to connect to others?

5 5

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

Re: [App_rpt-users] additional- app_rpt_script_execution
by mike＠midnighteng.com 21 Jul '14

21 Jul '14

3 2

Re: [App_rpt-users] BeagleBone Black Allstar Official Release
by Doug Crompton 18 Jul '14

18 Jul '14

Steven, I think you are asking about hardware? BBB, sound FOB, Radio. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Wed, 25 Jun 2014 22:07:11 -0700 From: donegan(a)donegan.org Subject: Re: [App_rpt-users] BeagleBone Black Allstar Official Release To: doug(a)crompton.com What is the complete configuration required? IE BBB+? Being a computer professional (+geek+electronics geek+ham etc) I might just replace my low power mac mini sized node with an even more small and power efficient unit - and besides I like hacking on linux and asterisk :-) ____________ Steven Donegan KK6IVC SSCC/NORC Life Member, Car #86 www.sscc.us From: Doug Crompton <doug(a)crompton.com> To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> Sent: Wednesday, June 25, 2014 10:02 PM Subject: [App_rpt-users] BeagleBone Black Allstar Official Release Hello and welcome to the first public release of Allstar on the BeagleBone Black. This represents months of trial and error testing which first started with the Raspberry Pi back at the beginning of the year and was finally successful on the BBB platform. We have had several beta versions out now for over two months with many testers and we had very good reports. There is more to be done but this is a working system that will allow many to get rid of their energy consuming PC's with constantly running hard drives and have an Allstar system that fits in the palm of your hand. The web page I have created gives very detailed instructions on how to download, install, and configure your BBB for use with Allstar. The web page is: hamvoip.org There you will find a link to download the image and also to join the arm-allstar email list. Please try to address questions specific to the BBB and Allstar to the arm-allstar list and not the apt-rpt list. While the code is the current Acid release there are many differences in how things are done on the BBB and the OS we are using, Arch Linux, is much different than Centos or Debian. Please refer to the web page for detailed info on some of the differences. We also recommend that you NOT use the nodesetup routine that is offered on the standard Acid release. In many ways this is faulty and often more trouble than it is worth. For that reason we have renamed nodesteup on the image and made it non-executable. Besides what is described on the web page there is a very detailed how-to describing first time setup of the config files. We encourage you to edit the existing config files rather than wholesale copying your existing configs on top of the examples. There is a little learning involved but in the long run it is good to know how things work by configuring the files on your own. We also encourage you to make image backups once you have your system configured. This will avoid having to recreate your configuration should a failure of some kind occur. While we have not seen any problems with power failures and as far as we know not one SD card has ever failed running Allstar there is always a first time and better safe than sorry. This release does not have the backup/restore scripts that we promised but they will be available soon. Basically what they will do is copy /etc/asterisk and all directories under it in entirety into a tar file and then you would use winscp or a similar file copy program to transfer the tar file to another computer. This would allow you to make updates of the image when new code is released in the future without losing your former configuration. For now you can do this manually. See the howto on the web page for instructions on doing image and directory backups. It is not hard to do and well worth the piece of mind. Have fun and I hope you enjoy your new BBB Allstar node. There will be many more features and upgrades available in the future all of which will be announced on the arm-allstar email list. There are already plenty of experienced users on the list that can help you with any problems you might have. 73 Doug, WA3DSP _______________________________________________ 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.

4 5

Does anyone have a working circuit diagram for Baofeng/Kenwood to URIx?
by Steven Donegan 18 Jul '14

18 Jul '14

I am looking for a circuit diagram so I can fabricate a cable to connect a URIx to a Baofeng (or pair of Baofeng's) suitable for use with ACID/Allstar. Any assistance would be useful. I have not found anything on the web thus far... ____________ Steven Donegan KK6IVC SSCC/NORC Life Member, Car #86 www.sscc.us

9 8

Re: [App_rpt-users] App_rpt-users] Cent OS Updating?
by Thor Wiegman 17 Jul '14

17 Jul '14

My experience is exactly what Jim suggests, it kills the Zaptel modules. With the ACID distro what I end up doing is a complete update of the OS then I do a complete update and recompile of the SVN. Basically you: 1) Do all of your OS updates using yum. (Or, I use the tool in Webmin). 2) Update the ACID SVN using these steps: cd /usr/src rm -rf astsrc wget http://x.allstarlink.org/svn-trunk.tar.gz -O- | tar xzv mv trunk astsrc cd astsrc make upgrade-acid 3) Finally update Zaptel with these steps: cd /usr/src/astsrc/zaptel ./configure make make install make config modprobe zaptel service zaptel start service asterisk restart I have no idea if this is the "right" way to do all this. But I do know that it's working for me. YMMV. 73 Thor (Operator of N7JCT) ---------------------------------------- > > Message: 2 > Date: Sat, 12 Apr 2014 20:30:53 -0700 > From: Jim Duuuude <telesistant(a)hotmail.com> > To: Tim Sawyer <tim.sawyer(a)mac.com>, Greg <kb1ncj(a)gmail.com> > Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] Cent OS Updating? > Message-ID: <BLU180-W110437AB9DEDF02ECED3FFB1560(a)phx.gbl> > Content-Type: text/plain; charset="windows-1252" > > At my size, if I "jump" in. Im likely to break it!! > > How about a "gentle step"... > > :-) > > Yes, when Centos updates to a new kernel, the previously-compiled Zaptel modules are no > longer compatible with the running kernel and need to be re-compiled. > > Jim > > > > From: tim.sawyer(a)mac.com > Date: Sat, 12 Apr 2014 20:27:00 -0700 > To: kb1ncj(a)gmail.com > CC: app_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] Cent OS Updating? > > That?s a good question. One I?ve been meaning to look into myself. > Here?s what suspect happens: I think the issue is when you install a new kernel it breaks Zaptel. So you have to then update App_rpt with the instructions on the site. But, like I said, that?s what I suspect happens and I?ve never tried it myself. > Perhaps someone will jump in here and enlighten us. > > -- > Tim > :wq > > > On Apr 12, 2014, at 2:42 PM, Greg <kb1ncj(a)gmail.com> wrote:Is it possible to update Allstar base OS without breaking something? Will "yum update" work or is there some other option that is safer? When I checked the list of updates, asterisk wasn't one of them but haven't executed it yet. > Thanks > Greg > _______________________________________________ > 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. > > >

5 4

Odd CTCSS behavior on RTCM
by Chris Bunting 14 Jul '14

14 Jul '14

Running version 1.41 . Have 2 rtcms connected to mtr2000 , thunderbolt gps , pretty standard setup. My simulcast is working great, however I can't get ct decode to work properly. It's either in carrier mode or it doesn't work . Odd things happen when I put what I assume is the correct settings in the ct and for config on the rtcm. The rx light flashes and sometimes let's a signal thru , but my repeater sorta goes flaky like the rtcm is pulling the line down and flaking it out. The voltage pulsates on the CTCSS line and the repeater receiver light goes out when it is actually receiving a signal. Very odd . Is 1.41 the best version? Any ideas what I'm doing wrong?? I'm using the rdstat2 pin on the MTR for CTCSS decode and it reads 5 volts when receiving a valid pl . Thanks in advance N3FYI -- Sent from My iPad

4 8

"Official" "fixed" DAHDI patches
by Jim Duuuude 10 Jul '14

10 Jul '14

After much lamenting this morning, I have come up with what I feel comfortable as a "working" DAHDI patch set. This is useful if you are wanting to "roll your own" app_rpt system (perhaps on some non-(Centos 5.X 32 bit) platform). If you take any of the distros of DAHDI 2.5.1 or newer, and apply these patches, it should "work". This patch set may be obtained from: https://allstarlink.org/fixed-dahdi-patches.tar.gz or from SVN at: http://svn.ohnosec.org/viewvc/projects/allstar/astsrc-1.4.23-pre/trunk/fixe…

7 11

BeagleBone Black Allstar Official Release
by Doug Crompton 01 Jul '14

01 Jul '14

Hello and welcome to the first public release of Allstar on the BeagleBone Black. This represents months of trial and error testing which first started with the Raspberry Pi back at the beginning of the year and was finally successful on the BBB platform. We have had several beta versions out now for over two months with many testers and we had very good reports. There is more to be done but this is a working system that will allow many to get rid of their energy consuming PC's with constantly running hard drives and have an Allstar system that fits in the palm of your hand. The web page I have created gives very detailed instructions on how to download, install, and configure your BBB for use with Allstar. The web page is: hamvoip.org There you will find a link to download the image and also to join the arm-allstar email list. Please try to address questions specific to the BBB and Allstar to the arm-allstar list and not the apt-rpt list. While the code is the current Acid release there are many differences in how things are done on the BBB and the OS we are using, Arch Linux, is much different than Centos or Debian. Please refer to the web page for detailed info on some of the differences. We also recommend that you NOT use the nodesetup routine that is offered on the standard Acid release. In many ways this is faulty and often more trouble than it is worth. For that reason we have renamed nodesteup on the image and made it non-executable. Besides what is described on the web page there is a very detailed how-to describing first time setup of the config files. We encourage you to edit the existing config files rather than wholesale copying your existing configs on top of the examples. There is a little learning involved but in the long run it is good to know how things work by configuring the files on your own. We also encourage you to make image backups once you have your system configured. This will avoid having to recreate your configuration should a failure of some kind occur. While we have not seen any problems with power failures and as far as we know not one SD card has ever failed running Allstar there is always a first time and better safe than sorry. This release does not have the backup/restore scripts that we promised but they will be available soon. Basically what they will do is copy /etc/asterisk and all directories under it in entirety into a tar file and then you would use winscp or a similar file copy program to transfer the tar file to another computer. This would allow you to make updates of the image when new code is released in the future without losing your former configuration. For now you can do this manually. See the howto on the web page for instructions on doing image and directory backups. It is not hard to do and well worth the piece of mind. Have fun and I hope you enjoy your new BBB Allstar node. There will be many more features and upgrades available in the future all of which will be announced on the arm-allstar email list. There are already plenty of experienced users on the list that can help you with any problems you might have. 73 Doug, WA3DSP

13 14