01 · Which call?
Find it
Yesterday
Pull traces from each system separately, then guess which file holds the call.
Today with FRINK
Search by number, device, time or disconnect reason.
Troubleshooting a failed call
One failed call.
Two ways to find the cause.
Today, one failed call means a senior engineer collecting traces from several systems: 20+ text files of 1,000+ lines each, two or more hours, several technologies – before analysis even starts.
02 · Each leg
What happened on it?
Yesterday
Scroll through 1,000+ lines per file to find the right leg and timestamps.
Today with FRINK
Media statistics, quality grade and disconnect reason for both ends of the call.
03 · The messages
Which one caused it?
Yesterday
Rebuild the message flow by hand across several technologies.
Today with FRINK
SIP ladder and call routing data for CUCM; SIP debug and dial-peer simulator for CUBE.
04 · Result
Cause named
Yesterday
Two or more hours in – and analysis has only just started.
Today with FRINK
Fix applied. The evidence is one link.
What changes
- EvidenceYesterday: 20+ text filesToday with FRINK: One link
- Time to causeYesterday: 2+ hoursToday with FRINK: Minutes
- Who can do itYesterday: A senior engineerToday with FRINK: Any UC engineer
Worked example · Insight 02
Call loops within CUCM
Users reported "dropped calls". The real cause was a loop – visible in one filtered list instead of across hours of trace files.
Read the full case- Find itCUCM call records filtered by the calling and called numbers.
- What happened on it?A burst of records with near-zero duration, linked into one call journey.
- Which one caused it?The same trunk as originating and destination device.
- Cause namedA call loop – not dropped calls.