Differences

This shows you the differences between two versions of the page.

--- cookbooks:4.0.x:core [2013/03/02 22:20] – created miconda
+++ cookbooks:4.0.x:core [2018/08/21 07:21] (current) – henningw
@@ Line 1: / Line 1: @@
 ====== Kamailio SIP Server v4.0.x (stable): Core Cookbook ======
-This tutorial collects the functions and parameters exported by Kamailio core to configuration file.
+This tutorial collects the functions and parameters exported by Kamailio core to [[cookbooks:4.0.x:core:cfg|configuration file]].
 **Note:** The parameters on this page are **NOT** in alphabetical order.
@@ Line 774: / Line 774: @@
 Prototype: **loadmodule "modulepath"**
-If modulepath is only modulename or modulename.so, then Kamailio will try to search also for **modulename/modulename.so**, very useful when usining directly the version compiled in the source tree.
+If modulepath is only modulename or modulename.so, then Kamailio will try to search also for **modulename/modulename.so**, very useful when using directly the version compiled in the source tree.
 Example of usage:
@@ Line 1252: / Line 1252: @@
 If the internal resolver/cache is enabled you can add/remove records by hand (using sercmd or xmlrpc) using the DNS RPCs, e.g. dns.add_a,
-dns.add_srv, dns.delete_a a.s.o. For more info on DNS RPCs see http://sip-router.org/docbook/sip-router/branch/master/rpc_list/rpc_list.html#dns.add_a
+dns.add_srv, dns.delete_a a.s.o. For more info on DNS RPCs see http://www.kamailio.org/docs/docbooks/4.0.x/rpc_list/rpc_list.html#dns.add_a
 Note: During startup of SIP-Router, before the internal resolver is loaded, the system resolver will be used (it will be used for queries done from module register functions or modparams fixups, but not for queries done from mod_init() or normal fixups).
@@ Line 1500: / Line 1500: @@
 ==== 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 is not enabled, it has no effect.
+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 is not enabled, it has no effect.
   tcp_conn_wq_max = bytes (default 32 K)
@@ Line 1614: / Line 1614: @@
 ==== tcp_wq_max ====
-Maximum bytes queued for write allowed globally. It has no effect if tcp_write_buf is not enabled.
+Maximum bytes queued for write allowed globally. It has no effect if tcp_buf_write is not enabled.
   tcp_wq_max = bytes (default 10 Mb)
@@ Line 2342: / Line 2342: @@
   * onreply_route[0] (stateless): equivalent to set_reply_*() (it's better to use set_reply_* though)
-  * onreply_route[!=0] (tm): ignored
+  * onreply_route[!=0] <nowiki>(tm)</nowiki>: ignored
   * branch_route: affects the current branch only (all messages sent on this branch, like possible retransmissions and CANCELs).