You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

In this section:

Related articles:

Overview


The 

Unable to show "metadata-from": No such page "_space_variables"
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 
    Unable to show "metadata-from": No such page "_space_variables"
  • SBC ERE solution consisting of the ERE, a third-party Intercept Server and EMA

The

Unable to show "metadata-from": No such page "_space_variables"
works in conjunction with the Intercept Server as well as the ERE and EMA (or an external PSX and
Unable to show "metadata-from": No such page "_space_variables"
) 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

Unable to show "metadata-from": No such page "_space_variables"
supports four types of LI:

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

In order to intercept media packets, ensure

Unable to show "metadata-from": No such page "_space_variables"
is either the same or a higher version as that of the SBC and PSX platforms. 


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:

Table 1: LI Types and Supported Platforms

LI TypeCDC ConfigurationPlatformsRouting PolicyLI InterfaceStreams Supported
Intercept StandardVendor IdD-SBCSBC SWe/SBC 7000External PSXEREX1X2X3D-SBCSBC SWe/SBC 7000
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 SupportedSupportedSupportedSupportedSOAP
  • Diameter
  • Diameter over IPsec
  • UDP
  • UDP over IPsec
Not SupportedAudio, Video

Call Data Channel (CDC) Model

The 

Unable to show "metadata-from": No such page "_space_variables"
 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.


  • No labels