- App_rpt-users - lists.keekles.org

TX Timeout
by Bernie McIntosh 07 Jun '17

07 Jun '17

I am using a smartphone to access my node so that I can listen to the radio channel, and when required, transmit on the channel. All is well, but I want to implement a timeout so that if I put the node into transmit mode from my smartphone and do not return it to receive, the transmitter will turn off, after say, 30 seconds. I am using the default IAX configuration for the smartphone. The tx_timeout parameter makes the transmitter turn off at the required time as expected. But when a radio user subsequently transmits on the channel and then goes back to receive, the node keys the transmitter again and continues to send audio from the smartphone on the channel. It is as if the smartphone PTT is still "closed" and so the timeout timer resets itself and waits another 30 seconds before switching off again. So I guess I need a way to disconnect the smartphone after x seconds of PTT from it ? Google is failing me on this one and I'd be grateful for any help. Thanks Bernie GM4WZG > -----Original Message----- > From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users- > bounces(a)ohnosec.org] On Behalf Of app_rpt-users-request(a)ohnosec.org > Sent: 03 December 2016 17:00 > To: app_rpt-users(a)ohnosec.org > Subject: App_rpt-users Digest, Vol 94, Issue 3 > > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: Podcast Server (Danny) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 Dec 2016 19:03:17 +0200 > From: Danny <mynixmail(a)gmail.com> > To: app_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] Podcast Server > Message-ID: <20161202170316.GA3444(a)fever.havannah.local> > Content-Type: text/plain; charset=us-ascii > > >On Dec 02 16, Eric Guth : > > > > Dear Danny, > > > > This is very clever. Thanks for including my podcast, QSO Today, in your > Allstar jukebox of podcasts. > > > > 73, > > > > Eric Guth > > 4Z1UG > > Allstar: 28422 > > QSO Today > > > > Hi Eric, > > It is only a pleasure. I have been listening to your podcast for so long and I > thought it would be befitting to repay you and all the others that have > podcasts in such a manner. > > Would you believe me if I told you the same evening I advertised "Play > Something" on this list we experienced heavy thunderstorms which forced > me to shut down the whole system ... lol ... > > But at least I got to test my skills at unplugging everything within a flash. I > think I broke my own record ... less than 4 minutes to pull the plug and > disconnect all feedlines ... > > However, on a slightly different note ... please guys, if you register with a > mistyped callsign contact me immediately in order for me to rectify it. Too > many hams blamed the system, but when I checked the database and their > original registration e-mail, they mistyped/misspelled their own callsigns > and/or e-mail address. > > Some of you asked me to give a little more detail, so here goes. > > "Play Something" does exactly what it's name says, it "Plays Something". You > don't know what you are going to get. But I guarantee you will not hear the > same podcast played more than once in 3 months or more (except for ARRL > news). The algorithm I have developed will prevent this from happening. > Podcasts are not randomly selected, but rather in a fashion where you will be > able to follow a certain podcast provider from his first podcast to his last > podcast in a sequential order. Also, you will not hear the same podcaster > twice in a row. > > "Play Something" observes time-outs. It transmits for 150 seconds, then > unkeys for 10 seconds. I think 10 seconds should be enough for anyone to > squeeze through a DTMF code ... ;) ... > > Oh yes ... one important thing ... YOU NEED TO CONNECT TO MY NODE to > listen ... > people send me mails telling me "Play Something" is not working but they > never even connected ... ;) ... > > "Play Something" is for EVERYONE and ANYONE for FREE (for as long as > possible). > I have no problem if you park your node permanently at my node whilst you > are just listening ... that's just fine by me ... > > I am open to suggestions ... and if you have a podcaster you would like to add > you are more than welcome to make a suggestion > > Thank you > > Danny > ZS6XOX > 73's > > AllStar node 44081 > EchoLink ZS6XOX-R > > zs6xox(a)gmail.com > > (p.s: Thank you for listening ...) > > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 94, Issue 3 > ********************************************

1 0

