ALLMON3 Not connecting to other nodes

Allmon
21

He deleted 62717 (+ the two expanded NNX node numbers 627170/627171). New node # 65457 was issued.

22

65457 = radio@127.0.0.1/65457,NONE

65457=radio@69.195.16.68:4569/65457,69.195.16.68,y
This node is registered. Not the other.

This is the registered internal node in your file.
I don't know why you allmon3 is showing some other node as I don't use allmon3.
Not sure where it is extracting that info.

Is it logging into the correct system ?
Perhaps check ip address if you have/had a 2nd system ? or reconfig allmon.

Try a connect from the asterisk cli> or dtmf, it should work.

23

Screenshot_1
Screenshot_11617×720 36.6 KB

All Mon is showing the correct node number now and not allowing connections still.

What can I use in place of Allmon3?

24

At time of posting, I could not connect to 65457 as well.

Perhaps post your extensions.conf for some extra eyes

25

Folks..... this is not an Allmon3 issue, it's not a registration issue, and it's not an extension issue. The system is not starting up an app_rpt for node 65457. That error is just showing the response that you'd get from the Asterisk CLI if you ran the same command there.

The core issue is that app_rpt doesn't think 65457 exists. Since that's the case and this is a pseudo/dahdi type node according to rpt.conf then that means that something with the install is messed up and, most likely, the DAHDI kernel modules are not loaded.

@w6ehy please do the following:

  1. Look at /var/log/asterisk/messages.log and see if there are errors about unable to attach to a pseudo channel.

  2. Run the following commands IN THIS ORDER AS ROOT (i.e., sudo -s):

    apt install --reinstall kernel-headers-$(uname -r)
apt install --reinstall dahdi-dkms
modprobe dahdi
modprobe dahdi_dummy
modprobe dahdi_transcode
systemctl restart asterisk

  3. Then, still from the console:

    asterisk -rvvvvv
rpt show registrations

The second command will run inside the asterisk CLI. Please provide all screen output.

26

Also, is the the ASL3 Pi Appliance or a self-install on Debian 12?

27

This is a Debian Self Install.

on a Proxmox Container Hosted inside my LAN

root@AllStarCT:~# sudo -s apt install --reinstall kernel-headers-$(uname -r)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package kernel-headers-6.8.12-8-pve
E: Couldn't find any package by glob 'kernel-headers-6.8.12-8-pve'
root@AllStarCT:~# sudo -s apt install --reinstall dahdi-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
iptables libip6tc2 libnetfilter-conntrack3 libnfnetlink0
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 66 not upgraded.
Need to get 0 B/1219 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 48286 files and directories currently installed.)
Preparing to unpack .../dahdi-dkms_1%3a3.4.0-6+asl_all.deb ...
Module dahdi-3.4.0 for kernel 6.1.0-37-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

dahdi_dummy.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.1.0-37-amd64/updates/dkms/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

dahdi.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.1.0-37-amd64/updates/dkms/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

dahdi_transcode.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.1.0-37-amd64/updates/dkms/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.
      depmod...
      Deleting module dahdi-3.4.0 completely from the DKMS tree.
      Unpacking dahdi-dkms (1:3.4.0-6+asl) over (1:3.4.0-6+asl) ...
      Setting up dahdi-dkms (1:3.4.0-6+asl) ...
      Loading new dahdi-3.4.0 DKMS files...
      It is likely that 6.8.12-8-pve belongs to a chroot's host
      Building for 6.1.0-37-amd64
      Building initial module for 6.1.0-37-amd64
      Done.

dahdi_dummy.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/6.1.0-37-amd64/updates/dkms/

dahdi.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/6.1.0-37-amd64/updates/dkms/

dahdi_transcode.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/6.1.0-37-amd64/updates/dkms/
      depmod...
      root@AllStarCT:~# sudo -smodprobe dahdi
      sudo: invalid option -- 'm'
      usage: sudo -h | -K | -k | -V
      usage: sudo -v [-ABkNnS] [-g group] [-h host] [-p prompt] [-u user]
      usage: sudo -l [-ABkNnS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command [arg ...]]
      usage: sudo [-ABbEHkNnPS] [-r role] [-t type] [-C num] [-D directory] [-g group] [-h host] [-p prompt] [-R directory] [-T timeout] [-u user] [VAR=value] [-i | -s] [command [arg ...]]
      usage: sudo -e [-ABkNnS] [-r role] [-t type] [-C num] [-D directory] [-g group] [-h host] [-p prompt] [-R directory] [-T timeout] [-u user] file ...
      root@AllStarCT:~# sudo -s modprobe dahdi
      modprobe: FATAL: Module dahdi not found in directory /lib/modules/6.8.12-8-pve
      root@AllStarCT:~# sudo -s modprobe dahdi_dummy
      modprobe: FATAL: Module dahdi_dummy not found in directory /lib/modules/6.8.12-8-pve
      root@AllStarCT:~# sudo -s modprobe dahdi_transcode
      modprobe: FATAL: Module dahdi_transcode not found in directory /lib/modules/6.8.12-8-pve
      root@AllStarCT:~# sudo -s systemctl restart asterisk
      root@AllStarCT:~# asterisk -rvvvvv
      Asterisk 22.2.0+asl3-3.4.5-1.deb12, Copyright (C) 1999 - 2025, Sangoma Technologies Corporation and others.
      Created by Mark Spencer markster@digium.com
      Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
      This is free software, with components licensed under the GNU General Public
      License version 2 and other licenses; you are welcome to redistribute it under
      certain conditions. Type 'core show license' for details.
      =========================================================================
      Connected to Asterisk 22.2.0+asl3-3.4.5-1.deb12 currently running on AllStarCT (pid = 11908)
      == Manager 'admin' logged on from 127.0.0.1
      AllStarCT*CLI> rpt show registrations
      Host Username Perceived Refresh State
      34.105.111.212:443 65457 0 Not Registered
      34.105.111.212:443 65457 64.233.158.58:4569 179 Registered
      2 HTTP registrations.
28

When you say a “container” on Proxmox are you meaning a virtual machine or an actual composed container? Your issue is seen above… the OS you’re installing above doesn’t know anything about a kernel version 6.8.12-8-pve. Since that isn’t a standard Debian kernel I suspect you’re trying to use some sort of para-virtualization system and that kernel is coming from “outside” the environment you’re working in. That simply isn’t compatible with ASL. You need to install Debian 12 as a full VM.

29

Noted. I will delete the Container and Build a VM.

30

Joseph, I have to say, when you have a install that is not on the normal beaten path,
You should have stated that up front.
The time you wasted is not only your own. Try to remember this in the future.