-
<font class="basetext">Adds SIP flood protection and improves Jingle / Google Voice support.</font></div><br/>
8 KB (1,086 words) - 09:08, 31 July 2018
-
== Protection against possible attacks ==
9 KB (1,569 words) - 13:20, 20 March 2013
-
* [[SIP Flood Protection]]
Yate provides a protection mechanism against several types of SIP flood attacks.
9 KB (1,376 words) - 10:01, 27 October 2017
-
* define [[SIP_Flood_Protection|flood protection mechanisms]].
8 KB (1,261 words) - 08:43, 4 November 2013
-
* [[SIP Flood Protection]]
Yate provides a protection mechanism against several types of SIP flood attacks.
8 KB (1,083 words) - 11:49, 27 October 2017
-
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.
4 KB (598 words) - 15:43, 31 October 2013
-
* '''[[SIP_Flood_Protection|flood protections]]''' mechanisms
; for INVITE/REGISTER/SUBSCRIBE/OPTIONS messages if the flood protection is on.
25 KB (3,811 words) - 10:09, 6 July 2018
-
...is used. This will add confidentiality, message authentication, and replay protection to the RTP data.
...ofile for RTP will add confidentiality, message authentication, and replay protection to the protocol.-->
3 KB (431 words) - 08:45, 4 November 2013
-
...interval in milliseconds for this gateway to fire bad client configuration protection.
...has been reached and asp_switch timer has not expired, the client override protection will be fired.
13 KB (2,284 words) - 11:12, 13 December 2017
-
; to fire bad client configuration protection
;protection will be fired.
11 KB (1,842 words) - 09:53, 27 October 2017
-
; to fire bad client configuration protection
;protection will be fired.
15 KB (1,985 words) - 10:45, 27 October 2017
-
... is not standard operating system implementation of semaphore. It's a Yate protection used to avoid too many semaphore signal (unlock) operations
4 KB (491 words) - 10:39, 9 September 2024
