ASL3 connection issue

App_rpt-users
1

I have an ASL3 on Pi3B+ that is fine in all respects except the following issue:

  1. all inbound connections are successful,
  2. outbound connections fail except on node numbers in the 2xxx range.

Any ideas??

2

Version of the software ?

asterisk -rvvv
cli> core show version

Likely you need update to the latest version.

3

Itā€™s current:
Asterisk 20.9.1+asl3-3.0.4-1.deb12, Copyright (C) 1999 - 2022, Sangoma Technologies Corporation and others.
Created by Mark Spencer markster@digium.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ā€˜core show warrantyā€™ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ā€˜core show licenseā€™ for details.

Connected to Asterisk 20.9.1+asl3-3.0.4-1.deb12 currently running on portable (pid = 1671)

4

Asterisk 20.9.1+asl3-3.0.4-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2024-07-29 20:34:10 UTC

I also get the same behavior on Pi4 .

5

We are adding a new asl-node-lookup command to the release. Itā€™s currently in the beta channel but should be moved to the production channel soon. Details are available @ 20240816 - Package Updates - Beta Channel.

In this case, and given that the content in the beta channel content is currently minimal, I would suggest/ask that you :

  • enable the beta channel software
  • apt update/upgrade to install the updated ASL3 and ASL3-Pi-Appliance packages
  • disable the beta channel software (to keep any ā€œnewā€ beta updates from being installed unless/until you are ready)
  • exec the new asl-node-lookup command with a few node #'s.
sudo asl-node-lookup <node-number>

Then, repeat the same commands but specify an alternate DNS server.

sudo asl-node-lookup --ns 8.8.8.8 <node-number>
6

@Tom - What is the output of rpt lookup 2000 on your node?

7

asl-node-lookup 2000

SRV (_iax._udp.2000.nodes.allstarlink.org)
11 10 4569 2000.nodes.allstarlink.org.

A (2000.nodes.allstarlink.org)
162.248.93.134

TXT (2000.nodes.allstarlink.org)
NN=2000
RT=2024-08-23 23:27:53
RB=0
IP=162.248.93.134
PIP=0
PT=4569
RH=register-west

RPT LOOKUP (2000)
radio@162.248.93.134:4569/2000,162.248.93.134

asl-node-lookup --ns 8.8.8.8 2000

SRV (_iax._udp.2000.nodes.allstarlink.org)
11 10 4569 2000.nodes.allstarlink.org.

A (2000.nodes.allstarlink.org)
162.248.93.134

TXT (2000.nodes.allstarlink.org)
NN=2000
RT=2024-08-23 23:27:53
RB=0
IP=162.248.93.134
PIP=0
PT=4569
RH=register-west

RPT LOOKUP (2000)
radio@162.248.93.134:4569/2000,162.248.93.134

8

I see no difference in the two responses.

If I want to turn off beta mode, what is the command?

9

If I want to turn off beta mode, what is the command?

sudo asl-repo-switch -r
sudo apt update

I see no difference in the two responses.

Didnā€™t you write that you had no issues with 2xxx nodes? If you are having issues with longer (5-digit, 6-digit) node numbers then try repeating the asl-node-lookup commands with the the node numbers you are having issues.

The key responses are the ā€œSRVā€ record, the ā€œAā€ record, and the ā€œRPT LOOKUPā€.

10

Here is node lookup for 42610:

asl-node-lookup 42610

SRV (_iax._udp.42610.nodes.allstarlink.org)
11 10 4569 42610.nodes.allstarlink.org.

A (42610.nodes.allstarlink.org)
50.43.65.82

TXT (42610.nodes.allstarlink.org)
NN=42610
RT=2024-08-23 23:28:50
RB=0
IP=50.43.65.82
PIP=0
PT=4569
RH=register-west

RPT LOOKUP (42610)
radio@50.43.65.82:4569/42610,50.43.65.82

asl-node-lookup --ns 8.8.8.8 42610

SRV (_iax._udp.42610.nodes.allstarlink.org)
11 10 4569 42610.nodes.allstarlink.org.

A (42610.nodes.allstarlink.org)
50.43.65.82

TXT (42610.nodes.allstarlink.org)
NN=42610
RT=2024-08-23 23:28:50
RB=0
IP=50.43.65.82
PIP=0
PT=4569
RH=register-west

