You are definitely rate-limited by posting so many pictures. It’s much more efficient to copy/paste the text.
I believe your missing a fundamental concept for AllStarLink. It is NOT like Echolink where you have a “client” and something else is a “server”. You need to think of your ASL node as a single unit as you’re intending to use it. Your Pi + Radio is “the node”. When your radio is sending DTMF, you’re controlling YOUR node. Nothing else. You cannot control a node that’s a hop or more beyond yours. When you make a link to another AllStar-enabled Node, your DTMF is not passed along to the next node. Passing along DTMF would quickly devolve into madness. AllStarLink connects your node to one or more other nodes - BUT all audio is shared equally. If you connect to two different nodes, then your node will bridge the other nodes and everyonew will hear everyone else. It’s NOT point-to-point like Echolink.
First off, I’m assuming that you’re using the AllStarLink V3 Pi Appliance image when you talk about having installed it on a Pi. If that is NOT the case, then I strongly suggest that you reimage your Pi with the ASL3 image. See https://allstarlink.github.io/user-guide/pi-detailed/. After that, don’t start fiddling with permissions or running asterisk as root with asterisk -cvvv. Everything about the appliance is setup for “turnkey” operation. Most information you’ll find in Google will be obsolete for the very old versions of ASL2 of HamVOIP. If you haven’t see it, https://www.youtube.com/watch?v=aeuj-yI8qrU&feature=youtu.be is a very good walkthrough on how to install it.
Once you have it installed and configured, you should be able to get to the Asterisk CLI with asterisk -r through the Cockpit Terminal or via SSH. Again, don’t fiddle with the permissions of the applications.
You can issue commands from Allmon3 or the CLI. Both will work fine.
I’m pretty sure im running rhe proper allstarlink v3 Raspberry Pi image. I’m using a Raspberry Pi 4b, and I followed the instructions very carefully, from the same page you just sent to me when i initially set it all up.
The reason I dont copy/paste and post pictures here, is because I’m on my phone.
The version of the image I used is
allstar3-arm64-3.0.12.img
Im assuming this is the correct image for my Raspberry Pi 4B?
I thought that the V3 was the better choice over the hamvoip, as i was reading many negative things about hamvoip, and all the politics surrounding these versions, and was told i wouldnt get good support with hamvoip.
So, at this point, i can key the HT in my hand that is tuned to the same frequency that the HT connected to my G1LRO Universal radio controller (which is connected to the Raspberry Pi 4b) is tuned to, and the HT transmits, i hear a reply tone and the morse code response on my HT, and i see that allmon3 monitoring dashboard on my PC shows the state change from "transmit idle to “Transmit - local source”, and then back to “transmit idle” again once i release the key on the HT. It looks like everything is working correctly in terms of the whole PTT part of things, but what im wondering is, what next?
What do i then do on my handheld HT to communicate with the node to get a response that shows me its all working, other than just keying up and getting a response? I dont know if im missing a key part of the user manual, but im just not seeing anything that walks me through step by step in the “operation” of this node, and that explains in short laymans terms what it should be doing and when it should be doing it, it seems everything “assumes” i already know all of this, but as a beginner with this, i do not know, lol. The information seems either incomplete, or overwhelming.
I mean im not a complete dummy, i managed to easily build a Raspberry Pi direwolf digipeater with no problems, but im having trouble navigating through the information i need to get this allstarlink v3 all working and set up properly, which includes step by step operation instructions once its actually set up. Lol.
73
From looking at your screenshots, I can’t tell if you have buggered up the configs or have a corruption in the software. A good bit to sort out.
Perhaps start again with a fresh image per @N8EI instruction.
If you can’t get to a asterisk CLI> from the start without error, then you have other issues.
Rely on the pi install guide for asl3 installation.
The wiki may help guide you on some files/settings. https://wiki.allstarlink.org/wiki/Special:AllPages
Actually, it just started working. I didn’t do anything to it. The asterisk CLI runs fine, everything loads the way it should.
At this point, it just needs tweaking i think.
I just installed hamvoip on a seperate SD card, and it runs fine as well. The bugs I’m experiencing are with that G1LRO Universal radio controller, its not working as the setup on the G1LRO page says to set it up in simpleUSB, but now that ive figured out that whole PTT and CTCSS thing, i knew exactly how to set it up for hamvoip when i just installed that. The only weird thing that happened is that when i set it to toggle echo mode, it keyed up and just kept looping and toggling until i disabled it lol.
Weird stuff like that, and its probably all to do with the G1LRO Universal radio controller. I also cant get fldigi to work with that URC, but thats a whole otger topic meant for another place.
73
Well, I really can’t help with hamvoip stuff. I thought testing it per instruction would lead you to the light.
Because you were trying to debug software for hardware you couldn’t be certain of. And with instruction not intended.
And I am no help with that other hardware either.
But perhaps now you can hit issues per instance, one at a time with asl3 and kinda know where you stand.
I would say a good troubleshooting experience has been earned !
Remember, if it all just works, you learn nothing.
Except perhaps you follow instruction well ? LOL