--- title: "2.2.x.x Release notes" slug: "22xx-release-notes" updated: 2026-10-23T19:00:30Z published: 2026-10-23T19:00:30Z canonical: "docs.telosalliance.com/22xx-release-notes" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt > Use this file to discover all available pages before exploring further. # 2.2.x.x Release notes ## Version 2.2.21 10/21/26 - Ticket 26493: Long form responses to LWCP commands (pathfinder will issue at connect time) would crash the Altus application. A regression introduced due to updated build system. ## Version 2.2.20 10/2/26 - Ticket 26433: Healthcheck issue regarding localhost vs 127.0.0.1. Localhost can resolve to IP6 in some systems and resolve to unhealthy state. ## Version 2.2.19 9/2/26 - Ticket 26317: Resolved an issue with failed negotiations with WebRTC monitoring, introduced in 2.2.11. ## Version 2.2.18 8/25/26 - Ticket 26293: Resolve backend fault, introduced in 2.2.11, which impacted the License page on Altus SE. No change to Docker deployments. ## Version 2.2.17 7/29/26 - release - Ticket 25968 : Logic Profile not included in backup - Ticket 26118 : Normalize webRTC server config entry. Previously didn’t want “https:” text and would result in failed connection. Now will support the URL or the server path - Ticket 26018 : Introduce option to ignore a built in safety for same source load when ON within the override active channel function. - Continued effort to resolve scanner flags ## Version 2.2.11 6/10/26 - Update base OS and curated runtime artifacts for WebRTC to avoid vulnerabilities introduced in package-level plugins. ## Version 2.2.10 6/9/26 - Introduce dynamic amount of meters on meter bridge to manage smaller width conditions (e.g. when only 4 faders are enabled) - Ticket 25997 : incorrect loading of Logic Profile on page refresh. - CVE-2021-44906 - CVE-2022-2421 ## Version 2.2.9 5/14/26 - Ticket 25922 : Resolves a buffer overflow possibility when Logic Profiles are defined and a threshold amount of Source Profiles are defined. The overflow would lead to system crash. ## Version 2.2.8 5/4/26 - Ticket 25935 : Regression issue introduced in 2.2.1 which impacted advertisement data. Impacts a system if there were more than a single Altus within the system. Issue could lead other host system to interpret the advertisement data coming from a single Altus and not each individual Altus. ## Version 2.2.7 4/30/26 - Discovered uninitiated variable that could introduce a crash which was hidden by a bug that prevented link information for channels to be reported in command protocol. - link (webRTC) information now reported on a per channel basis for future use. ## Version 2.2.6 4/22/26 - Ticket 24338 : Changing an output would restore default names of outputs that followed, only applied to webRTC outputs. - Ticket 25877 : Add option to force host mode sync. Resolves issue when other methods are present, host mode sync was not possible. ## Version 2.2.5 4/2/26 - Ticket 25801: Regression with NDI discovery config resolved - Ticket 25549: Word spelling issue on config page ## Version 2.2.3 3/12/26 - release - Ticket 25693 : Resolve monitor source select disable in show profile ## Version 2.2.2 10/21/25 - release - Ticket 24994: Resolve quantity of numbers accepted into VX dialer - Ticket 24823: Support real time interface switching for AoIP traffic ## Version 2.2.0 8/20/25 -release - Licensing fix that allows for proper refresh of status on changes in server - Introduce Logic Profiles