- sr-users - kamailio.org

tcpconn_main_timeout
by Kjeld Flarup 23 Mar '18

23 Mar '18

We are developing an app with a pjsip client. I see this error when trying to send an invite from kamailio. Mar 17 00:29:46 raspberrypi /usr/sbin/kamailio[18720]: ERROR: <core> [tcp_main.c:4258]: tcpconn_main_timeout(): connect 62.44.134.85:43829 failed (timeout) A few seconds before 62.44.134.85:43829 did a register. I can understand that either the TCP connection was close by the other end or no one is listening. How much can I see in a pcap from this scenario? I cannot see the invite, but somehow there must be some TCP communication to show what is failing. -- -------------------- Med Liberalistiske Hilsner ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

3 10

htable not visible in another thread
by Kjeld Flarup 22 Mar '18

22 Mar '18

Im trying to do a t_suspend, but cant get htable to work I save to $sht $sht(vtp=>join::$rU) = "" + $T(id_index) + ":" + $T(id_label); xlog( "L_ALERT", "Suspended transaction sht(vtp=>join::$rU) = [$sht(vtp=>join::$rU)]\n" ); Mar 19 23:36:28 raspberrypi /usr/sbin/kamailio[2167]: ALERT: <script>: Suspended transaction sht(vtp=>join::004540294149) = [23690:1238111367] But in my register thread nothing is read xlog("L_ALERT","sht(vtp=>join::$tU) = $sht(vtp=>join::$tU)\n"); Mar 19 23:36:31 raspberrypi /usr/sbin/kamailio[2114]: ALERT: <script>: sht(vtp=>join::004540294149) = <null> # -------- htable params -------------- modparam("htable", "db_url", DBURL) modparam("htable", "htable", "vtp=>size=10;autoexpire=120;dbtable=htable;dbmode=1") modparam("htable", "htable", "a=>size=6;") I never see any data in htable in the database. What am I doing wrong? -- -------------------- Med Liberalistiske Hilsner ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

3 3

phonenum module erratic behaviour with 5.1.2
by George Diamantopoulos 22 Mar '18

22 Mar '18

