Modified: for 12.1.4
In this section:
The SBC Core acting as P-CSCF or I-BCF can be configured to intercept IMS sessions. This feature can also be used in non-IMS deployments, to intercept audio/video/clearmode and fax streams.
The figure below depicts the deployment scenario of the SBC to support Lawful Interception (LI).
SBC for Lawful Interception
X3 interface: This interface is known as Media interface that is supported by Ribbon SBC to send call content (media) messages over UDP or TCP. These media streams (audio/video/image/clearmode/MSRP/BFCP/FECC) carries a copy of the stream sent/received towards/from the target. The SBC sends media call content messages over UDP or TCP through X3 interface. The SBC is enhanced to support sending the media call content messages over TCP using an optional IPsec tunnel through X3 interface.
The SBC support IPsec with IMS LI for media interception over UDP and TCP.
At a high level, the functions performed by the Lawful Intercept are:
Support for sending intercepted signaling messages over TCP, using an optional IPSec tunnel
To prevent lag and duplication of services, configure the SBC to intercept calls on only leg of a call by configuring the SIP Trunks Groups to include or exclude from Lawful Intercept.
If media interception over UDP and TCP are both configured at the CDC, the transport type for interception is decided based on the following conditions:
The SBC is enhanced to support IMS LI for PS-to-PS Handover scenarios. The enhancement has no impact on the IMS routing.
For more information on RAMP and PSX configuration for Lawful intercept, refer to the RAMP doc Lawful Intercept Guide.
For configuration details, see Configuring SBC For Lawful Interception.
The interface between PSX and the SBC allows the PSX to send, and the SBC to receive, the TAP ID or Lawful Intercept ID. Use RAMP to perform the relevant configurations.
The TAP ID, is a decimal value between 1 and 4,294,967,295 (4 bytes). The default value of TAP ID is 0.
If the SBC receives a non-zero TAP ID from the PSX, it embeds the value in the Correlation ID (CCID) and sends the TAP ID as a separate Tag Length Value (TLV) in the Direct Signaling Report (DSR) message.
If the SBC receives the value 0 as TAP ID, it does not take any action.