Versions Compared

Old Version 1

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'}

...

borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to Security

...

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

...

  • Intercept Server and EMA

The

Spacevars
0

...

product
works in conjunction with the

...

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

...

Intercept Server. It also sends

...

media stream (call content) to an IP address provided by the

...

Intercept Server.

...

The

Spacevars
0product

...

supports four types of LI:

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

Div
classpdf6pttext
Caption
0Table
1LI Types and Supported Platforms
LI TypeCDC ConfigurationPlatformsRouting PolicyLI InterfaceStream Supported
Intercept StandardVendor IdD-SBCSBC SWe/SBC 5000/7000 SeriesExternal PSXEREX1X2X3D-SBCSBC SWe/SBC 5000/7000 Series
Legacy LI (default)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 LI3gpp/etsiVerint/utimaco/none/GroupTwoThousandSupportedSupportedSupportedSupportedSOAP
  • DSR
  • DSR over IPsec
  • UDP
  • UDP over IPsec
  • TCP
  • TCP over IPsec
Audio OnlyAll Streams
PacketCable 2.0PacketcableVTwonone/atos Not SupportedSupportedSupportedNot SupportedSOAP
  • Diameter
  • Diameter over IPsec
  • UDP
  • UDP over IPsec
Not SupportedAudio, Video

Call Data Channel (CDC) Model

The 

Spacevars
0product
 supports various types of LI using a generic Call Data Channel (CDC) model. 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 types.
  • 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.

 

In some call scenarios, Sonus network elements are not part of the media path. This is referred to as "direct media." When LI and "direct media" are configured on the

Spacevars
0product
, Lawful intercept takes precedence, and any direct media calls are converted to ordinary pass-through calls.

Intercept criteria are identified by an "Intercept_Criteria_Type" and "Intercept_Criteria" (or criteria ID) attribute. The

Spacevars
0product
currently supports the following intercept criteria types:

  • Directory Number
  • SIP URI

Associated with each intercept type are corresponding criteria IDs.

  • If Intercept_Criteria_Type is "Directory Number", then the criteria IDs are "Country Code" and "National Id".
  • If the Intercept_Criteria_Type is "SIP URI", then the criteria ID is "SIP URI".

To configure LI, see following pages:

Centralized PSX Solution

Solution details:

  • Required network elements: external PSX, IS and EMS.
  • User "calea" must be created on SBC before attempting LI provisioning.
  • User must login as "calea" in PSX to do LI CDC provisioning and target settings.
  • LI is not supported for Video and SRTP calls. For LI CDC provisioning, the
    Spacevars
    0product
     node must be registered with "calea" and appropriate password instead of using default "admin/admin" as the Agent login and password.

A separate license is required on EMS and/or

Spacevars
0product
to enable this service. Without these licenses, the APIs for this feature are not accessible. Only authorized users can access LI functions.

The following Centralized PSX diagram includes the

Spacevars
0series
for the example.

Caption
0Figure
1LI Provisioning Diagram (Centralized PSX)

Image Removed

For EMS-related LI configurations, please see Sonus Insight User Guide and Insight Lawful Intercept Guide located at the Sonus Documentation and Support Portal.

SBC ERE Solution

The SBC ERE solution includes the following requirements:

  • Required network elements: EMA, IS and ERE.
  • User "calea" must be created on SBC before attempting LI provisioning.
  • User must login as "calea" in EMA to do LI CDC provisioning and target settings.
  • The "calea" username and appropriate password must be used on the LI server to perform LI target provisioning as opposed to default username/password (calea/calea).
Note

Only "calea" users can access LI functions.

Caption
0Figure
1LI Provisioning Diagram (SBC ERE Solution)

Image Removed

For EMA-related LI configurations, please see EMA User Guide.

...

Spacevars
0product

...

Spacevars
0product

...

Spacevars
0product

...