Insurance and Liability: What the Phone System Record Proves
The claim arrives six months after the event: a delivery that was never confirmed, an instruction that was allegedly given, an emergency call that supposedly went unanswered. The phone system either has the evidence or it does not, and by the time anyone asks, the retention window has often closed.
The Four Questions a Claim Turns On
Most disputes that involve telephony reduce to a small set of factual questions. Was the call made, and when exactly? Who answered it? What was said? And what did the organisation do next? Call detail records answer the first three at the level of metadata; recordings answer the fourth only if they were captured and retained.
The awkward part is that these questions are asked months later, by people who were not involved, using systems whose logs roll over. A six-month retention period meets most operational needs and fails most claims.
| Question | Evidence source | Typical retention problem |
|---|---|---|
| Was the call made | Call detail records | Logs rotated monthly on small systems |
| When exactly | CDR timestamp, synchronised clock | Unsynced clocks shift events across time zones |
| Who answered | Extension, queue, agent record | Agent identifiers reused after departure |
| What was said | Recording, if enabled and retained | Recording off by default, or deleted on a 30-day cycle |
| What happened next | Ticket, dispatch, or callback record | Separate system, different retention |
Time Synchronisation Is Not a Detail
Disputes turn on minutes. A record showing a call at 14:07 when the third party's record shows 14:02 is an argument; a record that agrees to the second is evidence. The precondition is that every element in the path, from the phone system to the carrier to the logging server, uses the same time source. Where the platform drifts, the whole call history becomes approximate, and approximate evidence is weak evidence.
Retention Should Match Exposure, Not Habit
Retention is usually set by what storage allows rather than by what the business could be asked to prove. The useful exercise is to list the claim types the business actually faces, identify how long after the event they surface, and set retention to cover that window with margin. For contractual disputes and personal injury this is often measured in years, not weeks.
- Keep call detail records for the period in which claims actually surface
- Synchronise all clocks to a common source and monitor drift
- Record the identifiers that let a call be tied to a person and a ticket
- Preserve recordings for flagged incidents rather than relying on the general window
- Export evidence in a form that survives a platform change
- Document the retention decision so its absence can be explained later
Platform Change Is Where Evidence Dies
A migration to a new platform is a natural moment to lose history. The old system is decommissioned, the archive is exported in a proprietary format, and nobody checks whether it can be read. Before any migration, the export should be tested by someone who did not create it, using tools that will still exist afterwards. A plain recording file plus a CSV of call records is unglamorous and almost always sufficient.
Redstone Approach
Redstone platforms produce call detail records that include calling and called numbers, extension, queue, duration, and disposition, and support synchronisation against an external time source. Records can be exported in open formats so that history remains readable after a platform change rather than depending on the vendor's software.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Current Location :

