# OK: Unknown node number (MYNODENO.) **URL:** \ **Category:** Archive\ **Tags:** allmon3, asl3\ **Created:** [September 26, 2024, 5:20am UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937 "2024-09-26T05:20:36Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Patiwat\_Inpleang](https://community.allstarlink.org/user_avatar/community.allstarlink.org/patiwat_inpleang/32/3142_2.png) [@Patiwat\_Inpleang](https://community.allstarlink.org/u/Patiwat_Inpleang)\ **Post date:** [September 26, 2024, 5:20am UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/1 "2024-09-26T05:20:36Z")
Hi sir. how to fix when conect to other node show eror …OK: Unknown node number (MYNODENO.) thank you .//AllStarLink allmon 3 ver 1.3.4 on Cloud ![1727183820643 (1)](https://community.allstarlink.org/uploads/default/original/2X/b/bf65edc16541984ce63c0f9bf9db4649a51daf77.jpeg) ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 26, 2024, 12:25pm UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/2 "2024-09-26T12:25:28Z")
That error is stating node 620570 on the underlying ASL host you’re connecting to isn’t properly configured. If you connect to ASL directly and do `rpt cmd 620570 ilink 3 57855` does it work? ---
**Author:** ![Patiwat\_Inpleang](https://community.allstarlink.org/user_avatar/community.allstarlink.org/patiwat_inpleang/32/3142_2.png) [@Patiwat\_Inpleang](https://community.allstarlink.org/u/Patiwat_Inpleang)\ **Post date:** [September 26, 2024, 9:28pm UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/3 "2024-09-26T21:28:03Z")
Unknown node number 620570. ![1727386050090](https://community.allstarlink.org/uploads/default/original/2X/8/8a668daa13e86feb2aee1a5e047c502995cfa4b6.jpeg) ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [September 26, 2024, 10:20pm UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/4 "2024-09-26T22:20:42Z")
This is showing the node you are attempting to connect to does not exist. But with a look The node 57855 is ‘not registered’ and can do nothing on the network connection-wise. When it is registered again, it will be connectable. ---
**Author:** ![KD3CSR](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/e8c25b/32.png) [@KD3CSR](https://community.allstarlink.org/u/KD3CSR)\ **Post date:** [September 5, 2025, 6:36am UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/5 "2025-09-05T06:36:26Z")
Hi! Im also having the same issue. I have created a debian 13 virtual machine with asl3 and after adding a node and setting up zoiper, I also have unknown node number issue. The node is registered and I tried adding a private node 1999 to connect the two as well but I got unknown for both nodes 62919 and 1999. ![image](https://community.allstarlink.org/uploads/default/original/2X/6/60b8ffd2d181409baa3b21f10ed738b0a7f1c1a9.png) asterisk CLI shows this ![image](https://community.allstarlink.org/uploads/default/original/2X/e/e71beeca22b95a4e69d9c3919a5d0d7369c6fa72.png) When I try connecting from zoiper I get this in asterisk CLI ![image](https://community.allstarlink.org/uploads/default/original/2X/a/a5d9026ced1c7d78e92fe65d5f7434729c3d9517.png) rpt lookup 62919 shows up correct ![image](https://community.allstarlink.org/uploads/default/original/2X/e/e85e8dc328b4e090324dc9b3bab10d7d772c147c.png) Any idea what I could be missing here? I have removed the node and rebooted, re-added but issue persists. I also added node 62702 and got the same issue. I was going to open a new topic but found this thread so I thought it could be related. Let me know if a new topic would be better. Port 4569 is forwarded internally, so zoiper should be able to connect via iax. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 5, 2025, 1:47pm UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/6 "2025-09-05T13:47:23Z")
Look at `/var/log/asterisk/messages` at startup time to see if there are errors. The most likely issue is you don't have a functioning DAHDI kernel module set. ---
**Author:** ![KD3CSR](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/e8c25b/32.png) [@KD3CSR](https://community.allstarlink.org/u/KD3CSR)\ **Post date:** [September 9, 2025, 4:35am UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/7 "2025-09-09T04:35:19Z")
That was it. I made a new VM with Debian 12 instead as I was facing the same issue constantly on Debian 13. Even reinstalling dahdi didn’t work. Thank you! ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 9, 2025, 2:13pm UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/8 "2025-09-09T14:13:26Z")
Debian 13 is not yet supported by ASL as I mentioned in the package announcements. Unless you're prepared to do some extra legwork to troubleshoot problems, stick with Bookworm. ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [September 9, 2025, 6:28pm UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/9 "2025-09-09T18:28:39Z")
I had this same issue on a recent Intel VM. But in my case, I was already on Debian 12 bookworm. The solution was to see exactly what kernel module dahdi had installed and then to make my kernel match that version. `root@racknerd-XYZ:/lib/modules# find . -iname "*dah*"` `./6.1.0-38-amd64/updates/dkms/dahdi.ko` `./6.1.0-38-amd64/updates/dkms/dahdi_dummy.ko` `./6.1.0-38-amd64/updates/dkms/dahdi_transcode.ko` `uname -r` `6.1.0-9-amd64` `uname -a` `Linux racknerd-XYZ 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux` You see the mismatch here? I have no idea how that happened but it’s easy enough to fix it. To fix it, I did this: `apt install linux-image-6.1.0-38-cloud-amd64` `apt install linux-headers-6.1.0-38-cloud-amd64` Once done (plus a reboot of course), I had a working system. I also found that allmon3 seemed basically “unconfigured”, but that was easy, just edit asterisk’s manager.conf and get it matching with allmon3’s configuration. –E de W6EL ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 10, 2025, 1:43am UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/10 "2025-09-10T01:43:28Z")
This is what `asl-check-install` does for you automatically. ---
**Author:** ![KD3CSR](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/e8c25b/32.png) [@KD3CSR](https://community.allstarlink.org/u/KD3CSR)\ **Post date:** [September 10, 2025, 6:02am UTC](https://community.allstarlink.org/t/ok-unknown-node-number-mynodeno/21937/11 "2025-09-10T06:02:46Z")
I just faced the issue mentioned by @W6EL with a Debian 12 VPS cloud and running `asl-check-install` after ASL3 installation fixed everything. Didn’t know it existed. Will be running it after every install going forward. Thanks a ton!