I think I'm gong to give up on this

AllStarLink
1

I can usually figure out how to do what I want to do. This ASL3 with all the old misinformation (Youtube) and a manual that seems to jump around to other links has me baffled. I think I have the node configured okay for a radio to node. This is not what I had in mind. I did not bother to connect a radio as I wanted to establish a link first. I wanted to be able to access the radio from the internet. Laptop>internet, internet>node>radio.... to repeater. I also wanted to be able to get the laptop internet through Starlink. I tried to set up IAXRpt on my Linux laptop, and it seems to run. I cannot make a connection to the node that works from IAXRpt. I occasionally get error messages depending on configuration in Allmon. Don't ask me what I'm doing, as I don't know. I have been beating my head against a wall for some time now, and I am at the point where I'm not sure if this exercise is worth it anymore. I see several places where IAXRpt is 'SO old'. I find it strange that there is not a Linux, or a Winblows application running under Linux, based dashboard that lets you control the radio functions. At this point, I'm pretty much done though. I am running Tailscale on both the node and the laptop, and that appears to be working okay. Maybe I'm wanting something that ASL is not capable of, I don't know.

OS : Debian GNU/Linux 13 (trixie)
OS Kernel : 6.18.34+rpt-rpi-v8

Asterisk : 22.9.0+asl3-3.9.3-1.deb13
ASL [app_rpt] : 3.9.3

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.9.1-1.deb13
asl3 3.18-2.deb13
asl3-appliance 2.1.0-2.deb13
asl3-appliance-pi 2.1.0-2.deb13
asl3-asterisk 2:22.9.0+asl3-3.9.3-1.deb13
asl3-asterisk-config 2:22.9.0+asl3-3.9.3-1.deb13
asl3-asterisk-modules 2:22.9.0+asl3-3.9.3-1.deb13
asl3-menu 1.18-1.deb13
asl3-update-nodelist 2.0.0-1.deb13
asl-apt-repos 2.0-1.deb13
cockpit 337-1+deb13u1
cockpit-bridge 337-1+deb13u1
cockpit-networkmanager 337-1+deb13u1
cockpit-packagekit 337-1+deb13u1
cockpit-sosreport 337-1+deb13u1
cockpit-storaged 337-1+deb13u1
cockpit-system 337-1+deb13u1
cockpit-wifimanager 1.2.0-1.deb13
cockpit-ws 337-1+deb13u1
dahdi 1:3.1.0-2.1
dahdi-linux 1:3.4.0-11.asl.deb13
pi@Node68295:~ $

Use sudo asl-show-version to obtain this information from the console or SSH

Asterisk Version: 22..x.y+asl3-3.n.m
ASL3 Version: 3.x.y

Inquiry

See https://allstarlink.github.io/user-guide/troubleshooting/ on how to ask a good question to obtain the quickest and best assistance

2

AllStarLink isn't a radio remote control system which is seems like that's what you're doing. I doesn't do remote radio control like a CAT or something - i.e. you're not going to change the channel, frequency, settings, etc. from ASL.

You can use an AllStarLink node as simplex link to a repeater. The normal method for a simplex link like you're discussing is you setup a radio on the frequency of interesting with all of the particulars for the repeater you want to access. Make sure that all works first. Then you can use an IAX context to add an app to remotely key the attached radio. However this isn't a standard use case so there's no "one stop" directions for doing it. However, the gist is to setup a node as a normal simplex node and get that working first. The manual has step-by-step install directions and based on you calling it "node" I"m assuming you're using a Pi. ASL3 Appliance Installation - AllStarLink Manual. Then configure a separate IAX context for your application: IAX Direct Authentication - AllStarLink Manual.

Be advised that using a direct IAX client is not very user friendly. There's a more modern all someone on the forum is developing that support Windows - https://qso1.net/. You still need a node with a radio setup though.

3

I read it that he's trying to connect to a link radio to a repeater.

IAXRPT works great but you need to make sure the name and "secret" match, then point it at the right ip address and port.

GeorgeC W2DB