- sr-users - kamailio.org

Kamailio v4.4.0 Released - new major version is out
by Daniel-Constantin Mierla 30 Mar '16

30 Mar '16

Kamailio v4.4.0 is out – it comes with 9 new modules and a consistent set of improvements touching more than 60 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v4-4-0-release-notes/ Many thanks to all developers and community members that made possible this release. Enjoy Kamailio v4.4.0! The development will start to focus on 5.0.0 - join the discussion on sr-users mailing list to design and decide what should Kamailio 5.0.0 look like - some notes are already collected at: * https://www.kamailio.org/wiki/devel/kamailio-5.0-design Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

1 0

Releasing Kamailio v4.4.0
by Daniel-Constantin Mierla 30 Mar '16

30 Mar '16

Hello, with no major issues reported lately, I think we are on a good track for releasing stable v4.4.0. Next week a lot of people prepare for Easter, therefore I propose to do the release on Wednesday, March 30, 2016. If new things pop up, the exact date can be adjusted a bit before or after the current proposal. Any new discovered issue should be reported to bug trucker: * https://github.com/kamailio/kamailio/issues Help to complete the upgrade guide would be very appreciated: * https://www.kamailio.org/wiki/install/upgrade/stable-to-devel A draft list of what is new in 4.4 is already available at: * https://www.kamailio.org/wiki/features/new-in-4.4.x Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

1 2

Kamailio local and hosted
by Sébastien Brice 29 Mar '16

29 Mar '16

Hi everyone At my workplace there's plenty of hardphone directly connected to an hosted sbc in the cloud. As an added value i proposed to add locally Kamailio as a proxy server to 'federate' all the sip traffic. ipphone behind nat (A) <---> sip proxy local 192.168.x.x (B)<----> sbc registrar (mydomain.com) and sip proxy with public IP (C) when hardphone try to register, B rewrite (with rewritehost) the ip public of (C). B then uses exported function of TM to t_relay_to(C). to route INVITE from A to C i use proxy_authenticate("mydomain.com") function (on B) from auth_db to pass the calls inbetween. This works well, but i am wondering if that makes sense if i get several phones behind B. Should stateless forward works better in this kind of scenario? In a near future i plan to offer disaster recovery, and i want all users binding to C (users(a)mydomain.com)instead bind on B (in case link B---C get down)and assume some kind of telephone functionnality Is that possible ? Do you have some sort of example Kamailio do it good On-premise/localy ? How to deal with nat since all hardphones have rfc1918 address? , thx you PS: as an sbc (C) i did setup kamailio/asterisk in a real-time configuration. Sébastien BRICE VoIP, Support et Intégration

1 1

Proxy configuration
by Jignesh Gandhi 29 Mar '16

29 Mar '16

Hello, Is it possible to use kamailio to be a stateful outbound proxy ? The use case is kamailio is an outbound proxy for multiple instances of Asterisk. Thus all responses need to go back to the same instance of Asterisk that generated them. After the call is established. How can I ensure that the Re-Invites, BYEs, etc are sent to the same instance of Asterisk that generated the outbound Invite ? Any help is appreciated. Thanks, --Jignesh

2 1

Destination Timeout (ACK message)
by Al S 29 Mar '16

29 Mar '16

