Latest ASL3 update broke ability to connect hotspot (duplex = 1) to most nodes

[Brent_Dix]

Setup Information

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

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.12.34+rpt-rpi-v8

Asterisk : 22.4.1+asl3-3.5.4-1.deb12
ASL [app_rpt] : 3.5.4

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.5.1-1.deb12
asl3 3.8-1.deb
asl3-asterisk 2:22.4.1+asl3-3.5.4-1.deb12
asl3-asterisk-config 2:22.4.1+asl3-3.5.4-1.deb12
asl3-asterisk-modules 2:22.4.1+asl3-3.5.4-1.deb12
asl3-menu 1.14-1.deb12
asl3-pi-appliance 1.10.0-1.deb12
asl3-update-nodelist 1.5.1-1.deb12
cockpit 287.1-0+deb12u3
cockpit-bridge 287.1-0+deb12u3
cockpit-networkmanager 287.1-0+deb12u3
cockpit-packagekit 287.1-0+deb12u3
cockpit-sosreport 287.1-0+deb12u3
cockpit-storaged 287.1-0+deb12u3
cockpit-system 287.1-0+deb12u3
cockpit-wifimanager 1.1.1-1.deb12
cockpit-ws 287.1-0+deb12u3
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-6+asl
dahdi-linux 1:3.4.0-6+asl

I'm running a Shari USB on a Raspi 4B.

Inquiry

Everything was working fine until I did a software update today. Now most of the nodes I normally connect to like the East Coast Reflector (45192) return a Connection Failed message. Asterisk CLI shows the call accepted but then an immediate hangup.
-- Call accepted by 12.17.28.213:4569 (format ulaw)
-- Format for call is (ulaw)
-- Hungup 'IAX2/12.17.28.213:4569-4879'
I've tried this with several other nodes that I regularly listen to and all return connection failed. Interestingly, the one exception I've found is the Parrot node (55553) which continues to work. And, no, I'm not using the default password per the latest security topic. I've tried multiple apt update/upgrades and reboots. Tried changing node_lookup_method from both to file and reverified my allstar registration but no change. Any suggestions?

[N2DYI]

My parrot node (55553) has the |x flag in it's radio-secure context, meaning it doesn't care if you are registered or not. Thus, even an unregistered node can connect. So, my first guess would be a registration issue.
from Asterisk CLI:

rpt show registrations

Does the node appear to be registered? Does the IP address it reports match your WAN IP?
Are you on a mobile hotspot?

[Brent_Dix]

[quote="N2DYI, post:2, topic:23447"]
Thanks for the insights Patrick. This is a fixed mobile hotspot, 'rpt show registrations' does show the status as registered and the 'percieved' WAN address is correct including the IAX port. My ISP is a T-mobile home gateway so I do have the double NAT issue but not planning to use incomming connections and was hoping to avoid having to go the VPN route. Is there a way to force a re-registration just to make sure there isn't something 'hidden' in the IP path that changed?

[N8EI]

T-Mobile is one of the known-problematic services. See IAX-Based Registration - AllStarLink Manual.

[Brent_Dix]

Thanks Jason, that did the trick!
Interesting that it worked for the last few weeks since I first set up the hotspot using HTTP registration. Not sure if it was the ASL update or something coincident that T-Mobile did but will continue to use IAX and hope it doesn't eventually get depricated like the file header warns.

[N8EI]

Just coincidence. Not the update.

IAX registration isn’t going anywhere for a long while. We need to redo the whole registration/authorization for a whole host of reasons. But that’s a long way off.