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

AllStarLink News and Updates
by AllStarLink Admin Role 13 Jul '18

13 Jul '18

We here at AllStarLink are not always best at publishing what the organization is up to. There's lots of great things happening, some more visible than others. Below is a bit of what we've been up to since the AllStar project was turned over to us. AllStarLink has assembled team of around a dozen volunteer admin/support experts to troubleshoot any possible AllStar infrastructure problems, process node and user ID requests, improve and bug fix ASL, attempt to keep up with end user support and pay the bills. Our team has identified and fixed every issue which has been brought to our attention. There is always room for improvement and we're continually working to this end. We are improving the current infrastructure to eliminate single points of failure. There are new geo-redundant registration servers in test with a clustered database backend. DNS has been migrated to this cluster of servers and has been running without fail for months. As AllStar supports a diverse userbase; many running older distributions at remote sites who desire stability, our admin team must operate with stability as the highest priority. As such we cannot make sweeping changes to critical network infrastructure without extensive testing. The registration and database servers have uptimes approaching a year, and have been continually available during this time. These servers are responsible for the nodes list, which is distributed to redundant public facing servers and on to users AllStar nodes. Even in the event of an outage during maintenance, the node list simply stops updating for a time. While inconvenient to nodes registering during this window, the vast majority of nodes are still able to link with this older node list. Our admin team has built a new stats server and are working on a new portal. By the way, we have been successfully processing ID and node requests on this new portal for months and have received very positive feedback on its new node list. We added a new node map and performance improvements to the stats server. MediaWiki has been installed with advanced search, a WYSIWYG editor, and other plugins, enabling anyone to create or update documentation. The Drupal site at docs.allstarlink.org is migrating as editors time permits. Our distribution has been updated including ASL 1.01 to run on the latest OS and has many improvements. More improvements are under active development. We're always open to assistance, whether it be design work, admin/support team help, or a completely new feature created by a code contributor. It's easy to get involved at any level. In closing we want to stress that if you have a problem with AllStar servers or want to help out in any way, please let us know by posting to the app_rpt-users list. That's the best way to insure the fastest response. AllStarLink, Inc. Directors: Kevin Custer, W3KKC Pete Elke, WI6H Bryan Fields, W9CR Tim Sawyer, WD6AWP

1 0

Re: [App_rpt-users] IAXRPT
by Mike Besemer - WM4B 13 Jul '18

13 Jul '18

Just saw this. I got my butt kicked by that too! Mike WM4B On Fri, Jul 13, 2018 at 1:44 PM, Russell Thomas wrote: > Someone called me in regards to the post and after some > troubleshooting it appears I didn't need to use special characters in > the password. > > Thanks everyone!! > > > 73, > Russell Thomas, KV4S > > Cell: 205.202.1701 > DMR: 3101393 > D-Star: KV4S > AllStar: 47923 > EchoLink: KV4S-L (1003254) > HamShackHotline: 614 > Web: http://KV4S.com > > > On Fri, Jul 13, 2018 at 12:41 PM, Mike <mm(a)midnighteng.com> wrote: >> Well, >> >> I'm going to bet you left a set-up set out. >> >> Look in your extentions.conf >> >> The below works if you define what node, node1 and node2 are >> >> [globals] >> HOMENPA = 330 ; change this to your Area Code >> NODE = 48396 ; change this to your node number >> NODE1 = 1999 >> NODE2 = 1010 >> NODE3 = 1020 >> >> [iaxrpt] >> exten => ${NODE},1,rpt(${NODE}|X) >> exten => ${NODE1},1,rpt(${NODE1}|X) >> exten => ${NODE2},1,rpt(${NODE2}|X) >> >> >> Otherwise >> >> define them exact like this >> >> [iaxrpt] >> >> exten => 48396,1,rpt(48396}|X) >> >> >> I showed both ways since when you look at the default settings in the >> file, >> you may see it listed either way. >> >> Can be confusing to those that do not know. >> >> Just so you understand the difference since the top one has been >> defined as >> a variable. >> >> Also make sure the 'context' is correct and your password in iax.conf >> >> Also, if you are using poerts 4570, or outside the normal/default, >> you will >> need to include that in your >> >> iaxrpt program connection data 'HOST' for the account like... >> >> 192.168.1.222:4570 >> >> .That should get you somewhere ! >> >> ...mike/kb8jnm >> >> >> >> On 7/13/2018 12:16 PM, Russell Thomas wrote: >>> >>> Looking for some help setting up IAXPRT on our club's AWS ASL node. >>> >>> I edited the iax.conf and the extensions.conf. I made sure the IAX >>> ports were open on the AWS instance. >>> >>> When I try connecting from the Windows client it says calling and >>> the >>> state has a "?" in it. Eventually it drops out. >>> >>> Any ideas? >>> >>> >>> 73, >>> Russell Thomas, KV4S >>> >>> Cell: 205.202.1701 >>> DMR: 3101393 >>> D-Star: KV4S >>> AllStar: 47923 >>> EchoLink: KV4S-L (1003254) >>> HamShackHotline: 614 >>> Web: http://KV4S.com >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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.

