November 2015 - sr-users

Kamailio 4.3 and Debian 8.2 systemctl
by Grant Bagdasarian 16 Nov '15

16 Nov '15

Hello, I've just installed Kamailio 4.3 on Debian 8.2, but starting kamailio does not work since Debian requires systemctl to be setup. I've tried the below config but it didn't work (https://github.com/kamailio/kamailio/issues/294#issuecomment-138590939) usr/local/src/kamailio# systemctl status kamailio.service â kamailio.service - Kamailio SIP Server Loaded: loaded (/etc/systemd/system/kamailio.service; disabled) Active: failed (Result: resources) systemd[1]: [/etc/systemd/system/kamailio.service:14] Not an absolute path, ignoring: $PIDFILE systemd[1]: Failed to load environment files: No such file or directory systemd[1]: kamailio.service failed to run 'start' task: No such file or directory systemd[1]: Failed to start Kamailio SIP Server. systemd[1]: Unit kamailio.service entered failed state. [Unit] Description=Kamailio (OpenSER) - the Open Source SIP Server After=syslog.target network.target [Service] Type=forking Environment='PIDFILE=/var/run/kamailio/kamailio.pid' Environment='CFGFILE=/etc/kamailio/kamailio.cfg' Environment='SHM_MEMORY=64' Environment='PKG_MEMORY=8' Environment='USER=kamailio' Environment='GROUP=kamailio' EnvironmentFile=/etc/default/kamailio PIDFile=$PIDFILE # ExecStart requires a full absolute path ExecStart=/usr/sbin/kamailio -P $PIDFILE -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -u $USER -g $GROUP ExecStopPost=/bin/rm -f $PIDFILE Restart=on-abort [Install] WantedBy=multi-user.target Does anyone have a working kamailio.service file? Regards, Grant

4 3

TLS module not initialized in 4.3.3, worked in 4.1.5
by Sebastian Damm 16 Nov '15

16 Nov '15

Hello, we just updated one kamailio server from 4.1.5 to 4.3.3, and although the config file is correct and kamailio starts up, it doesn't initialize TLS and says " tls support enabled, but no tls engine available (forgot to load the tls module?)" In the log I see: Old shutdown (last lines): Nov 13 11:44:38 lasola /usr/sbin/kamailio[15890]: DEBUG: <core> [mem/shm_mem.c:235]: shm_mem_destroy(): destroying the shared memory lock Nov 13 11:44:41 lasola /usr/sbin/kamailio[14818]: ERROR: <core> [tcp_read.c:271]: tcp_read_data(): error reading: Connection reset by peer (104) Nov 13 11:44:41 lasola /usr/sbin/kamailio[14818]: ERROR: <core> [tcp_read.c:1296]: tcp_read_req(): ERROR: tcp_read_req: error reading New startup (first lines): Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: DEBUG: <core> [daemonize.c:583]: set_core_dump(): core dump limits set to 18446744073709551615 Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: WARNING: <core> [main.c:2475]: main(): tls support enabled, but no tls engine available (forgot to load the tls module?) Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: WARNING: <core> [main.c:2476]: main(): disabling tls... Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: DEBUG: <core> [async_task.c:88]: async_task_init(): start initializing asynk task framework Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: DEBUG: <core> [sr_module.c:959]: init_mod(): xmlrpc Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <bind_sl> in module sl [/usr/lib/x86_64-linux-gnu/kamailio/modules//sl.so] Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: DEBUG: <core> [sr_module.c:959]: init_mod(): sl In our config file we have the following lines for TLS (pretty late, after all other module loading and after most parameters): #!ifdef ENABLETLS loadmodule "tls.so" modparam("tls", "private_key", "/etc/ssl/private/my.kamailio-key.pem") modparam("tls", "certificate", "/etc/ssl/certs/my.kamailio.crt") #!ifdef TLS_CA_CHAIN # Maybe we want to use a chain to the CA modparam("tls", "ca_list", "/etc/ssl/certs/my.ca-bundle.crt") #!endif enable_tls=1 listen=tls:1.2.3.4:5061 #!endif After starting up, kamailio listens on port 5060, but not on port 5061. In version 4.1.1, this config worked without a problem. Has anybody seen this before? the tls module is there and available, it doesn't say anything about "cannot load module", and it is only a warning message. I'm also wondering, why this message is the first after starting the server. From config I would expect that sl, tm and all the other modules should be initialized before tls. Best Regards, Sebastian

2 9

Detecting problems of kamailio under very high load
by aft 16 Nov '15

16 Nov '15

