- App_rpt-users - lists.keekles.org

Radio-tune-menu not functioning
by John Rudolph- N2YP 28 Mar '18

28 Mar '18

I'm at a loss. I upgraded my Dial system to the new All Star Link 1.0 and am have a few issues. When I try and run radio-tune-menu I get root@N2YP_Rogers_Knob:~# radio-tune-menu Error parsing device parameters I've read through past messages and checked that chan_usbradio was the active one in modules and that simple USB was set for no load. Also as of right now my nodes load with the URI's and sort of function as they are. Even when no radios are hooked up they lockup in "transmit" mode. I've tried rebooting the system and any other suggestions I could find with no luck. I've tried with both new and old conf files with no success. John Rudolph Amateur Radio Op N2YP Unadilla,NY

3 4

Transmit issues
by KB7YS-Stacey 27 Mar '18

27 Mar '18

A bit frustrated this morning. Node 46857, latest image install on an RPi 3, all updates (update/upgrade) performed. Allmon2 installed and working fine. SimpleUSB through a CM FOB, connected to a 888s (however radio is most times turned off). Yesterday was adding my phone hotspot to the wireless configs and testing through both to make sure it was working by connecting to node 2560 in listen mode. I was controlling through Allmon2, with radio attached, but not transmitting. After I was all done I tried to connect to WINS on 2560 and was rejected, several times - eventually was contacted and told I had keyed down the system 3 times, a couple minutes each. Odd thing was as I said I never transmitted. I checked messages log and did not find anything other than the usb not being ready at startup, but eventually it does start about 15 sec later and no other messages after. Later last night I connected to 2560 (after being un-banned) and listened to almost an hour of the insomniac net, controlling through allmon2 and listening via android iaxrpt. All the time watching the Asterisk cli, then checking after I disconnected the tail of the messages log. All looked fine. This morning (node on all night, not connected to any other node, radio off). Connected to 46857 via iaxrpt desktop and used macro to connect to 2560. Not 10 min later I noticed I was not hearing anything from iaxrpt. Opening Allmon2 I saw I was disconnected from 2560 again. I received an email that I was keying the system again... I wasn't touching anything or doing anything config wise. I did have the cli open, here is what it said: Verbosity is at least 3 -- Accepting AUTHENTICATED call from 192.168.1.129: > requested format = gsm, > requested prefs = (), > actual format = gsm, > host prefs = (ulaw|adpcm|gsm), > priority = mine -- Executing [46857@iaxrpt:1] Rpt("IAX2/iaxrpt-6390", "46857|X") in new stack == Spawn extension (iaxrpt, 46857, 1) exited KEEPALIVE on 'IAX2/iaxrpt-6390' == Refreshing DNS lookups. -- Call accepted by 173.82.59.253 (format ulaw) -- Format for call is ulaw -- Hungup 'DAHDI/pseudo-714478141' -- Hungup 'DAHDI/pseudo-104883990' -- Hungup 'DAHDI/pseudo-1905028877' -- Hungup 'DAHDI/pseudo-1251358383' -- Hungup 'DAHDI/pseudo-547114662' -- Hungup 'IAX2/173.82.59.253:4569-1730' -- Hungup 'DAHDI/pseudo-605528485' -- Hungup 'DAHDI/pseudo-553835508' == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:35074 -- Accepting AUTHENTICATED call from 192.168.1.107: > requested format = ulaw, > requested prefs = (ulaw), > actual format = ulaw, > host prefs = (ulaw|g726aal2|gsm), > priority = mine -- Executing [46857@phone-iaxrpt:1] Rpt("IAX2/android-iaxrpt-7544", "46857|P") in new stack == Spawn extension (phone-iaxrpt, 46857, 1) exited KEEPALIVE on 'IAX2/android-iaxrpt-7544' == Refreshing DNS lookups. == Refreshing DNS lookups. == Refreshing DNS lookups. == Refreshing DNS lookups. == Refreshing DNS lookups. == Refreshing DNS lookups. == Refreshing DNS lookups. == Refreshing DNS lookups. == Manager 'admin' logged on from 127.0.0.1 -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:59606 -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 [Mar 27 08:02:20] WARNING[584]: chan_iax2.c:3101 __attempt_transmit: Max retries exceeded to host 192.168.1.107 on IAX2/android-iaxrpt-7544 (type = 6, subclass = 2, ts=2477969, seqno=113) -- Hungup 'IAX2/android-iaxrpt-7544' -- Hungup 'DAHDI/pseudo-1835956150' == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 == Refreshing DNS lookups. == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 == Refreshing DNS lookups. == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:53095 == Refreshing DNS lookups. -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:40182 -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:51207 -- Registered IAX2 'android-iaxrpt' (AUTHENTICATED) at 192.168.1.107:46617 == Refreshing DNS lookups. -- <DAHDI/pseudo-491804915> Playing 'rpt/node' (language 'en') -- Hungup 'DAHDI/pseudo-868072667' -- Hungup 'DAHDI/pseudo-1469835999' -- <DAHDI/pseudo-491804915> Playing 'digits/2' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/5' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/6' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/0' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'rpt/connected' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/2' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'rpt/node' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/4' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/6' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/8' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/5' (language 'en') -- <DAHDI/pseudo-491804915> Playing 'digits/7' (language 'en') -- Hungup 'DAHDI/pseudo-491804915' -- Hungup 'DAHDI/pseudo-1496043418' -- <DAHDI/pseudo-788169365> Playing 'rpt/node' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/2' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/5' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/6' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/0' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'rpt/connected' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/2' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'rpt/node' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/4' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/5' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/8' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/5' (language 'en') -- <DAHDI/pseudo-788169365> Playing 'digits/3' (language 'en') -- Hungup 'DAHDI/pseudo-788169365' About 2/3 of the way down you see where the system was transmitting telem - this has me confused also this is where I turned on the radio... why did that start playing then? After it started going into the 2nd set of info I just pulled the plug. Ok, sorry about writing a book here, but I am quite confused as to why the system keeps keying down that node - is there a more detailed log that someone can point me too... I am at a bit of a loss and honestly a little afraid to connect to anything at this point. Thoughts? ThanksStacey - KB7YS

