"Direct Client" connections (callsigns for Node) cannot disconnect with red 'X' disconnect option

Allmon
1

Clients in the Allmon3 list shown as 'Direct Client', unable to remove their connection with the red 'x' in the web interface of Allmon3. Typically these stations show up with callsign as the node number.

Should this be possible to do?

********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.12.20+rpt-rpi-v8

Asterisk : 22.2.0+asl3-3.3.0-6.deb12
ASL [app_rpt] : 3.3.0

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.4.2-1.deb12
asl3 3.7.1-1.deb
asl3-asterisk 2:22.2.0+asl3-3.3.0-6.deb12
asl3-asterisk-config 2:22.2.0+asl3-3.3.0-6.deb12
asl3-asterisk-modules 2:22.2.0+asl3-3.3.0-6.deb12
asl3-menu 1.12-1.deb12
asl3-pi-appliance 1.10.0-1.deb12
asl3-update-nodelist 1.5.1-1.deb12
cockpit 287.1-0+deb12u3
cockpit-bridge 287.1-0+deb12u3
cockpit-networkmanager 287.1-0+deb12u3
cockpit-packagekit 287.1-0+deb12u3
cockpit-sosreport 287.1-0+deb12u3
cockpit-storaged 287.1-0+deb12u3
cockpit-system 287.1-0+deb12u3
cockpit-wifimanager 1.1.1-1.deb12
cockpit-ws 287.1-0+deb12u3
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-6+asl
dahdi-linux 1:3.4.0-6+asl

2

No, you cannot disconnect an IAX-based client. That's a system-level connection not an app_rpt "dynamic" connection.

3

OK Hmm.

I thought this was something that could be done with Supermon.

I just went back to a test node running ASL3 3.3.0, but using the Supermon interface I am able to disconnect such a node.

I guess this is a design choice of Allmon3?

4

Does it actually disconnect though? I believe it'll come right back because it's an IAX2 trunk connection with a dialplan right into the node.

5

Yes it does disconnect.

For an example, I have DVSwitch on my android phone. When I connect to my node using the web transceiver mode, my callsign shows in the node number field, and 'Direct Client' for the node info/description.

When I boot my dvswitch client from supermon, client disappears from the node and I get a message on my phone:

"TextMessage: !!DISCONNECT!!"

And DVSWitch on my phone changes such that I have to enter node number and 'connect' again.

I have attached some side by side pics of allmon3 and supermon, and dvswitch:

Screenshot 2025-04-24 110004
Screenshot 2025-04-24 1100041678×898 130 KB

Screenshot_20250424-110033
Screenshot_20250424-1100331080×2400 155 KB

6

If I follow what Supermon executes to disconnect nodes, a custom command in allmon3 like this works:

rpt cmd MY_NODE ilink 11 TARGET_NODE

I guess it would be handy if the red 'X' would work for the less savy control ops heh.

7

Probably related, but clicking on the line with a node number that has a callsign such as my example, also doesn't prepopulate for the 'execute linking commands' drop downs.

8

If Supermon uses ilink 11 does Allmon3 work if you do a "Disconnect Permanent"? That's what the command ilink 11 is vs. ilink 1 which is what Allmon3 does by default.

9

I am not sure what the action of clicking on the red 'x' in allmon3 does.

Is that supposed to execute ilink 1, or ilink 11?

10

By default it's an ilink 1

11

OK I tried both of these, manually filling in the node 'KB9OIV', since clicking on the allmon3 node row to 'prefill' and the red 'x' did not work.

Both 'permanent' YES and NO did work successfully.

12

So something with allmon3 coding in particular I guess, for the red 'x' and the prefill to not work?

13

To add a bit more, clicking on the red 'x' next to a callsign in the 'Node' column does not open the pop up window to do any disconnection actions (including 'prefill'), like it does for line entries for the 'Node' column that are numbers.

14

Okay. Can you file a bug for this in GitHub? I was asked to implement the red X box and I've regretted it since I did...