- App_rpt-users - lists.keekles.org

Reg server root cause
by Bryan Fields 19 Sep '18

19 Sep '18

Looks like we had a failure in Tampa this morning, but as expected the registration server did kick over to Chicago (ORD), but there are still several hundred nodes not running dnsmgr and thus kept trying to use the IP of the Tampa server. Please check your registrations as below: > > iax2 show registry > Host dnsmgr Username Perceived Refresh State > 44.72.21.13:4569 Y 44233 44.98.249.6:4569 60 Registered > 44.72.21.13:4569 Y 42032 44.98.249.6:4569 60 Registered If you don't have dnsmgr as 'Y' please add this below as /etc/asterisk/dnsmgr.conf -- [general] enable=yes ; enable creation of managed DNS lookups ; default is 'no' refreshinterval=300 ; refresh managed DNS lookups every <n> seconds ; default is 300 (5 minutes) -- Then restart asterisk and verify you're now seeing dnsmgr as 'Y' in the registry messages. Also inexplicably, about 300 nodes are still hitting allstarlink.org directly for registrations. This server may go offline at any time. We've personally messaged node owners with the address on file before, please ensure you're using register.allstarlink.org as the registration server and you have dnsmgr enabled. The root cause today looks to be IPSEC tunnels went down and didn't reestablish automatically as they should have. As all traffic between the allstarlink.org servers is inside these tunnels this caused the TPA nodes to drop out of the cluster. The DNS did fail over to the register-ord server so for the majority of people DNS refreshed and you moved over. We're going to let it run on ORD for a bit. Further complicating this was as these tunnels were down, our monitoring system was unable to contact us, so we learned about the outage 15 minutes later than we should have. We'll be correcting this. We're investigating why IPSEC didn't refresh and reestablish these tunnels automatically, as testing before showed they had. Please ensure you have dnsmgr running on your node(s). 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0

Registration Issues
by Sean McCarthy 19 Sep '18

19 Sep '18

Is this something on my end? Can't connect out anywhere... [Sep 19 10:16:12] NOTICE[360] chan_iax2.c: Registration of '46483' rejected: 'Registration Refused' from: '44.98.254.145' Thanks, Sean

2 1

Node 48455 still having registration issues after adding private module
by qrz＠tg9aor.net 19 Sep '18

19 Sep '18

After another attempt to integrate a private module(1001), I got the following: repeater*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 48455 <Unregistered> 60 Rejected [Sep 19 08:18:15] NOTICE[22786]: chan_iax2.c:9712 socket_process: Registration of '48455' rejected: 'Registration Refused' from: '44.98.254.145' Do I need to put the private module at the very end of rpt.conf? ,before the last line that starts with # The node works, connects to allstar and echolink nodes, bridges to DMR no problem, but it fails to register on the stats.allstarlink.org database. I deleted the private node from rpt.conf , modules.conf, extensions.conf, and after that it shows up on the database again. I guess I will try to compile instead of using the image for armhf architechture, but then again I recall there is this DAHDI issue when compiling with stretch and a RPi 3B+. Do I loose by not being registered at allstarlink.org? Is it OK to just run it as is with the DMR bridge and not showing up on the stats.allstarlink.org list? 73 de TG9AOR

1 0

Politics
by Tim Sawyer 18 Sep '18

18 Sep '18

