- App_rpt-users - lists.keekles.org

Adding echolink to Dial
by Steve Siesel 26 Dec '17

26 Dec '17

All, I am trying to add echolink to my ASL install (Dial). I read the ASL FAQ's and added the echolink.conf. I also made sure the ports are open as well. Is there anything else I need to do besides adding echolink.conf in the /etc/asterisk directory? Is there anything else I need to do? [el0] confmode=no call=K4KSA-L ; Change this! pwd=***** ; Change this! name=Steve Siesel ; Change this to your real name! qth=Seminole, Florida ; Change this to your actual QTH! email=steve(a)siesel.net ; Change this! maxstns=20 rtcptimeout=10 node=950077 ; Change this! recfile=/tmp/recorded.gsm astnode=46031 ; Change this to your active Allstar node number! context=radio-secure server1=server1.echolink.org server2=server2.echolink.org server3=server3.echolink.org freq=145.000 ; Freq in MHz tone=0 ; CTCSS Tone (0 for none) lat=27.863859 ; Latitude in decimal degrees lon=--82.833252 ; Longitude in decimal degrees power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) gain=0 ; Gain in db (0-9) dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)

2 1

New DIAL Install No RX or TX Audio from URI
by Keith Dobbins 26 Dec '17

26 Dec '17

I had my node working under ACID till a hard drive decided to crash on me. I did the re-install with the 32 bit DIAL install. Everything about the node appears to function properly but from asterisk to my URI I get ZERO audio in or out. It's the only audio adapter, and the URIDIAG with the loopback plug tests fine. It will activate the TX and I get the blinking green led but no audio in or out. Is there somewhere I can look to troubleshoot this issue? The motherboard is an older atom 330 board. Should I fall back to the older ACID install for this node which had worked. Thanks for any guidance that you can provide.Keith Dobbins N8KLD

2 3

24/7 Echolink Connection Dropping Audio
by Will Bashlor 22 Dec '17

22 Dec '17

Hello all, We have an AllStar node setup using a Pi 3, DMK URI, and a Yaesu 7800. It’s AllStar Node 46648 and it’s connected to 3004544 (echolink) 24/7. It works fine most of the time, but intermittently the audio quits working in the Internet to node/radio direction. It shows up on allmon2 and echolink as connected and if you talk RF everyone on the echolink network can hear you, but when they talk back no audio comes through to 46648 or to the Yaesu that’s connected to it and it doesn’t turn green on allmon2. If I disconnect the echolink node and connect it again it fixes the no audio until it happens again. I’ve tried with a normal connect and a permanent connect and the same thing happens using both. It may be 30 minutes or 3 days before it happens again. I wouldn’t mind it disconnecting every now and then because I have a script running (also tested without the script running) that automatically connects it back, but I have no way to detect when the audio drops except listening to it on echolink and my node at the same time. I am using a Ubiquiti Edge X router and have 4569, 5198, and 5199 UDP forwarded correctly (I’m a network guy). I’ve checked the asterisk log but it’s so full of brute force attacks I can’t really find any clue of what’s going on. I am wide open for suggestions. Any ideas or anyone experienced this issue before? Thanks in advance and 73. Will, KE4IAJ TARG <https://www.facebook.com/profile.php?id=196073504193006&ref=br_rs> AEC

3 7

Re: [App_rpt-users] 8. Re: Did i read that we have an apt-get install allstarlink? (Steve Zingman)
by Jim Aspinwall No1PC 22 Dec '17

22 Dec '17

"... You have to add the repository to your pt/sources.list.d/ You also have to add the key." Who/what/where is: pt/sources.list.d/ ??? Full proper paths and syntax ???? TYPOchmod +x /install-repository Should be: chmod +x .//install-repository ?? TYPO:ap-get install allstarlink -y Should be: apt-get install allstarlink -y ???

3 2

Re: [App_rpt-users] Connect to Echolink as Conference Server?
by Jeff Carrier 21 Dec '17

21 Dec '17