Hi, The destination node is down. By adding the following code Kamailo re-routing INVITE to a new destination after getting 408 timeout (as below). failure_route[MANAGE_FAILURE]{ if (t_branch_timeout()) { # change to new destination IP $rd = "10.10.10.10"; t_relay(); exit; }...} However, the ACK message coming from source is still being send to the old destination. How can I reroute other messages in the dialog to be sent to this new destination.. Thank, AS

1 0

SIP / WebRTC / GSoC proposals
by Daniel Pocock 29 Mar '16

29 Mar '16

Hi all, We had a few GSoC applications[1] from students who would like to do work relating to SIP and WebRTC this summer. The students have a range of skills. Some are interested in the server side (C, C++) code. Some are interested in Android and Java projects (e.g. the Lumicall and CSipSimple dialers) and some are web developers, interested in making practical use of WebRTC. Would anybody else from the community be interested in helping to mentor one of these projects? Prospective mentors can review the proposals privately before making any firm commitment, please contact me for details. Mentors can have some input in the direction of the students' work, just as long as all code is released publicly. Regards, Daniel 1. http://danielpocock.com/gsoc-2016-voice-video-chat

2 2

XML-RPC reply doesn't contain any data
by Arsen 29 Mar '16

29 Mar '16

Hi guys! We have an issue with XML-RPC module. >From this doc: http://kamailio.org/docs/modules/4.3.x/modules/xmlrpc.html "Success replies always contain at least one return value. In our case the simplest success replies contain single boolean with value 1" We are trying to reload domain module after adding/removing new domain, so we send the following request: XX - web server; YY - kamailio T XX.XX.XX.XX:55028 -> YY.YY.YY.YY:8080 [AP] POST /RPC2 HTTP/1.1. Host: YY.YY.YY.YY:8080. Accept: */*. Accept-Encoding: deflate, gzip. User-Agent: cURL. Accept-Charset: UTF-8. Content-Length: 120. Content-Type: application/x-www-form-urlencoded. . <?xml version="1.0" encoding="iso-8859-1"?> <methodCall> <methodName>domain.reload</methodName> <params/> </methodCall> T YY.YY.YY.YY:8080 -> XX.XX.XX.XX:55028 [AP] HTTP/1.1 200 OK. Sia: SIP/2.0/TCP XX.XX.XX.XX:55028. Server: kamailio (4.3.4 (x86_64/linux)). Content-Length: 108. . <?xml version="1.0"?> <methodResponse> <params> <param> <value></value> </param> </params> </methodResponse> As you can see in the response from the kamailio there is no any data, so our script is waiting until timeout... Please advice. Thanks, -- Regards, Arsen.

4 6

Timeout Handling (update)
by Al S 28 Mar '16

28 Mar '16

Hi, I am trying to re-route to a different $ru after timeout and right before Kamailio reply with a 408.I made the changes right before sl_reply_error(), however it does not work as I expected. Any help will be appreciated. Also, $rm represents the request message received by Kamailio. Is there a variable represents the messages leaving Kamailio?. route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|SUBSCRIBE")) { t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { // re-route to a new $ru before sending 408 sl_reply_error(); } exit;} Thanks,AS

2 2

using DMQ , Kamailio shutsdown
by Sunil More 28 Mar '16

28 Mar '16

Hello All, I am running two instances of kamailio and using dmq. Kamailio starts good. However one of the node shutsdown unexpectedly. Unsure what is going wrong. Please let me know what could be wrong. below is a the conf detail. loadmodule "dmq.so" modparam("dmq", "server_address", "sip:sunilmore.in:5060") modparam("dmq", "notification_address", "sip:sunilmore.in:5064") loadmodule "usrloc.so" modparam("usrloc", "db_mode", 2) modparam("usrloc", "db_url", DBURL2) modparam("usrloc", "use_domain", 1) modparam("usrloc", "matching_mode", 0) modparam("usrloc", "desc_time_order", 1) modparam("usrloc", "nat_bflag", FLB_NATB) modparam("usrloc", "db_insert_null", 1) loadmodule "dmq_usrloc.so" modparam("dmq_usrloc", "enable", 0) Below is the backtrace of the logs. ar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 11: kex Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: kex [kex_mod.c:161]: child_init(): rank is (11) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [srid-56f4d496-36d7-] (0 / 19) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 11: mi_rpc Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 11: ndb_redis Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14013]: DEBUG: <core> [main.c:1723]: main_loop(): Expect maximum 2177 open fds Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14040]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 12: htable Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14040]: DEBUG: htable [htable.c:237]: child_init(): rank is (12) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14040]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 12: websocket Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14040]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 12: mi_datagram Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: tm Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: tm [callid.c:134]: child_init_callid(): DEBUG: callid: ' 0e4b331663a1f7ae-14041(a)sunilmore.in' Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: tmx Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: tmx [tmx_mod.c:272]: child_init(): rank is (-4) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: sl Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: tls Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: ndb_mongodb Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: dmq Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: usrloc Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [ulcx-56f4d496-36d9-] (0 / 19) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14040]: DEBUG: <core> [local_timer.c:61]: init_local_timer(): timer_list between 0xa762c8 and 0xaba2c8 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: dmq_usrloc Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14040]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa76100, 40, 1, (nil)), fd_no=0 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 11: htable Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: htable [htable.c:237]: child_init(): rank is (11) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 11: websocket Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank 11: mi_datagram Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: dmq_usrloc [dmq_usrloc.c:110]: child_init(): child_init PROC_INIT Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: registrar Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [uloc-56f4d496-36d9-] (0 / 19) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: nathelper Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: nat_traversal Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: mi_fifo Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: avpops Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: rtimer Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: dialog Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: domain Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: uac Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: presence Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: kex Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: kex [kex_mod.c:161]: child_init(): rank is (-4) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [srid-56f4d496-36d9-] (0 / 19) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: mi_rpc Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: ndb_redis Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: htable Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: htable [htable.c:237]: child_init(): rank is (-4) Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: websocket Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [sr_module.c:914]: init_mod_child(): rank -4: mi_datagram Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [local_timer.c:61]: init_local_timer(): timer_list between 0xa762c8 and 0xaba2c8 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14039]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa76100, 38, 1, (nil)), fd_no=0 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [local_timer.c:61]: init_local_timer(): timer_list between 0xa32028 and 0xa76028 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 8, 1, 0x7fab28a78438), fd_no=0 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 9, 1, 0x7fab28a786a8), fd_no=1 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 10, 4, 0x7fab082bb21c), fd_no=2 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 11, 4, 0x7fab082bb2a8), fd_no=3 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 12, 4, 0x7fab082bb334), fd_no=4 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 13, 4, 0x7fab082bb3c0), fd_no=5 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 14, 4, 0x7fab082bb44c), fd_no=6 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 15, 4, 0x7fab082bb4d8), fd_no=7 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 16, 4, 0x7fab082bb564), fd_no=8 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 17, 4, 0x7fab082bb5f0), fd_no=9 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 18, 4, 0x7fab082bb67c), fd_no=10 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 19, 4, 0x7fab082bb708), fd_no=11 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 20, 4, 0x7fab082bb794), fd_no=12 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 21, 4, 0x7fab082bb938), fd_no=13 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 22, 4, 0x7fab082bb9c4), fd_no=14 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 23, 4, 0x7fab082bba50), fd_no=15 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 24, 4, 0x7fab082bbadc), fd_no=16 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 27, 4, 0x7fab082bbb68), fd_no=17 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 25, 4, 0x7fab082bbbf4), fd_no=18 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 26, 4, 0x7fab082bbc80), fd_no=19 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 29, 4, 0x7fab082bbd0c), fd_no=20 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 31, 4, 0x7fab082bbd98), fd_no=21 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 28, 3, 0x7fab28d647f0), fd_no=22 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 30, 3, 0x7fab28d64810), fd_no=23 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 36, 3, 0x7fab28d64830), fd_no=24 Mar 25 06:03:02 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0xa31e60, 39, 3, 0x7fab28d64850), fd_no=25 Mar 25 06:03:03 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:03 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:04 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:04 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:05 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:05 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:06 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:06 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:07 P172 /usr/local/kamailio/sbin/kamailio[14027]: DEBUG: tm [h_table.c:127]: free_cell_helper(): freeing transaction 0x7fab0853a9d8 from timer.c:648 Mar 25 06:03:07 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:07 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:08 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:08 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:09 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:09 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:10 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:10 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:11 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:11 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:12 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:12 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:13 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:13 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:458]: wsconn_get_list(): wsconn_get_list Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14034]: DEBUG: websocket [ws_conn.c:502]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14041]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 21 Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [tcp_main.c:3448]: handle_ser_child(): dead child 14, pid 14031 (shutting down?) Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14041]: DEBUG: <core> [io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0xa31e60, 21, -1, 0x0) fd_no=26 called Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14013]: ALERT: <core> [main.c:739]: handle_sigs(): child process 14031 exited by a signal 11 Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14013]: ALERT: <core> [main.c:742]: handle_sigs(): core was generated Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14013]: INFO: <core> [main.c:754]: handle_sigs(): terminating due to SIGCHLD Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14013]: DEBUG: <core> [main.c:756]: handle_sigs(): terminating due to SIGCHLD Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14038]: INFO: <core> [main.c:809]: sig_usr(): signal 15 received Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14040]: INFO: <core> [main.c:809]: sig_usr(): signal 15 received Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14037]: INFO: <core> [main.c:809]: sig_usr(): signal 15 received Mar 25 06:03:14 P172 /usr/local/kamailio/sbin/kamailio[14035]: INFO: <core> [main.c:809]: sig_usr(): signal 15 received There were no UAs that tried to register while this error occured. Thanking You, Sunil More Ph : 9503338275

