mirror of
https://github.com/TelegramMessenger/tgcalls.git
synced 2026-11-18 21:35:28 +00:00
The server's v8 + v14 A/B serves 14.0.0 to one end of a call and 8.0.0 (InstanceV2Impl) to the other. Each end picks its signaling framing from its own version string and nothing in-band names the peer's, so CompatImpl ran 13.0.0's framing (gzip over SCTP) against 8.0.0's EncryptedConnection reliable messages: no message crossed either way. All 200 not_inited calls of the 2026-11-06 production sample had that shape (the CompatImpl side logs PARSE_FAILED for every peer packet, the 8.0.0 side "Bad incoming data hash"). 14.0.0 now maps to 8.0.0's framing, so it runs the compat:8.0.0 path, including the two V2-only fixes (the resend-timer service packet and the post-answer offer hold). network_kcp_experiment still moves any version to 13.0.0's framing, which is how a 14.0.0 end talks to a 13.0.0 one. A 14.0.0 build without this change fails against 8.0.0 and against a 14.0.0 build with it, so the server must serve 14.0.0 only to builds that have it. The map moves to v2/CompatSignalingFraming.h, pinned by a host test (compat_signaling_framing_test in the superproject's BUILD: red on the 14.0.0 line before the change). run-parity-tests.sh takes -c SPEC to run CompatImpl's ends under another version string. Verified with tgcalls_cli p2p: 14.0.0 -> 8.0.0 and 8.0.0 -> 14.0.0 (audio, --video, --video-late with 100-300 ms delay, 30% signaling loss 6+6 runs, network_use_mtproto), 14.0.0 <-> 14.0.0 (audio, --video, --video-late, with 30% loss), 14.0.0 <-> 13.0.0 under network_kcp_experiment, compat:13.0.0 -> 13.0.0: all connected with media both ways, 0 PARSE_FAILED, 0 bad hash. 14.0.0 <-> 13.0.0 without the flag fails as expected. run-parity-tests.sh -c 14.0.0 (528 calls) against 8 <-> 8: no failure without loss; at 30% loss 1-2 per pairing (p >= 0.25); cameras mid-call at 30% loss, the caller gets no video in 27/48 (8 <-> 8), 17/48 (14 as caller), 0/48 (14 as callee). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>