Allmon3 - Not connecting

Interesting item, the password in the manager.conf match what is in ASL webpage

but when I attempt to connect to another node I get this error

It says command successful, but at the bottom it says this:

Unknown node number 620306

I cannot connect from another node to this one or the other way.

I have the port set correct on the firewall and 5038 is open on the local network only.

What am I missing? I have this setup on an HP Thin Client with Debian 12 and ASL3 (Updated with all the new updates).

Thank you

It means your local node is configured incorrectly. The app_rpt module is not running a repeater for node 620306.

Interesting, I returned the files back to original, made sure the nodes were deleted and restarted asterisk, then configured the main node again, but still the same issue. Compared several files with a working node, basically the same except the node number and the password.

I checked the modules.conf there is load app_rpt.so is there.

What else would you suggest? Thank you

Q? are you using asl-menu to make the changes to your nodes configuration? or editing the configuration file by hand with an editor?

The node password is case sensitive. Can we assume that you’ve checked to ensure that you are using the correct upper/lower case letters? and that you haven’t mixed up the o’s, O’s, and 0’s?

You mention comparing the configuration files of your new node with those of a working node. Can we assume that the working node is also an ASL3 node?

Have you looked at the /var/log/asterisk/messages.log file for clues?

do you have the port forwarded for 620306? as I can not connect to it.

Can you say a little more about both nodes. The Connectee and connector.

Are they behind the same NAT ? are they in the same server ?.
What are both node numbers.

Is var/lib/asterisk/rpt_extnodes of recent date/time on both if on other servers and yours.

Did you set-up NNX properly ? you should look it over again.

That message is misleading in this context. It means that the command was successfully executed not that whatever the command did what you expected it to. There’s no reasonable way to assess each command execution for “did what you expected it to” which is why the output from AMI is directly and fully displayed. You’d see the same thing if you ran that from the Asterisk CLI.