1 0

User Guide
by Tom 26 Mar '18

26 Mar '18

I am a newbie to Linuix and as well as AllStar Link. Well maybe not totally new but new enough that I do not have much of a clue as to what I am doing. I know that there a few .conf files examples that are on the web site. But I am wondering if there is a single document that I can download that will kinda take me through the steps to setup an operational node, with out getting help from some of my ham friends. 73 Tom AD2TM

3 2

Announcing AllStarLink Asterisk version 1.01
by John Rudolph- N2YP 25 Mar '18

25 Mar '18

Steve I know you're a very busy guy and we appreciate all your work. Have you gotten a chance to post how to upgrade from DIAL to the new All Star Link? Jeff, The Images and NetInstallers are built on Debian or Raspbian. For installs on existing Debian Based distributions (Ubuntu or Linuxmint...), you will be able to install via "apt-get install allstarlink". I have one tweak to make to the repository and I will publish the instructions for adding the repository to a existing system. 73, Steve N4IRS On 03/18/2018 09:38 PM, Jeffrey Lehman, KC8QCH wrote: > > Great job Steve! This is awesome! > > One question. Does this still only run on Debian (i see it does > stretch) or can we now use this on any Debian based distro? Like > Ubuntu or Linuxmint? > > Thanks for all of your hard work. > > Jeff John Rudolph Amateur Radio Op N2YP Unadilla,NY

2 1

Re: [App_rpt-users] Announcing AllStarLink Asterisk version 1.01
by Greg Noneman 24 Mar '18

24 Mar '18

Steve, I have a question about the installation/update of AllStarLink Asterisk version 1.01 that I don’t believe the ReadMe file addressed (pardon me if I missed it). I have both Intel/AMD and RPi installations that are currently running DIAL. Is there any simple/effective way to “automatically" upgrade tp ASLA 1.01, or is it necessary to back up my config files, perform a new clean install, and then restore my configs? Thanks, Greg WB6ZSU > On Mar 18, 2018, at 3:08 PM, Steve Zingman <szingman(a)msgstor.com> wrote: > > We are happy to announce AllStarLink Asterisk version 1.01. This updated version contains a number of bug fixes and enhancements. The method used for installing and upgrading AllStarLink Asterisk has been changed from building from source code to simply install and upgrade the programs that make up AllStarLink Asterisk. AllStarLink Asterisk is now using the same update method any other Debian program has used for years. The package management system is called APT (acronym for Advanced Package Tool). APT is a set of tools for managing Debian packages, and therefore the applications installed on your Debian system. > > The link on allstarlink.org and the wiki <wiki.allstarlink.org> Now point to the new images for x86/AMD and Raspberry Pi. > > <http://dvswitch.org/files/ASL_Images/Intel-AMD/Stretch/ASL_1.01-20180228-am…> > <http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228…> > > The repository of AllStarLink Images is located at <http://dvswitch.org/files/ASL_Images/> > > For a more complete explanation of the changes to AllStarLink Asterisk see <http://dvswitch.org/files/ASL_Images/readme.txt> > > 73, Steve N4IRS > _______________________________________________ > 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.

