Skip to end of metadata
Go to start of metadata

Overview

The SBC Core platforms support Lawful Intercept (LI) functionality using one of the following solutions:

  • Centralized PSX solution consisting of an external PSX, a third-party Intercept Server (IS), and EMS
  • SBC ERE solution consisting of the ERE, a third-party IS and EMA

The SBC works in conjunction with the IS, as well as the ERE and EMA (or an external PSX and EMS) to provide call data and call content to law enforcement agencies for calls involving identified intercept subjects. When it receives matching LI criteria in a policy response from the ERE (or PSX), the SBC routes the call as directed and additionally reports call events to the IS. It also sends media stream (call content) to an IP address provided by the IS.

The SBC supports three LI flavors:

  • Default LI
  • IMS LI
  • PCSI LI

The following table describes the Call Data Channel (CDC) configuration information required to distinguish between Default LI, IMS LI, and PCSI (P-Com.Session-Info) LI. It also provides the LI flavors supported in different platforms:

Table : LI Flavors with Supported Platforms

Flavors CDC Configuration Platforms Routing Policy LI Interface
Intercept Standard Vendor Id D-SBC SBC SWe/SBC 5000/7000 Series External PSX ERE X1 X2 X3
Legacy LI (default) packetCable None/Utimaco/Verint Not Supported Supported Supported Supported SOAP
  • RADIUS
  • RADIUS over IPSec
UDP
PCSI LI packetCable Ss8 Supported Not supported Supported Not Supported TLS Not Supported
  • TCP
  • TCP over IPSec
IMS LI 3gpp/etsi Verint/utimaco/none Not Supported Supported Supported Supported SOAP
  • DSR
  • DSR over IPSec
  • UDP
  • TCP
  • TCP over IPSec

Call Data Channel (CDC) Model

The SBC supports various flavors of LI and a generic Call Data Channel (CDC) model to support any new flavors of LI. The CDC configuration model is described as follows:

  • The CDC model includes two fields, vendorId and interceptStandard, to support identifying and configuring the various LI flavors.
  • Each Mediation Server is configurable to support both signaling and media interception. Separate configuration fields are present under the Mediation Server to handle this functionality.
  • The CDC model for a given mediation server allows media interception over UDP and/or TCP.
  • The CDC model for a given mediation server supports signaling interception either over TCP or UDP. It does not support both simultaneously.

 

  • No labels