2 4

Kamailio Dispatcher error msg 407
by Rex Lin (林昱頡) 28 Mar '16

28 Mar '16

Hi admins, I'm kinda new in this group and I'm not quite sure if I'm posting in a correct way, advise if I'm wrong. below is my post. ------------------------------------------------------------------------------------------------------------------------------------ I would like to activate Dispatcher module for apply Load Balance functionality purpose. but it's been hard to complete so far, I wonder if you can give me some advise in below situation. we have 2 Kamailios, the version is 4.3.3 ; we use domain for the SIP registration. we want to make Kamailios work in double active mode for SIP load balancing, we have a F5 to do the domain name round robin to make two UAC regitering under two UAS. I have put the "route(DISPATCH) b4 PSTN in request_route. when I try to make UAC-A call to UAC-B, it appears 407 proxy authentication required. we wiresharked, UAS has sent INVITE to UAS-B, but UAS-B sent the error code 407 to UAS-A Is the configuration has to be set to "UAS-B accepting INVITE of UAS-A" ? or the UAS-A should carrying the auth info into UAS-B ? detail configuration as below. ------------------------------------------------------------------------------------------------------------------------------------ dispatcher params modparam("dispatcher", "list_file", "/usr/local/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 1) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "ds_ping_from", "sip:kamailio1@awesomedomain.com") modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 1) DISPATCHER Routing route[DISPATCH] { # round robin dispatching on gateways group '1' if(!ds_select_dst("1", "4")) { send_reply("404", "No destination"); exit; } xdbg("--- SCRIPT: going to <$ru> via <$du>\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } # Re-route in case of failure failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } # next node - only for 500 or local timeout if (t_check_status("500") || (t_branch_timeout() && !t_branch_replied())) { if(ds_next_dst()) { t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } Best Regards, Rex Lin