There has been a ton of inaccurate statements by the HamVoIP principals in numerous posts, emails and telephone calls regarding what AllStarLink is up to. Before you read the rest of this email please take a look at the August 16 post over on hamVoIP.org. I really don't want to wade into this political BS. I should be coding not spending time on this BS. Even so I've spent tons of time behind the scenes attempting to get folks working together. I hesitate to speak publicly on this but my low key approach has not worked. So, some false statements must be publicly corrected. I will address only this particular post at this time. First, "The server" is not owned by one person. The very reason AllStarLink, Inc. was formed is to prevent that scenario. Second, there is not just one server. There are numerous servers around the country run by folks that donate their time, effort and money. Third, HamVoIP principals continually imply that AllStar was unofficially taken over. That's just not true. The reigns were turned as officially as possible given Jim's sudden death. Jim's long time friends and co-developers of AllStar contacted current and past AllStarLink board members and made arrangements for what you see today. Additionally, it's true that migration to the new servers didn't go perfectly. But it's extreme unfair to bash individuals who are only attempting to improve AllStar. Ham Radio is about learning if it's about anything. Making mistakes happens as part of the learning process. Now we have a better system and no one got shot as my Marine friend used to say. The August 16 HamVoIP statements are divisive and only serve to build up some individuals at the expense of others. To HamVoIP principals I say enough of that crap! If you want to build a better mouse trap you are welcome to that. Go for it. But don't justify yourself by speaking badly of others who have nothing but good intentions. -- Tim WD6AWP

13 20

Re: [App_rpt-users] Politics
by Mike Besemer 18 Sep '18

18 Sep '18

