Compliance Analysis Services

Many companies purchase CALEA solutions from manufacturers without properly testing the solution to ensure that it provides their company “safe harbor” a regulatory term that denotes full compliance with technology requirements of the law.  Subsentio’s Compliance Analysis gives service providers the peace of mind that their equipment is capable of providing the appropriate call data and call content in an industry-acceptable format in the event that a court order is presented.

Test Data and Validation Techniques

To test CALEA compliance, Subsentio uses the same Pen-Link ( equipment deployed by federal, state and local law enforcement agencies.  In business for over 20 years, Pen-Link, Ltd. provides state-of-the-art software and systems for the collection, storage and analysis of telephonic and IP-based communications.

Pen-Link’s software and systems, Pen-Link 8 and LINCOLN, are widely recognized as industry standards, with thousands of licensed law enforcement and intelligence agency users in federal, state, and local agencies worldwide.  The LINCOLN 2 Server is equipped with the hardware necessary to terminate the physical connections of call data that are being received from the service provider’s switch. Once call data is received, LINCOLN immediately routes the data flow to the appropriate Pen-Link workstation for live monitoring. Test call data is recorded to the LINCOLN Server’s hard drive. At the same time, the Pen-Link 8 workstation decodes and displays data messages in call sessions, each with a call sequence number.

A combined Test Plan/Test Case document gives an overview of how the testing will be accomplished.  The source of the document is the Functional Specification and Technical Design documents.  The purpose of the combined Test Plan/Test Case document is to record important high-level information on the service provider’s state of technical compliance with CALEA.

The test case portion of this document gives the specific steps that are taken to test each call feature.  Each requirement in the Functional Specification is referenced in a test case, providing mapping back to the requirements.  Validation that each requirement is being tested is given by referencing each requirement in the test case where it is verified.

Sample call scenarios that are tested in a CDMA environment are shown below.


Test Case





Incoming Basic Call


Incoming No Answer Call


Incoming Busy Call


Outgoing Basic Call


Abandoned Call Attempt


Partial Dial Abandon


Pre-Answer Abandon


Call Delivery to a Mobile Station


Speed Calling


Outgoing No Answer Call


Outgoing Busy Call


Redirection Inconditional


Redirection on No Answer


Call Forward


Call Waiting


Call Waiting with Recall


Call Waiting with Recall on Single Call Identity


Conference Call


Short Message Service


Intrasystem Hand-off


Hand-off to a Third System Without Path Minimization


Hand-off to Third system


Multi-stage Dialing


CDMA Packet Data Delivery