> > You can do this but you also have to pay echolink a "donation" of $40/year > to have a conference server. > de K0JSC > > Hi List, > > > > Any idea if you can connect to the Echolink network via AllStar as an > Echolink Conference server? In other words, configure echolink.conf with > credentials that allows it to connect to Echolink as a conference server > instead of -R or -L? > > > > 73 > > Will, KE4IAJ > > <https://www.facebook.com/profile.php?id=196073504193006&ref=br_rs> TARG > AEC > >

2 1

Connect to Echolink as Conference Server?
by Will Bashlor 21 Dec '17

21 Dec '17

Hi List, Any idea if you can connect to the Echolink network via AllStar as an Echolink Conference server? In other words, configure echolink.conf with credentials that allows it to connect to Echolink as a conference server instead of -R or -L? 73 Will, KE4IAJ <https://www.facebook.com/profile.php?id=196073504193006&ref=br_rs> TARG AEC

1 0

Official AllStarLink RPi Image - Testing Updated Version (Not yet released)
by Will Bashlor 19 Dec '17

19 Dec '17

Hi List, Here’s some exciting news to give, JFYI! I am testing an updated version (not yet released to the public) of the official AllStarLink image for the RPi. Currently it’s installed on an RPi Zero W connected to a modified CM108 FOB and a modified BF-888S (~30mW). Seems to be working great so far. If you have any questions feel free to reply to the list and hopefully they can be answered with a collaborative effort. 73 Will, KE4IAJ TARG <https://www.facebook.com/profile.php?id=196073504193006&ref=br_rs> AEC

1 0

Re: [App_rpt-users] [Allstar-admin] AllStarLink Install process.
by Steve Zingman 18 Dec '17

18 Dec '17

Folks, This now needs to end. Please refrain from this subject on either side and return this list to it's intended purpose. I will place on moderation anyone that carries this further. 73, Steve N4IRS

1 0

Re: [App_rpt-users] Can I get some one to point me to the iso image for allstarlink..
by David KE6UPI 17 Dec '17

17 Dec '17

Hello Loren, Dial x86/AMD http://dvswitch.org/files/AllStarLink/allstar-firmware-8.7.1-amd64-i386-net… You'll need to unzip the file with 7zip. burn the .iso image to a CD-ROM. Then boot your AllStarLink computer with the CD-ROM. Check that the BIOS is set to boot from the CD-Rom or check boot options and choose CD-ROM or DVD. The MD5 file just checked the .iso file. (Not needed if the install goes OK) DIAL Raspberry Pi http://dvswitch.org/files/AllStarLink/RAT_RC1.tar.gz You'll neded to unzip the file with 7zip. You'll then need a image writer (Win32 DiskImager). After you right the image to the MicroXD card. You can boot your Raspberry Pi. Read the README.txt file login info. David KE6UPI On Sun, Dec 17, 2017 at 5:10 AM, Steve Zingman <szingman(a)msgstor.com> wrote: > Maybe you did not understand me. The MD5 of the ISO matches the included > file Someone else can explain MD5. > > > On 12/17/2017 08:04 AM, Loren Tedford wrote: > >> Greetings I have downloaded the iso image on now 7 seperate machines >> looking to get a non corrupted iso image for allstar.. The one on the main >> site seems to be corrupted for me but not for Steve so reaching out to the >> community for help with this one.. Anyone that has the official iso in a >> google drive or drop box please let me have the link so i can get a iso >> image that is correct.. >> >> >> Thanks Loren (KC9ZHV) >> >> _______________________________________________ >> 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. >> > > _______________________________________________ > 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. >

3 3

AllStarLink Install process.
by Steve Zingman 17 Dec '17

17 Dec '17

