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?

 

[Tom_Neverwinter]

I love this update. I think I go home every day after work and just look at it.

 

[LeSueurC]

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.

With the “changed “or “updated” aliases I’ve noticed when I look in the Radio.notes file, the first time it decodes the alias, it doesn’t decode it all the way or it’s not the right alias, example I’ve seen Fire_DI_12, then after is shows updated or changed it’ll show Medic_12A.

 

[mtindor]

With the “changed “or “updated” aliases I’ve noticed when I look in the Radio.notes file, the first time it decodes the alias, it doesn’t decode it all the way or it’s not the right alias, example I’ve seen Fire_DI_12, then after is shows updated or changed it’ll show Medic_12A.

That's just an alias that got updated. When originally copied it was Fire_DI_12, but at some point the programmers re-appropriated the radio to a new user or agency and the next time the alias was copied it was Medic_12A.

Most aliases probably change rarely, but some change more often. Move equipment from vehicle to another. Re-assign a radio from one user to another.

 

[LeSueurC]

That's just an alias that got updated. When originally copied it was Fire_DI_12, but at some point the programmers re-appropriated the radio to a new user or agency and the next time the alias was copied it was Medic_12A.

Most aliases probably change rarely, but some change more often. Move equipment from vehicle to another. Re-assign a radio from one user to another.

Mmmm afraid not. This was a pretty short amount of time that I noticed this. It’s a Harris core mixed with Motorola/Harris radios, so that could be another factor. I’ve noticed it’ll get one part of the alias correct, and at some point or the next day when I run it, it changes to the correct

 

[mtindor]

Mmmm afraid not. This was a pretty short amount of time that I noticed this. It’s a Harris core mixed with Motorola/Harris radios, so that could be another factor. I’ve noticed it’ll get one part of the alias correct, and at some point or the next day when I run it, it changes to the correct

Good to differentiate. Harris and Moto OTA is completely different. Moto OTA is hashed/encrypted/whatever. Harris OTA are in the clear.

If you think there is a problem, gather your proof of the issue and send it to dsdplusfastlane@gmail.com. After all, you didn't post any actual data showing what you are describing here that I can see. If you are using anything other than the latest 2p523, then ignore what I said altogether and upgrade.

 

[seagravebuff60]

Received. Thank you all for helping me and everyone else understand this better. There is a lot of great info here, and it is a very useful feature.

I also noticed that I see a lot of "Talker alias reacquired for BEE00.00A-8675309; data was stale." I assume this is a regular check to see if the alias was updated. I did set my re-acquisition rate to 1 day. I am monitoring a new system, and they change the aliases a lot, lol.

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?

I think, depending on the system, there needs to be a voice transmission in order to decode the alias.

 

[inthesmoke]

I think, depending on the system, there needs to be a voice transmission in order to decode the alias.

Yes, for your system to decode it. However the server changed status I am theorising is when it’s the alias on the server has changed and your system picks the update, rather than you decoding it. But the whole alias check for radios with an existing alias in your file (not blank), seems to be triggered by a voice call, so wondering what might trigger a check with the server, but not be able to decode it. There are a few situations I can think of, but would think they are relatively limited

 

[inthesmoke]

Pretty amusing watching my system upload a few hundred aliases to the server after being offline all day due to an ISP outage. Would be interesting to have our own stats for uploaded, downloaded, updated etc

 

[seagravebuff60]

Pretty amusing watching my system upload a few hundred aliases to the server after being offline all day due to an ISP outage. Would be interesting to have our own stats for uploaded, downloaded, updated etc

That would be cool if it were explicitly stated. The workaround I use is the Find, Mark, and Bookmark features in Notepad++.

I search for "alias server" and then have it bookmark the lines containing that info, open a new page, and paste the bookmarked lines in there. The number of lines will show you the amount. You can take it a few steps further by filtering per system or even per uploaded, downloaded, or changed, as you mentioned.

 

[inthesmoke]

That would be cool if it were explicitly stated. The workaround I use is the Find, Mark, and Bookmark features in Notepad++.

I search for "alias server" and then have it bookmark the lines containing that info, open a new page, and paste the bookmarked lines in there. The number of lines will show you the amount. You can take it a few steps further by filtering per system or even per uploaded, downloaded, or changed, as you mentioned.

Our system is now at nearly 15,000 aliases on the server now. Anecdotally from watching when I'm WFH, I'd have uploaded a fair chunk of those. But that would be a lot of processing from the logs to achieve your suggestion! It's just the sort of thing I would mess with, but enough other things to do at the moment instead.

 

[seagravebuff60]

Looks like I might have missed one.

I'm assuming that "Talker alias "TEST" acquired for BEE00.00A-8675309" means that this is a new alias that I acquired locally on my machine and sent to the server?