In this section:

Related articles:

Note

Applicable only for CALEA users.

Overview

This section outlines the commands to configure the IMS LI on the I-SBC. For more information about the IMS LI configuration, refer to IMS LI Configuration.

Note
  • As a prerequisite to configure the IMS LI on the I-SBC, ensure that the Call Data Channel (CDC) and the Mediation Server are enabled and running.
  • You can configure the IMS LI with only the default address context.
  • For more information on the parameters and their descriptions, refer to Intercept - CLI.

Creating CDC for Intercept Flavor as IMS LI

To configure the IMS LI on the I-SBC, use the following commands to configure the media (X3) interface.

For other options of how to configure the intercept flavor as IMS LI, refer to Configuring SBC For Lawful Interception.

% set addressContext default intercept callDataChannel <callDataChannel_Name> 
    interceptStandard <etsi | threeGpp>
    vendorId <verint | utimaco | none | groupTwoThousand>
    ipInterfaceGroupName <ipInterfaceGroup_name>
    mediaIpInterfaceGroupName <mediaIpInterfaceGroup_name>
	dsrProtocolVersion <0 | 1>
	liPolDipForRegdOodMsg <disabled | enabled>
	rtcpInterception <disabled | enabled>
% commit

The following is an example of how to create a CDC for the intercept flavor as IMS LI.

Example
% set addressContext default intercept nodeNumber 74120 callDataChannel CDC ipInterfaceGroupName LIG1 interceptStandard etsi vendorId groupTwoThousand mediaIpInterfaceGroupName LIG2 dsrProtocolVersion 1 liPolDipForRegdOodMsg enabled rtcpInterception enabled
% commit
Note

The ipInterfaceGroup and mediaIpInterfaceGroup for the CDC must differ from the other signaling and media ipInterface groups. This difference ensures that the LI does not use the signaling ipAddress to send intercepted traffic (signaling or media) towards the mediation server.

Note

The SBC allows configuration of a maximum of 16 mediation servers for the IMS LI in the CDC. When a call is tapped, the SBC selects among the Delivery Function 2 (DF2) servers in a round-robin manner, and establishes persistent TCP connections with all configured mediation servers.

Each mediation server object contains the Signaling (X2) and Media (X3) IP addresses. The SBC allows configuration of multiple mediation servers with the same X2 IP address but a different X3 IP address.

For the IMS LI, the SBC does not support any Active-Standby configurations for the X2 servers. The SBC assumes that the DF2 servers run in Active-Active mode and, in case of a failure, moves the IP address of the active DF2 server to the standby DF2 server.

The X2 and X3 servers operate independently. Even if the X2 servers are not reachable, the SBC sends X3 media if DF3 servers are available, and vice versa.

The SBC buffers the X2 messages if the corresponding mediation server is not operational.

For more information, refer to Intercept - CLI.

The alarms sonusSbxImMediationServerX2MsgBufferFull and sonusSbxImMediationServerX2MsgBufferAvailable indicate the status of the DSR buffer. The alarms are raised depending on whether the DSR buffer is full or available.

Configuring CDC for Media Interception over TCP or UDP

% set addressContext default intercept callDataChannel <callDataChannel_name> mediationServer <mediationServer_name> media <tcp | udp>
   ipAddress <IP_Address>
   portNumber <0-65535>
   dscpValue <0-63>
   mode <inService | OutofService>
   state <disabled | enabled>
   kaTime <60-7200>
   kaInterval <5-60>
   kaProbe <4-8>
% commit

The following is an example of how to configure a CDC for the media interception over TCP.

Example
% set addressContext default intercept callDataChannel CDC mediationServer MS1 media tcp ipAddress 10.54.78.20 portNumber 65120 
% commit
% set addressContext default intercept callDataChannel CDC mediationServer MS1 media tcp state enabled mode inService
% commit 

The following is an example of how to configure a CDC for the media interception over UDP.

Example
% set addressContext default intercept callDataChannel CDC mediationServer MS1 media udp ipAddress 10.54.78.20 portNumber 65200
% commit
% set addressContext default intercept callDataChannel CDC mediationServer MS1 media udp state enabled mode inService
% commit 
Note

The SBC supports IPsec for signaling interception over TCP, and media interception over TCP and UDP.

Configuring CDC for Signaling Interception

% set addressContext default intercept callDataChannel <callDataChannel_name> mediationServer <mediationServer_name> signaling
   ipAddress <IP_Address>
   portNumber <0-65535>
   dscpValue <0-63>
   protocolType <tcp | udp>
   mode <inService | OutofService>
   state <disabled | enabled>
% commit
Note

The signaling interception does not support the protocolType udp.

The following is an example of how to configure a CDC for the signaling interception.

Example
% set addressContext default intercept callDataChannel CDC mediationServer MS1 signaling ipAddress 10.54.78.20 portNumber 65300 protocolType tcp
% commit
% set addressContext default intercept callDataChannel CDC mediationServer MS1 signaling state enabled mode inService
% commit

Configuring CDC for RTCP Interception

% set addressContext default intercept callDataChannel CDC rtcpInterception enabled
% commit
Note

The rtcpInterception parameter is available only when the interceptStandard and vendorId parameters are configured as IMS LI.

Configuring CDC for LiPolDipForRegdOodMsg

When the liPolDipForRegdOodMsg parameter is enabled, it makes the SBC send a policy request to the PSX or ERE for registered Out-Of-Dialog requests (messages) to be intercepted. When this parameter is disabled, the SBC does not send a policy request to the PSX or ERE for registered Out-Of-Dialog requests (messages).

Use the following command to enable the support for policy dip, for registered users out-of-dialog messages, to decide on interception.

% set addressContext default intercept callDataChannel CDC liPolDipForRegdOodMsg enabled
% commit
Note

The liPolDipForRegdOodMsg parameter is available only when the interceptStandard and vendorId parameters are configured as IMS LI.