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

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

User "calea" must be created on SBC before attempting LI provisioning.

Creating the CALEA user

  1. Log on as admin user.
     
  2. Create a CALEA user, by executing the following command:

    % set oam localAuth user calea group Calea
    commit


    You will see a system-generated password. Use this password when you log on to CALEA user for the first time.

Creating Call Data Channel (CDC)

Execute the following command to create a CDC:

% set addressContext default intercept callDataChannel CDC
commit

View the CALEA user status

View the CALEA user status, by executing the following command:

> show status oam localAuth userStatus
userStatus admin {
    currentStatus Enabled;
    userId        3000;
}
userStatus calea {
    currentStatus Enabled;
    userId        3329;
}
[ok]

  • No labels