Error connecting to other nodes

AllStarLink
1

Folks I get this error with I try to connect my Node 68192 to my friends nod 518582

Connected to Asterisk 22.7.0+asl3-3.7.1-1.deb13 currently running on WB8CQV-PI (pid = 66447)

WB8CQV-PI*CLI> rpt fun 68192 *3518582

[2026-02-09 10:35:42.801] NOTICE[66480]: chan_iax2.c:4830 __auto_congest: Auto-congesting call due to slow response

-- Hungup 'IAX2/74.136.155.221:4568-3225'

-- Hungup 'DAHDI/pseudo-163676563'

WB8CQV-PI*CLI>

I need some help to resolve this problem. My internet speed is typically 900MB when checked with speedtest. I have tried to connect to other nodes with similar errors.

Here is my ping results for Google

wb8cqv@WB8CQV-PI:~ $ ping google

PING google (142.250.191.142) 56(84) bytes of data.

64 bytes from ord38s29-in-f14.1e100.net (142.250.191.142): icmp_seq=8 ttl=118 time=18.8 ms

^C

--- google ping statistics ---

8 packets transmitted, 8 received, 0% packet loss, time 7011ms

rtt min/avg/max/mdev = 18.370/18.710/19.082/0.215 ms

wb8cqv@WB8CQV-PI:~ $

I have verified port these ports are forwarded to the proper internal IP addresses.

192.168.0.121 is my PI 4 with operating system Debian 13 loaded on computer and where Astreisk3 is running. I am currently NOT trying to run Echolink at this time and Echolink has yet to be loaded or configured.

John, WB8CQV

VOTE !!! It is a RIGHT and a OBLIGATION !!!

2

That almost always means your node isn't properly registered. If it is, then the other issue is something is blocking the networking between your node and the remote nodes.

I've added a new tool to the asl3 package that's currently in beta. If you're comfortable doing it, try installing the beta asl3 package:

sudo asl-repo-switch -l beta
sudo apt update
sudo apt install asl3
sudo asl-repo-switch -l main

That will give you a new tool I've been developing - asl-node-auth-check that will test your node's authentication, registration, and reachability. Here's an example:

# asl-node-auth-check

-----===== AllStarLink Node Authentication Check =====-----

Checking configuration:
      Info: rpt.conf has configuration for: 48496, 430780, 430781, 430782, 43078                                                             3, 430784, 430785, 63467
      Info: /etc/asterisk/iax.conf contains no registration lines.
      Info: /etc/asterisk/rpt_http_registrations.conf contains 8 registration li                                                             ne(s)
      Info: Registrations present for configured node(s): 48496, 430780, 430781,                                                              430782, 430783, 430784, 430785, 63467
      Info: IP from https://conntest-east1.allstarlink.org/ip reports: 3.138.188                                                             .232
      Info: IP from https://conntest-west1.allstarlink.org/ip reports: 3.138.188                                                             .232
      Info: IP from https://conntest-west2.allstarlink.org/ip reports: 3.138.188                                                             .232
      Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: 3.138.188                                                             .232
      Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 3.138.188                                                             .232
      Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 3.138.188                                                             .232
        OK: HTTP IP probes have consensus on the same perceived IP
        OK: IAX IP probes have consensus on the same perceived IP

Testing node 48496:
        OK: Node registration config is well-formed
        OK: Node registration type is HTTP
        OK: register.allstarlink.org is reachable (via HTTP)
        OK: HTTP registration state is Registered
        OK: Perceived IAX IP:PORT for this node is: 3.138.188.232:4569
        OK: Registered to aws-east1a-register2.allstarlink.org - 52.44.147.201
        OK: Server-set UDP port matches bindport in iax.conf
        OK: Node registration within 10 minutes: 2026-02-09 20:46:43 UTC
      Info: Last time IP changed was 2025-01-11 22:56:07 UTC
        OK: Incoming connections to IAX from other nodes is successful
      Info: IAX ping test has a roundtrip time of 11ms
        OK: No problems detected with node 48496
3

Jason:

I get this error when trying the scripts you provided for the update.

image
image841×444 113 KB

I get this error when trying to run:

Check the update node service

The asl3-update-nodelist service is NOT enabled.

I get this error when trying to run:

Restart the update node service

asl3-update-nodelist service restart failed (exit code │

      │ 5).                                                      │ 

      │

I suspect they are all related but I need some help in solving the problems.

John, WB8CQV

VOTE !!! It is a RIGHT and a OBLIGATION !!!

4

Is this an ASL3 appliance? Roundcube is a webmail server. That message is telling you the database isn't setup correctly for Roudncube. It's irrelevant to ASL3. Can't even guess how you got that.

Do you have the command asl-node-auth-check command available now?

5

Here is the result of asl-node-auth-check:

image
image906×633 198 KB

6

And here is the result of trying to connect to my friend node:

image
image1259×168 76.5 KB

I hope this gives you a little more insight.

John, WB8CQV

7