1 0

IAXRPT
by Russell Thomas 13 Jul '18

13 Jul '18

Looking for some help setting up IAXPRT on our club's AWS ASL node. I edited the iax.conf and the extensions.conf. I made sure the IAX ports were open on the AWS instance. When I try connecting from the Windows client it says calling and the state has a "?" in it. Eventually it drops out. Any ideas? 73, Russell Thomas, KV4S Cell: 205.202.1701 DMR: 3101393 D-Star: KV4S AllStar: 47923 EchoLink: KV4S-L (1003254) HamShackHotline: 614 Web: http://KV4S.com

2 2

Current procedure for re-compiling asterisk/asl on deb9 ?
by Mike 13 Jul '18

13 Jul '18

Do we have a current procedure for re-compiling asterisk/asl on deb9 ? Any links to a written version ? ...mike/kb8jnm

3 6

Re: [App_rpt-users] URI-X Issues With New Raspbian build
by Jim Aspinwall No1PC 13 Jul '18

13 Jul '18

First, apologies for what ended up coming out as a rant that 'got' to a few people. Not my intention... I tried to be casual/conversational and that doesn't work in-type. As a result I did get a different perspective on the history of AllStar developments... :O *** Steve: thanks for the specific log locations... I'll fetch and send them soonest. If there are common known errors and clues to "yup, bad card..." or "check x.conf and y.conf for consistency of z parameter" - I'm more than willing to start documenting log tidbits, clues, etc. for the 'KB' effort. (when I designed software I did ask the developers to spit out details once in awhile so we knew when function X crapped out... "wow, you know we can do that? CRAP!") In a production support realm, when you see a trend of 10... 20 similar issues, you start looking to how-to, KB, or systematic remote fixes to relieve the support team of production issues. As the back-end person pushing apps and updates the last thing *I* want is end-user calls/e-mails for the easy stuff... I have my own images, patches, packages and deployments to work on and annoy the user base on "Patch Tuesday"... the help desk knows better than to 'dox' me out to the users... :O *** Mike, you asked: "Could you state what the 'first few' commands are on 1st boot with your new image ? ...mike/kb8jnm" What am I looking for? The boot process of course dumps a ton of initialization info... What I type in? I go for "sudo asl-menu"

2 1

*** Net Tues July 14th - Open Source Engineering ASL-Pi HOT SPOTs WX8L Guest for Q&A !
by Mike 12 Jul '18

12 Jul '18

