User Tools
cookbooks:devel:core
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
cookbooks:devel:core [2020/04/09 11:15] miconda [Command Line Parameters] |
cookbooks:devel:core [2020/10/14 21:52] miconda [sip_warning (noisy feedback)] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== Core Cookbook ====== |
| + | Version: Kamailio SIP Server v5.5.x (devel) | ||
| ===== Overview ===== | ===== Overview ===== | ||
| Line 970: | Line 971: | ||
| </ | </ | ||
| + | |||
| + | ==== ipv6_hex_style ==== | ||
| + | |||
| + | Can be set to " | ||
| + | |||
| + | Example of usage: | ||
| + | |||
| + | <code c> | ||
| + | ipv6_hex_style = " | ||
| + | </ | ||
| ==== kemi.onsend_route_callback ==== | ==== kemi.onsend_route_callback ==== | ||
| Line 1025: | Line 1036: | ||
| ==== latency_limit_action ==== | ==== latency_limit_action ==== | ||
| - | Limit of latency in ms for config actions. If a config action executed by cfg interpreter takes longer than its value, a message is printed in the logs, showing config path, line and action name when it is a module function, as well as internal action id. | + | Limit of latency in us (micro-seconds) |
| Default value is 0 (disabled). | Default value is 0 (disabled). | ||
| Line 1543: | Line 1554: | ||
| ==== route_locks_size ==== | ==== 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 the config script sequentially for 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. | + | Set the number of mutex locks to be used for synchronizing the execution of config script for messages sharing the same Call-Id. In other words, enables Kamailio to execute the config script sequentially for 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 (all children processes). | For smaller impact on parallel processing, its value it should be at least twice the number of Kamailio processes (all children processes). | ||
| Line 1594: | Line 1605: | ||
| shm_mem_size = 64 (default 64) | shm_mem_size = 64 (default 64) | ||
| + | |||
| + | ==== sip_parser_log ==== | ||
| + | |||
| + | Log level for printing debug messages for some of the SIP parsing errors. | ||
| + | |||
| + | Default: 0 (L_WARN) | ||
| + | |||
| + | <code c> | ||
| + | sip_parser_log = 1 | ||
| + | </ | ||
| + | |||
| + | ==== sip_parser_mode ==== | ||
| + | |||
| + | Control sip parser behaviour. | ||
| + | |||
| + | If set to 1, the parser is more strict in accepting messages that have invalid headers (e.g., duplicate To or From). It can make the system safer, but loses the flexibility to be able to fix invalid messages with config operations. | ||
| + | |||
| + | If set to 0, the parser is less strict on checking validity of headers. | ||
| + | |||
| + | Default: 1 | ||
| + | |||
| + | <code c> | ||
| + | sip_parser_mode = 0 | ||
| + | </ | ||
| ==== sip_warning (noisy feedback) ==== | ==== sip_warning (noisy feedback) ==== | ||
| Line 1680: | Line 1715: | ||
| + | ==== stats_name_separator ==== | ||
| + | Specify the character used as a separator for the internal statistics' | ||
| + | Default value is " | ||
| + | |||
| + | Example of usage: | ||
| + | stats_name_separator = " | ||
| ==== tos ==== | ==== tos ==== | ||
| Line 3680: | Line 3721: | ||
| </ | </ | ||
| - | ==== Log Engine ==== | + | ==== Log Engine |
| The **--log-engine** parameter allows to specify what logging engine to be used, which is practically about the format of the log messages. If not set at all, then Kamailio does the classic style of line-based plain text log messages. | The **--log-engine** parameter allows to specify what logging engine to be used, which is practically about the format of the log messages. If not set at all, then Kamailio does the classic style of line-based plain text log messages. | ||
| Line 3696: | Line 3737: | ||
| * **N** - do not add EOL at the end of JSON document | * **N** - do not add EOL at the end of JSON document | ||
| - | Example of JSON logs when running Kamailio with **--log-engine=json: | + | Example of JSON logs when running Kamailio with "**--log-engine=json: |
| < | < | ||
cookbooks/devel/core.txt ยท Last modified: 2022/04/11 17:10 by bkaufman
Page Tools
