01 · Which calls
How many, and where?
Yesterday
Ask around which sites complain most.
Today with FRINK
Quality by site and device group; by day and hour in the heatmap.
Call quality
Bad audio.
Two ways to find where it's lost.
Today, users say calls sound bad. Nobody can say which calls, which site or which leg – so it becomes a phone problem, then a network problem, then nobody's.
02 · Which leg
Where is it lost?
Yesterday
Capture packets on a suspect phone and hope it happens again.
Today with FRINK
Packet loss, jitter and delay for both ends of every call already made.
03 · Which cause
Network, device or codec?
Yesterday
Argue phones vs. network vs. carrier.
Today with FRINK
The bad calls share a segment, a firmware or a codec – visibly.
04 · Result
Fault located
Yesterday
"The phones are bad." Ticket closed, problem open.
Today with FRINK
One segment or device group named, with numbers.
What changes
- Calls with dataYesterday: A handful of capturesToday with FRINK: Every call
- Time to locateYesterday: Weeks of complaintsToday with FRINK: One filtered view
- Handover to networkYesterday: "It sounds bad"Today with FRINK: Loss, jitter, delay per side
Worked example · Insight 11
The site that dragged the quality score down
POOR calls were rising at one branch. The site filter moved the ticket from telephony to networking.
Read the full case- How many, and where?Sites with the most poor calls: one branch on top, up against the previous month.
- Where is it lost?Every degraded call in the same hours – day-by-hour heat map.
- Network, device or codec?Across every device type: the site, not the phones.
- Fault locatedQoS misconfiguration on the branch WAN.