Node fails to connect

I have had this Shari node running for several years with no issues, however, a couple of weeks ago, it started to fail to connect to nodes I have been using regularly. I does not matter which node on Hubnet I choose it fails. The node address is sent out of internet, appears to connect for a couple of seconds and drops out. I have run the Asterisk CLI client and attach the result showing the failure. Any help to explain or cure this help greatly.
73
Malcolm M0MCR

MobaXterm_192.168.1.96root_dial_process1.pdf (231.5 KB)

Not sure if this applies but here is a starting point based on a previous post:

Good luck!

Auto-congesting call due to slow response

looks like an internet issue

Hi, and thanks for the link. My situation is not quite the same, my system does connect to any outbound address sent, even when sent from my handheld as an inbound command although the hand held is connected fine… I shall check some the points they make but my router hardware is different.
Cheers

Hi, I have 2 x Pi-Star nodes one running DMR and one Fusion also here and online, as they have all been for past 3 years without any issue. The Shari has also been running for the same time with them, with no issues.

I have also turned off my router firewall and tested but no good, then stopped AVG Firewall also still Shari does not connect.

are you hard wired or over Wifi?

While you might not think it is possible,
please review this for it’s possibilities in your set-up…

https://wiki.allstarlink.org/wiki/Private_nodes#Numbering

All nodes are wifi connected.

Do you have privet nodes connected to your connecting node ?
ie 1999 1998 etc

Hi, No, I do not have any pivet or other nodes connected. Each of the three systems are simple mode setups.

What are the node numbers in question ?

The nodes trying to connect to, main address is 41689, also, 50681, and 50683.
cheers
Malcolm

I also now a completely new RPi and the latest version Hamvoip 1.7.01 insalld and running with the Shari VHF node, but I still ahve the same issue as before see Asterisk client log here:
Connected to Asterisk 1.4.23-pre.hamvoip-V1.7.1-04 app_rpt-0.327-01/22/2022 currently running on M0MCR (pid = 1131)
Verbosity is at least 4
[Sep 5 09:39:55] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char *
[Sep 5 09:39:56] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char 3
[Sep 5 09:39:56] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char 5
[Sep 5 09:39:57] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char 0
[Sep 5 09:39:57] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char 6
[Sep 5 09:39:57] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char 8
[Sep 5 09:39:58] NOTICE[1249]: chan_simpleusb.c:2725 simpleusb_read: Got DTMF char 1
– Call accepted by 45.143.120.78 (format ulaw)
– Format for call is ulaw
– Hungup ‘IAX2/45.143.120.78:4569-101’
– Hungup ‘DAHDI/pseudo-1377311244’
– Hungup ‘DAHDI/pseudo-834608549’
– Hungup ‘DAHDI/pseudo-334704346’
– <DAHDI/pseudo-454378295> Playing ‘rpt/node’ (language ‘en’)
– <DAHDI/pseudo-454378295> Playing ‘digits/5’ (language ‘en’)
– <DAHDI/pseudo-454378295> Playing ‘digits/0’ (language ‘en’)
– <DAHDI/pseudo-454378295> Playing ‘digits/6’ (language ‘en’)
– <DAHDI/pseudo-454378295> Playing ‘digits/8’ (language ‘en’)
– <DAHDI/pseudo-454378295> Playing ‘digits/1’ (language ‘en’)
– <DAHDI/pseudo-454378295> Playing ‘rpt/connection_failed’ (language ‘en’)
– Hungup ‘DAHDI/pseudo-454378295’

does this give us a new issue??

Malcolm

What node numbers are you trying to connect from ?

From my own single simplex node number 52044.

So, it looks like you converted 52044 to NNX (so, your simplex node is now 520440). Was the change to NNX recent? If so, did this issue you are having start when you converted?

Jim, K6JWN

https://wiki.allstarlink.org/wiki/NNX

However, you need to consult hamvoip usage of nnx for precise instruction.

I have now, after reading the section on NNX from the link you sent to me, reset my node back to the original 52044 with no extensions, this appears to have solved the problem, other than I still cannot connect to the original node 41689. I must have some other issue somewhere that is stopping my node from connecting to 41689, as the node is up and running in the Hubnet bubble diagram.

Many thanks for your help

When look at my node in the active node list, it says “Node configured incorrectly” or something similar. Any thoughts on what that might be, could it be related to my original issue??