In this section:
Note
Not applicable to the SBC Software Edition.
When configuring LI through EMA/ERE, you must be 'Calea' user. See "Default Accounts and Passwords" for descriptions of users and permissions.
The
Unable to show "metadata-from": No such page "_space_variables"
provides Lawful Intercept (LI) support using one of two methods:- Using ERE with provisioning support from EMA (license required).
- Using centralized PSX with provisioning support from EMS (license required).
The
Unable to show "metadata-from": No such page "_space_variables"
supports up to 500 simultaneous LI sessions. Unable to show "metadata-from": No such page "_space_variables"
works in coordination with an Intercept Server (IS) 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 ERE (or external PSX in centralized PSX solution), the Unable to show "metadata-from": No such page "_space_variables"
routes the call as directed and additionally reports call events to the IS.The
Unable to show "metadata-from": No such page "_space_variables"
also sends an RTP copy of the call's voice streams (call content) to an IP address provided by the IS. LI is configured by EMA (or EMS in centralized PSX solution). The target number is uploaded to LI table of ERE (or PSX, with the help of EMS).You can configure the LI using only the default AddressContext.
See Lawful Intercept page for an in-depth explanation of LI functionality.
Note
The SBC 52x0 and SBC 7000 systems support creating IP Interface Groups containing sets of IP interfaces that are not "processor friendly" (i.e. carried on physical Ethernet ports served by separate processors). However, restrictions exist regarding the usage of such Interface Groups.
(This ability does not apply to the SBC 51x0 and SBC 5400 systems which have only two physical media ports. IP interfaces from the two physical ports may be configured within the same IP Interface Groups without restriction.)
For complete details, refer to Configuring IP Interface Groups and Interfaces.
Command Syntax
As user 'Calea', use the following commands to configure LI:
% set addressContext <default> intercept callDataChannel <callDataChannel> displaylevel <displaylevel> nodeNumber <integer>
As user 'Calea', use the following command to establish the LI call data channel configuration:
% set addressContext <default> intercept callDataChannel <callDataChannel_name> ipInterfaceGroupName <ipInterfaceGroup_Name> kaTimer <kaTimer_name> priIpAddress <value> priMode <outofservice | standby> priPort <priPort_name> priState <disabled | enabled> retries <value> secIpAddress <IP_Address> secMode <active | outofservice | standby> secState <disabled | enabled>
As user 'Calea', use the following command in System-level mode to retrieve the LI statistics:
> show status addressContext <default> intercept interceptCallDataChannelStatistics <intexierceptCallDataChannelStatistics>
Command Parameters
Intercept Parameters
Parameter | Length/Range | Description |
|---|---|---|
| 1-23 | Lawful Intercept Call Data Channel list for this address context. |
| NA | The user-configured LI Call Data Control Channel name. |
| NA | The global unique node number for the Unable to show "metadata-from": No such page "_space_variables" used by the LI Server for ID. |
| NA | Name of the IP interface group used to stream to the LI Server. |
| 0-65535 | The Keep Alive Timer value, in seconds. (default = 5) |
| NA | The primary LI Server's IPv4 address where Call Data Channel messages are sent. (default = 0.0.0.0) |
| NA | Mode of the primary server. Options are:
|
| 0-65535 | The primary LI Server's UDP port where Call Data Channel messages are sent. (default = 0) |
| NA | Use this flag to enable/disable communication to the primary LI Server.
|
| NA | Number of retries before the LI Call Data Channel is considered as failed. (default = 3) |
| NA | Secondary LI Server's IPv4 address where Call Data Channel messages are sent. (default == 0.0.0.0) |
| NA | Mode of the secondary server. Options are:
|
| NA | Use this flag to enable/disable communication to secondary LI Server.
|
Command Examples
% show status addressContext default intercept
interceptCallDataChannelStatistics
interceptCallDataChannelStatistics default
{
primaryChannelStatus InService;
secondaryChannelStatus outOfService;
StartSuccess 7967;
StartFailures 0;
StopSuccess 7967;
StopFailures 0;
CallAnswerSuccess 7929;
CallAnswerFailures 0;
CallDisconnectSuccess 7965;
CallDisconnectFailures 0;
ServiceInstanceSuccess 0;
ServiceInstanceFailures 0;
IndicationSuccess 185;
IndicationFailures 0;
KeepAliveSuccess 665;
KeepAliveFailures 0;
RestartSuccess 1;
RestartFailures 0;
RadiusAckReceived 53064;
StartResponsesReceived 7967;
}
Overview
Content Tools