We have multiple kamailio servers with 4 cpu cores and 16G RAM. We use kamailio+rtpproxy as a outbound sip proxy. Usually there are many thousands of concurrent sip sessions of occurring there. Periodically sometimes it just stops serving request and spits out 5** replies. At that point we usually reload the kamailio daemon and things return back to normal. As we have a lot of servers, manually doing this is a pain in the neck. So We installed a homer/sipcapture on a separate server . And from there, we periodically scan for 500 msgs for a given time interval. If there are any, we then proceed to reload kamailio. I know its hell of an inefficient system to monitor. So I'm wondering, if there can be any more rational way to detect problems pre-emptively. any fifo/mi command which we could run to find out if the kamailio instance is hung up? Cheers Arif

3 2

Loading mohqueue stops kamailio from starting up
by David Villasmil Govea 14 Nov '15

14 Nov '15

Hello all, I installed kamailio on debian from kamailio's apt repository. Configured it with kamdbctl, started it up properly, no issues. I configured mysql also, worked properly. Next i loaded up "mohqueue" and everything went to hell :) This is my config: loadmodule "mohqueue.so" # ----- moh-queue ----- modparam ("mohqueue", "db_url", "mysql://user:password@localhost/kamailio") modparam ("mohqueue", "db_qtable", "mohqueue") modparam ("mohqueue", "db_ctable", "mohqcalls") modparam ("mohqueue", "mohdir", "/var/kamailio/MOH") and my db table for mohqueue is: +----+------------+-------------------------+--------------------+---------+-------+ | id | name | uri | mohdir | mohfile | debug | +----+------------+-------------------------+--------------------+---------+-------+ | 1 | test_queue | sip:1234@172.16.163.130 | /var/kamailio/MOH/ | test | 9 | +----+------------+-------------------------+--------------------+---------+-------+ when starting, i get: ... 0(5069) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_relay> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(5069) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_forward_nonack> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(5069) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_release> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(5069) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <load_rr> in module rr [/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so] 0(5069) DEBUG: <core> [sr_module.c:695]: find_mod_export_record(): find_export_record: <rtpproxy_answer> not found 0(5069) ERROR: mohqueue [mohq.c:390]: mod_init(): Unable to load rtpproxy_answer 0(5069) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module mohqueue (/usr/lib/x86_64-linux-gnu/kamailio/modules/mohqueue.so) ERROR: error while initializing modules Anyone can help? Thanks! -- DVG -- Imagination is more important than knowledge Albert Einstein

2 2

(no subject)
by David Villasmil Govea 14 Nov '15

14 Nov '15

