|
|
| (75 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | Lawful Intercept configuration in [[Toolpack]] Web Portal is made with the following steps:
| + | === '''''Applies to version(s): v2.7''''' === |
| − | # Configuring a Law Enforcement Agency and it's parameters
| + | {{DISPLAYTITLE:Configuring Lawful Interception}} |
| − | # Creation of a NAP connected to the Law Enforcement Agency
| + | |
| − | # Providing a list of targets to intercept (through a coma-separate-values .csv file)
| + | |
| − | # Enabling the Lawful Intercept routing script filter
| + | |
| | | | |
| − | Here is how these steps are performed using Toolpack Web Portal.
| |
| | | | |
| − | = Configuring a Law Enforcement Agency and it's parameters =
| |
| − | * Log into the Web Portal
| |
| − | * Go to the left menu of the Web Portal
| |
| − | * Click the "Lawful Intercept" section, under "Gateway"
| |
| | | | |
| − | This page contains global Lawful Intercept parameters, and a list of Law Enforcement Agencies. | + | '''Note:''' This procedure assumes that a Law Enforcement Agencies NAP has been created. Each Law Enforcement Agencies requires that a NAP be configured in order that the intercepted call legs are sent. NAPs can be dedicated for lawful interceptions or not. |
| | | | |
| − | == Global Lawful Intercept parameters ==
| |
| − | * NWO (Network Operator) Identifier: An internationally unique identifier that represents the network operator, access provider or service provider using the [[Tmedia]] equipment
| |
| | | | |
| − | == Law Enforcement Agency parameters ==
| |
| − | Multiple Law Enforcement Agencies can be created in [[Toolpack]]. Each act in an independent manner from the others, and can intercept the same calls, or different calls.
| |
| | | | |
| − | Each Law Enforcement Agency has the following parameters:
| + | Multiple Law Enforcement Agencies can be created in [[Toolpack]]. They operate independently of each other. They can intercept the same calls, as well as different ones. |
| − | * Name
| + | |
| − | * .csv file that contains the list of targets to intercept
| + | |
| − | * NAP to use for making outgoing calls to Law Enforcement Agency, carrying audio for intercepted call legs
| + | |
| − | * Configuration of FTP client for uploading IRI records to Law Enforcement Agency's FTP server:
| + | |
| − | ** IP address or domain name of the FTP server
| + | |
| − | ** User name to use for FTP server login
| + | |
| − | ** Password to use for FTP server login
| + | |
| − | ** Remote directory to store IRI records into
| + | |
| − | ** FTP connection timeout
| + | |
| − | ** Maximum number of IRI entries in the upload queue
| + | |
| − | ** Maximum time a IRI entry can remain in the upload queue
| + | |
| | | | |
| − | = Creation of a NAP connected to the Law Enforcement Agency =
| + | '''To configure a Law Enforcement Agency:''' |
| − | Create a NAP, like would normally be done with [[Toolpack]]. The ETSI specifications refer to ISDN NAP, but other type of NAPs are also supported by TelcoBridges. This NAP must be connected to the Law Enforcement Agency that will receive the intercepted calls.
| + | |
| | | | |
| − | Documentation on NAPs creation can be found here: [[Toolpack_v2.3:Creating_a_NAP|Creating a NAP]]
| + | 1- Select '''Lawful Interception''' from the navigation panel |
| | | | |
| − | = Providing a list of targets to intercept (through a coma-separate-values .csv file) =
| + | [[Image:Toolpack_Navigation_LawfulInterception_A.png]] |
| | | | |
| − | == Uploading/modifying Lawful Intercept Targets configuration files (.csv) ==
| + | 2- Enter an Indentifier for the Network Operator. |
| − | The list of targets to intercept is provided as a .csv file. Each configured Law Enforcement Agency points to it's own .csv file.
| + | * Click '''Save''' |
| | | | |
| − | The .csv file is uploaded from the Web Portal:
| + | 3- Create a Lawful Agency |
| − | * Log into the Web Portal
| + | * Click '''Create New Lawful Agency''' |
| − | * Go to the left menu of the Web Portal
| + | |
| − | * Click the "File Db" section, under "Gateway" | + | |
| − | * Edit one of the listed File Db, or click "Create New File Db" to create a new one
| + | |
| − | * Under section "Lawful Intercept Targets", click "import" (to create new file) or "update" one of the existing files
| + | |
| | | | |
| − | To activate a .csv file, go to the Law Enforcement Agency configuration page (left menu, "Lawful Intercept" under "Gateway), and select the .csv file in the appropriate Law Enforcement Agency's configuration page.
| |
| | | | |
| − | == Format Lawful Intercept Targets configuration files (.csv) ==
| + | [[Image:Lawful_configuration_shot.png]] |
| − | The Lawful Intercept Targets configuration files must be formatted in .csv (coma-separated values) format. The following columns must be present:
| + | |
| − | * LIID: Text string that uniquely identifies the target to intercept. This ID will be provided with each outgoing call on interception NAP to the Law Enforcement Agency, and in each IRI record uploaded to the FTP server.
| + | |
| − | * Phone number: The phone number of the target to intercept. Any call with this number as the calling, or the called number, will be intercepted.
| + | |
| − | * Start time: Starting date/time from which the interception can take place. Calls made before that date from/to the target won't be intercepted.
| + | |
| − | * End time: End date/time where this target interception ends. Calls made after that date from/to the target won't be intercepted.
| + | |
| | | | |
| − | Example:
| + | 4- Configure the Lawful Agency parameters: |
| − | LIID,number,start,end
| + | * Click '''Save'''. |
| − | John Smith,555-0001,2012-10-24T00:00:00-05:00,2012-10-24T23:59:59-05:00
| + | |
| − | James Bond,333-3007,2012-01-01T00:00:00-05:00,2012-12-31T23:59:59-05:00
| + | |
| | | | |
| − | = Enabling the Lawful Intercept routing script filter =
| |
| − | Interpretation of the Lawful Intercept Targets configuration files (.csv) is done by a routing script filter, that can easily be added to any existing routing script used by the [[Toolpack]] system.
| |
| | | | |
| − | Documentation on routing script can be found here: [[Scriptable_Routing_Engine|Scriptable Routing Engine]]
| + | [[Image:lawful_agency_shot.png]] |
| | | | |
| − | The Lawful Intercept filter is activated by:
| |
| − | * Including the 'Lawful intercept' module in your routing script
| |
| − | * Include the LawfulIntercept class
| |
| − | * Add the Lawful Intercept "after_filter" to your script
| |
| | | | |
| − | Here is an example "simple routing" script that enables Lawful Intercept:
| + | ==List of Parameters== |
| | | | |
| − | require 'base_routing'
| + | * [[Parameter: LI_Name|Name]] |
| − | require 'lawful_intercept'
| + | * [[Parameter: FTP Server Address|FTP Server Address]] |
| − |
| + | * [[Parameter: FTP User Name|FTP User Name]] |
| − | class SimpleRouting < BaseRouting
| + | * [[Parameter: FTP Server Password|FTP Server Password]] |
| − | include LawfulIntercept
| + | * [[Parameter: FTP Server Directory|FTP Server Directory]] |
| − |
| + | * [[Parameter: IRI Records Queue Length|IRI Records Queue Length]] |
| − | route_match :call_field_name => :called
| + | * [[Parameter: IRI Upload Mode|IRI Upload Mode]] |
| − | route_match :call_field_name => :calling
| + | * [[Parameter: Maximum grouped file delay before upload|Maximum grouped file delay before upload]] |
| − | route_match :call_field_name => :nap
| + | * [[Parameter: Maximum grouped file upload size|Maximum grouped file upload size]] |
| − | route_remap :call_field_name => :called, :route_field_name => :remapped_called
| + | * [[Parameter: File name prefix|File name prefix]] |
| − | route_remap :call_field_name => :calling, :route_field_name => :remapped_calling
| + | |
| − | route_remap :call_field_name => :nap, :route_field_name => :remapped_nap
| + | |
| − |
| + | |
| − | after_filter :method => :enable_lawful_intercept
| + | |
| − | end
| + | |
| − |
| + | |
| − | @@routing = SimpleRouting.new
| + | |
| − |
| + | |
| − | def init_routes( routes )
| + | |
| − | @@routing.init routes
| + | |
| − | end
| + | |
| − |
| + | |
| − | def route( call, nap_list )
| + | |
| − | @@routing.route call, nap_list
| + | |
| − | end
| + | |
