March 2011 - App_rpt-users - lists.keekles.org

Order of startup in rpt.conf
by Bryan D. Boyle 29 Mar '11

29 Mar '11

I'm running a box that's hosting 4 nodes...one as a hub so that I can experiment (in my down time...after my Real Job) to "flex the muscles" of the software (and it allows me to release from the normal hub I connect to for normal traffic so as to not tie up the other machines with announce connect and disconnect telemetry) with node-to-node comms and the like. However, the first node that I registered is what I placed the first (of a planned 3 bands worth) repeater hardware on, and...have added other nodes as time went on. I'd like to leave the original registration in place, since downline external systems in our net up here have entries that reference the original number. Keeps the book keeping and churn to a minimum. What I'm running into is that the node that I've configured as my hub is down the list in rpt.conf (it's the third node stanza), so, in trying to bring up my other nodes (2 are lower numbers and before the hub, one after), I note that they don't connect as I would like the end state "to be": my hub connected to the other hub, with all my leaf nodes connecting to my own hub. So...question...should I re-arrange my rpt.conf so that the hub is the first that is read on boot or restart, establish the *953 persistent connection to the other hub and /then/ connect my leaf nodes? Right now, I'm doing it manually when I get a chance via either iaxrpt into my nodes from my desktop or over the web transciever. Or, is it a question of the iax registration sequence in iax.conf, or ??? Am I missing something here? Thx for any insight...or apologies if this has been chewed upon in gory detail sometime in the murky (for me) past... (I also have some questions re the custom/rpt.conf capability, but I'll save them for later....) tnx es 73 -- Bryan WB0YLE Allstar 27294 Echolink WB0YLE-R 224.54- PL 141.3 www.wb0yle.com Morrisville PA

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 25, Issue 37
by Steve Zingman 28 Mar '11

28 Mar '11

> Message: 3 > Date: Sun, 27 Mar 2011 15:23:31 -0700 > From: Stephen Rodgers<hwstar(a)rodgers.sdcoxmail.com> > Subject: [App_rpt-users] SVN checkout over HTTP > > Read-only SVN checkout over HTTP is now supported. > The checkout URL's are as follows-- > Asterisk Sources > http://svn.ohnosec.org/svn/projects/allstar/astsrc-1.4.23-pre/trunk > Limey Linux > http://svn.ohnosec.org/svn/projects/allstar/limey-linux/trunk/ > ACID > http://svn.ohnosec.org/svn/projects/allstar/acid/trunk/ > Example use: > svn co http://svn.ohnosec.org/svn/projects/allstar/astsrc-1.4.23-pre/trunk > Commits-- > This repository is read only. Commits can only be done by Jim and I. > Additionally: > 1. The new viewvc url is now http://svn.ohnosec.org/viewvc and the app-rpt-svn.ohnosec.org/viewvc url will be deleted soon. > 2. All read-only svn+ssh accounts assigned on a case-by-case basis on ohnosec.org will be deleted soon. > Steve > WA6ZFT THANK YOU !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

1 0

Re: [App_rpt-users] SVN checkout over HTTP
by Stephen Rodgers 28 Mar '11

28 Mar '11

On 03/27/2011 04:53 PM, Tim Sawyer wrote: > Limey Linux dosen't have svn on it. Can you give us the wget version, and/or maybe update Drupal? > -- > Tim > :wq > > On Mar 27, 2011, at 3:23 PM, Stephen Rodgers wrote: > >> Read-only SVN checkout over HTTP is now supported. >> >> The checkout URL's are as follows-- >> >> Asterisk Sources >> >> http://svn.ohnosec.org/svn/projects/allstar/astsrc-1.4.23-pre/trunk >> >> Limey Linux >> >> http://svn.ohnosec.org/svn/projects/allstar/limey-linux/trunk/ >> >> ACID >> >> http://svn.ohnosec.org/svn/projects/allstar/acid/trunk/ >> >> Example use: >> >> svn co http://svn.ohnosec.org/svn/projects/allstar/astsrc-1.4.23-pre/trunk >> >> >> Commits-- >> >> This repository is read only. Commits can only be done by Jim and I. >> >> >> Additionally: >> >> 1. The new viewvc url is now http://svn.ohnosec.org/viewvc and the app-rpt-svn.ohnosec.org/viewvc url will be deleted soon. >> >> 2. All read-only svn+ssh accounts assigned on a case-by-case basis on ohnosec.org will be deleted soon. >> >> >> Steve >> WA6ZFT >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > For limey, if you want the latest svn you can use the tarball feature of viewvc to fetch the latest code. if you navigate to /projects/allstar/astsrc-1.4.23-pre/trunk with viewvc, and look at the bottom of the page, you'll see a link named "Download GNU tarball". Save that link location and use it for your wget. Yhe x.allstarlink.org links on http://ohnosec.org/drupal/node/74 and http://ohnosec.org/drupal/node/29 will start working once Jim changes these redirects to use svn.allstarlink.org instead of app-rpt-svn.allstarlink.org Steve WA6ZFT

2 1

Re: [App_rpt-users] connected to stations
by Ryan Collier 27 Mar '11

27 Mar '11

Neal, I want remote telemetry off. 2135 is killing me from all the connects and disconnects. Along with allthe other ones. Ryan

2 1

SVN checkout over HTTP
by Stephen Rodgers 27 Mar '11

27 Mar '11

Read-only SVN checkout over HTTP is now supported. The checkout URL's are as follows-- Asterisk Sources http://svn.ohnosec.org/svn/projects/allstar/astsrc-1.4.23-pre/trunk Limey Linux http://svn.ohnosec.org/svn/projects/allstar/limey-linux/trunk/ ACID http://svn.ohnosec.org/svn/projects/allstar/acid/trunk/ Example use: svn co http://svn.ohnosec.org/svn/projects/allstar/astsrc-1.4.23-pre/trunk Commits-- This repository is read only. Commits can only be done by Jim and I. Additionally: 1. The new viewvc url is now http://svn.ohnosec.org/viewvc and the app-rpt-svn.ohnosec.org/viewvc url will be deleted soon. 2. All read-only svn+ssh accounts assigned on a case-by-case basis on ohnosec.org will be deleted soon. Steve WA6ZFT

1 0

Event Management Subsystem
by K&R Yoksh 27 Mar '11

27 Mar '11

Hello all, I'd like to learn more about the Event Management Subsystem. Specifically, I don't understand the syntax in the examples: http://ohnosec.org/drupal/node/176 I managed to get the following command to work, but I am at a complete loss to understand how this works: status,2 = c|f|RPT_NUMLINKS The above line will cause your node to speak "Good evening/morning/afternoon, the time is......" after the last node connected to you is disconnected. I understand the first part of the line (the command to execute) but I have no idea what the syntax for the second part is. I'd like to have the opposite of the command above. That is, whenever my node connects to ANY other node, it should issue a DTMF. I discovered that using connpgm and discpgm for my fan control works so long as I initiate the connections. If anyone connects to ME, the fan is not turned on. I'm hoping that using the Event Management Subsystem will solve this problem. Thanks. 73 Kyle K0KN

1 0

New Releases
by Jim Duuuude 27 Mar '11

27 Mar '11

There is a new release available of all the Distros for app_rpt/Allstar, ACID, Limey Linux (both platforms) and Pickle which reflect the current SVN state as of yesterday (3/26/2011). If you already have an ACID Distro CD, you do not need to download a new one, as the OS load is the same for all of our releases (it just downloads different files once Centos gets installed). JIM WB6NIL

3 4

Issues with Remote Base - Initial connect keyup & tail blurp
by GARY BONEBRAKE 24 Mar '11

24 Mar '11

Setup - UHF repeater IC-706 remote base 3 GHz P4 PC, 1G mem ACID CentOS install DMK URIs app_rpt version 0.273 Two issues with remote base operation that are not acceptable. 1. When initially connect RB node - keys up RB for 1-2 seconds (occasionally with loud raspy "braaaaap"). Occurs with *3nnnn and *2nnnn. 2. Randomly distorts last spoken word on RB and adds 0.5 - 1.5 second "braaaaap". Any suggestions on cause/remedy? Gary W5BI

2 1

Re: [App_rpt-users] connected to stations
by Neal Garbenis 24 Mar '11

24 Mar '11

Ryan, What telemetry do you want on you end I have mine turned of all the time. When I want to check my status I made a macro to turn it on, play status, then turn it back off 90=cop,33 turn on 91=cop,34 turn off [macro27629] 1=*90,*70,*91 So no the *51 will play my status This works for me but then again I don't know what you want. On another note what do you know about the link box I want to make a exp ref for IRLP to crosslink all systems legally in irlp standards. I will catch up with you soon on the radio. Neal NG8Y

1 0

IAX registration problems
by Stephen - K1LNX 23 Mar '11

23 Mar '11

Ok... where am I going wrong? Running ACID, self managed server (not portal managed) and I can not get Asterisk to register to the registration server correctly. I am attempting to use port 4570 and set bindport=4570 in iax.conf. If I do an iax2 show registry: allstar*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 67.215.233.178:4569 N 2335 70.90.228.195:4569 60 Registered It show registered, but not on the correct port ??? I also show the entry in /var/lib/asterisk/rpt_extnodes to be incorrect, it shows the IP I was previously using: [root@allstar asterisk]# cat /var/lib/asterisk/rpt_extnodes | grep 2335 2335=radio@70.90.228.196:4570/2335,70.90.228.196 Anyone have any ideas? I've been off the air for a while due to hardware issues, and these configs were working previously, but it's probably been a year or more..... tnx and 73, Stephen -- **************************************** Stephen Brown - ARS K1LNX Johnson City, TN EM86 http://www.k1lnx.net Allstar Link: 2335 IRLP: 4829 PSTN: 423-665-9367 SIP: k1lnx(a)k1lnx.net ****************************************

4 12