If I do an “echolink show nodes” it shows call letters, node number, and ip correctly. I added my echolink node to web.ini over-ride. I also start astdb, added my echolink node number to the top. I made two entries, one with just the node number and one with the padded 3. I turned the timer off on astdb, so it not remove my entries. Allmon3 just says node not in database.
Where does Allmon3 pull the information for echolink users?
Thanks David
If I understand you correctly, you added a node to the ‘local file’ which is not the asterisk database and will not show there.
The purpose is to have it show in your allmon etc when it’s not in the database.
Such as private nodes.
The node database is made of only ‘publicly registered nodes’
I am simply asking where does Allmon3 pull data for Echolink users.
ASL3 shows this:
echolink show nodes
837500 KG5RDF 47.xxx.xxx.xxx samsung SM-N950U user
I just need some help what Allmon3 looking at. It sure is there in Asl3 data.
I believe it pulls it’s data from asl which pulls data from
Echolink DB on echolink servers .
If it did, it would not say node not in database. I do not mind changing code to make it work, but I am looking to understand where its pulling its data from. I was hoping not to have to search it out.
Not sure I follow your problem exactly.
Perhaps you missed a step adding a private node
systemctl restart allmon3.service
or
Your browser cache may be effecting your lack of updated display.
or
you entry was not in the correct format
But adding a echolink node number to the private node list in no way adds it to any database. Just the local private node list.
Or better describe your issue.
I am not sure you can add a echolink node number directly anyway.
What I do is attach the echolink node to a local private node. I use 1950 & 1951 on other server
I then describe the 1950 as echolink node # and location in the private node text file.
And because it is attached to a private node, I can connect it to what ever repeater I want or disconnect it all together.
If you’re asking if you can use the [node-overrides] section in web.ini to rename an Echolink node, I believe I don’t account for that use case in the code You would need to include the prefix 3 or 8 if it were to work but I’m pretty sure that part of the code doesn’t look at the ASL nodedatabase structure since it’s not technically ASL.
The code pulls the entry, if it exists, from echolink dbget. There are a few cases where that information comes out odd and doesn’t get parsed but I’ve never had anyone give me enough information to debug the problem.
I did have sometime to make a test node. Seams supermon 7.4 has same issue. I also noticed that “echolink show nodes” has the callsign correct, but can have node numbers wrong. If I look at “echolink dbdump” node numbers are correct. Both also look at nodes and not users. Like with direct client, you can see each individuals callsign and not grouped under one node callsign. I look at the code for Allmon3 and Supermon 7.4. I think they are checking for numbers against strings. Not sure how that would work well with all the variations. Sorry I am no help, thanks for the responce. I attached two pictures of echolink node connections.
Looks good. Is this Asl3 and Allmon3? If so what code changes were made?
Answer was above. No code re-writes. All functions built-in. This is Allmon2
The ini file should not be any different. I don’t think I have changed this in 6 years.
But the structure I have used for 10.
Nice, yes it all worked on older platforms. We will just use DVSmobile and abandoned Echolink. Thanks for your responses.
If you’re talking about the display of the line about Echolink, this is solely due to problems with the Echolink database information. I can likely fix it IF it’s possible to recreate the problem. However for everyone I know that uses Echolink, it always works. I need someone who consistently has a problem to connect to a system and let me look at the AMI data to see if I can correct the issue.
I need to setup chan_echolink on my test hub system and then if someone who routinely has this problem can coordinate with me to connect and leave Echolink connected for a few hours, I can probably fix the issue in the Allmon3 code. The problem now is I can’t reproduce the problem.
I have recreated and fixed this bug. It will be fixed in the forthcoming Allmon3 1.3.5 release.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
