Every Kahevo now runs the Kahevo Rust Engine, on servers and branch boxes alike, with nothing to switch.
Three days ago the Kahevo Rust Engine went into production beside the engine Kahevo started with, and each server and branch office chose between them with a switch. From this release there is no switch. Kahevo Legacy is retired, and every Kahevo runs the Rust engine.
What changes for you
| Before | Now |
|---|---|
| A switch on the Settings page | The page simply says the Rust engine is running |
| A switch on each branch office's page | Every branch box uses the Rust engine |
| Two sets of figures for a branch box | One: 130 to 200 calls at once on a four-core mini PC |
| A third-party SIP library shipped with Kahevo | It is gone; Kahevo's own engine does the work |
Why now
The Rust engine carries the whole call: setting it up, its audio, encryption, browser and app calls, and joining the two sides. It does that on less than half the processor the old engine needed, and without the pauses for cleaning up memory that the old one had. Keeping two engines meant testing everything twice and choosing every time. Choosing once, for everyone, is simpler and safer.
It also means Kahevo no longer depends on a third-party library whose license terms could change under us. That was one of the reasons we wrote our own engine in the first place.
Upgrading
Update the SIP service and every branch box to this release. The engine comes with Kahevo and must be beside the program, or the service will not start, and it says so in its log. A branch box on an older release is told by the main office to switch to the Rust engine for its next call. The Settings page warns, in bold, about any service still on the old engine.
The honest part
The Rust engine is in production, but this release, with no fallback, is new. Update a test system first, check that calls connect and that the Settings page says what you expect, and keep a snapshot to go back to.