On Thu, Nov 14, 2024 at 3:39?PM Patrick Perdue via <borrisinabox=[email protected]> wrote:
Greetings:
For some reason, the reported address
is not correct using for node 48579.
resolves to
204.38.204.189. This works.
, which ASL
is using, resolves to 204.38.204.187, which doesn't.
Try the following:
Make sure the asl3-update-nodelist package is installed.
sudo apt update
sudo apt install asl3-update-nodelist
Then, in /etc/asterisk/rpt.conf, change the line
node_lookup_method = both??????????
;method used to lookup nodes
to
node_lookup_method = file ?????????
;method used to lookup nodes
and then restart Asterisk.
It seems like ASL's DNS sometimes
doesn't update when an IP address changes. I don't know why.
73
N2DYI
On 11/14/2024 11:41 AM, Michael Johnson
via wrote:
I'm not sure this is an appropriate issue for this group, but
I have to start somewhere.... redirect prod's are welcome.
?
I've got a SHARI node which has been stellar for the past
year.? I like to experiment and ended up messing up the Hamvoip
software a few months back so I plunged ahead with an ASL3
update.? That has been a satisfying experience and with one
exception, has been very successful.
?
The exception:? Since making the change to ASL3, I cannot
successfully connect to talk group #48579.? Every attempt
results in a Connection Failed message.? I communicated with the
node owner and he could find nothing on his end wrong on his end
and reported his linked repeater system is working like a
champ.? I have not tried reinstalling Hamvoip to see if that
would correct the situation, bad me.? So I am wondering how to
go about troubleshooting the problem.? Where to look for log
entries or what not.? I have no idea why the connection fails
repeatedly.
?
BTW, I don't really explore the ASL Node Network extensively,
but I have zero connection issues with any of my other dozen or
so favorite nodes.? Just #48579.??