KK4PF
November 14, 2024, 3:35pm
1
I have recently installed ASL3 on a Raspberry Pi 5. I have Allmon3 working on this system and am using Supermon 7.4+ to display the info.
When an Allstar station is connected, Supermon displays the correct info.
When an EchoLink node corrects, Supermon (or Allmon) does not displays an incorrect node number of the connected station. Also, Supermon does not display the callsign of the connected station. However, Allmon displays the callsign associated with the (incorrect) node number.
This appears to be unique to my system as when I connect to another system (not ASL3) things display correctly.
Any help would be greatly appreciated as my node supports a daily net and our NCS stations rely on this info.
Thanks,
Stan
N8EI
November 14, 2024, 3:47pm
2
When you’re talking about Allmon, you are referring to Allmon3 correct? Make sure you are running Allmon3 v1.4.1. There was some bugfixes that went in to support Echolink node number display issues for certain Echolink node number types.
Mike
November 14, 2024, 11:27pm
3
Stan, this may or may not apply to your situation but you do need to know that sometimes when there is a EL connection through a RELAY or PROXY, the node number or callsign is of the RELAY, not the user.
You would have to consult the echolink folks for best explanation.
KK4PF
November 15, 2024, 1:04am
4
N8EI,
Thanks for the response. Yes, I am using Allmon3 Version1.4.1.
Thanks,
Stan
KK4PF
November 15, 2024, 1:06am
5
Mike,
Yes, I am aware of what you are talking about with the relay and Proxy. I have used both at various times. However, In this case, the node numbers are displaying correctly on another node which I help manage, so I’m fairly confident that the problem is on my end. However, thanks for responding.
Stan
N8EI
November 15, 2024, 1:49pm
6
Do you have anything configured in the [node-overrides] stanza of /etc/allmon3/web.ini? From the asterisk console, what does echolink dbget nodename NNNNNNN report?
Allmon3’s data for Echolink nodes comes only from one of two places.
KK4PF
November 15, 2024, 9:45pm
7
N8EI,
As best I can tell, there is nothing in that stanza. I haven’t put anything there. There does appear to be a blank line in that stanza, don’t know if that is relevant. Copy of the info is below.
[node-overrides]
;;
Thanks,
Stan
KK4PF
November 15, 2024, 10:05pm
8
N8EI,
I believe that I am in the right place to get what you are asking for. If not, please advise. I selected
Connected to Asterisk 20.9.3+asl3-3.0.6-1.deb12 currently running on node54633 (pid = 1035)CLI> echolink dbget nodename 550195 CLI>
Thanks,
Stan
N8EI
November 15, 2024, 10:44pm
9
Interesting. Can you attach a screencap of what you see on your node when you connect?
KK4PF
November 16, 2024, 12:38am
10
Sure,
The 60827 node is an Allstar node and displays correctly.
Thanks,
Stan
N8EI
November 16, 2024, 4:00pm
11
That is Supermon which I cannot help with. You said above you were having problems with Allmon3 I thought?
KK4PF
November 16, 2024, 11:24pm
12
I am also having problems with Allmon3. I assume that the issues are related, but don’t know for sure.
As far as Allmon 3, when I connect to an Allstar node things work as expected.
When I connect an EchoLink station, and reload the Allmon3 page, the Allmon3 display does not display the Allstar node, or the EchoLink node see the screenshot.
So the EchoLink connection appears to be making Allmon3 unhappy.
On the ASL dashboard, the node number is correct, but there is no callsign listed for the EchoLink connection.
Thanks,
Stan
N8EI
November 17, 2024, 12:23am
13
Can you send me the output of journalctl -xeu allmon3.service? They problems are likely related only in that parsing of Echolink is a messy proposition.
KK4PF
November 17, 2024, 12:08pm
14
Sure,
Note: I replaced all instances of https in the file with LinkRemoved as the forum will only let me post a maximum of two links in a message.
KK4PF@node54633:~ $ journalctl -xeu allmon3.service
Thanks,
N8EI
November 20, 2024, 11:22pm
15
Would you be able at some point to connect to my test hub with your Echolink node so I can see what’s going on?
However did you have any errors or problems upgrading Allmon3 to 1.4.1? That error exactly what was fixed in 1.4.1. You might want to try an apt install --reinstall allmon3 to make sure all the files are correct.
KK4PF
November 21, 2024, 11:39am
17
N8EI,
Thanks for your patience. I will try the re-install. It may be this weekend before I can get to that. I’d be fine with connecting wo your hub if that doesn’t work.
I did not have any install errors that I am aware of. This was a new install on a Raspberry Pi 5. Just a couple of weeks ago.
Thanks,
Stan
