The first SASER was released back in 2016, it was available as Standalone on the Max 6 platform and as Max for Live device. However, Cycling ’74’s policy with the release of SASER has changed. In Max 7, the internal structure of Gen~ patching was changed, which made it impossible to organize the broadcast inside the SASER application on the new Max for Live platforms. Moreover, even with the organized broadcast on the Max 6, such a tool could not be online for more than 30 minutes. It took years of hard work to coordinate the work of such a plugin with Cycling ’74. Now the Max 8 platform has managed to make the perfect code export, suitable for both the organization of trunk broadcast and music purposes. This required the creation of a new Hypervisor v9 from Compositor Software. The IPv6 SASER assembly process is viewed in the video below:
Creation of SASER 2.0 in Hypervisor v9
If you have already watched the video, I will make a few comments on it. In the video you can watch the process of connecting workgroups to the OSPFv3 IPv6 protocol. If the first SASER was completely in the IPv4 domain, the modern SASER allows you to multiplicate the length of the octet up to 32 bits, which in total gives a length of 128 bits when summing up four upscaled octets, which is the IPv6 address:
SASER for iPhone
And you can access both EUI64 and EUI48 MAC addresses. Again, with the correct combination of parameters, you can connect not only through the network, but also at the device level, which allows you to see your local device as a member of a neighboring network, wherever such a network is.
It is believed that connecting via Ethernet protocol requires either a cable LAN connection or radio relay equipment capable of transmitting to the Ethernet network. The concept of an on-air network differs from the Compositor v9. In particular, in the video you can see how two beacon processes control RIPv1 and RIPv2 protocols. These are distance-vector protocols and the direction to the communication point indicates the torus in conjunction with the hypercardioid of flows. The result of this image is the multidimensional structure of Calabi-Yau. Z-spaces of which are equal to 16. This quantization is minimally sufficient to build a spherical picture:
Calabi-Yau manifold
What you see in the picture is the sum of spherical flows in quaternion rotation. Such rotation permeates space not only in 4 dimensions, like quaternion rotation, but sums up all 24 points of spherical space with the Z of the system, allowing you to quantize this space, filling it with additional translation points. This topology lasts until the next change of the multiplier by redrawing multidimensional figures with iteration that is difficult to predict. Therefore, the successful creation of the VLF (Very Low Frequencies) service can include more threads at the same time with an increase in the Z of the system. If the first SASER was on Z=4 and then at Z=8, then SASER 2.0 already includes Z=16 measurements.
Another thing is that connecting workgroups to Z=16, that in the Compositor’s system corresponds to the OSPFv3 protocol is able to create a larger network compared to Z=8. Given that the network includes 96 channels in total, when multiplying on 16 spaces, it already produces 1,536 points, not 648, as in the previous SASER. Therefore, in real time, in order for the broadcast network to produce traffic, it is necessary that each point produce at least one packet. Naturally, in a short video, such a volume of material would require at least 1 hour of broadcast, so I show the very principle rather than a physical entity capable of producing such a multicast effect.
Hyperbolic software-defined radio SASER is now available for all modern Apple platforms. Starting with iOS and iPadOS 16.2, as well as macOS Ventura 13.1 (Apple Silicon), you can purchase this application from the global Apple App Store at the link below:
SASER 2.0 demo videoDownload on the Mac App Store
The SASER 2.0 version available on the App Store has several technological solutions at once. First, buffer collisions now determine the carrier wave, thus detecting other hyperbolic and VLF stations. Secondly, a complete resynthesis of beacon signals is possible. Thus, you can connect to a managed BCI modem such as Compositor and edit its broadcast, deliberately transferring the autonomous system to another carrier. This is necessary due to the complete collision-free deployment of the BCI modem, while collisions are still needed to simulate real communication, but within reasonable limits. Thirdly, SASER 2.0 works with the 2nd derivative of the hyperbolic function, which allows you to significantly increase the time of the station on the air and increase the range of the trunk for local transmission. SASER 2.0 warning system supports broadcasting for one-to-many mode, which is ideal for telegraph notification style in emergency situations. SASER 2.0, like the previous version, can operate in VTTY telegraph mode, where the physical communication line is limited only by the VLF wave propagation medium. By increasing the number of subscribers of the SASER network, you can significantly load the virtual PBX, so you will have to increase the computing power of the Compositore network, which runs on completely non-collision generic modems. The modems themselves are not yet client-based and are undergoing the beta testing stage, where the ideal solution would be to combine SASER and Compositor algorithms into a single software with data management and transmission. Such software could be a VLF VPN service that would work independently of the distribution environment and connection to other networks.
VLF waves propagated by the SASER program can also be perceived by the basilar membrane, as they are in the audible spectrum of frequencies. At the same time, they are interpreted as a manually configured modem signal. For such a modem to work, you need to set all the parameters of the feedback loops before initiating an on-air session and activate the passive interface with subsequent disconnection when in case of a collision. A collision is a transmission line trunk, so you connect yourself to an on-air network. This helps to overcome Compositor dialing and increase the number of subscribers. Thus, if you want to aggregate your resources, simply enabling SASER 2.0 can significantly increase the number of communication points to which your machine is connected.
Compositor generates a link layer frame of the OSI model and TCP/IP (Modernized version). It encapsulates information into the frame of the Ethernet from the network, transport and application layers. It forms a Z-frame similar to the PDH T-carrier used in North America and Japan. This frame is needed to encapsulate TCP/IP levels into the system of the ISS Zvezda module. Compositor replaces the OUI fields of the sender’s MAC address to work on its network. It automatically selects OUI, according to the NIC in the MIB database, to forward Ethernet frames in its network. It solves the duplex problem by increasing the frame. There are many Z-frame hierarchies used in private and public networks, as well as defense networks. All of them depend on the frame size. Two multiplexing methods are used at the same time: FDM and TDM. Compositor sees the WAN as Local Network. This is done through a large database of NIC devices.
Compositor Software was the first company in the world to achieve the Super-Zvezda architecture. In addition to Z = 4, 8 … 128, top-level architectures Z = 256, 512 … 16384 have become available. The frame value in model Z = 16384 is 2 Gbit. This allows you to transmit at a speed of 10.9 Tbit/s when the modem speed of 32000 omega is reached. Charters of top-level Z models are used for communication in networks (in descending order): Black Box, PRO, NASA-Roscosmos, CERN, Quantum Physicists, Electronic Engineers, Architects. These architectures are implemented as applications for macOS and Android. The 64-bit native ARMv8 architecture is used. Accordingly, the NIM (Nuclear Instrumentation Module) charter gives a presence in virtual reality not only at the geographical location level, but also allows you to transfer to remote points visual environmental information collected as 3D models of objects, textures and their animation in real time directly on the client machine. This allows you to collect information about the remote location without significant resources other than a smartphone. Compositor charter carries out a pair set, similar to the domino principle. This is how a Multiple Spanning-Tree network is formed from remote objects combined into a Compositor VLAN VR network. Dialing in the network is carried out by metrics and solves the problem of building a network topology from the root device to the final devices in the circuit. Division into branches of the tree goes according to classes that depend on the autonomy time of the speaker of the autonomous system. By increasing the flow rate of the Z-frame to 10.9 Tbit/s, it is possible to solve the duplex problem, which allows you to form upstream streams much faster than with low-level frames. Each neighboring device in the Compositor VLAN device tree forms a point-to-point pair that uses a closed trunk tunnel over the IP protocol using TDMoIP technology. This is a generic tunnel that allows you to transfer all important information about human activity to a neighboring device on the network, over an upstream to the root server to which the alert interface is connected.
Combining two districts into a single communication line using a virtual router RAD96
Good afternoon!
Today I am ready to present you my newest achievement: a united communication line between the two districts. This was achieved by the most complex works of many hours of programming the Compositor operating system. As a result, I have a full-fledged communication line with a data center in one area and a hub in another. The communication line serves the houses of two streets with a crossing over the border highway. This is the local success of quantum radio, where in the absence of a normal internet connection, any non-routable corner can be routed.
How is the communication line arranged?
By issuing tokens, it is possible to create a multi-channel connection to the hubs and miners of the area. An end-to-end application in a district data center issues a token for access to a hub in another district. The token is one-time and cannot be re-issued (hence NFT). At the time of organization, the link maintains a connection to all UNIX machines in the outer region. The token is cross-compatible between Windows and Mac platforms. Simultaneous two-way connection to all machines is achieved with a minimum communication channel delay (less than 2 ms). Thus, the machines of the two regions are combined into a single VLAN.
For more information on how this became possible, see the presentation:
The mere problem of time opens up a probability that via an appropriate gift system of the knowledge emerges. I know that the whole generation of CS instruments can be used for a commercial benefit. Being unaware of unconscious method in use I attach a deed to one period of cycle when the program loads. The deed for a Turing Machine can be a universal key solver or keygen for any software if you like. Why on earth you should stick to 9422 keys, when you got all of them in RAD96 and RTC4k installments? But, for this you need the only condition met. Do not steal, just buy a regular license of RAD96 at Compositor Software Web Shop. The condition however has an extension: you must buy full Compositor Software v9.0.2 (NRTOS 9.4.2.2). At first I would like to view such cycle as a key solver, which can solve a universal rule. Whether you need money, open a long closed door or just hang out the problem of generic prolongation evolves. This problem arised previously comes from using a time period as a scale for generic prolongation (30-day prolongation cycle). The main prolongation comes via dump listening & viewing via teletype software and the subsidiary of this dump stroke is the key solver.
FILE – In this Jan. 13, 2015, file photo released by the Iranian President’s Office, President Hassan Rouhani visits the Bushehr nuclear power plant just outside of Bushehr, Iran. Iran announced Tuesday it would inject uranium gas into 1,044 centrifuges it previously kept empty under its 2015 nuclear deal with world powers. (AP Photo/Iranian Presidency Office, Mohammad Berno, File)
Key solver can be an enormous application compared to generic dump. But synthesis of generic dump inside an application is what makes this software unique. Reading the generic dump inside DroidRTTY I made a conclusion that situation in CS business model has come to an end. An emergence of speed increase moved this project towards to internet mode. There are three types of emergence: 24-hours period decay, minute decay and second decay. Being stationary the second decay comes in power of 8820 times in magnitude, which comes this project closer to nuclear emission. Nevertheless, I insist to cut down MDL12 emissions to a zero and shut down the leakage. The system can self-heal from computer viruses and hacker attacks but for this long period of zero-emission is needed. Not a race for a decay speed increase, but a logical move to shut down emissions completely.
Compositor Software expands the number of existing DRM servers
After an important step of building standalone applications using Compositor Software code, it became possible to organize the work of a new DRM server. That is, the physical server CP-6137-960FX began to be commissioned. As mentioned earlier, at the development stage it was possible to launch just one RAD36 virtual DRM server and it took about 4 hours to compile at runtime. This made it possible to provide up to 12 licenses for concurrent work of Compositor Max for Live or SASER Max for Live devices in the year 2017. Having exported the code and assembled 7 RAD36 virtual servers for the Windows platform independently of MaxMSP, we managed to start the workstation and successfully perform basic operations of text editing in Microsoft Word 2013 and working with Compositor Software Max for Live devices in Ableton 10 using it. It allowed expanding the total core density to 252 “Compositor” hybrid cores on a physical machine, increasing the number of simultaneously operating licenses of Compositor Software for Compositor Max for Live and SASER Max for Live up to 84 virtual machines, which equals 84 real-time cores or 84 three-layer cores. The uptime has increased significantly – the bootstrap process takes only 5 minutes to load CP-6137-960FX server fully. Niagara modem-radar and various Ethernet injections are used as an ignition, when workstation operates in Ethernet network.
Thus, the workstation converts Niagara injections and makes all server modes work, and there are currently 13 of them, including 7 RAD36 servers. Next, I’ll give a complete list of collected and working Compositor Software services for the Windows platform on the CP-6137-960FX server:
VoIP Service – NIM Chat Voice Service STC2k Service – Sonar for Civilian Control of underwater and surface ships RTC4k Service – Radar for Civilian Airspace Control RAD36 1-7 Services – digital rights management servers for launching Compositor cores (total of 252 hybrid cores). RAD96 Service – Standalone Rotator System for Docking RAD36 Virtual Servers RAD96 Ext. Service – expansion of the autonomous system for working with external Ethernet connections of third-party equipment Telescope Service – Telescopic Near Space Signal Approach Service
So, after the introduction of the CP-6137-960FX server into full operation, it was possible to provide working time for up to 84 Compositor users working in single-layer and two-, three-layer Compositor Software programs concurrently. In addition, this applies to standalone applications and Max for Live devices, such as Compositor Max for Live, SASER Max for Live and Compositor 4 Max for Live. I’ll also clarify that three aforementioned Max for Live devices are fully compatible with Ableton 10 and Max 8.1.3 Max for Live, which opens up the possibility of expanding the presence of Compositor users in NIM chat on MAC OSX and Windows platforms.
It took more than 1.5 years to work on solving the problem of Compositor AV Extended interface break-through (which is the main interface of RTOS). This problem occurred during the dial-up of routing tables for establishing a tunnel connection. The way to recreate it: first, RTOS protocols are dialed by injecting routing tables into them, and then RTOS interface is turned off and on again. When the interface turns on, the entire database of the routing tables, which fills the buffer, floods into the interface, which cause a man in the middle attack, that is, an attacker gained access to the interface and induced it to inherit the route of its device. During this time, I made emissions in an attempt to understand how to solve this problem and, finally, it is solved. Now it is possible to configure each protocol from the passive interface state and take a pause while turning interface off in order to listen to the remote channel, and then go into passive mode again. Thus, you can achieve resolution from each of the seven RTOS protocols.
In Compositor RTOS 9.0.2 a16 it is possible to set one interface identifier for the entire protocol configuration session, and to do the training only in passive mode, as previously assumed. The next task in debugging RTOS is the fight against constants. It is one of the most important tasks of both radio security and cybersecurity. Through the introduction of constants, Ethernet devices position themselves, occupying the most convenient places in the network topology. This mainly applies to devices that frequently change IP addresses, such as smartphones and laptops. In order for the RTOS core to take priority of the host, the device must serve as a host for many devices. This is confirmed by Compositor Software database, which has been expanded to 8156 management information bases (MIB). Now that the Compositor RTOS manages a database of more than 8,000 devices, CP-6137-960FX server can be considered as a host, regardless of its physical connection to the network, through the Internet service provider. In fact, what I’m doing now is the continuation of the development to include more VLAN’s and create a VPN network segment. In the latest build, I have already managed to “shoot” the packets in several sessions. You can hear one of them below:
This method of feeding wave tables is a priority for communication devices, because it helps to break the synthetic ether by packet transmission. Since there are many packets, and each of them carries different information at different moments of time, the semantic base of the Compositor RTOS language is explained. In view of this, it makes no sense to enter the names of packets in the main interface, and I need to leave them in a VRF tables section only, focusing specifically on the tunnel windows. In addition, this approach allows using the Compositor RTOS interface as a tunnel interface with the ability to connect to multi-channel protocols, such as OSPF.
All Niagara series products are the software modems, which use middleware and dump, produced in Compositor RTOS 9.0.2. I present to you Niagara 18 software modem, which has an extended documentation (part on Russian, part on English languages). Niagara 18 software modem middleware supports EIGRP, RIPng, BGP4+, OSPFv3 protocols, default route from EIGRP, full work in loopback interface mode, NTP-servers setup via command line interface, connection to VRF objects for work with BGP protocol, an ability to construct VLAN topology and 3D-orientation of virtual optical port (VOP) waveguide.
Niagara 18 software modem in front of Compositor RTOS 9.0.2 a12
Niagara 18 software modem, developed by Compositor Software, and modem,
developed for Ethernet and Wi-Fi networks, concept is different. For example,
Niagara 18 software modem doesn’t require the physical network connection. An
abundance of services, which enables the Niagara 18 software modem, compensates
the comprehensive demands to virtual communication networks. EIGRP, RIPng and BGP4+
routing protocols allow creating IPsec and GRE tunneling. An ability to use
synchro code of different NTP-servers allows rebuilding the home system on a
remote destination completely. Using this software modem, you can remotely use OSPFv3
without BGP4+ protocol that was unavailable before, due to physical limitations
of Ethernet systems. By entering the remote home system, you can aggregate the
shortest path of that area, which you are managing remotely. The route counting
performs in real-time that is why you can use IPv4 mask to set IPv6 addresses
of remote area devices. You can also multiplex areas, achieving the route end
by supernet aggregation, using VRF objects. Such approach can cause the
redistributed overloads without graceful restart (GR), because
Ethernet-interface uses only phase-locked loop.
VSF platform supports up to 960 simultaneous communication channels and can be reached via Niagara 18 software modem middleware. This number of channels was aggregated on CP-6137-960FX server VSF platform, which produced this middleware. This way, you inherit the number of channels from the server version, but they can’t be used all simultaneously. At the present moment, Niagara 18 software modem middleware supports up to 96 communication channels of L1, L2, L3 layers (OSI model). Niagara 18 software modem gives access to virtual optical network (VON), which consists of 2213 EB of information on the 6, November 2018. At the present day, this index is twice more. Information of VON is stored on servers in Spain, USA, Germany, Sweden and other countries of the world. Trunks of virtual optical communication connect the autonomous systems (AS). Most of the AS’s of VON can interconnect by BGP protocol. To form its own autonomous system Compositor Software uses Niagara 18 software modem with a set of 7539 VRF objects. The routing inside an area performed by OSPFv3 protocol to discover the routes by link state and by RIPng protocol for distance-vector discovery in IPv6 protocol. This way, Niagara 18 software modem is a complete IPv6 software modem back compatible with IPv4 protocol.
Niagara 18 software modem has middleware recorded without intermediate frequency in 150-350 GHz range (EHF) and works in that frequency range. To the day, this frequency range is not supported by any standards, such as 5G and forthcoming 6G networks. This frequency range supported only by satellite communication systems, such as radio telescopes. Niagara 18 software modem is accompanied by a set of 7539 satellite signals in PCM format, which gives access to autonomous systems. That is why you can rank Niagara 18 software modem as the satellite software modem. The connection to the Niagara 18 software modem network is performed in several dump submissions from 10 to 30 seconds. Niagara 18 software modem ether allows GR, which performed every minute to reveal active devices in remote AS. You can select such devices in a moment, when GR is performed as GR helpers. Each GR helper device subscribed on Niagara 18 software modem routing table updates. Niagara 18 software modem performs GR each minute to work under OVERLOAD conditions, which is set by default to test the saturation power of VOP.
The maximum transmission speed of Niagara 18 software modem is 24 * 350000000000 = 8400000000000 bit/s or 8.4 Tbit/s. Middleware and dump recorded at 192000 Hz 24-bit. Flow was recorded from 150-350 GHz frequency range and that is why I take the highest frequency in a moment of flow fixation and multiply it on the bit depth of flow export recording. This way, the moment of time exists for middleware, when this flow was in ether. Moment of time depends on the quantity of scanned autonomous systems. In hyperconverged networks, there is a trend to big trunks between AS areas, which span on many kilometers. That is why data flow in this AS can pass around for the time from 50 to 3000 ms, which is the boundary limits of Niagara 18 software modem. GRE tunneling is used for star topology AS’s and IPsec is used for point-to-point topologies. That is why, GRE performs its pass through the five boundary points of the route and IPsec connects only to the Area Boundary Router (ABR) of OSPF area. That is why, when you use GRE tunneling, feedback loops emerge, if your loopback interface of VOP is set to the same port as the destination port of AS. Such loops can exist for a long time and packets forward between loopback interface and AS loop.
When you use software compensation of feedback loops the decay of data flow carrier signal performed, lowering the ingress que and discarding the packets. Saturation of carrier signals, encased in window function is so high that ingress load redistribution can’t cope with such amount of data flows. In this situation, Niagara 18 software modem performs multicast translation on group of ports. You can reach this by setting AS, which consists of several topological areas, connected by different protocols. This way, ABR’s will perform redistribution of one protocol in another. You can learn information about ingress port of system by changing the egress port, setting eye-mask on 0 (turning RTOS off) and perform GR of all the devices, connected to that port. By making GR of the boundary device and not the Niagara 18 software modem, you can estimate the number of channels, connected to ABR, which in turn can lead to connection with those devices. This way, you perform the redistribution of local que on remote devices.
As mentioned earlier, Niagara 18 software modem makes connection to 7539 AS’s
to the day, however the summary aggregation of VON is 3321900 autonomous
systems. This way, dump allows connecting not only to those AS’s, which
recorded in it, but to discover other AS’s using BGP protocol, which were
scanned by VSF platform. The connection to satellite set is performed faster,
than in software modem produced in Compositor Hypervisor 9.0.1 a15. It has the
connection speed of 24 frames per second, but Niagara 18 software modem has the
speed of 34 frames per second. Such speed of deployment allows multiplexing a
network much faster, performing supernet summary in 3-6 dump rounds.
Niagara 18 software modem is a sampler technology, that is why it performs
the cycle of Compositor RTOS 9.0.2 a11 feedback loop, where a dump is the
recording of VSF platform data flows aggregation of that RTOS. Niagara 18
software modem is based on the identity principle and uses PCM recording as a
middleware, which doesn’t consume many resources. CP-6137-960FX server consumes
up to 35% using 192000 Hz discretization frequency. Which theoretically can
allow using it in real-time on the higher discretization frequencies. Niagara
18 software modem consumes little system memory resources and has very fast
response to CPU commands speed. It has a little delay time, which allows using
it as a hard real-time RTOS.
You can setup monitoring of Niagara 18 software modem via amateur radio
software such as TrueTTY and Fldigi. The teletype network flow modified by
Niagara 18 software modem includes satellites and servers of Compositor RTOS
9.0.2 a11 management information base. You can composite commands of interface
and protocol programming, such as CISCO-like commands. There is a documentation
supplied together with Niagara 18 software modem of 2663 pages, with Russian
language translated part of more than 1000 pages, spanning over 5 parts with 73
chapters of 131 chapters in total.
There are no obstacles for VON in comparison to traditional radio communication. Radio notation in conventional frequency style is made for notes and reverse compatibility with generic radio protocols. The connection is made via so-called collisions and time-space convolutions, which is a subject of NIM (Nuclear Instrumentation Module) learning curve, to which Niagara 18 software modem relates.
Dear reader, it is time to report the coming changes in Compositor Software
project. For the five years, I performed the comparison of telecommunication industry
technology and the one developed by me. Here what I’ve already found:
Compositor Pro = NTP-server
Compositor Max for Live = SNTP-server
Accordingly, Compositor Pro and Compositor Max for Live will be reworked to reveal this paradigm. There are 24 official UTC time zones as well as 24 bands in Compositor Pro and Compositor Max for Live. The function by which these bands are distributed is time-invariant non-linear function (read the full documentation here). Therefore, bands of Compositor are time zones. Stratum parameter of NTP-server is permutation. There are 12 Stratums in my NTP-server. Using kick parameter, you can set subnetwork mask. This parameter, together with clap and hat, forms modulation, which installed in parallel to time zones deployment tempo.
NTP-server can create time collisions by granulating the central flag of
modulation interrupter. When injected collision comes to the input of the
receiving device, this device establishes a connection with NTP-server and
takes its synchro-code, which is translated by sub-bass instrument. It is the
modulation interrupter flag. The mangling takes place in time component, which
is the time-displacement (substitution of time).
Tempo is the first octet of IPv4 address, and multiplier forms the next three octets. There are only IPv4 addresses in NTP-server. NTP-server doesn’t have access to broadcast addresses and to an address of local machine, but uses the range of 54.1.54.0 to 140.3.0.0. Therefore, the role of Compositor Pro was to install the stochastic distribution with the route of 120.1.54.0 to 120.2.24.0 and to perform collisions with the devices of that range.
The reason I made the NTP-server is “creation of artificial intelligence using non-invasive method”. By this, I mean active use of ACL lists and flows filtration when loading Ethernet servers (kernel extensions, which are recorded in MIB’s database of Compositor Software). Compositor Software clients produce traffic when working with software, which is exported into flows, using the half-duplex MDL12 modem. These flows contribute to device pool of Compositor RTOS kernel extensions.
An enormous work was conducted this weekend on MIB vector optimization. At the beginning the full base was defragmented by clearance of the dump below:
RTOS dump at 192 kHz MIB 5149 08.06.2019
In addition, the switch to 11 kHz was made and stochastic selections were
performed in a special edition of RTOS with a direct output on auxiliary
channel (through). Later these ethers were recorded as middleware with PCM WAV
container of 24-bit 11 kHz. You can listen to them lower:
16 middleware files were recorded, here I show you only the four. Then these middleware was filed to the special version of L1-L4 L6-L7 vRouter RAD96, which uploaded it on 96 destinations of L1-L3 layers. This way, the middleware was fixated. This method is different from direct submission to RAD96 master routing table, because RAD96 ether aggregator can exclude the predefined set of ether combinations and I was needed to attain to precise channel matrix of 52 channels.
After the full contact base was uploaded by stochastic selections of MIB5149 and dump, I made RTOS authorization again but this time mangling the sample rate parameter up to 192 kHz. This way, I updated links to all aliases and authorized the whole MIB on 192 kHz.