Hello guys, I'm trying to startup 4.3 and i'm getting the following: 0(4420) DEBUG: <core> [db_row.c:117]: db_allocate_row(): allocate 192 bytes for row values at 0x7fe6bf6b5a48 0(4420) DEBUG: <core> [db_val.c:74]: db_str2val(): converting INT [1] 0(4420) DEBUG: <core> [db_val.c:118]: db_str2val(): converting STRING [ sip:1234@172.16.163.130] 0(4420) DEBUG: <core> [db_val.c:118]: db_str2val(): converting STRING [/var/kamailio/MOH/] 0(4420) DEBUG: <core> [db_val.c:118]: db_str2val(): converting STRING [test.8] 0(4420) DEBUG: <core> [db_val.c:118]: db_str2val(): converting STRING [test_queue] 0(4420) DEBUG: <core> [db_val.c:74]: db_str2val(): converting INT [9] 0(4420) ERROR: mohqueue [mohq_db.c:504]: update_mohq_lst(): Queue,Field (test_queue,mohdir): Unable to find MOH files (/var/kamailio/MOH//test.8.*)! 0(4420) DEBUG: <core> [db_pool.c:100]: pool_remove(): removing connection from the pool 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <bind_sl> in module sl [/usr/lib/x86_64-linux-gnu/kamailio/modules/sl.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <load_tm> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_newtran> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_relay_to_tcp> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_relay_to_udp> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_relay> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_forward_nonack> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <t_release> in module tm [/usr/lib/x86_64-linux-gnu/kamailio/modules/tm.so] 0(4420) DEBUG: <core> [sr_module.c:689]: find_mod_export_record(): find_export_record: found <load_rr> in module rr [/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so] 0(4420) DEBUG: <core> [sr_module.c:695]: find_mod_export_record(): find_export_record: <rtpproxy_answer> not found 0(4420) ERROR: mohqueue [mohq.c:390]: mod_init(): Unable to load rtpproxy_answer 0(4420) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module mohqueue (/usr/lib/x86_64-linux-gnu/kamailio/modules/mohqueue.so) ERROR: error while initializing modules Any help is appreciated, Thanks! -- DVG -- Imagination is more important than knowledge Albert Einstein

2 1

Kamailio queues
by David Villasmil Govea 13 Nov '15

13 Nov '15

Hello Guys, I'm new to this list. I'm trying to setup a queue with 4.3.3 (x86_64/linux) and I see a couple of things i'm wondering about: - kamdbctl created the table "mohqueues" and the associated value in the "version" tables. Whereas kamailio uses "mohqueue" (no extra "s" at the end). - after fixing that, it finds the table, but when searching for the moh file, which i set as "/var/kamailio/MOH/test.8" on the mohqueue table, but kamailio can't find it: 0(61540) ERROR: mohqueue [mohq.c:390]: mod_init(): Unable to load rtpproxy_answer 0(61540) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module mohqueue (/usr/lib/x86_64-linux-gnu/kamailio/modules/mohqueue.so) ERROR: error while initializing modules ls -l /var/kamailio/MOH/test.8 -rw-rw-rw- 1 root root 166038 Jun 10 2009 /var/kamailio/MOH/test.8 Can anyone lend a hand? Thanks! David -- DVG -- Imagination is more important than knowledge Albert Einstein

1 0

Re: [SR-Users] Flaky & unstable RTP connections
by Infinicalls Infinicalls 13 Nov '15

13 Nov '15

Hi, I have started RTP with # ./rtpproxy -F -l localhost -s udp:*:7890 and when I issue #netstat -pln | grep rtpp I get, udp 0 0 0.0.0.0:7890 0.0.0.0:* 8759/rtpproxy I am using another similar instance of RTP also. Still my connection seems to be flaky. This doesn't occur always. I am not using dispatcher here. Simple rtpproxy with udp:rtp1 and udp:rtp2 in kamailio.cfg file. Is there anyway to tell if RTP is healthy other than making calls and finding out? Can somebody test it from your end? Or is this problem client specific? I am using microlite and sipper on windows. phone.infinicalls.com u:test;p:test123 u:trial;p:trial123 5060 regards Ganesh Kumar

1 0

Support-for-AKAv2-MD5-authentication-in-kamailio
by Anil Kumar 13 Nov '15

13 Nov '15

Hi, I want to enable AKAv2-MD5 type authentication using a plain kamailio. Is there any way I can achieve it ? Please do needful. Thanks Anil

2 1

Kamailio with Siremis
by Ryan Holbein 12 Nov '15

12 Nov '15

Hello, I have setup with my phone provider an IP endpoint to do IP Auth. How would I go about setting that up in Kamailio or even better can some tell me how to do that in Siremis?

2 5

issue with uac_req_send to websocket peer
by Vasiliy Ganchev 12 Nov '15

12 Nov '15

Hi folk! Have a scenario: UA-A -> REGISTER -> kamailio kamailio make auth, and save(location), after this, before exit, I want to send to UA-A a custom NOTIFY with specific event (this should be done without SUBSCRIBE/PUBLISH/NOTIFY logic) .... $uac_req(method) = "NOTIFY"; $uac_req(ruri) = $sel(contact.uri); $uac_req(furi) = "sip:service@" + $rd; $uac_req(turi) = $sel(contact.uri); $uac_req(hdrs) = ......... here custom header is added xlog("L_ERR", "debuginfo, NOTIFY to ru $uac_req(ruri), fu $uac_req(furi); uac_req_send(); ............ when UA-A is connected via UDP/TCP/TLS - works OK when UA-A connected via WS/WSS", have errors: Nov 10 14:59:29 /usr/sbin/kamailio[6260]: ERROR: <script>: debuginfo, NOTIFY to ru sip:251@10.100.1.218:47114;transport=ws, fu sip:service@10.100.1.85, Nov 10 14:59:29 /usr/sbin/kamailio[6260]: WARNING: <core> [msg_translator.c:2799]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Nov 10 14:59:29 /usr/sbin/kamailio[6260]: ERROR: tm [t_msgbuilder.c:1365]: assemble_via(): assemble_via: via building failed Nov 10 14:59:29 /usr/sbin/kamailio[6260]: ERROR: tm [t_msgbuilder.c:1545]: build_uac_req(): build_uac_req(): Error while assembling Via Nov 10 14:59:29 /usr/sbin/kamailio[6260]: ERROR: tm [uac.c:379]: t_uac_prepare(): t_uac: Error while building message I see no problem with ws connect (calls to/from this ws peer works OK), immediately after registration: root@local:/home/admin# kamctl fifo ws.dump 2: wss:127.0.0.1:40239 -> wss:127.0.0.1:5061 (state: OPEN, last used 5s ago, sub-protocol: sip) The difference in UDP/TCP/TLS from WS/WSS - that first connects directly to Kamailio to port 5060/5061, but second connects to custom ports, where listen special daemon and proxy sip to kamailio 5060/5061 via localhost I tried also to add in script $uac_req(sock) = "tls:127.0.0.1:5061"; but the result is the same version: kamailio 4.2.5 (i386/linux) any suggestion? cheers -- View this message in context: http://sip-router.1086192.n5.nabble.com/issue-with-uac-req-send-to-websocke… Sent from the Users mailing list archive at Nabble.com.

2 2