2 3

Custom Authentication module with Java Code
by Jungtae Kim 28 Mar '16

28 Mar '16

Hello, I'm new to Kamailio. I'm trying to make my own auth module to check if incoming SIP messages are sighed with a correct key. I want to do this by calling a Java code snippet. I found app_java module but I can't figure out if this will support my usecase. Does app_java allow me to call Java code from another module? If not, what can I do to meet my use case? My token verification code is written in Java, so I'd like to reuse my code if possible. Thanks

2 1

Kamailio return response
by Shiv Patidar 28 Mar '16

28 Mar '16

i run client socket program for send SIP request to kamailio server kamailio registration is done successfully with 200OK and i want to store 200OK in client.c program in structure like struct reg_db { char *to char *from char ..... ....... } please help me how to store ?

2 1

Two different Database at the same time
by Barış Şekerciler 28 Mar '16

28 Mar '16

Hello,I want to use Cassandra and PGSQL at the same time in Kamailio. Is that possible?For example, for CDR records I want to use Cassandra and for other things I want to use PostgreSQL. Regards.

2 4

Re: [SR-Users] Kamailio PostgreSQL Asking Password Everytime
by Barış Şekerciler 26 Mar '16

26 Mar '16

Hello Daniel,Thanks for your reply. So I can't see any password for root user option in the kamctlrc file by default.How can I add? Regards.Barış. To: sr-users(a)lists.sip-router.org From: miconda(a)gmail.com Date: Wed, 23 Mar 2016 08:26:58 +0100 Subject: Re: [SR-Users] Kamailio PostgreSQL Asking Password Everytime Hello, I haven't used the postgres in a long while, but I think it should ask only once. Can you try by setting the password inside the kamctlrc file and see if works straight away? Cheers, Daniel On 22/03/16 11:52, Barış Şekerciler wrote: Hello, I have one postgres server at one server and Kamailio at another server. So I believe I did true configuration to the Kamailio. Actually I made some tests and I could create user and authenticated etc. But I have a problem. When I tried to present "kamdbctl create" Kamailio asks password 50 times (almost, much or less idk certainly). After 50 times Db created successfully and works. And it looks like this: root@bs-kamailio:/home/bs-kamailio# kamdbctl create INFO: creating database kamailio ... Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: So how can I solve this situation? I want Kamailio to asks password one time and handle it's job. Regards. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

