Skip to end of metadata
Go to start of metadata


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

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

Intercept StandardVendor IdFlavors
packetCableNone/Utimaco/VerintLegacy LI (default)
packetCableSs8PCSI LI
3gpp/etsiVerint/utimaco/noneIMS LI

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