4 5

Wireless issues on new install
by KB7YS-Stacey 23 Mar '18

23 Mar '18

Final issue I will bring up for a while (I hope, but can't promise): On the Acer Aspire One I installed on I added the wlan adapter to the interfaces file: # wireless adapter with dhcp auto wlp2s0 iface wlp2s0 inet dhcp wpa-ssid myssid wpa-key-mgmt WPA-PSK wpa-group TKIP CCMP wpa-psk mypasskey After doing this I ran across the script in the asl-menu for setting up wireless and ran it - it looked like it added info to the wpa.supplicant (I verified it's all info was correct). Ok, so here is the issue - the wlan connects and gets proper addresses and dns - I can ping anything and get responses, I can ssh to other systems on my network, there seems to be no problem with bi-directional communications *if* originated from the system. The same cannot be said for incoming - no ping response, no ssh, apparently nothing connects when coming in. I don't think it's an issue with the adapter or driver, also it was working (after manually adding to interfaces) on the previous image. I am not sure where to start but hoping someone can help direct my focus and efforts. Thanks again!Stacey - KB7YS

4 4

Connecting to other Nodes
by kk4avi＠yahoo.com 23 Mar '18

23 Mar '18

Hello, I'm trying to configure my node. It connect to AllStar and I can have other nodes connect to my node. I'm unable to connect to any nodes. When I do *70, it gives the node number and then says "REPEAT ONLY". I'm using a Motorola Maxtrac radio connected to a raspberry pi. Do I have something configured wrong? Robert KK4VI Alvaton, KY

3 2

DIAL install on Virtual Box
by KB7YS-Stacey 22 Mar '18

22 Mar '18

Still learning, but getting there... After no luck with getting a previous version of DIAL that was available on the ASL site to work with my fob interface, a suggestion led me to find there was a new version available. After installing and working though the asl-menu setup I finally had a working node with my old Acer Aspire One. However there were still some tasks to complete. While working through the Allmon2 install process I thought why not use Oracle Virtual Box to test on instead of the actual system. It was a good thought however the currently available image will not install on Virtual Box 5.2.8. Just for kicks I grabbed the current 32bit Debian iso - this installed on the virtual system with no issues. Anyone have any thoughts or ideas on why the DIAL image would not work. Error is 'no kernal' during the install... and it stops. I can continue, but then grub has nothing to load when the virtual reboots. Thank for any assistance. (PS - I did finally get Allmon2 installed and working, that was a bit of a bumpy ride, a good learning experience) Stacey - KB7YS

4 5

DIAL install - asl-menu setup glitch?
by KB7YS-Stacey 22 Mar '18

22 Mar '18

After running through the set up menu items and saving the settings then making it "live" one final question was if I wanted to start the menu again on next login - I accidentally answered yes, but figured I would just answer no next time if necessary. Even after going through the make it live process and choosing 'no' to start on next login (multiple times), my system always started (until I manually disabled) into the menu. Not sure if others have seen this, but wanted to share my experience just in case. Actually it would be nice to have a way to disable from the menu without running through the setup all the way... or at the very least having that choice change and stick. Hope this input helps make the install process better for all. Stacey - KB7YS

3 3

First time run problem
by TGundo 2003 22 Mar '18

22 Mar '18

Good morning all- newbie to the project here, and I'm learning Linux at the same time. I have a tiny bit of Linux experience, but not enough at this point. Still trying to get all the basic commands down (too much DOS stuck in my head). I managed to successfully download the latest DIAL image, put it on an SD card, and get my Pi2 to boot up. It prompted me to change the PW, which i did in the default repeater@repeater user. I also logged into root and changed that password. The 2 current issues I have are: 1- I never had the "first run" prompts for the node config pop up, and from what I read on the wiki it should. Any thoughts? 2- I cannot seem to SSH either into the root or repeater user from putty. It rejects the connection. I am trying to use port 222. Any thoughts? The user Repeater doesn't seem to have rights to install apps, i tried to get VIM per the instructions of another Ham, it wouldn't under the repeater user, but it did under the root user. Is that normal? Thanks for any help, sorry for such basic questions! TomW9SRV

2 1