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

Xipar and echo link
by Bradley Haney 19 Jul '14

19 Jul '14

Hello all. I have xipar and eeverything working great except echollink. I switch from acid. And had it working perfect on it. But now on xipar. When a echolink client is connected and when they transmit. Xipars courtesy tone keeps beeping and they chop. I have messed with several different settings for the echolink tx and ex settings but no good. Allstarlink to Allstarlink connections sound sound fine. Any thoughts?

1 0

webstransceiver acces
by ea8ee 19 Jul '14

19 Jul '14

I fellows all I could always access my node from the any browser through the webtransceiver but since some days I change my ip range on your router noted that the java works well but my name station appears and neither hear sound on the node however the node echolink works well I have noticed that this happens in many nodes in the list of webstransceiver, which may be the cause? not a problem that this open port on the router? according to my router is open

1 0

Re: [App_rpt-users] Dual PL Setup
by mike＠midnighteng.com 18 Jul '14

18 Jul '14

1 0

XIPAR and 4xxxx node numbers
by Chuck Kraly 18 Jul '14

18 Jul '14

Has anyone noticed if their version of XIPAR can connect to 4xxxx nodes without getting the "no irpl" channel notice? I thought it was working, and we created a new build and notice the message on trying to connect. Also I went and tried it on all of our nodes and no joy. XIPAR is at rev 275 (according to xiapl xipar-update) and Asterisk is at 1.4.44 -- Chuck K0XM Backyard Repeater Group k0xm(a)byrg.net

1 0

Dual PL Setup
by Jake Litwin 18 Jul '14

18 Jul '14

I'm looking for a way to be able to set up dual pl's so that one pl will just activate the local node repeater. If users wanted to talk to another node that is already connected to the local node, they would have to use a different pl. The idea here is that we just want to have the other node connected all of the time but don't necessarily want all of our local traffic passed on to it. We want to do this so we don't have to keep disconnecting and reconnecting the other node. The repeater is a Motorola GR1225 which already handles PL. XIPAR is running with a URI hooked up to the repeater. Any ideas on how this would be accomplished?

1 0

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

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

18 Jul '14

I'm using this as a script. In my users home directory is a directory called bin (/home/thor/bin) where I keep scripts. Each is made executable (chmod +x script_name). This one I run after any yum update. Call it what you like, I call it update_acid. This isn't entirely my creation, like all things open source, I borrowed from others, especially K0KN. Anyway, by making this an executable script you turn this into an almost painless process. #!/bin/bash #This first part downloads the latest ACID and unpacks it cd /usr/src rm -rf astsrc wget http://allstarlink.org/svn-trunk.tar.gz -O- | tar xzv #This next bit removes the radio_relax module from the code #But I don't remember why I do that mv trunk astsrc cd astsrc sed -i 's/MENUSELECT_CFLAGS=RADIO_RELAX LOADABLE_MODULES/MENUSELECT_CFLAGS=LOADABLE_MODULES/g' /usr/src/astsrc/asterisk/menuselect.makeopts #Compiles the code make upgrade-acid #This part whacks the zaptel drivers into submission. #Without it the newly upgraded ACID will not run cd /usr/src/astsrc/zaptel ./configure make make install make config cd modprobe zaptel service zaptel start service asterisk restart On 07/17/2014 02:55 AM, app_rpt-users-request(a)ohnosec.org wrote: > Date: Wed, 16 Jul 2014 22:58:52 -0700 > From: Tim Sawyer <tim.sawyer(a)mac.com> > To: David Osborn <david.osborn(a)manx.net> > Cc: app_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] App_rpt-users] Cent OS Updating? > Message-ID: <60568681-1080-4CFF-A99B-03BB9E276809(a)mac.com> > Content-Type: text/plain; charset="windows-1252" > > Good idea. I?ll make myself a note to do that. > > On Jul 16, 2014, at 10:55 PM, David Osborn <david.osborn(a)manx.net> wrote: > >> Any chance of adding this nugget to the Drupal (or even allstarlink.org) site for future reference? >> >> David Osborn >> GD4HOZ >> >> >> From: Randy Neals [mailto:randy@neals.ca] >> Sent: 16 July 2014 18:27 >> To: Thor Wiegman >> Cc: app_rpt-users(a)ohnosec.org >> Subject: Re: [App_rpt-users] App_rpt-users] Cent OS Updating? >> >> >> Wanted to say "Thank You" for this set of instructions. >> >> Just used it to recover my node after a yum update left it hung up and not working. Thanks! >> >> -Randy >> >> >> >> >> On Sun, Apr 13, 2014 at 10:10 AM, Thor Wiegman <n7jct(a)aplaceonthe.net> wrote: >> 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) >> >>

2 1

