Kamailio SIP Server Wiki

User Tools

Site Tools

Trace:
cookbooks:5.4.x:core

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
cookbooks:5.4.x:core [2020/07/17 08:11]
miconda created 		cookbooks:5.4.x:core [2021/05/12 13:35] (current)
giavac [kemi.received_route_callback]
Line 64: Line 64:
 This is the second section of the configuration file, containing the directives to load modules and set their parameters. This is the second section of the configuration file, containing the directives to load modules and set their parameters.
  
-It contains the directives **loadmodule** and **modparam**. In the default configuration file starts with the line setting the path to modules (the assignment to **mpath** core parameter.+It contains the directives **loadmodule** and **modparam**. In the default configuration file it starts with the line setting the path to modules (the assignment to **mpath** core parameter).
  
 Example of content: Example of content:
Line 129: Line 129:
   * integer - numbers of 32bit size   * integer - numbers of 32bit size
   * boolean - aliases to 1 (true, on, yes) or 0 (false, off, no)   * boolean - aliases to 1 (true, on, yes) or 0 (false, off, no)
-  * string - tokens enclosed in between double or single quotes+  * string - tokens enclosed in double or single quotes
  
  
Line 152: Line 152:
 ==== Identifiers ==== ==== Identifiers ====
  
-Identifiers are tokens which are not enclosed in single or double quotes and to match the rules for integer or boolean values.+Identifiers are tokens which are not enclosed in single or double quotes and don't match the rules for integer or boolean values.
  
 For example, the identifiers are the core parameters and functions, module functions, core keywords and statements. For example, the identifiers are the core parameters and functions, module functions, core keywords and statements.
Line 493: Line 493:
 ==== status ==== ==== status ====
  
-If used in onreply_route, this variable is a referece to the status code of the reply. If it used in a standard route block, the variable is a reference to the status of the last reply sent out for the current request.+If used in **onreply_route**, this variable is a reference to the status code of the reply. If used in a standard route block, the variable is a reference to the status of the last reply sent out for the current request.
  
 Example of usage: Example of usage:
Line 506: Line 506:
 ==== snd_af ==== ==== snd_af ====
  
 +In **onsend_route** it identifies the address family (see **af**) used to send the message out.
 ==== snd_ip ==== ==== snd_ip ====
  
 +In **onsend_route** it contains the IP address used by Kamailio to send the message out.
 ==== snd_port ==== ==== snd_port ====
  
 +In **onsend_route** it contains the port used by Kamailio to send the message out.
 ==== snd_proto ==== ==== snd_proto ====
  
 +In **onsend_route** it identifies the protocol (see **proto**) used to send the message out.
 ==== src_ip ==== ==== src_ip ====
  
Line 538: Line 542:
 ==== to_ip ==== ==== to_ip ====
  
 +In **onsend_route** it contains the destination IP address where the message will be sent to.
 ==== to_port ==== ==== to_port ====
  
 +In **onsend_route** it contains the destination port where the message will be sent to.
 ==== to_uri ==== ==== to_uri ====
  
Line 677: Line 683:
 The variable can be used to test if the host part of an URI is in the list. The usefulness of this test is to select the messages that has to be processed locally or has to be forwarded to another server. The variable can be used to test if the host part of an URI is in the list. The usefulness of this test is to select the messages that has to be processed locally or has to be forwarded to another server.
  
-See "alias" to add hostnames,IP addresses and aliases to the list.+See **alias** to add hostnames, IP addresses and aliases to the list.
  
 Example of usage: Example of usage:
Line 988: Line 994:
 ==== kemi.received_route_callback ==== ==== kemi.received_route_callback ====
  
-Set the name of callback function in the KEMI script to be executed as the equivalent of `event_route[core:msg-received]` block (from the native configuration file). For execution, it also require to have the received_route_mode global parameter set to 1.+Set the name of callback function in the KEMI script to be executed as the equivalent of `event_route[core:msg-received]` block (from the native configuration file). For execution, it also requires to have the **received_route_mode** global parameter set to 1.
  
 Default value: none Default value: none
Line 997: Line 1003:
  
 <code c> <code c>
-kemi.received_route_callback="ksr_my_receieved_route"+kemi.received_route_callback="ksr_my_received_route"
 </code> </code>
  
Line 1027: Line 1033:
 ==== 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) 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.
  
 Default value is 0 (disabled). Default value is 0 (disabled).
cookbooks/5.4.x/core.1594966270.txt.gz ยท Last modified: 2020/07/17 08:11 by miconda

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki