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 | ||
features:new-in-devel [2019/07/06 23:45] henningw [Interpreter] |
features:new-in-devel [2019/07/16 12:53] henningw |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Kamailio SIP Server | + | ====== Kamailio SIP Server - New Features in Devel Version ====== |
**Current devel version will be numbered 5.3.0 and it is planned to be released in the autum 2019**. | **Current devel version will be numbered 5.3.0 and it is planned to be released in the autum 2019**. | ||
Line 63: | Line 63: | ||
* https:// | * https:// | ||
* https:// | * https:// | ||
+ | |||
+ | Add new parameter keep_proxy_rr to loop BYE through proxy. When in use, sending locally generated in-dialog requests will loop back to the proxy with a proper Record-Route header, including any parameters. | ||
==== dispatcher ==== | ==== dispatcher ==== | ||
Line 86: | Line 88: | ||
* https:// | * https:// | ||
- | ==== ims ==== | + | ==== imc ==== |
Extend module functionality significantly, | Extend module functionality significantly, | ||
Line 273: | Line 275: | ||
* New global parameter bind_ipv6_link_local. If set to 1, try to bind also IPv6 link local addresses by discovering the scope of the interface. This apply for UDP socket for now, to be added for the other protocols. | * New global parameter bind_ipv6_link_local. If set to 1, try to bind also IPv6 link local addresses by discovering the scope of the interface. This apply for UDP socket for now, to be added for the other protocols. | ||
* https:// | * https:// | ||
- | * Introduce new configuration parameter tcp_accept_haproxy parameter. When active, inbound TCP connections are expected to behave according to the HA PROXY protocol. Both the v1 (human-readable) and v2 (binary) versions of the protocol are supported. | + | * Introduce new configuration parameter tcp_accept_haproxy parameter. When active, inbound TCP connections are expected to behave according to the HAProxy |
* https:// | * https:// | ||
* Added latency_limit_cfg global parameter to print execution time for configuration script only if it exceeds this value. It is printed to latency_cfg_log level, another added parameter. | * Added latency_limit_cfg global parameter to print execution time for configuration script only if it exceeds this value. It is printed to latency_cfg_log level, another added parameter. | ||
Line 285: | Line 287: | ||
==== Memory Managers ==== | ==== Memory Managers ==== | ||
- | Refactoring and unification of memory allocation error logging infrastructure. Completed in the core, major modules were migrated as well. | + | Refactoring and unification of memory allocation error logging infrastructure. Completed in the core, major modules were migrated |
==== Architecture ==== | ==== Architecture ==== | ||
Line 291: | Line 293: | ||
* Extend internal IPv4 and IPv6 parsing functions in the core. | * Extend internal IPv4 and IPv6 parsing functions in the core. | ||
* Create Contacts header with path vector as Route header. When Kamailio is functioning as a registrar sends a 302 redirect, the registered contacts are sent inside the Contact header. If a contact as a path vector, that path should become a Route header in the INVITE (rfc 3327). This patch adds the path vector as a Route header parameter to the Contacts in the redirect so the receiving entity of the 302 can add the proper Route headers. This is a standard way to specify headers to be added to a request, see rfc3261 section 19.1.1. | * Create Contacts header with path vector as Route header. When Kamailio is functioning as a registrar sends a 302 redirect, the registered contacts are sent inside the Contact header. If a contact as a path vector, that path should become a Route header in the INVITE (rfc 3327). This patch adds the path vector as a Route header parameter to the Contacts in the redirect so the receiving entity of the 302 can add the proper Route headers. This is a standard way to specify headers to be added to a request, see rfc3261 section 19.1.1. | ||
+ | * Add DB_TABLE_VERSION_ERROR(table) error helper #define to DB1 API and migrate (almost) all modules that use version tables to it. This unify the logging and error behavior of the relevant modules that uses a database. | ||
==== kamailio.cfg ==== | ==== kamailio.cfg ==== | ||
+ | |||
+ | Changes to the default kamailio.cfg | ||
+ | |||
+ | * detect sipvicious as scanner | ||
+ | * do sanity check for sip responses | ||
+ | * no connect for forwarding requests withing dialog | ||
+ | * set no connect flags for replies and natted messages | ||
+ | * explicitely set the tcp/tls connections upper limits | ||
===== Tools ===== | ===== Tools ===== | ||
Line 308: | Line 319: | ||
==== kamdbctl ==== | ==== kamdbctl ==== | ||
- | Added verification before database reinit, warn that drop command will indeed drop the database. | + | * Added verification before database reinit |
+ | * Warn that drop command will indeed drop the database. | ||
| | ||
==== kamcli ==== | ==== kamcli ==== | ||