Kamailio-kamailio.cfg - Revision history

Pchero: /* branch_route */

2020-03-10T12:04:04Z

branch_route

@@ Line 647: / Line 647: @@
 Note: for backward compatibility reasons,  the main 'reply' routing block can b e also identified by 'onreply_route{...}' or 'onreply_route[0]{...}'.
-=== branch_route ===
+=== onreply_route ===
 == See also ==

2020-03-10T12:01:28Z

route

@@ Line 630: / Line 630: @@
 </pre>
-=== route ===
+=== reply_route ===
 === branch_route ===

2020-02-08T20:20:50Z

Routing Blocks

← Older revision		Revision as of 20:20, 8 February 2020
Line 595:		Line 595:

	There can be so called sub-route blocks, which can be invoked from another route blocks, like a function. Invocation is done with 'route' followed by the name of sub-route to execute, enclosed in between parentheses.		There can be so called sub-route blocks, which can be invoked from another route blocks, like a function. Invocation is done with 'route' followed by the name of sub-route to execute, enclosed in between parentheses.
			<pre>
			request_route{
			...
			route("test");
			...
			}

			route["test"]{
			...
			}
			</pre>

	=== request_route ===		=== request_route ===

2020-02-08T20:20:32Z

Routing Blocks

← Older revision		Revision as of 20:20, 8 February 2020
Line 582:		Line 582:
	== Routing Blocks ==		== Routing Blocks ==
	The routing blocks are the parts of the configuration file executed by kamailio at runtime. They can be seen as blocks of actions similar to functions (or procedures) from common programming languages.		The routing blocks are the parts of the configuration file executed by kamailio at runtime. They can be seen as blocks of actions similar to functions (or procedures) from common programming languages.


	A routing block is identified by a specific token, followed by a name in between square brackets and actions in between curly braces.		A routing block is identified by a specific token, followed by a name in between square brackets and actions in between curly braces.
Line 590:		Line 589:
	}		}
	</pre>		</pre>
			The name can be any alphanumeric string, with specific routing blocks enforcing a particular format.
			: route(number) is equivalent to route("number").

			Route blocks can be executed on network events (e.g., receiving a SIP message), timer events(e.g., retransmission timeout) or particular events specific to modules.

			There can be so called sub-route blocks, which can be invoked from another route blocks, like a function. Invocation is done with 'route' followed by the name of sub-route to execute, enclosed in between parentheses.

	=== request_route ===		=== request_route ===

2019-07-27T13:39:20Z

Core Functions

@@ Line 579: / Line 579: @@
 force_rport();
 </pre>
 == See also ==

2019-07-24T07:19:59Z

Core parameters

@@ Line 566: / Line 566: @@
      alias=other.domain.com:5060
      alias=another.domain.com:5060
 </pre>

2019-07-13T23:07:12Z

advertised_port

@@ Line 555: / Line 555: @@
 <pre>
    advertised_port=5080
 </pre>

2019-07-13T22:56:38Z

Core parameters

@@ Line 541: / Line 541: @@
 == Core parameters ==
 === advertised_address ===
 == See also ==

2019-07-13T22:50:09Z

WSS

@@ Line 521: / Line 521: @@
    };
 </pre>
 == See also ==

2019-07-13T22:44:29Z

Core Keywords