********** AllStarLink [ASL] Version Info **********
OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.12.25+rpt-rpi-v8
Asterisk : 22.2.0+asl3-3.4.5-1.deb12
ASL [app_rpt] : 3.4.5
Installed ASL packages :
Package Version
============================== ==============================
allmon3 1.4.2-1.deb12
asl3 3.7.1-1.deb
asl3-asterisk 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-config 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-dbgsym 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-dev 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-doc 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-modules 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-modules-dbgsym 2:22.2.0+asl3-3.4.5-1.deb12
asl3-asterisk-tests 2:22.2.0+asl3-3.4.5-1.deb12
asl3-menu 1.13-1.deb12
asl3-pi-appliance 1.10.0-1.deb12
asl3-tts 1.0.1-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-pcp 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
Ok I'm getting the following when an external ASL3 node is attempting to connect to me
[2025-06-16 21:45:56.782] WARNING[1773]: chan_iax2.c:10442 socket_process_helper: Silently dropping frame without existent call number: 6617
So I understand that the call is being dropped, but what I don't understand is why! this node has been connected to me for months and just this weekend past it has stopped being able to connect. the node trying to connect to me is 63103 and my node is 62040.
So I have two node here, 51515 & 62040 and they both have unique ports and port forwarding rules in my mikrotik router. So as stated 63103 can't connect to 62040 but it can connect to 51515. I've not touched the config for either of my nodes in months! and it's the same for the 63103 node it hasn't had anything changed either.
So I'm just a tad stuck as to why its all of a sudden not connecting...