
This maintenance release is available on the stable channel for appliances on the 0.8.6 line.
Enhancement: Policy History follows your time zone. Days in Policy History now start and end at midnight in your organization's time zone instead of UTC. The default 24-hour view also moves forward each time you change a filter, rather than staying fixed at the moment the page opened.
New feature: Tab completion for the ct command. Press Tab to complete commands, options and app names, with a short description for each option. Updating installs it for bash and zsh and reinstalls it if it goes missing, and ct doctor reports whether it is working.
Fix: Appliances with very large policies (1,000+ rules) stay up under load instead of running out of memory.
Fix: Call routing keeps working while live debugging is on, and post-call actions are no longer skipped.
Fix: Policy History charts place calls in the correct hour and day, and filtering by app action finds the matching calls.
Fix: Calls without caller ID display correctly in policy analytics, and the TDoS overview updates when you change filters.
Fix: Large uploaded CDR and CMR files import reliably, and faster.
Fix: JTAPI phone control keeps running when an optional JTAPI feature fails to start.
Fix: E911 bulk address imports show which rows failed, and a switch can only be assigned a saved address.
Fix: CUCM log collection resumes after an interruption, and AXL query errors explain what went wrong.
Fix: ct health --wait waits until the appliance is actually ready, and ct app up is safe to run on a stack that is already running.
Fix: LDAP sign-in says clearly when no matching user exists. The update check stops flooding logs with certificate errors, and the update screen says when it is showing fallback release information.
Security: LDAP sign-in safely handles special characters in user names.
Security: SMTP passwords are no longer returned by the API or shown in settings.
Security: A development certificate key is no longer shipped in the web image.
Security: Logs and error messages no longer include sensitive values.
Security: Resolved CVE-2026-14456 (High): updated libcrypto3 3.5.7-r0 to 3.5.8-r0 and libssl3 3.5.7-r0 to 3.5.8-r0 in the prometheus-nats-exporter image.
Update with:
sudo curl -fsSL https://get.calltelemetry.com | sudo sh -s -- update stable