User Tools
cookbooks:4.4.x:core
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
cookbooks:4.4.x:core [2016/03/28 23:26] miconda created |
cookbooks:4.4.x:core [2018/08/15 21:10] (current) henningw [tcp_wq_max] |
||
|---|---|---|---|
| Line 125: | Line 125: | ||
| "this is a string value" | "this is a string value" | ||
| - | 'this is another string value" | + | 'this is another string value' |
| // next is a boolean | // next is a boolean | ||
| Line 972: | Line 972: | ||
| Prototype: **loadmodule " | Prototype: **loadmodule " | ||
| - | If modulepath is only modulename or modulename.so, | + | If modulepath is only modulename or modulename.so, |
| Example of usage: | Example of usage: | ||
| Line 1007: | Line 1007: | ||
| + | ==== log_engine_data ==== | ||
| + | Set specific data required by the log engine. See also the **log_engine_type**. | ||
| + | |||
| + | <code c> | ||
| + | log_engine_type=" | ||
| + | log_engine_data=" | ||
| + | </ | ||
| + | |||
| + | ==== log_engine_type ==== | ||
| + | |||
| + | Specify what logging engine to be used and its initialization data. A logging engine is implemented as a module. Supported values are a matter of the module. | ||
| + | |||
| + | For example, see the readme of **log_custom** module for more details. | ||
| + | |||
| + | <code c> | ||
| + | log_engine_type=" | ||
| + | log_engine_data=" | ||
| + | </ | ||
| ==== log_facility ==== | ==== log_facility ==== | ||
| Line 1023: | Line 1041: | ||
| ==== log_name ==== | ==== log_name ==== | ||
| - | Allows to configure a log_name prefix which will be used when printing to syslog. This is useful to filter log messages when running many instances of Kamailio on same server | + | Allows to configure a log_name prefix which will be used when printing to syslog |
| < | < | ||
| - | log_name=" | + | log_name=" |
| </ | </ | ||
| Line 1755: | Line 1773: | ||
| ==== tcp_conn_wq_max ==== | ==== tcp_conn_wq_max ==== | ||
| - | Maximum bytes queued for write allowed per connection. Attempting to queue more bytes would result in an error and in the connection being closed (too slow). If tcp_write_buf | + | Maximum bytes queued for write allowed per connection. Attempting to queue more bytes would result in an error and in the connection being closed (too slow). If tcp_buf_write |
| tcp_conn_wq_max = bytes (default 32 K) | tcp_conn_wq_max = bytes (default 32 K) | ||
| Line 1874: | Line 1892: | ||
| ==== tcp_wq_max ==== | ==== tcp_wq_max ==== | ||
| - | Maximum bytes queued for write allowed globally. It has no effect if tcp_write_buf | + | Maximum bytes queued for write allowed globally. It has no effect if tcp_buf_write |
| tcp_wq_max = bytes (default 10 Mb) | tcp_wq_max = bytes (default 10 Mb) | ||
| Line 2259: | Line 2277: | ||
| ==== force_rport ==== | ==== force_rport ==== | ||
| - | Force_rport() adds the rport parameter to the first Via header of the received message. Thus, Kamailio will add the received | + | force_rport() adds the rport parameter to the first Via header of the received message. Thus, Kamailio will add the received port to the top most Via header in the SIP message, even if the client does not indicate support for rport. This enables subsequent SIP messages to return to the proper port later on in a SIP transaction. |
| - | This is useful for NAT traversal, to enforce symmetric response | + | This is useful for NAT traversal, to enforce symmetric response |
| - | The rport parameter is defined in RFC 3581. | + | The rport parameter is defined in [[https:// |
| - | Note: there is also a force_rport parameter which changes the gobal behavior | + | Note: there is also a force_rport parameter which changes the global behaviour |
| Example of usage: | Example of usage: | ||
| force_rport(); | force_rport(); | ||
| - | |||
| ==== add_rport ==== | ==== add_rport ==== | ||
| Alias for force_rport(); | Alias for force_rport(); | ||
cookbooks/4.4.x/core.1459200384.txt.gz ยท Last modified: 2016/03/28 23:26 by miconda
Page Tools
