Versions Compared

Old Version 13

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
Info
titleNote

Unless otherwise stated, the LI configuration process is the same on Cloud-based and non-Cloud based systems.

The 

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

The

Spacevars
0product
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

Spacevars
0product
supports three LI flavors:

  • Default LI
  • IMS LI
  • PCSI LI

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:

Div
classpdf6pttext
Caption
0Table
1LI Flavors with Supported Platforms
FlavorsCDC ConfigurationPlatformsRouting PolicyLI InterfaceStream Supported
Intercept StandardVendor IdD-SBCSBC SWe/SBC 5000/7000 SeriesExternal PSXEREX1X2X3D-SBCSBC SWe/SBC 5000/7000 Series
Legacy LI (default)packetCable/packetCablePlusEtsiNonenone/Utimacoutimaco/Verintverint

SupportedNote:

SupportedSupportedSupportedSOAP
  • RADIUS
  • RADIUS over IPSec
UDPAudio OnlyAudio Only
PCSI LIpacketCableSs8ss8SupportedNot supportedSupportedSupportedNot SupportedTLSNot Supported
  • TCP
  • TCP over IPSec
All StreamsAudio Only
IMS LI3gppthreeGpp/etsiVerintverint/utimaco/none/groupTwoThousandSupportedSupportedSupportedSupportedSOAP
  • DSR
  • DSR over IPSec
  • UDP
  • UDP over IPSec
  • TCP
  • TCP over IPSec
Info
titleNote
Audio OnlyAll Streams
Legacy/Default LI and IMS LI on D-SBC supports interception of Audio streams only; lawful Intercept of other media streams are supported by PSCI LI.

Call Data Channel (CDC) Model

The 

Spacevars
0product
 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:

  • The CDC model includes two fields, vendorId and interceptStandard, to support identifying and configuring the various LI flavors.
  • 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.