In this section:
Unless otherwise stated, the LI configuration process is the same on Cloud-based and non-Cloud based systems. The SBC Core platforms support Lawful Intercept (LI) functionality using one of the following solutions: SBC ERE solution consisting of the ERE, a third-party IS and EMA (refer to Configuring LI on I-SBC using the EMA GUI) You can use the SBC EMA to configure only the default and IMS LI for the I-SBC. 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: 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: LI Flavors with Supported Platforms SupportedFlavors 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 All Streams Audio Only IMS LI threeGpp/etsi verint/utimaco/none/groupTwoThousand Supported Supported Supported Supported SOAP Audio Only All Streams
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:
vendorId
and interceptStandard,
to support identifying and configuring the various LI flavors.