DSDPlus FL 2.506 released

[DaveNF2G]

Perhaps. That would be a question for the DSD+ anonymous developers. But again, OTAs are not a per-site thing. It's done at the system level.
What system are you referring to?

Edit: I just looked at the aliasstats file, and I don't see any system with 839 pending aliases.

I probably didn't phrase it clearly enough. What I meant to say is that I have received a total of 839 alias responses from the server, but over the past couple of days DSDPlus has seen many more RIDs and indicated that the Aliases are being queried, but no new responses have come in.

The system is Albany/Schenectady Counties (NY) SysID 695. I have over 7000 RIDs stored locally.

 

[mtindor]

I probably didn't phrase it clearly enough. What I meant to say is that I have received a total of 839 alias responses from the server, but over the past couple of days DSDPlus has seen many more RIDs and indicated that the Aliases are being queried, but no new responses have come in.

The system is Albany/Schenectady Counties (NY) SysID 695. I have over 7000 RIDs stored locally.

If you are basing that upon seeing "Alias" in the Channel Activity window, I previously said that any time you see that it is collecting an alias to send to the server. I was wrong. "Alias" in the Channel Activity window simply means it is checking that RID for an OTAAlias transmission.

Thus, if you are going by seeing "Alias" in the Channel Activity window, it is not the indicator that you think / I thought it was.

If you look in your DSDPlus.radios file, it'll be clear which ones have OTA Aliases. Use some tool to count up the SysID 695 RIDs that have OTAAliases versus those that do not. It may just be that not all users on the systems have radios set to / equipped to send OTA Aliases.

Mike

 

[DaveNF2G]

If you are basing that upon seeing "Alias" in the Channel Activity window, I previously said that any time you see that it is collecting an alias to send to the server. I was wrong. "Alias" in the Channel Activity window simply means it is checking that RID for an OTAAlias transmission.

Thus, if you are going by seeing "Alias" in the Channel Activity window, it is not the indicator that you think / I thought it was.

If you look in your DSDPlus.radios file, it'll be clear which ones have OTA Aliases. Use some tool to count up the SysID 695 RIDs that have OTAAliases versus those that do not. It may just be that not all users on the systems have radios set to / equipped to send OTA Aliases.

Mike

That makes sense. Apparently after an OTA alias has been processed, DSDPlus no longer checks that RID. It does keep checking RIDs for which there is no OTA alias listed yet.

I started up again this morning after having been shut down overnight. After an hour, still checking for aliases, but no new responses.

Can anyone say whether the server is up or down?

 

[slicerwizard]

The alias server is sending me LMRN aliases right now.

 

[mtindor]

That makes sense. Apparently after an OTA alias has been processed, DSDPlus no longer checks that RID. It does keep checking RIDs for which there is no OTA alias listed yet.

I started up again this morning after having been shut down overnight. After an hour, still checking for aliases, but no new responses.

Can anyone say whether the server is up or down?

It will check a RID again, depending on the ReAcquisition Rate you set. By default it's set to 30 days. You can change it to something lower. But if you think the aliases are fairly "mature" and unlikely to change, you can probably leave the setting as is.

I don't see any reason why the server would be down. I suspect it's just a matter of aliases collecting, and that the batch would be processed later today. AliasStats.txt will tell the tale. If you see "pending" increasing, it's just batching up OTA Aliases for cleartext processing later. Nothing is immediate at this time.

 

[BM82557]

Received 8 clear returns at 0937 EST

 

[slicerwizard]

The stats download says that data for only 1030 aliases from system 695 has been submitted and decoded. So maybe not all radios on that system have aliases attached to them.

 

[RaleighGuy]

Can anyone say whether the server is up or down?

Tried to download allstats and it failed three times just now. (And yes I have a good internet connection)

 

[dave3825]

But you're saying this "server" provided by the DSD+ team is calling up system names from RRDB to put 'em in the AliasStats.txt file ?

I did not say anything like that at all.

Systems that do ota decoding that are not in the db will show up in the stats file with just the system id.

Tried to download allstats and it failed three times just now. (And yes I have a good internet connection)

I was just able to download the file now.




edit:

It is also actively decoding aliases at this time.

 

[seagravebuff60]

All good here as of 14:40 Hrs today.

 

[DaveNF2G]

Still not sure why so many aliases for agencies that have some are not being returned.

BTW, is OTA info sent on any other event besides a voice transmission? The overwhelming majority of RIDs from the county system are logged from affiliations and registrations. Many of them have never been logged making a voice transmission. I expect that those will ever remain unidentified (aside from interpolating which agency owns them).

EDIT: The system shows 74 pending queries, so I'll keep watching.

 

[dave3825]

Thought I read it only works on voice transmissions.

 

[GTR8000]

BTW, is OTA info sent on any other event besides a voice transmission?

No. Traffic channels only during voice grants.

 

[DaveNF2G]

No. Traffic channels only during voice grants.

This made me stop and think about how I was monitoring. When I went back to running DSDPlus after having shut down for a while, I thought to conserve resources by running only the CC instance. The mention of "traffic channels" made me go "hmm" and start up the VC instance as well. Voila! Alias queries are working as they had been when I first saw them.

 

[GTR8000]

Yeah, that has been covered more than once in both this and the previous thread. 🤦‍♂️