Re: [App_rpt-users] /bin/cp: /tmp/rpt_extnodes-temp and /tmp/rpt_extnodes-temp are the same file
by izzy_y2k＠yahoo.com 06 Jun '17

06 Jun '17

Hello Steve Thanks for the quick reply I am using Dial version 325 Thanks John K1IF --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

A little confusion regarding the X86 Downloads
by Jeremy Utley 06 Jun '17

06 Jun '17

Hey all! As I reinstall my hub node after it got compromised this morning, I find myself a little confused at just which download option I should use for an amd64 architecture machine. The site seems to recommend DIAL RC1, but RC *usually* means Release Candidate - meaning it's not quite ready for prime time, but getting close to release. I would not usually consider a "RC" release to be the recommended release under any circumstances. The other problem comes from looking at the file modification dates on the dvswitch.org server: The RC1 file - amd64-i386-DIAL-RC1.tar.gz - is dated Nov 15, 2016 The other file - dial-allstar-netinstall.iso - is dated Jan 22, 2017 So it *seems* that the RC1 is older than the other one, while still being the recommended install - but the name would not tend to agree, as the RC should be a candidate for release as a newer version, so should be newer than the existing "stable" version - and the stable version should be the recommended download - or at least this is how it would work in most open source projects. What am I missing? And once installed, is there any danger in using the Debian "apt-get update" command to update the packages for the underlying Linux OS to their newest versions? Thanks, Jeremy, NQ0M

2 1

/bin/cp: /tmp/rpt_extnodes-temp and /tmp/rpt_extnodes-temp are the same file
by izzy_y2k＠yahoo.com 06 Jun '17

06 Jun '17

Keep seeing this error pop up. I assume it is from an update node list generated by allstar but not sure how or where to fix? Thank you John K1if --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Re: [App_rpt-users] What is the "debian" user in the DIAL distro?
by Thor Wiegman 06 Jun '17

06 Jun '17

You're not the first person I'm aware of to have this type of problem. AllStarLink nodes are an easy target to become bitcoin miners and members of botnets. Most people installing these nodes don't know the basics of Linux system administration and the defaults aren't even remotely secure. Not only should that "debian" user be deleted, the appropriate changes to SSH need to be made to prevent the superuser "root" from logging in remotely. That is one of the first things that everyone needs to be change after installation of a DIAL system, not sure why it's even allowed by default. I've noticed that a lot of node ops tend to login as root and execute commands as the root user. Crazy! It's an extremely dangerous and insecure thing to do, but people new to Linux don't know any better. It would be nice if the default installation were setup in such a way that prevented or discouraged login by the superuser. It's odd that sudo doesn't appear to be installed by default. Would be very nice if the installation script prompted for the creation of a user account with proper permissions in much the same way as standard distros do. Not perfect, but it's a start. Most of these systems are being run by people who are new to Linux. They don't know about Linux/Unix system administration and nobody is "elmering" them in it. The result is people taking dangerous shortcuts and developing bad habits. The community would benefit from some guidance in system administration as well as from some improved defaults in the distro. On 05/10/2017 12:38 PM, app_rpt-users-request(a)lists.allstarlink.org wrote: > What is the "debian" user in the DIAL distro?

6 8

Re: [App_rpt-users] App_rpt-users Digest, Vol 100, Issue 6
by Steve Wright 05 Jun '17

05 Jun '17

On Tue, Jun 6, 2017 at 9:00 AM, Bob Pyke <k6ecm1(a)gmail.com> wrote: > > > http://docs.allstarlink.org/drupal/ > > Thanks Bob, others. Don't quite know why I didn't find that.. Overall, the docs are pretty frustrating and I don't have anywhere near the skills to rewrite them. Steve

3 2

ohnosec
by Steve Wright 05 Jun '17

05 Jun '17

What is the proper entry point for asterisk app_rpt? If ohnosec is it, then quite frankly it is completely incoherent - even for seasoned linux folks. thanks s

4 4

First Time Install with some issues..
by Steve Siesel 02 Jun '17

02 Jun '17