I just wish all this talk would stop! I get it - I really do - but all this talk is just stirring the pot and it certainly doesn't solve anything. It's like watching Congress! Mike WM4B -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Buddy Brannan Sent: Tuesday, September 18, 2018 4:34 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Politics Heya Lauren, Nope. This is all to do with the HamVOIP folks, AKA Doug ’n Dave, who developed an alternative bistro for the Pi, previous the BBB and friends, on an ArchLinux bistro. There’s some not nice ball playing going on here, beginning with but not limited to development of software without any source code release in evidence or, apparently, planned, like ever. > On Sep 18, 2018, at 10:05 AM, Loren Tedford <loren(a)lorentedford.com> wrote: > > I have been seeing some of theses posts.. But what the heck is going on???????????? > > > > Is this over the whole deal where i am degrading the product or what ever because of my purchase of voipham.com? I created it originally to be a tutorial kinda page for those of us that had trouble installing allstar link back in the day.. Yeah i know its about 5 or 6 years old now and i haven't done much with it since my accident in October of 2014 and sorry about that.. Also Tim I am looking at digging a bit further into allmon will update things eventually but was looking at making it more mobile compliant that sort of thing and possibly locking it down with like an admin page using MySQL database or some thing.. Just haven't gotten around to having Mark to help me with some of that since i have forgotten just about all of it now. > > > > Anyway still trying to figure out exactly what i missed that started this whole political incorrectness or what ever.. > > > > Thank You all involved :) Keep up the good work! > > Loren Tedford (KC9ZHV) > > > > > > > > > > > On 9/18/2018 9:11 AM, Tim Sawyer wrote: >> Supermon is based on my Allmon 2 software https://github.com/tsawyer/allmon2 which I give freely to anyone who wants it with no restrictions. If the HamVoIP folks told you not to port Supermon to Allstarlink, that further demonstrates their total disregard for fairness. >> >> But it's more than fairness. Great things in humanity are built upon the knowledge of others. Software is no exception. HamVoIP took Asterisk/AllStar/app_rpt which has thousands of hours of development by countless people and closed it, ending the path to the next level of knowledge. Think about where we'd be if no one shared their knowledge. "We stand on the shoulders of giants" is the point I'm making. No one will be standing on HamVoIP's shoulders. >> >> HamVoIP (David) did give back some code (a security fix) to Allmon 2. A whole lot more of that should be happening. >> >> On Mon, Sep 17, 2018 at 8:00 PM Pierre Martel <petem001(a)gmail.com> wrote: >> I had the pleasur to be in the moderated status on that list after asking for the source code.. I was even kicked out after I publicly told them I would use there packet of supermon to port it to allstar link. Never did as I dont want to agravate this with the coder of supermon, wich I dont remember the name. >> >> >> >> Le lun. 17 sept. 2018 à 01:03, Buddy Brannan <buddy(a)brannan.name> a écrit : >> Harold, did you get put on moderated status after daring to question the lack of any source code release? I did. No real skin off my nose, but still. >> >> As for the magnetic loop group, do you mean magloop@yahoogroups? I skim there, generally a pretty decent bunch, but there’s always someone who will try to ruin it for everyone. (Sigh) And so it goes. Sadly, our hobby is a microcosm of society in general; were it not so. >> >>> On Sep 16, 2018, at 7:33 PM, <k7ilo1(a)gmail.com> <k7ilo1(a)gmail.com> wrote: >>> >>> I don’t know much about them but after going to the website, it reminded me of how I had known about them. >>> They private emailed me about what they were up to after I hit this post with a question about something that I don’t remember, but that’s besides the point. >>> The email if I remember correctly was kind of, in a way, hateful toward the asterisk group. >>> I never pursued their website or anything else about them since. >>> >>> It really sucks that OUR HOBBY has become this way. I left the magnetic loop group after expressing my feelings toward something that was said. >>> It put down all of the people that had joined this hobby during the 90’s when the FCC introduced the no code technician and they bashed the crap out of em. >>> Which I took personal because Im one of them. >>> >>> Anyway, I just wanted to throw my 2 cents in about how political and how ham groups bash the other. What has OUR HOBBY come to? >>> >>> Harold >>> K7ILO >>> Las Vegas, NV. >>> Node 27863 >>> >>> From: App_rpt-users <app_rpt-users-bounces(a)lists.allstarlink.org> On Behalf Of Tim Sawyer >>> Sent: Sunday, September 16, 2018 2:11 PM >>> To: Users of Asterisk app_rpt <app_rpt-users(a)lists.allstarlink.org> >>> Subject: [App_rpt-users] Politics >>> >>> >>> There has been a ton of inaccurate statements by the HamVoIP principals in numerous posts, emails and telephone calls regarding what AllStarLink is up to. Before you read the rest of this email please take a look at the August 16 post over on hamVoIP.org. >>> >>> I really don't want to wade into this political BS. I should be coding not spending time on this BS. Even so I've spent tons of time behind the scenes attempting to get folks working together. I hesitate to speak publicly on this but my low key approach has not worked. So, some false statements must be publicly corrected. I will address only this particular post at this time. >>> >>> First, "The server" is not owned by one person. The very reason AllStarLink, Inc. was formed is to prevent that scenario. >>> >>> Second, there is not just one server. There are numerous servers around the country run by folks that donate their time, effort and money. >>> >>> Third, HamVoIP principals continually imply that AllStar was unofficially taken over. That's just not true. The reigns were turned as officially as possible given Jim's sudden death. Jim's long time friends and co-developers of AllStar contacted current and past AllStarLink board members and made arrangements for what you see today. >>> >>> Additionally, it's true that migration to the new servers didn't go perfectly. But it's extreme unfair to bash individuals who are only attempting to improve AllStar. Ham Radio is about learning if it's about anything. Making mistakes happens as part of the learning process. Now we have a better system and no one got shot as my Marine friend used to say. >>> >>> The August 16 HamVoIP statements are divisive and only serve to build up some individuals at the expense of others. To HamVoIP principals I say enough of that crap! If you want to build a better mouse trap you are welcome to that. Go for it. But don't justify yourself by speaking badly of others who have nothing but good intentions. >>> >>> -- >>> Tim WD6AWP >>> _______________________________________________ >>> 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. >> >> >> -- >> Tim WD6AWP >> >> >> _______________________________________________ >> 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

Re: [App_rpt-users] App_rpt-users Politics
by Jim Aspinwall No1PC 17 Sep '18

17 Sep '18

Tim, Thank you for this difficult/challenging/challenged response. Of all the things amid the demand of *strict private dialog...* (like, what are you going to do, sue me for making email in MY Inbox public?) from HamVoIP, after getting past the rhetoric, what struck me most and remains a curiosity, is their claim that they created "apt rpt" code 3 years before others did or stole theirs, or whatever. The genesis of Asterisk and it's implementations certainly NOT in question. So, maybe further revelation may or may not help... but the question is out there or by this I'm putting it there - stirring the pot - who/what/when/where... is/was the first application of Asterisk to radio interfacing? HamVoIP branding and "market penetration" speak suggests something less than benevolent, and their creative alternatives/options for some aspects of the scheme... fine - depart from rather than collaborate toward improvements of the WHOLE of the AllStar system. Amateur radio has NO room for the 'bitchiness' of X- vs Y- , etc. Let's connect and communicate. All due respect and appreciation for this. Carry on! -------------------------------------Message: 1 Date: Sun, 16 Sep 2018 14:11:15 -0700 From: Tim Sawyer <tisawyer(a)gmail.com To: Users of Asterisk app_rpt <app_rpt-users(a)lists.allstarlink.org> Subject: [App_rpt-users] Politics Message-ID: <CAG3ht9vYTz7KeWomAOkjMWw_jvTeChRi3oVr-qY=_3Bp0yXiAw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8"

