Kamailio module - Revision history

Pchero: /* SANITY */

2020-05-17T19:59:24Z

SANITY

@@ Line 59: / Line 59: @@
 ==== mf_process_maxfwd_header(max_value) ====
 Same as maxfwd_process(max_value).
 == SANITY ==

Pchero: /* HTABLE */

2019-07-28T08:15:42Z

HTABLE

Show changes

Pchero at 06:42, 28 July 2019

2019-07-28T06:42:06Z

← Older revision		Revision as of 06:42, 28 July 2019
Line 272:		Line 272:
	sl_send_reply("404", "Not found");		sl_send_reply("404", "Not found");
	</pre>		</pre>

			== See also ==
			* https://www.kamailio.org/docs/modules/5.3.x/

	[[category:kamailio]]		[[category:kamailio]]

Pchero: /* SANITY */

2019-07-24T07:11:45Z

SANITY

← Older revision		Revision as of 07:11, 24 July 2019
Line 211:		Line 211:

	These checks are not required by Kamailio itself for its functionality. But on the other side it does not make much sense if a broken request traverses through a SIP network if it is rejected sooner or later by a SIP device any way. As every sanity check cost extra performance because of additional parsing and evaluation it is with this module now up to the Kamailio administrator what checks should be done on which request.		These checks are not required by Kamailio itself for its functionality. But on the other side it does not make much sense if a broken request traverses through a SIP network if it is rejected sooner or later by a SIP device any way. As every sanity check cost extra performance because of additional parsing and evaluation it is with this module now up to the Kamailio administrator what checks should be done on which request.

			=== Parameters ===
			==== default_checks(integer) ====
			This parameter determines which of the checks from the sanity module are executed if no parameter was given to the sanity_check function call. By default, all implemented checks are included in the execution of the sanity_check function. Ths integer value is the sum of the check numbers which should be executed by default.

			Default value is "3047". This resolves to the following list of checks: ruri_sip_version(1), ruri_scheme(2), required_headers(4), cseq_method(32), cseq_value(64), content_length(128), expires_value(256), proxy_require(512), digest_credentials(2048).
			<pre>
			modparam("sanity", "default_checks", 1)
			</pre>

			==== uri_checks(integer) ====
			This parameter determines which URIs are going to be checked if the 'parse uri' will be executed.

			Default value is 7. This resolves to the following list of parsed URIs: Request URI(1), From URI(2) and To URI(4)
			<pre>
			modparam("sanity", "uri_checks", 3)
			</pre>

	=== Functions ===		=== Functions ===

Pchero: /* sanity_check([msg_checks [, uri_checks]]) */

2019-07-24T07:01:17Z

sanity_check([msg_checks [, uri_checks]])

← Older revision		Revision as of 07:01, 24 July 2019
Line 215:		Line 215:
	==== sanity_check([msg_checks [, uri_checks]]) ====		==== sanity_check([msg_checks [, uri_checks]]) ====
	This function makes a row of sanity checks over the given SIP request. The behavior of the function is also controlled by autodrop parameter. If autodrop=0, the function returns false (-1) if one of the checks failed. When autodrop=1, the function stops the execution of configuration file. In both cases, if one of checks fails the module sends a precise error reply via SL send_reply(). Thus there is no need to reply with a generic error message.		This function makes a row of sanity checks over the given SIP request. The behavior of the function is also controlled by autodrop parameter. If autodrop=0, the function returns false (-1) if one of the checks failed. When autodrop=1, the function stops the execution of configuration file. In both cases, if one of checks fails the module sends a precise error reply via SL send_reply(). Thus there is no need to reply with a generic error message.

			Optionally the function takes an integer argument which overwrites the global module parameter default_checks. This makes it possible to run certain tests from script region. The integer value is again the sum of the checks (like for the module parameter) which should be executed at this function call.

			Optionally the function takes a second integer argument which overwrites the global module parameter uri_checks and thus determines which URIs will be checked if the parse uri test will be executed.

	'''Example'''		'''Example'''

Pchero: /* sanity_check([msg_checks [, uri_checks]]) */

2019-07-23T22:08:02Z

sanity_check([msg_checks [, uri_checks]])

← Older revision		Revision as of 22:08, 23 July 2019
Line 214:		Line 214:
	=== Functions ===		=== Functions ===
	==== sanity_check([msg_checks [, uri_checks]]) ====		==== sanity_check([msg_checks [, uri_checks]]) ====
	This function makes a row of sanity checks over the given SIP request.		This function makes a row of sanity checks over the given SIP request. The behavior of the function is also controlled by autodrop parameter. If autodrop=0, the function returns false (-1) if one of the checks failed. When autodrop=1, the function stops the execution of configuration file. In both cases, if one of checks fails the module sends a precise error reply via SL send_reply(). Thus there is no need to reply with a generic error message.

			'''Example'''
			<pre>
			if(!sanity_check("17895", "7")) {
			xlog("Malformed SIP message from $si:$sp\n");
			exit;
			}
			</pre>

	== SL ==		== SL ==

Pchero: /* SL */

2019-07-23T22:05:02Z

@@ Line 204: / Line 204: @@
 ==== mf_process_maxfwd_header(max_value) ====
 Same as maxfwd_process(max_value).
 == SL ==

Pchero: /* SL */

2019-07-23T21:23:33Z

← Older revision		Revision as of 21:23, 23 July 2019
Line 215:		Line 215:

	To speed up the filtering process, the module uses a timeout		To speed up the filtering process, the module uses a timeout

			=== Functions ===
			==== sl_send_reply(code, reason) ====
			For the current request, a reply is sent back having the given code and text reason. The reply is sent stateless, totally independent of the Transaction module and with no retransmission for the INVITE's replies.

			If the code is in the range 300-399 (redirect reply), the current destination set is appended to the reply as Contact header. The destination set contains the request URI(R-URI), if it is modified compared to the received one, plus the branches added to the request(e.g., after an append_branch() or lookup("location")). If the R-URI was changed but it is not desired to be part of the destination set, it can be reverted using the function revert_uri().

			Custom headers to the reply can be added using append_to_reply() function from textops module.

			'''Parameters'''
			* code: Return code
			* reason: Reason phrase

			'''Example'''
			<pre>
			sl_send_reply("404", "Not found");
			</pre>

	[[category:kamailio]]		[[category:kamailio]]

Pchero: /* MAXFWD */

2019-07-23T21:13:23Z

MAXFWD

← Older revision		Revision as of 21:13, 23 July 2019
Line 158:		Line 158:

	== MAXFWD ==		== MAXFWD ==
	* https://www.kamailio.org/docs/modules/5.0.x/modules/maxfwd.html~~#maxfwd.f.mf_process_maxfwd_header~~		* https://www.kamailio.org/docs/modules/5.0.x/modules/maxfwd.html

	Max-Forward SIP header 와 관련된 기능을 수행할 수 있는 모듈이다.		Max-Forward SIP header 와 관련된 기능을 수행할 수 있는 모듈이다.
Line 201:		Line 201:
	...		...
	</pre>		</pre>

			==== mf_process_maxfwd_header(max_value) ====
			Same as maxfwd_process(max_value).

	== SL ==		== SL ==

Pchero: /* htable.listTables */

2019-07-23T21:05:25Z

htable.listTables

@@ Line 139: / Line 139: @@
 	size: 256
 	dmqreplicate: 0
+}
 </pre>