CIS MFSK-33 (here:15+∅+17), likely a "Serdolik" multimode waveform

Fig. 1 - "Serdolik" multimode waveform

The MFSK segments have the usual 40Bd and 40Hz (channels separation) values which are typical of the Serdolik waveforms family: a long-range radio system used by the Russian and CIS countries Diplomatic Service, possibly Serdolik V2. It's worth noting in Figure 2 - at least in this sample - that although the system provides a 33 channels grid, only 32 are the effective (used) ones: specifically, the first 15 lower channels plus the 17 higher ones (the 16th channel is not used).

Fig. 2 - MFSK segments

The FSK inserts too have usual Serdolik values, ie 40Bd/680Hz in this sample, and consist of short "01"s sequences (Figure 3).

Fig. 3 - FSK segments

This sample has been recorded on 20.8155 MHz/USB using a remote AirSpy server located in UK.

CIS MFSK-33 waveform is not the only one that does not always use all the available channels of the frequency grid: CIS MFSK-34 (aka Crowd-36) is another example in this regard (Figure 4).

Fig. 4 - frequency grid of some CIS MFSK-34 samples

https://disk.yandex.com/d/wgskeCZfRcz6Ow

3G-HF Fast Traffic Manager (FTM) at work

This sample provides an example of the use of 3G-HF (STANAG-4538) Fast Traffic Manager (FTM) protocol, which is sometimes referred to as simply FLSU (Fast Link SetUp). More precisely, FLSU is used to set up links, and it includes the traffic type that will be used immediately after the link set up is complete; FTM is used after the FLSU for cases in which the traffic type needs to be changed, or to negotiate channel access among linked stations.
As stated in S-4538 Annex-C Edition1 Amendment2, if a link has been established for delivery of packet traffic using the HDL+ data link protocol (BW7), all FTM and FLSU Protocol Data Units (PDUs) transmitted for the remaining duration of the packet link shall be transmitted using the BW6 burst waveform: thus, since the use of BW6, the link was initialized for HDL+ protocol. But, as you can see in Figure 1, at some point an FTM negotiation causes the change of the traffic type: from HDL+  (BW7 waveform) to LDL (BW3 waveform).

Fig. 1 - traffic type change

It's worth noting the use of BW4 waveform bursts after LDL data delivery, it's requested by the #4.6.5 Dual Demodulation condition: "Under no circumstances shall stations be required to simultaneously demodulate more than two waveforms. Any scenario requiring more than dual-demodulation is either an error in the specification or an error in interpretation" (1).

 
By the way, the BW3 burst transports a L3Harris "Citadel" encrypted message (Figure 2).

Fig. 3

https://disk.yandex.com/d/YCupV-cFBXOmqQ

(1) HDL+ states is missing in the Table 4.6.5-1: however, since BW6 burst waveform is used for Ack/EOM/Term messages, Master and Slave stations expect to receive a BW6 or a BW7 waveform.