Page History
| Panel | ||||
|---|---|---|---|---|
In this section:
|
| Info | ||
|---|---|---|
| ||
Related articles:
|
Overview
| Excerpt |
|---|
| Noprint | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
In this section:
|
...
The |
...
platforms support Lawful Intercept (LI) functionality using one of the following solutions:
The |
...
|
...
media stream (call content) to an IP address provided by the IS. |
...
The |
...
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:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Call Data Channel (CDC) Model
The
| Spacevars | ||
|---|---|---|
|
- The CDC model includes two fields,
vendorIdandinterceptStandard,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.
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
, Lawful intercept takes precedence, and any direct media calls are converted to ordinary pass-through calls.Spacevars 0 product
Intercept criteria are identified by an "Intercept_Criteria_Type" and "Intercept_Criteria" (or criteria ID) attribute. The
currently supports the following intercept criteria types:Spacevars 0 product
- 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:
- EMA: see Address Context - Lawful Intercept
- CLI: see Intercept - CLI
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
node must be registered with "calea" and appropriate password instead of using default "admin/admin" as the Agent login and password.Spacevars 0 product
A separate license is required on EMS and/or
to enable this service. Without these licenses, the APIs for this feature are not accessible. Only authorized users can access LI functions.Spacevars 0 product
The following Centralized PSX diagram includes the
for the example.Spacevars 0 series
| Caption | ||||
|---|---|---|---|---|
| ||||
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 | ||||
|---|---|---|---|---|
| ||||
For EMA-related LI configurations, please see EMA User Guide.
...
| Spacevars | ||
|---|---|---|
|
...
| Spacevars | ||
|---|---|---|
|
...
| Spacevars | ||
|---|---|---|
|
...
Overview
Content Tools