The customer calls first
A trunk silently degrades ASR from 90% to 70%. Global thresholds never see it. The ticket comes from the customer, not from monitoring.
音声エンジニアをより速く、より効率的に、より効果的にするために設計。VoxyWatchは、音声チームが異常を検出し、SIPの問題を理解し、テレコムに特化したオブザーバビリティとAIによってインシデント分析を加速させるのを支援します。
curl -fsSL https://raw.githubusercontent.com/VoxyWatch/publish/main/install.sh | sudo bash すぐに連携できる対応機器
A trunk silently degrades ASR from 90% to 70%. Global thresholds never see it. The ticket comes from the customer, not from monitoring.
Wireshark, grep on the SBC, manual captures and correlation by hand. Every incident burns hours of a senior engineer's time.
Without your own evidence, diagnosis ends in a ticket with the SBC vendor: days of waiting and zero control.
Which carrier is degrading? Which destination is failing? Without per-trunk and per-country attribution, it's all opinion, not evidence.
Actions execute only after your approval — and the AI has no tool to change your network. By design, not by promise.
Every anomaly becomes a persistent incident with a lifecycle (open → acknowledged → resolved), deduplication, an auditable timeline and stability-based auto-resolve. A dedicated Incidents tab with one-click actions.
The moment an incident opens, VoxyWatch investigates by itself: sample failing calls, dominant SIP codes, failing IP paths, and whether other trunks degraded too — the local-vs-carrier tell. With your LLM key, it writes the probable root cause citing that evidence.
Critical incidents reach your phone with the diagnosis attached and inline buttons: Ack · Resolve · Investigate · plus a proposed remediation when one applies. Each portal user links their own chat with a one-time code. Every action audited by real username, gated by role.
Ships with field runbooks the investigator 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 size, measurement coverage, deviation from the trunk's own baseline, sustained degradation. Validated on production data: −92% false-critical noise.
Audio retention is measured, not guessed — capacity incidents open before you run out. A daily/weekly digest lands in Telegram or your webhook on schedule.
Proposed actions come from a closed, code-level catalog (restart the capture sniffer, recompute baselines — never your SBC), execute only after your tap, and land in the incident timeline with who-approved-what.
キャリア、ITSP、UCaaSプロバイダー、音声インテグレーター向け。ベンダー非依存、マルチSBC、セルフホスト。
すべての相互接続を見渡すNOCビュー:ルートごとのASR/NER、トランクごとの異常検出、5xxスパイクをリアルタイムでフラグ。
顧客ごとの可視性、宛先ごとの品質、ITU-T E.164によるキャリア帰属、そして「何が起きたか」を証明する必要があるときの音声。
テナントごとに監査可能な音声品質:MOS、ジッター、損失、PDD。顧客がエスカレーションする前に劣化を検出。
SBCベンダーにエスカレーションせずに通話を診断。エビデンスベース、マルチプラットフォームのインシデント分析。
キャプチャ、帰属、学習、説明 — すべてを一つのセルフホスト型バイナリに。
Asterisk、Kamailio、OpenSIPS、FreeSWITCH、Oracle/ACME、Ribbon、AudioCodes、Cisco CUBEからUDPおよびTCPでHEP v1/v2/v3を受信。HEPを送信できないソース向けに、付属のvoxywatch-probe(Go + libpcap、amd64 & arm64)も提供。
トランクを一度ロードすれば、すべての通話はIP/CIDRでキャリアに、ITU-T E.164ロンゲストマッチエンジン(197コード)で着信国に自動的に帰属されます。ONNETトラフィックは別途フラグ付け。
各トランクが独自の正常値(時間ごとの平均±σ)を学習。グローバル閾値が見逃す静かなドリフト(あるキャリアでASRが90%から70%へ等)を検知。
トランク別およびサマリーのコパイロット:ヘルス+ベースライン+48時間トレンドを読み、考えられる原因とNOCのアクションを返します。OpenAI、Anthropic、Gemini、OpenRouterに対応。SBCには絶対に触れません。
SNMP v2c/v3エージェント内蔵、30以上のOIDとエッジトリガー方式のトラップ:キャプチャ損失、スニッファー停止、低ASR/MOS、ディスク/CPU/RAM圧迫を通知。MIBダウンロード可能。PRTG、Zabbix、Nagiosに統合。
単一バイナリ + PostgreSQL/TimescaleDB、インストーラーが60秒でプロビジョニング。あなたのハードウェア、あなたのデータ、クラウドなし、テレメトリなし、コールホームなし。
VoxyWatchはNOCの24時間365日の可観測性のために構築されています。Wiresharkのようなパケットツールや、HOMERのようなオープンソースプロジェクトを置き換えるのではなく、補完します。
| VoxyWatch | HOMER | SBCダッシュボード | Wireshark | |
|---|---|---|---|---|
| セルフホスト | ✓ | ✓ | — | ✓ |
| Webポータル | ✓ | ✓ | ✓ | — |
| HEPv1 / v2 / v3 | ✓ | ✓ | ~ | ~ |
| E-model MOS | ✓ | ✓ | ~ | — |
| SIPREC音声の再構成 | ✓ | — | ~ | — |
| ブラウザ内音声再生 | ✓ | — | ~ | — |
| 組み込みAIアシスタント | ✓ | — | — | — |
| 単一バイナリインストール | ✓ | — | · | ✓ |
| パケットフォレンジック調査(専門ツール) | · | ~ | — | ✓ |
When your customers dictate card numbers by phone, sensitive RTP is dropped at the source. Payment audio never leaves the secure environment, never travels the network, never reaches VoxyWatch.
The Probe drops RTP of a payment window at the source — the smallest possible PCI scope for your deployment.
Add or remove SSRCs in pci_suppress.json — Probe applies within seconds, no restart, no service window.
Pairs with portal-side suppression for a two-layer guarantee: misconfigured Probe entries are caught server-side before storage.
Your contact-center system writes the SSRC entry when the agent triggers pause. Resume removes it. No new infrastructure.
VoxyWatch ships a standalone Model Context Protocol server: connect Claude Desktop, Claude Code or any MCP-compatible agent and let it query health, KPIs, trunk status, CDRs and incidents — with evidence and diagnosis — through 6 read-only tools. Authenticated with the same scoped API keys.
voxywatch-mcp.js · 6 read-only tools · scoped API keys Your corporate AI can now interrogate your voice network.
あらゆるHEPv3送信元がすぐに動作。それ以外もWikiに正確な手順があります。
SBCがネイティブHEPに非対応ですか?HEPlifyサイドカーまたはSPANポートで解決できます — Wikiで手順を解説しています。
軽量。控えめなサーバーでも快適に動作します。
理論から診断まで数分で。
ステータス=失敗でフィルタし、任意の通話を開くと、SIPダイアグラムにINVITE → 100 → 486が表示されます。根本原因を5分以内に特定。
音声を再構成し、チャンネルごとに聴き、ジッターとRTCPを照合して、着信側の音声が途切れた箇所を正確に特定。
テスト通話を行い、正しい番号・高いMOS・クリーンなダイアグラムで表示されることを本番投入前に確認。
VoxyWatchは前四半期にSIPを学んだ汎用オブザーバビリティプラットフォームではありません。音声ネットワークを実際に運用してきた人々によって設計され、それを行うエンジニアのために特別に構築されています。
🔒 最初の顧客ウェーブをオンボーディングしている間、アーリーアダプター価格はロックされています。
The most common things buyers ask before getting started.
Open the Paddle customer portal and cancel from there in one click — link below. Your license stays active until the end of the billing period.
Open Paddle customer portal →Yes, on request. Write to contact@voxywatch.com with your preferred method and plan length, and we set it up.
Yes. Open a support ticket and we credit the unused portion of your Pro license toward the Telco plan.
Open a support ticket. We re-issue your license for the new HWID. Same plan, same expiration.
Yes. Open a support ticket with your billing details (legal name, tax ID, address) and we send a proper invoice for your records.
On request. Open a support ticket with the currency and plan length, and we coordinate it outside the default Paddle USD flow.
No. Your CDRs, audio recordings, and configuration stay intact on your server. Only new captures are paused until you renew.
No. VoxyWatch is 100% self-hosted. No telemetry, no call-home, no data leaves your network. The only outbound calls are AI copilot requests — and those use YOUR API key, going to YOUR chosen provider.
Yes. The Free tier (50 concurrent calls, 1,000 CDRs) is lifetime free and includes every feature. No credit card. Install in 60 seconds.
No. The AI has no tool to touch your SBC — by design, not by promise. Proposed remediations come from a closed, code-level catalog (restart the capture sniffer, recompute baselines) and execute only after a human explicitly approves, with full audit of who approved what.
It is bring-your-own-key. You configure your own OpenAI, Anthropic, Gemini, or OpenRouter API key. Requests go directly from your VoxyWatch instance to your AI provider. VoxyWatch never sees the data and never proxies through our servers.
Earn 10% to 30% of the first payment when you refer a customer to VoxyWatch. The exact percentage depends on your involvement: a simple referral starts at 10%; active sales support (introductions, technical pre-sales, demo coordination) goes up to 30%.
Contact us at partners@voxywatch.com with the prospect details.
We agree on the commission percentage based on the support level.
When the customer pays for any plan (1 month, 6 months, 1 year, or 2 years), you receive your commission on that first payment.
Payment method and minimum payout agreed by email.
Email partners@voxywatch.com and we send the full program terms.