sr-dev October 2015

sr-dev@lists.kamailio.org

28 participants
236 discussions

by M S

Hi, I was asked some interesting questions yesterday by a rather techy client related to Kamailio and RTPEngine performance. Q1: For Kamailio we have say 8 child processes, which means there are 8 threads per listen address to process sip messages, i.e. for example 8 INVITE messages at any instance of time can be processed by Kamailio. If say, one INVITE takes 200ms to be processed and send out to destination, then we can estimate processing power of kamailio to be 40 INVITE requests per second per listen address, right? Q2: If so, then assuming each INVITE requires to engage RTPEngine. How can we ensure that RTPEngine would be capable to handle these 40 INVITE requests? The only relevant parameter I see in RTPEngine daemon script is "NUM_THREADS" (default value 5). What does this represent? Does this analogs to children as in Kamailio? Q3: How does RTPEngine manages SRTP <=> RTP translation (e.g. if one endpoint is WebRTC and other is traditional SIP)? My understanding is that RTPEngine has a kernel module (assuming kernel module is installed) which also manages this conversion besides forwarding the media packets. The Linux kernel already has encoders / decoders for nearly all encryption algorithms which are utilized by RTPEngine for doing the conversion in kernel space, right? if not then how it is done? Q4: Continuing to Q2, If these NUM_THREADS process actual media packets (RTP or SRTP) then are these synchronous or asynchronous? I think these are asynchronous, just want to confirm (otherwise RTPEngine won't process more then e.g. 5 calls at a time). So, assuming asynchronous how many packets can be queue to each thread? This would help estimating RTPEngine throughput using various codecs in calls. (e.g. assuming G.711 codec we have 50pps, if each thread queue size is 1000 then each thread can process 1000/50=20 concurrent calls and whole RTPEngine would process 20x5=100 concurrent calls). Thank you.

9 years, 1 month

[kamailio] nat_traversal: Builds wrong URI for IPv6, bad URI parsing (#362)

by Olle E. Johansson

nat_traversal doesn't handle IPv6 keepalives. It doesn't add [ and ] around IPv6 addresses and there's some bad parsing of SIP URI's in the code, assuming the first colon after "sip:" (not sips or tel) is a separator for port numbers. A better parser would be nice to use. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/362

9 years, 1 month

git:master:cc8ff059: nat_traversal Add comment about lacking IPv6 support

by Olle E. Johansson

Module: kamailio Branch: master Commit: cc8ff059d362e0c805de2067d73f64cbd12acdb8 URL: https://github.com/kamailio/kamailio/commit/cc8ff059d362e0c805de2067d73f64c… Author: Olle E. Johansson <oej(a)edvina.net> Committer: Olle E. Johansson <oej(a)edvina.net> Date: 2015-10-19T09:11:20+02:00 nat_traversal Add comment about lacking IPv6 support --- Modified: modules/nat_traversal/README Modified: modules/nat_traversal/doc/nat_traversal_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/cc8ff059d362e0c805de2067d73f64c… Patch: https://github.com/kamailio/kamailio/commit/cc8ff059d362e0c805de2067d73f64c…

9 years, 1 month

Kamailio v4.3.2 crash in dialog module

by M S

Hi, I am having kamailio crash in dialog module. I am using Kamailio v4.3.2 rev. 3763f6 on Debian Wheezy 32 bit. Here is back trace. -- #0 0xb59871c3 in update_dialog_vars_dbinfo (cell=0xa5be5888, var=0x1) at dlg_db_handler.c:651 #1 0xb5987e66 in update_dialog_dbinfo_unsafe (cell=0xa5be5888) at dlg_db_handler.c:724 #2 0xb59895cd in dialog_update_db (ticks=79670306, param=0x0) at dlg_db_handler.c:891 #3 0x0821aebb in compat_old_handler (ti=1274724909, tl=0xa54d3704, data=0xa54d3704) at timer.c:996 #4 0x0821b7be in slow_timer_main () at timer.c:1130 #5 0x080e2176 in main_loop () at main.c:1628 #6 0x080e7bb5 in main (argc=13, argv=0xbff13e54) at main.c:2533 -- The 'bt full' of first entry point gives this, -- #0 0xb59871c3 in update_dialog_vars_dbinfo (cell=0xa5be5888, var=0x1) at dlg_db_handler.c:651 values = {{type = DB1_INT, nul = 0, free = -1248330084, val = {int_val = 7403, ll_val = -5359754473965085461, double_val = -2.0264210675928217e-50, time_val = 7403, string_val = 0x1ceb <Address 0x1ceb out of bounds>, str_val = { s = 0x1ceb <Address 0x1ceb out of bounds>, len = -1247915084}, blob_val = {s = 0x1ceb <Address 0x1ceb out of bounds>, len = -1247915084}, bitmap_val = 7403}}, {type = DB1_INT, nul = 0, free = -1232817552, val = {int_val = 22351, ll_val = -5310283511641385137, double_val = -4.1167425495098089e-47, time_val = 22351, string_val = 0x574f <Address 0x574f out of bounds>, str_val = {s = 0x574f <Address 0x574f out of bounds>, len = -1236396728}, blob_val = { s = 0x574f <Address 0x574f out of bounds>, len = -1236396728}, bitmap_val = 22351}}, {type = DB1_STR, nul = 0, free = -1241051128, val = {int_val = -1512860372, ll_val = 37141845292, double_val = 1.8350509781927642e-313, time_val = -1512860372, string_val = 0xa5d3952c "G", str_val = {s = 0xa5d3952c "G", len = 8}, blob_val = {s = 0xa5d3952c "G", len = 8}, bitmap_val = 2782106924}}, {type = DB1_STR, nul = 0, free = -1074710904, val = {int_val = -1513070788, ll_val = 84386275132, double_val = 4.1692359523228702e-313, time_val = -1513070788, string_val = 0xa5d05f3c "L", str_val = {s = 0xa5d05f3c "L", len = 19}, blob_val = {s = 0xa5d05f3c "L", len = 19}, bitmap_val = 2781896508}}} insert_keys = {0xb59e53c4, 0xb59e53bc, 0xb59e53cc, 0xb59e53d4} __FUNCTION__ = "update_dialog_vars_dbinfo" -- Let me know if you need more info. Thank you.

9 years, 1 month

git:master:da70040e: modules/ims_qos: new mod param terminate_dialog_on_rx_failure

by Richard Good

Module: kamailio Branch: master Commit: da70040e8f782e90ab8378f54f210e8752b085bc URL: https://github.com/kamailio/kamailio/commit/da70040e8f782e90ab8378f54f210e8… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: 2015-10-15T18:10:22+02:00 modules/ims_qos: new mod param terminate_dialog_on_rx_failure terminate_dialog_on_rx_failure this parameter determines if a dialog is torn down if a media Rx session is terminated --- Modified: modules/ims_qos/cdpeventprocessor.c Modified: modules/ims_qos/mod.c --- Diff: https://github.com/kamailio/kamailio/commit/da70040e8f782e90ab8378f54f210e8… Patch: https://github.com/kamailio/kamailio/commit/da70040e8f782e90ab8378f54f210e8… --- diff --git a/modules/ims_qos/cdpeventprocessor.c b/modules/ims_qos/cdpeventprocessor.c index 360cff1..94f03f9 100644 --- a/modules/ims_qos/cdpeventprocessor.c +++ b/modules/ims_qos/cdpeventprocessor.c @@ -63,6 +63,8 @@ extern int cdp_event_list_size_threshold; extern struct ims_qos_counters_h ims_qos_cnts_h; +extern int terminate_dialog_on_rx_failure; + int init_cdp_cb_event_list() { cdp_event_list = shm_malloc(sizeof (cdp_cb_event_list_t)); if (!cdp_event_list) { @@ -226,7 +228,10 @@ void cdp_cb_event_process() { LM_DBG("This is a media bearer session session"); //this is a media bearer session that was terminated from the transport plane - we need to terminate the associated dialog //so we set p_session_data->must_terminate_dialog to 1 and when we receive AUTH_EV_SERVICE_TERMINATED event we will terminate the dialog - p_session_data->must_terminate_dialog = 1; + //we only terminate the dialog if terminate_dialog_on_rx_failure is set + if(terminate_dialog_on_rx_failure) { + p_session_data->must_terminate_dialog = 1; + } } break; diff --git a/modules/ims_qos/mod.c b/modules/ims_qos/mod.c index 56be1d8..fc9be1a 100644 --- a/modules/ims_qos/mod.c +++ b/modules/ims_qos/mod.c @@ -121,6 +121,8 @@ static int fixup_aar(void** param, int param_no); int * callback_singleton; /*< Callback singleton */ +int terminate_dialog_on_rx_failure = 1; //this specifies whether a dialog is torn down when a media rx session fails - in some cases you might not want the dialog torn down + str early_qosrelease_reason = {"QoS released", 12}; str confirmed_qosrelease_headers = {NULL, 0}; @@ -152,6 +154,7 @@ static param_export_t params[] = { { "video_default_bandwidth", INT_PARAM, &video_default_bandwidth}, { "early_qosrelease_reason", PARAM_STR, &early_qosrelease_reason}, { "confirmed_qosrelease_headers", PARAM_STR, &confirmed_qosrelease_headers}, + { "terminate_dialog_on_rx_failure", INT_PARAM, &terminate_dialog_on_rx_failure}, { 0, 0, 0} };

9 years, 1 month

setflag and hash table variables

by Asgaroth

Hi All, Quick question, is it possible to use variables in the setflag function, I am trying to set a flag that is stored in a hash table using the setflag function, but I keep getting syntax errors. I am using kamailio 4.3.3. Here's what I am trying to do: htable core_setid defines a dispatcher setid key and its value is associated with a flag as follows: id:key:key_type:value_type:value:expires 1:102:0:1:7:0 so, simple hash table type with an integer key of value 7 and no expiry In dispatcher I have the following modparams set, so that ds_is_from_list() will set them if found: modparam("dispatcher", "setid_pvname", "$var(ds_setid)") modparam("dispatcher", "attrs_pvname", "$var(ds_setid_attrs)") Then in my routing logic I have the following code block: if ( ds_is_from_list() ) { if ( $sht(core_setid=>$var(ds_setid)) != $null ) { setflag( $sht(core_setid=>$var(ds_setid)) ); return; } else { send_reply("403", "No flag set for source"); exit; } } When I test this using kamailio -c -f <filename> I get the following error: 0(20629) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 21-52: syntax error 0(20629) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 21-52: missing '(' or ')'? 0(20629) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 21-52: bad command: missing ';'? 0(20629) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 53: bad command ERROR: bad config file (4 errors) If I change the setflag line to setflag(7), then I dont get the error. I was wondering if its possible to have hashtable variables as parameters to the setflag function, or am I going about this in the wron way. Any thoughts would be appreciated. Thanks

9 years, 1 month

[kamailio] Use the Additional section of SRV queries instead of doing extra requests (#366)

by Tristan F.

It seems like kamailio when using SRV records does not read and use the ADDITIONAL SECTION, and instead sends another DNS request to get the IP for the host, which is inefficient and could be supported just like mentioned in the [RFC 2782](https://www.ietf.org/rfc/rfc2782.txt) : For each element in the new list query the DNS for address records for the Target or use any such records found in the Additional Data section of the earlier SRV response. Example, for our `_sip._udp` service using our service discovery tool : ;; ANSWER SECTION: _sip._udp.service.consul. 15 IN SRV 1 1 5063 ourserver.node.us.consul. _sip._udp.service.consul. 15 IN SRV 1 1 5060 ourserver.node.us.consul. _sip._udp.service.consul. 15 IN SRV 1 1 5062 ourserver.node.us.consul. _sip._udp.service.consul. 15 IN SRV 1 1 5061 ourserver.node.us.consul. ;; ADDITIONAL SECTION: ourserver.node.us.consul. 15 IN A 98.XXX.XXX.XXX It has all the information it needs but it still does an extra request. Any thoughts? --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/366

9 years, 1 month

[kamailio] Module cnxcc: Error in log while parsing fake message (#324)

by Rick

``` 10(21119) DEBUG: dialog [dlg_req_within.c:384]: send_bye(): BYE sent to callee 10(21119) DEBUG: dialog [dlg_hash.c:832]: dlg_unref(): unref dlg 0x808f57580 with 1 -> 2 10(21119) DEBUG: cnxcc [cnxcc_mod.c:1005]: terminate_call(): dlg_end_dlg sent to call [] 10(21119) DEBUG: cnxcc [cnxcc_sip_msg_faker.c:45]: faked_msg_init_with_dlg_info(): fake msg: OPTIONS sip:you@kamailio.org SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1 From: <>;tag= To: <>;tag= Call-ID: CSeq: 1 OPTIONS Content-Length: 0 10(21119) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 10(21119) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <OPTIONS> 10(21119) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: <sip:you@kamailio.org> 10(21119) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 10(21119) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=2 10(21119) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 10(21119) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 10(21119) exec: *** cfgtrace:request_route=[CNXCC] c=[/usr/local/etc/kamailio/kamailio.cfg] l=777 a=26 n=xlog 10(21119) ERROR: <core> [parser/parse_addr_spec.c:764]: parse_addr_spec(): ERROR: parse_to : unexpected char [>] in status 5: <<<>> . 10(21119) ERROR: <core> [parser/msg_parser.c:165]: get_hdr_field(): ERROR: get_hdr_field: bad to header 10(21119) DEBUG: <core> [parser/msg_parser.c:280]: get_hdr_field(): get_hdr_field: error exit 10(21119) INFO: <core> [parser/msg_parser.c:338]: parse_headers(): ERROR: bad header field [To: <>;tag= Call-ID] 10(21119) ERROR: pv [pv_core.c:635]: pv_get_callid(): cannot parse Call-Id header 10(21119) INFO: <script>: [<null>]: call killed ``` it seems that the fake message values are not filled, does I miss load an special module or is it an error because of old source code. Using version 4.31. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/324

9 years, 1 month

4.3 branch gcc warnings

by Victor Seva

Hi, building the 4.3 branch I'm having a lot of: "declared but never defined" for parse_param. For instance: gcc -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -Wall -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DVERSIO N_NODATE -DNAME='"kamailio"' -DVERSION='"4.3.3"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 5.2.1"' -D__CPU_x86_64 -D__OS_linux -DSER_VER=4003003 -DCFG_DIR='"/etc/kamailio/"' -DRUN_ DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DDBG_QM_MALLOC -DMEM_JOIN_FREE -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DUSE_RAW_SOCKS -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c parser/contact/parse_contact.c -o parser/contact/parse_contact.o -MMD -MP In file included from parser/contact/contact.h:38:0, from parser/contact/parse_contact.h:40, from parser/contact/parse_contact.c:37: parser/contact/../parse_param.h:146:19: warning: inline function 'parse_param' declared but never defined extern inline int parse_param(str *_s, pclass_t _c, param_hooks_t *_h, param_t *t);

9 years, 1 month

Something wrong with HTML page generation

by Olle E. Johansson

I get an error on this page http://kamailio.org/docs/modules/modules/tm.html /O

9 years, 1 month

← Newer
1
...
9
10
11
12
13
14
15
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2015