Overview
Track MOS, jitter, and packet loss; auto-route failover trunks and notify VoiceOps.
Problem
Quality issues are spotted late, after customers hang up or complain.
Solution
VoiceLink collects WebRTC stats and SIP RTCP, surfaces dashboards, and triggers FlowForge alerts/actions when thresholds are breached.
How it works
Enable the /metrics endpoint, create QoS thresholds, and define actions (post to Slack, switch trunk, tag call). Use ISP and geo breakdowns to isolate issues quickly.
Who is this for
SRE/VoiceOps
NOC
Expected outcomes
- Faster detection and mitigation of call quality issues
- Automatic failover under degradation
Key metrics
MTTD for QoS incidents
Baseline
45 minutes
Target
5 minutes
Calls with MOS < 3.0
Baseline
8 %
Target
2 %
Gallery
Downloads & templates
Case studies
TravelCo auto-fails over within minutes
QoS alerts cut incident impact windows dramatically.
Travel Mid-market NA
Security impact
- Aggregated quality metrics; call IDs · PII: none
Compliance
- SOC2 (monitoring & alerting)
Availability & next steps
Team
Business
Enterprise