Compliant on paper is not compliant.
Many providers buy a CALEA solution from a manufacturer and never test whether it actually delivers safe harbor. The equipment can be perfectly configured and still produce call data an agency's systems cannot read. Compliance Analysis is the difference between a capability on a specification and a capability that has been proven.
"Safe harbor" is a finding, not a purchase.
Safe harbor is a regulatory term denoting full compliance with the technical requirements of the law. Buying equipment that claims it is not the same as demonstrating it — and the demonstration is what a court order will demand, at the worst possible moment to discover a gap.
Compliance Analysis gives a provider the assurance that its equipment is capable of delivering the appropriate call data and call content, in an industry-acceptable format, in the event that a court order is presented.
Not a simulator. The real thing.
Validation runs the same collection-system software used by many federal, state and local agencies — software with thousands of licensed law-enforcement and intelligence users worldwide. Test traffic is transmitted exactly as it would be to an agency's monitoring center.
Terminate
The collection server terminates the physical connections carrying call data from your switch, exactly as an agency's would.
Route
Incoming call data is routed to the analysis workstation for live monitoring, and recorded to disk as it arrives.
Decode
Data messages are decoded and displayed as call sessions, each with its own call sequence number, so gaps and mis-sequencing are visible rather than inferred.
Report
Results are recorded against the plan, and you receive a documented report of what passed and what did not.
Traceable from requirement to result.
A combined Test Plan/Test Case document sets out how the testing will be accomplished, drawn from the functional specification and technical design. Its purpose is to record your state of technical compliance at a level of detail that survives scrutiny.
Every requirement in the functional specification is referenced in a test case, which maps each result back to the requirement it proves. That mapping is what turns "we tested it" into something a regulator, an agency or a court can follow.
Find the gap before an order does.
Tell us what you have deployed and who supplied it. We will tell you what testing it properly involves.