In this section:
To configure Call Data Channel (CDC):
All LI flavors except Default/Legacy LI support IPV6 addresses.
As user ''Calea'', use the following commands to configure LI:
set addressContext default intercept nodeNumber 7788
For other options of configuring the intercept flavor as IMS LI, refer to the section Configuring SBC For Lawful Interception.
% set addressContext default intercept callDataChannel <callDataChannel_name> liPolDipForRegdOodMsg <disabled | enabled> interceptStandard <etsi | threeGpp> rtcpInterception <disabled | enabled> ipInterfaceGroupName <ipInterfaceGroup_name> mediaIpInterfaceGroupName <mediaIpInterfaceGroup_name> vendorId <verint | utimaco | none | groupTwoThousand> dsrProtocolVersion <0 | 1>
An example of how to create a CDC for the intercept flavor as IMS LI is shown below:
The dsrProtocolVersion
always comes after the interceptStandard
and vendorId
.
set addressContext default intercept nodeNumber 74120 callDataChannel CDC ipInterfaceGroupName LIF1 interceptStandard etsi vendorId groupTwoThousand mediaIpInterfaceGroupName LIF1 dsrProtocolVersion 1 % commit
The ipInterfaceGroup
/mediaIpInterfaceGroup
for CDC must be different from other signaling/media ipInterface
groups. This ensures that LI doesn't use signaling ipAddress
to send intercepted traffic (media/signaling) towards the mediation server.
Refer to Viewing the CDC Configuration for an example configuration. For IPsec encapsulation, refer to the section Configuring IPSec for Signaling and Media Interception.
The SBC allows configuration of a maximum of 16 mediation servers for IMS LI in the Call Data Channel (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 IMS LI, the SBC does not support any Active-Standby configuration for the X2 servers. It assumes that the DF2 servers are running 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.
% set addressContext default intercept callDataChannel <callDataChannel_name> mediationServer <MS_name> media tcp ipAddress <IP_Address> portNumber <0-65535> dscpValue <0-63> mode <inService | OutofService> state <disabled | enabled> kaTime <60-7200> kaInterval <5-60> kaProbe <4-8>
The following is an example of how to configure a CDC for the media interception over TCP.
% 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
% set addressContext default intercept callDataChannel <callDataChannel_name> mediationServer <MS_name> media 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>
The following is an example of how to configure a CDC for the media interception over UDP.
% 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
The SBC supports IPSec for signaling interception over TCP.
The SBC supports IPSec for media interception over TCP and UDP.
% set addressContext default intercept callDataChannel <callDataChannel_name> mediationServer <MS_name> signaling ipAddress <IP_Address> portNumber <0-65535> dscpValue <0-63> protocolType <tcp | udp> mode <inService | OutofService> state <disabled | enabled>
The protocolType
udp
is not supported for signaling interception.
The following is an example of how to configure a CDC for the signaling interception.
% 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
% set addressContext default intercept callDataChannel CDC rtcpInterception enabled % commit
The rtcpInterception
parameter is visible, when interceptStandard
and vendorId
is configured as IMS LI.
The parameter liPolDipForRegdOodMsg
when enabled is used to indicate SBC to send policy request to PSX for registered Out-Of-Dialog requests(messages) to be intercepted. When this parameter is disabled, policy request is not sent to PSX for registered Out-Of-Dialog requests (messages).
Enable the support for Policy dip, for registered users out-of-dialog messages, to decide on interception, by executing the command
% set addressContext default intercept callDataChannel CDC liPolDipForRegdOodMsg enabled % commit
The liPolDipForRegdOodMsg
parameter is visible, when interceptStandard
and vendorId
is configured as IMS LI.
As user ''Admin'', use the following commands to configure IPSec:
The SBC supports IPSec for signaling interception over TCP.
The SBC supports IPSec for media interception over TCP and UDP.
localIdentity ipAddress
– The SBC Interface Group IP associated with the LI CDC.
remoteIdentity ipAddress
– The Mediation Server IP configured in the LI CDC.
The recommended setting for LI IPsec mode is 'transport'.
For more information on IPsec configuration, refer to the section IP Security - CLI.
### create and configure IKE and IPsec protection profiles set profiles security ipsecProtectionProfile PRGGSX2_IPSEC_PROT_PROF saLifetimeTime 28800 set profiles security ipsecProtectionProfile PRGGSX2_IPSEC_PROT_PROF espAlgorithms integrity hmacSha1,hmacMd5 set profiles security ipsecProtectionProfile PRGGSX2_IPSEC_PROT_PROF espAlgorithms encryption aesCbc128,_3DesCbc set profiles security ikeProtectionProfile PRGGSX2_IKE_PROT_PROF saLifetimeTime 28800 set profiles security ikeProtectionProfile PRGGSX2_IKE_PROT_PROF algorithms encryption aesCbc128,_3DesCbc set profiles security ikeProtectionProfile PRGGSX2_IKE_PROT_PROF algorithms integrity hmacSha1,hmacMd5 set profiles security ikeProtectionProfile PRGGSX2_IKE_PROT_PROF dpdInterval noDpd ### create IKE peer set addressContext default ipsec peer PRGGSX2 ipAddress 10.54.78.20 preSharedKey 00000000000000000000000000000000 localIdentity type ipV4Addr ipAddress 10.220.41.161 set addressContext default ipsec peer PRGGSX2 remoteIdentity type ipV4Addr ipAddress 10.54.78.20 set addressContext default ipsec peer PRGGSX2 protocol ikev1 protectionProfile PRGGSX2_IKE_PROT_PROF ### create an SPD rule for this IKE peer set addressContext default ipsec spd PRGGSX2_SPD state enabled precedence 1001 set addressContext default ipsec spd PRGGSX2_SPD localIpAddr 10.220.41.161 localIpPrefixLen 32 remoteIpAddr 10.54.78.20 remoteIpPrefixLen 32 set addressContext default ipsec spd PRGGSX2_SPD action protect set addressContext default ipsec spd PRGGSX2_SPD protocol 0 set addressContext default ipsec spd PRGGSX2_SPD protectionProfile PRGGSX2_IPSEC_PROT_PROF set addressContext default ipsec spd PRGGSX2_SPD mode transport set addressContext default ipsec spd PRGGSX2_SPD peer PRGGSX2 ### enable IPsec on the IP interface group set addressContext default ipInterfaceGroup LIG1 enabled
The SBC is enhanced to support IMS LI for PS-to-PS Handover scenarios. The enhancement has no impact on the IMS routing.
Enter the show commands to view the configurations.
To view the intercept details, execute the following command:
show status addressContext default intercept callDataChannel callDataChannel CDC { mediationServerMediaStatus MS1 { tcpChannelstatus inService; tcpPacketsSent 0; tcpPacketsLost 0; udpPacketsSent 0; udpPacketsLost 0; } mediationServerSignalingStatus MS1 { tcpChannelStatus inService; DSRSuccess 0; DSRFailures 0; } } [ok]
To view the CDC configuration, execute the following command:
show addressContext default intercept nodeNumber 7788; callDataChannel CDC { dsrProtocolVersion 0; interceptStandard etsi; vendorId verint; ipInterfaceGroupName LIG1; liPolDipForRegdOodMsg enabled; rtcpInterception enabled; mediaIpInterfaceGroupName LIG1; mediationServer MS1 { signaling { ipAddress 10.54.78.20; portNumber 65300; protocolType tcp; mode inService; state enabled; } media { tcp { ipAddress 10.54.78.20; portNumber 65120; mode inService; state enabled; } udp { ipAddress 10.54.78.20; portNumber 65200; mode inService; state enabled; } } } } [ok]