Panel | ||||
---|---|---|---|---|
In this section:
|
Info | ||
---|---|---|
| ||
Related articles:
|
The
Spacevars | ||
---|---|---|
|
The figure below depicts the deployment scenario of the
Spacevars | ||
---|---|---|
|
Figure 1: SBC for Lawful Interception
Spacevars | ||
---|---|---|
|
X3 interface: This interface is known as Media interface that is supported by Ribbon
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Info | ||||
---|---|---|---|---|
| ||||
The
|
At a high level, the functions performed by the Lawful Intercept are:
Support for sending intercepted signaling messages over TCP, using an optional IPSec tunnel
If media interception over UDP and TCP are both configured at the CDC, the transport type for interception is decided based on the following conditions:
Info | ||
---|---|---|
| ||
The SBC is enhanced to support IMS LI for PS-to-PS Handover scenarios. The enhancement has no impact on the IMS routing. |
For more information on EMS and PSX configuration for Lawful intercept, refer to Lawful Intercept.
For configuration details, see Configuring SBC For Lawful Interception.
Info | ||
---|---|---|
| ||
The interface between PSX and the SBC allows the PSX to send, and the SBC to receive, the TAP ID or Lawful Intercept ID. Use the EMS to perform the relevant configurations. The TAP ID, is a decimal value between 1 and 4,294,967,295 (4 bytes). The default value of TAP ID is 0. If the SBC receives a non-zero TAP ID from the PSX, it embeds the value in the Correlation ID (CCID) and sends the TAP ID as a separate Tag Length Value (TLV) in the Direct Signaling Report (DSR) message. If the SBC receives the value 0 as TAP ID, it does not take any action. |
Pagebreak |
---|