1 0

Server uptime, distributed resources, etc.
by Michael Wolthuis 17 Sep '18

17 Sep '18

Good afternoon, Many of you were aware of many recent updates to the server infrastructure that runs the Allstar network as maintained by the core Allstar team. Some of these updates did cause some issues around NAT that we do NOT need to relive. I am one of the people who donates servers, bandwidth and storage space at my top tier datacenters. My company is gracious enough to allow me research space that I have donated to the project directly to Jim and beyond. Those recent updates worked really hard to make sure we had a distributed architecture! We do NOT rely on a single location, a single datacenter, a single physical server. The ORD (Chicago, IL) location of Allstar that the core team uses is actually made up of over 32 blade servers and the load even with-in the datacenter is distributed. I just thought, given the recent weather issues across the US it would be important to note that this painful work (done by some very tired out people) was done for your benefit! The network as designed using the core and original Allstar network systems is now redundant and distributed. There is a core team of us who are Network Engineers and Data Center Engineers on the original team (going back to when Jim was alive) and we are doing this right! To that point, as the goal is to be open and forth-right with information – please feel free to see the Public link to our network statistics and information: https://grafana.allstarlink.org/ You as an end-user can now see the stats of the Allstar core infrastructure at any time! Please know we continue to work on improvements, it was a LARGE project to get the legacy network to this point and now that those waters are settling you will begin to see advances. We don’t run the back-end of this network lightly or on a Raspberry Pi :> If you have questions, as always, the team is here to assist. Please know there are many of us working behind the scenes to keep the Allstar network we all know and love running and online 24x7x365. Feel free to email directly off-list if any questions need to be answered. Want to help? Use the donation link to send Allstar a donation (please note, my commercial company doesn’t request any fees). Mike Wolthuis KB8ZGL

1 0

PC Version
by John Griffith 17 Sep '18

17 Sep '18

Greetings! Are we close to having an image for PC's yet? John Griffith, N7OKN

3 4

Fwd: Re: Politics
by Jeremy Utley 16 Sep '18

16 Sep '18

