DSDPlus understanding alias server terminology

[seagravebuff60]

I monitor several systems with OTA talkers enabled. This is a very useful feature. However, over the past few updates since it was implemented, it seems some terminology in the event log files has changed with each update.
Anyway, the latest version (2.523) it shows that there are 3 "terms" that show the talker alias process. I have a few questions about what they mean.

In my event log files, I have "Alias server returned talker alias"; "Alias server updated with talker alias" ; and "Alias server *CHANGED*"

I assume "returned" is a new alias the server has acquired?
Im a little confused about what "updated" means.
I assume "*CHANGED*" means that the talker alias changed recently?

Ive also noticed that I am getting some server aliases returned from a system I don't currently monitor but have previously monitored. I'm assuming this is from other users monitoring that system, and the data is getting sent to my DSD+ because that record or system is in my radio file?

Thanks.

 

[inthesmoke]

Yes, yes and yes, from my interpretation of what’s been shared and what I’ve seen.

Server returned: downloaded from the server. Means you had a RID that someone else decoded the alias and sent to server.
Server updated: you decoded the alias and uploaded
Server changed: I’m not certain , but likely means an updated decode

 

[BM82557]

Ive also noticed that I am getting some server aliases returned from a system I don't currently monitor but have previously monitored. I'm assuming this is from other users monitoring that system, and the data is getting sent to my DSD+ because that record or system is in my radio file?

Thanks.

Yes also

 

[wx2watch]

Thanks for expanding upon the meaning of those messages.

My question would be about stale data:

reacquired for BEE00.D14-36381; data was stale

 

[BM82557]

Thanks for expanding upon the meaning of those messages.

My question would be about stale data:

reacquired for BEE00.D14-36381; data was stale

The way I understand it is that the radio has not been active on the system for longer than the Talker Alias Reacquisition Rate is set for so the Alias is reacquired. The default Rate is 30 days but can be adjusted by the user, in my case I have it set for 5 days --

 

[inthesmoke]

Yes, that's my interpretation also. What I'm not 100% sure about is whether than applies only to decoding, or also to pulling from the server.
I have mine set to a number of days also, as we do see aliases updated frequently as spares are moved around.

 

[inthesmoke]

Doing a little looking through a log.

For Server alias updated, can confirm 2 scenarios
- When I acquire a new alias that isn't on the server
- When I acquire a changed alias
In both cases the log file reports the Alias server updated with talker alias "abc"

So far in a couple of logs I've searched, I don't have any results for Alias Server Changed. In my case, I imagine that would be because the aliases most likely to change for me, are on sites/TGs that I'm actively monitoring, so I'm the one decoding updated alias. I might startup a recent backup od DSD to see what it reports as it gets updates from the server (without FMP running)

 

[inthesmoke]

Doing a little looking through a log.

For Server alias updated, can confirm 2 scenarios
- When I acquire a new alias that isn't on the server
- When I acquire a changed alias
In both cases the log file reports the Alias server updated with talker alias "abc"

So far in a couple of logs I've searched, I don't have any results for Alias Server Changed. In my case, I imagine that would be because the aliases most likely to change for me, are on sites/TGs that I'm actively monitoring, so I'm the one decoding updated alias. I might startup a recent backup od DSD to see what it reports as it gets updates from the server (without FMP running)

Ran DSD on my other machine
Confirmed a RID that was 'out of date' in that radio file. (It updated yesterday in my 'live' setup)
DSD returned server aliases for about 20 aliases. These all appeared to be radios without a previous alias on that machine.

It seemed that no existing aliases were updated. This leads me to believe that the download occurs only for radios without an alias. For radios with an existing talker alias, I'm guessing that an active call or at least registration/affiliation is needed to trigger an alias check. This would mean that the server changed status would be a limited situation where a refresh is triggered, but your setup wasn't able to decode it and it's gone to the server to look for it? A very short call, or a data only call perhaps?