| Noprint |
|---|
| Panel |
|---|
| borderColor | green |
|---|
| bgColor | transparent |
|---|
| borderWidth | 2 |
|---|
| Additional sections: |
|
Overview
| Excerpt |
|---|
The supports 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 and EMA
The 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 an RTP copy of the call's voice streams (call content) to an IP address provided by the IS. |
Call content is sent from the product | to the IS in an RTP media stream for each direction of an intercepted call. Call content will always be sent to the IP addresses and UDP ports specified by the intercept server in the Signaling Start Response message. The IS decides if it is sent to the LEA based on the configured warrant. The intercept server performs in-band tone detection and sends the appropriate call data messages to the LEA for this detection. The IS detects RFC2833 DTMF Relay RTP packets and sends the appropriate call data messages to the LEA. SBC detects out of band tones and sends the appropriate call data messages to the IS. The IS performs any gateway function of the audio signal required by the LEA before sending the call content to the LEA.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.
Intercept criteria are identified by an "Intercept_Criteria_Type" and "Intercept_Criteria" (or criteria ID) attribute. The currently supports the following intercept criteria types:
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 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 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 for the example.
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | LI 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 |
|---|
| 0 | Figure |
|---|
| 1 | LI Provisioning Diagram (SBC ERE Solution) |
|---|
|
Image Removed |
For EMA-related LI configurations, please see EMA User Guide.
supports three flavors of LIs: The following table describes the configuration information required to distinguish between Default LI, IMS LI, and PCSI LI. | interceptStandard | vendorId | Flavors |
|---|
| packetCable | None/Utimaco/Verint | Legacy LI (default) | | packetCable | Ss8 | PCSI LI | | 3gpp/etsi | Verint/utimaco/none | IMS LI |
|
Call Data Channel (CDC) Model
supports various flavors of LI and a generic Call Data Channel (CDC) model to support any new flavors of LI. The new CDC configuration model is described as follows:- The new CDC model co-exists with the old CDC model. The old CDC model is used only to configure default/legacy LI.
- The new CDC model have introduced two new fields
vendorId and interceptStandard to identify and configure the flavors of the LI. - Each Mediation Server can be configured to support both signaling and media interception. Separate configuration fields are present under the Mediation Server to handle this functionality.
- The new CDC model for a given mediation server allows media interception over UDP and/or TCP.
- The new CDC model for a given mediation server supports signaling interception either over TCP or UDP. It does not support both simultaneously.
| Note |
|---|
The field priIpAddress was used to configure mediation server for IMS LI in SBC 05.00.00S20x VoLTE Release. The field mediaTypeIntercepted was updated with the value "multimedia" to distinguish IMS LI from the Legacy LI |
| Note |
|---|
When upgrading, and you wish to maintain the pre-existing centralized PSX LI solution, no change to local user account is needed. But if a change to an existing solution is desired, or if you are switching to the new ERE solution, a local LI user account must be established. |