Startup Macro cannot handle NNX nodes

AllStarLink
,
1

When I add a startup macro to my private numbered node, permanently linking it to my NNX numbering plan node, it fails, and when looking at asterisk, it seems to be dropping the last digit and can’t locate that node because it doesn’t exist.

Use sudo asl-show-version to obtain this information from the console or SSH

root@chucktaylor:~# asl-show-version
********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-40-amd64

Asterisk : 22.5.2+asl3-3.6.2-1.deb12
ASL [app_rpt] : 3.6.2

Installed ASL packages :

Package Version
============================== ==============================
asl3 3.11-1.deb12
asl3-asterisk 2:22.5.2+asl3-3.6.2-1.deb12
asl3-asterisk-config 2:22.5.2+asl3-3.6.2-1.deb12
asl3-asterisk-modules 2:22.5.2+asl3-3.6.2-1.deb12
asl3-menu 1.15-1.deb12
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-10.asl.deb12
dahdi-linux 1:3.4.0-10.asl.deb12
dahdi-source 1:3.4.0-10.asl.deb12

Inquiry

See https://allstarlink.github.io/user-guide/troubleshooting/ on how to ask a good question to obtain the quickest and best assistance

2

Is this a "new" NNX node number? If so, you may be affected by ASL3 Manual : Issues with connections to "new" NNX Nodes.

What is the node number you are trying to connect to?

3

So I actually had read that before posting kinda came to the determination it wouldn’t impact me since both my nodes were local to each other (same asterisk session).

4

Is there a preferred way to hard code these entries somewhere other than an authoritative NS locally and forwarding everything else?

5

Nodes on the same network have a special configuration.

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.