DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
The SBC Core platforms support Lawful Intercept (LI) functionality using one of the following solutions: The SBC works in conjunction with the Intercept Server 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 Intercept Server. It also sends media stream (call content) to an IP address provided by the Intercept Server. The SBC supports four types of LI: In order to intercept media packets, the EMS must be either the same version or higher version as that of the SBCs and PSXs. 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, and PacketCable 2.0 LI. It also lists the types of LI supported on different platforms: Table 1: LI Types and Supported Platforms Supported Audio,Video and T140LI Type CDC Configuration Platforms Routing Policy LI Interface Stream Supported Intercept Standard Vendor Id D-SBC SBC SWe/SBC 5000/7000 Series External PSX ERE X1 X2 X3 D-SBC SBC SWe/SBC 5000/7000 Series Legacy LI (default) PacketCable, PacketCablePlusEtsi None/Utimaco/Verint Supported Supported Supported SOAP UDP Audio Only Audio only PCSI LI PacketCable Ss8 Supported Supported Supported Not Supported TLS Not Supported Audio, Video and T140 IMS LI 3gpp/etsi Verint/utimaco/none/GroupTwoThousand Supported Supported Supported Supported SOAP Audio Only All Streams PacketCable 2.0 PacketcableVTwo none/atos Not Supported Supported Supported Supported SOAP Not Supported Audio, Video
User "calea" must be created on SBC before attempting LI provisioning.
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.
You do not need to create a CALEA user for EMS registered D-SBC setups.
Select Calea from the Role drop-down menu.
Click Save.
The CALEA user saves with a temporary password, which appears in the Create User panel. Record the temporary password.
A prompt to create a new password appears. Enter and confirm a new password.
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]