2 3

Kamailio PostgreSQL Asking Password Everytime
by Barış Şekerciler 25 Mar '16

25 Mar '16

Hello,I have one postgres server at one server and Kamailio at another server.So I believe I did true configuration to the Kamailio. Actually I made some tests and I could create user and authenticated etc. But I have a problem. When I tried to present "kamdbctl create" Kamailio asks password 50 times (almost, much or less idk certainly).After 50 times Db created successfully and works. And it looks like this: root@bs-kamailio:/home/bs-kamailio# kamdbctl create INFO: creating database kamailio ... Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: Password for user postgres: So how can I solve this situation? I want Kamailio to asks password one time and handle it's job. Regards.

3 2

Custom Authentication module with Java code
by Jungtae Kim 25 Mar '16

25 Mar '16

Hello, I'm new to Kamailio. I'm trying to make my own auth module to check if incoming SIP messages are sighed with a correct key. I want to do this by calling a Java code snippet. I found app_java module but I can't figure out if this will support my usecase. Does app_java allow me to call Java code from another module? If not, what can I do to meet my use case? My token verification code is written in Java, so I'd like to reuse my code if possible. Thanks

1 0

Re: [SR-Users] Multiple LCR instances with LCR module
by DanB 25 Mar '16

25 Mar '16

Hey Juha, Many thanks for so quick feedback! Changing the module param did the trick. Have a good one! DanB

1 0

Problem with authdb and view(?)
by Jon Bonilla (Manwe) 25 Mar '16

25 Mar '16

Hi all I've created a "subscriber" table which is a view of a asterisk sippeers table. The view is created as follows: create view subscriber as select id, name as username, fromdomain as domain, secret as password, email as email_address, md5secret as ha1, md5secret as ha1b, NULL as rpid from sippeers where type="friend"; and one of the resulting subscribers looks like this: *************************** 5. row *************************** id: 100022 username: user domain: domain.com password: plain or empty email_address: user(a)domain.com ha1: 3a4f5cc8dc0efb0d899cawe4dec9ea08 ha1b: 3a4f5cc8dc0efb0d899cawe4dec9ea08 rpid: NULL But when I try to register I get ERROR in the logs: New request - M=REGISTER R=sip:domain.com F=sip:user@domain.com ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Unknown column 'md5secret' in 'field list' ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query ERROR: auth_db [authorize.c:187]: get_ha1(): failed to query database Is there any problem with views? Why the logs talks about md5secret column when it should see ha1? cheers, Jon

1 1

Multiple LCR instances with LCR module
by DanB 25 Mar '16

25 Mar '16

Hey Guys, I was wondering if any of you use multiple LCR instances with LCR module since I could see that the documentation allows it, however for some reason the queries to load data (both on restart or kamcmd lcr.reload) somehow hardcode the value of 1 inside: """ select `gw_name`,`ip_addr`,`port`,`uri_scheme`,`transport`,`params`,`hostname`,`strip`,`prefix`,`tag`,`flags`,`defunct`,`id` from `lcr_gw` where `lcr_id`=0 select `gw_name`,`ip_addr`,`port`,`uri_scheme`,`transport`,`params`,`hostname`,`strip`,`prefix`,`tag`,`flags`,`defunct`,`id` from `lcr_gw` where `lcr_id`=1 select `id`,`prefix`,`from_uri`,`stopper`,`enabled`,`request_uri` from `lcr_rule` where `lcr_id`=1 select `rule_id`,`gw_id`,`priority`,`weight` from `lcr_rule_target` where `lcr_id`=1 """ My kamailio version: """ # kamailio -V version: kamailio 4.3.5 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 4.9.2 """ Many thanks in advance for any kind of tip! DanB

2 1

kamailio memory issue
by Volodymyr Rykhva 25 Mar '16

25 Mar '16

Hi, I have started using kamailio recently. Added to db almost 100K users. And now I am trying to increase shared and private memory with this command when server is running: kamailio -M 12 -m 128. But then I check it with `kamailio -l` and the same values (64 and 8 respectively) are there. Can I change it with config? or what I do wrong. And what's the purpose of child process? - Will kamailio process requests faster if I set child=32 (for example)? Thanks and best regards, Volodymyr

