Call Telemetry
Call Telemetry
  • Docs
  • Changelog
  • Feature requests
  • Support portal

Call Telemetry changelog

0.8.6.6 Stable Changelog

This maintenance release is available on the stable channel for appliances on the 0.8.6 line.
This release consolidates the validation work from the 0.8.6.6-rc* release candidates into a single stable build. It is a maintenance release focused on database upgrade safety, management API reliability, policy reporting, licensing, and Cisco integration tooling.

Enhancements

  • Enhancement: Optional org-level diagnostics: appliances can forward backend error telemetry and alarm-lifecycle events to a PostHog project for support correlation. Off by default; opt-in per org.

Fixes

  • Fix: Added missing stable database migrations for Grafana settings, alarm preferences, token sessions, and per-user alarm sound settings. This fixes upgrade/runtime crashes caused by missing database fields.

  • Fix: Several management API endpoints now return proper 404 or 422 responses instead of 500 errors for edge-case requests, including rules and policies, TDoS history, webhook logs, phone statistics, report queries, and CallManager discovery.

  • Fix: Policy history dashboards and reputation reporting paths refresh correctly after fresh install or upgrade.

  • Fix: Active product licenses are preserved across transient license-server validation failures instead of briefly dropping to an unlicensed state.

  • Fix: Cisco integration workflows are more robust: AXL/JTAPI errors return clean payloads, JTAPI BIB/greeting rollback and audit metadata are safer, runtime-created lab CallManagers surface inventory correctly, and SFTP session ownership is preserved.

Update with:

sudo curl -fsSL https://get.calltelemetry.com | sudo sh -s -- update stable