*Net Tues July 17th @ 8:30pm EDT ( that's wed July 18th @ 00:30 utc ) * *Connection data will be added as we put it together at - www.29999.link* SHOW-N-TELL - OPEN SOURCE ENGINEERING ! Sean, WX8L is Going to chat with us on his "ASL Micro-node/HotSpot " ! https://wx8l.blogspot.com/2018/06/personal-allstar-pocket-node-based-on.html You GOTTA Check Out His How-2 Page ! Trying to get others stuff for us all but Shawn is the main attraction and he is eager to answer questions on his ASL Pi Hotspot in our Q&A. Taking questions for the net via email at KB8JNM [at] USWX.mobi or Live during the Net But here is a tease from me... Just thought I would give everyone a sneak peek at what I have been working on, for mine that uses a touch screen that I intend to utilize to it's fullest potential... But it already does not look like this ... LOL But I'm not ready to answer questions Yet ! But it has a working DMR Bridge loading talk groups via DTMF ! Without a radio, so far, I have $75 in my 3B+ version. Tune in and 'help with your knowledge' and perhaps show-off your Open Source Engineering skills. I will collect photos/links of your projects for posting to the group on our web page ! www.29999.link/kb8jnm-asl-pi.JPG *This net will be recorded and played back at a new day and time, * *perhaps Sat 14th / Sun 15th in the afternoon. TBA * ...mike/kb8jnm

1 1

Re: [App_rpt-users] URI-X Issues With New Raspbian build
by Jim Aspinwall No1PC 12 Jul '18

12 Jul '18

So, I 'blew' the latest Stretch build into a new USB flash device... booted and tried to configure an existing node onto it on hardware that is known to work under prior. 1. ASL-MENU did NOT over-write the rpt.conf nor iax.conf files with given parameters - run as 'repeater' sudo root or enabled root user. FAIL. How is this fail 'possible' ? 2. Asterisk -rvvvvv... consistently revealed that the attached known interface did not exist and failed out with "...var/run/asterisk.ctl..." does not exist... when it actually does - what condition manifests this? NO low voltage errors on the console... all this on a known Pi3 AND RA-40 interface configuration under prior Jessie install... To this... after decades of WinTel system support and a variety of x-Nix support work... ... please understand I do NOT *want* to hint at, support, or indicate that 'Crompton' may be on to something because his builds aren't all that stable and documentation and support are no better an often wrong, accusational... but have not exhibited this level of 'stupid' non-function. I am also someone at the brunt of "it doesn't work" as an esclation point in massive enterprises, and can at least identify and analyze log files that may contain some hints... "give me (path)xxx log file..." and at least I provide or know full paths, not casual non-specific references. I would hope, expect the contributing community to be robust in definitive, helpful logging and not simply dismiss users to unqualified rhetoric/fault. That said...the latest Jessie build is a failure. The latest Stretch build is a failure. "change my mind" I'm back to tweaking the prior Jessie build to work as 'advertised' sans asl-menu and don't dare chance an upgrade/update process to the latest... I merely anticipate the coders know various failure conditions, can detect and log them... but that is an anticipation not rendered in actual logical recorded fact.| OK - get it - code contributors are volunteers. Volunteers that are supposedly intimate and knowledgeable with the code, functions, conditions, etc. Bad power (not evident), bad storage/boot device (not evident), yadda... so, what? If you cannot document the 'proper' necessary requirements for hardware, process, etc. you cannot hold us users accountable or nor unknown circumstances to blame for failures. This is logical, programmatic... SOMETHING can detect (or not) attached hardware and communications functions... but yet not tell us what part(s) failed? Certainly when a convenient configuration menu/utility cannot/will not write-out changed parameters - one can determine a file system or rights issue... and reveal same... not leaving the user with the deception the system is good to go when it is sitting there at useless defaults. We really do NOT want this project left to Crompton for the popular vote, nor the x-Nix elitists... it's much too good for either of that. I among others are willing to dig deep and provide any log files, etc. that are effective to supportive solutions. If logging content is ambiguous, not adequate to specific known logical issues, improve logging. If scripts do not work... let's debug... The leave behind is that if you were lucky enough to capture a prior Jesse build... sans asl-menu... stash it away and work around manual configs, leave it not user-friendly. If there are specific hardware, storage device requirements, document and better test for them. Obviously a current bootable latest Jessie build is NOT effective to new or existing node success. Why? Leave all of this to unstable, undocumented Crompton builds, or do equal or better... How can I/we help? -------------------Today's Topics: 1. Re: URI-X Issues With New Raspbian build (Steve Zingman) 2. Replay of June 26th Net at 8pm EDT (tonight) on 29999 (Mike) ---------------------------------------------------------------------- Message: 1 Date: Tue, 10 Jul 2018 15:31:47 -0400 From: Steve Zingman <szingman(a)msgstor.com> To: Users of Asterisk app_rpt <app_rpt-users(a)lists.allstarlink.org> Subject: Re: [App_rpt-users] URI-X Issues With New Raspbian build Message-ID: <b9e5a338-8b97-9d40-5a73-7a1757b76366(a)msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" If I had to guess, I would say a bad SD card burn. or a bad card. Steve N4IRS

6 6

Asterisk MODULES required for Phone Patch ?
by Mike 12 Jul '18

12 Jul '18

Can anyone state for the record, What asterisk 'MODULES' are required for the phone patch to function ? ...mike/kb8jnm

3 5

*** NODE LOAD TESTING HAS BEEN CANCELED FOR THIS SAT 14th ***
by Mike 12 Jul '18

12 Jul '18

*** NODE LOAD TESTING HAS BEEN CANCELED FOR THIS SAT 14th *** Reason... 'One' participant, and that participant stated he would not be around for the test. ???????? While I think this is 'very important', I personally will not 'ENTERTAIN' anyone state to me that I should use a 'untested resource' for use in nets etc . Nobody will be putting your head on the chopping block when things do not work out. I feel the more the better but _everyone needs some experience doing this sort of stuff. _Pass the torch !_ _ And this is not the same game it was just 2-3 years ago. I do know since I have taken part in many very large nets. How do you make judgements on load distribution without this data ? Just throw a lot of what you think are large assets at it and 'hope' it works ? _Well, Good luck in your 'RELIABLE' ecomm endeavors. _ Anyone think they have a 'magic formula' for figuring this out ? ... Keep guessing ! Most think it is simply a Network Bandwidth issue, and more often, it is a CPU/Memory bandwidth issue. Allison will eat into that 'heavily on smaller systems'. Heavy loads to your allmon page will do the same because it uses PHP server side scripting and is constantly querying your system for live data with each visitor that just sits there and monitors. Unlike HTML where you are just 'reading' the text, PHP uses the servers CPU to generate a HTML output in a dynamic way. I could state other things that eat into your available mem/cpu but for most of us, those are the 2 major ones but does not account for other services some run in their systems. Both of those mean less available resources for voice data to be distributed. So it is not just about 'Internet Bandwidth'. (It's-A Put-Up or Shut-Up situation. Just so all those 'back seat drivers' know where they stand with me.) I have been putting the work up to make 'even better things' possible and understandable going forward, and most of all, PLAN-ABLE. A large group of successful 'real world' tests will help us develop a formula that everyone will benefit from. Or we can continue to head down the path of failure from our own ignorance as this continues to grow rapidly. The issues will not be going away, but getting more important. I have stated my case for it the best I know how. Blaming it on 'the summer', *_I will re-visit the idea again this winter_*. 73, ...mike/kb8jnm

1 0

URI-X Issues With New Raspbian build
by Jim Aspinwall No1PC 12 Jul '18

12 Jul '18

Coincidence? Serendipity? I just tried the latest builds from: http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ Liking asl-menu... that helps... but as with others below... I have found, on a Pi3 + RA-40 that works under the prior 'build' - I too am experiencing multiple errors and ultimately failure of asterisk app to identify, connect to and use the USB-connected RA-40 as either USBRadio or SimpleUSB that worked under same configuration parameters. It's even complaining that asterisk.ctl is not in /var/run when it clearly is there. On the console I am getting low voltage errors I never saw before... using the same power source. Measurement at the board is minimum 4.96v. Power source is a PowerPole USBBuddy 3A device from clean DC - these run all of my field-racked nodes so far. Even a 1.5a wall-wart has been fine prior. Doesn't make sense when the operational voltage tolerance of the Pi is greater than this 0.8% difference. If the low-voltage check is getting in the way... how do we fix that? Separate power sources for Pi vs interface boards? If the voltage issue is NOT "getting in the way" of Asterisk using a good known USB-interfaced device? What is? Again, I can shut down the boards, swap the USB Flash drive from the latest build to the prior and it runs fine. I'm reluctant to in-place update the working node/stick... until I can properly clone the stick and test on an expendable build. (What tool does one use to make an image from a bootable stick?) Yeah it's decidedly an issue with snd-pcm-oss missing from the system.. > may need to compile a custom kernel.. _shrug_ >> this may not be relevant, but worth saying at this point. >> >> I have found that if you initialize a pi node while not supplying the Pi >> board with enough current >> >> during the initial start-up. Many things seem to go wrong. >> >> I'm building a bigger 5v power supply to handle 2 or three of these at >> once to verify what I'm thinking, >> >> but not tested anything yet. >> >> In my case, it is Dahdi >>> Not sure why but the /dev/dsp1 seems to be missing... I've installed >>> oss-compat and tried a number of things.. see below output... >>> >>> $ sudo uridiag >>> URIDiag, diagnostic program for the DMK Engineering URI >>> USB Radio Interface, version 0.9, 08/14/15 >>> >>> Found CM119 USB Radio Interface at 001/005 >>> Unable to re-open DSP device 1: /dev/dsp1 >>>

4 5