Skip to main content
Version: 0.9.16

Release compatibility

Every Delphi release is delivered as a single version. When you set that version for your deployment, all of the platform's services are designed and tested to run together — you never mix versions between services. Upgrading is simply moving your deployment from one release to the next.

This page is about how the platform's own services fit together across releases: which releases are available, which one to run, and which services changed in each. If you build voice apps on the client SDK, see SDK compatibility for how SDK versions line up with platform versions.

Releases​

ReleaseReleasedStatusWhat it delivers
v0.9.17latest patch: v0.9.17-patch2September 2026CurrentSuper Viewer, speech detection and Silero VAD, per-app recording artefacts, hangup and transfer SIP signaling, max call duration, seven.io SMS, and hidden production Swagger. Patch 1 improves audio startup, SIP header preservation, edge trunk probes and diagnostics. Patch 2 reduces idle edge reconciliation work, fixes structured application-ID searches and trunk probes, and closes audit-display, redaction and empty-severity gaps. It also improves targeted AI flow edits, sandbox validation, realtime transcript timing and consistent error alarm attributes. Release notes
v0.9.16latest patch: v0.9.16-patch2you are reading these docsJuly 2026SupportedMicrosoft Entra SSO, Super Admin hardening, config versioning and backups, SIP trunk health monitoring, API credential jail, TOBi sensitive storage and DTMF improvements, and TelPhi SDK 0.1.4. Release notes
v0.9.15latest patch: v0.9.15-patch4July 2026SupportedCustom deal subscriptions, platform-secret edge TLS with rolling service refresh, TOBi application metadata, TTS character usage reporting, and autoscaling hardening. Release notes
v0.9.14latest patch: v0.9.14-patch3June 2026SupportedFull TelWeb internationalization, layered resilience defaults and bot-delay handling, new voice providers, hard account lockout, TOBi DTMF controls, API access gating, and broader observability and operations controls. Release notes
v0.9.13latest patch: v0.9.13-patch3June 2026SupportedManaged telephony actions, Flow Builder rollback and checkpoints, security/session hardening, billing improvements, richer SIP observability, and a dedicated migration container. Release notes
v0.9.12latest patch: v0.9.12-patch1May 2026SupportedOperational reliability and workflow polish: TelAPI health checks, Flow Builder version cleanup, TOBi webhook hardening, and separate database and Redis TLS trust bundles. Release notes
v0.9.11May 2026SupportedIntroduces the AI Flow Builder, upgrades the voice stack to Asterisk 22.9, broadens AI provider support, and adds managed billing. Release notes
v0.9.10latest patch: v0.9.10-patch1April 2026SupersededEarlier 0.9.x release. Superseded by v0.9.11; upgrade when convenient.

Which release should I run?​

  • Run the release marked Current. It is the newest tested release and gets the latest fixes.
  • If your release line has a latest patch, apply it — patches contain fixes only and are always safe to take.
  • Supported releases still receive critical fixes, but plan to move to the current release.
  • Superseded releases are no longer updated; upgrade when convenient.

What changed in each release​

A release upgrades every service together, but not every service changes in every release — many are carried forward unchanged. The table below shows which services got a new build in each recent release. To pick up a particular service's update, run at least the release where it last changed.

Servicev0.9.17-patch2v0.9.17-patch1v0.9.17v0.9.16-patch1v0.9.16v0.9.15v0.9.14-patch3v0.9.14-patch1v0.9.14v0.9.13-patch3v0.9.13-patch1v0.9.13v0.9.12-patch1v0.9.12v0.9.11Last updated in
TelProTelephony / WebRTC gatewayUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdated·UpdatedUpdatedUpdatedUpdated··Updatedv0.9.17-patch2
RTPEngineMedia proxy·Updated·UpdatedUpdatedUpdatedUpdated·Updated······v0.9.17-patch1
WebRTC (Janus)Browser-to-SIP bridge·Updated··UpdatedUpdatedUpdated·Updated······v0.9.17-patch1
TelSysAsterisk PBX·UpdatedUpdated·UpdatedUpdated··Updated··Updated··Updatedv0.9.17-patch1
TelPhiAI conversation engineUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedv0.9.17-patch2
AudioProcAudio processing·UpdatedUpdated·UpdatedUpdatedUpdated·Updated······v0.9.17-patch1
TelAPIAPI / WebSocket serverUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdated·UpdatedUpdatedv0.9.17-patch2
TelWebManagement dashboardUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdated·UpdatedUpdatedv0.9.17-patch2
Media serverTTS media cache·UpdatedUpdated·UpdatedUpdated··Updated····UpdatedUpdatedv0.9.17-patch1
ScalerAutoscalerUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdated·Updated··Updated·UpdatedUpdatedv0.9.17-patch2
TaskerBackground jobsUpdatedUpdatedUpdated·UpdatedUpdatedUpdated·UpdatedUpdated·Updated·UpdatedUpdatedv0.9.17-patch2
DB migrateOne-shot migration and release seedingUpdatedUpdatedUpdated·UpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdatedUpdated···v0.9.17-patch2
Log-to-spanStructured SIP log to OTLP span bridge·UpdatedUpdatedUpdatedUpdatedUpdatedUpdated····Updated···v0.9.17-patch1

Updated means the service got a new build in that release. To pick up a service's update, run at least the release where it last changed (the Last updated in column). Services with no recent change are carried forward unchanged and need no action.

See also​

  • Release notes — what changed in each release and the upgrade checklist.
  • SDK compatibility — how client-SDK versions line up with platform versions.
  • Version sources — the upstream component versions bundled in a release.