Node Connection Failed (for no reason)

AllStarLink
1

I am trying to connect back to a node that I know the lookup is correct and the node is online and should be connectable.
But I only get connection failed.
I have the asterisk console up with full verbosity and no information is given for the "connection failed".
I am certain the node is there and should be connectable.
How do I go about getting the actual reason it is not connecting?
This is an ongoing problem and it seems that when he reboots on his end it gets resolved but then the problem keeps coming back periodically.
Nothing is changing network-wise and he is always available at the same IP and port.
From my end it looks as if he is simply rejecting the connection. (Hungup)
My own lookup is also valid and nothing about mine changes either.


rpt lookup 622140
Node: 2586       Data: radio@24.8.205.76:4569/622140,24.8.205.76
  
    -- Hungup 'DAHDI/pseudo-135176850'
    -- Hungup 'IAX2/24.8.205.76:4569-8341'
    -- Hungup 'DAHDI/pseudo-1101514458'
    -- <DAHDI/pseudo-783988577> Playing 'custom/rpt/node.gsm' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/digits/6.ulaw' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/digits/2.ulaw' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/digits/2.ulaw' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/digits/1.ulaw' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/digits/4.ulaw' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/digits/0.ulaw' (language 'en')
    -- <DAHDI/pseudo-783988577> Playing 'custom/rpt/connection_failed.gsm' (language 'en')
    -- Hungup 'DAHDI/pseudo-783988577'
2

The 5 most popular reasons for connection failure

3

I just tried connecting to that node, and got:

aslCLI> rpt cmd 506318 ilink 3 622140
[2025-06-01 05:25:03.638] NOTICE[1219]: chan_iax2.c:4820 __auto_congest: Auto-congesting call due to slow response
-- Hungup 'IAX2/24.8.205.76:4569-11496'
-- Hungup 'DAHDI/pseudo-825770655'
aslCLI>

So the server never gets the call. Tried from two different nodes.
I didn't check to see when the node was last seen. The node is either down/not registered, or there's a firewall problem, at least in this case.

Do you happen to know if the remote node you are connecting to is ASL or HamVoIP?

4

It's ASL3 (up to date) both sides. Myself and the node I am attempting connection to.
And working fine (at the moment).
Also I did not get the Auto-congesting call due to slow response that you show in yours.
But I was using rpt fun and the DTMF command versus what you did.
I'll try that next time it is in "failure mode" and see if I get any difference in response on the attempt.
Thanks.

5

" The 5 most popular reasons for connection failure](https://community.allstarlink.org/t/the-5-most-popular-reasons-for-connection-failure"

Am familiar with these and verified all were good (as I normally would) before posting here.
I am particularly interested in the seeming lack of reporting why when it fails.
Or my unfamiliarity of where to look.
With max verbosity set on the asterisk console (-rvvvvvvv) I am expecting to see a little more info than this.
Will keep at it and report back when I have more info.

6

It normally does not take more than a verbose of 3 to see an connection issue in IAX, but that does depend on the nature of it.
Registered is
2586=radio@108.239.105.244:4473/2586,108.239.105.244,y

That Y is denoting a remote base.
That only allows for one connection.
If it has one, no other connections are possible.

Try changing it to a N or no or none and test again.

7

I didn't know about the "y"
Also I am not having any kind of issues on my end with multiple connections ever.
This looks like it's pointing to my node with the "y".
I am having issues connection the the specific friend not shown in the line with the "y".
And I have never had any issues with multiple connections in or out on my end.
When having the issue described this was connection out to my friend.
Seems to get fixed if he reboots.
Also I'm slow to follow up on this post as my freind is away for several weeks and not able to work on this until he gets back.
I think he has just been remotely rebooting it for now.

8

This is maddening.
Now I cannot connect in from one of my other nodes with "connection failed".
And as always displayed "for no reason".
I very much know what I'm doing on the networking end and in general know what I'm doing with the entire Allstarlink system.
Didn't notice this problem so much until lately.
I'm out of time and need to mess with this more later.
Thanks.

9

Steve, it really sounds like more than one issue, but,
when you speak without specifics, you are not adding to troubleshooting info anyone can work with.

Nobody is going to write a book on all possibilities in a post. But I did give you one I use over and over.
I or anyone else can give you ideas, but you ultimately have to test them, report results.

10

I don't know if this will help but you may get some additional insights by cranking up the chan_iax debug level (on both the calling and called node).

core set debug 1 chan_iax2.so

and if level "1" doesn't give you enough info then you can also try level "2" or "3".

11

Thanks.
I will dig in more when he gets back.

12

Thanks for this tip!