RPT LOOKUP (42610)
radio@50.43.65.82:4569/42610,50.43.65.82

11

I again, see no difference.

12

'Canā€™t connect TO 42610; but can be connected FROM 42610.

1 Like
13

Well, it looks like your node can pickup the information needed to connect to the remote nodes.

Good that your incoming connections are working.

As for your outgoing connections, this feels like a networking issue. Are you using any type of VPN? or might you have an outgoing firewall blocking (or redirecting) your traffic?

14

My ASL2 nodes on the same LAN donā€™t have this problem.

15

I just started having the same problem myself with ASL3 and Rpi4. It was working ok yesterday.

16

I just started tcpdump looking at traffic to the gateway (192.168.0.1):
tcpdump -n host 192.168.0.1

When I try to connect to 42610, I see this:
23:54:50.721009 IP 192.168.0.80.51459 > 192.168.0.1.53: 18906+ SRV? _iax._udp.4261.nodes.allstarlink.org. (54)

'Looks like the node 42610 is truncated to just 4 digits. Node 2000, of course is no problem. Perhaps this was broken in a recent ā€œupdateā€.

17

ASL will start looking for node information as soon as youā€™ve entered 4 digits. But, you should see additional queries as you enter more digits.

The recent ASL3-Asterisk 20.9.1+asl3-3.0.4-1 update included :

  • app_rpt: Correct 5 digit node lookup from 4 digit node pr #372
    [/quote]

Q? is it possible that you did not restart your node after it was last updated to v3.0.4 and that the ā€œasteriskā€ process is still running an earlier version?

Note: the recently added Node Resolution - AllStarLink Manual page may be of interest.

18

I wonder if this is related to my issue with DTMF strings longer that six characters? I can also join 4 char nodes, but 5 character and longer fail. Are you seeing anything in /var/log/asterisk/messages? "Exceptionally long voice queue length" during DTMF

Sounds like the same symptoms. I can link nodes with Allmon3 no matter the length, Iā€™m betting the node lookup tool will all work. Itā€™s only when using DTMF longer than 6 chars. Thatā€™s when the queue backs up on the channel the DTMF came in on.

19

As I noted in the case I created, the asl-node-lookup command is successful and matches with google DNS or my ISP DNS. Perhaps something with pr #372 is hanging the channel after the 4th digit of the node? It looks like itā€™s only link and unlink, wait just link, commands that hang at 6 chars. The disconnect/unlink/*1 command is working as expected on node numbers longer than 4 chars. I can enter *722722722 and it will ā€˜hearā€™ all the characters. Updating my other case with more detail.

20

outbound connections are fine from Allmon3. Here is a connection to 42610:

from asterisk CLI:

-- Call accepted by 50.43.65.82:4569 (format ulaw)
-- Format for call is (ulaw)

from TCP dump:

09:47:02.677585 IP 192.168.0.80.45272 > 192.168.0.1.53: 47916+ SRV? _iax._udp.42610.nodes.allstarlink.org. (55)
09:47:02.741800 IP 192.168.0.1.53 > 192.168.0.80.45272: 47916 1/0/0 SRV 42610.nodes.allstarlink.org.:4569 11 10 (102)
09:47:02.742297 IP 192.168.0.80.38929 > 192.168.0.1.53: 27212+ A? 42610.nodes.allstarlink.org. (45)
09:47:02.791083 IP 192.168.0.1.53 > 192.168.0.80.38929: 27212 1/0/0 A 50.43.65.82 (61)
09:47:02.891124 IP 192.168.0.80.43180 > 192.168.0.1.53: 4493+ A? stats.allstarlink.org. (39)
09:47:02.891952 IP 192.168.0.1.53 > 192.168.0.80.43180: 4493 2/0/0 CNAME stats-west.allstarlink.org., A 34.105.111.212 (95)

I see from some previous dialogs that there is a line needed in rpt.conf. Iā€™ve added that with no change. The problem isnā€™t a network issue. It is ASL3 not properly handling DTMF or ā€œrpt fun 41886 *342610ā€.

added to rpt.comf:

max_dns_node_length = 6

was already in rpt.comf:

node_lookup_method = both

K5TRA