Can not connect to ASL3 node

App_rpt-users
1

I have a new ASL3 node on a shari pihat. it connects out but I can not connect into it. I have only one node here at home. I have tried all of the suggestions in the forums. I am at my wits end as of right now. The node I am trying to connect into is 504371.
I will gladly provide any information needed. I have attempted so much it will be a book to write it out.
Thanks in advance.
Phil
KK4FWU

2

What IAX Port number are you going with? Is it the default 4569 ?

3

What are the node number for both?
Are they both on different servers behind the same router ?
Or are the on the same server?

Different servers behind the same NAt require you do specify the exact address of each node inside that NAT in the local network in [nodes] in rpt.conf.

A internal (local server) is described as 127.0.0.1 but a node on the other server inside your NAT needs the local IP. and port.
ie 192.168.1.100:2370

4

Hi! @Mike 's link is great to understand how to have two nodes behind same network.

However if this is a standalone node on a separate network then I too faced an issue with one of my nodes on a separate ISP connection where it could connect to nodes and showed up online on allstar website but no one could connect to it.

It turned out to be port forwarding issue from ISP side, so node had internet access and could reach other nodes but couldn't be connected from outside due to ports not being forwarded from the ISP. Once connected it worked as expected i.e. I could rx and tx flawlessly.

The ISP is still the same there and what I have done to work around the issue is I added an autoconnect cronjob that I found here in the forums so it automatically connects to my other nodes.

I need it connected all the time so the cron script is great for me as it checks every few minutes whether it is still connected and if not it attempts reconnection. If you require it to always be connected you could set it up as well.

#!/bin/bash
date >> /home/whatever-folder-you-want-to-keep-log'in/cron_check.txt
CHK=
echo “Checking whether node connected to main node”

/sudo/sbin/asterisk -rx >> "rpt nodes nodenumber" | grep -c othernode
echo $CHK >> /home/whatever-folder-you-want-to-keep-log'in/cron_check.txt

if [ $CHK -eq 1 ]
then
echo “OK, Connected.”
echo “OK, connected.” >> /home/whatever-folder-you-want-to-keep-log'in/cron_check.txt
else
echo “Reconnecting yournode to othernode.”
echo “Reconnecting.” >> ~/cron_check.txt
/usr/sbin/asterisk -rx “rpt cmd yournode ilink 3 othernode”
fi
exit

Save it as nodeconnect.sh and make it executable by chmod +x and add it to sudo crontab -e

You can use https://crontab.guru/ to get the code for the required frequency

If this is what you needed then do let me know if you face any hurdles with it

5

There are a lot of things that could be at issue here, but lets start with the stupid stuff.
Here is a common list I made you can look at.
The 5 most popular reasons for connection failure

Now, one thing that stands out as a possibility that should be eliminated is loopback protection. Public or private node(s).

If your node A is connected to node (any#) and your other node B is connected to the same, you will not be able to connect the 2 nodes of yours ( A & B ) together.

But it might help to watch asterisk commands in the foreground to see if the connection attempts are reporting.

asterisk -rvvv
1 Like
6

Make sure your port is set correctly and forwarded UDP on that port to that device. according to allstar your on 4570. so make sure in your router you have 4570 forwarded UDP for that local IP your device is on