Pending registration causing connection failure

AllStarLink
,
1

Hello,

I am attempting to setup my first node (fresh download of ASL3 image) and have a problem I can’t find an answer for. I have attempted the setup on a Proxmox VM and a Pi4 with the same results. I can connect to 55553 Parrot but nothing else. I have consistently not been able to ping registration.allstarlink.org or allstarlink.org, although an October 2025 post suggested that is no longer a test I should use since it has been disabled to save bandwidth. I am behind a T-Mobile wireless internet gateway and have tried the IAX registration setup as mentioned in the instructions and a few YouTube Videos with no change.

I am pretty comfortable around Linux and know enough networking to find it frustratingly the cause of may issues, however in this case I am at the end of the line for ways to troubleshoot this further, having used multiple machines, multiple routers (with port forwarding), multiple T-Mobile gateways all with the same apparent registration issue. Help anyone? Is T-Mobile doing something on the outbound/inbound IP to obfuscate the necessary IP information?

I have seen others mention a similar ability to use Parrot but not connect to other nodes. Why is that?

Inquiry

Host dnsmgr Username Perceived Refresh State
52.20.63.146:4569 Y 67717 60 Request Sent
1 IAX2 registrations.

Setup Information

********** AllStarLink [ASL] Version Info **********

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

Asterisk : 22.5.2+asl3-3.6.3-1.deb13
ASL [app_rpt] : 3.6.3

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.6.1-1.deb13
asl3 3.11-1.deb13
asl3-appliance 2.0.1-2.deb13
asl3-appliance-pi 2.0.1-2.deb13
asl3-asterisk 2:22.5.2+asl3-3.6.3-1.deb13
asl3-asterisk-config 2:22.5.2+asl3-3.6.3-1.deb13
asl3-asterisk-modules 2:22.5.2+asl3-3.6.3-1.deb13
asl3-menu 1.15-1.deb13
asl3-update-nodelist 2.0.0-1.deb13
cockpit 337-1
cockpit-bridge 337-1
cockpit-networkmanager 337-1
cockpit-packagekit 337-1
cockpit-sosreport 337-1
cockpit-storaged 337-1
cockpit-system 337-1
cockpit-wifimanager 1.1.1-1.deb13
cockpit-ws 337-1
dahdi 1:3.1.0-2.1
dahdi-dkms 1:3.4.0-10.asl.deb13
dahdi-linux 1:3.4.0-10.asl.deb13
dahdi-source 1:3.4.0-10.asl.deb13

2
3

I can address that question. Assuming you’re talking about parrot 55553, that node has the source-IP address validation feature turned off. Anyone can connect to 55553, regardless of whether their node is properly registered.

4

This is correct re node 55553. At some point, I would like to bake something into the logic that checks the incoming node for registration, and plays a message via early media (less than five seconds) if your node is not registered, before your node actually connects. It would be very easy to do this on node connect, but then that message would go out globally, and I’d rather not do that.

Node 55553 is currently running on HamVoIP, so it uses outdated dialplan stuff from Asterisk 1.4.26.3, so I’d probably have to port it to a more modern system before attempting such a thing.

I’d also like to build in a PL tone detector. I often hear people coming in with PL tones bleeding through, some quite loudly, which throws off the average RMS significantly, and could eventually cause other issues.

But, back to the topic of registration, my node doesn’t care if you are registered or not, as Bruce mentioned. Most nodes do.

5

Many thanks for the comments and explanations. Seems like a change of plans will be needed as a simple workaround is not sounding probable. It is helpful to understand why 55553 works. That makes my troubleshooting make much more sense.

6

If you can't get better Internet service, you can try 44Net Connect for ASL - AllStarLink Manual.

7
8

FWIW, I too experience this, however after a few minutes the problem goes away. I am connected to my home internet, radioless. 55553 works but nothing else… wait 3-5 minutes and the problem goes away.

VA3JPX

9

I am experiencing essentially the same problems with a mature ASL node on a T-Mobile network. I live in rural Rienzi MS, so T-Mobile is my current best internet option. It used to work when I shut it down a couple of months ago, now it won’t register, I can’t ping stats.allstarlink.org, and can’t connect if the node can’t register. N3SDO
GRRR!

10

I signed up, requested, installed, and currently using a 44net tunnel. This is the best this node has ever worked for me on T-Mobile! It’s still configured for IAX2 registration, but its working! I will let it run a few hours, and may get brave and try to switch over to http later this evening.

1 Like
11

N8EI, thanks for turning me on to 44net. Its fixed my T-Mobile issues! 73 Ed N3SDO

2 Likes
12

Fantastic! I am glad to hear a success story.

1 Like