You node is fine, I just connected to it. Node 518582 is not responding to incoming IAX2 connections. So the problem is on the other end, not your end.

8

Jason:

Thanks for your help. I can connect to node 2198 FB.

Thanks once again for putting up with my "newbie" learning curve!

9

Hello I’m having the same issues with my node 67891.

I get this error no matter what node I try

-- Hungup 'DAHDI/pseudo-1602524781' [2026-02-13 16:40:42.255] NOTICE[205768]: chan_iax2.c:4830 __auto_congest: Auto-congesting call due to slow response -- Hungup 'IAX2/104.232.32.242:4569-16351' -- Hungup 'DAHDI/pseudo-138165559' -- Hungup 'DAHDI/pseudo-954800751'

Here is the result of the auth check

-----===== AllStarLink Node Authentication Check =====-----

Checking configuration:
Info: rpt.conf has configuration for: 67891
Info: /etc/asterisk/iax.conf contains no registration lines.
Info: /etc/asterisk/rpt_http_registrations.conf contains 1 registration line(s)
Info: Registrations present for configured node(s): 67891
Info: IP from https://conntest-east1.allstarlink.org/ip reports: 24.222.169.103
Info: IP from https://conntest-west1.allstarlink.org/ip reports: 24.222.169.103
Info: IP from https://conntest-west2.allstarlink.org/ip reports: 24.222.169.103
Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: 24.222.169.103
Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 24.222.169.103
Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 24.222.169.103
OK: HTTP IP probes have consensus on the same perceived IP
OK: IAX IP probes have consensus on the same perceived IP

Testing node 67891:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
OK: register.allstarlink.org is reachable (via HTTP)
OK: HTTP registration state is Registered
OK: Perceived IAX IP:PORT for this node is: 24.222.169.103:4569
OK: Registered to aws-east1a-register1.allstarlink.org - 52.21.169.197
OK: Server-set UDP port matches bindport in iax.conf
OK: Node registration within 10 minutes: 2026-02-13 23:42:33 UTC
Info: Last time IP changed was 2026-01-30 04:47:02 UTC
OK: Incoming connections to IAX from other nodes is successful
Info: IAX ping test has a roundtrip time of 106ms
OK: No problems detected with node 67891

And the ping results

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=43.1 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=42.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=42.1 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=40.6 ms
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 40.156/41.700/43.085/1.120 ms

Am I missing something?

Thanks

Sean VE6SAR

10

Most likely the issue is on the other end. What node are you trying to connect to?

11

I’m able to connect to 67891…

12

I tried several nodes earlier to today.

I’ll try a few more tomorrow

Thanks

13

Coming back to this, after a busy few months. I'm still having the "chan_iax2.c:4830 __auto_congest: Auto-congesting call due to slow response" error. I verified my port forwarding is setup. I tried several active nodes this afternoon.

Could this be my ISP filtering the UDP ports?

Thanks

14

Filtered ports, carrier-grade NAT, unregistered node... lots of reasons.

15

Since I already have a Tailnet setup, I am using a digital ocean server as my exit node now to avoid any ISP router interference.

asl-check-install

=====================================================================

II Gathering asl-show-version information

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

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-52-amd64

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

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.9.1-1.deb12
asl3 3.18.2-2.deb12
asl3-asterisk 2:22.9.0+asl3-3.9.3-1.deb12
asl3-asterisk-config 2:22.9.0+asl3-3.9.3-1.deb12
asl3-asterisk-modules 2:22.9.0+asl3-3.9.3-1.deb12
asl3-menu 1.18-1.deb12
asl3-tts 1.0.1-1.deb12
asl3-update-nodelist 2.0.0-1.deb12
asl-apt-repos 2.0-1.deb12
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-11.asl.deb12
dahdi-linux 1:3.4.0-11.asl.deb12
dahdi-source 1:3.4.0-11.asl.deb12

=====================================================================

II There are no errors in /var/log/asterisk/messages

NN The above can be pasted into a forum post or a GitHub issue

asl-node-auth-check

-----===== AllStarLink Node Authentication Check =====-----

Checking configuration:
Info: rpt.conf has configuration for: 678910, 678911
Info: /etc/asterisk/iax.conf contains no registration lines.
Info: /etc/asterisk/rpt_http_registrations.conf contains 2 registration line(s)
Info: Registrations present for configured node(s): 678910, 678911
Info: IP from https://conntest-east1.allstarlink.org/ip reports: 159.89.127.188
Info: IP from https://conntest-west1.allstarlink.org/ip reports: 159.89.127.188
Info: IP from https://conntest-west2.allstarlink.org/ip reports: 159.89.127.188
Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: 159.89.127.188
Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 159.89.127.188
Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 159.89.127.188
OK: HTTP IP probes have consensus on the same perceived IP
OK: IAX IP probes have consensus on the same perceived IP

