SIP Flood Protection - Revision history

Monica at 15:43, 31 October 2013

2013-10-31T15:43:26Z

Dana: /* Notes */

2013-05-30T13:12:59Z

‎Notes

Dana at 13:51, 20 May 2013

2013-05-20T13:51:24Z

Dana at 13:51, 20 May 2013

2013-05-20T13:51:04Z

Dana at 13:49, 20 May 2013

2013-05-20T13:49:41Z

Dana: /* Configuration */

2012-11-08T15:46:46Z

‎Configuration

Dana: /* Notes */

2012-11-08T15:45:33Z

‎Notes

Dana: /* Configuration */

2012-11-08T15:44:39Z

‎Configuration

Monica: /* Configuration */

2012-11-08T15:11:43Z

‎Configuration

Monica at 15:08, 8 November 2012

2012-11-08T15:08:25Z

← Older revision		Revision as of 15:43, 31 October 2013
Line 55:		Line 55:
	* [[SIP Configuration File]]		* [[SIP Configuration File]]
	* [[Telephony]]		* [[Telephony]]
		+
		+	[[Category:SIP]] [[Category:Server]] [[Category:Flood]] [[Category:Protection]]

← Older revision		Revision as of 13:12, 30 May 2013
Line 54:		Line 54:

	* [[SIP Configuration File]]		* [[SIP Configuration File]]
		+	* [[Telephony]]

@@ Line 33: / Line 33: @@
   ; NOTE! This mechanism is activated by default, to disable it configure this parameter to false.
   ;floodprotection=on
 ====Parameter '''floodevents'''====

@@ Line 1: / Line 1: @@
-This page describes the SIP protection against flood attacks.
+Starting with Yate 4.2 or SVN revision 5234, Yate provides a protection mechanism against several types of SIP flood attacks.
-Starting with Yate 4.2 or SVN revision 5234, Yate provides a protection mechanism against several types of SIP flood attacks. The aim of this document is to provide information about this protection and how can it be used.
+The aim of this document is to provide information about this protection and how can it be used.
 === Functionality===

@@ Line 1: / Line 1: @@
 This page describes the SIP protection against flood attacks.
 Starting with Yate 4.2 or SVN revision 5234, Yate provides a protection mechanism against several types of SIP flood attacks. The aim of this document is to provide information about this protection and how can it be used.
@@ Line 24: / Line 22: @@
 This protection is on by default in Yate and is triggered when the SIP processing engine detects that it handled a configured number of SIP events in a row.
-The interesting parameters in regards to this mechanism are the ''floodevents'' and ''floodprotection'' parameters in the ''general'' section of ''ysipchan.conf'':
+The interesting parameters in regards to this mechanism are the ''floodevents'' and ''floodprotection'' parameters in the ''general'' section of ''ysipchan.conf''.
-* '''floodprotection''' - this parameter explicitly enables or disables the filter mechanism. This setting is on by default. This value is applicable on reload.
+==== Parameter '''floodprotection'''====
   ; floodprotection: bool: Activate the drop mechanism for INVITE/REGISTER/SUBSCRIBE/OPTIONS messages when
@@ Line 35: / Line 35: @@
-* '''floodevents''' - this parameter specifies at which number of handled events in a row a flood warning should be displayed. If the filter mechanism was enabled, this is also the value at which the SIP messages mentioned above are dropped. Note that setting this parameter to 0 will disable the display of flood warning and the filter mechanism, even if ''floodprotection'' is set to true. This value is applicable on reload.
+====Parameter '''floodevents'''====
   ; floodevents: int: How many SIP events retrieved in a row trigger a flood warning and the drop mechanism

@@ Line 27: / Line 27: @@
 * '''floodprotection''' - this parameter explicitly enables or disables the filter mechanism. This setting is on by default. This value is applicable on reload.
   ; floodevents: int: How many SIP events retrieved in a row trigger a flood warning and the drop mechanism
@@ Line 33: / Line 42: @@
   ;  setting this parameter to 0 will disable the flood warning and protection.
   ;floodevents=100
 === Notes===

← Older revision		Revision as of 15:45, 8 November 2012
Line 49:		Line 49:

	* In case of flood attacks using INVITE messages, it is also useful to limit the allowed number of simultaneous calls using the '''maxchans''' configuration parameter in the ''general'' section of ''ysipchan.conf''. It can be an added protection for the case when lots of INVITEs pass through the filter while the number of handled events has not yet reached the triggering threshold. The ''maxchans'' value is applicable on reload. If not configured, it defaults to the value set in ''yate.conf'' in the ''telephony'' section for the same parameter. The value from ''yate.conf'' is not applicable on reload.		* In case of flood attacks using INVITE messages, it is also useful to limit the allowed number of simultaneous calls using the '''maxchans''' configuration parameter in the ''general'' section of ''ysipchan.conf''. It can be an added protection for the case when lots of INVITEs pass through the filter while the number of handled events has not yet reached the triggering threshold. The ''maxchans'' value is applicable on reload. If not configured, it defaults to the value set in ''yate.conf'' in the ''telephony'' section for the same parameter. The value from ''yate.conf'' is not applicable on reload.
		+
		+
		+	See also:
		+
		+	* [[SIP Configuration File]]