All, Here is what my problems are: 1. Getting the following in my asterisk trace: [Jun 1 21:33:22] WARNING[587] chan_iax2.c: REGISTER-LOG: registry rereqquest [Jun 1 21:34:12] WARNING[588] chan_iax2.c: REGISTER-LOG: Sending registration request for '46031' [Jun 1 21:34:12] WARNING[580] chan_iax2.c: REGISTER-LOG: registry rereqquest However my iax2 show registry shows: DMRLink*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 67.215.233.178:4569 Y 46031 47.203.114.127:1025 60 Registered 2. I have port forwarded both udp and tcp 4569 to the Allstar node. I have also added the following to iax.conf for Zopier access: [k4ksa] username=steve type=friend context=myphone host=dynamic auth=md5 secret=xxxxxxx disallow=all allow=ulaw allow=g726aal2 allow=gsm codecpriority=host transfer=no ;callerid=K4KSA I have also added the context to extensions.conf as well. This is what I am getting in the asterisk trace when trying to register (also getting error 29 from Zopier) [Jun 1 21:35:35] NOTICE[585] chan_iax2.c: No registration for peer 'steve' (from 47.203.114.127) [Jun 1 21:35:37] NOTICE[582] chan_iax2.c: No registration for peer 'steve' (from 47.203.114.127) [Jun 1 21:35:40] NOTICE[585] chan_iax2.c: No registration for peer 'steve' (from 47.203.114.127) 3. Telephone access from Allstar. When using the dial in telephone number trying to get voice or function access it times out with a busy signal. I did a tcpdump port 4569 and I can see the telephone service making It to the machine: 21:43:29.564494 IP seal.lambdatel.com.iax > DMRLink.home.iax: UDP, length 96 21:43:29.565075 IP DMRLink.home.iax > seal.lambdatel.com.iax: UDP, length 65 Using RAT RC1 Anyone have any thoughts to my three problems? Steve K4KSA

2 3

Re: [App_rpt-users] mini-pc recommendations for Allstar / Dial
by Mark Johnston 02 Jun '17

02 Jun '17

I don't know how often there would be a freeze up, *root@KC7DMF:~# uptime* * 19:22:06 up 19 days, 31 min, 1 user, load average: 0.05, 0.09, 0.12* *I believe this may address the issue, I added **kernel.panic = 20 * *to /etc/sysctl.conf* *I know it would kernel panic once in a great while, never did find exactly why, but this seems to keep it running.* *I also wrote a script when the network has packet loss, to restart...* "Got Root?" How many software engineers does it take to change a light bulb? *None. It's a hardware problem.* Unix is user friendly. It's just very particular about who it's friends are. WINDOWS: Will Install Needless Data On Whole System MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools Teenagers. A ntennas P oorly P laced L acks E ngineering The best way to accelerate a computer running Windows is at 9.81 m/s². *"I get paid to support Windows, I use Linux to get work done."* On Thu, Jun 1, 2017 at 9:31 AM, Ken Alker <ka6ken(a)alker.net> wrote: > Thanks. Have you managed to avoid the freeze-up issue due to the clock > problems on certain Atom processors (Bay Trail, and possibly others) due to > a conflict with the kernel being used in the Dial release (apparently, a > CPU problem, but a problem nonetheless)? > > > --On Thursday, June 01, 2017 5:46 AM -0700 Mark Johnston < > markjohnston73(a)gmail.com> wrote: > > I have purchased a few using the Intel Atom CPU, they are not super fast, >> but I have had 4 URI's connected with no issues, and internet streaming >> as well on one node... they are inexpensive, and no fan on them, got 12V >> power supplies for them, mounted it all in a 1U rack, but there are >> plenty of other small form factor PC's like that if you just want a >> desktop style (mini) computer. Some are "Industrial" type, might look at >> what amazon has, etc... >> >> >> >> >> >> >> >> >> "Got Root?" >> >> >> How many software engineers does it take to change a light bulb? >> None. It's a hardware problem. >> >> >> >> >> Unix is user friendly. It's just very particular about who it's friends >> are. >> WINDOWS: Will Install Needless Data On Whole System >> MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools >> Teenagers. >> >> >> >> >> >> A ntennas >> P oorly >> P laced >> L acks >> E ngineering >> >> The best way to accelerate a computer running Windows is at 9.81 m/s². >> >> >> "I get paid to support Windows, I use Linux to get work done." >> >> >> >> On Thu, Jun 1, 2017 at 12:51 AM, Ken Alker <ka6ken(a)alker.net> wrote: >> >> Hello, >> >> I am brand new to this list and Allstar (although I have been using >> Asterisk for well over a decade). I would like to run three URIs off of >> one PC running Dial. The PC will also communicate with at least three >> RTCMs at other locations. I ASSuME, based on this requirement, that a >> mini-PC would be the best platform (and not a Rasberry Pi or other ARM >> based processor). Please correct me if this is wrong (as I'd love to >> get away with a super low power $35 computer). >> >> What mini-PC platforms have people successfully used (IOW, what mini-PCs >> would you suggest I look into)? I'd like something relatively >> inexpensive, low power, and with no moving parts (for a difficult to >> reach remote location at high elevation). >> >> I've been looking into the Qotom mini-PCs, however, many of them seem to >> be based on the J1900, and I have heard that the Intel "Bay Trail" >> processors (of which the J1900 is one) have some clock issues due to a >> conflict with the (Debian) kernel being used in the Dial/Allstar >> project. I don't know if newer releases of the processor have fixed >> this, or if it applies to every single Bay Trail processor ever >> produced. Perhaps someone can expound on this for me, as well. >> >> Thank you! >> >> Ken Alker >> KA6KEN >> http://www.impulse.net >> _______________________________________________ >> 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/c > gi-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] mini-pc recommendations for Allstar / Dial
by Mark Johnston 01 Jun '17

