Current Location ：
Time Synchronisation, Logs, and Voice Forensics
Two systems, two clocks, two versions of events. A call that the platform logs at 14:03:12 and the carrier records at 14:07:40 is the same call, and the gap is a clock that drifted. Investigating a complaint, a dispute, or a billing query depends on being able to line up records from different systems, and that depends on something nobody thinks about until it fails.
Where the Clocks Come From
Each device in a voice path keeps its own time. Handsets, gateways, the platform, switches, and servers all have clocks, and each drifts at its own rate. Time synchronisation protocols keep them aligned, but only if every device is configured to use a source, and only if that source is reachable from the network segment the device sits on. Devices that cannot reach a source drift, quietly, for years.
| Device | Typical drift if unsynchronised | Consequence |
|---|---|---|
| Platform server | Seconds to minutes per month | Logs misaligned with carrier records |
| Gateway | Similar | Call records inconsistent with the platform |
| IP handset | Variable, sometimes large | Displayed call times wrong; user confusion |
| Network switches | Small but cumulative | Capture timestamps do not match logs |
| Recording system | Follows its host | Recording index misaligned with call detail |
One Source, Reachable by Everything
The practical rule is a single authoritative time source, reachable from every segment that contains a voice device, with a documented fallback. Where a segment cannot reach the source, that is a design gap rather than a device problem, and it will produce exactly the misalignment that makes investigations difficult. Checking that each class of device reports synchronised time is a five-minute audit that repays itself the first time a dispute arises.
- Use one authoritative source with a documented fallback
- Verify synchronisation per device class, not only on servers
- Record the source in the network documentation
- Check timezone configuration separately from time accuracy
- Re-verify after any network segmentation change
Correlating Records
An investigation usually combines platform call detail, a packet capture, a carrier record, and often a recording. Those four have independent clocks. Where they are aligned within a second, a timeline can be built. Where they are not, the investigator spends the first hour establishing offsets, and sometimes draws the wrong conclusion because a log entry appears to precede its cause.
Compliance Has the Same Requirement
Where records may be produced for an audit or a legal process, timestamp accuracy becomes a matter of credibility. A record whose time cannot be reconciled with other evidence is weaker than one that can. The controls are unglamorous, cheap, and usually absent: a documented time source, a check that devices use it, and a note of the timezone convention applied.
Redstone Approach
Redstone deployments include time source configuration for the platform and guidance for gateways and endpoints, with the convention recorded in the handover documentation. Where an investigation requires correlating records, we state the time basis of each source rather than assuming they agree.
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.
