Vodia Monitor 1.0.0
Release Date: April 2026
The first official release of Vodia Monitor — a self-hosted fleet monitoring platform for Vodia PBX systems.
Highlights
Fleet Overview — At-a-glance status across all PBX servers with version, uptime, license expiry, active calls, tenant/account counts, disk usage, and port health on every server card.
Tenants & Accounts — Full breakdown of every PBX domain and account type across the fleet, including extensions, queues, IVRs, auto attendants, ring groups, paging groups, park orbits, service flags, and conference rooms.
Port Monitoring — Continuous HTTP, HTTPS, SIP-UDP, and SIP-TLS connectivity checks with per-port response times and configurable poll intervals per PBX.
Certificate Monitoring — TLS certificate tracking with expiry dates, chain validation, per-tenant enable/disable, and on-demand manual checks.
Trunk Status — SIP trunk registration monitoring across all tenants and PBX servers with per-trunk detail, type filtering, and a call simulator.
Uptime Tracking — Per-server, per-port uptime percentages with hourly heatmaps and a full downtime event log. Supports 1h / 6h / 24h / 7d / 30d views.
Rankings — Fleet-wide comparative charts across account types (extensions, queues, IVRs, attendants) and system metrics (peak calls, registrations, CPU, memory).
Blocked IPs — Real-time PBX blocklist with country attribution, connection logs, and all-time historical totals across the fleet.
Alerts — Critical event notifications for port outages, registration drops, and certificate issues. Supports auto-resolution, manual acknowledgement, and notification via SMTP, Twilio SMS, and PagerDuty.
History — Fleet-wide configuration change log and admin login audit trail pulled from each PBX.
AI Health Summary — One-click fleet health reports via OpenAI, Anthropic Claude, or Google Gemini, with key observations and recommended actions.
Multi-PBX — Monitor any number of Vodia PBX servers from a single Vodia Monitor instance. Each PBX has independently configurable poll intervals.
Security — AES-256-GCM encryption for all stored credentials, WebAuthn passkey support, JWT authentication, and MongoDB/Redis authentication.
Vodia Monitor 1.0.1
Release Date: May 2026
What's New
Custom Port Numbers — Each PBX can now use non-standard port numbers for HTTP, HTTPS, SIP-UDP, and SIP-TLS monitoring. Custom ports are configured per-PBX directly from the PBX Management page alongside the existing port enable/disable toggles. All views — Port Status, Uptime heatmaps, Fleet Overview badges, and alert messages — reflect the actual port numbers in use. Defaults to standard ports (80, 443, 5060, 5061) when no custom value is set; fully backward compatible with existing PBX configurations.
Trunk Monitoring Improvements — Fixed an edge case in global trunk status detection where trunks with non-standard registration states were being misclassified. The trunk monitor now handles these states correctly, ensuring accurate fleet-wide trunk health reporting.
Version Display — The current version number is now shown in the bottom-left corner of the sidebar for quick reference.
Trunk Snapshot Cleanup — Trunks deleted from a PBX were previously displayed in the Monitor indefinitely, since the dashboard query had no staleness filter. The Trunks page now excludes any snapshot not updated within 48 hours, so removed trunks disappear automatically on the next poll cycle. A TTL index was also added to the trunksnapshots collection to automatically expire records older than 7 days, preventing unbounded collection growth.
Installation
Requires Ubuntu 24.04, a domain name, and under 10 minutes:
apt-get install -y wget unzip
wget https://cdn.vodia.net/vodia-monitor/vodia-monitor.zip
unzip vodia-monitor.zip
cd vodia-monitor
sudo bash install.sh
Upgrading
cd vodia-monitor
wget https://cdn.vodia.net/vodia-monitor/vodia-monitor.zip -O vodia-monitor-update.zip
unzip -o vodia-monitor-update.zip
cp -rf vodia-monitor/* .
rm -rf vodia-monitor/
rm -rf vodia-monitor-update.zip
docker compose build --no-cache
docker compose up -d
Database migrations run automatically. No data loss.