01 Jun '17

I have purchased a few using the Intel Atom CPU, they are not super fast, but I have had 4 URI's connected with no issues, and internet streaming as well on one node... they are inexpensive, and no fan on them, got 12V power supplies for them, mounted it all in a 1U rack, but there are plenty of other small form factor PC's like that if you just want a desktop style (mini) computer. Some are "Industrial" type, might look at what amazon has, etc... "Got Root?" How many software engineers does it take to change a light bulb? *None. It's a hardware problem.* Unix is user friendly. It's just very particular about who it's friends are. WINDOWS: Will Install Needless Data On Whole System MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools Teenagers. A ntennas P oorly P laced L acks E ngineering The best way to accelerate a computer running Windows is at 9.81 m/s². *"I get paid to support Windows, I use Linux to get work done."* On Thu, Jun 1, 2017 at 12:51 AM, Ken Alker <ka6ken(a)alker.net> wrote: > Hello, > > I am brand new to this list and Allstar (although I have been using > Asterisk for well over a decade). I would like to run three URIs off of > one PC running Dial. The PC will also communicate with at least three > RTCMs at other locations. I ASSuME, based on this requirement, that a > mini-PC would be the best platform (and not a Rasberry Pi or other ARM > based processor). Please correct me if this is wrong (as I'd love to get > away with a super low power $35 computer). > > What mini-PC platforms have people successfully used (IOW, what mini-PCs > would you suggest I look into)? I'd like something relatively inexpensive, > low power, and with no moving parts (for a difficult to reach remote > location at high elevation). > > I've been looking into the Qotom mini-PCs, however, many of them seem to > be based on the J1900, and I have heard that the Intel "Bay Trail" > processors (of which the J1900 is one) have some clock issues due to a > conflict with the (Debian) kernel being used in the Dial/Allstar project. > I don't know if newer releases of the processor have fixed this, or if it > applies to every single Bay Trail processor ever produced. Perhaps someone > can expound on this for me, as well. > > Thank you! > > Ken Alker > KA6KEN > http://www.impulse.net > _______________________________________________ > 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/c > gi-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.

2 1