cookbooks:5.2.x:core
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cookbooks:5.2.x:core [2018/11/28 09:23] – [onsend_route] typo mslehto | cookbooks:5.2.x:core [2020/04/03 07:34] (current) – [mem_join] henningw | ||
|---|---|---|---|
| Line 47: | Line 47: | ||
| </ | </ | ||
| + | Usually setting a parameter is ended by end of line, but it can be also ended with **;** (semicolon). This should be used when the grammar of a parameter allows values on multiple lines (like **listen** or **alias**) and the next line creates a conflict by being swallowed as part of value for previous parameter. | ||
| + | |||
| + | <code c> | ||
| + | alias=" | ||
| + | </ | ||
| + | |||
| + | If you want to use a reserved config keyword as part of a parameter, you need to enclose it in quotes. See the example below for the keyword " | ||
| + | |||
| + | <code c> | ||
| + | listen=tcp: | ||
| + | </ | ||
| ==== Modules Settings Section ==== | ==== Modules Settings Section ==== | ||
| Line 725: | Line 736: | ||
| ==== auto_bind_ipv6 ==== | ==== auto_bind_ipv6 ==== | ||
| - | When turned on, Kamailio will automatically bind to all IPv6 addresses (much like the default behaviour for IPv4). | + | When turned on, Kamailio will automatically bind to all IPv6 addresses (much like the default behaviour for IPv4). Default value is off. |
| Example: | Example: | ||
| Line 855: | Line 866: | ||
| ==== flags ==== | ==== flags ==== | ||
| - | **Alias name: bool** | + | SIP message (transaction) flags can have string names. |
| + | The //name// for flags cannot be used for **branch** or **script flags**(*) | ||
| + | |||
| + | |||
| + | <code c> | ||
| + | ... | ||
| + | flags | ||
| + | FLAG_ONE | ||
| + | FLAG_TWO | ||
| + | ... | ||
| + | </ | ||
| + | |||
| + | (*) The named flags feature was propagated from the source code merge back in 2008 and is not extensively tested. The recommended way of defining flags is using [[cookbooks: | ||
| + | <code c> | ||
| + | #!define FLAG_NAME FLAG_BIT | ||
| + | </ | ||
| ==== force_rport ==== | ==== force_rport ==== | ||
| Line 971: | Line 998: | ||
| ==== latency_limit_db ==== | ==== latency_limit_db ==== | ||
| - | Limit of latency in ms for db operations. If a db operation executed via DB API v1 takes longer that its value, a message is printed in the logs, showing the first 50 characters of the db query. | + | Limit of latency in us (micro-seconds) |
| Line 1263: | Line 1290: | ||
| It can be set via config reload framework. | It can be set via config reload framework. | ||
| - | Default is 0 (disabled). | + | Default is 1 (enabled). |
| <code c> | <code c> | ||
| Line 1386: | Line 1413: | ||
| ==== pv_buffer_size ==== | ==== pv_buffer_size ==== | ||
| - | The size in bytes of internal buffer to print dynamic strings with pseudo-variables inside. The default value is 8192 (8kB). | + | The size in bytes of internal buffer to print dynamic strings with pseudo-variables inside. The default value is 8192 (8kB). Please keep in mind that for xlog messages, there is a dedicated module parameter to set the internal buffer size. |
| Example of usage: | Example of usage: | ||
| Line 1425: | Line 1452: | ||
| reply_to_via=0 | reply_to_via=0 | ||
| + | | ||
| + | ==== route_locks_size ==== | ||
| + | |||
| + | Set the number of mutex locks to be used for synchronizing the execution of messages sharing the same Call-Id. In other words, enables Kamailio to execute sequentially the requests and replies received within the same dialog -- a new message received within the same dialog waits until the previous one is routed out. | ||
| + | |||
| + | For smaller impact on parallel processing, its value it should be at least twice the number of kamailio processes (children | ||
| + | |||
| + | Example: | ||
| + | |||
| + | <code c> | ||
| + | route_locks_size = 256 | ||
| + | </ | ||
| ==== server_id ==== | ==== server_id ==== | ||
| Line 1468: | Line 1507: | ||
| ==== sip_warning (noisy feedback) ==== | ==== sip_warning (noisy feedback) ==== | ||
| - | Can be 0 or 1. If set to 1 (default value) a ' | + | Can be 0 or 1. If set to 1 (default value is 0) a ' |
| The header contains several details that help troubleshooting using the network traffic dumps, but might reveal details of your network infrastructure and internal SIP routing. | The header contains several details that help troubleshooting using the network traffic dumps, but might reveal details of your network infrastructure and internal SIP routing. | ||
| Line 2841: | Line 2880: | ||
| Add " | Add " | ||
| + | |||
| ===== Custom Global Parameters ===== | ===== Custom Global Parameters ===== | ||
| Line 3048: | Line 3088: | ||
| - | SIP reply routing block executed by **tm** module. It contains a set of actions to be taken for SIP replies in the contect of an active transaction.. | + | SIP reply routing block executed by **tm** module. It contains a set of actions to be taken for SIP replies in the contect of an active transaction. |
| The ' | The ' | ||
| - | Main 'onreply_route' block is executed before a possible tm ' | + | Core 'reply_route' block is executed before a possible |
| <code c> | <code c> | ||
| Line 3340: | Line 3380: | ||
| * ^ : bitwise XOR | * ^ : bitwise XOR | ||
| * ~ : bitwise NOT | * ~ : bitwise NOT | ||
| - | * << : bitwise left shift | + | * <nowiki><<</ |
| - | * >> : bitwise right shift | + | * <nowiki>>></ |
| Example: | Example: | ||
| Line 3393: | Line 3433: | ||
| | | ||
| Example: if (defined $v && !strempty($v)) $len=strlen($v); | Example: if (defined $v && !strempty($v)) $len=strlen($v); | ||
| + | |||
cookbooks/5.2.x/core.1543396988.txt.gz · Last modified: 2018/11/28 09:23 by mslehto