This is nuts! Loren contacted me directly at 18:30 Saturday night, to tell me "Hey! You might want to add this before the installation of the certificates.. apt-get install ca-certificates <- With out this you can't download it on a fresh system.. (Just found out today)" When I get a report like this I try to recreate the issue. I could not recreate her problem. I suggested she do a apt-get upgrade since the cert should be up to date. This did not help. She then reported another error when trying to do a apt-get install allstarlink. I decided it was time to spin up a fresh VM to see if I could recreate here problem. I run a VMware ESX cluster at work, so it's easy for me to spin up a VM. I did a fresh install of Debian 8, 64 bit, added the repository and performed the apt-get install allstarlink. It did not report any errors and the install worked. Just in case I ran a second test this time doing a 32bit install. Again, no problem. At 19:30 She told me "you can install proxmox on a main machine use the linux container rather than a VM" "container is better than a vm though as far as resource and cpu latency that is.." Ah, she is running on a container. I do use VMs in production and they are a great tool to test things like a ISO install. I can roll back quickly and do not have problems installing from stock Linux ISOs. Since ASL requires DAHDI, a kernel module has to be built. I said I have to question the ability of a container to install a kernel module. Google turned up a number of hits and possible solutions. At this point Loren had moved on to installing from the ISO. I posted the ISO in July. The file is a .tar.gz file. Pretty standard for most operating systems. Could it have been a zip? Yes. I did not see much difference. Inside of the compressed file are a couple of readme files, the ISO and a text file containing the MD5 of the ISO file. I may be wrong, but this is pretty good insurance that the ISO you get is what I posted. At about 20:00 Loren reported that the ISO install was stuck on Reading State information. I went to the download site, downloaded <http://dvswitch.org/files/AllStarLink/allstar-firmware-8.7.1-amd64-i386-net…> This is the file I posted in July. I used 7zip oin Windows to extract the ISO and used that ISO to test install 32 bit and 64 bit. Both worked as expected. Loren then told me "the files are saved as a tar and its a tar inside of a tar no matter how many times i unzip it it shows this way" I tried to explain that a .tar.gz file is a gzipped tar file. I tried to explain the the MD5 in the text file needed to match the MD5 of the ISO file. I went so far as to send her a screen shot from my Window 7 machine showing 7zip and the contents of the file. it's now almost 22:00. She told me "Those file sizes are incorrect for what i have here.. I also use 7 zip to unpack files.." Also, "I suggest probably just pulling the iso now especially since its not working correctly" Really? Quite a few people have used the exact same download. I can't recreate here problem and it's time to head for bed. At 08:00 the next morning Loren posts "I have downloaded the iso image on now 7 seperate machines looking to get a non corrupted iso image for allstar" OK, I've had enough. The ISO is built from the Debian NetInstall ISO. As with the the Debian ISO, parts of the install are on the ISO and parts are downloaded from the Internet. In our case, with this version of the ISO, the source code is downloaded and installed. The ISO installer as gone through a number of changes to try to address issues people have encountered. I can not test on every piece of hardware or platform. I have to rely on repeatable reports. The apt-get install and the ASL repository are the first step in moving away from installing from source. With the repository as bugs are found and enhancements added, I can push out a change and the user can do a simple apt-get upgrade. The RaspberryPi version is now built this way and the next version of the ISO will be built the same way. The current source code will always be be in github and available to anyone who wants to install from source or customize it. It's open source and always will be. Is software perfect? No, is the install method perfect? No. It is a work in progress. Do the scripts need work? Absolutely. I have to admit, I don't spend enough time on the hand holding scripts. I know I should. I am spending most of my time in the install itself. I feel if ASL itself is installed and running that is a good part of the battle. In a private e-mail Loren complained about the nodesetup script. It's a legacy script and it does suck! I invite Loren to step up and fix it. A side note to Loren, I have gone out of my way a number of time to help you. I setup a account on your old provider so I could help you install ASL. Since your last post on the list you have sent me 4 e-mails directly. Please stop. I have enough work on my plate. If you have a question, post on the list. Someone will help you out. This is peer to peer support after all. In closing, if you expect perfection, do it yourself. All the source code is posted. Bugs, warts and all. We welcome pull requests. 73, Steve N4IRS

2 1