Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cookbooks:core-cookbook:devel [2011/07/05 09:38] 85.178.69.40 |
cookbooks:core-cookbook:devel [2013/01/11 14:48] (current) alexh [workdir] |
||
|---|---|---|---|
| Line 497: | Line 497: | ||
| + | ==== corelog ==== | ||
| + | |||
| + | Set the debug level used to print some log messages from core, which might become annoying and don't represent critical errors. For example, such case is failure to parse incoming traffic from the network as SIP message, due to someone sending invalid content. | ||
| + | |||
| + | Default value is -1 (L_ERR). | ||
| + | |||
| + | Example of usage: | ||
| + | |||
| + | < | ||
| + | corelog=1 | ||
| + | </ | ||
| ==== debug ==== | ==== debug ==== | ||
| Line 727: | Line 738: | ||
| maxbuffer=65536 | maxbuffer=65536 | ||
| + | | ||
| + | ==== sql_buffer_size ==== | ||
| + | |||
| + | The size in bytes of the SQL buffer created for data base queries. For database drivers that use the core db_query library, this will be maximum size object that can be written or read from a database. Default value is 65535. | ||
| + | |||
| + | Example of usage: | ||
| + | |||
| + | sql_buffer_size=131070 | ||
| ==== max_while_loops ==== | ==== max_while_loops ==== | ||
| Line 857: | Line 876: | ||
| port=5080 | port=5080 | ||
| + | |||
| + | ==== pv_buffer_size ==== | ||
| + | |||
| + | The size in bytes of internal buffer to print dynamic strings with pseudo-variables inside. The default value is 1024. | ||
| + | |||
| + | Example of usage: | ||
| + | |||
| + | < | ||
| + | pv_buffer_size=2048 | ||
| + | </ | ||
| + | |||
| + | ==== pv_buffer_slots ==== | ||
| + | |||
| + | The number of internal buffer slots to print dynamic strings with pseudo-variables inside. The default value is 10. | ||
| + | |||
| + | Example of usage: | ||
| + | |||
| + | < | ||
| + | pv_buffer_slots=12 | ||
| + | </ | ||
| ==== reply_to_via ==== | ==== reply_to_via ==== | ||
| Line 982: | Line 1021: | ||
| user_agent_header=" | user_agent_header=" | ||
| </ | </ | ||
| + | |||
| + | ==== version_table ==== | ||
| + | Set the name of the table holding the table version. Usefull if the proxy is sharing a database within a project and during upgrades. Default value is " | ||
| + | |||
| + | Example of usage: | ||
| + | |||
| + | | ||
| ==== workdir ==== | ==== workdir ==== | ||
| Line 1195: | Line 1241: | ||
| | | ||
| + | |||
| + | |||
| + | ==== tcp_accept_no_cl ==== | ||
| + | |||
| + | Control whether to throw or not error when there is no Content-Length header for requests received over TCP. It is required to be set to **yes** for XCAP traffic sent over HTTP/1.1 which does not use Content-Length header, but splits large bodies in many chunks. The module **sanity** can be used then to restrict this permission to HTTP traffic only, testing in route block in order to stay RFC3261 compliant about this mandatory header for SIP requests over TCP. | ||
| + | |||
| + | Default value is **no**. | ||
| + | |||
| + | <code c> | ||
| + | tcp_accept_no_cl=yes | ||
| + | </ | ||
| ==== tcp_async ==== | ==== tcp_async ==== | ||
| Line 1561: | Line 1618: | ||
| ==== real_time ==== | ==== real_time ==== | ||
| - | Sets real time priority for all the ser processes, or the timers (bitmaks). | + | Sets real time priority for all the ser processes, or the timers (bitmask). |
| | | ||
| 1 - the " | 1 - the " | ||
| Line 1630: | Line 1687: | ||
| Without parameter, the function copies the current URI into a new branch. Thus, leaving the main branch (the URI) for further manipulation. | Without parameter, the function copies the current URI into a new branch. Thus, leaving the main branch (the URI) for further manipulation. | ||
| - | With a parameter, the function copies the URI in the parameter into a new branch. Thus, the current URI is not manipulated. Note: append_branch(uri) still copies the destination URI, which is usually | + | With a parameter, the function copies the URI in the parameter into a new branch. Thus, the current URI is not manipulated. Note: append_branch(uri) still copies the destination URI, which is usually |
| Note that it's not possible to append a new branch in " | Note that it's not possible to append a new branch in " | ||
