01 · What happened
Show the record
Yesterday
Ask the team what they remember about that week.
Today with FRINK
Call records and logs retained as long as policy requires – up to 10 years.
Audits and SLAs
One audit question.
Two ways to answer it.
Today, "show us the configuration on that date", "prove the call left your network" and "who changed this?" each mean a week of digging – and the logs are usually gone.
02 · What it looked like
Show the configuration
Yesterday
Rebuild the configuration from backups, if they exist.
Today with FRINK
The nightly snapshot of that component on that date, comparable to any other.
03 · Who did it
Show the change
Yesterday
Nobody remembers who changed it.
Today with FRINK
Audit trail with user and time for every change made through FRINK; snapshots show the diff.
04 · Result
Answered from data
Yesterday
A week of digging and a best guess.
Today with FRINK
Answered from data, with a date and a name.
What changes
- Time per audit questionYesterday: A weekToday with FRINK: An hour
- Evidence age availableYesterday: Until the logs rotateToday with FRINK: Up to 10 years
- AttributionYesterday: RecollectionToday with FRINK: User and time; diff from snapshots
Worked example · Insight 06
Fax failing on T.38 negotiation
Weeks after the fault, CUCM had deleted its logs – the SIP ladder from the traces FRINK had kept still showed the far end's reply, and the CUBE configuration the local side.
Read the full case- Show the recordThe SIP ladder from retained CUCM traces still shows "488 Not Acceptable Media" from the far end.
- Show the configurationThe CUBE running configuration confirms T.38 allowed locally.
- Show the changeNo change on this side – the rejection came from the remote fax server.
- Answered from dataFault placed on the remote fax server, with evidence.