Oops, Meant to send this directly to the list. Discussion mailing lists *really* should be set up so that replies go to the list, not to the sender :) Jeremy, NQ0M -------- Forwarded Message -------- Subject: Re: [App_rpt-users] Politics Date: Sun, 16 Sep 2018 19:36:13 -0500 From: Jeremy Utley <jerutley(a)gmail.com> To: Tim Sawyer <tisawyer(a)gmail.com> Unfornately, the only solution to the current problems is going to be someone who can show they have copyright in the existing codebase, and deep enough pockets to fund a lawsuit. Without that, all that can be done is to bring social pressure - and unfortunately, the biggest majority of people that use his software don't really understand open source. I myself started off with his release, but once I realized he refused to actually release his code, I immediately started to move things back to DIAL. My old repeater (now off-air) that ran AllStar had to use a VPN - I was stuck behind a *Triple-NAT* so there was absolutely no way I could get a port forwarded, and OpenVPN allowed me to get around that. But the OpenVPN package never started on boot properly in his installation, nor did the SNMP daemon I used for monitoring the performance of the system. I also had to have another "backdoor" means (a router with VPN and SSH capability) to get into the node to start the VPN and SNMP daemons after a power failure. DIAL of course never had this problem, but it exhibited a different problem - there was a slight delay in the transmitted audio, so when I would transmit on the repeater, I would hear about a half-second of my transmission. It wasn't annoying enough to go back, but I'd have loved to have gotten ahold of his source code, and compiled it under Debian to see if that solved it. Honestly, if I had my own choice, we'd still be running under CentOS - I much prefer that to Debian, but I'm OK with Debian/Raspbian, and can't stand Arch at all. I'm honestly tempted to try to compile against Centos, it's just not worth the time it would take to build on ARM. My biggest concern right now is in the fact that the underlying Asterisk code being used is so old (it's lke 1.4 still, is it not?). But I'm sure porting apt_rpt to newer versions isn't an easy thing - I just don't like running end-of-life code. But I have all my setups majorly firewalled, and usually even running behind a VPN, so that helps to ease the worry. Jeremy, NQ0M On 9/16/18 4:11 PM, Tim Sawyer wrote: > > There has been a ton of inaccurate statements by the HamVoIP > principals in numerous posts, emails and telephone calls regarding > what AllStarLink is up to. Before you read the rest of this email > please take a look at the August 16 post over on hamVoIP.org. > > I really don't want to wade into this political BS. I should be coding > not spending time on this BS. Even so I've spent tons of time behind > the scenes attempting to get folks working together. I hesitate to > speak publicly on this but my low key approach has not worked. So, > some false statements must be publicly corrected. I will address only > this particular post at this time. > > First, "The server" is not owned by one person. The very reason > AllStarLink, Inc. was formed is to prevent that scenario. > > Second, there is not just one server. There are numerous servers > around the country run by folks that donate their time, effort and money. > > Third, HamVoIP principals continually imply that AllStar was > unofficially taken over. That's just not true. The reigns were turned > as officially as possible given Jim's sudden death. Jim's long time > friends and co-developers of AllStar contacted current and past > AllStarLink board members and made arrangements for what you see today. > > Additionally, it's true that migration to the new servers didn't go > perfectly. But it's extreme unfair to bash individuals who are only > attempting to improve AllStar. Ham Radio is about learning if it's > about anything. Making mistakes happens as part of the learning > process. Now we have a better system and no one got shot as my Marine > friend used to say. > > The August 16 HamVoIP statements are divisive and only serve to build > up some individuals at the expense of others. To HamVoIP principals I > say enough of that crap! If you want to build a better mouse trap you > are welcome to that. Go for it. But don't justify yourself by speaking > badly of others who have nothing but good intentions. > > -- > Tim WD6AWP > > _______________________________________________ > 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 visithttp://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

New AllStar Portal - A work in Progress
by Tim Sawyer 16 Sep '18

16 Sep '18

We've been working on a new AllStar portal. The goal is to eventually replace the original allstarlink.org with a modern, secure, better looking and more usable site. It 's not going very fast but there has been progress. Just to update everybody, here's what's on the new portal so far. - The site has moved to a faster server with better access to the database. The new location is https://web-tpa.allstarlink.org/. - It has a much better nodes list over the original. It has sort, filter, pagination and links to the stats pages. - There a new sign up page to register with AllStar. It has a much friendlier form and should assure more accurate input. - There is a password reset page. BTW, your login and password are the same as on the original allstarlink site as it's accessing the same database. - A new feature the original site doesn't have to change your callsign. This is much easier for you as well as admins which should get these completed faster. If you request a callsign change by email (the old way) you'll probably be asked to use the new site for your request. - All of the normal admin functions have been performed on this site for nearly a year. You won't see these unless you are an admin. - Works much better on mobile devices using 'mobile first' coding methods. - Secure login Cookie with longer expiration. - No more Flash. Yeah! Please use this new site when you can. We think you'll really like the new nodes list. Let us know if you find any bugs, typos, spelling errors, unclear wording, etc. You could even let us know if you like it :-) PS. The site is coded in HTML 5 using Twitter Bootstrap, jQuery, pdo, jwt and other web developer geek alphabet soup. PPS. Don't forget we have a new WiKi as well https://wiki.allstarlink.org/ <https://wiki.allstarlink.org/wiki/Main_Page> -- Tim WD6AWP

7 14