
This maintenance release is available on the stable channel for appliances on the 0.8.6 line.
Upgrade behavior change: CallManager phone web scraping now honors the Enable phone query setting. That setting defaults to off, so after upgrading, CallManagers without phone query enabled no longer scrape phone web pages for neighbor (CDP/LLDP) and serial details. AXL, RIS and Extension Mobility discovery are unchanged. To keep phone-page enrichment, enable phone query on each CallManager.
No enhancements in this release.
Fix: End-user sync from CUCM no longer logs duplicate-insert errors when two sync batches update the same user at the same time. The synced user data was already correct; the conflicting write is now skipped instead of reported as an error.
Fix: Network page discovery no longer logs warnings when IPv6 is disabled or absent (such as 0/ prefixes), reserving warnings for genuinely malformed subnet values.
Fix: DIME CDR backfill classifies CUCM job not found responses as a distinct, terminal job-not-found outcome rather than retrying as a generic failure.
Fix: Watch list violation lifecycle seeding now links blocked call events to the violation, ensuring blocked call counts accurately reflect blocked attempts.
Fix: Missed-call deduplication is now scoped per organization, preventing missed calls in one organization from suppressing notifications in another.
Fix: CUBE details and updates are now restricted to the owning organization; previously a request could read or modify a CUBE belonging to another organization.
Fix: CUBE update requests now accept flat request bodies without a nested wrapper, returning a valid update response instead of an error.
Fix: Emergency location report routes now restrict operations to available actions, preventing errors when requesting individual report details.
Fix: System performance monitoring uses growth-based alerting for BEAM literal allocator usage, eliminating false-positive error-level alerts under normal memory allocation.
Security: Updated com.google.guava to 33.7.2 in the JTAPI sidecar, addressing CVE-2026-102554.
Trivy 0.74.0 scan of the shipped linux/amd64 images for 0.8.6.33. Scan date: 2026-11-09 (UTC). Trivy vulnerability database: 2026-11-08 (UTC). Counts are Critical and High findings in the image scan. The full per-container report is at https://docs.calltelemetry.com/releases/scans/0.8.6.33-trivy-scan.html. | Image | Tag | Digest | Critical | High | | --- | --- | --- | ---: | ---: | | `alertmanager` | `v0.34.2` | `sha256:39d8bb3966c694a124428a3a88fbcffd40bd069129ecd47c059f8a3f17c55f3b` | 0 | 2 | | `alloy` | `v1.21.3` | `sha256:8ab871206bd2d8f89277f53abffee5f452a293980788d52f85fa183a87a505a4` | 0 | 3 | | `appliance-mcp` | `1.2.3` | `sha256:ae31842cdf522e349e25f5a91f9c0b65519e8b0d658a5079b0f42e490660dbfe` | 0 | 0 | | `caddy` | `2.11.8-alpine` | `sha256:f6228111e5fafa1a5238258d0858e103f10599b8d1659a146e7726681a002bb9` | 0 | 3 | | `ct-media-go` | `1.5.14` | `sha256:e8401cffa3969fd6b50d8206dced5b1a2d1b67cdc4e7f4dda18c6e85f642a8d6` | 0 | 46 | | `ct-syslog-ingest-go` | `1.1.8` | `sha256:08f8a932a76a8c709ad42bb08b18d88a8e0c5572d07f87d53495f00ecc1db21e` | 0 | 0 | | `grafana` | `12.4.14` | `sha256:ae509d9ae8c1021ca32ec370a9ca975d40165eda9fccd1e1102d317ff8787cd7` | 0 | 4 | | `jtapi-sidecar` | `0.8.7-beta-e5680d4685a2` | `sha256:61134a54673f3ef0148d04de693829c25ea9d381f161509787250362eea884ad` | 0 | 0 | | `loki` | `3.7.9` | `sha256:0db216b630ae1f348a1584c67f3cead8b4c1fc839169a39501db664744158e28` | 0 | 1 | | `nats` | `2.15.2-alpine` | `sha256:823e7f1d6d8ffe3b30dbd73d4a06bbb939acf94929f7fdf224404da7a05bafb5` | 0 | 0 | | `node-exporter` | `v1.12.1` | `sha256:1b4e4438faca4dd7e001dd445d161a4a2091b0fededa84093b3a8dfeae1f1be0` | 0 | 16 | | `opentelemetry-collector-contrib` | `0.165.0` | `sha256:e40d61f10c9a617cca1ffd1be4d7e2b3a4b0f0001798ff07e58cabe82e618cea` | 0 | 0 | | `postgres-14` | `14` | `sha256:0cc1fe2fb53fba71f11dde77206fda6e04d3bf7bfb6869013d9219a7bbe4a4ff` | 8 | 63 | | `postgres-18` | `18` | `sha256:602a442f31124465cb0c51b0aee82c413fa6a4631e7080bb645c008a0bebd88f` | 8 | 63 | | `postgres-exporter` | `v0.20.1` | `sha256:ac5ec343104fae0e2d84a27bb8d69b38430a11910c5382cad85d478d2bab713e` | 0 | 19 | | `prometheus` | `v3.15.1` | `sha256:fa3302279710be2f21a8301ec17a8b4f2301fd829bd113839b3b6b02b6f191a2` | 0 | 2 | | `prometheus-nats-exporter` | `0.20.3` | `sha256:4b8ddc1c86fec360b5cd3d5e1fbc6fb52bdafd5805bba3901cc52926538af255` | 0 | 3 | | `seaweedfs` | `4.52` | `sha256:57877e32bb90073b37dc109b438ba66e84fd5ed9ced5f5c04f56444ef243ce59` | 0 | 1 | | `tempo` | `3.1.1` | `sha256:64e2fbd56d9c2b3412a4b430a58ea59e91a670b1e75f920a0c702213ad145044` | 0 | 2 | | `traceroute-go` | `1.4.11` | `sha256:922a1432ca71fa4c1b53faa792d8811ed01ae869fcbaf168b5ff68647dac5d1a` | 0 | 48 | | `vue` | `0.8.6-stable-035c35895cef` | `sha256:ba1e5399bfb8e7eb374a0593b7b044ac4ab6a05d9de3de213b8d4cb630c001c6` | 0 | 0 | | `web` | `0.8.6-stable-36bf85592569` | `sha256:7a4ef3adcb8625af8f7ce346b34000f33a2ca80a401eafab61bbcae976a1f95c` | 0 | 0 | The `web` image Trivy scan is listed above. A supplemental Elixir audit of that component also reported 3 Critical and 6 High findings, which are not included in the Trivy counts. Those findings are in the full report.
Update with:
sudo curl -fsSL https://get.calltelemetry.com | sudo sh -s -- update stable