Lawful Interception - Revision history

Luc Morissette: Removed the version reference to the ETSI spec - we now support version 3.1

2022-02-24T18:54:26Z

Removed the version reference to the ETSI spec - we now support version 3.1

← Older revision		Revision as of 14:54, 24 February 2022
Line 13:		Line 13:
	** Forwards a copy of call audio (both directions) to the agency through forked calls (Content of Communication link (CC link) - a call toward the agency, carrying intercepted audio)		** Forwards a copy of call audio (both directions) to the agency through forked calls (Content of Communication link (CC link) - a call toward the agency, carrying intercepted audio)
	** Sends information records ([[IRI]] records) to the agency		** Sends information records ([[IRI]] records) to the agency
	* The Telcobridges Lawful Interception implementation is based on specification ETSI ES 201 671 ~~v2.1.1 (2001-09)~~, and not CALEA, PCES, and ANSI T1.678		* The Telcobridges Lawful Interception implementation is based on specification ETSI ES 201 671, and not CALEA, PCES, and ANSI T1.678

	==Lawful Interception Requirements==		==Lawful Interception Requirements==

Luc Morissette at 19:55, 27 September 2021

2021-09-27T19:55:29Z

← Older revision		Revision as of 15:55, 27 September 2021
Line 156:		Line 156:
	Ben Yi,450-621-1990		Ben Yi,450-621-1990
	</pre>		</pre>
			<br>
	'''Complete configuration instructions are here: '''		'''Complete configuration instructions are here: '''
	*[[Toolpack:Lawful_Interception_Settings_E\|\|Enable Lawful Interception]]		*[[Toolpack:Lawful_Interception_Settings_E\|Enable Lawful Interception]]
			<br>

	==Lawful Interception Statistics==		==Lawful Interception Statistics==

Luc Morissette: Removed the routing script configuration -> Full instructions are better

2021-09-27T19:54:57Z

Removed the routing script configuration -> Full instructions are better

← Older revision		Revision as of 15:54, 27 September 2021
Line 156:		Line 156:
	Ben Yi,450-621-1990		Ben Yi,450-621-1990
	</pre>		</pre>
	*[[Toolpack:Enable Lawful Interception in Routing Script B\|Enable Lawful Interception in a Routing Scripts]]
	** The <<lawful interception>> routing script filter is provided with toolpack		'''Complete configuration instructions are here: '''
	** Users only need to <<include>> it in their current routing script<br>		*[[Toolpack:Lawful_Interception_Settings_E\|\|Enable Lawful Interception]]
	~~<pre>~~
	~~require~~ '~~lawful_intercept~~'
	~~(...)~~
	~~include LawfulIntercept~~
	~~(...)~~
	~~after_filter~~ :~~method => :enable_lawful_intercept~~
	~~</pre>~~
	* ~~For more information on Routing Scripts, please see~~ [[~~Routing script tutorial~~:~~Mini Development Guide~~\|~~mini development guide~~]]

	==Lawful Interception Statistics==		==Lawful Interception Statistics==

Luc Morissette: Removed toolpack 2.7

2021-09-27T19:52:30Z

Removed toolpack 2.7

← Older revision		Revision as of 15:52, 27 September 2021
Line 156:		Line 156:
	Ben Yi,450-621-1990		Ben Yi,450-621-1990
	</pre>		</pre>
	*[[Toolpack:Enable Lawful Interception in Routing Script B\|Enable Lawful Interception in a Routing Scripts]] ~~([[Toolpack:Enable Lawful Interception in Routing Script A\|For Toolpack 2.7]])~~		*[[Toolpack:Enable Lawful Interception in Routing Script B\|Enable Lawful Interception in a Routing Scripts]]
	** The <<lawful interception>> routing script filter is provided with toolpack		** The <<lawful interception>> routing script filter is provided with toolpack
	** Users only need to <<include>> it in their current routing script<br>		** Users only need to <<include>> it in their current routing script<br>

Abrassard: /* References */

2019-06-20T10:51:02Z

References

