Versions Compared

Old Version 9

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c, userName='null'}
JIRAIDAUTHSBX-75410
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86573c09001659ee33a580027, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c85a017fd9015a5f286f710015, userName='null'}

Panel

In this section:

Table of Contents
maxLevel3

Info
iconfalse

Related articles:

Children Display

Overview

Excerpt

The 

Spacevars
0series4
platforms support Lawful Intercept (LI) functionality using one of the following solutions:

  • Centralized PSX solution consisting of an external PSX, a third-party Intercept Server (IS), and EMS
  • SBC ERE solution consisting of the ERE, a third-party IS Intercept Server and EMA

The

Spacevars
0product
works in conjunction with the IS, 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 IS Intercept Server. It also sends media stream (call content) to an IP address provided by the IS Intercept Server.

The

Spacevars
0product
supports three four types of LI flavors:

  • Default LI
  • IMS LI
  • PCSI LI
  • PacketCable 2.0 LI


Info

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 provides lists the types of LI flavors supported in on different platforms:

Div
classpdf6pttext
Caption
0Table
1LI Types and Supported Platforms
LI TypeCDC ConfigurationPlatformsRouting PolicyLI InterfaceStream Supported
Intercept StandardVendor Id
Flavors
D-SBCSBC SWe/SBC 5000/7000 Series
packetCable
External PSXEREX1X2X3D-SBCSBC SWe/SBC 5000/7000 Series
None/Utimaco/Verint
Legacy LI (default)
Not supportedSupportedpacketCableSs8PCSI LISupported
PacketCable, PacketCablePlusEtsiNone/Utimaco/Verint

Supported

SupportedSupportedSupportedSOAP
  • RADIUS
  • RADIUS over IPsec
UDPAudio OnlyAudio only
PCSI LIPacketCableSs8SupportedSupportedSupportedNot SupportedTLSNot Supported
  • TCP
  • TCP over IPsec

Audio,Video and T140

Audio, Video and T140
IMS LI
Not supported
3gpp/etsiVerint/utimaco/none/GroupTwoThousandSupportedSupportedSupportedSupportedSOAP
  • DSR
  • DSR over IPsec
  • UDP
  • UDP over IPsec
  • TCP
  • TCP over IPsec
Audio OnlyAll Streams
PacketCable 2.0PacketcableVTwonone
IMS LINot supported
/atos Not SupportedSupportedSupportedNot SupportedSOAP
  • Diameter
  • Diameter over IPsec
  • UDP
  • UDP over IPsec
Not SupportedAudio, Video
Supported

Call Data Channel (CDC) Model

The 

Spacevars
0product
 supports various flavors types of LI and using a generic Call Data Channel (CDC) model to support any new flavors . This facilitates adding support for new types of LI. The CDC configuration model is described as follows:

  • The CDC model includes two fields, vendorId and interceptStandard, to support identifying and configuring the various LI flavorstypes.
  • Each Mediation Server is configurable to support both signaling and media interception. Separate configuration fields are present under the Mediation Server to handle this functionality.
  • The CDC model for a given mediation server allows media interception over UDP and/or TCP.
  • The CDC model for a given mediation server supports signaling interception either over TCP or UDP. It does not support both simultaneously.