Happy it's working well for you, thanks for the praise.
Not sure I fully understand request.
To block a GSSI you would need a list of (known) target GSSIs to exclude from 'main' list. ('TETRA_GSSI.txt').
Logging all seen GSSI then putting unwanted GSSIs into 'Lockout' seems easy to me.
I'm guessing you refer to the list that is displayed in 'G/SSI Editor'
I maybe be able to add a checkbox that filters out the locked out GSSIs from the list when opened.
Latest version (v1.0.14) can be found here: Release post
uplex Hook_method:No hook signalling (direct through-connect) Basic_service:Broadcast Clear Unprotect_72 Call status:7 Modifyuplex requestedI use TETRA demod plug-in (hotfix 6, released Jan 2019) and when monitoring encrypted network (which supports also security class 1, clear speech supported) it shows in network info e.g.
SYSINFO - Main_carrier:x Offset:3 Frequency_Band:3
SSI:x Call ID:x Encrypt:Clear D_TX_Granted Transmission Granted_to_another_user
TS4_unallocated 10
SSI:x Call ID:x D_Call_Proceeding Mode_of_Operation
SSI:x D_Status Pre-coded status #:x (Reserved value)
TS3_unallocated 9
SSI:x Reserved20
PDU encrypted:2 Data incorrect! SSI:x Call ID:x D_Alert Mode_of_Operation:Simplex Modify:Simplex requested
D_NEW_CELL Channel_command_valid: Follow MAC channel change (follow channel allocation in MAC header)
SSI:x D_Facility
SYSINFO - Main_carrier:x Offset:3 Frequency_Band:3
TS4_unallocated 10
TS3_unallocated 9
PDU encrypted:2 Data incorrect! SSI:x Call ID:x Disconnect_cause:Not_allowed_traffic_case D_Disconnect
PDU encrypted:2 Data incorrect! SSI:x D_SDS_Data Party_SSI:x Type:UDT-3 Length:64 Data:x
Support your question TTT very Good only for monitoring signalling, RAW data etc!
The red text that follows "Data incorrect!" is actually incorrect, false, rubbish or dodgy.
This is all your going to see from an encrypted PDU.
Both of what? Both encrypted and unencrypted PDUs can exist in network and that is what I am seeing when using old version (hotfix 6) of the plug-in. The latest plug-in (when monitoring same network and same frequency) shows nothing but PDU encrypted: MAC_resource (CCK-id is even) on timeslot .....
The G/SSI Editor is quite basic and is not structured to be that fancy.
I have added a checkbox that (when enabled) will filter out the locked out GSSIs from the displayed GSSI list.
Any GSSIs seen will still be stored in "TETRA_GSSI.txt" record file. (And NOT locked out by default)
If 'Filter lockouts' is enabled and you wish to allow a locked out GSSI, then disable 'Filter lockouts' to reload list and show all GSSIs (that are either locked out or allowed) then change state of desired GSSI.
Latest version (v1.0.14) can be found here: Release post
FIXED: 'Listen only clear speech' was not working properly. Encrypted audio can sometime bleed through.
- After fix there is a caveat to this:
- When PDU's are clear and speech is encrypted, then blocking of speech should occur (when enabled)
- When PDU's are clear and speech is a mix of clear and encrypted, then blocking of speech should occur for encrypted speech (when enabled)
- When PDU's are encrypted and speech is encrypted then blocking of speech should occur (when enabled)
- When PDU's are a mix of clear and encrypted and speech is a mix of clear and encrypted then blocking of speech may not work well (when enabled)
- This is because both clear and encrypted PDUs are seen confusing things. Not much can be done about this I think.