← Older revision		Revision as of 06:51, 20 June 2019
Line 188:		Line 188:

	* [http://en.wikipedia.org/wiki/Lawful_interception Wikipedia lawful intercept article]		* [http://en.wikipedia.org/wiki/Lawful_interception Wikipedia lawful intercept article]
	* [~~http~~://~~cryptome~~.org/~~espy~~/~~ES201-671-v211~~.pdf ETSI ES 201 671 V2.1.1 (~~2001~~-09) ~~- Cryptome~~]		* [https://www.etsi.org/deliver/etsi_es/201600_201699/201671/03.02.01_60/es_201671v030201p.pdf ETSI ES 201 671 V3.2.1 (2018-05)]
	* [http://asn1-playground.oss.com/ ASN.1 Playground - learn, play, test]		* [http://asn1-playground.oss.com/ ASN.1 Playground - learn, play, test]
	* [https://www.marben-products.com/asn.1/services/decoder-asn1-security.html Free Online Security ASN.1 Messages Decoder]		* [https://www.marben-products.com/asn.1/services/decoder-asn1-security.html Free Online Security ASN.1 Messages Decoder]

William Wong at 01:58, 2 January 2019

2019-01-02T01:58:22Z

← Older revision		Revision as of 21:58, 1 January 2019
Line 1:		Line 1:
	Lawful intercept is a feature provided by service providers to law enforcement agencies (FBI, Interpol, RCMP, etc.) that ~~allow~~ law enforcement agencies to intercept calls by receiving a copy of the audio of both parties and call information records.		Lawful intercept is a feature provided by service providers to law enforcement agencies (FBI, Interpol, RCMP, etc.) that allows law enforcement agencies to intercept calls by receiving a copy of the audio of both parties and call information records.

	==Overview==		==Overview==

Allyntree: Needs revising edit

2018-03-16T19:12:00Z

Needs revising edit

William Wong: /* Configuring Lawful Interception */

2016-10-18T10:41:20Z

Configuring Lawful Interception

← Older revision		Revision as of 06:41, 18 October 2016
Line 166:		Line 166:
	after_filter :method => :enable_lawful_intercept		after_filter :method => :enable_lawful_intercept
	</pre>		</pre>
	** For more information on ~~routing scripts~~, please see [[Routing script tutorial:Mini Development Guide\|mini development guide]]		* For more information on Routing Scripts, please see [[Routing script tutorial:Mini Development Guide\|mini development guide]]

	==Lawful Interception Statistics==		==Lawful Interception Statistics==

William Wong: /* Configuring Lawful Interception */

2016-10-18T10:40:02Z

Configuring Lawful Interception

← Older revision		Revision as of 06:40, 18 October 2016
Line 166:		Line 166:
	after_filter :method => :enable_lawful_intercept		after_filter :method => :enable_lawful_intercept
	</pre>		</pre>
			** For more information on routing scripts, please see [[Routing script tutorial:Mini Development Guide\|mini development guide]]

	==Lawful Interception Statistics==		==Lawful Interception Statistics==

William Wong: /* Configuring Lawful Interception */

2016-10-18T10:33:47Z

Configuring Lawful Interception

← Older revision		Revision as of 06:33, 18 October 2016
Line 156:		Line 156:
	Ben Yi,450-621-1990		Ben Yi,450-621-1990
	</pre>		</pre>
	*[[Toolpack:Enable Lawful Interception in Routing Script B\|Enable Lawful Interception in a Routing Scripts]]		*[[Toolpack:Enable Lawful Interception in Routing Script B\|Enable Lawful Interception in a Routing Scripts]] ([[Toolpack:Enable Lawful Interception in Routing Script A\|For Toolpack 2.7]])
	** The <<lawful interception>> routing script filter is provided with toolpack		** The <<lawful interception>> routing script filter is provided with toolpack
	** Users only need to <<include>> it in their current routing script<br>		** Users only need to <<include>> it in their current routing script<br>

← Older revision		Revision as of 15:12, 16 March 2018
Line 1:		Line 1:
	A feature provided by service providers to law enforcement agencies (FBI, Interpol, RCMP, etc.) that ~~allowing~~ law enforcement agencies to intercept calls by receiving a copy of the audio of both parties and call information records.		Lawful intercept is a feature provided by service providers to law enforcement agencies (FBI, Interpol, RCMP, etc.) that allow law enforcement agencies to intercept calls by receiving a copy of the audio of both parties and call information records.

	==Overview==		==Overview==
Line 5:		Line 5:
	[[Image:Lawful-intercept-details.png\|thumb\|360px\|Schematic showing interception of a call already routed with a Tmedia]]		[[Image:Lawful-intercept-details.png\|thumb\|360px\|Schematic showing interception of a call already routed with a Tmedia]]

	* Lawful Interception (process of intercepting a ~~target's~~ conversation)		* Lawful Interception (process of intercepting a conversation)
	* Interception target (someone under investigation by law enforcement agency, and whom the agency wants to intercept calls)		* Interception target (someone under investigation by a law enforcement agency, and for whom the agency wants to intercept the calls)
	* Law enforcement agency ( an agency that has, by law, the power to request the interception of calls ~~toward~~ or from targets)		* Law enforcement agency ( an agency that has, by law, the power to request the interception of calls to or from targets)
	* A law enforcement agency sends, to the service provider, a list of targets to intercept (phone numbers)		* A law enforcement agency sends to the service provider a list of targets to intercept (phone numbers)
	* Service provider configures its equipment to intercept the ~~targets, based on~~ phone numbers		* Service provider configures its equipment to intercept the target phone numbers
	* When service provider equipment ~~detect~~ a call that involves a target to intercept, it		* When service provider equipment detects a call that involves a target to intercept, it
	** Forwards a copy of call audio (both directions) to the agency through forked calls (Content of Communication link (CC link) - a call toward the agency, carrying intercepted audio)		** Forwards a copy of call audio (both directions) to the agency through forked calls (Content of Communication link (CC link) - a call toward the agency, carrying intercepted audio)
	** Sends information records ([[IRI]] records) to the agency		** Sends information records ([[IRI]] records) to the agency
	* Telcobridges Lawful Interception implementation is based on specification ETSI ES 201 671 v2.1.1 (2001-09), and not CALEA, PCES, and ANSI T1.678		* The Telcobridges Lawful Interception implementation is based on specification ETSI ES 201 671 v2.1.1 (2001-09), and not CALEA, PCES, and ANSI T1.678

	==Lawful Interception Requirements==		==Lawful Interception Requirements==
Line 21:		Line 21:
	*** LIID (Lawful Intercept Identifier, unique identifier assigned to a target by an agency) for the target		*** LIID (Lawful Intercept Identifier, unique identifier assigned to a target by an agency) for the target
	*** Phone number of the target		*** Phone number of the target
	*** Start/end ~~date~~ and ~~time~~ for the interception		*** Start and end dates and times for the interception
	** Service provider updates targets in its equipment and equipment ~~detect~~ a matching calling or called number, and activates the interception		** Service provider updates targets in its equipment and equipment detects a matching calling or called number, and activates the interception
	* Intercepting targets		* Intercepting targets
	** In a call, each call leg can be an interception target		** In a call, each call leg can be an interception target
Line 44:		Line 44:
	* Forking does NOT require DSPs		* Forking does NOT require DSPs
	* Audio forking is done as soon as possible		* Audio forking is done as soon as possible
	** Immediately for the audio <<from>> the target (this may include even the ring back tone, or may include audio from incoming call during ringing)		** Immediately for the audio <<from>> the target (this may include even the ring back tone, or may include audio from an incoming call during ringing)
	** Upon joining with ~~other~~ active leg for the audio <<to>> the target		** Upon joining with another active leg for the audio <<to>> the target

	==IRI records==		==IRI records==

	The call data (known as Intercept Related Information or [[IRI]] in Europe and Call Data or CD in the US) consists of information about the targeted communications, including destination of a voice call (e.g., called party’s telephone number), source of a call (caller’s phone number), time of the call, duration, ~~etc~~.		The call data (known as Intercept Related Information or [[IRI]] in Europe and Call Data or CD in the US) consists of information about the targeted communications, including destination of a voice call (e.g., called party’s telephone number), source of a call (caller’s phone number), time of the call, duration, and more.
	Intercept Related Information record (IRI record) is a CDR-style record that contains IRI information on an intercepted call		Intercept Related Information record (IRI record) is a CDR-style record that contains IRI information on an intercepted call

	===Types of IRI records===		===Types of IRI records===

	# IRI-BEGIN: ~~Indicate~~ that the interception is starting at first event of the communication attempt, opening the IRI transaction		# IRI-BEGIN: Indicates that the interception is starting at first event of the communication attempt, opening the IRI transaction
	# IRI-CONTINUE: ~~Indicate~~ call state change at any time during the communication attempt within the IRI transaction		# IRI-CONTINUE: Indicates call state change at any time during the communication attempt within the IRI transaction
	# IRI-END: ~~Indicate~~ the end of the interception at the end of the communication attempt, closing the IRI transaction		# IRI-END: Indicates the end of the interception at the end of the communication attempt, closing the IRI transaction
	# IRI-REPORT: General use for any non-communication related events		# IRI-REPORT: General use for any non-communication related events

	For information related to an existing communication case, the record types 1 to 3 shall be used. They form an IRI		For information related to an existing communication case, the record types 1 to 3 shall be used. They form an IRI
	transaction for each communication case or communication attempt, which corresponds directly to the communication		transaction for each communication case or communication attempt, which corresponds directly with the communication
	phase (set-up, active or release).<br>		phase (set-up, active or release).<br>

	For some packet oriented data services such as GPRS, the first event of a communication attempt ~~shall be~~ the Packet Data Protocol (PDP)		For some packet-oriented data services such as GPRS, the first event of a communication attempt is the Packet Data Protocol (PDP)
	context activation or a similar event and an IRI-BEGIN record ~~shall be~~ issued. The end of the communication attempt		context activation or a similar event and an IRI-BEGIN record is issued. The end of the communication attempt
	shall be the PDP context deactivation or a similar event and an IRI-END record shall be issued. While a PDP context is		shall be the PDP context deactivation or a similar event and an IRI-END record shall be issued. While a PDP context is
	active, IRI-CONTINUE records ~~shall be~~ used for CC relevant IRI data records, IRI-REPORT records otherwise.<br>		active, IRI-CONTINUE records are used for CC relevant IRI data records, IRI-REPORT records otherwise.<br>

	Record type 4 is used for non-communication related subscriber action, like Subscriber Controlled Input (SCI) for		Record type 4 is used for non-communication related subscriber action, like Subscriber Controlled Input (SCI) for
	service activation. For simple cases, it can also be ~~applicable~~ for reporting unsuccessful communication attempts.<br>		service activation. For simple cases, it can also be used for reporting unsuccessful communication attempts.<br>
	The record type is an explicit part of the record. The 4 record types are defined independently of target communication		The record type is an explicit part of the record. The 4 record types are defined independently of target communication
	events. The actual indication of one or several communication events, which caused the generation of an IRI record, is		events. The actual indication of one or several communication events, which caused the generation of an IRI record, is
	part of further parameters ~~within~~ the record's, information content. Consequently, the record types of the IRI		part of further parameters in the record's information content. Consequently, the record types of the IRI
	transactions are not related to specific messages of the signalling protocols of a communication case, and are therefore		transactions are not related to specific messages of the signalling protocols of a communication case, and are therefore
	independent of future enhancements of the intercepted services, of network specific features~~, etc~~. Any transport level		independent of future enhancements of the intercepted services and of network specific features. Any transport level
	information (i.e. higher-level services) on the target communication-state or other target communication related		information (i.e. higher-level services) on the target communication-state or other target communication related
	information is contained ~~within~~ the information content of the IRI records.<br>		information is contained in the information content of the IRI records.<br>

	For some packet oriented data services such as GPRS, if Lawful Interception (LI) is being activated during an already established PDP		For some packet oriented data services such as GPRS, if Lawful Interception (LI) is being activated during an already established PDP
	context or similar, an IRI-BEGIN record will mark the start of the interception. If LI is being deactivated during an		context or similar, an IRI-BEGIN record will mark the start of the interception. If LI is being deactivated during an
	established PDP context or similar, no IRI-END record will be transmitted. The end of interception can be		established PDP context or similar, no IRI-END record will be transmitted. The end of interception can be
	communicated to the LEA ~~by other means~~ Handover Interface Port 1 (for Administrative Information)~~(HI1) (~~whereas Handover Interface Port 2 (~~HT2~~) transports IRI information and Handover Interface Port 3 (~~HT3~~) transports Content of Communication information).		communicated to the LEA a Handover Interface Port 1 (HI1)(for Administrative Information); whereas Handover Interface Port 2 (HI2) transports IRI information and Handover Interface Port 3 (HI3) transports Content of Communication information).

	===Typical information found in an IRI record===		===Typical information found in an IRI record===
Line 102:		Line 102:
	* They provide information on the interception, and call state		* They provide information on the interception, and call state
	* In a call, each call leg can be an interception target		* In a call, each call leg can be an interception target
	* When a leg is an interception target, ~~it’s~~ intercepted:		* When a leg is an interception target, it's intercepted:
	** Audio «from» this leg is forked to a new outgoing call toward the agency		** Audio «from» this leg is forked to a new outgoing call toward the agency
	** Audio «to» this leg is forked to a new outgoing call toward the agency		** Audio «to» this leg is forked to a new outgoing call toward the agency
Line 195:		Line 195:

	[[category:Tmedia_Features]]		[[category:Tmedia_Features]]
	~~[[category:Needs revising]]~~