2 1

Re: [SR-Users] htable - banning users
by meres 24 Mar '16

24 Mar '16

Thank u Vasiliy and Daniel, I used -3 condition as you suggested! Regards, meres

1 0

dynamic weighting for dispatcher
by Brooks Bridges 24 Mar '16

24 Mar '16

So I'm building a load balancer solution that needs to monitor remote devices at a specific interval via snmp for certain data (channels and cps) and use that data to create a dynamically updated weight for each of the destinations. I can't find any reasonable mechanism for updating the weight attribute in the dispatcher module itself without having to do some hacky "update the database column then trigger dispatcher.reload" script, which I very much want to avoid. Is this something I should just be thinking of ditching the dispatcher module and rolling my own design or am I missing something obvious? Brooks Bridges | Sr. Voice Services Engineer O1 Communications 5190 Golden Foothill Pkwy El Dorado Hills, CA 95762 office: 916.235.2097 | main: 888.444.1111, Option 2 email: bbridges(a)o1.com<mailto:bbridges@o1.com> | web: www.o1.com<http://www.o1.com/>

2 2

Dispatching Registrations to Weight based servers
by SamyGo 24 Mar '16

24 Mar '16

Hi All, I'm having a wee little bit of difficulty in trying to load-balance registrations to multiple servers based on their weights. Kind of similar scenario as discussed in this thread: http://lists.sip-router.org/pipermail/sr-users/2014-December/086235.html The problem I'm facing is that dispatcher is always choosing the first destination from the group. I do suspect that dispatcher is not considering registrations as load at all and only counts INVITES as load. If above is correct then is there a way to use dispatcher to count registrations as load ? Thanks, Sammy

2 3

Kamailio 5.0 - B2BUA
by Alex Balashov 24 Mar '16

24 Mar '16

Hi, I wanted to raise the possibility of an inline signalling-only B2BUA component to Kamailio. I know that's an extremely poor fit for Kamailio, and not at all what it's supposed to do. And there are many things about the OpenSIPS B2BUA module that reveal how awkwardly it is situated, as a square peg in a round hole. I myself am philosophically opposed to a B2BUA in Kamailio to the threshold of physical violence. However, the reason I bring it up for discussion is that there are very few viable, high-performance signalling-only B2BUA alternatives that are FOSS. There is enormous demand for a B2BUA, mainly for topology concealment purposes, from the short-duration traffic industry, which many users of Kamailio deal with. It's why a lot of them end up going to OpenSIPS; they need the B2BUA, and prefer to consolidate on one OpenSER brand. Anyone who has tried to run high-CPS traffic through the existing FOSS signalling-only B2BUAs out there situated in front of Kamailio has discovered, sometimes in a very financially painful way, that: - FreeSWITCH falls over at around +/- 300 CPS. This is with RTP relay disabled -- signalling-only. It requires horizontally scaling a large number of FreeSWITCH boxes to meet a capacity requirement of, say, 2000 CPS, which is unfortunate given the favourable proposition offered by Kamailio for the infrastructure unit economics. In other words, it's ironic to have to build a fleet of 10 FreeSWITCH boxes for the 1% problem of topology concealment when Kamailio can otherwise churn through 2000 CPS with no issues. - SEMS' 'sbc' module is a good candidate and can handle the load, but Frafos offers practically no support for it, with all efforts focused on their commercial ABC SBC product. That's very understandable, but just not practical given the high technical knowledge SEMS requires to deploy and maintain in this capacity. - None of the other userspace B2BUA folk traditions can handle the load. So, like I said, I personally recoil in shock and horror at the idea of introducing a B2BUA into something that was designed to be anything but a B2BUA. But, there is a huge market opportunity for this functionality in North America, and at the moment, users who need it are mostly ending up in OpenSIPS land. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

8 15

Presence Publish expires
by Igor Olhovskiy 24 Mar '16

24 Mar '16

Hi! Is there any possibility to set Expires in PUBLISH message to never in Presence module? I want to have BLF’s that indicates states, that driven via PUBLISH, but can be really irregular (let’s say once a week) -- Best regards, Igor

3 5

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