Hello all, It seems that the phonenum module in at least 5.1.2 (haven't tried previous versions) is behaving somewhat erratically. More specifically, if there are any references to any phn PVs with the key other than "number": if ( phonenum_match("1-484-555-8888", "src") ) { xlog("number norm: $phn(src=>number)\n"); xlog("number country: $phn(src=>country)\n"); dbg_pv_dump(30, "L_ERR"); } kamailio will not start: Mar 19 20:06:49 modcom-sbc-dev1 kamailio[5042]: 0(5044) DEBUG: <core> [core/pvapi.c:494]: pv_spec_lookup(): PV <$phn(src=>country)> is not in cache Mar 19 20:06:49 modcom-sbc-dev1 kamailio[5042]: 0(5044) DEBUG: phonenum [phonenum_pv.c:160]: pv_parse_phonenum_name(): phonenum [src] - key [country] Mar 19 20:06:49 modcom-sbc-dev1 kamailio[5042]: 0(5044) ERROR: phonenum [phonenum_pv.c:205]: pv_parse_phonenum_name(): error at PV phonenum name: src=>country Mar 19 20:06:49 modcom-sbc-dev1 kamailio[5042]: 0(5044) ERROR: <core> [core/pvapi.c:951]: pv_parse_spec2(): pvar "phn" has an invalid name param [src=>country] Mar 19 20:06:49 modcom-sbc-dev1 kamailio[5042]: 0(5044) ERROR: <core> [core/pvapi.c:1106]: pv_parse_spec2(): wrong char [)/41] in [$phn(src=>country)] at [17 (5)] Mar 19 20:06:49 modcom-sbc-dev1 kamailio[5042]: 0(5044) ERROR: xlog [xlog.c:513]: xdbg_fixup_helper(): wrong format[number country: $phn(src=>country) If I comment the offending line, all is well, but when dumping PVs with dbg_pv_dump(30, "L_ERR");, only $phn(src=>number) is listed, not the other keys (country, operator, region according to the docs) However, what is more disturbing is that phn(src=>number) always contains the string provided to phonenum_match() function, even if invalid characters are included, with no normalization. For example: phonenum_match("14~8%^88", "src") will result in dbg_pv_dump reporting: "$phn(src=>number)": "14~8%^88" Please note that I'm using sipwise's debian repository for stretch for kamailio, and debian's stable stretch repository for libphonenumnber (currently at 7.1.0-5+b1). I have also tried building current libphonenumber myself (version v8.9.2), but the result is the same. Is this a bug? Or am I missing something? Thanks! BR, George

3 4

Kamailio htable.dump command returns - reply too big
by José Seabra 22 Mar '18

22 Mar '18

Hello there, I have an htable with 3000 entries and when i try dump the htable through the command kamcmd htable.dump htable, this command returns "ERROR: reply too big". I have tried to increase the body size using the following modparam: modparam("ctl", "binrpc_max_body_size",1024) But the result still the same "ERROR: reply too big", do I need to configure another parameter to be able dump this htable? The kamailio version that i'm using is 4.4.2 Thank you. Regards José Seabra

2 3

Kamailio behind NAT no Audio
by Benjamin Marty 22 Mar '18

22 Mar '18

Hi, I am new to Kamailio and coming a bit from the Asterisk side. Currently I'm using the Amazon EC2 Infrastructure and set up an Kamailio with standard configuration. EC2 uses Destination NAT on their side. Thus I enabled WITH_NAT and WITH_NATSIPPING. I'm using the rtpproxy from master branch of https://github.com/miconda/rtpproxy. Besides those two parameters I also changed the listen parameter in the Kamailio config: listen=udp:10.0.0.221:5060 advertise 52.59.XXX.XXX:5060 My rtpproxy is running with following parameters: ./rtpproxy -A 52.59.XXX.XXX -F -l 10.0.0.221 -m 20000 -M 30000 -s udp:*:7722 -d INFO When I use two Softclients (Zoiper) on different Networks (with Source NAT on the Firewall) the Softclient tries to transmit the RTP Packets to the Public IP of the other Network. But the Client obviously thus doesn't get the RTP Packets. Is there an easy and documented way to solve that issue? If I understood it correctly Kamailio together with rtpproxy should be able to receive the RTP Packets and forward them to the other client. So it should signal the IP of the Kamailio to send the RTP packets to. Or am I on the complete wrong way? Regards, Benjamin

1 0

avpops and mongo problem
by hdssdsdsdsfsdf hdssdsdsdsfsdf 22 Mar '18

22 Mar '18

Hi all, I have kamailio setup that uses a mongo cluster, and everything works fine. Only I have problems with the avpops module. The avp_db_load fails with "field [attribute] not found in result iterator", even if the attribute field is present in the object in mongo. Does anybody know what could be going wrong? Thanks in advance, and kind regards, =============================================================================== kamailio.cfg: ... # ---- avpops params ---- modparam("avpops", "db_url", DBURL) modparam("avpops", "avp_table", "usr_preferences") ... xlog("trying avp_db_load\n"); if (avp_db_load("$fu/username", "$avp(s:attributevalue)")) { xlog("if succeeded\n"); } xlog("if not succeeded\n"); ... =============================================================================== mongo: rs:SECONDARY> db.usr_preferences.find({"username":"1234567890"}) { "_id" : ObjectId("5ab22a5b384cd2aa0d4cf403"), "attribute" : "attributevalue", "username" : "1234567890", "domain" : null, "value" : "750", "uuid" : "", "type" : 0 } =============================================================================== syslog: ... Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: <script>: trying avp_db_load Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:851]: db_mongodb_query(): query to collection [usr_preferences] Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:885]: db_mongodb_query(): query filter: { "username" : "1234567890", "attribute" : "attributevalue" } Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:904]: db_mongodb_query(): columns filter: { "value" : 1, "attribute" : 1, "type" : 1 } Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 56 bytes for result set at 0x7f43b613c480 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:349]: db_mongodb_get_columns(): 3 columns returned from the query Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:154]: db_allocate_columns(): allocate 24 bytes for result names at 0x7f43b613c318 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:165]: db_allocate_columns(): allocate 12 bytes for result types at 0x7f43b614d888 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:377]: db_mongodb_get_columns(): Found a field[0] named: value Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:396]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7f43b614d9b8 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:431]: db_mongodb_get_columns(): use DB1_STRING result type Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:460]: db_mongodb_get_columns(): RES_NAMES(0x7f43b614d9b8)[0]=[value] (2) Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:377]: db_mongodb_get_columns(): Found a field[1] named: attribute Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [attribute] not found in result iterator Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 3 columns Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7f43b614d9b8 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:92]: db_free_columns(): freeing result names at 0x7f43b613c318 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:97]: db_free_columns(): freeing result types at 0x7f43b614d888 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0x7f43b613c480 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: avpops [avpops_impl.c:381]: ops_dbload_avps(): db_load failed Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: <script>: if not succeeded ... ===============================================================================

3 3

drouting & rd
by Jean Cérien 22 Mar '18

22 Mar '18

Hello I have setup 2 gateways in my dr_rules: 5,6 - so the 2nd one is tried if the first fails. The second one requires credentials. When the first one fails: I execute the following code: failure_route[ROUTEFAIL] { if ( t_check_status("[345][0-9][0-9]") or (t_branch_timeout() and !t_branch_replied() )) { t_on_failure("ROUTEFAIL"); if (use_next_gw()) { xlog("L_INFO","failure_route(ROUTEFAIL) @@ routing to: rd: $rd, ru:$ru, t_relay"); t_relay(); exit; } then in the same ROUTEFAIL (before this code), I have if (t_check_status("401|407")) { xlog("L_INFO","failure_route(ROUTEFAIL) @@ call to uac_auth(), $si rd: $rd\n"); ..... So, when the first gateway replies with a 404, it executes correctly the first block, finds the second gw and I see in the log that rd is set to its address. Yet, when the 2nd gw replies with 401, rd is set to the very first gw. However, the pcap traces confirm it is indeed the second that replies this. If this behaviour is correct, I cant seem to find the source IP of the gateway that replied to me, to retrieve credentials from the db. version: kamailio 5.0.5 / 5.0.6 (tested on both) Thank you for your help J

2 1

XMLRPC with params
by David Villasmil 22 Mar '18

22 Mar '18

Hello guys, I'm trying to call an xmlrpc method with parameters like: <?xml version="1.0"?> <methodCall> <methodName>dispatcher.set_state</methodName> <params> <param> <value><string>state:i</string></value> </param> <param> <value><string>group:1</string></value> </param> <param> <value><string>sip:1.2.3.4:5060</string></value> </param> </params> </methodCall> I'm getting back "Invalid Parameters". I can't find any documentation as to _how_ to call it with parameters. Can anyone help? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 2

(no subject)
by hdssdsdsdsfsdf hdssdsdsdsfsdf 21 Mar '18

21 Mar '18

Hi all, I have kamailio setup that uses a mongo cluster, and everything works fine. Only I have problems with the avpops module. The avp_db_load fails with "field [attribute] not found in result iterator", even if the attribute field is present in the object in mongo. Does anybody know what could be going wrong? Thanks in advance, and kind regards, =============================================================================== kamailio.cfg: ... # ---- avpops params ---- modparam("avpops", "db_url", DBURL) modparam("avpops", "avp_table", "usr_preferences") ... xlog("trying avp_db_load\n"); if (avp_db_load("$fu/username", "$avp(s:attributevalue)")) { xlog("if succeeded\n"); } xlog("if not succeeded\n"); ... =============================================================================== mongo: rs:SECONDARY> db.usr_preferences.find({"username":"1234567890"}) { "_id" : ObjectId("5ab22a5b384cd2aa0d4cf403"), "attribute" : "attributevalue", "username" : "1234567890", "domain" : null, "value" : "750", "uuid" : "", "type" : 0 } =============================================================================== syslog: ... Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: <script>: trying avp_db_load Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:851]: db_mongodb_query(): query to collection [usr_preferences] Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:885]: db_mongodb_query(): query filter: { "username" : "1234567890", "attribute" : "attributevalue" } Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:904]: db_mongodb_query(): columns filter: { "value" : 1, "attribute" : 1, "type" : 1 } Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 56 bytes for result set at 0x7f43b613c480 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:349]: db_mongodb_get_columns(): 3 columns returned from the query Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:154]: db_allocate_columns(): allocate 24 bytes for result names at 0x7f43b613c318 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:165]: db_allocate_columns(): allocate 12 bytes for result types at 0x7f43b614d888 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:377]: db_mongodb_get_columns(): Found a field[0] named: value Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:396]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7f43b614d9b8 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:431]: db_mongodb_get_columns(): use DB1_STRING result type Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:460]: db_mongodb_get_columns(): RES_NAMES(0x7f43b614d9b8)[0]=[value] (2) Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: db_mongodb [mongodb_dbase.c:377]: db_mongodb_get_columns(): Found a field[1] named: attribute Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [attribute] not found in result iterator Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 3 columns Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7f43b614d9b8 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:92]: db_free_columns(): freeing result names at 0x7f43b613c318 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:97]: db_free_columns(): freeing result types at 0x7f43b614d888 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0x7f43b613c480 Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: avpops [avpops_impl.c:381]: ops_dbload_avps(): db_load failed Mar 21 17:15:16 ccccc /opt/kamailio/sbin/kamailio[2544]: ERROR: <script>: if not succeeded ... ===============================================================================

1 0

Problems with dispatcher reload
by Arik Halperin 21 Mar '18

21 Mar '18

Hello, I’ve installed kamailio 5.1 but when I run: kamctl dispatcher reload I get: { "jsonrpc": "2.0", "error": { "code": 500, "message": "Method Not Found" }, "id": 31222 } How do I fix this? Thanks, Arik Halperin

4 6

How does Kamailio decide which msg to store when receiving it double from 2 servers?
by Zigelman, Amit 21 Mar '18

21 Mar '18

I am using Captagent on 2 sip servers communicating with each other. Both Captagents then route the SIP traffic to the same Kamailio. Therefore, if I understand, Kamailio will get every msg between them twice. Once from server A and once from server B. Let's say that each of them has a different capturing code (100 for server A and 200 for server B) How will the data look in the DB? Will it hold both entries pretty much the same with a difference is some fields such as the capture node? Thanks a lot, Amit -- *Amit Zigelman* | *Software Developer* Mobile (+972) 54-570-9129 <+972%254-570-9129> | amit.zigelman(a)vonage.com

2 1

authenticating to mongodb fails
by hdssdsdsdsfsdf hdssdsdsdsfsdf 21 Mar '18

21 Mar '18

When I connect using mongo, the credentials work: $ mongo kamailio -u "kam" -p "kam" MongoDB shell version v3.4.9 connecting to: mongodb://127.0.0.1:27017/kamailio MongoDB server version: 3.4.9 > db.subscriber.find() { "_id" : ObjectI ... But when I use the following DBURL in kamailio.cfg, kamailio fails to even login to mongo: #!define DBURL "mongodb://kam:kam@localhost/kamailio" If I disable mongodb authentication, kamailio starts up just fine again. Any idea what's going wrong here?

3 10

NATDETECT Flag 16
by Duarte Rocha 21 Mar '18

21 Mar '18

Greetings, I have a doubt about the flag 16 used in nat_uac_test() belonging to the module NATDETECT. In the documentation, the following is stated : *16* - Test if the source port is different from the port in the “Via” header I have some situations that I receive a request from port 5060 and the Via Header contains no port. I think it probably assumes that it is the default port. Will this situation trigger the "16" flag ? Thanks in advance, Cheers

2 2

S-CSCF can not allocate memory
by tyd 21 Mar '18

21 Mar '18

Hello, I haved install debian 8 and kamailio 4.4.7 for IMS testing. After registering 10000 users, SIPp generates CPS 25 SIP INVITE message and BYE message after 100 seconds. After about 240000 calls, there are "cannot allocate memory" messgae on S-CSCF. The command of S-CSCF is "kamailio -m 512 -f /etc/scscf/kamailio.cfg" The parameter mem_join=1 is included in kamailio.cfg. I have modified the share memory to 1024 and 2048, but the result is the same, just increasing the pass calls. Would you please tell me how to solve the memory problem? Thanks. Mar 21 12:25:03 Kamailio440 kamailio[16483]: ERROR: <core> [sip_msg_clone.c:981]: msg_lump_cloner(): cannot allocate memory Mar 21 12:25:03 Kamailio440 kamailio[16483]: ERROR: tm [t_fwd.c:1656]: t_forward_nonack(): ERROR: t_forward_nonack: failed to save the message lumps Mar 21 12:25:03 Kamailio440 kamailio[16483]: ERROR: tm [t_reply.c:545]: _reply_light(): ERROR: _reply_light: cannot allocate shmem buffer Mar 21 12:25:03 Kamailio440 kamailio[16483]: ERROR: tm [t_lookup.c:1489]: t_unref(): ERROR: t_unref: generation of a delayed stateful reply failed Mar 21 12:25:03 Kamailio440 kamailio[16446]: ERROR: tm [t_reply.c:1893]: relay_reply(): ERROR: relay_reply: cannot alloc reply shmem Mar 21 12:25:03 Kamailio440 kamailio[16446]: ERROR: tm [t_reply.c:545]: _reply_light(): ERROR: _reply_light: cannot allocate shmem buffer Mar 21 12:25:03 Kamailio440 kamailio[16435]: ERROR: tm [t_reply.c:316]: update_totag_set(): ERROR: update_totag_set: no memory Mar 21 12:25:03 Kamailio440 kamailio[16406]: ERROR: ims_dialog [dlg_profile.c:472]: set_dlg_profile(): no more shm memory Mar 21 12:25:03 Kamailio440 kamailio[16406]: ERROR: ims_dialog [ims_dialog.c:619]: w_set_dlg_profile(): failed to set profile Mar 21 12:25:03 Kamailio440 kamailio[16406]: ERROR: tm [t_lookup.c:1289]: new_t(): ERROR: new_t: out of mem: Mar 21 12:25:03 Kamailio440 kamailio[16406]: ERROR: tm [t_lookup.c:1429]: t_newtran(): ERROR: t_newtran: new_t failed root@Kamailio440:~# kamcmd tm.stats { current: 69 waiting: 0 total: 991300 total_local: 0 rpl_received: 2183891 rpl_generated: 20232 rpl_sent: 1475856 6xx: 0 5xx: 2704 4xx: 10124 3xx: 0 2xx: 978329 created: 991300 freed: 991231 delayed_free: 0 } root@Kamailio440:~# kamctl stats shmem shmem:fragments = 1630 shmem:free_size = 4303040 shmem:max_used_size = 536870912 shmem:real_used_size = 532567872 shmem:total_size = 536870912 shmem:used_size = 415668000

1 0

execute only on INITIAL INVITE
by David Villasmil 20 Mar '18

20 Mar '18

Hello guys, I want to execute an sql only for INITIAL INVITEs, I'm trying like: #!ifdef WITH_DID_VALIDATE if(!has_totag()) { sql_query("acd", "select * from did_numbers where didNumber = '$tU' and active = 'Y'", "ra"); xlog("L_ERR", "[REQUEST_ROUTE] number of rows in table domain: $dbr(ra=>rows)\n"); if( $dbr(ra=>rows)==0 ) { xlog("L_ERR", "[REQUEST_ROUTE] DID Number validation returned [$dbr(ra=>rows)], not responding to this request\n"); exit; } sql_result_free("ra"); } #!endif But, say I remove the DID from the allowed list while a call is going on. Then responses to the allowed INVITE would not be processed. How would I limit that to ONLY the INITIAL INVITE? Should I use has_totag? Thanks! David Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

3 4

kamailio 4.4.7 websockets
by draden vandewind 20 Mar '18

20 Mar '18

Hello, Can you explain to me how configure kamailio for to use websocket. I search a kamailio.cfg file with websocket support.... best regards draden

2 1

Security announcement related to Kamailio
by Henning Westerholt 19 Mar '18

19 Mar '18

Hello, as already announced from Daniel-Constantin Mierla on the lists last Wednesday [1], we strongly advise you to update your Kamailio installation to the latest stable release for security reasons. All supported releases (4.4, 5.0. and 5.1) contains two important security fixes related to the tmx and lcr module. Technical details for the tmx issue: A specially crafted REGISTER message with a malformed branch or From tag triggers a so called "off-by-one heap overflow". This vulnerability existed in the tmx module and makes it possible to remotely crash the Kamailio service. If an attacker sends many of this messages this would lead to a Denial of Service of the attacked infrastructure. This is especially critical as no authentication for the remote source is needed. This vulnerability was found from Sandro Gauci and Alfred Farrugia from the Security Company Enable Security. Many thanks to them for finding the issue and reporting it to us. You find all the details including a proof of concept code in the published security announcement from them: https://github.com/EnableSecurity/advisories/tree/master/ES2018-05-kamailio… Technical details for the lcr issue: A vulnerability existed in the lcr next_gw() function. It happens when a very long R-URI username is sent with an INVITE due to an mistake in the function error code handling. It can be triggered from a remote source, but should be only from a trusted peer, as it expected that calls going through lcr are authenticated by user or IP address. This vulnerability was reported from an user in the Netherlands to us, thanks as well for the bug report. So far we are not aware of any public exploits of this errors. But as already mentioned, we advise you to update your Kamailio servers to the latest stable release as soon as possible, especially as the tmx vulnerability will reported to more security lists later today. Please address any detailed technical questions related to the two bugs to the developer list at sr-dev(a)lists.kamailio.org . In case of confidential remarks related to this or other security issues, please address them to the Kamailio Management at management(a)kamailio.org . Best regards, Henning Westerholt Kamailio Project [1] https://lists.kamailio.org/pipermail/sr-users/2018-March/100672.html

1 2

msilo on proxy in front of registrar
by Stefan Sayer 19 Mar '18

19 Mar '18

Hello, I have a bit of a strange situation where I want to add SIP MESSAGE reliability (store and forward) for a proxy that is in front of the (message-wise unreliable) registrar/message originator. So I m_store MESSAGEs in the failure_route of MESSAGE requests. By default, msilo's m_dump works only for REQUEST_ROUTE, thus I can't use that in the 200 to REGISTER. But when I add a function to msilo for ONREPLY_ROUTE (without the check for MESSAGE support) it works. So, is there a reason that there's m_dump only for REQUEST_ROUTE? And, is this: if ((msg->first_line).type == SIP_REQUEST) the correct way to check whether we're handling a request or reply? Also, is there a way to check the expires of contacts in the 200 to REGISTER from the script, so I don't try to m_dump on de-REGISTER? Or does this have to go into the m_dump function for the ONREPLY_ROUTE case? Many thanks for hints! Stefan

2 1

Some clarifications needed on async_task_route
by George Diamantopoulos 19 Mar '18

19 Mar '18

Hello all, I've been exploring the async module a little, and async_task_route() more specifically. I have async_workers set, and the async module loaded. However, whenever this async function is involved in SIP processing, kamailio returns a 500 error to the UAC. I was hoping that someone could confirm that this function is suitable for my needs, I'm not sure I understand the docs very well on this one. So the plan is to have some of the processing of the transaction performed asynchronously, as it is not required for routing etc. Here's an example of what I'm trying to achieve, it's not really critical if NICE_TO_HAVE route functions fail etc, I just need request_route processing to continue normally without waiting for async_task_route("NICE_TO_HAVE") to finish whatever it's going to be doing: request_route() { ... SIP_PROCESSING_A ... async_task_route("NICE_TO_HAVE") ... SIP_PROCESSING_B t_relay(); } route(NICE_TO_HAVE) { dlg_var(sth) = something_derived_from_global_vars(); } Is this possible, or am I completely out of scope here? Thanks! BR, George

2 1

INFO: Relevant fixes in the last releases
by Daniel-Constantin Mierla 19 Mar '18

19 Mar '18

Hello, I want to highlight that the last stable versions (for the latest 3 release series: 4.4, 5.0 and 5.1) include fixes for two issues that can crash a running instance of Kamailio, therefore it is strongly recommended to upgrade if you are using tmx or lcr modules. Next week a CVE report is going to be created with more details about one of these issues. The issues were reported privately, one by security researchers and one by a community member, and were fixed quickly. The code related to the reported issues is rather old (few years by now) and there are no known incidents of exploiting these issues so far. However, once the CVE report comes public, there could be a higher risk of exploitation. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 2

Kamailio World 2018 - grants for students and underrepresented people
by Daniel-Constantin Mierla 19 Mar '18

19 Mar '18

Hello, we are glad to announces that, thanks to the sponsors, we can offer again couple of free seats at Kamailio World Conference, May 14-16, 2018, in Berlin, for students as well as for underrepresented people. In this way we are continuing the program from last years, based on the roots and the tight relation of Kamailio project with the academic environment, the eligible people being students enrolled in universities or research institutes (bachelor, master and PhD programs qualify) as well as people from underrepresented groups. If you think you are eligible and want to participate, email me directly (miconda(a)gmail.com) or to registration(a)kamailio.org . Participation to all the content of the event (workshops, conference and social event) is free, but you will have to take care of expenses for traveling and accommodation. Write a short description about your interest in real time communications and, when it is the case what is the university or the research institute you are affiliate to. Also, if you are not a student, but you are in touch with some or have access to students forums/mailing lists, it will be very appreciated if you forward these details. More information about Kamailio World is available on the web site: - https://www.kamailioworld.com Many thanks to the event sponsors that allowed to continue this program, respectively: Evosip, 2600hz, Sipwise, Sipgate, Simwood, NG-Voice, Evariste Systems, Digium, LOD.com, Pascom, Core Network Dynamics, FhG Fokus and Asipto. Expect a full house event! Looking forward to meeting many of you in Berlin! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Select last URI from Record-Route
by John Petrini 19 Mar '18

19 Mar '18

Hello list, Does anyone how I can extract the last URI from a compact Record-Route header? I've tried using a negative index in the parameter of my select but it returns the first URI in the header instead of the last. $var(rr_last_uri) = @record_route.uri[-1]; Maybe there's another way instead of using selects? Thanks, John

4 7

Select last URI from Record-Route
by Ilie Soltanici 18 Mar '18

18 Mar '18

Hi, Try $(hdr(Record-Route)[-1]), to extract URI only you can use: $(hdr(Record-Route)[0]{nameaddr.uri})

1 0

Logging unregister
by Kjeld Flarup 17 Mar '18

17 Mar '18

Is there a way to get a log entry when a client unregisters incl. when tcp connection is lost for a registration. -- -------------------- Med Liberalistiske Hilsner ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

1 0

kamailio as load balancer
by Seyed Mohammad Mirheydari 16 Mar '18

16 Mar '18

Hi I have 5 asterisk servers. And I want to use kamailio as load balancer. How can route sip calls from outside to asterisk servers? Note: I installed kamailio and mairadb , etc. I configured subscriber for kamailio. And add my 5 servers to databse. Hust to know how to change the file kamailio.cfg to route all incoming calls to my 5 asterisk server (round robin). thanks

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users