|
|
| Line 1: |
Line 1: |
| − | Lawful Interception with [[Tmedia]] running [[Toolpack]] software is capable of performing lawful interception of calls, based on ETSI 201 671 v2-1-1 standard.
| + | #REDIRECT [[Tmedia_Lawful_Intercept]] |
| − | | + | |
| − | ==Functionality overview==
| + | |
| − | | + | |
| − | [[Image:Lawful-intercept-details.png|thumb|360px|Schematic showing interception of a call already routed with a Tmedia]]
| + | |
| − | | + | |
| − | Lawful interception will identify a call to intercept, and send the following information to one or multiple Law Enforcement agencies:
| + | |
| − | * information on an intercepted call (calling/called numbers, timestamps, call duration, etc.)
| + | |
| − | * audio from both directions of the call
| + | |
| − | | + | |
| − | Interception of a call is triggered by:
| + | |
| − | * A phone number to monitor
| + | |
| − | * A date/time period
| + | |
| − | A call that matches the number and the time period will be intercepted.
| + | |
| − | | + | |
| − | ==Toolpack implementation==
| + | |
| − | With a [[Tmedia]] system running the [[Toolpack]] software (version 2.7 or above), lawful interception is triggered by a routing script. This script uses the information from a configuration file (csv format), to determine which phone number must be intercepted during which time period.
| + | |
| − | | + | |
| − | A call that matches the number (calling or called number) and the time period will be intercepted.
| + | |
| − | | + | |
| − | During the interception, two outgoing calls toward an interception [[NAP]] will be placed, each containing a copy of the audio of one direction of the intercepted call. The specified [[NAP]] must be configured to point to the Law Enforcement Agency, generally using ISDN trunks.
| + | |
| − | | + | |
| − | In addition, information records (containing general call information like calling/called number, timestamps, and call duration, etc.) will be sent to the Law Enforcement Agency. That information is sent as data files (format specified by ETSI 201 671 v2-1-1) to a FTP server (Toolpack also supports SFTP for more security).
| + | |
| − | | + | |
| − | Lawful Intercept configuration (NAP to use, login information of the FTP/SFTP server, target numbers to intercept, etc.) can be configured in the [[Toolpack]] Web Portal.
| + | |
| − | See the following page for more information: [[configuring_lawful_interception|Configure Lawful Interception in Toolpack]].
| + | |
| − | | + | |
| − | ==Information to get from Law Enforcement Agencies==
| + | |
| − | In order to use Lawful interception in Toolpack, the Law Enforcement Agency must provide:
| + | |
| − | * List of targets to intercept:
| + | |
| − | ** Unique target identifier (defined as LIID in ETSI 201 671 v2-1-1)
| + | |
| − | ** Target phone number
| + | |
| − | ** Start and end date/time for the interception
| + | |
| − | * ISDN trunks (or eventually SS7 trunks or SIP path) to carry intercepted call audio
| + | |
| − | * FTP/SFTP server address, user name, password and directory path to use for uploading call information (defined as IRI records in ETSI 201 671 v2-1-1)
| + | |
| − | | + | |
| − | This information must be entered in Toolpack configuration as explained in the following page: [[configuring_lawful_interception|Configure Lawful Interception in Toolpack]].
| + | |
| − | | + | |
| − | [[category:Coming Soon]]
| + | |
| − | [[category:Needs revising]]
| + | |
