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 [2019/12/04 14:19] henningw [listen] |
cookbooks:devel:core [2020/04/08 18:59] miconda [route_locks_size] |
||
|---|---|---|---|
| Line 1073: | Line 1073: | ||
| <code c> | <code c> | ||
| - | listen=udp: | + | listen=udp: |
| </ | </ | ||
| Line 1079: | Line 1079: | ||
| <code c> | <code c> | ||
| - | listen=udp: | + | listen=udp: |
| </ | </ | ||
| Line 1085: | Line 1085: | ||
| A typical use case for advertise address is when running SIP server behind a NAT/ | A typical use case for advertise address is when running SIP server behind a NAT/ | ||
| + | |||
| + | A unique name can be set for sockets to simplify the selection of the socket for sending out. For example, the rr and path modules can use the socket name to advertise it in header URI parameter and use it as a shortcut to select the corresponding socket for routing subsequent requests. | ||
| + | |||
| + | The name has to be provided as a string enclosed in between quotes after the **name** identifier. | ||
| + | |||
| + | <code c> | ||
| + | listen=udp: | ||
| + | listen=udp: | ||
| + | listen=udp: | ||
| + | listen=udp: | ||
| + | ... | ||
| + | $fsn = " | ||
| + | t_relay(); | ||
| + | </ | ||
| + | |||
| + | Note that there is no internal check for uniqueness of the socket names, the admin has to ensure it in order to be sure the desired socket is selected, otherwise the first socket with a matching name is used. | ||
| ==== loadmodule ==== | ==== loadmodule ==== | ||
| Line 1333: | Line 1349: | ||
| It can be set via config reload framework. | It can be set via config reload framework. | ||
| - | Default is 0 (disabled). | + | Default is 1 (enabled). |
| <code c> | <code c> | ||
| Line 1527: | Line 1543: | ||
| ==== 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 sequentially 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 messages sharing the same Call-Id. In other words, enables Kamailio to execute |
| - | For smaller impact on parallel processing, its value it should be at least twice the number of kamailio | + | For smaller impact on parallel processing, its value it should be at least twice the number of Kamailio |
| Example: | Example: | ||
| Line 1536: | Line 1552: | ||
| route_locks_size = 256 | route_locks_size = 256 | ||
| </ | </ | ||
| + | |||
| + | Note that ordering of the SIP messages can still be changed by network transmission (quite likely for UDP, especially on long distance paths) or CPU allocation for processes when executing pre-config and post-config tasks (very low chance, but not to be ruled out completely). | ||
| ==== server_id ==== | ==== server_id ==== | ||
| Line 1579: | Line 1597: | ||
| ==== sip_warning (noisy feedback) ==== | ==== sip_warning (noisy feedback) ==== | ||
| - | Can be 0 or 1. If set to 1 (default value) a ' | + | Can be 0 or 1. If set to 1 (default value is 0) a ' |
| The header contains several details that help troubleshooting using the network traffic dumps, but might reveal details of your network infrastructure and internal SIP routing. | The header contains several details that help troubleshooting using the network traffic dumps, but might reveal details of your network infrastructure and internal SIP routing. | ||
cookbooks/devel/core.txt ยท Last modified: 2022/04/11 17:10 by bkaufman
Page Tools
