The customer calls first
A trunk silently degrades the ASR from 90% to 70%. Global thresholds never see it. The ticket arrives from the client, not from monitoring — with the SLA already expired.
It does not just capture your calls. It watches them, investigates anomalies on its own, explains the root cause, and alerts your phone with action buttons. Acknowledge, resolve, investigate deeper, or approve a safe remediation. Every resolution makes the next diagnosis smarter.
curl -fsSL https://raw.githubusercontent.com/VoxyWatch/publish/main/install.sh | sudo bash Works out of the box with
Run the live demo, price the deployment, install the free tier, or ask Voxy AI which route fits your network.
Every minute it takes you to detect a voice quality problem is a minute your customer is already considering leaving.
A trunk silently degrades the ASR from 90% to 70%. Global thresholds never see it. The ticket arrives from the client, not from monitoring — with the SLA already expired.
Wireshark, grep in SBC, manual captures and correlation by hand. Each incident burns up senior engineer hours while traffic continues to fail.
Without evidence of your own, the diagnosis ends in a ticket with the manufacturer of the SBC. Days of waiting, generic answers and zero control over the timeline.
Carrier A or Carrier B? Destination or route? Without attribution by trunk and by country, conversations with suppliers are competing opinions, not evidence.
Actions are executed only after your approval — and the AI has no tools to change your network. By design, not by promise.
The multi-agent harness is based on Google Agent Development Kit (ADK): an orchestrator coordinates specialists for SIP, fraud, Flash Calls, traffic, platform health and releases.
Each anomaly becomes a persistent incident with a lifecycle (open → recognized → resolved), deduplication, auditable timeline and self-resolution for stability. Dedicated Incident Tab with one-click actions.
As soon as you open an incident, VoxyWatch investigates on its own: sample failed calls, dominant SIP codes, failing IP routes, and whether other trunks were degraded as well — the local-vs-carrier signal. Using your LLM key, write down the probable root cause citing that evidence.
Critical incidents arrive on your phone with the attached diagnosis and inline buttons: Recognize · Resolve · Investigate · plus proposed remediation when applicable. Each portal user links their own chat with a single-use code. Each action audited by real user, restricted by role.
Includes field runbooks that the researcher follows and cites step by step — add your own as JSON. Resolved incidents become institutional memory: “same as incident #123, resolved: carrier maintenance.”
CRITICAL must be earned: minimum sample, measurement coverage, deviation from the core's own baseline, sustained degradation. Validated with production data: −92% false critical noise.
Audio retention is measured, not estimated — capacity incidents open before you run out of space. A daily/weekly digest arrives at Telegram or your webhook according to the calendar.
The proposed actions come from a closed catalog at the code level (restart the capture sniffer, recalculate baselines — never your SBC), are executed only after your tap, and remain in the timeline of the incident with who-approved-what.
Find automation and abuse patterns from the signaling you already capture, without depending on the SBC brand.
Detects probable missed-call authentication patterns from originator CANCEL timing, 487 responses, no-answer/no-media evidence and destination fan-out.
Surfaces new destinations, high-risk country growth, short-call storms, velocity changes and international-mix anomalies with evidence by trunk.
VoxyWatch observes and explains. It never blocks, reroutes or controls the SBC.
Carriers, ITSPs, UCaaS providers, and voice integrators. Vendor-agnostic, multi-SBC, self-hosted.
A NOC view of every interconnect: ASR/NER by route, anomaly detection by trunk, and 5xx spikes flagged as they happen.
Visibility by customer, quality by destination, carrier attribution via ITU-T E.164, and audio evidence when you need to prove what happened in a call.
Auditable voice quality by tenant: MOS, jitter, packet loss, and PDD. Detect degradations before customers escalate.
Diagnose calls without escalating to the SBC vendor. Incident analysis with evidence across multiple platforms.
Capture, attribute, learn and explain — all in a single self-hosted binary.
Two ingestion paths: HEP v1/v2/v3 (tested with Asterisk, Kamailio, OpenSIPS, FreeSWITCH, RTPEngine, Sansay) and a native SIPREC recording server in beta (Oracle, Ribbon, AudioCodes, Cisco CUBE) — plus the included voxywatch-probe (Go + libpcap) for everything else.
Load your trunks only once. Each call is attributed to its carrier by IP/CIDR and to its destination country via an ITU-T E.164 engine with longest match (197 codes). ONNET traffic marked separately.
Each trunk learns its own normal (mean ± σ per hour). Detects silent drifts that global thresholds miss — like a ASR dropping from 90% to 70% on a single carrier.
Co-pilot by trunk and summary: reads health + baseline + 48h trend, returns probable cause and action for NOC. Works with OpenAI, Anthropic, Gemini or OpenRouter. Never touch the SBC.
Integrated SNMP v2c/v3 agent with 30+ OIDs and traps per edge for capture loss, sniffer down, low ASR/MOS, disk/CPU/RAM pressure. Downloadable MIB. Integrates with PRTG, Zabbix, Nagios.
Self-hosted with PostgreSQL/TimescaleDB. Your hardware and traffic data stay under your control. Optional diagnostics can be enabled or disabled by the customer.
Upload chan_sip, PJSIP and dial-plan files, preview detected trunks and merge only after operator review.
Export SIP findings, DTMF evidence, PCAP and a bounded anonymous call-share bundle without exposing raw traffic or full identifiers.
Per-user chat history and context, provider choice, refresh controls, token budgets, routing, caching and optional offline Batch.
An ADK-based harness coordinates seven specialists and seven operational runbooks while every tool remains read-only and evidence-based.
VoxyWatch is made for 24/7 observability of NOC. It complements — not replaces — tools like Wireshark or open source projects like HOMER.
| VoxyWatch | HOMER | Dashboards SBC | Wireshark | |
|---|---|---|---|---|
| Self-hosted | ✓ | ✓ | — | ✓ |
| Web portal | ✓ | ✓ | ✓ | — |
| HEPv1/v2/v3 | ✓ | ✓ | ~ | ~ |
| MOS E-model | ✓ | ✓ | ~ | — |
| Audio reconstruction SIPREC | ✓ | — | ~ | — |
| Audio playback in browser | ✓ | — | ~ | — |
| AI Assistant | ✓ | — | — | — |
| Autonomous incident investigation | ✓ | — | — | — |
| Actionable Telegram notifications | ✓ | — | — | — |
| Installation in a binary | ✓ | — | · | ✓ |
| Forensic Packet Inspection (Specialist Tool) | · | ~ | — | ✓ |
When your customers dictate card numbers over the phone, the sensitive RTP is discarded at the source. The payment audio never leaves the secure environment, never travels over the network, never reaches VoxyWatch.
The Probe discards the RTP from the payment window at the source — the lowest possible PCI scope for your deployment.
Add or remove SSRCs in pci_suppress.json — Probe applies in seconds, no reboot, no maintenance window.
Works with portal suppression for two-layer assurance: misconfigured Probe entries are detected on the server before storage.
Your contact center system writes the SSRC when the agent activates pause. Resume removes it. No new infrastructure.
If your device speaks HEP or SIPREC — and almost everything does — VoxyWatch works with it.
Validated in laboratory and production.
VoxyWatch includes a native SIPREC recording server (RFC 7865/7866). These SBCs send their recording session directly to VoxyWatch — without agent HEP. SIPREC support is in active beta; Write to us and we will validate it with you for your specific SBC.
Does your source emit neither HEP nor SIPREC? voxywatch-probe (libpcap) captures it straight from the NIC. Step by step guide on the wiki ↗.
Light. It runs comfortably on a modest server.
From theory to diagnosis in minutes.
Filter by status = failed, open any call and the SIP diagram shows the INVITE → 100 → 486. Root cause confirmed in less than 5 minutes.
Reconstructs the audio, listens by channel, and traverses with jitter and RTCP to locate exactly where the client's audio was cut off.
Make test calls and verify that they appear with correct numbers, high MOS and clean diagrams before going to production.
VoxyWatch is not a generic observability platform that SIP learned last quarter. It's designed by people who have operated voice networks — and built specifically for the engineers who do.
What we get asked the most before we start.
Open the Paddle customer portal and cancel in one click — link below. Your license remains active until the end of the period.
Open Paddle portal →Yes, upon request. Write to [email protected] with the method and duration you prefer, and we will coordinate it.
Yes. Open a support ticket and we will credit the unused portion of your Pro license towards the Telco plan.
Open a support ticket. We reissue your license for the new HWID. Same plan, same expiration.
Yes. Open a support ticket with your tax information (company name, RFC/Tax ID, address) and we will send a formal invoice.
Upon request. Open a support ticket with the currency and duration, and we coordinate outside of Paddle's default USD flow.
No. Your CDRs, audio recordings and settings remain intact on your server. Only new captures are paused until you refresh.
SIP traffic monitoring, call capturing, and network observability run 100% locally on your server (zero cloud dependencies). The optional AI copilot uses external LLMs (OpenAI, Anthropic, Gemini, or OpenRouter) with your own API key (BYOK), connecting directly from your server to the provider without passing through VoxyWatch servers.
Yes. The Free tier (50 concurrent calls, unlimited CDRs) is free for life and includes all features. No card. You install in 60 seconds.
No. The AI does not have any tools to touch your SBC — by design, not by promise. The proposed remediations come from a closed catalog at the code level (restart the capture sniffer, recalculate baselines) and are executed only after explicit human approval, with full audit of who approved what.
It's bring-your-own-key. You configure your own API key of OpenAI, Anthropic, Gemini or OpenRouter. Requests go directly from your VoxyWatch to the provider you choose. VoxyWatch never sees the data and never passes through our servers.
Yes. We offer a referral program for VoIP consultants and integrators. Email us at [email protected] for details.
You can chat directly with our team on our official WhatsApp line: +52 55 9221 7665.
Open WhatsApp Chat (+52 55 9221 7665) →