sr-dev February 2018

sr-dev@lists.kamailio.org

33 participants
355 discussions

[kamailio] error while dumping dialog via RPC (#145)

by Savolainen Dmitri

In part of profiles and/or variables section while using `static inline void internal_rpc_print_dlg(rpc_t *rpc, void *c, dlg_cell_t *dlg, int with_context) ` May be it is an error of ctl module ``` # kamcmd dlg.list { h_entry: 6718 h_id: 20440 call-id: 48c9fe85f6750163(a)192.168.5.60 from_uri: sip:000*051@xxxxxx.xx:5068 to_uri: sip:002@xxxxxx.xx:5068 state: 4 start_ts: 1430324850 init_ts: 1430324847 timeout: 1430368049 lifetime: 43200 dflags: 515 sflags: 0 iflags: 0 caller: { tag: bda5e24faa4c4ff5 contact: sip:000*051@192.168.5.60:5066;transport=udp;alias=xxx.xxx.78.202~5066~1 cseq: 5457 route_set: socket: udp:xxx.xxx.66.150:5068 } callee: { tag: 4y2gjr7N9231K contact: sip:002@xxx.xxx.66.151:5080;transport=udp cseq: 0 route_set: socket: udp:xxx.xxx.66.150:5068 } profiles: { ERROR while parsing the record 62, @698: 03 : bad record ``` --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/145

6 years

[kamailio/kamailio] Feature Request: possibility to reload dialogs from db without restarting kamailio (#1274)

by alexsosic

Hi, we're trying to have scalable Kamailio nodes that are stateless. That means that we can for example load dispatchers and reload them from an API endpoint. Now we're stuck on the dialog part. All our nodes load the dialogs from a shared db, what happens when a node gets down is that a packet reaches another node and does not know how to handle that because the dialog does not have it's ip address. Also there is no possibility to reload the dialogs from db so that we could update the records in the db and have the dialogs ip changed on an anctive node's ip. Is there a possibility to have a function to reload the dialogs from db on a running kamailio? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1274

6 years

[kamailio/kamailio] define flag_t as unsigned long (#1288)

by juha-h

Currently core/flags.h defines typedef unsigned int flag_t; It would better to use unsigned long in order to allow more that 32 flags on 64 bit architectures. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1288

6 years

[kamailio/kamailio] IPOPS is_in_subnet function doesn't match host address in cidr notation (#1250)

by kbdfck

### Description is_in_subnet function requires subnet param to be network address and fails for host address in cidr notation despite it is contained in corresponding subnet. For example, is_in_subnet("1.2.3.2", "1.2.3.0/30") returns true but is_in_subnet("1.2.3.2", "1.2.3.2/30") returns false, although 1.2.3.2 is present in 1.2.3.2/30 and 1.2.3.2 is allowed IP of 1.2.3.0/30 Of course, "1.2.3.2/30" this is not actually a subnet specification and rather is IP in CIDR notation, but sometimes it is required to check if some IP matches specified IP with CIDR. ### Possible Solutions It would be cool if is_in_subnet take such cases as matches. I think this should not break anything, because host IP and CIDR always define network containing specified host. Another solution would be separate function with more relaxed behavior... This happens on Kamailio 5.1 devel. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1250

6 years, 1 month

[kamailio/kamailio] Kamailio + rsyslog, still writing logs to /var/log/syslog in DEBUG_MODE (#1070)

by Fyodor

Ubuntu 16.04.2 LTS version: kamailio 4.3.4 (x86_64/linux) /etc/kamailio/kamailio.cfg: ``` ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 ``` /etc/rsyslog.d/50-default.conf ``` local0.* -/var/log/kamailio.log ``` kamailio.log file ``` -rw-r--r-- 1 syslog adm 1788189 Apr 14 12:09 /var/log/kamailio.log ``` If i disable WITH_DEBUG in kamailio config - it writes log to /var/log/kamailio.log, if i enable it - kamailio write logs to /var/log/syslog. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1070

6 years, 1 month

[kamailio/kamailio] db_cassandra can't find table version (#618)

by goharahmed

Hi devs, I'm trying to make the db_cassandra work for my kamailio specifically userblacklist module. I've cassanda keyspace and tables defined along with the db_schema directory structure defined as instructed however the debug logs keep telling me that table 'version' doesn't exist. I've taken a look inside the dbcassa_table.c file https://github.com/kamailio/kamailio/blob/master/modules/db_cassandra/dbcas… Somewhere in this function it just doesn't get hold of "tbc" and hence it throws up error. Here is how I've figured out this code. hash = core_hash(dbn, tbn, DBCASSA_TABLE_SIZE); **if(!hash) LM_ERR("hash NOT FOUND\n");** hashidx = hash % DBCASSA_TABLE_SIZE; **if(!hashidx) LM_ERR("hashidx NOT FOUND\n");** ref_read_data(dbcassa_tbl_htable[hashidx].lock); tbc = dbcassa_tbl_htable[hashidx].dtp; **if(!tbc) LM_ERR("TBC NOT FOUND\n");** while(tbc) { LM_DBG("found dbname=%.*s, table=%.*s\n", tbc->dbname.len, tbc->dbname.s, tbc->name.len, tbc->name.s); if(tbc->hash==hash && tbc->dbname.len == dbn->len && tbc->name.len == tbn->len && !strncasecmp(tbc->dbname.s, dbn->s, dbn->len) && !strncasecmp(tbc->name.s, tbn->s, tbn->len)) { memcpy(full_path_buf + dbcassa_schema_path.len, dbn->s, dbn->len); len = dbcassa_schema_path.len + dbn->len; full_path_buf[len++] = '/'; memcpy(full_path_buf + len, tbn->s, tbn->len); full_path_buf[len + tbn->len] = '\0'; if(dbcassa_check_mtime(&tbc->mt) == 0) return tbc; old_tbc = tbc; break; } tbc = tbc->next; } unref_read_data(dbcassa_tbl_htable[hashidx].lock); **if(!old_tbc) { LM_ERR("OLD_TBC NOT FOUND\n");** return NULL; } and upon starting of kamailio after recompiling the module I see these lines printed. 0(15574) DEBUG: db_cassandra [dbcassa_base.cpp:149]: db_cassa_new_connection(): opening connection: cassa://xxxx:xxxx@127.0.0.1:9160/kamailio 0(15574) DEBUG: <core> [mem/f_malloc.c:439]: fm_malloc(): fm_malloc(0x7f9c14f8a010, 48) called from db_cassandra: dbcassa_base.cpp: db_cassa_new_connection(155) 0(15574) DEBUG: <core> [mem/f_malloc.c:514]: fm_malloc(): fm_malloc(0x7f9c14f8a010, 48) returns address 0x7f9c150055f0 0(15574) DEBUG: db_cassandra [dbcassa_base.cpp:161]: db_cassa_new_connection(): 0x7f9c150055f0=pkg_malloc(48) 0(15574) DEBUG: db_cassandra [dbcassa_base.cpp:117]: dbcassa_open(): Opened connection to Cassandra cluster 127.0.0.1:9160 0(15574) DEBUG: db_cassandra [dbcassa_base.cpp:955]: db_cassa_query(): query table=version **0(15574) ERROR: db_cassandra [dbcassa_table.c:463]: dbcassa_db_get_table(): TBC NOT FOUND 0(15574) ERROR: db_cassandra [dbcassa_table.c:486]: dbcassa_db_get_table(): OLD_TBC NOT FOUND** 0(15574) ERROR: db_cassandra [dbcassa_base.cpp:449]: cassa_translate_query(): table version does not exist! 0(15574) ERROR: db_cassandra [dbcassa_base.cpp:962]: db_cassa_query(): Failed to query Cassandra cluster 0(15574) ERROR: <core> [db.c:397]: db_table_version(): error in db_query 0(15574) ERROR: <core> [db.c:436]: db_check_table_version(): querying version for table userblacklist 0(15574) ERROR: userblacklist [db_userblacklist.c:86]: userblacklist_db_init(): during table version check. 0(15574) DEBUG: <core> [db_pool.c:100]: pool_remove(): removing connection from the pool 0(15574) DEBUG: <core> [mem/f_malloc.c:575]: fm_free(): fm_free(0x7f9c14f8a010, 0x7f9c150055f0), called from db_cassandra: dbcassa_base.cpp: db_cassa_free_connection(203) 0(15574) DEBUG: <core> [mem/f_malloc.c:594]: fm_free(): fm_free: freeing block alloc'ed from db_cassandra: dbcassa_base.cpp: db_cassa_new_connection(155) 0(15574) DEBUG: <core> [mem/f_malloc.c:575]: fm_free(): fm_free(0x7f9c14f8a010, 0x7f9c15005318), called from core: db.c: db_do_close(356) 0(15574) DEBUG: <core> [mem/f_malloc.c:594]: fm_free(): fm_free: freeing block alloc'ed from core: db.c: db_do_init2(298) 0(15574) ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module userblacklist (/usr/local/lib64/kamailio/modules/userblacklist.so) ERROR: error while initializing modules Kindly look into this and let me know how to make this work. Thanks, Sammy --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/618

6 years, 2 months

git:master:52a8def8: utils: kamdbctl - updated help message for migrate command

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 52a8def8d2a3e83170ab554a85b26d977d99f51a URL: https://github.com/kamailio/kamailio/commit/52a8def8d2a3e83170ab554a85b26d9… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2018-02-14T11:24:37+01:00 utils: kamdbctl - updated help message for migrate command --- Modified: utils/kamctl/kamdbctl.base --- Diff: https://github.com/kamailio/kamailio/commit/52a8def8d2a3e83170ab554a85b26d9… Patch: https://github.com/kamailio/kamailio/commit/52a8def8d2a3e83170ab554a85b26d9… --- diff --git a/utils/kamctl/kamdbctl.base b/utils/kamctl/kamdbctl.base index 2abde29d26..13af37e7c6 100644 --- a/utils/kamctl/kamdbctl.base +++ b/utils/kamctl/kamdbctl.base @@ -97,7 +97,7 @@ usage: $COMMAND create <db name or db_path, optional> ...(creates a new database $COMMAND backup <file> ...........................(dumps current database to file) $COMMAND restore <file> ..........................(restores tables from a file) $COMMAND copy <new_db> ...........................(creates a new db from an existing one) - $COMMAND migrate <old_db> <new_db> ...............(migrates DB from 1.2 to 1.3, not implemented yet!) + $COMMAND migrate <old_db> <new_db> ...............(migrates DB - no longer maintained!) $COMMAND presence ................................(adds the presence related tables) $COMMAND extra ...................................(adds the extra tables) $COMMAND dbuid ...................................(adds the uid tables)

6 years, 2 months

[kamailio/kamailio] rtpengine: added support for DTLS transports (#1460)

by jerzyptak

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #1458 #### Description  Added ability to explicitly request usage of DTLS transports UDP/TLS/RTP/SAVP and UDP/TLS/RTP/SAVPF via rtpengine API. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1460 -- Commit Summary -- * rtpengine: added support for DTLS transports -- File Changes -- M src/modules/rtpengine/doc/rtpengine_admin.xml (6) M src/modules/rtpengine/rtpengine.c (23) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1460.patch https://github.com/kamailio/kamailio/pull/1460.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1460

6 years, 2 months

[kamailio/kamailio] Problem with topos together with track_cseq_updates (#1038)

by lamSteven

### Description When using the dialog track_cseq_updates feature (to increase the cseq for calls that are authenticated using the uac uac_auth) together with topos, it seems like a reply is not handled by topos. #### Log Messages I have a 2219 line debug log demonstrating this, i can supply this on request. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1038

6 years, 2 months

Planing next Kamailio releases - v4.4.7 v5.0.6 and v5.1.2

by Daniel-Constantin Mierla

Hello, I am considering to do releases from last three stable branches during next week. v4.4.7 is going to be released out of latest code in branch 4.4 to mark the end of official maintenance for series v4.4.x. The version 4.4.0 was released in March 2016, so it had more or less two years of maintenance. Commits can still go in 4.4 branch if developers wants to push there, end of official maintenance means that there is no plan to do packaging and release another version from the branch in the future, so you will have to build it from sources or generate packages yourself. v5.0.6 and v5.1.2 are the usual minor releases we do from the last two stable branches. If there are any issues you are aware of and not reported on bug tracker, create the items as soon as possible to get a better chance to review and eventually fix. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

6 years, 2 months

← Newer
1
...
4
5
6
7
8
9
10
...
36
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev February 2018