Recycled node number problem

AllStarLink
1

I recently obtained node number 53999 for callsign VE3RAG in Barrie Ontario. I downloaded the latest image from HamVOIP and installed it on a Raspberry Pi 4B. The installation and configuring using the "First Time" script went smoothly and it is registering correctly on the network, but after logging into Supermon, I noticed that it was providing the weather for ZIP 33904 (in Florida?) as my location's weather.
The next step was to configure the Android app DVswitch Mobile, but when I attempted to connect to 53999, the app indicated it was connecting to node 1998 in Mansfield Texas and then failed to connect.
On searching through the Pi's Asterisk files, I found that the First Time script had created an entry in "/etc/asterisk/local/privatenodes.txt" of "1000|WB6XYZ| . ." which was not remmed out.
So far I have been unable to connect to my node with the Android app after following instructions in several videos and documents.
I am wondering if the problem might be that all of the old info from the previous owner of node number 53999 has not been removed from the network servers.
AL - VE3RRD

2

This community forum is for ASL, not hamvoip. Hamvoip is extremely outdated and should be avoided. Use ASL3 instead.

3

Thanks for info, just installed ASL3 on my Pi 4B. Works much better and I can now connect to it with the Android app. Although the app is still showing a callsign of KI5NDA in Mansfield TX under the status tab for node 53999.

4

"Status Tab" where? What are you referring to?

5

I was referring to the status tab on the Android app when I connect to my node.

6

have you been to the ASL Portal at https://www.allstarlink.org/ and updated the Server and Node Settings?

7

Yes, the Portal Server Settings and Node Settings have always shown the correct info for the node callsign and location, even back when I was using HamVOIP

8

Assuming you're talking about DVSwitch (we don't do any phone apps, that's all 3rd party), I show incorrect metadata for several of my own Allstar nodes where I changed it over a year ago. It wasn't that important to me so I ignored it. I think you'll have to ask N6IRS about how to deal with that on his groups.io group.
Your node settings in the portal show exactly what you said they did, so everything on this end is as it should be, as far as I know.

9

Just a guess here, but on DVSwitch Mobile, try navigating More, AllstarLink, Update Node List. That might refresh the status page next time you connect.

David, WD5M