24th Public Release - TETRA Trunk Tracker and TETRA Demodulator plug-in - v1.7.0.0
Please note that TTT and TETRA Demodulator plug-in has some new experimental changes and requires all components to be updated.
I suggest creating a new SDR# and TTT folder for this version.
Please read the changelog for usage procedures for any new and experimental stuff.
This package (version) of TETRA Trunk Tracker and TETRA Demodulator plug-in (with codec libtetradec.dll) are only meant to be used
with each other and with no other previous versions. To do so will cause issues.
TETRA Demodulator plug-in has been updated by me. "Tweaked Edition (Unofficial) v1.7.0.0"
This is required to be used with TETRA Trunk Tracker v1.7.0.0. Please read the documentation files in zip for plug-in.
This plug-in version changes/adds and fixes some items:
Code:
Summary of changes:
v1.7.0.0
Rolled up all hot-fixes and updates (from v1.6.3.4 up) for release
Various fixes
ADDED: When plug-in is used in stand alone mode (TTT mode not enabled), the active call will highlight in the calls list
Updated libtetradec.dll
=====================================================================================================
v1.6.3.10 - Hotfix - Experimental version, not released
Various fixes and changes
FIXED(part): CMCE - SDS when text coding scheme was 'UCS-2 with the UTF-16BE extension' error seen
FIXED: Bad crash of SDR# (no crash reports)
- This was caused by incorrect offset calculation that resulted in a negative value.
FIXED: SNDCP - IPv4 TCP
CHANGED: SNDCP UI
- IP/Port fields removed
When a transfer occurred, I noticed that IP/Ports change between some SDUs.
- SDU panel larger and now each entry contains IP/Port
CHANGED: SYNCINFO element renamed from 'Security_Class_3_supported_on_cell' to Security_Class_2_or_3_supported_on_cell
- This better indicates the dual nature of element.
ADDED/CHANGED: Very experimental show encrypted "call" details
- This may NOT be 100%.
If it does not work then disable it.
- The purpose of this is to try and show encrypted activity on the current carrier and other carriers (not possible to know which one).
This does NOT decrypt anything, it just tries to associate voice activity with the encrypted PDU activity on assigned timeslots.
Don't be that guy that asks for decrypting PDUs and audio to be added. It not going to happen.
The encrypted PDUs can be more than just call control PDUs (CMCE) so seeing them does not indicated only D_TX_Grant, D_TX_Ceased.
The call shown in 'Network Info' 'Calls' is only going to partly showing real information:
- Call ID is NOT real. It's 20000 + usage marker value. (So any Call ID above 20000 is not real)
- Group will be either 'Unknown' or 'Encrypted' (Will be determined on encrypted PDU activity)
- TXer will be the SSI the encrypted PDU was targeted too. This could possibly show that the MS is in call but this does not mean the MS is actually talking.
- Users same as TXer, will populate as encrypted PDUs are seen on assigned channel.
- Carrier is real, except when '9999', this is a possible call on another carrier.
- Timeslot is real, except when ' '. This is a possible call on another carrier.
- Mode Op (Simplex/Duplex). There is no way to determine this so will always be simplex.
- Encrypted/Unknown calls that are active on a timeslot of the current carrier will be highlighted light yellow.
The SDR# side-panel will show 'Unknown' or 'Encrypted' for GSSI and ISSI will be the SSI the encrypted PDU was targeted too. This will show that the MS is in call but this does not mean the MS is actually talking.
'X' will show when 'Unknown' or 'Encrypted'
'Unknown' will most likely show when on a carrier that is not the main carrier and call is not encrypted.
Encrypted "calls" will not be selected for listening if 'Listen only clear speech' enabled.
=====================================================================================================
v1.6.3.9 - Hotfix - Experimental version, not released
FIXED: Detection of an unassigned carrier for a call.
- On some occasions, a carrier is not assigned (by AACH) as 'assigned' or 'traffic' (by network) when
a call is set-up. When this occurs, there is no call traffic and the call will wait until the 'Call timeout' triggers.
This change should see the unallocated code detect this and exit call immediately.
CHANGED: When D_SDS text messages (of various known protocol IDs) are seen with unsupported 'TextCodingScheme',
a binary string will also be output.
This can be used with TTT 'TETRA_sds_unknown_protocol' processing feature.
CHANGED: D_SDS: Duplicate 'External subscriber number' would cause error.
see 'changelog.txt' for full list and details.
If SDR# is crashing when 'Demodulator' is enabled, it's because you have not set-up the plug-in correctly.
You MUST do this 1st. This is NOT TETRA Trunk Trackers fault.
You generally need to get these installed:
"Microsoft .NET Framework 4.6.2 (Offline Installer)"
"Microsoft .NET Framework 4.7.2 (Offline Installer)"
"Microsoft Visual C++ 2015 Redistributable" and install both 32/64 bit versions (if you use 64 bit OS)
This TETRA Trunk Tracker version changes/adds and fixes some items:
Code:
Summary of changes:
v1.7.0.0 - Release
Rolled up all hot-fixes and updates (from v1.6.3.4 up) for release
FIXED: D_Call_Restore PDU
- This PDU does not always have 'New call ID' element and was ignored when the PDU didn't have it.
CHANGED: Include processing of 'Usage' element
- This will help only playing of call related audio and filter out other audio or encrypted audio.
FIX: D_Setup PDU
- With the inclusion of 'Usage' element, it was noticed that occasionally some 'D_Setup' PDUs did not have the 'Usage' element
present which would cause a no audio play condition in the plug-in.
=====================================================================================================
v1.6.3.9 - Hotfix - Debug version, not released
FIXED: On incomplete call set-ups (private only?), '-1' was incorrectly stored to G/ISSI records.
ADDED: Processing of known 'Protocal IDs' (text messages) but with unknown 'TextCodingScheme'.
- TTT will pass the binary string though the 'Unknown Protocol' section to process a binary string.
ADDED: Store Call ID + Party ISSI [Experimental]
- Used for calls where the Party ISSI is just missed because it is only sent once. see v1.6.3.1
see 'changelog.txt' for full list and details.
Has been tested on Windows 7 - Basic (64 bit)
Has been tested on Windows 7 - Professional SP1 (32 bit), English
Has been tested on Windows 10 - Professional (64 bit)
I have created it to suit my needs. And it currently works for me with the TETRA network I monitor.
I make no claim that it will work for other networks.
Please read the provided files for set-up and usage:
- TTT_set-up_manual.pdf
- TTT_Features_and_Usage.pdf
- TETRA_Demodulator.pdf
I have tried to be as thorough as possible with the documentation to explain usage and features.
I believe any questions can be answered by reading these files.
These files most likely are not complete and contain errors and are not laid out as good as they could be.
The TETRA plug-in is now been mainly tested with SDR# 1700 on Windows 7 Professional 32 bit with no issues seen.
The TETRA plug-in with SDR# 1700 on Windows 7-10 64 bit PCs is partly tested with no issues seen.
The TETRA plug-in with SDR# 1727+ on Windows 7-10 32/64 bit PCs is partly tested with no issues seen.
It only works with the provided TETRA plug-in supplied in zip. (2020-February-27).
This version no longer uses a custom compiled version of 'Net Remote'
It is only meant to be a temporary solution until something better comes along.
I'm sure all these changes are going to create addition bugs.
I have tested to the best of my ability.
Putting it in the wild should be a better test of things. Please report any issues.
Note: This link now is to a folder that stores the download, which means the link to the location of the files will stay the same but the files in it can vary.
Download
MD5 HASH b077a3e86827339f5e7d72fd1c0be0f7