Testing node 678910:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
OK: register.allstarlink.org is reachable (via HTTP)
OK: HTTP registration state is Registered
OK: Perceived IAX IP:PORT for this node is: 159.89.127.188:4569
OK: Registered to aws-east1a-register1.allstarlink.org - 52.21.169.197
OK: Server-set UDP port matches bindport in iax.conf
OK: Node registration within 10 minutes: 2026-09-08 22:58:11 UTC
Info: Last time IP changed was 2026-08-21 23:18:27 UTC
Warning: Node is not perceived as registered; not tested

Warning: Node 678910 has 1 warning(s)!
Warning: Warnings may or may not be problems depending on configuration

Testing node 678911:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
OK: register.allstarlink.org is reachable (via HTTP)
OK: HTTP registration state is Registered
OK: Perceived IAX IP:PORT for this node is: 159.89.127.188:4569
OK: Registered to aws-east1a-register1.allstarlink.org - 52.21.169.197
OK: Server-set UDP port matches bindport in iax.conf
OK: Node registration within 10 minutes: 2026-09-08 22:58:06 UTC
Info: Last time IP changed was 2026-09-08 22:18:52 UTC
Warning: Node is not perceived as registered; not tested

Warning: Node 678911 has 1 warning(s)!
Warning: Warnings may or may not be problems depending on configuration

When I try to make a call to 55553 I get this

va6shs-r*CLI> rpt fun 678910 *355553
-- Channel Announcer/IAXLink-0000003f;2 joined 'softmix' base-bridge
-- Channel Announcer/Telemetry-00000040;2 joined 'softmix' base-bridge <02b8a3d9-ed83-4f3f-9fc4-ca48523558cb>
-- Channel Announcer/Telemetry-00000040;2 left 'softmix' base-bridge <02b8a3d9-ed83-4f3f-9fc4-ca48523558cb>
[2026-09-08 17:01:48.339] NOTICE[871]: chan_iax2.c:4830 __auto_congest: Auto-congesting call due to slow response

[2026-09-08 17:02:16.340] WARNING[869]: chan_iax2.c:3645 __attempt_transmit: Max retries exceeded to host 104.232.32.242 on IAX2/104.232.32.242:4569-9916 (type = 6, subclass = 1, ts=3, seqno=0)
-- Hungup 'IAX2/104.232.32.242:4569-9916'

16

I would double check your port forwarding. While it does appear you're going out of your exit node; it doesn't seem to be able to make the incoming connection back in to your node through the exit node:

> Warning: Node is not perceived as registered; not tested
> 
> Warning: Node 678910 has 1 warning(s)!
> Warning: Warnings may or may not be problems depending on configuration

Compare that with my tunneled (and dockerized) node's output:

-----===== AllStarLink Node Authentication Check =====-----

Checking configuration:
      Info: rpt.conf has configuration for: 594080
      Info: /etc/asterisk/iax.conf contains no registration lines.
      Info: /etc/asterisk/rpt_http_registrations.conf contains 1 registration line(s)
      Info: Registrations present for configured node(s): 594080
      Info: IP from https://conntest-east1.allstarlink.org/ip reports: 144.172.124.240
      Info: IP from https://conntest-west1.allstarlink.org/ip reports: 144.172.124.240
      Info: IP from https://conntest-west2.allstarlink.org/ip reports: 144.172.124.240
      Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: 144.172.124.240
      Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 144.172.124.240
      Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 144.172.124.240
        OK: HTTP IP probes have consensus on the same perceived IP
        OK: IAX IP probes have consensus on the same perceived IP

Testing node 594080:
        OK: Node registration config is well-formed
        OK: Node registration type is HTTP
        OK: register.allstarlink.org is reachable (via HTTP)
        OK: HTTP registration state is Registered
        OK: Perceived IAX IP:PORT for this node is: 144.172.124.240:4568
        OK: Registered to aws-east1a-register1.allstarlink.org - 52.21.169.197
        OK: Server-set UDP port matches bindport in iax.conf
        OK: Node registration within 10 minutes: 2026-09-09 21:40:02 UTC
      Info: Last time IP changed was 2026-09-03 00:51:52 UTC
        OK: Incoming connections to IAX from other nodes is successful
      Info: IAX ping test has a roundtrip time of 21ms
        OK: No problems detected with node 594080

Those last three lines are the important ones. I would check the rules on your digital ocean vps to ensure it's sending port 4569 over your VPN:

iptables -t nat -A PREROUTING -p udp --dport 4569 -j DNAT --to-destination node-ip:4569
iptables -A FORWARD -p udp -d <node-ip> --dport 4569 -j ACCEPT

But I don't think that'll actually fix the problem you're having. You were directly connectable on the results you printed in February; so your ISP wasn't blocking ports.

Did you ever try any other nodes? I would make sure it's happening on every node you try before digging deeper. One node not working could be a problem with the remote node.

17

Thanks for the reply

I just tried with several nodes this evening with the same result.

I disabled the firewall on the machine for testing, no change.

I switched back to using the local router instead of the tailnet, no change.

I'm not sure where else to go