Telefon Portal doesn`t work
by torben＠klimt-online.com 18 Jul '14

18 Jul '14

hi all, i set up an new allstarlink node. everythink works fine but the Telefon Portal doesn`t work. i dial the telefonnumber, dial the nodenr dial 1 dial security pin and then nothing for round about 30sec after this i get a busy Signal :-( any ideas ? greetings Torben Klimt Eicherstrasse 58 85123 Karlskron-Grillheim Telefon: 08453-34 45 040 Fax: 08453 - 4085296 Mobil: 0151-178 74499 torben(a)klimt-online.com<mailto:torben@klimt-online.com>

1 0

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

RF repeater linking using Allstar
by Loren Tedford 17 Jul '14

17 Jul '14

I have seen many posts here about linking repeater via rf into all star I would like to do the same thing here where I live there is repeaters close by that I would like to link them into my repeater however it seems that my problem has come up with ensuring proper Id by the link radio. I need the radio to only ID when it transmit I have found so far that Duplex=0 does not work for this set up it stops all Id's all together I really don't need any telemetry data of other links connecting up to the repeater because this will add extra transmit time etc..Here is a sample of my rpt.conf file If some one would show me where i messed up that would be great remember this is a link not a repeater and the link is connected to a USB uri that is connected up to a VHF Motorola Maxtrac the radio has been programmed to specific frequencies I would like to use and pl tones applied.. So the goal here is to get the node to key up to the repeater give an id when there is traffic coming through the node not when traffic is received from the repeater.. So example problem with Duplex=1 repeater keys up with tones and ids but every 10 minutes the repeaters get into a repeater id war repeater ids then node ids which resets repeater timer and makes the repeater id then turns around and resets node timer and causes it to id... So... where did i screw up with the config file.. ; Radio Repeater configuration file (for use with app_rpt) ; ; ; Your Repeater ; [27103] ; Change this to your assigned node number rxchannel=Radio/usb27103 duplex=0 erxgain=-3 etxgain=3 ;controlstates=controlstates scheduler=schedule27103 morse=morse27103 macro=macro27103 functions=functions27103 phone_functions=functions27103 link_functions=functions27103 telemetry=telemetry wait_times=wait-times context = radio callerid = "Repeater" <0000000000> idrecording = |iKC9ZHV/L accountcode=RADIO hangtime=50 althangtime=100 totime=150000 idtime=540000 politeid=3000 idtalkover=|iKC9ZHV/L unlinkedct=ct2 remotect=ct3 linkunkeyct=ct8 ;nolocallinkct=0 ;eannmode=1 ;connpgm=yourconnectprogram ;discpgm=yourdisconnectprogram ;lnkactenable=0 ;lnkacttime=1800 ;lnkactmacro=*52 ;lnkacttimerwarn=30seconds ;remote_inact_timeout=1800 ;remote_timeout=3600 nounkeyct=1 ;holdofftelem=0 beaconing=0 telemdefault=2 ; ; *** Status Reporting *** ; ; Uncomment the either group following two statpost lines to report the status of your node to stats.allstarlink.org ; depending on whether you are running ACID or Limey Linux. ; ** For ACID *** statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ** For Limey Linux ** ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ; Morse code parameters, these are common to all repeaters. ; [morse27103] speed=18 frequency=800 amplitude=4096 idfrequency=750 idamplitude=1024 [schedule27103] ;dtmf_function = m h dom mon dow ; ala cron, star is implied [functions27103] 1=ilink,1 2=ilink,2 3=ilink,3 4=ilink,4 5=macro,1 70=ilink,5 71=ilink,6 72=ilink,7 73=ilink,15 74=ilink,16 75=ilink,8 80=status,1 81=status,2 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up 0=autopatchdn ; Autopatch down ;989=cop,4 980=status,3 99=cop,6 ; Place command macros here [macro27103] [telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ct2=|t(660,880,150,2048) ct3=|t(440,0,150,4096) ct4=|t(550,0,150,2048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ct8=|t(700,1100,150,2048) remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); remotemon=|t(1209,0,50,2048) cmdmode=|t(900,903,200,2048) functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) patchup=rpt/callproceeding patchdown=rpt/callterminated ; ; This section allows wait times for telemetry events to be adjusted ; A section for wait times can be defined for every repeater ; [wait-times] telemwait=2000 idwait=500 unkeywait=2000 calltermwait=2000 ; ; This is where you define your nodes which cam be connected to. ; [nodes] ; Note, if you are using automatic update for allstar link nodes, ; no allstar link nodes should be defined here. Only place a definition ; for your locak nodes, and private (off of allstar link) nodes here. 27103 = radio(a)127.0.0.1/27103,NONE ; Memories for remote bases [memory] ;00 = 146.580,100.0,m ;01 = 147.030,103.5,m+t ;02 = 147.240,103.5,m+t ;03 = 147.765,79.7,m-t ;04 = 146.460,100.0,m ;05 = 146.550,100.0,m #includeifexists custom/rpt.conf Loren Tedford (KC9ZHV) Email: lorentedford(a)gmail.com Email: loren(a)lorentedford.com http://www.lorentedford.com

1 0